JPH09261346A - Service managing device and service controller for exchange network - Google Patents

Abstract

PROBLEM TO BE SOLVED: To compress data to be transferred to a service controller, to shorten a transfer time and to attain efficient database version-number management by giving the number of versions to a place to be updated at the time of updating service data. SOLUTION: A DB text Updata & Stack requesting part 11 receives a record index key and data attending it by the input of an operator, a record index is reported to a DB Allocate part 12 and the acquisition request of a service controller identifier is executed. The part 12 selects the transfer destination of the record index key from plural service devices by a random number processing so as to generate the identifier, to give it to the key and report it to the requesting part. It is written in a DB text 6 and loaded in a Current Version Stack Area 15. SCP DB undate 17 reads the key with the identifier of the Area 15 by the instruction of the operator so as to recognize the service controller of the transfer destination, to generate an edition result file and to execute an editing processing.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an intelligent network service, and more particularly, to version number management of an intelligent network service database.

[0002]

2. Description of the Related Art With the development of advanced information society, ISDN
Due to the widespread use of data, there is a demand for diversification of data from voice to data and images. In addition, the demand for services to improve the usability of communication is also increasing. In order to respond to this diversification of services, it will be more and more necessary to provide highly convenient services that satisfy the demands of individual users.

In response to this request, an independent node consisting of a computer, a database, etc. is provided in the network in addition to the exchange, and by utilizing this, services such as toll free dialing are provided. Under the new network structure that has this intelligence in the network, the concept for providing various highly convenient services is collectively referred to as "Intelligent Network (IN)".
I'm calling

Intelligent Network (IN: In
The configuration of the telligent Network) service will be described with reference to FIG. FIG. 21 is a diagram showing a system configuration diagram in the IN service. In the figure, reference numeral 41 represents an exchange, and an SS that accesses the SCP 42 for a call that needs service processing in addition to basic exchange / call processing.
P (Service Switching Point),
42 is an SCP (Service Control Point) that specifies service processing in response to a request from the SSP 41 and performs processing such as number conversion and call release to the SSP 41, and 43 is a DB duplicate that centrally holds service data. (Data Base duplicate: database duplicate), 44 is IN
Management of the entire network, service support and SC
SMS (Service Management Syste) that centrally manages addition, modification, deletion, etc. of data in the database of P
m: service management device), 45 to 47 are TOs (Terminals)
Operator: terminal administrator, 47 is a DB original (Data Bas) that holds the original of the service data held by the SCP 42
e original: original database), respectively.

Here, the operation of the IN service will be described taking free dial as an example. The caller makes a call using a toll-free number. Upon receiving this call, the SSP 41 recognizes from the toll-free number that the call requires service processing, and sends this number to the SCP 42 (call is kept as it is). The SCP 42 collates the received toll-free number with the DB duplicate 43, recognizes that the call requires service processing, converts it to a normal telephone number, and then calls the SSP 41 to that telephone number. Command to connect. Here, the toll-free number is not a logical number but a physical number indicating an actual telephone number. This correspondence is held in the DB duplicate. The SSP 41 connects the call to the telephone number.

The operation of adding, changing, deleting, etc. of service data is as follows. TO45-4 as required
The administrator of 7 inputs a request for addition, change, deletion, etc. of service data. When the SMS 44 receives this request for addition, change, deletion, etc., it checks the validity of the data of this request, updates the data of the DB original 48 if it is valid, and issues a data update command to the SCP 42. SCP
At 42, the data update command is received, and the data of the DB duplicate 43 is updated.

With the increasing demand for IN services in recent years,
The service data is also becoming huge. Therefore, it is inevitable that security and reliability are improved. In response to this, IN service,
The version number of the database is managed. This is because the DB original 48 and the DB duplicate 43 store a number of generations by adding a version number to the data before the update processing as needed,
When the stored data is required, the version number is specified and the reading process is performed.

[0008]

The version number assignment in the conventional version number management is given to the service data after the update processing. Therefore, the service data to be transferred to the DB copy 43 is inefficient if there is only a small amount of updated data per generation, regardless of the amount of updated data, and it is inefficient for each generation.

Further, the SCP 42 and the DB replica 43 having a redundant configuration have the following problems. That is, for the IN service having the redundant configuration described above, the DB replica 43 of the active system and the DB replica 4 of the standby system are used.
No. 3 stores the same service, and the active system S
In case of failure due to CP42, the standby system S
The service is continued by switching to the CP 42, and after restoration, the service is continued by switching back to the active SCP 42.

If service data update processing occurs while the active system is disconnected, the active DB replica 43 is generated.
There is a difference in version number between the service data of 1) and the service data of the backup DB duplicate 43. In this case, SMS44
Recognizes that there is a difference in version number because the update process of the DB replica 43 of the active system could not be performed.
Waiting for the recovery of the CP 42, it is necessary to transfer the differential service data of the version number to the DB replica 43 of the active system in units of version numbers. In this case, the same problem occurs.

Further, if the service data update process occurs a plurality of times while the active SCP 42 is disconnected,
Service data of the DB replica 43 of the active system and D of the standby system
Differences will occur between the service data of the B duplicate 43 and the version numbers of several generations. In this case as well, the SMS44
The difference in version number is recognized because the update process of the active DB replica 43 could not be performed. After waiting for the recovery of the active SCP 42, the differential service data for several generations is transferred to the active DB replica 43. The above-mentioned problem becomes more serious because the data must be transferred in units of version numbers.

In the IN service having a plurality of SCPs 42, the DB master 6 stores service data for each of a plurality of DB replicas 43. SCP 42 and DB copy 43
If a redundant configuration is adopted, the same service data will be stored in the DB master 6, and the use of the DB master 6 will be inefficient. This problem becomes more serious as the demand for services increases and the service data increases accordingly.

Further, when the service data increases, the DB
As with the increase in the burden on the original 6, the DB duplicate 4
The burden of 3 is also a problem. That is, as the amount of service data increases, the amount of data stored in each DB replica 43 also increases and there is a possibility that the processing capacity may drop. An object of the present invention is to improve the efficiency of database version number management by assigning a version number to the data at the updated location when updating the service data.

Another object of the present invention is to improve the efficiency of processing by averaging the loads on a plurality of service control devices. Further, it is an object of the present invention to improve the efficiency of storage of the database original by compressing the service data and storing it in the database original.

[0015]

[Means for solving the problems] Exchange of calls from subscribers
For calls that require service processing in addition to call processing, the service switching apparatus requesting the service processing and the service processing in response to the request from the service switching apparatus are specified, and processing such as number conversion and services are performed. A service control device for releasing a call to the switching device, an original database for centrally holding service data, and management of the entire switching network at the same time as support for service provision and database duplication of the service control device. The service management device in the exchange network of the first invention, which has a service management device that centrally manages addition, change, deletion, etc. of data, provides a service data before and after updating when the service data of the original database is updated. Editing means to edit the updated part from the edit data to create edit data, and the version number for the edit data It has a version number assigning means for assigning, and transfer means for transferring the edited data attached version number to the database copy of the service control device.

In the service management device in the exchange network of the second invention, the service data version number assigning means of the first invention controls the service for the edited data edited before being transferred to the service control device. When transferring to the device, the same version number is collectively given. In the service management device in the exchange network of the third invention, the first
The editing means of the invention of claim 1 configures the edited service data of the update location from the pre-update data of the update location and the post-update data of the update location.

In the service management device in the exchange network of the fourth invention, the service control device of the first invention updates the service data of the database duplicate based on the edited data with the version number, and after the update, It has a database copy editing means for giving a version number based on the version number to the service data. In the service management device in the exchange network of the fifth invention, when the version number of the database duplicate is given before the version number of the database original, the version number between the database duplicate and the database original is provided. And a database original reading unit that reads the service data of the database original based on the version difference and transfers it to the database duplicate.

The service management device in the exchange network according to the sixth aspect of the present invention, when the edit data is distributed and transferred to the database duplicates of the plurality of service control devices, adds the service control device identifier indicating the transfer destination to the edit data. It has a service control device identifier giving means. A service management device in a switching network according to a seventh aspect of the present invention, a load detection means for detecting loads on a plurality of service control devices when transferring edited data in a distributed manner to a database copy of a plurality of service control devices, and load detection means. Selecting means for selecting the service control device of the transfer destination according to the detection result of the means.

[0019]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is a system configuration diagram in the first embodiment. In the figure, 1 is a DB duplicate A,
2 is SCPGroup A, 3 is DB duplicate B, 4 is SCPGroup
B, 5 are SMS, 6 is the original DB, and 7, 8 and 9 are TO, respectively. SCPGroupA, SCPGroupB, DB
The duplicate A and the duplicate DB B are in a redundant configuration. The current system, S
When a failure occurs in CPGroupA and disconnection occurs, if service data update processing occurs before restoration, a difference in version number occurs between the service data of DB duplicate A and the service data of DB duplicate B.

The operation of transferring the version difference of the service data to the DB copy A will be described with reference to FIG. FIG. 2 is an explanatory diagram of database version number management. In the figure, the same reference numerals as those in FIG. 1 indicate the same members, 11 is a DB original update & stack request unit for requesting editing of a database original and storage of an edited image, and 12 is a service control device for transferring service data. DB Allocate section that relocates
13 is a Stack reception unit for storing the edited image, and 14 is D
DB that reads and transfers the information in the original DB when a failure occurs in the B duplicate
Originals Loading section, 15 is the Current Version Stack Area section where the edited image is stored, 16 is the Version Manager section that gives the version number, 17 is the SCP DB Update section that edits the SCP database, and 18 is the version number Version 1.0, 19, 22 which is an example of the edited image that has been stored stores error information at the time of writing to the database. Error Report (1), (2) parts, 20 and 23 restore the data before updating the database. Roll Back (1), which performs processing
Parts (2) and 21, 24 respectively represent Retry (1) and (2) parts for repeating the writing operation to the database. 6 ~
The members up to 24 are components for managing the version number of the database existing in the SMS 5. Also, Roll B
The operation of the ack (1) unit will be described later with reference to FIG.

Stack information edited from the original DB editing
Figure 3 shows the operation up to storing the Current Version Stack Area 15.
~ It demonstrates using FIG. FIG. 3 is an operation explanatory diagram in the database original edition / stack information stacking operation, and FIG. 4 is a database original edition / stack information stacking operation sequence (1). In the figure, the same reference numerals as those in FIG. 2 indicate the same members.

Here, the Stack information indicates only the difference between the data before and after the update of the DB original 6 when the DB original 6 needs to be updated, that is, only the updated portion of the DB original 6 such as addition, change or deletion. . The original DB Update & Stack request unit 11 sends a message to the Stack reception unit 13 in preparation for stacking the Stack information.
Issue a Stack reservation. If the booking is successful, Stac
The k reception unit 13 notifies the original DB Update & Stack request unit 11 of the reservation number of Stack. If the reservation fails, an Error notification is sent to the DB original data Update & Stack request unit 11. Original DB Update & Stack Request Part 1
In 1, when the Error notification is received, the editing process ends. Upon receiving the reservation number of Stack, the DB original data Update & Stack request unit 11 updates the DB original data 11. When the update of the DB original 6 is successful, the DB original copy Update & Stack requesting unit 11 notifies the Stack receiving unit 11 of the Stack information. When the Stack reception unit 13 receives the notification of Stack information,
Stack information is stacked in the Current Version Stack Area section 15. When the update of the DB original 6 fails, as shown in FIG. 5, the DB original Update & Stack request unit 11 notifies the Stack reception unit 13 of the Stack reservation number Cancel.

The original DB update & stack request unit 11 is St
Figure 6 shows an image of Stack information delivered to the ack reception unit 13.
This will be described using. FIG. 6 is a diagram showing an image of editing a database delivered to the Stack reception desk. Where NPS
Is the service name, PN is the Ported Number: subscriber number, N
N is Network Number: Network number, Operator Cod
e is the operation number, and SvcStatus is the Service Status: service status (indicating whether or not the service is in operation).

The first row shows data modification. Ol
The NN number, Operator Code and SvcStatus, which are the data before and after the change, are shown in d Value and New Value, respectively. The second row shows the addition of data.
Therefore, there is no Old Value data, and only the New Value shows the NN number, Operator Code, and SvcStatus.

The third row shows data deletion. Therefore, there is no New Value data, and only the Old Value shows the NN number, Operator Code, and SvcStatus. In the Current Version Stack Area section 15, the stack information to which the version number has already been added and the (Current Version) stack information that is being accumulated before the version number is added are stacked.

The current Stack information, which is the current version, continues to be stacked until the Update Process is started by the SCP DB Update section 17, and at the time of the start, the version number is added to the stacked stack information until then. It is something. This version number assignment / transfer operation is repeatedly performed by an operator's instruction. This transfer operation will be described with reference to FIG. Figure 7
FIG. 8 is a sequence diagram of a Stack information transfer operation to the SCP. In the figure, the same reference numerals as those in FIG. 2 denote the same members.

Stack of Current Version Stack Area 15
After the stacking starts, when the operator gives instructions, SCP
Since the DB Update unit 17 starts the editing process (S1),
The Update Process is started (S2). If it cannot be started normally, it will be Update NG (S
3). Here, Update Process is Current Version
It shows a series of operations for transferring from Stack Area to SCP of Stack information.

When the Update Process is started normally, when the stack information to be edited is transferred to the SCP, the Ve
The version number is added by rsion Manager 16 (see Fig. 2).
1.0 "18) (S4). The stack information with this version number is also stored in the Current Version Stack Area 15.

Since the update process is passed the edition number to be edited, it is possible to recognize which information is to be read by the edition number, and the current version stack area can be recognized.
It is read from section 15. After that, the Stack information with the version number is transferred to the DB copy (A, B) (S
6) and the editing process ends (S7).

The SCP DB Update section 17 can recognize the recognition of the transfer result by the Report of the Error Report section. 8 shows the SCP DB Updat from the Error Report section 19.
It is a figure which shows the Report image notified to the e section 17.
This image shows that the service is an NPS service, the version number is Version 1.4, and the SCPs to be transferred are scp0 and scp1 indicating that the editing operation has been completed.

Further, FIG. 9 shows that the Error Report unit 19
It is a figure which shows the Error Report image notified to SCP DB Update part 17. In this image, the service is NP
S service, version 1.4, SCP to be transferred
It indicates that the editing work with scp0 and scp1 failed. As a further reason, there is already data for 8887777 (despite the additional data), and 912301
For 29, no data is shown (despite deleted data).

A screen for specifying Stack information to be transferred to the SCP in the Stack DB Update unit 17 will be described with reference to FIGS. 10 to 13. FIG. 10 shows the Stack information transfer designation screen (1). The upper part is a screen for selecting stack information to be transferred in the Current Version Stack Area 15, and the lower part is a screen for specifying a transfer destination.

All Current Versions is specified in Selection. This is the Current Version for each service.
Exists, and all of them are targets for transfer to the SCP. Also, for NPS services, Versio
The version numbers of n1.2 and Version 1.3 have been added to December 20, 1995 and December 30, 1995, respectively. Current Version to Version 1.4
The fact that "is attached" indicates that this version will be attached unless otherwise specified.

Actions include Trigger (explained in FIG. 13), Update Result List (explained in FIG. 12), Initialize Version for specifying the version number, Dump for storing the current screen information on the disk, and copy of the screen. Do Print All
, Hardcopy and Exit to exit the screen can be selected. Here, the screen when Update Result List is selected on the screen of FIG. 10 will be described with reference to FIG.

FIG. 11 shows the Stack information transfer designation screen (2). On this screen, a list indicating which action exists in the service information to which the version number is added is displayed.
Actions on this screen include Detail to display detailed information, Previous to display the previous screen, Next to display the next screen, Delete to delete selection information, Print to perform a hard copy of the screen, Selection information Cancel that corrects can be specified.

On this screen, specify PN = 12345678 and select De
The screen when tail is selected will be described with reference to FIG. FIG. 12 shows the Stack information transfer designation screen (3). On this screen, it is a diagram showing a detailed information image per editing work. The editing work of PN = 12345678, which I specified earlier,
This is a change, and the image before change is NN = 55512345, Op
eratorCode = 555, SvcStatus = OFF, and the changed image is NN = 66666666, OperatorCode = 123, SvcStatu
Indicates that s = ON.

In addition, in the Stack information transfer screen (1) of FIG.
The screen when Trigger is selected will be described with reference to FIG. FIG. 13 shows the Stack information transfer screen (4). On this screen, transfer control of the stack information that is actually edited to the service control unit is performed using this screen. In this screen, Stac
When transferring k information, the version number is 1.4 and the S
SCP0 and SCP1 are designated as CPs. In addition, there is also a function to specify the transfer time.
Select e to specify the time.

As described above, St shown in FIGS.
The ack information transfer designation screens (2) and (3) are used to confirm the edited contents of the Stack information to be transferred.
The Stack information transfer designation screen (4) shown in 3 is used to actually transfer the editing information. Here, the restoration processing of the DB duplicate when an error occurs during the transfer of the edited Stack information to the DB duplicate via the SCP will be described with reference to FIG.

FIG. 14 shows a Roll Back operation sequence. In the figure, the same reference numerals as those in FIG. 2 denote the same members. Current Version Stack Area15
An error occurs when the version number 1.4 is added to the Current information of and the data is transferred to the DB duplicates A and B via SCP (S1
The case of 1) is assumed. Error Report (1) part 19 is Er
The ror is detected (S12), and the SCP DB Update 17 is notified as an Error Report, and at the same time, an inquiry for Roll Back activation (S13) is performed.

In SCP DB Update 17, this Error Repo
In response to the rt and Roll Back activation inquiries, confirm whether or not it is necessary to activate Roll Back from the Roll Back activation flag in its own environment file. As a result of confirmation, if it is necessary to activate Roll Back, SCP DB Update 17 will issue a activation request.
A roll back activation request is issued to the ll back (1) unit 20 (S14).

When the Roll Back (1) unit 20 receives the Roll Back activation request, it starts the Roll Back operation (S1).
5). First, the Old Value in the generation at the time of Error (Version 1.4 in this case) is sequentially acquired for the Current Version Stack Area 15 (S16), and the DB duplicates A and B are acquired.
Restore process. In this case, if the generation at the time of Error is only additional information, there is no Old Value and restoration processing is not performed.

Up to this point, the Current Version Stack Area
Although the transfer of the Stack information accumulated in 15 to the DB duplicate has been described, the database recovery processing when a failure occurs in the DB duplicate will be described below. DB
The SCP supervisor unit (not shown) monitors the status of the duplicate. This SCP supervisor section manages the status of the SCP (Active status, HotStanby status, C status).
The old Stanby state) and the amount of data in the SCP database copy are regularly monitored and the result is retained.

The DB is triggered by the activation by the operator.
The original copy loading section 14 inquires of the SCP supervisor section about the status of the DB copy, and displays the result on the screen. This screen image will be described with reference to FIG. Figure 15: Database loading screen image
(1). Here, SCP is for each group (OC-SCP Gro
up, NT-SCP Group) has a redundant configuration (OC-SCP
OCSCP1 and OCSCP2 for Group, NTSCP1 and NTSCP2 for NT-SCP Group), active system is in active state, standby system is
It is intended for those in the Hot Stanby state and in the Cold Stanby state when a failure occurs in the DB duplicate or SCP.

This screen shows the situation described below. First, the data model version in SMS is Version 1.2
It is. Of the members of OC-SCP Group, OCSCP1 is Co
The data model version is Version 1.0 in the ld Stanby state, and the data model version is Version in the OCSCP2 Active state.
It is 1.1. Similarly, among those belonging to the NT-SCP Group, NTSCP1 is in the Active state and the data model version is Version.
1.1, the data model version is Version 1.1 with NTSCP2 in Hot Stanby state.

Here, the database model refers to the "type" of the database itself, specifically, the structure of the data stored in the database, and the data model can be changed by increasing the management parameters of the database as the number of fields increases. It is necessary to change the form, and the version number is added to this. Therefore, adding, changing, or deleting Stack information does not change the "type" of the database itself, so it does not update the database model version (it only updates the pure database version). ). Further, in the drawings, the case of the database model version has been described as an example, but also in the case of the version of a pure database, the state of each service control device and its version can be similarly confirmed.

Further, as an action, Detail indicating detailed information and Checkpoi for erasing the disk information in the SCP
nt Clear, Ch to write the disk information in SCP
eckpoint Create, Print All that duplicates the screen, Hard
You can select copy or Exit to exit the screen. The operator can view the OC-SCP Group by the Cold Stanby display on this screen.
Recognize that a failure has occurred in OCSCP1 belonging to. We also recognize that the version number of OCSCP1 is Version 1.0 and the other versions are Version 1.1, so the version number for one generation was updated during the failure.

Now, a method of transferring the loading information after recognizing the difference in version number will be described with reference to FIG.
FIG. 16 is a diagram showing a database loading screen image (2). This drawing is OCSC of OC-SCP Group in the database loading screen image (1) shown in FIG.
This is the screen when P1 is specified and Detail is selected as the action.

At the top of this screen, the SCP of the selected information
Group is OCSCP, SCP Host is OSCP1, SCP Data Model Ve
rsion is Version 1.0, SMS Data Model Version is Version
Indicates 1.2. Furthermore, in the central part, the version number of the SCP type is 1.0, whereas the version number of the SCP database, that is, the version number of the pure DB duplicate is Version 1.3. That is, it is shown that the version number of the pure DB original is Version 1.5. That is,
There is a difference of two generations between the version number of the DB duplicate and the version number of the DB original.

As actions, for the database whose version number information is empty, Load for reading the service data of that version number, Initialize for temporarily emptying the specified version number information, and copy screen information You can select Print or Cancel to cancel the action being executed. Here, the operator recognizes that the version number of the SCP database has not been updated for two generations, and the following operation is performed in order to write the service data corresponding to this difference in the SCP database.

That is, first, Version 1.3 which is the version number of the SCP database is specified, Initialize is selected, and the version number information is temporarily emptied. Furthermore, in this state, if you select Load and the version number is Initialize, the DB original
Loading part 14 is DB1.4, Version1.4, Vers
Request read of ion1.5. The DB original that has received the request reads the service data related to Version 1.4 and Version 1.5 and sends it to the DB original Loading section 14. D
Upon receiving this service data, the B original copy loading unit 14 transfers this information to the DB copy of OCSCP1.

As a result, the version number of the DB copy of OCSCP1 is
It will be the same as the version number of the DB duplicate of OCSCP2 in the redundant configuration.
In the first embodiment, when updating service data,
Although the efficiency of database version number management has been explained by assigning the version number to the updated data, in the second embodiment below, the load on the service control device is averaged and efficient operation is realized. It is a thing.

FIG. 17 is a diagram showing a second embodiment. In the figure, the same reference numerals as those in FIG. 1 denote the same members, 1-1 is a DB replica A, 1-2 is a DB replica A, 2-1 is SCP GroupA, 2-2 is SCPG.
roupA, 3-1 is DB duplicate B, 3-2 is DB duplicate B
4-1 is SCP Group B, 4-2 is SCP Group
Indicates B.

Here, DB duplicate A1-1 and DB duplicate A
1-2, SCP GroupA 2-1 and SCP GroupA
2-2, DB duplicate B3-1 and DB duplicate B3-2, S
Both CP GroupB 4-1 and SCP GroupB 4-2 have a redundant configuration. The DB original 6 stores service data for each DB duplicate. In the present embodiment, in order to average the loads on the service control devices and operate them efficiently, the original DB is constructed as described below and the service data is rearranged.

A structural image of the DB master copy 6 of this embodiment will be described with reference to FIGS. FIG. 18 is a diagram showing an image of the original database structure. The structure of service data, which is a logical number typified by a toll-free number and is an identifier for identifying subscriber data, and service data composed of data attached to the record index is the same as that of the conventional database original. In the present embodiment, the service control device identifier is further added to each data. The service control identifier will be described in detail with reference to FIG.

FIG. 19 shows the structure of the service control identifier. Here, 32 columns of 0 to 31 are prepared, and the transfer destination of the service data to which the service control identifier is added is set in the target column in 1-bit units.
N / OFF can be set. here,
The column will be described with reference to FIG. FIG. 20 is a service control device correspondence table. This table shows which service control device the 32 columns prepared by the service control identifier correspond to.

According to the figure, the service controller A is located at column position 0 and the service controller A is located at column position 1.
However, at the column position 2, the service control device B is ...
The service control device m corresponds to the column position 31. 18 to 20 are summarized, the record index Key0433 shown in FIG.
AAAAA, DATA2 is BBBBB, DATA3 is CCCCC, ...
The data whose DATA4 is NNNNN is the service data regarding the service control device corresponding to the column positions 0 and 1 shown in FIG. 19, and the service control device corresponding to this column position 0 and 1 is as shown in FIG. , Service control device A and service control device A, respectively.

The operation of relocating service data will be described with reference to FIG. 2 by using the configuration image of the DB original 6. First, when the record index Key and the data accompanying it are received by the operator's input, the DB original data Update & Stack request unit 11 makes the DB Allocate
The record index is notified to the unit 12 and the service control device identifier acquisition request is made.

The DB Allocate unit 12 selects a transfer destination of the record index Key from a plurality of service control devices by random number processing. A service control device identifier is created based on the selection result, and the record index Ke is created.
It is given to y and notified to the original DB update & stack request unit 11. Here, the present embodiment is not limited to random number processing, and the service control device identifier may be configured so that there is no bias in the amount of data handled among a plurality of service control devices. For example, the data amount of each service control device owned by the SCP supervisor is ordered, and the record index. Arranging the Key is also effective.

The original DB Update & which received the notification of the record index Key to which the service control device identifier is added
The Stack requesting unit 11 writes this in the DB original 6 and Cu
Stack in rrent Version Stack Area 15. SCP DB Update
17 is Current Version Stac according to the instruction of the operator.
The record index Key provided with the service control device identifier loaded in the k Area 15 is read out. The service control device of the transfer destination is recognized from the service control device identifier, an edit result notification file is created, and the edit process is executed.

When there are a plurality of service control devices as transfer destinations based on the service control device identifier, an edit result notification file is created for each service control device, and the edit processing is executed for each service control device. Furthermore, when performing the latest DB loading due to a failure of the service control unit, the DB original
The loading unit 14 reads all the service data of the required version of the service control device from the original DB 6 and confirms the service data for the faulty service control device from among the service control device identifiers. To extract and transfer.

[0061]

In the first embodiment, when the service data is updated, the service data to be transferred to the service control device is compressed by assigning the version number to the data at the updated location, and the transfer is performed. The database version number management can be made more efficient by shortening the time.

Further, in the second embodiment, the processing speed of the plurality of service control devices can be increased in the entire network by averaging the loads on the plurality of service control devices. Furthermore, in the present embodiment, by compressing service data and storing it in the database original, the database original can be used efficiently.

[Brief description of drawings]

FIG. 1 is a system diagram in a first embodiment.

FIG. 2 is an explanatory diagram of database version management.

FIG. 3 is an operation explanatory diagram in database original editing / stack information stacking.

FIG. 4 is a diagram showing a database original editing / stack information stacking operation sequence (1).

FIG. 5 is a diagram showing a database original editing / stack information stacking operation sequence (2).

FIG. 6 is a diagram showing a database editing image delivered to a stack reception.

FIG. 7 is a diagram showing a stack information transfer operation sequence to the SCP.

FIG. 8 is a stack information transfer result Report to the SCP.
It is a figure which shows an image.

FIG. 9: Stack information transfer result Error to SCP
It is a figure which shows a Report image.

FIG. 10 is a diagram showing a Stack information transfer designation screen (1).

FIG. 11 is a diagram showing a Stack information transfer designation screen (2).

FIG. 12 is a diagram showing a Stack information transfer designation screen (3).

FIG. 13 is a diagram showing a Stack information transfer designation screen (4).

FIG. 14 is a diagram showing a Roll Back operation sequence.

[Figure 15] Image of original database loading screen
It is a figure showing (1).

FIG. 16: Image of loading the original database
It is a figure showing (2).

FIG. 17 is a system configuration diagram in the second embodiment.

FIG. 18 is a diagram showing an image of the original database configuration.

FIG. 19 is a service control device identifier configuration diagram.

FIG. 20 is a diagram showing a service control device correspondence table.

FIG. 21 is a system configuration diagram in the intelligent network service.

[Explanation of symbols]

 1 DB Duplicate A 2 SCP GroupA 3 DB Duplicate B 4 SCP GroupB 5 SMS 6 DB Original 7-9 TO 11 DB Original Update & Stack Request 12 DB Allocate 13 DB Accepting 14 DB Original Loading 15 Current Version Stack Area 16 Version Manager Part 17 SCP DB Update Part 18 Version 1.0 (Image) 19 Error Report (1) Part 20 Roll Back (1) Part 21 Retry (1) Part 22 Error Report (2) Part 23 Roll Back (2) Part 24 Retry (2) department

 ─────────────────────────────────────────────────── ─── Continuation of front page (72) Inventor Yoshitaka Kato 3-9-18 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa Fujitsu Communication Systems Limited (72) Inventor Shoichi Kimura 3 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa 9-9-18 Fujitsu Communication Systems Limited (72) Inventor Miki Matsuyama 3-9-18 Shin-Yokohama, Kohoku Ward, Yokohama City, Kanagawa Prefecture Fujitsu Communication Systems Limited

Claims (8)

[Claims] 1. In addition to call exchange / call processing from subscribers,
For calls that require service processing, the service switching apparatus that requests the service processing and the service processing in response to the request from the service switching apparatus are specified, and processing such as number conversion and call to the service switching apparatus are specified. A service control device that performs release, an original database that centrally holds service data, and management of the entire self-switching network network. At the same time, support for service provision and addition or modification of data in the database copy of the service control device. In a service management device in a switching network having a service management device that centrally manages deletion, deletion, etc., when the service data of the original database is updated, the updated part is edited from the service data before and after the update Editing means for creating a version number and adding a version number to the editing data The number providing unit, the service management system in an exchange network, characterized in that it comprises a transfer means for transferring the edited data attached to the version number to the database copy of the service control device. 2. The service data version number assigning means collectively assigns the same version number to the edited data edited before being transferred to the service control device when the edited data is transferred to the service control device. The service management apparatus according to claim 1, wherein the service management apparatus is a switching network. 3. The exchange according to claim 1, wherein the editing means configures the edited service data of the update location with pre-update data of the update location and post-update data of the update location. Service management device in the network. 4. The service data transfer means transfers the pre-updated data of the update location of the edited service data of the update location to the database duplicate of the service control device. 2. A service management device in the exchange network according to 2. 5. The service control device updates the service data of the database copy based on the edition data provided with the version number, and the version number based on the version number for the updated service data. The service control device in the exchange network according to claim 1, further comprising: a database copy editing means for adding the. 6. A difference for extracting a difference in version number between the database duplicate and the database original when the version number of the database duplicate is given before the version of the database original. 2. The exchange network according to claim 1, further comprising: an extracting unit; and a database original reading unit that reads service data of the database original based on the difference in the version numbers and transfers the service data to the database duplicate. Service management equipment. 7. A service control device identifier assigning means for assigning a service control device identifier indicating a transfer destination to the edit data when the edit data is distributed and transferred to a database copy of a plurality of service control devices. A service management device in a switching network according to claim 1, wherein: 8. A load detection unit that detects loads on the plurality of service control devices when the edited data is distributed and transferred to database duplicates of a plurality of service control devices, and a detection result of the load detection unit is used. The service management apparatus in the exchange network according to claim 1, further comprising: a selecting unit that selects a service control apparatus of a transfer destination.