6 NGN PSTN/ISDN simulation services XCAP application usage

24.4233GPPExtensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating NGN PSTN/ISDN Simulation ServicesPSTN/ISDN simulation servicesRelease 8TISPANTS

6.1 Structure of the XML document

XCAP provides for the existence of application usages that define the conventions and constrains related to the manipulation of XML documents in an XCAP server. The present document defines an NGN PSTN/ISDN simulation services XCAP application usage. This application usage is common for a variety of PSTN/ISDN simulation services defined by NGN Release 1. Further releases may extend this application usage when deemed practical.

The present document follows a modular approach, as depicted in figure 4. We provide for the existence of a simservs XML document that contains the data associated to one or more NGN PSTN/ISDN simulation services. The simservs XML document is composed of a common part, defined by the present document, and a number of XML fragments corresponding to each of the NGN PSTN/ISDN simulation services. This modular approach has significant advantages. Particularly, it is versatile enough to allow any number of configurations. For example, in one configuration, an XCAP server might be managing a given server. In this case, the simservs XML document will contain one subtree per service. In another configuration, each service is managed in its own XCAP server, case in which the XML document in each XCAP server will contain the common parts and a single XML subtree that manages the service. Yet in a third configuration the XCAP server stores several XML documents, each document managing one or more services.

The XML schema for the simservs XML document, including the common parts, is specified in clause 6.3. This XML schema allows for each of the individual XML schemas pertaining to a particular service to import the common parts XML schema. Each XML fragment affects the settings of a PSTN/ISDN simulation service (or group of related PSTN/ISDN simulation services). The XML schema of each of the PSTN/ISDN simulation services is specified in its own specification. A template of the XML schema for a PSTN/ISDN simulation service is provided in clause 6.4.

Figure 4: Structure of an NGN PSTN/ISDN simulation services XML document

The simservs XML document starts with a <simservs> root XML element that can contain one or more child elements pertaining to PSTN/ISDN simulation services. Each of these service elements can contain an "active" attribute that indicates whether the service is activated or not. When the "active" attribute is absent on a service element, it indicates that the service is activated. Elements and attributes from different namespaces can be present as well.

6.2 XCAP application usage

XCAP requires application usages to fulfil a number of steps in the definition of such application usage. The reminder of this clause specifies the required definitions of the NGN PSTN/ISDN simulation services XCAP Application Usage.

Application Unique ID (AUID): Each XCAP application usage is associated with a unique name called the Application Unique ID (AUID). The AUID defined by this application usage falls into the vendor‑proprietary namespace of XCAP AUID, where ETSI is considered a vendor.

The AUID allocated to the NGN PSTN/ISDN simulation services XCAP application usage is:

simservs.ngn.etsi.org

XML schema: Implementations in compliance with the present document shall implement the XML schema that includes the XML Schema defined in clause 6.3. Additionally, each PSTN/ISDN simulation service (or group of them) is modelled with a XML fragment that is validated according to a specific XML schema. The XML schema that affects the settings of the related service is specified in the specification of the given PSTN/ISDN simulation service. Clause 6.4 provides a template that shall be included in XML Schema that also includes the XML Schema defined in clause 6.3 along with inclusion of XML schema defined by each of the PSTN/ISDN simulation services that implement XML schemas for data manipulation. Additionally the schema in clause 6.3 contains the specification of a number of common service specific elements and types, the semantics and applicability of these elements is described in the service specifications that use them.

Default namespace: XCAP requires application usages to declare the default namespace. The default namespace of the NGN PSTN/ISDN simulation services XCAP application usage is:

http://uri.etsi.org/ngn/params/xml/simservs/xcap

MIME type: The MIME type of NGN PSTN/ISDN simulation services XML documents is:

application/vnd.etsi.simservs+xml

Validation constraints: The present document does not specify any additional constraint beyond those defined by XCAP [8]. Note, however, that each of the supplementary services may specify additional constraints on each of the XML subdocuments.

Data semantics: The XML schema does not accept URIs that could be expressed as a relative URI reference causing a resolution problem. However, each of the supplementary services should consider if relative URIs are allowed in the subdocument tree, and in that case, they should indicate how to resolve relative URI references. In the absence of further indications, relative URI references should be resolved using the document URI as the base of the relative URI reference.

Naming conventions: By default, NGN PSTN/ISDN simulation services XML documents are stored under the user’s Home Directory (which is located under the "users" sub‑tree). In order to facilitate the manipulation of an NGN PSTN/ISDN simulation services XML document, we define a default XML file name:

simservs.xml

Resource interdependencies: The present document does not specify additional resource interdependency beyond those specified in the XML schema and beyond any resource interdependency that may be specified in each of the NGN PSTN/ISDN simulation services.

Authorization policies: The default XCAP [8] authorization policy is used in the application usage defined by the present document.

NOTE: The default policy indicates that the creator of the XML document is the one authorized to manipulate it.

6.3 XML schema

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema targetNamespace="http://uri.etsi.org/ngn/params/xml/simservs/xcap"

xmlns:ss="http://uri.etsi.org/ngn/params/xml/simservs/xcap"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified"

attributeFormDefault="unqualified">

<!– The element "simservs" maps to the Common Parts of an NGN PSTN/ISDN Simulation services document –>

<xs:element name="simservs">

<xs:annotation>

<xs:documentation>XML Schema for data manipulation of ETSI

NGN PSTN/ISDN Simulation Services

</xs:documentation>

</xs:annotation>

<xs:complexType>

<xs:sequence>

<xs:element ref="ss:absService" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="extensions" minOccurs="0">

<xs:complexType>

<xs:sequence>

<xs:any namespace="##other" processContents="lax"

minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

</xs:element>

<xs:element name="absService" abstract="true" type="ss:simservType"/>

<xs:complexType name="simservType">

<xs:attribute name="active" type="xs:boolean"

use="optional" default="true" />

<xs:anyAttribute namespace="##any" processContents="lax"/>

</xs:complexType>

<!– service specific IETF common policy condition elements–>

<xs:element name="anonymous" type="ss:empty-element-type"/>

<xs:element name="presence-status" type="ss:presence-status-activity-type"/>

<xs:element name="media" type="ss:media-type"/>

<xs:element name="communication-diverted" type="ss:empty-element-type"/>

<xs:element name="rule-deactivated" type="ss:empty-element-type"/>

<xs:element name="not-registered" type="ss:empty-element-type"/>

<xs:element name="busy" type="ss:empty-element-type"/>

<xs:element name="no-answer" type="ss:empty-element-type"/>

<xs:element name="not-reachable" type="ss:empty-element-type"/>

<xs:element name="roaming" type="ss:empty-element-type"/>

<!– service specific type declarations –>

<xs:simpleType name="media-type" final="list restriction">

<xs:restriction base="xs:string"/>

</xs:simpleType>

<xs:simpleType name="presence-status-activity-type" final="list restriction">

<xs:restriction base="xs:string"/>

</xs:simpleType>

<xs:complexType name="empty-element-type"/>

</xs:schema>

6.4 Template for a PSTN/ISDN simulation service XML schema

PSTN/ISDN simulation services that implement XCAP operations to manipulate the data associated to its service shall base their XML schema in the following template. Replace "ServiceName" with the name or acronym of the actual service.

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema targetNamespace="http://uri.etsi.org/ngn/params/xml/simservs/xcap" xmlns:ss="http://uri.etsi.org/ngn/params/xml/simservs/xcap" xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified"

attributeFormDefault="unqualified">

<xs:element name="ServiceName" substitutionGroup="ss:absService">

<xs:annotation>

<xs:documentation>Template of a PSTN/ISDN Simulation

Service XML Schema

</xs:documentation>

</xs:annotation>

<!– If the service needs to add children elements or attributes –>

<!– it can use the following complexType for such purpose –>

<xs:complexType>

<xs:complexContent>

<xs:extension base="ss:simservType">

<xs:sequence>

<!– service specific elements can be defined here –>

</xs:sequence>

<!– service specific attributes can be defined here –>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:element>

</xs:schema>

Annex A (informative):
Bibliography

  • ETSI TS 187 001: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); NGN SECurity (SEC); Requirements".

Annex B (normative):
Connectivity Aspects when using XCAP