JP2013021529A - Subscriber data management method and call control system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten a response time to a user terminal, while preventing load concentration in a subscriber data management device.SOLUTION: Subscriber data held in a subscriber data management device 500 as an original is held in a call control server 300 as cache data of a duplicate to the original.

Description

  The present invention relates to a subscriber data management technique in a call control system.

  In a conventional telephone network, subscriber information (hereinafter referred to as subscriber data) necessary for providing a service to a subscriber is held by a subscriber exchange that accommodates the subscriber's telephone terminal.

  For this reason, since it is necessary to hold the update history and backup data of the subscriber data in the subscriber exchange, there is a problem that the recovery process when a failure occurs in the subscriber exchange becomes complicated.

  The specific restoration process differs depending on the cause of failure. The cause of failure is the case of hardware failure in FIG. 15A, the occurrence of severe disaster in FIG. 15B, and the time of network failure in FIG. Can be mentioned.

  For example, when a hardware failure occurs, replacement work is performed by a maintenance person. In order to prepare for service interruption due to a hardware failure, it is necessary to perform hardware replacement work on site by a maintenance person even at night. In the event of a catastrophic disaster, services will be provided instead of spare subscriber exchanges. When a network failure occurs, it is necessary to wait for the network to recover, or to recover using a procedure similar to that used when suffering a catastrophic disaster.

  On the other hand, according to a call control system defined by 3GPP (3rd Generation Partnership Project), subscriber data is centrally managed by a subscriber data management database (hereinafter referred to as subscriber data management device) called HSS (Home Subscriber Server). (See Non-Patent Document 1).

  Since subscriber data is held by a device different from a server device (hereinafter referred to as a call control server) that realizes the function of a conventional subscriber exchange, it is sufficient to perform recovery processing for each device in which a failure has occurred. The above-mentioned problems in the telephone network are solved to some extent.

3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signaling flows and message contents (Release 9)", 3GPP TS 29.228, V9.3.0, September 2010

  However, when call connection requests are simultaneously generated from a plurality of user terminals, subscriber data inquiries from the call control server that has received the requests to the subscriber data management apparatus are concentrated, and thereby the subscriber data management apparatus Since the load is high, there is a problem that the capital investment cost for the countermeasure increases, and the response time to the user terminal becomes long, so that the service is deteriorated.

  The present invention has been made in view of the above problems, and even when call connection requests are generated all at once, the load concentration of the subscriber data management device is prevented and the response time to the user terminal is reduced. The first problem is shortening, and the second problem is to simplify the recovery process when a failure occurs in the call control server.

  The subscriber data management method according to claim 1 is a call control server for controlling a call transmitted from a user terminal of a subscriber via a transfer system device, and a subscriber data management for managing subscriber data related to the subscriber. In the subscriber data management method performed by the apparatus, the subscriber data management apparatus comprises first subscriber data input to the maintenance operation apparatus and second subscriber data notified from the user terminal. Receiving subscriber data; and storing the received subscriber data in a storage means as an original; receiving the subscriber data by the call control server; and receiving the subscription Storing data in the storage means as duplicate cache data for the original.

  According to the present invention, since the subscriber data held as the original in the subscriber data management apparatus is held as a duplicate cache data for the original by the call control server, the call data is sent to the subscriber data management apparatus when a call connection request is made. This eliminates the need for inquiries, so even when call connection requests are generated all at once, it is possible to prevent the load concentration on the subscriber data management device and to shorten the response time to the user terminal. it can.

  The subscriber data management method according to claim 2 is the subscriber data management method according to claim 1, wherein the call control server accommodates when the duplicate cache data is lost by the call control server. The method further comprises the step of acquiring subscriber data related to the transfer system device from the subscriber data management device.

  According to the present invention, when the cache data of the copy is lost by the call control server, the subscriber data related to the transfer system device accommodated in the call control server is acquired from the subscriber data management device. Can be recovered by using the subscriber data as described above, so that the recovery process in the event of a failure of the call control server can be simplified.

  The subscriber data management method according to claim 3 is the subscriber data management method according to claim 1 or 2, wherein the subscriber data management device causes the call control server accommodating the transfer system device to receive another call. When migrating to a control server, change the identifier of the call control server defined in the correspondence table indicating the correspondence between the accommodated transfer device and the accommodated call control server to the identifier of the call control server of the migration destination, The method further comprises the step of transmitting subscriber data related to the transfer system device to the transfer destination call control server and deleting the subscriber data of the transfer source call control server.

  According to the present invention, when the call control server that accommodates the transfer system device is transferred to another call control server by the subscriber data management device, the accommodated transfer system device and the accommodated call control server The identifier of the call control server defined in the correspondence table indicating the correspondence relationship is changed to the identifier of the transfer destination call control server, the subscriber data related to the transfer system device is transmitted to the transfer destination call control server, and the transfer source Since the subscriber data of the call control server is deleted, the recovery process in the event of a failure of the call control server can be simplified.

  5. The subscriber data management method according to claim 4, wherein the original contains the subscriber data and a user terminal that has notified the subscriber data. Is transferred to the subscriber data management device when the transfer device accommodating the user terminal is transferred to another transfer device by the subscriber data management device. Change the identifier of the transfer system device to the identifier of the transfer destination transfer device, send the changed subscriber data to the call control server that accommodates the transfer destination transfer device, and change the transfer source device of the transfer source The method further comprises the step of deleting subscriber data of the accommodated call control server.

  According to the present invention, when the transfer system device accommodating the user terminal is transferred to another transfer system device by the subscriber data management device, the identifier of the transfer system device in the subscriber data is transferred to the transfer system of the transfer destination. Change to the identifier of the device, send the changed subscriber data to the call control server that accommodates the transfer-destination transfer-system device, and subscriber data of the call control server that accommodates the transfer-source transfer-device Therefore, it is possible to simplify the recovery process when a failure occurs in the call control server.

  The subscriber data management method according to claim 5 is the subscriber data management method according to any one of claims 2 to 4, wherein when the subscriber data is set in the storage means in the call control server, call control is performed. The subscriber data related to the user terminal that generated the request is prioritized.

  According to the present invention, when subscriber data is set in the storage means in the call control server, the subscriber intends to use communication in order to prioritize the subscriber data related to the user terminal that generated the call control request. Can reduce the time during which communication is not available.

  The call control system according to claim 6 is a call control server that controls a call transmitted from a user terminal of a subscriber via a transfer system device, and a subscriber data management device that manages subscriber data related to the subscriber. In the call control system, the subscriber data management device includes subscriber data composed of first subscriber data input to the maintenance operation device and second subscriber data notified from the user terminal. Is stored when the received subscriber data is stored in the storage unit as an original, and the call control server storing the transfer system device is transferred to another call control server. Change the identifier of the call control server defined in the correspondence table indicating the correspondence between the transfer device and the accommodated call control server to the identifier of the transfer destination call control server, Means for transmitting subscriber data related to the transfer system device and deleting subscriber data of the call control server of the migration source; and the original contains the subscriber data and a user terminal that has notified the subscriber data. Subscriber data associated with a certain transfer system device, and when the transfer system device accommodating the user terminal moves to another transfer system device, the identifier of the transfer system device in the subscriber data Is changed to the identifier of the transfer destination device of the transfer destination, the changed subscriber data is transmitted to the call control server that accommodates the transfer destination device of the transfer destination, and the transfer source device of the transfer source is accommodated Means for deleting subscriber data of the call control server, the call control server storing means for receiving the subscriber data and storing the received subscriber data as duplicate cache data for the original. And means for acquiring subscriber data related to a transfer system device accommodated in the call control server from the subscriber data management device when the cache data of the duplicate is lost. It is characterized by that.

  According to the present invention, since the subscriber data held as the original in the subscriber data management apparatus is held as a duplicate cache data for the original by the call control server, the call data is sent to the subscriber data management apparatus when a call connection request is made. This eliminates the need for inquiries, so even when call connection requests are generated all at once, it is possible to prevent the load concentration on the subscriber data management device and to shorten the response time to the user terminal. it can.

  According to the present invention, when the cache data of the copy is lost by the call control server, the subscriber data related to the transfer system device accommodated in the call control server is acquired from the subscriber data management device. Can be recovered by using the subscriber data as described above, so that the recovery process in the event of a failure of the call control server can be simplified.

  According to the present invention, when the call control server that accommodates the transfer system device is transferred to another call control server by the subscriber data management device, the accommodated transfer system device and the accommodated call control server The identifier of the call control server defined in the correspondence table indicating the correspondence relationship is changed to the identifier of the transfer destination call control server, the subscriber data related to the transfer system device is transmitted to the transfer destination call control server, and the transfer source Since the subscriber data of the call control server is deleted, the recovery process in the event of a failure of the call control server can be simplified.

  According to the present invention, when the transfer system device accommodating the user terminal is transferred to another transfer system device by the subscriber data management device, the identifier of the transfer system device in the subscriber data is transferred to the transfer system of the transfer destination. Change to the identifier of the device, send the changed subscriber data to the call control server that accommodates the transfer-destination transfer-system device, and subscriber data of the call control server that accommodates the transfer-source transfer-device Therefore, it is possible to simplify the recovery process when a failure occurs in the call control server.

  According to the present invention, even when call connection requests are generated all at once, it is possible to prevent the load concentration of the subscriber data management device and to shorten the response time to the user terminal. In addition, it is possible to simplify the recovery process when a failure occurs in the call control server.

It is a figure which shows the whole structure of a call control system. It is a figure which shows the example of the corresponding | compatible table and subscriber data (original) which defined the corresponding | compatible relationship between the accommodated transfer system apparatus and the accommodated call control server. It is a figure which shows the example of subscriber data (replication). 6 is a diagram illustrating an operation sequence of an operation example 1. FIG. It is a figure which shows the operation | movement sequence of the operation example 2. FIG. It is a figure which shows the operation | movement sequence of the operation example 3. FIG. It is a figure which shows the whole structure of the call control system in the operation example 4. It is a figure which shows the example of the corresponding | compatible table and subscriber data (original) in the operation example 4. FIG. It is a figure which shows the operation | movement sequence of the operation example 4. FIG. It is a figure which shows the whole structure of the call control system in the example 5 of operation. It is a figure which shows the example of the corresponding | compatible table and subscriber data (original) in the operation example 5. FIG. 10 is a diagram illustrating an operation sequence of an operation example 5. FIG. It is a figure explaining the concept of the priority process in the operation example 6. FIG. It is a figure which shows the operation | movement sequence of the operation example 6. FIG. It is a figure which shows the example of a failure generating factor.

  Hereinafter, an embodiment for carrying out the present invention will be described with reference to the drawings. However, the present invention can be implemented in many different modes and should not be construed as being limited to the description of the present embodiment.

  First, the configuration of the call control system according to the present embodiment will be described. FIG. 1 is a diagram showing the overall configuration of a call control system.

  The call control system 1 includes a transfer system device 100 that accommodates a subscriber's user terminal 900, a call control server 300 that controls a call transmitted from the user terminal 900 via the transfer system device 100, and a subscriber-related subscription. Subscriber data management device 500 that manages subscriber data, and a maintenance operation device 700 that is used when the call control server 300 and the subscriber data management device 500 are maintained and operated.

  The subscriber data management device 500 is connected to the maintenance operation device 700 and the call control server 300 so that they can communicate with each other. Further, the transfer system device 100 is connected to the call control server 300 so as to be capable of mutual communication, and can be realized by an edge router or the like that can accommodate a plurality of user terminals 900.

  The subscriber data management device 500 includes a subscriber data original storage unit 51, a subscriber data backup storage unit 52, a subscriber data transmission / reception unit 53, a maintenance operation device interface 54, and a call control server interface 55. ing. Hereinafter, the function of each part will be described in detail.

  As shown in FIG. 2 (a), the subscriber data original storage unit 51 includes a call control server 300 (accommodated call control server in FIG. 2 (a)) accommodated in the subscriber data management device 500, and its call. The control server 300 has a function of storing a correspondence table indicating a correspondence relationship with the transfer system device (accommodated transfer system device 100 in FIG. 5A).

  In addition, as shown in FIG. 5B, a subscriber identifier for identifying a subscriber and a transfer system device that accommodates a user terminal 900 having the subscriber identifier (accommodated transfer system device in FIG. ) 100 and the subscriber data (for example, contract data, custom data, linkage data, etc.) associated with the subscriber are stored in the original subscriber data.

  The contract data is data input from the maintenance person through the maintenance operation device 700 when the user terminal 900 is newly installed or contract contents are changed. The custom data is data input by a user operation. The cooperation data is data notified from the user terminal 900, such as a MAC address and register information. The contract data, custom data, and linkage data are all information for each user terminal associated with the subscriber identifier.

  The subscriber data backup storage unit 52 has a function of storing a backup of the original subscriber data stored in the subscriber data original storage unit 51 and an update history.

  The subscriber data transmission / reception unit 53 receives the subscriber data received from the maintenance operation device 700 via the maintenance operation device interface 54 or from the call control server 300 via the call control server interface 55, and the subscriber data original storage unit 51. And the function of transmitting the subscriber data acquired from the subscriber data original storage unit 51 to the call control server 300 via the call control server interface 55.

  The call control server 300 includes a subscriber data cache management unit 31, a subscriber data cache transmission / reception unit 32, a subscriber data management device interface 33, and a transfer system device interface 34. Hereinafter, the function of each part will be described in detail.

  As shown in FIG. 3, the subscriber data cache management unit 31 has a function of storing a copy of the original subscriber data received from the subscriber data management apparatus 500 as cache data.

  The subscriber data cache transmission / reception unit 32 stores the subscriber data received from the subscriber data management device 500 via the subscriber data management device interface 33 in the subscriber data cache management unit 31, and the transfer system device 100. The subscriber data received via the transfer system device interface 34 is transmitted to the subscriber data management device 500 via the subscriber data management device interface 33.

  The subscriber data management device 500 and the call control server 300 are realized by storage means such as a memory and control means such as a CPU. In particular, the subscriber data cache management unit 31 is preferably a storage unit capable of writing / reading data at a higher speed than the subscriber data original storage unit 51 and the subscriber data backup storage unit 52.

  Next, a subscriber data management method performed in the call control system having such a configuration will be described.

[Operation example 1]
In the operation example 1, an operation of registering subscriber data related to contract data and custom data input to the maintenance operation device 700 will be described. FIG. 4 is a diagram illustrating an operation sequence of the first operation example.

  First, the subscriber data input by the maintenance person is notified to the subscriber data management apparatus 500 by the maintenance operation apparatus 700 (step S11).

  Next, the subscriber data management apparatus 500 accumulates the subscriber data notified in step S11 as an original in a predetermined position of the subscriber data original storage unit 51 (step S12).

  Next, the subscriber data notified from the maintenance and operation apparatus 700 by the subscriber data management apparatus 500 immediately causes the call control server 300 that accommodates the transfer system apparatus 100 that accommodates the user terminal 900 related to the subscriber data. Is notified together with information for identifying the accommodation transfer system device (step S13).

  Note that the subscriber data to be notified may be difference data for only the change notified from the maintenance operation device 700 or all subscriber data. In addition, the notification of subscriber data to the call control server 300 may be performed at regular intervals.

  Finally, the subscriber data notified from the subscriber data management device 500 by the call control server 300 is copied to a predetermined location of the subscriber data cache management unit 31 together with information for identifying the accommodation transfer system device. (Step S14).

  As described above, according to the operation example 1, the subscriber data management apparatus 500 accumulates the subscriber data related to the contract data and the custom data as an original, and the call control server 300 caches the subscriber data for the original. Since it is stored as data, there is no need to make an inquiry to the subscriber data management device 500 at the time of a call connection request. Therefore, even when call connection requests are generated all at once, the load on the subscriber data management device 500 Concentration can be prevented, and the response time to the user terminal 900 can be shortened.

[Operation example 2]
In the second operation example, an operation for registering subscriber data related to cooperation data generated when the call control server 300 receives a user signal transmitted from the user terminal 900 due to establishment of a new user terminal or the like will be described. . FIG. 5 is a diagram illustrating an operation sequence of the operation example 2.

  First, data related to the user terminal 900 (for example, the MAC address of the terminal or the blocked state) by the user terminal 900 is called by the user signal through the transfer system 100 via the transfer system 100. The control server 300 is notified (step S21).

  Next, based on the user signal notified from the user terminal 900, the call control server 300 generates linkage data included in the subscriber data related to the user terminal 900 (step S22).

  Next, the call control server 300 notifies the subscriber data management device 500 of the subscriber data including the cooperation data generated in step S22 together with information for specifying the accommodation transfer system device at regular intervals (step). S23).

  Note that the notification to the subscriber data management apparatus 500 may be performed immediately after step S22.

  Next, the subscriber data management device 500 stores the subscriber data notified in step S23 and the information for specifying the accommodation transfer system device as originals in a predetermined position of the subscriber data original storage unit 51 ( Step S24).

  Next, the subscriber data management device 500 notifies the call control server 300 of a response that the subscriber data notified in step S23 has been stored in the subscriber data original storage unit 51 (step S25). .

  Finally, the subscriber data including the cooperation data generated in step S22 by the call control server 300 is copied as predetermined cache data in the subscriber data cache management unit 31 together with information for identifying the accommodation transfer system device. Accumulated (step S26).

  As described above, according to the operation example 2, the subscriber data management apparatus 500 accumulates the subscriber data including the linkage data as an original, and the call control server 300 accumulates the subscriber data as duplicate cache data for the original. Therefore, since it is not necessary to make an inquiry to the subscriber data management device 500 at the time of a call connection request, load concentration of the subscriber data management device 500 is prevented even when call connection requests are generated simultaneously. The response time to the user terminal 900 can be shortened.

[Operation example 3]
In the operation example 3, a recovery operation when a failure occurs in the call control server 300 and the cache data stored in the subscriber data cache management unit 31 is lost will be described. FIG. 6 is a diagram illustrating an operation sequence of the third operation example.

  First, after the failure occurs, the call control server 300 starts recovery by executing a restart process (step S31).

  Next, the call control server 300 requests the subscriber data management device 500 to obtain all subscriber data or differential data of subscriber data updated after the failure occurrence time (step S32).

  Next, the subscriber data management device 500 stores the difference data of all the subscriber data related to the transfer system device 100 accommodated in the call control server 300 or the subscriber data updated after the failure occurrence time. Obtained from the subscriber data original storage unit 51 and the subscriber data backup storage unit 52 (step S33). Specifically, duplicate data of subscriber data stored as an original is acquired.

  Next, the subscriber data management device 500 performs call control together with all subscriber data acquired in step S33 or differential data of subscriber data updated after the failure occurrence time together with information for identifying the accommodation transfer system device. The server 300 is notified (step S34).

  Finally, by the call control server 300, all the subscriber data acquired from the subscriber data management device 500 or the difference data of the subscriber data updated after the failure occurrence time, together with information for identifying the accommodation transfer system device, The data is stored in a predetermined position in the subscriber data cache management unit 31 (step S35).

  In step S32, the call control server 300 requests the subscriber data management device 500 to obtain all subscriber data and update history, and in step S33, the subscriber data management device 500 All the subscriber data and update history related to the transfer system device 100 accommodated in the control server 300 are acquired from the subscriber data original storage unit 51 and the subscriber data backup storage unit 52. In step S34, the subscriber data Based on all the subscriber data acquired from the management device 500 and the update history, the latest subscriber data is generated and stored in a predetermined location of the subscriber data cache management unit 31 together with information for identifying the accommodation transfer system device. You may make it do.

  As described above, according to the operation example 3, when the duplicate cache data is lost by the call control server 300, the subscriber data related to the transfer system 100 accommodated in the call control server 300 is managed as the subscriber data management. Since the data is acquired from the device 500, it can be recovered using the subscriber data as the original, so that the recovery processing when the call control server 300 fails can be simplified.

[Operation Example 4]
In the operation example 4, the operation when the call control server is transferred (switched) for each transfer system device will be described with reference to the overall configuration of FIG. 7 instead of FIG.

  Here, as shown in FIG. 8 (a), the accommodated call control server held in the subscriber data original storage unit 51 by the subscriber data management apparatus 500 and the accommodated transfer system accommodated in the call control server. It is assumed that the correspondence table indicating the correspondence relationship with the device has information on two accommodated call control servers, that is, the migration source and the migration destination. FIG. 9 is a diagram illustrating an operation sequence of the operation example 4.

  First, the maintenance operation device 700 makes a transfer system device (transfer system device # 1) 100 to be switched and a transfer destination call control server (call control server # 2) 300b to the subscriber data management device 500. A call control server transition instruction including the above is notified (step S41).

  Next, in the correspondence table (see FIG. 8A) held in the subscriber data original storage unit 51 by the subscriber data management device 500, the transfer system device # 1 notified from the maintenance operation device 700 is transferred to the transfer system device # 1. Call control server # 2 is stored in the corresponding accommodated call control server (migration destination) (step S42).

  Next, the subscriber data management device 500 applies to the transfer source call control server (call control server # 1) 300a and the transfer destination call control server (call control server # 2) 300b corresponding to the transfer system device # 1. Subscriber data of all user terminals 900 accommodated in the transfer system device # 1 is notified together with information specifying the accommodated transfer system device (steps S43 and S45).

  For the source call control server (call control server # 1) 300a, the difference that has been changed after step S41 in the subscriber data of all user terminals accommodated in the transfer system device # 1. The subscriber data is notified, and all the subscriber data is notified to the transfer destination call control server (call control server # 2) 300b.

  Next, all the subscriber data acquired from the subscriber data management device 500 by the transfer source call control server (call control server # 1) 300a and the transfer destination call control server (call control server # 2) 300b are accommodated and transferred. Along with the information specifying the system device, it is stored in a predetermined position of each subscriber data cache management unit 31 (step S44, step S46).

  Next, the subscriber data management device 500 notifies the migration source call control server (call control server # 1) 300a that all the user terminals 900 to be accommodated are blocked (step S47).

  Although not shown, the migration source call control server (call control server # 1) 300a and the migration destination call control server (call control server # 2) 300b set routing information.

  Next, the subscriber data management device 500 uses the transfer source call control server (call control server # 1) 300a as a subscriber of all the user terminals 900 accommodated in the transfer system device # 1 to be switched. Data deletion is notified (step S48).

  Next, the migration source call control server (call control server # 1) 300a deletes the subscriber data of all user terminals accommodated in the transfer system device # 1 from the subscriber data cache management unit 31 (step). S49).

  Finally, as shown in FIG. 8 (a), the subscriber data management device 500 performs the accommodated call control server corresponding to the transfer system device # 1 in the correspondence table held in the subscriber data original storage unit 51. The call control server # 1 stored in (migration source) is deleted (step S50). Step S50 may be performed after step S42.

  As described above, according to the operation example 4, when the call control server accommodating the transfer system device 100 is transferred to another call control server by the subscriber data management apparatus 500, The identifier of the call control server defined in the correspondence table indicating the correspondence relationship with the accommodated call control server 300 is changed to the identifier of the transfer destination call control server, and the transfer destination call control server 300b is associated with the transfer system 100. Since the subscriber data is transmitted and the subscriber data of the migration source call control server 300a is deleted, the recovery process when the call control server 300 fails can be simplified.

[Operation Example 5]
In the operation example 5, the operation when the transfer system device is shifted (switched) for each user terminal will be described with reference to the overall configuration of FIG. 10 instead of FIG.

  Here, as shown in FIG. 11 (b), in the original subscriber data stored in the subscriber data original storage unit 51 by the subscriber data management device 500, there are two accommodated transfer systems of the migration source and the migration destination. It shall have information about the device. FIG. 12 is a diagram illustrating an operation sequence of the fifth operation example.

  First, the maintenance operation apparatus 700 includes the user terminal (user terminal # 1) 900 to be switched and the transfer destination transfer system apparatus (transfer system apparatus # 2) 100b with respect to the subscriber data management apparatus 500. The user terminal migration instruction is notified (step S51).

  Next, of the original subscriber data stored in the subscriber data original storage unit 51 by the subscriber data management device 500 (see FIG. 11B), the user terminal # notified from the maintenance operation device 700 is received. The transfer system device # 2 is stored in the accommodated transfer system device (migration destination) corresponding to one subscriber identifier # 1 (step S52).

  Next, the subscriber data management device 500 sends the subscriber data of the user terminal # 1 to the source call control server (call control server # 1) 300a and the destination call control server (call control server # 2) 300b. Is notified (step S53, step S55).

  The transfer source call control server (call control server # 1) 300a is notified of the difference subscriber data that has been changed after step S51 among the subscriber data of the user terminal # 1, and the transfer is performed. All the subscriber data is notified to the destination call control server (call control server # 2) 300b.

  Next, the subscriber data of the user terminal # 1 acquired from the subscriber data management device 500 by the migration source call control server (call control server # 1) 300a and the migration destination call control server (call control server # 2) 300b is stored. The data is stored in predetermined positions in each subscriber data cache management unit 31 (steps S54 and S56).

  Next, the subscriber data management device 500 notifies the migration source call control server (call control server # 1) 300a that the user terminal # 1 to be switched is blocked (step S57).

  Although not shown, the migration source call control server (call control server # 1) 300a and the migration destination call control server (call control server # 2) 300b set routing information.

  Next, the subscriber data management device 500 notifies the migration source call control server (call control server # 1) 300a of the deletion of the subscriber data of the user terminal # 1 that is the switching target (step S58). .

  Next, the migration source call control server (call control server # 1) 300a deletes the subscriber data of the user terminal # 1 from the subscriber data cache management unit 31 (step S59).

  Next, as shown in FIG. 11 (b), the subscriber data management device 500 uses the subscriber identifier # of the user terminal # 1 among the original subscriber data held in the subscriber data original storage unit 51. 1 is deleted (step S60). Step S60 may be performed after step S52.

  Next, the subscriber data management device 500 gives the transfer destination call control server (call control server # 2) 300b an accommodation transfer system device corresponding to the subscriber identifier # 1 of the subscriber data of the user terminal # 1 ( The deletion of the transfer system device # 1 stored in the migration source is notified (step S61).

  Finally, the transfer system device stored in the accommodated transfer system device (transfer source) corresponding to the subscriber identifier # 1 of the subscriber data of the user terminal # 1 by the transfer destination call control server (call control server # 2) 300b # 1 is deleted from the subscriber data cache management unit 31 (step S62).

  As described above, according to the operation example 5, when the transfer system device accommodating the user terminal 900 is transferred to another transfer system device by the subscriber data management device 500, the identifier of the transfer system device in the subscriber data. Is changed to the identifier of the transfer destination transfer system device, the changed subscriber data is transmitted to the transfer destination call control server 300b accommodating the transfer destination transfer system device 100b, and the transfer source transfer device 100a is accommodated. Since the subscriber data of the migration source call control server 300a being deleted is deleted, the recovery process in the event of a failure of the call control server 300 can be simplified.

[Operation Example 6]
In the operation example 6, the preferential operation when the call control server 300 sets the subscriber data in the subscriber data cache management unit 31 in the operation examples 3 to 5 will be described.

  The subscriber data setting process for the call control server 300 in the operation example 3 to the operation example 5 is performed in parallel with the reception of the call control in order to avoid service interruption. Here, when a call control request is generated from the user terminal 900 during data setting, priority is given to the setting of subscriber data related to the user as shown in FIG. FIG. 14 is a diagram illustrating an operation sequence of the operation example 6.

  When the transfer operation apparatus # 1 to be transferred and the call control server # 2 as information of the recovery or transfer destination call control server 300b are notified from the maintenance operation apparatus 700, the subscriber data management apparatus 500 transfers the transfer system apparatus # 1. All the subscriber data corresponding to # 1 are notified to the transfer destination call control server (call control server # 2) 300b.

  Then, the migration destination call control server (call control server # 2) 300b sequentially sets the subscriber data for each subscriber in the subscriber data cache management unit 31 based on the notified subscriber data (step) S63).

  In this setting process, from which subscriber the setting is performed may be based on a value set in the subscriber data or based on the order in which the subscriber data is received.

  If a signal is received from the user terminal 900 during the above-described sequential setting (step S64), the sequential setting process is temporarily stopped (step S65), and whether the user terminal 900 that transmitted the signal has already been set with data. If it is not set, the subscriber data setting process for the subscriber is preferentially performed (step S66). After the completion of this process, the opening process in step S63 is resumed (step S67).

  As described above, according to the operation example 6, when the subscriber data is set in the call control server 300, the subscriber data related to the user terminal 900 that has generated the call control request is prioritized. It is possible to reduce the time during which a subscriber who uses the communication cannot use communication.

DESCRIPTION OF SYMBOLS 1 ... Call control system 100 ... Transfer system apparatus 100a ... Migration source transfer system apparatus 100b ... Migration destination transfer system apparatus 300 ... Call control server 300a ... Migration source call control server 300b ... Migration destination call control server 31 ... Subscriber data cache management 32: Subscriber data cache transmission / reception unit 33 ... Subscriber management device interface 34 ... Transfer system device interface 500 ... Subscriber data management device 51 ... Subscriber data original storage unit 52 ... Subscriber data backup storage unit 53 ... Subscriber data Transmission / reception unit 54 ... maintenance operation device interface 55 ... call control server interface 700 ... maintenance operation device 900 ... user terminal S ... processing step

Claims (6)

In a subscriber data management method performed by a call control server that controls a call transmitted from a user terminal of a subscriber via a transfer system device, and a subscriber data management device that manages subscriber data related to the subscriber,
By the subscriber data management device,
Receiving subscriber data composed of first subscriber data input to the maintenance operation device and second subscriber data notified from the user terminal;
Storing the received subscriber data in a storage means as an original,
By the call control server,
Receiving the subscriber data;
Storing the received subscriber data in a storage means as duplicate cache data for the original;
A subscriber data management method comprising: By the call control server,
2. The method according to claim 1, further comprising the step of acquiring, from the subscriber data management device, subscriber data relating to a transfer system device accommodated by the call control server when the duplicate cache data is lost. The subscriber data management method described. By the subscriber data management device,
Call control defined in a correspondence table indicating a correspondence relationship between the accommodated transfer system device and the accommodated call control server when the call control server accommodating the transfer system device moves to another call control server A step of changing the identifier of the server to the identifier of the transfer destination call control server, transmitting the subscriber data related to the transfer system device to the transfer destination call control server, and deleting the subscriber data of the transfer source call control server The subscriber data management method according to claim 1 or 2, further comprising: The original is subscriber data in which the subscriber data is associated with a transfer system apparatus that accommodates a user terminal that has notified the subscriber data,
By the subscriber data management device,
When the transfer system apparatus that accommodates the user terminal shifts to another transfer system apparatus, the identifier of the transfer system apparatus in the subscriber data is changed to the identifier of the transfer system apparatus of the transfer destination, and the transfer destination transfer Further comprising the step of transmitting the changed subscriber data to the call control server accommodating the system device and deleting the subscriber data of the call control server accommodating the transfer-source device of the migration source. The subscriber data management method according to claim 3.   5. The subscriber data relating to a user terminal that has generated a call control request is prioritized when subscriber data is set in the storage means in the call control server. Subscriber data management method. In a call control system comprising: a call control server that controls a call transmitted from a user terminal of a subscriber via a transfer system device; and a subscriber data management device that manages subscriber data related to the subscriber.
The subscriber data management device comprises:
Means for receiving subscriber data composed of first subscriber data input to the maintenance operation device and second subscriber data notified from the user terminal;
Means for storing the received subscriber data in a storage means as an original;
Call control defined in a correspondence table indicating a correspondence relationship between the accommodated transfer system device and the accommodated call control server when the call control server accommodating the transfer system device moves to another call control server Means for changing the identifier of the server to the identifier of the call control server of the transfer destination, transmitting the subscriber data related to the transfer system device to the call control server of the transfer destination, and deleting the subscriber data of the call control server of the transfer source When,
The original is subscriber data in which the subscriber data is associated with a transfer system apparatus accommodating a user terminal that has notified the subscriber data, and the transfer system apparatus accommodating the user terminal Is transferred to another transfer system device, the identifier of the transfer system device in the subscriber data is changed to the identifier of the transfer system device of the transfer destination, and the call control server accommodating the transfer system device of the transfer destination is changed. Means for transmitting the changed subscriber data and deleting the subscriber data of the call control server that accommodates the transfer-source device of the migration source,
The call control server
Means for receiving the subscriber data;
Means for storing the received subscriber data in a storage means as duplicate cache data for the original;
Means for acquiring, from the subscriber data management device, subscriber data related to a transfer system device accommodated in the call control server when the cache data of the copy is lost;
A call control system comprising:

Images