1、 Access to Additional Content for ECMA-323 6thEdition, Dated: December 2011 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyri
2、ght holder of this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. ECMA-323 Extra Files Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer andb. satisfy the definitions, as spe
3、cified in ECMA-269, relevant to each CSTA service that the system claimsto implement.2.3 PICS RequirementTo conform to this Standard, the following shall be stated by the implementer when defining a PICScorresponding to an application or implementation:a. which CSTA operations, as defined in ECMA-26
4、9, are supported by the system for the particularimplementation; andb. which optional parameters are supported by each supported operations.A PICS proforma is specified in Annex A of this Standard.2.4 XML Tag OptionsTo conform to this Standard, a system shall support at least one of the XML tag opti
5、ons listed below. 2 Ecma International 20112.4.1 ECMA-323 Specified TagsInstance documents shall include the following URI for the namespace and conform to the schemas asspecified in Clause 9 through 27 of this Standard without transformations.http:/www.ecma-international.org/standards/ecma-323/csta
6、/ed62.4.2 ECMA-323 Specified Short TagsInstance documents shall include the following URI for the namespace and conform to the schemas asspecified in Clause 9 through 27 of this Standard with transformations as specified in Annex D.url: www.ecma-international.org/standards/ecma-323/csta/ed6/short_ta
7、gs2.4.3 Dynamic TransformationsImplementation claiming conformance to this option shall support XML schema transformations e.g. usingfor the schemas specified in Clause 9 through 27.2.5 CSTA Over SIP (uaCSTA) Transport Mechanism OptionAn implementation that conforms to ECMA-323 can also claim confor
8、mance to the “CSTA Over SIP (uaCSTATransport Mechanism Option” by implementing the SIP and CSTA procedures specified in Annex C.3 References3.1 ECMA/ISO Standards and Technical ReportsECMA-269 Services for Computer Supported Telecommunications Applications (CSTA) PhaseIII, 9thedition (December 2011)
9、ECMA-285 Protocol for Computer Supported Telecommunications Applications (CSTA) PhaseIII, 4thedition (December 2011)ECMA-354 Application Session Services (June 2004)ECMA TR/72 Glossary of Definitions and Terminology for Computer SupportedTelecommunications Applications (CSTA) Phase III, 3rdedition (
10、June 2000)ISO/IEC 8649:1996 Information technology - Open Systems Interconnection - Service definition for theAssociation Control Service Element (this corresponds to ITU-T Rec. X.217 1995)3.2 World Wide Web Consortium SpecificationsXML 1.0 XML 1.0. W3C Recommendation February 1998 (revised October
11、2000)XML Schema Part 1 XML Schema Language Part 1: Structures. W3C Recommendation 2 May 2001XML Schema Part 2 XML Schema Language Part 2: Datatypes. W3C Recommendation 2 May 2001SOAP 1.1 Simple Object Access Protocol (SOAP) 1.1, W3C Note 08 May 20004 Definitions and AbbreviationsCSTA-specific termin
12、ology is defined in ECMA TR/72. Ecma International 2011 35 CSTA Service Definition ModelCSTA services specified in ECMA-269 are modeled as a request/response interaction.Typically, one entity requests that a particular operation be performed; the other entity attempts to perform theoperation and res
13、ponds to the requestor.5.1 Request/Response InteractionsCSTA services consist of the following types of request/response interactions: Services which specify a response in case of success or failure. The protocol description for these servicesincludes a response element that represents the success (
14、i.e. positive acknowledgement). In case ofservice failure, a fault element is used to provide the failure information (i.e. negative acknowledgement). Services which only specify a response in case of failure. The protocol description for these services do notinclude a response element. A fault elem
15、ent is used to provide the failure information (i.e. negativeacknowledgement).For CSTA event reports, no response is generated.5.2 Request/Response Protocol RequirementsThis Standard specifies CSTA-specific XML-encoded content for messages that are sent across a CSTAService boundary. Typically this
16、CSTA-specific XML is enveloped by a request/response protocol that providesa mechanism for correlating a CSTA request with a CSTA response, manages faults, defines headerinformation, etc.This Standard does not mandate that a specific request/response protocol be used. However, this Standardprovides
17、examples of how the CSTA-specific XML can be used with several industry request/responseprotocols and transports such as SOAP (Simple Object Access Protocol), HTTP, and TCP. These examplesare provided beginning in Annex H.5.3 Cross Referencing of Event ReportsThe Monitor Cross Reference Identifier i
18、n CSTA event reports is used to correlate events to an earlier MonitorStart service request (see 6.7.2.1 of ECMA-269).5.4 Handling of Private Data If an entity receives CSTA Private Data in a CSTA message, and it can not recognize the informationcontained, the CSTA Private Data shall be discarded, a
19、nd the rest of the message shall be processed.6 Interconnection service boundaryThe protocol in this Standard is an OSI Application Layer protocol that assumes certain services are providedby the underlying layers, and these services are also assumed by the protocol for CSTA.This protocol also provi
20、des a mechanism for secure transmission of CSTA messages as defined in thisStandard.7 Association ManagementThe protocol in this Standard operates in the context of an application association as specifed in ECMA-269Clause 7. This application association can be achieved by: an implicit association ac
21、hieved via off-line agreement; or4 Ecma International 2011 an explicit association that is achieved dynamically.7.1 Implicit associationAn a-priori agreement exists between switching and computing functions: the application context is implicit,dynamic negotiation is not possible. See ECMA-269 7.1 an
22、d 7.2 for more information.7.2 Explicit associationAn explicit application association is established by a process of exchanging messages that define theapplication context for the association.This Standard does not require that a particular standard be used as part of the application associationest
23、ablishment procedure. When ACSE (ISO/IEC 8649) is used to establish an application association per 7.3 of ECMA-269, the CSTAAssociation Information includes CSTA Version information that indicates the CSTA protocol versionssupported by an implementation. The protocol defined in this Standard is indi
24、cated by setting the following bit in the CSTAVersion parameter ofthe CSTA Association Information as defined in 8.2.2 of ECMA-285. versionSixteen when using the ECMA-323 Specified Tag option (see section 2.4.1) versionSeventeen when using the ECMA-323 Specified Short Tag option (see section 2.4.2)
25、versionEighteen when using the Dynamic Transformation option (see section 2.4.3)Note that the ACSE messages are ASN.1 encoded while the CSTA messages are XML encoded as definedby this Standard.ECMA-354, Application Session Services can also be used to establish an application association per 7.4 ofE
26、CMA-269. When this Standard is used with ECMA-354 the following namespace is provided in therequestedProtocolVersions element of the Start Application Session service: http:/www.ecma-international.org/standards/ecma-323/csta/ed6 when using the ECMA-323 Specified Tagoption (see section 2.4.1) urn:www
27、.ecma-international.org/standards/ecma-323/csta/ed6/short_tags when using the ECMA-323Specified Short Tag option (see section 2.4.2) http:/www.ecma-international.org/standards/ecma-323/csta/ed6/dynamic_transformations when using theDynamic Transformation option (see section 2.4.3)8 XML Template Desc
28、riptionThis Clause describes the template format used to describe the XML schemas for CSTA services, events, andparameter types as specified in ECMA-269.The template consists of the following parts: XML header - this consists of the text “” which identifies the XMLversion used. XML Schema header - t
29、his identifies the start of an XML schema and provides information such as: the target namespace. In this edition of the Standard the target namespace is defined as “http:/www.ecma-international.org/standards/ecma-323/csta/ed6”. Note that this URI uniquely identifies the namespace for the 6thEdition
30、 of ECMA-323. Ecma International 2011 5 the csta namespace is the same as the target namespace. XML names that refer to names in the CSTAnamespace are prefixed with “csta:”. the xsd namespace. This identifies the XML Schema. XML names that refer to names in the XMLSchema namespace are prefixed with
31、“xsd:”. the element form default is specified as “qualified” which requires that all element names must beprefixed with a namespace (csta: or xsd:) documentation - this provides a comment that indicates the CSTA specific service, event report, or data-type set. included schemas - this provides a lis
32、t of other CSTA schemas that are referenced by the service, event, ordata type set. CSTA specific XML: for CSTA services, this consists of a service request element and a service response element. (Acomment is provided in some cases where a service response is not specified per ECMA-269.). This isfo
33、llowed, in some cases, by service-specific XML types that are referenced in the previous elements. for CSTA event reports, this consists of an event report element followed, in some cases, by event-specific XML type definitions that are referenced in the event report element. for CSTA data types, th
34、is consists of the data types that are referenced (included) by other CSTA XMLschemas. XML Schema end tag - indicates the end of the schema.Note that in general, each parameter defined in ECMA-269 is represented as an XML element and eachparameter type in ECMA-269 is represented as an XML simple or
35、complex type.6 Ecma International 20119 CSTA parameter types9.1 Switching function objectsCSTA-switching-function-objects Ecma International 2011 79.2 Device IdentifiersCSTA-device-identifiers8 Ecma International 2011uses flattened structure Ecma International 2011 910 Ecma International 2011 Ecma I
36、nternational 2011 119.3 Call and connection identifiersCSTA-call-connection-identifiersuses flattened structure - all types included here12 Ecma International 2011 Ecma International 2011 139.4 Connection statesCSTA-connection-states14 Ecma International 20119.5 Status reportingCSTA-status-reporting Ecma International 2011 1516 Ecma International 2011 Ecma International 2011 1718 Ecma International 2011 Ecma International 2011 19
