Example Oracle Communications Universal User Profile Use Cases and Deployment Scenarios

Oracle Communications Universal User Profile 20-5 3. Go to the Plug-ins tab for the new Diameter adapter. Select DiameterAdapterPlugin and click the Edit button. The Edit Plug-in: DiameterAdapterPlugin dialog box appears.

4. Add the following configuration parameters Name: Value to the Parameters

table by selecting a parameter and clicking the Edit button. The remoterealm and remotePeers parameters are required. ■ interface : The type of Diameter interface used to connect to HSS. The default value is Sh. ■ listener : The hostname of the Oracle Communications Universal User Profile server and the port to listen on to receive messages from the HSS server, which is a requirement of the HSS protocol. The listener value must be in the form of aaa:host:port, for example aaa:ovd.oracle.com:3689. The port must be accessible through the firewall from the HSS server. 3869 is the default port for HSS client listener ports. ■ nosctp : Determines whether to disable SCTP transport. Supported values are true and false. The default setting is true. ■ localrealm : The realm of this custom Diameter adapter and can be any valid value for the HSS server. The default is us.oracle.com. The localrealm parameter is used as a key to map records for Oracle Communications Universal User Profile to the HSS server. ■ remoterealm required: Supplied by the HSS provider, it is the remoterealm value for the HSS server. ■ remotePeers required: The remotePeers value is the hostname and port to the HSS server. Both values are provided by the HSS server. The remotePeers value must be in the format of aaa:host:port, for example, aaa:hss.oracle.com:3868. The default port is 3868. Note: Currently, Sh is the only supported value for the interface configuration parameter. Notes: ■ The aaa string in the listener value is not a replaceable variable—it must be explicitly included. ■ Do not confuse the listener parameter for an Oracle Virtual Directory listener. Note: Refer to Enabling SCTP Transport for more information about using the nosctp option and enabling SCTP Transport. Note: Multiple values can be specified by separating each with the semicolon character ;. For example, aaa:127.0.0.1:3868; aaa:different-host:3939. 20-6 Oracle Fusion Middleware Administrators Guide for Oracle Virtual Directory ■ remoteHost : Hostname of the remote HSS server. The default value is 127.0.0.1. ■ connectionWaitTimeout : The amount of time in milliseconds for the HSS service to be available while the adapter starts. The default value is 30000. ■ requestTimeout : The maximum waiting time in milliseconds for pending HSS transactions to complete. An empty value indicates no timeout. The default value is 5000. 5. Click the Finish button on the Edit Plug-in: DiameterAdapterPlugin dialog box.

20.3.2.1 Enabling SCTP Transport

The Diameter Adapter supports SCTP Transport only on Solaris SPARC10 and Linux. Perform the following steps to enable SCTP transport for the Diameter Adapter:

1. Enable SCTP on the server where Oracle Communications Universal User Profile

is running.

2. In Linux and Solaris SPARC 10 environments only, in the ORACLE_

INSTANCEconfigOPMNopmnopmn.xml file, update LD_LIB_PATH by adding the following to the end of the java-options property for the Oracle Virtual Directory server entry: ■ For Linux, add the following as one line: -Djava.library.path=ORACLE_ HOMEovddiameternativelinux32libsctpwrapper.so ■ For Solaris SPARC10, add the following as one line: -Djava.library.path=ORACLE_HOMEovddiameternativesolaris10_ sparc64libsctpwrapper.so

3. Add the following to the end of the java-classpath property for the same

Oracle Virtual Directory server entry in the ORACLE_ INSTANCEconfigOPMNopmnopmn.xml file: :ORACLE_HOMEovddiameterlibsctp.jar

4. Set the Diameter Adapter’s nosctp configuration parameter to false.

5. Set the Diameter Adapter’s listener configuration parameter to the fully qualified

domain name of the Oracle Communications Universal User Profile server.

6. Set the Diameter Adapter’s remotePeers configuration parameter to the fully

qualified domain name and port of the HSS server.

7. Set the Diameter Adapter’s remoteHost configuration parameter to the fully

qualified domain name of the HSS server. 8. Restart the Oracle Communications Universal User Profile server.

20.4 Mapping IMS 3GPP Schema to LDAP Schema

Oracle Communications Universal User Profile supports version 6 Sh user profile as defined in the 3GPP TS 29.328 specification which Oracle recommends becoming familiar with to understand IMS user profiles. schema.diameter.xml is the Oracle Communications Universal User Profile mapped LDAP schema and defines an LDAP orclHSSProfile objectclass containing the following attributes: Oracle Communications Universal User Profile 20-7 ■ orclHSSPublicId: Maps to the Public User Identity IMS user profile as defined in the 3GPP TS 23.008 specification. orclHSSPublicId is the filter attribute typically used to query the HSS Sh profile. ■ orclHSSServiceProfile: In ldapsearch results orclHSSServiceProfile contains the binary value of the XML document contained in the User-Data attribute-value pair of the Diameter Response message. This XML document conforms to version 6 Sh XSD. In ldapmodify requests orclHSSServiceProfile contains the RepositoryData serviceIndicator to be updated in the following format: serviceIndicator:serviceIndicator_value ■ orclHSSMSISDN: An alternative to orclHSSPublicId, orclHSSMSISDN maps to the Mobile Station ISDN Number as defined in the 3GPP TS23.008 specification. Example Entry Generally, the Diameter data can be linked to a core record by using the Join View adapter. For example, the subscribers core record exists in the billing database but the phones actual capabilities are stored in the HSS server. The following is an example of what the data may appear like when retrieved and printed out as an LDIF file: uid=user1,ou=uup2,dc=imc,dc=com givenname=Jane sn=Doe telephonenumber=15551234567 objectclass=top objectclass=person objectclass=organizationalperson objectclass=inetorgperson objectclass=orclHSSProfile uid=user1 cn=Jane Doe title=Associate authpassword;oid={SASLMD5}CPvyoxkufZJ69n0YBwfPsw== authpassword;oid={SASLMD5-DN}JnDX4y0mf8vdN1dAHVutDw== authpassword;oid={SASLMD5-U}a3vgMwtjQKe8dEcAdxQwQ== orclHSSPublicId=user1 orclHSSServiceProfile=?xml version = 1.0 encoding = UTF-8? Sh-Data RepositoryData PublicIdentifiers IMSPublicIdentity sip:test.usertest.company.com IMSPublicIdentity PublicIdentifiers ServiceIndicationDualRingDiameterServiceIndication SequenceNumber0SequenceNumber RepositoryData Sh-Data vdejoindn=Diameter:orclhsspublicid=user1,ou=Custom,dc=hsscontractid=2001-A57 Note: Notice the orclHSSServiceProfile attribute value is stored as XML, which allows for a complex data value to be stored for this attribute without needing to reference another LDAP object.