Supplementary Services Management in IMS
Supplementary service settings are typically stored as an XML document called the simservs document. The document may be stored and managed by an IMS Application Server (AS), such as the Telephony Application Server (TAS), or in an XML Document Management Server (XDMS).This document contains authorization rules that define how SIP requests should be handled to provide supplementary services to the user. Each rule consists of conditions and associated actions. The conditions specify the criteria under which a rule is applied, for example when a called user does not answer. The associated action defines how the AS should respond, such as forwarding the incoming session to voicemail.
Supplementary service management allows users to configure and manage IMS supplementary services. Users can create, modify, retrieve, or delete simservs documents using the XML Configuration Access Protocol (XCAP). XCAP uses the Hypertext Transfer Protocol (HTTP) to access and manage XML-based configuration data. The supported operations include create and modify using HTTP PUT, retrieve using HTTP GET, and delete using HTTP DELETE. These operations may target the entire XML document, a specific XML element, or an individual XML attribute. Applications using XCAP define an XCAP Application Usage ID (AUID), which specifies how a particular application uses XCAP and defines the structure of the associated XML document, such as simservs.
Several supplementary services can be configured with XCAP. GSMA IR.92 document includes CDIV and communication barring which are configurable using XCAP.
Communication Diversion
Communication Diversion services use rule-based authorization policies defined in the simservs document. Each rule contains one or more conditions and an associated forwarding action. The conditions specify the circumstances under which an incoming session should be diverted. Examples of such conditions include: the called user is busy, the called user is not registered, the called user does not answer, the called user is unreachable, time-based conditions, offered media type, identities derived from external lists, and identities that do not match any existing rule.
When the configured condition or set of conditions evaluate to true, the associated action forwards the session to a specified destination. Examples include forwarding call to a voice mail box when the user does not answer a call.
Communication Barring Services
Communication Barring services use rule-based authorization policies defined in the simservs document. Each rule contains one or more conditions and an associated barring action. The conditions specify the circumstances under which incoming or outgoing communication sessions should be restricted. Examples of such conditions include: the identity of the calling user, the identity of the called user, identities derived from external lists, identities that do not match any existing rule, anonymous callers, offered media type, , time-based conditions, diverted sessions, roaming status, calls to other countries.
When all conditions defined in a rule evaluate to true, the associated barring action is applied to the communication session.