System and method for supplementary services setting synchronization
View Patent ↗A synch server comprises a first interface configured to transmit and receive MAP messages, and communicate with a Home Location Register (HLR) in a Circuit-Switched (CS) network, a second interface configured to communicate with a Home Subscriber Server (HSS) in an IP-Multimedia Subsystem (IMS) network, and a third interface configured to transmit and receive Extensible Markup Language (XML) Configuration Access Protocol (XCAP) messages. A synch function module is configured to receive a message containing a change to a supplementary service setting associated with a User Equipment (UE) connected to a Circuit-Switched (CS) network or an IMS network, and communicate the change to the supplementary service setting to both the HLR and the HSS so that the supplementary service settings in both the HLR and the HSS are updated to reflect the change to the supplementary service setting.
1. A synch server comprising:
a Mobile Applications Part (MAP) interface configured to transmit and receive MAP messages from a Circuit-Switched (CS) network and communicate with a Home Location Register (HLR) in the CS network;
an Sh interface configured to communicate with a Home Subscriber Server (HSS) in an IP-Multimedia Subsystem (IMS) network;
a Ut interface configured to transmit and receive Extensible Markup Language (XML) Configuration Access Protocol (XCAP) messages;
a synch function module configured to:
receive a MAP message, via the MAP interface, related to a change to a supplementary service setting associated with a subscriber;
forward the received MAP message to the HLR;
receive a response from the HLR indicative of successful supplementary service setting update in the HLR;
generate an Sh command related to the change to the supplementary service setting related to the subscriber in the received MAP message;
forward the Sh command to the HSS; and
receive a response from the HSS indicative of successful supplementary service setting update in the HSS; and
the synch function module further configured to:
receive an XCAP message, via the Ut interface, related to a change to a supplementary service setting associated with a subscriber;
generate an Sh command related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forward the Sh command to the HSS;
receive a response from the HSS indicative of successful supplementary service setting update in the HSS;
generate a MAP message related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forward the MAP message to the HLR; and
receive a response from the HLR indicative of successful supplementary service setting update in the HLR.
2. The synch server of claim 1 , wherein the synch function module is further configured to generate and transmit an error response message in response to an error in updating the supplementary service setting in one of the HLR and HSS.
3. The synch server of claim 1 , wherein the synch function module is further configured to:
receive an error message from the HSS in response to an error in updating the supplementary service setting after the supplementary service setting in the HLR is already updated; and
restore the supplementary service setting in the HLR that existed prior to the update.
4. The synch server of claim 1 , wherein the synch function module is further configured to:
receive an error message from the HLR in response to an error in updating the supplementary service setting after the supplementary service setting in the HSS is already updated; and
restore the supplementary service setting in the HSS that existed prior to the update.
5. The synch server of claim 1 , wherein the synch function module is further configured to:
receive an error message from the HSS in response to an error in updating the supplementary service setting after the supplementary service setting in the HLR is already updated; and
record an HLR and HSS database misalignment alert entry in a log file.
6. The synch server of claim 1 , wherein the synch function module is further configured to:
receive an error message from the HLR in response to an error in updating the supplementary service setting after the supplementary service setting in the HSS is already updated; and
record an HLR and HSS database misalignment alert entry in a log file.
7. The synch server of claim 1 , wherein the synch function module is further configured to generate a MAP message reporting supplementary service setting update success and transmit the message to a User Equipment originating the supplementary service setting change via the MAP interface.
8. The synch server of claim 1 , wherein the synch function module is further configured to generate a XCAP message reporting supplementary service setting update success, and transmit the message to a User Equipment originating the supplementary service setting change via the Ut interface.
9. The synch server of claim 1 , wherein the synch function module is further configured to receive a MAP message related to a change to a supplementary service setting associated with an My-Time-Modification (ATM) operation, transmit the change to the supplementary service setting in the form of an Sh command and transmit the change to the HSS, and in the form of a MAP message and transmit the change to the HLR.
10. The synch server of claim 1 , wherein the synch function module is further configured to timestamp and log each supplementary service setting update operation.
11. A synch server associated with a Telephony Application Server (TAS) comprising:
a first interface configured to transmit and receive a first type of messages from a Circuit-Switched (CS) network and communicate with a Home Location Register (HLR) in the CS network;
a second interface configured to communicate with a Home Subscriber Server (HSS) in an IP-Multimedia Subsystem (IMS) network using a second type of messages;
a synch function module configured to receive a first type of message containing a change to a supplementary service setting associated with a User Equipment (UE) connected to a Circuit-Switched (CS) network, and communicate the change to the supplementary service setting to both the HLR and the HSS so that the supplementary service settings in both the HLR and the HSS are updated to reflect the change to the supplementary service setting; and
the synch function module further configured to receive a third type of message via a third interface containing a change to a supplementary service setting associated with a User Equipment (UE) connected to an IMS network, and communicate the change to the supplementary service setting to both the HLR and the HSS so that the supplementary service settings in both the HLR and the HSS are updated to reflect the change to the supplementary service setting.
12. The synch server of claim 11 , wherein the synch function module is further configured to:
receive the MAP message, via the first interface, related to the change to a supplementary service setting associated with a subscriber and the UE;
forward the received MAP message to the HLR;
receive a response from the HLR indicative of successful supplementary service setting update in the HLR;
generate an Sh command related to the change to the supplementary service setting related to the subscriber in the received MAP message;
forward the Sh command to the HSS via the second interface; and
receive a response from the HSS indicative of successful supplementary service setting update in the HSS.
13. The synch server of claim 11 , wherein the synch function module is further configured to:
receive the XCAP message, via the third interface, related to a change to a supplementary service setting associated with a subscriber and the UE;
generate an Sh command related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forward the Sh command to the HSS via the second interface;
receive a response from the HSS indicative of successful supplementary service setting update in the HSS;
generate a MAP message related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forward the MAP message to the HLR via the first interface; and
receive a response from the HLR indicative of successful supplementary service setting update in the HLR.
14. The synch server of claim 11 , wherein the synch function module is further configured to receive a MAP message, via the first interface, related to a change to a supplementary service setting associated with an Any-Time-Modification (ATM) operation, transmit the change to the supplementary service setting in the form of an Sh command and transmit the change to the HSS, and in the form of a MAP message and transmit the change to the HLR.
15. The synch server of claim 11 , wherein the synch function module is further configured to generate and transmit an error response message in response to an error in updating the supplementary service setting in one of the HLR and HSS.
16. The synch server of claim 11 , wherein the synch function module is further configured to:
receive an error message from the HSS in response to an error in updating the supplementary service setting after the supplementary service setting in the HLR is already updated; and
restore the supplementary service setting in the HLR that existed prior to the update.
17. The synch server of claim 11 , wherein the synch function module is further configured to:
receive an error message from the HLR in response to an error in updating the supplementary service setting after the supplementary service setting in the HSS is already updated; and
restore the supplementary service setting in the HSS that existed prior to the update.
18. The synch server of claim 11 , wherein the synch function module is further configured to:
receive an error message from the HSS in response to an error in updating the supplementary service setting after the supplementary service setting in the HLR is already updated; and
record an HLR and HSS database misalignment alert entry in a log file.
19. The synch server of claim 11 , wherein the synch function module is further configured to:
receive an error message from the HLR in response to an error in updating the supplementary service setting after the supplementary service setting in the HSS is already updated; and
record an HLR and HSS database misalignment alert entry in a log file.
20. The synch server of claim 11 , wherein the synch function module is further configured to generate a MAP message reporting supplementary service setting update success and transmit the message to a User Equipment originating the supplementary service setting change via the first interface.
21. The synch server of claim 11 , wherein the synch function module is further configured to generate a XCAP message reporting supplementary service setting update success, and transmit the message to a User Equipment originating the supplementary service setting change via the third interface.
22. The synch server of claim 11 , wherein the synch function module is further configured to timestamp and log each supplementary service setting update operation.
23. A telecommunication database synchronization method, comprising:
receiving a Mobile Applications Part (MAP) message containing a change to a supplementary service setting associated with a User Equipment (UE) connected to a Circuit-Switched (CS) network, and communicating the change to the supplementary service setting via a synch server to both a Home Location Register (HLR) of the CS network and a Home Subscriber Server of an IP-Multimedia Subsystem (IMS) network so that the supplementary service settings in both the HLR and the HSS are updated to reflect the change to the supplementary service setting; and
receiving an Extensible Markup Language (XML) Configuration Access Protocol (XCAP) message containing a change to a supplementary service setting associated with a User Equipment (UE) connected to the IMS network, and communicating the change to the supplementary service setting via a synch server to both the HLR and the HSS so that the supplementary service settings in both the HLR and the HSS are updated to reflect the change to the supplementary service setting.
24. The method of claim 23 further comprising:
receiving the MAP message, via a first interface, related to the change to a supplementary service setting associated with a subscriber and the UE;
forwarding the received MAP message to the HLR;
receiving a response from the HLR indicative of successful supplementary service setting update in the HLR;
generating an Sh command related to the change to the supplementary service setting related to the subscriber in the received MAP message;
forwarding the Sh command to the HSS via a second interface; and
receiving a response from the HSS indicative of successful supplementary service setting update in the HSS.
25. The method of claim 23 further comprising:
receiving the XCAP message, via a third interface, related to a change to a supplementary service setting associated with a subscriber and the HE;
generating an Sh command related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forwarding the Sh command to the HSS via the second interface;
receiving a response from the HSS indicative of successful supplementary service setting update in the HSS;
generating a MAP message related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forwarding the MAP message to the HLR via the first interface; and
receiving a response from the HLR indicative of successful supplementary service setting update in the HLR.
26. The method of claim 23 further comprising receiving a MAP message related to a change to a supplementary service setting associated with an Any-Time-Modification (ATM) operation, transmit the change to the supplementary service setting in the form of an Sh command and transmit the change to the HSS, and in the form of a MAP message and transmit the change to the HLR.
27. The method of claim 23 further comprising:
receiving the MAP message, via a first interface, related to the change to a supplementary service setting associated with a subscriber and the UE;
forwarding the received MAP message to the HLR;
storing existing supplementary service setting in the HLR;
receiving a response from the HLR indicative of successful supplementary service setting update in the HLR;
generating an Sh command related to the change to the supplementary service setting related to the subscriber in the received MAP message;
forwarding the Sh command to the HSS via a second interface;
receiving a response from the HSS indicative of error in updating supplementary service setting in the HSS; and
restoring the existing supplementary service setting in the HLR.
28. The method of claim 23 further comprising:
receiving the MAP message, via a first interface, related to the change to a supplementary service setting associated with a subscriber and the UE;
forwarding the received MAP message to the HLR;
storing existing supplementary service setting in the HLR;
receiving a response from the HLR indicative of successful supplementary service setting update in the HLR;
generating an Sh command related to the change to the supplementary service setting related to the subscriber in the received MAP message;
forwarding the Sh command to the HSS via a second interface;
receiving a response from the HSS indicative of error in updating supplementary service setting in the HSS; and
logging HLR and HSS database misalignment.
29. The method of claim 23 further comprising:
receiving the XCAP message, via a third interface, related to a change to a supplementary service setting associated with a subscriber and the UE;
generating an Sh command related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forwarding the Sh command to the HSS via the second interface;
storing existing supplementary service setting in the HSS;
receiving a response from the HSS indicative of successful supplementary service setting update in the HSS;
generating a MAP message related to the change to the supplementary service setting related to the subscriber in the received XCAP message;
forwarding the MAP message to the HLR via the first interface;
receiving a response from the HLR indicative of error in updating supplementary service setting in the HLR; and
logging HLR and HSS database misalignment.