Rhino Sentinel VoLTE delivers these services in an LTE/IMS network, following the GSMA IR.92 (v9.0) and IR.94 (v10.0) standards.

  • With the exception of Message Waiting Indication (MWI), all IR.92 services are supported within Sentinel VoLTE. Using Sentinel Create, it is possible to extend the feature set to very easily include other services.

  • Anonymous Call Rejection (ACR) is also supported, even though it is not an IR.92 service.


Below are details of GSMA required MMTel supplementary services that Rhino Sentinel VoLTE supports.

Originating Identification Presentation/Restriction (OIP/OIR) (3GPP TS 24.607)

The OIP service provides the terminating user with the possibility of receiving trusted (network-provided) identity information in order to identify the originating user.

The OIR service is a service offered to the originating user that restricts presentation of the originating user’s identity information to the terminating user. Both permanent and temporary modes are supported.

This service is implemented by the features:

Terminating Identification Presentation/Restriction (TIP/TIR) (3GPP TS 24.608)

The Terminating Identification Presentation (TIP) service provides the originating party with the possibility of receiving trusted information in order to identify the terminating party.

The Terminating Identification Restriction (TIR) is a service offered to the terminating party which enables the terminating party to prevent presentation of the terminating identity information to the originating party. Both permanent and temporary modes are supported.

This service is implemented be the features:

Communication Diversion (CDIV) (3GPP TS 24.604)

The Communications Diversion (CDIV) service enables the diverting user to divert the communications addressed to the diverting user to another destination. This includes the following services:

CDIV condition Service behaviour

CFU (Unconditional)

Unconditionally divert communications to a different destination.

CFB (Busy)

Divert communications to a different destination on busy. User-determined busy (UDUB) is supported.

CFNR (No Reply)

Divert communications to a different destination upon no reply. A timer is provided for configuration.

CFNRc (Not Reachable)

Divert communications to a different destination if the original destination is unreachable.

CD (Call Deflection)

Enables subscriber to divert incoming communications to a different destination.

CFNL (Not Logged In/Not Registered)

Divert communications to a different destination if the original destination is unregistered.

The CDIV service also checks and adds to the SIP history-info header as required, for example to determine if the diversion limit has been exceeded.

This service is implemented by the feature MMTelCDIV.

Communication Hold (HOLD) (3GPP TS 24.610)

The Communication Hold supplementary service enables a user to suspend the reception of media stream(s) of an established IP multimedia session, and resume the media stream(s) at a later time.

This service is implemented by the feature MMTelHold.

Communication Barring (CB) (3GPP 24.611)

The Communication Barring (CB) service offers the following services:

Service Behaviour

Incoming Communication Barring (ICB)

Rejects incoming communications that fulfil certain conditions.

Outgoing Communication Barring (OCB)

Rejects outgoing communications that fulfil certain conditions.

Anonymous Communication Rejection (ACR)

Specific case of ICB service, that allows barring of incoming communications from an anonymous originator.

The following conditions are supported:

Condition Result

All incoming

Barring of all incoming communications.

All outgoing

Barring of all outgoing communications.

All incoming when roaming

Barring of all incoming communications when subscriber is roaming outside the home network.

Outgoing International

Barring of all outgoing communications to international destinations.

Outgoing International-exHC

Barring of all outgoing communications to international destinations, except calls to the home country.

Anonymous

Barring of incoming communications when the originator is anonymous.

Media

Barring of communication using specific media.

These services are implemented by the features:

Operator Determined Barring (ODB) (3GPP TS 24.315 and TS 24.041)

The Operator Determined Barring (ODB) is not part of GSMA IR.92, but we include it here because it is related to barring conditions. ODB conditions are evaluated by the following services:

Service Behaviour

Incoming Communication Barring (ICB)

Rejects incoming communications that fulfil certain conditions, as specified by the operator.

Outgoing Communication Barring (OCB)

Rejects outgoing communications that fulfil certain conditions, as specified by the operator.

Explicit call transfer (ECT)

Prevent the ECT service from running for the served user.

Condition Result

Barring of All outgoing

Barring of all outgoing communications.

Barring of Outgoing International

Barring of all outgoing communications to international destinations.

Barring of Outgoing International-exHC

Barring of all outgoing communications to international destinations excluding home network.

Barring of Outgoing International when roaming

Barring of all outgoing communications roaming outside the home PLMN country.

Barring of All incoming

Barring of all international

Barring of Incoming International when roaming

Barring of all incoming communications roaming outside the home PLMN country.

Barring of Outgoing Premium Rate Communications Information

Barring of all information communications for subscribers under this category. [Note 1]

Barring of Outgoing Premium Rate Communications Entertainment

Barring of all entertainment communications for subscribers under this category. [Note 1]

Barring of Outgoing Premium Rate Calls Information When Roaming Outside HPLMN Country

Barring of all information communications for subscribers under this category when roaming. [Note 1]

Barring of Outgoing Premium Rate Calls Entertainment When Roaming Outside HPLMN Country

Barring of all entertainment communications for subscribers under this category when roaming. [Note 1]

Barring of Invocation of Communication Transfer

Barring of invocation of explicit communication transfer

Barring of Invocation of Communication Transfer where at least one Leg is charged

Not supported

Barring of Invocation of Communication Transfer where at least one Leg is charged at International Rates

Not supported

Barring of Invocation of Chargeable Communication Transfer

Not supported

Barring of Multiple Invocation of Communication Transfer

Barring of multiple invocation of communication transfer

Barring of Operator Specific Barring Type1

Barring of all calls when the operator defined rules type 1 applies. See Operator Specific Barring Rules

Barring of Operator Specific Barring Type2

Barring of all calls when the operator defined rules type 2 applies. See Operator Specific Barring Rules

Barring of Operator Specific Barring Type3

Barring of all calls when the operator defined rules type 3 applies. See Operator Specific Barring Rules

Barring of Operator Specific Barring Type4

Barring of all calls when the operator defined rules type 4 applies. See Operator Specific Barring Rules

Barring of Roaming outside the HPLMN

Not applicable to the AS. The AS has no procedure to avoid a subscriber from Roaming.

Barring of Roaming outside the HPLMN country

Not applicable to the AS. The AS has no procedure to avoid a subscriber from Roaming.

Barring of Registration of any communication diverted-to address

Not supported on the XCAP server

Barring of Registration of any International communication diverted-to address

Not supported on the XCAP server

Barring of Registration of any International communication diverted-to address Ex-HPLMNC

Not supported on the XCAP server

Barring of Supplementary Services Management

Not supported on the XCAP server

Note 1: The indication of a "Premium Rate Communications Information or Entertainment" is defined on TS 24.315 Release 12.1.0 on Section 3.1:

indication that this communication is a Premium Rate Communication: the Request-URI of the received INVITE request includes the " premium-rate" tel URI parameter set to either the value "information" or the value "entertainment".

For more information see Operator Determined Barring.

Explicit Communication Transfer (ECT) (3GPP TS24.629)

The Explicit Communication Transfer (ECT) service enables a transferor to transfer the call to a transfer target. The Explicit Call Transfer service uses 3PCC Call Transfer Procedures in case the transferee can not handle the transfer request. There is more discussion of this service in the Explicit Communication Transfer page.

This service is implemented by the feature MMTelECT.

Communication Waiting (CW) (3GPP TS24.615)

The Communication Waiting (CW) service enables a terminating party to be informed at the time that a new communication is requested. The user then has the choice of accepting, rejecting, or ignoring the incoming communication.

This feature is implemented by the feature MMTelCW.

Ad-hoc multi-party conference (CONF) (3GPP 24.605)

Sentinel VoLTE supports three party conferencing (3PTY) as part of this service. The following operations are supported:

Supported Operations Notes

Conference Creation

By sending a SIP INVITE to the conference-factory URI, which is Sentinel VoLTE.

Invite users to the conference

Via a SIP REFER request.

Remove user from conference

Only the conference creator can remove participants from the call.

Terminate conference

The conference is terminated when the conference creator has left the call, or if the conference creator is the only party left in the conference.

Subscribe

Conference users can subscribe to the conference-event package for the information specified in IR.92.

This service is implemented by the features:

Anonymous Call Rejection (ACR) (3GPP TS24.611)

XCAP interface (Ut)

Sentinel VoLTE supports the XCAP interface over the Ut reference point between the UE and MMTEL-AS, as per 3GPP TS24.623.

For more information please refer to the XCAP Support section. For information on the Authorization Proxy please refer to Sentinel Authentication Gateway.

Previous page Next page