The XCAP Server is a software component that runs inside a web application called Rhino Element Manager (or REM for short).

It uses OpenCloud’s Diameter Sh stack to communicate with the HSS.

Note For information on this piece of the Sentinel VoLTE product architecture, please see XCAP Support.

Diameter Sh configuration

The Diameter Sh stack must be configured before running the XCAP server functioning. See Configuring Diameter Sh for the XCAP server and REM.

HTTP configuration

The XCAP Server runs inside an HTTP servlet container. To configure it, please see that container’s documentation.

XCAP simservs configuration

The XCAP simservs configuration defines how an XML simservs document (typically coming from a UE) is mapped into an MMTel services document (stored in transparent data in the HSS).

A tool is available that will populate XCAP server settings with MMTel service data mappings The rest of this section describes how to manually configure those same settings.

This configuration is defined using XPath:

1

Select Sentinel ▶ XCAP — Simservs.

The resulting panel differs depending on whether a configuration has already been entered for the selected network operator.

Not yet configured

This occurs if (for example) a new network operator has been created and selected. In the following image, a network operator called TestOperator has been created and is selected.

xcap simservs mapping unconfigured operator

Configured

In this case, no network operator is selected, so the default platform configuration is displayed, for which Simservs mappings have already been configured.

xcap simservs mapping configured operator

2

For an existing configuration, to enter sufficient XCAP Simservs mappings for IR.92:

  • Click the + Add New button.

  • Click the + Add Mapping Group button.

A popup prompts you to enter details.

new simservs mapping group
  • Enter the following details.

Note You can enter the defaults in a selected text box by pressing the “down arrow” key (↓).
Field Name Required value for IR.92

Service indication

MMTEL-Services

Service data class

com.opencloud.volte.sentinel.simservs.xcap.TMMTelServicesType

Service data codec class

com.opencloud.volte.sentinel.provisioning.hss.TMMTelServicesCodec

JXPath factory class

com.opencloud.volte.sentinel.simservs.xcap.MMTelJXPathFactory

3

With the mapping group created, add mappings:

  • Click the + Add Mapping button.

A prompt displays to enter the mapping.

add mapping
  • Enter the Simservs Path and HSS Document Path.

  • Click the Save button.

Enter these defaults:

Simservs Path HSS Document Path
originating-identity-presentation
complete-originating-identity-presentation/originating-identity-presentation
originating-identity-presentation-restriction
complete-originating-identity-restriction/originating-identity-presentation-restriction
communication-diversion
complete-communication-diversion/communication-diversion
communication-waiting
complete-communication-waiting/communication-waiting
terminating-identity-presentation
complete-terminating-identity-presentation/terminating-identity-presentation
terminating-identity-presentation-restriction
complete-terminating-identity-restriction/terminating-identity-presentation-restriction
incoming-communication-barring
complete-communication-barring/incoming-communication-barring
outgoing-communication-barring
complete-communication-barring/outgoing-communication-barring

XCAP simservs extensions mappings

The XCAP server also supports simservs extensions mappings. This allows arbitrary elements of any transparent user data XML document from the HSS to be mapped to an element in the simservs document under the extensions parent element.

Examples:

Simservs Path HSS Document Path
extensions/operator-flexible-alerting
complete-flexible-alerting/operator-flexible-alerting
extensions/operator-flexible-alerting-group
complete-flexible-alerting/operator-flexible-alerting-group

In these examples, select parts of operator data from the MMTel services document are being exposed to the UE for viewing and updating via XCAP as part of the Simservs document. Each can be specifically accessed via the simservs XCAP URL with the node selector specified as per the simservs path in the mapping.

Rules for creating extensions mappings

  • An extension simservs path must start with extensions/.

  • The element name after extensions/ can be any alphanumeric string. Special characters are not allowed.

  • The element name must be singular. e.g. extensions/path1 is ok, but extensions/path1/path2 is not.

  • The HSS document path has to match an actual location in the HSS data.

  • Only simple element names can be used for the HSS Document Path. i.e. no positional or attribute selectors.

Note Extensions mappings have to be created in the MMTEL-Services Mapping Group, alongside the standard MMTel mappings.

XCAP host mappings

The XCAP server may be configured to function on behalf of multiple network operators, by using host mappings. Host mappings take the ‘host’ part of an HTTP URI (in other words, XCAP query URI) and treat it as a key.

This key then identifies the:

  • Rhino cluster in REM to communicate with

  • the Sentinel network operator to use for XCAP queries.

The Sentinel network operator determines various key AVPs that are required when communicating via the diameter Sh interface.

To navigate and view XCAP host mappings:

1

In REM, select Sentinel ▶ XCAP.

xcap host mappings

2

To view a mapping in more detail, select it in the panel at left. The example shows a single host mapping, for localhost.

xcap host mappings drilldown
Note

This configuration means that when the XCAP server receives a request, if the ‘host’ part of the HTTP request URI matches the value localhost, then:

  • The selected Rhino cluster is called Local.
    This is REM’s view of the Rhino cluster (when configuring a cluster to communicate within REM, the administratpor assigns it a name).

  • The network operator is null.
    This means Sentinel’s default network operator will be chosen.

  • The REM user account is emadm.

XCAP authentication

In the absence of an Authentication Proxy (AP), the XCAP server can be configured to authenticate requests itself using OpenCloud Sentinel AGW. Sentinel AGW provides an implementation of 3GPP GAA (Generic Authentication Architecture) procedures.

For more information, and instructions on configuring the XCAP Server with Sentinel AGW, see the Sentinel AGW Guide.

Example XCAP query

The following XCAP query requests subscriber configuration data for incoming-communication-barring.

The subscriber in question is identified by the IMS public identity sip:user222222@home1.net.

http://localhost:8090/rem/sentinel/xcap/simservs.ngn.etsi.org/users/sip:user222222@home1.net/simservs/~~/incoming-communication-barring

In this example query, the host part of the URI is localhost. The XCAP server will look for a configuration keyed on the host value (localhost).

Previous page Next page
Sentinel VoLTE Version 2.7.0