Wildcarded PUID Support

The Oracle Communications Unified Session Manager supports the use of wildcarded Public User IDs (PUIDs), typically for registering multiple endpoints on a PBX with a single PUID. A wildcard is composed of a regular expression that, when used in a PUID prefix, represents multiple UEs. The group of UEs is referred to as an implicit registration set and share a single service profile. This support is typically implemented to reduce HSS resource requirements. The regular expressions themselves are in form of Perl Compatible Extended Regular Expressions (PCRE).

Each implicit registration set is associated with an explicitly registered distinct PUID. Typically, this distinct PUID is the PBX itself. The implicit registration set is dependent on the distinct PUID, including the distinct PUID’s registration status.

There is no Oracle Communications Unified Session Manager configuration required.

Wildcarded PUID support is applicable to both I-CSCF and S-CSCF operation. In addition, all Oracle Communications Unified Session Managers in the applicable data paths must be in the same trust domain.

To allow the feature, the Oracle Communications Unified Session Manager supports:

• Wildcarded PUID AVP in the LIR, SAR and SAA
• User Profile AVP in the SAA
• P-Profile-Key across the Mw interface, as defined in RFC 5002

Note also that the HSS must support the wildcarded-public-Identify AVP.