HSS Initiated User Profile Changes

The Oracle Communications Core Session Manager can receive Push Profile Request (PPR) messages from an HSS and update the state of the IMS User Profile and associated subscription information it has cached locally. The SIP digest authentication information can also be updated and reassociated with an AoR in case that has changed too. The Oracle Communications Core Session Manager expects to receive the following AVPs in a PPR message.

• Private-User-Identity—the username, whose subscription/authentication data has changed.
• SIP-Auth-Data-Item—if present new authentication data is included here.
• User-Data—if present new User data is included here.
• Charging-Information—if present new charging information is included here.

The Oracle Communications Core Session Manager replies to an HSS’s PPR in a PPA message with the following AVPs:

• Result-Code—indicates Diameter base protocol error. Valid errors for in a PPA are:
  • DIAMETER_SUCCESS—The request succeeded.
  • DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA—The request failed. The Oracle Communications Core Session Manager informs HSS that the received user information contained information, which was not recognized or supported.
  • DIAMETER_ERROR_USER_UNKNOWN—The request failed because the Private Identity is not found in Oracle Communications Core Session Manager.
  • DIAMETER_ERROR_TOO_MUCH_DATA—The request failed. The Oracle Communications Core Session Manager informs to the HSS that it tried to push too much data into the Oracle Communications Core Session Manager.
  • DIAMETER_UNABLE_TO_COMPLY—The request failed.
• Experimental-Result—indicates diameter application (3GPP/Cx) error if present.