1、 ETSI ES 201 873-11 V4.7.1 (2017-06) Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 11: Using JSON with TTCN-3 ETSI STANDARD ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)2 Reference DES/MTS-00201873-11ed471JSON Keywords JSON, language, testing, TTCN-3 E
2、TSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: htt
3、p:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived
4、difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision o
5、r change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSup
6、portStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authori
7、zation of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the b
8、enefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)3 Contents Intellectual Property Rights 5g3Foreword . 5g3Mo
9、dal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references 6g32.2 Informative references . 6g33 Definitions and abbreviations . 7g33.1 Definitions . 7g33.2 Abbreviations 7g34 Introduction 8g35 Conformance and compatibility . 8g36 Using TTCN-3 as JSON Schema . 9g36.1 Approach . 9g36
10、.2 Validation of JSON Values . 9g36.3 Name conversion rules 9g36.4 Mapping of JSON Values 10g36.4.1 JSON Numbers 10g36.4.2 JSON Strings . 11g36.4.3 JSON Arrays 12g36.4.4 JSON Objects. 14g36.4.5 JSON Literals. 15g37 Using JSON to exchange data between TTCN-3 and other systems . 16g37.1 General rules
11、. 16g37.2 JSON representations of TTCN-3 values 17g37.2.1 Character strings 17g37.2.2 Binary Strings 17g37.2.3 Integer 17g37.2.4 Float . 18g37.2.5 Boolean 18g37.2.6 Enumerated 18g37.2.7 Verdicttype 19g37.2.8 Record and set 19g37.2.9 Record of, set of and arrays . 20g37.2.10 Union and anytype . 21g37
12、.2.11 Object Identifiers . 22g38 JSON representations of TTCN-3 values based on ASN.1 types . 22g38.1 General rules . 22g38.2 Character strings 23g38.3 Binary strings 23g38.4 BOOLEAN 23g38.5 ENUMERATED . 23g38.6 REAL 23g38.7 INTEGER 23g38.8 OBJID . 23g38.9 NULL 23g38.10 SEQUENCE and SET . 24g38.11 S
13、EQUENCE OF and SET OF . 24g38.12 CHOICE and Open Types . 24g3Annex A (normative): TTCN-3 module JSON 25g3ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)4 Annex B (normative): Encoding instructions 27g3B.1 General . 27g3B.2 The JSON encode attribute . 27g3B.3 Encoding instructions . 27g3B.3.1 General rules
14、. 27g3B.3.2 JSON type identification . 28g3B.3.3 Normalizing JSON Values 28g3B.3.4 Name as . 28g3B.3.5 Number of fraction digits 29g3B.3.6 Use the Minus sign 30g3B.3.7 Escape as . 30g3B.3.8 Omit as null . 31g3B.3.9 Default . 31g3B.3.10 As value . 32g3B.3.11 No Type . 32g3B.3.12 Use order . 32g3B.3.1
15、3 Error behaviour . 33g3Annex C (informative): Bibliography . 34g3History 35g3ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if
16、any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available
17、 on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or
18、 may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). The present document is part 11 of a multi-part deliverable. Full details of the entire series can be found in part 1
19、 1. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must no
20、t“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)6 1 Scope The present document specifies the rules to define schemas for JSON data structures in TTCN-3, to enable testing of JSON-based systems, interfaces and protocols, and the con
21、version rules between TTCN-3 1 and JSON 2 to enable exchanging TTCN-3 data in JSON format between different systems. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific referenc
22、es, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: Whi
23、le any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI ES 201 873-1: “Methods for Testing and Specification (MTS); The Testin
24、g and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. 2 IETFRFC 7159: “The JavaScript Object Notation (JSON) Data Interchange Format“. NOTE: Available at http:/www.rfc-editor.org/rfc/rfc7159.txt. 3 ISO/IEC 10646:2014: “Information technology - Universal Coded Character Set (UCS)“. NO
25、TE: Available at http:/standards.iso.org/ittf/PubliclyAvailableStandards/c056921_ISO_IEC_10646_2012.zip. 4 IEEETM754: “IEEE Standard for Floating-Point Arithmetic“. 5 ETSI ES 201 873-7: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 7: Using ASN.1
26、 with TTCN-3“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (i
27、ncluding any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with r
28、egard to a particular subject area. i.1 IETFdraft-zyp-json-schema-04: “JSON Schema: core definitions and terminology“. NOTE: Available at http:/tools.ietf.org/html/draft-zyp-json-schema-04. i.2 IETFdraft-fge-json-schema-validation-00: “JSON Schema: interactive and non interactive validation“. NOTE:
29、Available at http:/tools.ietf.org/html/draft-zyp-json-schema-04. ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)7 i.3 World Wide Web Consortium W3CRecommendation: “XML Schema Part 1: Structures“. NOTE: Available at http:/www.w3.org/TR/xmlschema11-1. i.4 World Wide Web Consortium W3CRecommendation: “XML Sch
30、ema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/xmlschema11-2. i.5 ETSI ES 201 873-8: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 8: The IDL to TTCN-3 Mapping“. i.6 ETSI ES 201 873-9: “Methods for Testing and Specification (MTS);
31、 The Testing and Test Control Notation version 3; Part 9: Using XML schema with TTCN-3“. i.7 ETSI ES 202 781: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support“. i.8 ETSI ES 202 782: “Method
32、s for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: TTCN-3 Performance and Real Time Testing“. i.9 ETSI ES 202 784: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extension
33、s: Advanced Parameterization“. i.10 ETSI ES 202 785: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Behaviour Types“. i.11 ETSI ES 202 786: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation
34、version 3; TTCN-3 Language Extensions: Support of interfaces with continuous signals“. i.12 ETSI ES 202 789: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Extended TRI“. 3 Definitions and abbreviations 3.1 Definitions For t
35、he purposes of the present document, the terms and definitions given in ETSI ES 201 873-1 1 apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation no. 1 IO ASN.1 Information Object JSON JavaScript Object Notation SUT Syste
36、m Under Test TTCN-3 Testing and Test Control Notation version 3 UCS Universal Coded Character Set USI UCS Sequence Identifier UTF-8 Unicode Transformation Format-8 XML eXtensible Markup Language XSD XML Schema Definition ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)8 4 Introduction An increasing number o
37、f distributed applications use the JSON to exchange data for various purposes like data bases queries or updates or event telecommunications operations such as provisioning. The JSON specification 2 defines the syntax and encoding for JSON types and defined literals, but no semantics is defined. JSO
38、N does not have a schema specification, like the XML Schema Definition Language used for XML documents (see i.3 and i.4). NOTE: Though an IETF draft proposal exists for JSON schema (see i.1 and i.2), it has not reached the RFC status. The core language of TTCN-3 is defined in ETSI ES 201 873-1 1 and
39、 provides a full text-based syntax, static semantics and operational semantics. Other parts of the ETSI ES 201 873 series are defining its use with other specification languages like ASN.1 5, IDL i.5, or XSD i.6 as shown in figure 1, while other documents as ETSI ES 202 781 i.7, ETSI ES 202 782 i.8,
40、 ETSI ES 202 784 i.9, ETSI ES 202 785 i.10, ETSI ES 202 786 i.11 and ETSI ES 202 789 i.12 specify language extensions and thus can define additional rules to the JSON/TTCN-3 mapping defined in the present document. Other presentation formats as defined in other parts of the standard or user-specific
41、 formats TTCN-3 Core Language TTCN-3 User JSON Types for example, the TTCN-3 system receiving contents of messages to be sent to an SUT, encode and send a message, receive and process the response and report the result to the other system. Consequently, there is a need to specify mappings between JS
42、ON and TTCN-3 for the above purposes. 5 Conformance and compatibility For an implementation claiming to support the use of TTCN-3 as a JSON schema language, all features specified in clause 6 of the present document shall be implemented consistently with the requirements given in clause 6 and Annex
43、B of the present document and in ETSI ES 201 873-1 1. For an implementation claiming to support the exchange of TTCN-3-based data between systems, and not supporting using ASN.1 with TTCN-3, all features specified in clause 7 of the present document, with the exception of the mapping of the objid ty
44、pe in clause 7.2.11 shall be implemented consistently with the requirements given in clause 7 and Annex B of the present document and in ETSI ES 201 873-1 1. Implementations claiming the support of using ASN.1 with TTCN-3, shall in addition support features in clause 7.2.11 and clause 8 of the prese
45、nt document. ETSI ETSI ES 201 873-11 V4.7.1 (2017-06)9 The language mappings presented in the present document is compatible to: ETSI ES 201 873-1 1, version 4.9.1. If later versions of those parts are available and should be used instead, the compatibility of the rules presented in the present docu
46、ment shall be checked individually. 6 Using TTCN-3 as JSON Schema 6.1 Approach JSON 2 defines a limited set of JSON types and literal values. The clauses below define the TTCN-3 types that can be used to specify a Schema for any JSON interface specification. The TTCN-3 types defined in the clauses b
47、elow will allow to use the same set of values as JSON permits. Annex A provides a TTCN-3 module containing all TTCN-3 definitions specified in these clauses. The JSON module in Annex A shall either explicitly be present in TTCN-3 test suites or TTCN-3 tools shall support these types implicitly. This
48、 is left as a tool implementation option. JSON in many cases allows different encoding options for the same value. These may be controlled by the JSON encoding instructions specified in Annex B. JSON encoding instructions may be added to TTCN-3 types and fields by using TTCN-3 variant attributes (se
49、e ETSI ES 201 873-1 1, clause 27.5). 6.2 Validation of JSON Values For further study. 6.3 Name conversion rules The current version of the JSON specification 2 uses names to identify JSON object members only. The present document defines JSON to TTCN-3 name conversion rules that shall be used when using TTCN-3 to specify a schema for a JSON interface (see for example clause 6.4.4). When the JSON and the TTCN-3 names differ after applying the rules in this clause, the “name as “
