Proposed solution for improving the reliability of HSS data by integrating a queue manager

摘要

The current trend is towards rich communications services (RCS). SCRs define a set of services that network operators can provide through the IMS architecture, including voice and video calls, instant messaging, and so on. Indeed, the IMS is considered today as the base to provide the new services and to converge all the existing means of communication. The IMS has a central element called HSS. HSS is a database that stores user-specific data, access settings, service invocation rules, and billing data. However, it is important that the authentication information exchange mechanisms based on the DIAMETER protocol are clear, since a malfunction can negatively impact the quality of service (QoS) and the profits of the operators. Moreover, it should be noted that a lot of research work around VoLTE has been conducted in recent years with free software implementing the IMS core network, like SER platforms such as: OpenIMSCore and KAMAILIO. Otherwise, various tests were carried out with the KAMAILIO platform coupled with the openIMSCore HSS to build an IMS core network. During these tests, various observations are made on the analysis of the registration messages, following which two problems were identified: - The HSS entity displays on its interface the "connected status" of the users, while the latter cannot connect; - When a user who is logged out leaves his / her session, the HSS entity does not display on its interface that the user is disconnected. Finally, this paper aims to highlight the dysfunction observed during registration message exchanges and to propose a solution to improve the reliability of the HSS data by integrating a queue manager. This handler will interact between the I-CSCF, S-CSCF and HSS entities so that when transferring or downloading the user's profile, the HSS entity does not display that the user is logged in without having the confirmation the S-CSCF entity that its profile is stored in the location table (called location) to then trigger the sending of the "SIP 200 OK" notifying the user that it is registered.