JP2007299151A - Communication system, redundant server, and notification method for data change - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To notify a notice registration request origin of data change even when the data change is first notified to a redundant server different from the notice request for the data change. <P>SOLUTION: This communication system is provided with a first client which changes data, and notifies any redundant server of data change and a second client which notifies any redundant server of the change in changing the data of the first client. Also, this communication system is provided with a storage means for storing notice registration information showing a redundant server to be registered from a second client in association with the client information. When a notice registration request is made from the second client, each redundant server sets notice registration information in the storage means, and when data change is notified from the first client, each redundant server notifies the second client to be determined by the notice registration information, of the data change. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a communication system, a redundant server, and a data change notification method, and can be applied to, for example, notification from a server with an N-duplex configuration to a client in an IP network.

  3GPP (3rd Generation Partnership Project) is an organization that studies next-generation All-IP-based mobile communication networks, and 3GPP is studying IMS (Internet Multimedia Sub System), which is a multimedia communication system using SIP. ing. Non-Patent Document 1 defines a part of the IMS model discussed in 3GPP, and attention is focused on access means to an HSS (Home Subscriber Server). The HSS is a server that operates as a kind of user management database in which subscriber data in the telephone network (authentication information, telephone number, contract information, etc. when the terminal connects to the network) is stored.

  A data change notification method from HSS to SIP AS (SIP Application Server) described in Non-Patent Document 1 will be described with reference to FIG. FIG. 2 is a diagram of FIG. The processing 10 to 13 in 1.1 is rewritten so that it can be easily understood.

  In the IP network, the HSS 1 appropriately communicates with an S-CSCF (Serving-Call Session Control Function) 2 and an SIP AS (SIP Application Server) 3. The S-CSCF 2 is a kind of SIP server that relays SIP messages, is a central SIP server for providing services to users, and is a proxy server to which all messages related to users to be managed are routed The server performs message processing (including message transfer processing to AS) and the like (server that processes SIP signals defined in RFC3261) and operates as a registration server. . The SIP AS 3 is a SIP entity that transmits and receives SIP messages to and from the S-CSCF 2 in order to realize an application, and operates as an arbitrary server or UA depending on the content of the service to be realized (for example, defined in RFC3265). Server providing SIP application such as presence service).

  In FIG. 2, the ShipAS 3 transmits a notification registration request to the HSS 1 (process T1). Here, the notification registration request is a message for requesting notification from the HSS 1 when the designated data is changed. The example of FIG. 2 is an example in which the HSS 1 is requested to notify the SIP AS 3 of the changed data when the data of the subscriber A is changed. The HSS 1 that has received the notification registration request returns a notification registration request response indicating that the notification registration request reception process has been completed to the SIP AS 3 (process T2).

  If the S-CSCF 2 changes the data of the subscriber A, the S-CSCF 2 transmits a data acquisition / change request for the subscriber A to the HSS 1 (process T3), and the HSS 1 receives the request. A data acquisition / change request response indicating that is completed is returned (process T4).

Since the data of the subscriber A related to the notification registration request has been changed, the HSS 1 notifies the changed data to the SIP AS 13-1 as a data change notification (process T5). The SIP AS 3 that has received the data change notification returns a data change notification response to the HSS 1 (process T6). By the above sequence, the SIP AS 3 can receive the change contents when the data of the subscriber A is changed.
3GPP TS 29.328 V6.8.0 (ftp://ftp.3gpp.org/Specs/archive/29_series/29.328/29328-680.zip)

  In the notification method from the HSS described in Non-Patent Document 1, the reliability of the HSS is not considered.

  In general, in a network where a service stop such as a telephone is not allowed, it is required that a server be configured in a duplex or N-duplex configuration so that the service can be continued with the remaining servers even if one server goes down. Here, when the HSS has an N-layer configuration, the notification method from the HSS described in Non-Patent Document 1 may not be used for proper notification.

  For example, as shown in FIG. 3 (A), it is assumed that the HSS1-1 and HSS1-2 are duplexed and both systems perform ACT operation. It is assumed that both the HSS 1-1 and the HSS 1-2 are connected to the same data storage unit (Storage) 4 and subscriber data is stored in the Storage 4. The Ship AS 3 and the S-CSCF 2 communicate with either one of the HSS 1-1 and the HSS 1-2. Here, it is assumed that S-CSCF2 communicates with HSS1-2 and SipAS3 communicates with HSS1-1.

  Health checks are periodically performed between the S-CSCF2 and the HSS1-2 and between the SIPAS3 and the HSS1-1. For example, as shown in FIG. 3B, when a failure occurs in the HSS 1-1, the SIP AS 3 switches to the HSS 1-2 when it detects that the connection with the HSS 1-1 is broken by the health check. In this way, when a failure occurs in one HSS, switching to the remaining HSS prevents the service from being stopped when the HSS failure occurs.

  However, when the SIP AS 3 is communicating with the HSS 1-1 and the S-CSCF 2 is communicating with the HSS 1-2 as shown in FIG. 3A, the data change notification registration request is received from the SIP AS 3 as shown in FIG. The HSS 1-1 receives the data change request from the S-CSCF 2 and becomes the HSS 1-2. The HSS 1-1 cannot detect the change of the subscriber data and cannot notify the SIP AS 3.

  Therefore, because the server has an N-duplex configuration, even if the data change notification registration request is different from the server to which the data change is first notified, the data change can be notified to the notification registration request source. A system, redundant server, and data change notification method are desired.

  A communication system according to a first aspect of the present invention provides a first client that changes data, a plurality of redundant servers that can be notified of data changes from the first client, and the first server for any one of the redundant servers. A second client that registers to be notified when the data of the client is changed, and a client information storage unit that stores information related to the first client shared by the plurality of redundant servers. The client information storage means includes a notification enabling information storage unit that stores information indicating which redundant server is notified and registered from which second client in association with client information, When each redundant server sets information in the notification enabling information storage unit when a notification registration request is received from the second client In, when the data change from the first client is notified, and notifies the data changes to the second client, which is defined by stored information of the notification enabling information storage unit.

  The redundant server according to the second aspect of the present invention provides a first client that performs data change, a plurality of redundant servers that can be notified of data change from the first client, and the first server with respect to any one of the redundant servers. Stores information related to the first client shared by the plurality of redundant servers and the second client that registers to be notified when the data of the client changes, and corresponds to the client information In addition, any one of the redundant servers in a communication system including client information storage means having a notification enabling information storage unit that stores information indicating which of the second clients is registered for notification from which second client When the notification registration request is received from the second client, information is set in the notification enabling information storage unit. In addition, when a data change is notified from the first client, the data change is notified to the second client defined by the storage information in the notification enabling information storage unit. .

  A data change notification method according to a third aspect of the present invention includes a first client that performs data change, a plurality of redundant servers that can be notified of data change from the first client, and any one of the redundant servers, Client information storage that stores information related to the first client shared by the plurality of redundant servers and a second client that registers to be notified when the data of the first client is changed A data change notification method in a communication system comprising: means for indicating which redundant server is notified and registered by which second client in association with the client information; Each of the redundant servers has a notification registration request from the second client. Is set in the notification enabling information storage unit, and when the data change is notified from the first client, it is defined by the storage information in the notification enabling information storage unit. The data change is notified to the second client.

  According to the present invention, even if the server is duplicated and the data change notification registration request is different from the server to which the data change is first notified, the data change can be notified to the notification registration request source. become able to.

(A) First Embodiment Hereinafter, a first embodiment of a communication system, a redundant server, and a data change notification method according to the present invention will be described with reference to the drawings.

(A-1) Configuration of First Embodiment FIG. 1 is a block diagram illustrating a configuration of a communication system 10 according to the first embodiment.

  In FIG. 1, a communication system 10 according to the first embodiment includes HSS 11-1, HSS 11-2, S-CSCF 12, SipAS 13 and Storage (data storage unit) 14 as components. HSS11-1, HSS11-2, S-CSCF12, and ShipAS13 are connected via IP network 15, and Storage14 is connected to HSS11-1 and HSS11-2 via different dedicated lines (Fibre Channel). Yes.

  HSS11-1, HSS11-2, S-CSCF12, and ShipAS13 correspond to hardware information processing servers that have communication functions, and are basically described in the section of the prior art by software processing. It is responsible for the functions described in the IMS model discussed in 3GPP.

  In the case of the first embodiment, the HSS 11-1, the HSS 11-2, the S-CSCF 12, and the Ship AS 13 are each equipped with a program for executing the sequence shown in FIG. 6, and the HSS 11-1 and the HSS 11-2 are A program P for executing the processing flow shown in FIG. 7 is installed. Note that the functions of the S-CSCF 12 and the Ship AS 13 are the same as the conventional ones, and only the functions of the HSS 11 (11-1, 11-2) are different from the conventional ones.

  Both HSS 11-1 and HSS 11-2 constitute an ACT redundant system (HSS is a redundant server), and S-CSCF 12 and Ship AS 13 are connected to either HSS 11-1 or HSS 11-2. Each of the S-CSCF 12 and the Ship AS 13 periodically performs a health check on the HSS 11-1 or HSS 11-2 that is connected to each other, and when a failure occurs in the connected HSS, the connection is switched to the other HSS.

  The Storage 14 functions as a data storage unit common to the HSS 11-1 and HSS 11-2, and stores subscriber data SD whose format is shown in FIG.

  In FIG. 5, the subscriber data SD comprises a subscriber identification information field F1, a SIP AS-Subscribe information field F2, and a service related data field F3. The subscriber identification information field F1 is the same as the existing one, and includes, for example, a subscriber ID field F11 and a telephone number field F12. The field F3 of data related to the service is the same as the existing one, and describes, for example, the type of service provided to the subscriber.

  The field F2 of the SIP AS-Subscribe information is newly provided in the first embodiment. When the HSS 11-1 or HSS 11-2 receives a notification registration request from the Ship AS 13, the information is set in the field F2 of the subscriber's Ship AS-Subscribe information related to the request. The SIP AS-Subscribe information is used to share information such as “which subscriber's data needs to be notified to the SIP AS” between the HSS 11-1 and the HSS 11-2. The field F2 includes a ShipAS field F21 and an HSS field F22. The ShipAS field F21 describes the address of the ShipAS that transmitted the notification registration request, and the HSS field F22 describes the address of the HSS that received the notification registration request. Is done.

(A-2) Operation of the First Embodiment Next, the notification operation when the subscriber data is changed (including the time when a part of data is newly acquired) in the communication system 10 of the first embodiment will be described. This notification operation is illustrated in FIG. This is an operation corresponding to processing 10 to 13 in 1.1. In the following description, it is assumed that the S-CSCF 12 communicates with the HSS 11-1 and the ShipAS 13 communicates with the HSS 11-2.

  FIG. 6 is a sequence diagram during a notification operation in the communication system 10 according to the first embodiment. FIG. 7 is a flowchart showing the operation (program P) of the HSSs 11-1 and 11-2 during the notification operation.

  First, with reference to the sequence diagram of FIG. 6, the flow of processing during the notification operation in the entire communication system 10 of the first embodiment will be described.

  Process T11: The ShipAS 13 transmits a notification registration request to the HSS 11-2. In the notification registration request, subscriber identification information (subscriber ID and telephone number) is input. Here, it is assumed that the notification registration request is for the subscriber A.

  Process T12: When receiving the notification registration request, the TSS 11-2 searches the storage 14 using the subscriber identification information as a key, and sets the address of the HSS 11-2 in the HSS field F22 of the SIPAS-Subscribe information of the corresponding subscriber data. , The address of the ShipAS 13 is set in the ShipAS field F21. Note that the initial value of the SIP AS-Subscribe information (the state in which the SIP AS 13 is not registered for notification) is NULL for both the HSS field F22 and the SIP AS field F21.

  Process T13: The HSS 11-2 updates the SIP AS-Subscribe information of the corresponding subscriber data in Storage 14, and then returns a response to the notification registration request to the SIP AS 13.

  Process T14: Assume that the S-CSCF 12 transmits a data acquisition / change request to the HSS 11-1 for updating the subscriber data (subscriber A). The data acquisition / change request includes subscriber identification information, subscriber data changed by the S-CSCF 12, and a change request flag. If the change request flag is TRUE, the HSS 11-1 changes the subscriber data. If the change request flag is FALSE, the HSS 11-1 only returns the subscriber data. In the sequence of FIG. 6, it is assumed that the change request flag is TRUE.

  Process T15: The HSS 11-1 that has received the data acquisition / change request acquires the subscriber identification information from the data acquisition / change request, searches the storage 14 using the subscriber identification information as a key, and acquires the corresponding subscriber data. .

  Process T16: The HSS 11-1 holds the SIP AS-Subscribe information F2 of the acquired subscriber data until the notification request transmission in process T18 described later is completed.

  Process T17: The HSS 11-1 acquires subscriber data from the data acquisition / change request received from the S-CSCF 12, and updates the subscriber data of Storage 14. At this time, the contents of the SIPAS-Subscribe information of the subscriber data stored in the Storage 14 are not updated.

  Process T18: The HSS 11-1 checks the HSS field F22 of the ShipAS-Subscribe information F2 held in the process T16. Here, since the address of the HSS 11-2 is described in the HSS field F22 of the ShipAS-Subscribe information F2, the HSS 11-1 transmits a notification request to the HSS 11-2. Note that the notification request includes the SIPAS-Subscribe information F2 retained in the process T16 and the changed subscriber data. In addition, when the held SIPAS-Subscribe information F2 is NULL, the notification request is not transmitted.

  Process T19: After transmitting the notification request, the HSS 11-1 returns a response to the data acquisition / change request received in Process T14 to the S-CSCF 12.

  Process T20: The HSS 11-2 that has received the notification request in process T18 confirms the ShipAS field F21 of the ShipAS-Subscribe information F2 included in the notification request, and acquires the address of the ShipAS13. Further, the HSS 11-2 acquires the changed subscriber data included in the received notification request, and transmits the changed subscriber data to the SIP AS 13 as a data change notification.

  Process T21: When the ShipAS 13 receives the data change notification from the HSS 11-2, it returns a response to the data change notification.

  Even if the HSS 11-2 that has received the notification registration request is different from the HSS 11-1 that has acquired the data acquisition / change request, the request source is notified of the change in the requested subscriber data. can do.

  As is clear from the comparison between FIG. 6 and FIG. 2, the operations of the S-CSCF 12 and the Ship AS 13 are the same as those of the conventional one.

  Next, details of the operation related to the notification operation in the HSS 11 (11-1, 11-2) of the first embodiment will be described with reference to the flowchart of FIG.

  Step S1: When the HSS 11 is activated, the processing shown in FIG. 7 is started.

  Step S2: It is confirmed whether a data acquisition / change request is received from the S-CSCF (12). If received, the process proceeds to step S5. If not received, the process proceeds to step S3.

  Step S3: It is confirmed whether a notification registration request is received from the SipAS (13). If received, the process proceeds to step S12. If not received, the process proceeds to step S4.

  Step S4: It is confirmed whether a notification request is received from another HSS. If received, the process proceeds to step S14, and if not received, the process proceeds to step S2 again. That is, in a state where a request from an external device or the like has not been received, steps S2 to S4 are repeated to enter a reception waiting state.

  Step S5: The processes from Step S5 to Step S11 are a series of processes when a data acquisition / change request is received from the S-CSCF (12), and a series of processes T15 to T19 in FIG. 6 described above. Corresponding to In step S5, subscriber identification information is acquired from the data acquisition / change request, storage (14) is searched, and subscriber data is acquired.

  Step S6: Check the change request flag in the data acquisition / change request, in other words, check whether the subscriber data has been changed. If TRUE, go to Step S7. If FALSE, go to Step S11. Transition.

  Step S7: The SIP AS-Subscribe information F2 of the subscriber data acquired from the Storage 14 in Step S5 is held.

  Step S8: The subscriber data of Storage 14 is updated to the update contents described in the received data acquisition / change request.

  Step S9: It is confirmed whether or not the notification destination HSS is specified in the HSS field F22 of the SIP AS-Subscribe information F2 held in Step S7. If it is specified (if not NULL), the process proceeds to Step S10. If the notification destination HSS is not designated, the process proceeds to step S11.

  Step S10: A notification request is transmitted to the notification destination HSS described in the HSS field F22 of the SIP AS-Subscribe information F2 held in step S7.

  Step S11: A data acquisition / change response is transmitted to the S-CSCF (12) that has transmitted the data acquisition / change request. After transmission, the process returns to step S2.

  Step S12: This step S12 and the next step S13 are processes when a notification registration request is received from the SipAS (13), and correspond to the processes T12 and T13 of FIG. When the notification registration request is received from the ShipAS (13), the storage (14) is searched using the subscriber identification information of the notification registration request as a key. The HSS address is set in the HSS field F22 of the SIPAS-Subscribe information F2 of the subscriber data obtained by searching Storage (14), and the address of the SiPS (13) that transmitted the notification registration request is set in the SIP AS field F21. Set.

  Step S13: A response to the notification registration request is transmitted to the Ship AS (13) that has transmitted the notification registration request. After transmission, the process returns to step S2.

  Step S14: This step S14 and the next step S15 are processes when a notification request is received from another HSS, and correspond to the above-described processes T20 and T21 of FIG. When the notification request is received from another HSS, the SIP AS-Subscribe information F2 and the changed subscriber data included in the notification request are acquired, and the SIP AS (13) specified in the SIP AS field F21 of the SIP AS-Subscribe information F2 is acquired. ) Send data change notification to

  Step S15: Waiting for a response to the data change notification from the ShipAS (13), and when receiving the response, return to Step S2.

  By executing the program shown in FIG. 7, the HSS can execute the processing at the time of the notification operation as the HSS containing the SIPAS 13 like the HSS-2 shown in FIG. 6, and the HSS shown in FIG. 6. The process at the time of the notification operation as the HSS accommodating the S-CSCF 12 such as -1 can be executed.

(A-3) Effects of the First Embodiment As described above, according to the first embodiment, (a) SIPAS-Subscribe information is prepared as data in Storage, (b) Notification from the SIPAS When registration is requested, information related to the notification is stored in the storage. (C) When changing the subscriber data, refer to the SIPAS-Subscribe information to notify that there is a data change between the HSSs. Even when the HSS has a duplex configuration, the subscriber data change notification can be transmitted to the SipAS.

(B) Second Embodiment Next, a second embodiment of the communication system, redundant server, and data change notification method according to the present invention will be described with reference to the drawings.

  In general, there are a plurality of ShipAS. For this reason, it is conceivable that the SIP AS, which should not be registered for notification, sends a notification registration request due to a server setting error or an unauthorized server. The second embodiment has been made in consideration of such security aspects.

(B-1) Configuration of the Second Embodiment FIG. 8 is a block diagram showing the configuration of the communication system 10B of the second embodiment, and the same and corresponding parts as FIG. 1 according to the first embodiment. Are indicated by the same reference numerals.

  The communication system 10B of the second embodiment is different from the first embodiment in that it includes a plurality (three examples in FIG. 8) of the SIP ASs 13-1 to 13-2. Each of the SIP ASs 13-1 to 13-3 is connected to one of the HSS 11-1 and the HSS 11-2.

  The functions of the S-CSCF 12 and the SIP ASs 13-1 to 13-3 are the same as those of the first embodiment.

  The HSSs 11-1 and 11-2 of the second embodiment are configured to determine whether or not notification registration can be performed with reference to the storage content (subscriber data SDB) of the Storage 14 when receiving the notification registration request. It differs from that of the first embodiment. In other words, the storage program PB of the HSS 11-1 and 11-2 of the second embodiment is provided with a part related to such determination.

  FIG. 9 is an explanatory diagram showing the format of the subscriber data SDB stored in the storage 14 of the second embodiment.

  The subscriber data SDB of the second embodiment is different from that of the first embodiment in that a permitted ShipAS list F23 is added to the ShipAS-Subscribe information F2. The permitted Ship AS list describes a list of Ship ASs that are permitted to register for notification for the subscriber in the row. In the case of the example in FIG. 9, for the subscriber A, the SIP ASs that can be notified and registered are the Ship AS 13-1 and the Ship AS 13-2, and the Ship AS 13-3 is not permitted to register for notification. The information of this list may be set together with, for example, registering data of a certain subscriber in the subscriber data SDB, and the administrator of the system sets it later using a maintenance terminal or the like. You may make it get.

(B-2) Operation of Second Embodiment FIG. 10 is a sequence diagram at the time of a subscriber data change notification operation in the communication system 10B of the second embodiment, and FIG. 6 according to the first embodiment is shown in FIG. It is a corresponding drawing.

  In FIG. 10, the SIP AS 13-1 to which notification registration is permitted makes a notification registration request, and accordingly, a series of processes T11 to T21 when notifying the change of the requested subscriber data is performed in the first implementation. It is almost the same as the processing of the form. However, the process T12 is slightly different.

  Process T12 of the second embodiment: Upon receiving the notification registration request, the process T12: HSS 11-2 searches the Storage 14 using the subscriber identification information as a key, and acquires the SIP AS-Subscribe information of the corresponding subscriber data. Further, it is confirmed whether or not there is a ShipAS 13-1 that is a transmission source of the notification registration request in the permitted ShipAS list F23 of the ShipAS-Subscribe information F2. In the case of the subscriber data example of FIG. 9, since the SIP AS 13-1 is present in the permitted Ship AS list F23 of the subscriber A related to the notification registration request, the HSS 11-2 permits the notification registration of the Ship AS 13-1 and the Ship AS- The address of the HSS 11-2 is set in the HSS field F22 of the subscribe information F2, and the address of the source SIP AS 13-1 is set in the SipAS field F21.

  Processes T31 and T32 in FIG. 10 are processes when the SIP AS 13-3 to which notification registration is not permitted makes a notification registration request.

  Process T31: The Ship AS 13-3 transmits a notification registration request for the subscriber A to the HSS 11-2.

  Process T32: The HSS 11-2 that has received the notification registration request searches the subscriber data of the Storage 14 using the subscriber identification information as a key, as in the process T12. Further, the HSS 11-2 confirms the permitted ShipAS list F23 of the ShipAS-Subscribe information F2 of the subscriber data obtained by the search. Since the HSS 11-2 does not have an address of the source SIP AS 13-3, the HSS 11-2 does not permit the notification registration of the Ship AS 13-3, and sends a response to the notification registration request indicating that the notification registration is not permitted to the Ship AS 13-3 (NG )

  FIG. 11 is a flowchart showing the operation of the HSS 11 (11-1, 11-2) according to the second embodiment. The same reference numerals are given to the corresponding steps in FIG. 7 according to the first embodiment. It shows.

  In the case of the second embodiment, the processes of steps S21 to S25 executed when a notification registration request is received from any of the SIP ASs (13-1 to 13-3) are different from those of the first embodiment.

  Step S21: Acquire subscriber identification information from the received notification registration request, search Storage (14) to acquire subscriber data, and confirm the SIP AS-Subscribe information F2 of the subscriber data.

  Step S22: It is confirmed whether or not the address of the SIP AS that has transmitted the notification registration request exists in the permitted SIP AS list F23 of the SIP AS-Subscribe information F2 acquired in step S21. If it exists, the process proceeds to step S23, and if not, the process proceeds to step S25.

  Step S23: The address of the HSS is set in the HSS field F22 of the SIPAS-Subscribe information F2 of the subscriber data obtained by searching the storage (14) in step S21, and the SIP AS that has transmitted the notification registration request to the SIP AS field F21 Set the address.

  Step S24: A response to the notification registration request is returned to the ShipAS that is the source of the notification registration request. After the transmission, the process returns to step S2.

  Step S25: Since the address of the SIP AS that sent the notification request is not in the permitted Ship AS list F23, a response (NG) of the notification registration request indicating that the notification registration is not permitted is returned to the source SIP AS. After the transmission, the process returns to step S2.

(B-3) Effect As described above, according to the second embodiment, the subscriber data to the SIP AS when the HSS is configured in a duplex configuration by providing the SIP AS-Subscribe information with the permitted SIP AS list. In addition to realizing change notification transmission, it is also possible to realize SipAS access control.

(C) Other Embodiments In each of the above embodiments, a case has been described in which the change of subscriber data in the IMS model is notified to the SIP AS, but the present invention is not limited to the IMS model. The present invention is applied to a communication system in which a server that manages data performs all ACT operations with a configuration of duplex or more, and a host that requests notification registration is different from a host that changes data. Can be applied.

  Moreover, although each said embodiment showed what HSS was doubled, this invention is applicable also when it is triple or more.

  Further, in each of the above embodiments, the storage element for storing the subscriber data is shown as Storage. However, in order to improve the performance, a memory DB (database) may be applied instead of Storage.

  In the second embodiment, for permitting access to the SIP AS, the permitted SIP AS list is given the address of the SIP AS. However, other identification information (ID, password, etc.) is applied instead of the SIP AS address. You may do it. Further, instead of storing the list of permitted SipAS in association with the identification information of the subscriber, the identification information list of subscribers that can be notified and registered by the SipAS is stored in association with the address of the SIPAS. May be.

It is a block diagram which shows the structure of the communication system of 1st Embodiment. It is a sequence diagram explaining the notification method from the conventional HSS. It is explanatory drawing of the necessity for making HSS into a redundant structure. It is a sequence diagram for demonstrating the subject by the notification method from the conventional HSS when a HSS is made into a redundant structure. It is explanatory drawing which shows the format of the subscriber data of 1st Embodiment. It is a sequence diagram which shows operation | movement of the whole communication system of 1st Embodiment. It is a flowchart which shows operation | movement of HSS of 1st Embodiment. It is a block diagram which shows the structure of the communication system of 2nd Embodiment. It is explanatory drawing which shows the format of the subscriber data of 2nd Embodiment. It is a sequence diagram which shows operation | movement of the whole communication system of 2nd Embodiment. It is a flowchart which shows operation | movement of HSS of 2nd Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10, 10B ... Communication system, 11-1, 11-2 ... HSS, 12 ... S-CSCF, 13, 13-1 to 13-3 ... SipAS, 14 ... Storage, 15 ... IP network.

Claims (6)

A first client for data modification;
A plurality of redundant servers that can be notified of data changes from the first client;
A second client that registers to notify any of the redundant servers when the data of the first client is changed;
Client information storage means for storing information relating to the first client shared by the plurality of redundant servers,
The client information storage means includes a notification enabling information storage unit that stores information indicating which redundant server is notified and registered from which second client in association with client information,
Each redundant server sets information in the notification enabling information storage unit when a notification registration request is received from the second client, and when a data change is notified from the first client. A data communication is notified to the second client defined by the storage information in the notification enabling information storage unit. The client information storage means includes a registration availability information storage unit that associates information related to the first client with identification information of the second client that permits registration of data change notification in the first client. Have
Each of the redundant servers, when a notification registration request is received from the second client, when the second client is permitted by the storage information of the registration permission / inhibition information storage unit, The communication system according to claim 1, wherein information is set in the storage unit. A first client that changes data, a plurality of redundant servers that can be notified of data changes from the first client, and a notification to that effect when any of the redundant servers changes data of the first client Storing information related to the first client that is shared by the plurality of redundant servers and the second client that registers that the redundant server is associated with the client information. Any one of the redundant servers in a communication system including a client information storage unit having a notification enabling information storage unit that stores information indicating whether the notification is registered from the second client,
When there is a notification registration request from the second client, information is set in the notification enabling information storage unit, and when a data change is notified from the first client, the notification enabling information A redundant server characterized in that a data change is notified to the second client defined by the storage information of the storage unit. The client information storage means includes a registration availability information storage unit that associates information related to the first client with identification information of the second client that permits registration of data change notification in the first client. Have
When there is a notification registration request from the second client, information is set in the notification enabling information storage unit when the second client is permitted by the storage information in the registration permission / inhibition information storage unit The redundant server according to claim 3, wherein: A first client that changes data, a plurality of redundant servers that can be notified of data changes from the first client, and a notification to that effect when any of the redundant servers changes data of the first client For notifying a data change in a communication system, comprising: a second client that registers to perform the operation; and a client information storage unit that stores information related to the first client shared by the plurality of redundant servers Because
The client information storage means includes a notification enabling information storage unit that stores information indicating which redundant server is notified and registered from which second client in association with client information,
Each redundant server sets information in the notification enabling information storage unit when a notification registration request is received from the second client, and when a data change is notified from the first client. A data change notification method comprising: notifying the second client defined by the storage information in the notification enabling information storage unit of the data change. The client information storage means includes a registration availability information storage unit that associates information related to the first client with identification information of the second client that permits registration of data change notification in the first client. Have
Each of the redundant servers, when a notification registration request is received from the second client, when the second client is permitted by the storage information of the registration permission / inhibition information storage unit, 6. The data change notification method according to claim 5, wherein information is set in the storage unit.

Images