hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0ff16a1353d18c9835694e27515ee034 | 101 666 | 10.4 Test Case Index | The Test Case Index contains a complete list of all Test Cases in the ATS. The following information shall be provided for each Test Case: a) an optional Test Group Reference (if the ATS is structured into Test Groups), which defines where in the test suite group structure the Test Case resides. Test Groups shall be li... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 10.5 Test Step Index | The Test Step Index contains a complete list of all Test Steps in the ATS. The following information shall be provided for each Test Step: a) an optional Test Step Group Reference, (if the ATS is structured into Test Step Groups), which defines where in the Test Step Library structure the Test Step resides. If the grou... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 10.6 Default Index | The Default Index contains a complete list of all Defaults in the ATS. The following information shall be provided for each Default: a) an optional Default Group Reference, (if the ATS is structured into Default Groups), which defines where in the Default Library structure the Default resides. If the group reference fo... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 10.7 Test Suite Exports | The Test Suite Exports table may be used to specify explicitly which objects in the test suite are designed to be re-usable and hence may be imported into other test suites or TTCN modules. The Test Suite Exports proforma is used to identify the objects which may be exported. The name of the original source object shal... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 10.8 The Import Part | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 10.8.1 Introduction | The purpose of the Import Part is to declare the objects used in the test suite that are imported from a source object. The effect of the imports is equivalent to having a copy of the imported objects within the test suite. An object may be imported only if a source object exports it. A test suite without an export tab... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 10.8.2 Imports | The Imports tables identify the source object and provides information on the overall objective of the source object. The following information shall be supplied in the Imports tables: a) the name of the source object; b) a description of the objective of the source object; c) a full reference to the source object; whi... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11 Declarations Part | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.1 Introduction | The purpose of the declarations part of the ATS is to define and declare all the objects used in the test suite. The following objects of an ATS referenced from the overview part, the constraints part and the dynamic part shall have been declared in the declarations part. These objects are: a) definitions: 1) Test Suit... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2 TTCN types | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.1 Introduction | TTCN supports a number of predefined types and mechanisms that allow the definition of specific Test Suite Types. These types may be used throughout the test suite and may be referenced when Test Suite Parameters, Test Suite Constants, Test Suite Variables, ASP parameters, PDU fields etc. are declared. TTCN is a weakly... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.2 Predefined TTCN types | A number of commonly used types are predefined for use in TTCN. All types defined in this clause may be referenced even though they do not appear in a type definition in a test suite. All other types used in a test suite shall be declared in the Test Suite Type definitions, ASP definitions or PDU definitions and refere... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.3 Test Suite Type Definitions | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.3.1 Introduction | Type definitions to be used as types for data objects and as subtypes for structured ASPs, PDUs etc. can be introduced using a tabular format and/or ASN.1. Wherever types are referenced within Test Suite Type definitions those references shall not be recursive (neither directly nor indirectly). |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.3.2 Simple Type Definitions using tables | To define a new Simple Type, the following information shall be provided: a) a name for the type; b) the base type, where the base type shall be a Predefined Type or a Simple Type. The base type is followed by the type restriction that shall take one of the following forms: 1) a list of distinguished values of the base... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.3.3 Structured Type Definitions using tables | Structured Types can be defined in the tabular form to be used for declaring structured objects as subtypes within ASP and PDU definitions and other Structured Types etc. The following information shall be supplied for each Structured Type: a) its name, where appropriate the full name, as given in the relevant protocol... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.3.4 Test suite type definitions using ASN.1 | Test Suite Types can be specified using ASN.1 This shall be achieved by an ASN.1 definition using the ASN.1 syntax as defined in ISO/IEC 8824-1. The following information shall be supplied for each ASN.1 type: a) its name, where appropriate the full name, as given in the relevant protocol standard, shall be used; if an... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.2.3.5 ASN.1 Type Definitions by Reference | Types can be specified by a precise reference to an ASN.1 type defined in an OSI standard or by referencing an ASN.1 type defined in an ASN.1 module attached to the test suite. The following information shall be supplied for each type: a) its name, where this name may be used throughout the entire test suite. This name... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3 TTCN operators and TTCN operations | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.1 Introduction | TTCN supports a number of predefined operators, operations and mechanisms that allow the definition of Test Suite Operations. These operators and operations may be used throughout any dynamic behaviour descriptions and constraints. |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.2 TTCN operators | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.2.1 Introduction | The predefined operators fall into three categories: a) arithmetic; b) relational; c) Boolean. The precedence of these operators is shown in table 3. Parentheses may be used to group operands in expressions, a parenthesized expression has the highest precedence for evaluation. Within any row in table 3, the listed oper... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.2.2 Predefined arithmetic operators | The predefined arithmetic operators are: "+", "-", "*", "/", MOD They represent the operations of addition, subtraction, multiplication, division and modulo. Operands of these operators shall be of type INTEGER (i.e., TTCN or ASN.1 predefined) or derivations of INTEGER (i.e., subrange). ASN.1 Named Values shall not be ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.2.3 Predefined relational operators | The predefined relational operators are: "=" | "<" | ">" | "<>" | ">=" | "<=" They represent the relations of equality, less than, greater than, not equal to, greater than or equal to and less than or equal to. Operands of equality ( =) and not equal to ( <>) may be of an arbitrary type. The two operands shall be compa... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.2.4 Predefined Boolean operators | The predefined Boolean operators are NOT AND OR They represent the operations of negation, logical AND and logical OR. Their operands shall be of type BOOLEAN (TTCN or ASN.1 or predefined). The result type of the Boolean operators is BOOLEAN. The logical AND returns the value TRUE if both its operands are TRUE; otherwi... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3 Predefined operations | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.1 Introduction | The predefined operations fall into two categories: a) conversion; b) others. Predefined operations may be used in every test suite. They do not require an explicit definition using a Test Suite Operation Definition table. When a predefined operation is invoked: a) the number of the actual parameters shall be the same ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.2 Predefined conversion operations | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.2.1 Introduction | TTCN supports the following predefined operations for type conversions: a) HEX_TO_INT converts HEXSTRING to INTEGER; b) BIT_TO_INT converts BITSTRING to INTEGER; c) INT_TO_HEX converts INTEGER to HEXSTRING; d) INT_TO_BIT converts INTEGER to BITSTRING. These operations provide encoding rules within the context of the op... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.2.2 HEX_TO_INT | HEX_TO_INT(hexvalue:HEXSTRING) ⇒ INTEGER This operation converts a single HEXSTRING value to a single INTEGER value. For the purposes of this conversion, a HEXSTRING shall be interpreted as a positive base 16 INTEGER value. The rightmost HEX digit is least significant, the leftmost HEX digit is the most significant. Th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.2.3 BIT_TO_INT | BIT_TO_INT(bitvalue:BITSTRING) ⇒ INTEGER This operation converts a single BITSTRING value to a single INTEGER value. For the purposes of this conversion, a BITSTRING shall be interpreted as a positive base 2 INTEGER value. The rightmost BIT is least significant, the leftmost BIT is the most significant. The bits 0 and ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.2.4 INT_TO_HEX | INT_TO_HEX(intvalue, slength:INTEGER) ⇒ HEXSTRING ETSI TR 101 666 V1.0.0 (1999-05) 48 This operation converts a single INTEGER value to a single HEXSTRING value. The resulting string is slength HEX digits long. For the purposes of this conversion, a HEXSTRING shall be interpreted as a positive base 16 INTEGER value. Th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.2.5 INT_TO_BIT | INT_TO_BIT(intvalue, slength:INTEGER) ⇒ BITSTRING This operation converts a single INTEGER value to a single BITSTRING value. The resulting string is slength bits long. For the purposes of this conversion, a BITSTRING shall be interpreted as a positive base 2 INTEGER value. The rightmost BIT is least significant, the l... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.3 Other predefined operations | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.3.1 IS_PRESENT | IS_PRESENT(DataObjectReference) ⇒ BOOLEAN As an argument the operation shall take a reference to a field within a data object only if it is defined as being OPTIONAL or if it has a DEFAULT value. The field may be of any type. The result of applying the operation is the BOOLEAN value TRUE if and only if the value of the... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.3.2 IS_CHOSEN | IS_CHOSEN(DataObjectReference) ⇒ BOOLEAN ETSI TR 101 666 V1.0.0 (1999-05) 49 The operation returns the BOOLEAN value TRUE if and only if the data object reference specifies the variant of the CHOICE type that is actually selected for a given data object. Otherwise the result is FALSE. The operation shall not be applied... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.3.3 NUMBER_OF_ELEMENTS | NUMBER_OF_ELEMENTS(Value) ⇒ INTEGER The operation returns the actual number of elements of a value that is of type ASN.1 SEQUENCE OF or SET OF. Its result is fully compatible with that of the equivalent ASN.1 SIZE constraint applied to objects of these types. The operation shall not be applied to values other than of A... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.3.3.4 LENGTH_OF | LENGTH_OF(Value) ⇒ INTEGER The operation returns the actual length of a value that is of type BITSTRING, HEXSTRING, OCTETSTRING, or CharacterString or of ASN.1 type BIT STRING or OCTET STRING. The units of length for each string type are defined in table 5 in 11.18.2. NOTE: These units of length are compatible with tho... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4 Test Suite Operation definitions and descriptions | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.1 Introduction | The ATS specifier may define operations specific to a test suite. To define a new operation, the following shall be provided: a) a name for the operation; b) a list of the input parameters and their types. This is a list of the formal parameter names and types. A colon and then the name of the parameter's type shall fo... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.2 Parameters | A test suite operation may be compared to a function in an ordinary programming language. Values shall only be passed into the operation by formal parameters. Each formal parameter shall be declared to be a Predefined Type, a Test Suite Type Identifier, ASP Type Identifier, PDU Type Identifier, CM Type Identifier or th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.3 Variables and Identifiers | If a procedural definition is used, it may include the declaration of local variables, placed at the head of the procedural definition, between the keywords VAR and ENDVAR. These variables may be of any type allowed in TTCN. The scope of these local variables is the procedural definition itself. These declarations decl... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.4 Procedure Statements | In a procedural definition, following the declaration of local variables, if any, there shall be a procedure statement of one of the following kinds: a) a Return statement; ETSI TR 101 666 V1.0.0 (1999-05) 53 b) an Assignment statement; c) an If statement; d) a While loop; e) a Case statement; f) a block containing a s... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.5 ReturnValue statements | Each evaluation of a test suite operation shall end with the evaluation of a ReturnValue statement, consisting of the keyword RETURNVALUE followed by an expression. This statement shall return the value of the given expression as the result of the test suite operation. The type of this result shall match the Result Typ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.6 Assignment statements | The form of Assignment is the same as in the TTCN behaviour descriptions (see 15.10.4), except that it is not enclosed in parentheses. The DataObjectReference on the left-hand side shall begin with a local variable. If the type of the local variable is a structured type then the DataObjectReference may access a compone... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.7 If statements | There are two forms of If statement: - IF expression THEN procedure-statement ELSE procedure-statement ENDIF; - IF expression THEN procedure-statement ENDIF. The expression following the keyword IF shall be evaluated first and shall evaluate to a Boolean value. If this evaluates to TRUE then the procedure statement fol... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.8 While loop | A While loop takes the form: - WHILE expression DO procedure-statement ENDWHILE. The expression following the keyword WHILE shall be evaluated first and shall evaluate to a Boolean value. If it evaluates to TRUE then the procedure statement following the keyword DO shall be evaluated and then, if no ReturnValue stateme... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.9 Case statement | A Case statement takes one of the two following forms: - CASE expression OF integer-label_1: procedure-statement_1; integer-label_2: procedure-statement_2; ... integer-label_n: procedure-statement_n; ELSE procedure-statement ENDCASE - CASE expression OF integer-label_1: procedure-statement_1; integer-label_2: procedure... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.3.4.10 Use of Test Suite Operations | A test suite operation together with its actual parameter list may be used wherever an expression is allowed. Each test suite operation should include appropriate error checking. If an error (e.g. division by zero, an invalid parameter, a type mismatch, or evaluation of an unbound variable) is detected during evaluatio... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.4 Test Suite Parameter Declarations | The purpose of this part of the ATS is to declare constants derived from the PICS and/or PIXIT which are used to globally parameterize the test suite. These constants are referred to as Test Suite Parameters, and are used as a basis for Test Case selection and parameterization of Test Cases. The following information r... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.5 Test Case Selection Expression Definitions | The purpose of this part of the ATS is to define selection expressions to be used in the Test Case selection process. This part of the ATS shall meet the requirements of ISO/IEC 9646-2. A selection expression is associated with one or more Test Groups and/or Test Cases by placing its identifier in the Test Case Selecti... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.6 Test Suite Constant Declarations | The purpose of this part of the ATS is to declare a set of names for values not derived from the PICS or PIXIT that will be constant throughout the test suite. The following information relating to each Test Suite Constant shall be provided: a) its name; b) its type, where the type shall be a predefined type, a simple ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.7 Test Suite Constant Declarations by Reference | The purpose of this part of the ATS is to declare a set of names for values not derived from the PICS or PIXIT that will be constant throughout the test suite. The following information relating to each Test Suite Constant shall be provided: a) its name; b) its type, where the type shall be a predefined type or an ASN.... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.8 TTCN variables | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.8.1 Test Suite Variable Declarations | A test suite may make use of a set of variables which are defined globally for the test suite, and retain their values throughout the test suite. These variables are referred to as Test Suite Variables. A Test Suite Variable is used whenever it is necessary to pass information from one Test Case to another. In concurre... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.8.2 Binding of Test Suite Variables | Initially Test Suite Variables are unbound. They may become bound (or be re-bound) in the following contexts: a) at the point of declaration if an initial value is specified; b) when the Test Suite Variable appears on the left-hand side of an assignment statement (see 15.10.4); Once a Test Suite Variable has been bound... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.8.3 Test Case Variable Declarations | A test suite may make use of a set of variables which are declared globally to the test suite but whose scope is defined to be local to the Test Case. In concurrent TTCN, each test component, including the MTC, receives a fresh copy of all Test Case Variables when it is created. These variables are referred to as Test ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.8.4 Binding of Test Case Variables | Initially Test Case Variables are unbound. They may become bound (or be re-bound) in the following contexts: a) at the point of declaration if an initial value is specified; b) when the Test Case appears on the left-hand side of an assignment statement (see 15.10.4). Once a Test Case Variable has been bound to a value,... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.9 PCO Type Declaration | This part of the ATS lists the set of service boundaries where the PCOs (Points of Control and Observation) are located. ETSI TR 101 666 V1.0.0 (1999-05) 61 The following information shall be provided for each PCO types used in the test suite: a) its name, which is used to identify the service boundary where the PCO is... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.10 PCO Declarations | This part of the ATS lists the set of points of control and observation (PCOs) to be used in the test suite and explains where in the testing environment these PCOs exist. NOTE 1: The number of PCOs is, where applicable, as defined in ISO/IEC 9646-1 and ISO/IEC 9646-2 for the test method(s) identified in the Test Suite... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.11 CP Declarations | CPs are used to facilitate the exchange of CMs between test components. CPs are modelled as two queues, one for each direction of communication. In this respect they are similar to PCOs (see figure 3). A difference between CPs and PCOs is that CPs connect two test components, while PCOs connect a test component with th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.12 Timer Declarations | A test suite may make use of timers. The following information shall be provided for each timer: a) the timer name; b) the optional timer duration, where the default duration of the timer shall be an expression which may be omitted if the value cannot be established prior to execution of the test suite; the terms in th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.13 Test Components and Configuration Declarations | 11.13.1 Test Components |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.13.1.1 Main Test Component | The Main Test Component is intended to fulfil the role of the Lower Tester Control Function (LTCF), as defined in ISO/IEC 9646-2, 11.5.2. Its behaviour is described in the first tree of the test case behaviour description table and all trees attached to it. It is responsible for: a) creating all PTCs required within th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.13.1.2 Parallel Test Components | Parallel Test Components are intended to fulfil the role of the Lower Testers or Upper Testers. Their behaviour is described in the tree which is referenced in a CREATE statement in the MTC, and all trees attached to it. A PTC assigns preliminary results but does not assign test verdicts. A PTC shall not: a) use Test S... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.13.1.3 Test Component Declarations | If concurrent TTCN is used, this section of the ATS shall declare all individual test components that are used. These test components are later referenced from the Test Component Configurations declarations which define specific configurations. The following information shall be provided for each test component: a) its... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.14 ASP Type Definitions | 11.14.1 Introduction The purpose of this part of the abstract TTCN test suite is to declare the types of ASPs that may be sent or received at the declared PCOs. ASP type definitions may include ASN.1 type definitions, if appropriate. 11.14.2 ASP Type Definitions using tables The following information shall be supplied ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.15 PDU Type Definitions | 11.15.1 Introduction The purpose of this part of the abstract TTCN test suite is to declare the types of the PDUs that may be sent or received either directly or embedded in ASPs at the declared PCOs. PDU type definitions may include ASN.1 type definitions, if appropriate. PDU definitions define the set of PDUs exchang... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.16 Test Suite Encoding Information | 11.16.1 Encoding Definitions To facilitate specification and testing of the encoding rules of an OSI protocol, if there is any allowed flexibility in the encoding rules applicable to the protocol, then an encoding definition should be provided. If an encoding definition is provided, a reference shall be given in the AT... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.17 CM Type Definitions | 11.17.1 Introduction CM parameters may be of any type that may be specified in TTCN. Simple CMs may contain no associated parameters or may contain just one parameter, e.g. a natural number, a preliminary result, or a character string like "suspend" or "continue". More complex CMs may carry additional information, e.g.... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.18 String length specifications | TTCN permits the specification of length restrictions on string types (i.e., BITSTRING, HEXSTRING, OCTETSTRING and all CharacterString types, plus the ASN.1 types BIT STRING and OCTET STRING) in the following instances: a) when declaring Test Suite Types as a type restriction; b) when declaring simple ASP parameters, P... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.19 ASP, PDU and CM Definitions for SEND events | In ASPs and/or PDUs that are sent from the tester, values for ASP parameters and/or PDU fields that are defined in the Constraints Part (see clause 12, 13, 14) shall correspond to the parameter or field definition. This means: a) the value shall be of the type specified for that ASP parameter or PDU field; and b) each ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.20 ASP, PDU and CM Definitions for RECEIVE events | For ASPs and/or PDUs received by the tester the ASP and/or PDU Type defines the class of incoming ASPs and/or PDUs that can match an event specification of that type. An incoming ASP or PDU is considered to be of that class if and only if: a) the ASP parameter and/or PDU field values are of the type specified in the AS... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 11.21 Alias Definitions | 11.21.1 Introduction In order to enhance the readability of TTCN behaviour descriptions, an Alias may be used to facilitate the renaming of ASP and/or PDU identifiers in behaviour descriptions. This renaming may be done to highlight the exchange of PDUs embedded in ASPs. The following information shall be provided for ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12 Constraints Part | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.1 Introduction | An ATS shall specify the values of the ASP parameters and PDU fields that are to be sent or received by the test system. The constraints part fulfils that purpose in TTCN. The dynamic behaviour descriptions (see clause 15) shall reference constraints to construct outgoing ASPs and/or PDUs in SEND events; and to specify... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.2 General principles | This subclause describes the general principles and defines the mechanisms of how to build constraints for SEND events and how to match RECEIVE events. These principles are common to both the tabular and ASN.1 forms of constraints. Constraints are detailed specifications of ASPs and/or PDUs. Normally, each constraint i... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.3 Parameterization of constraints | Constraints may be parameterized. In such cases the constraint name shall be followed by a formal parameter list enclosed in parentheses. The formal parameters shall be used to specify ASP parameter or PDU field values in the constraint. A colon and the name of the parameter's type shall follow each formal parameter na... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.4 Chaining of constraints | Constraints may be chained by referencing a constraint as the value of a parameter or field in another constraint. For example, the value of the Data parameter of an N-DATAreq (Network Data Request) ASP could be a reference to a T- CRPDU (Transport Connect Request PDU) PDU constraint, i.e., the T-CRPDU is chained to th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.5 Constraints for SEND events | Constraints that are referenced for SEND events shall not include wildcards (i.e., AnyValue ( ? ) or AnyOrOmit ( * )) unless these are explicitly assigned specific values on the SEND event line in the behaviour description. In tabular constraints, all ASP parameters and PDU fields are optional and therefore may be omit... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6 Constraints for RECEIVE events | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.1 Matching values | If a constraint is to be used to construct the values of ASP parameters or PDU fields that a received ASP or PDU shall match, it shall contain only specific values evaluated as explained in 12.6.3, or special matching mechanisms where it is not desirable, or possible, to specify specific values. The matching mechanisms... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.2 Matching mechanisms | An overview of the supported matching mechanisms is shown in table 6, including the special symbols and the scope of their application. The left hand column of this table lists all the ASN.1 types and TTCN equivalent types to which these matching mechanisms apply. The matching mechanisms in the horizontal headings are ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.3 Specific Value | This is the basic matching mechanism. Specific values in constraints are expressions. Unless otherwise specified, a constraint ASP parameter or PDU field matches the corresponding incoming ASP parameter or PDU field if, and only if, the incoming ASP parameter or PDU field has exactly the same value as the value to whic... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4 Instead of Value | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.1 Complement | Complement is an operation for matching that can be used on all values of all types. Complement is denoted by the keyword COMPLEMENT followed by a list of constraint values. Each constraint value in the list shall be of the type declared for the ASP parameter or PDU field in which the Complement mechanism is used. A co... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.2 Omit | Omit is a special symbol for matching that can be used on values of all types, provided that the ASP parameter or PDU field is optional. In ASN.1 constraints it is also possible to simply leave out an OPTIONAL ASP parameter or PDU field instead of using OMIT explicitly. NOTE: In tabular constraints, all parameters, fie... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.3 AnyValue | AnyValue is a special symbol for matching that can be used on values of all types. In both tabular and ASN.1 constraints AnyValue is denoted by "?". A constraint ASP parameter or PDU field that uses AnyValue matches the corresponding incoming ASP parameter or PDU field if, and only if, the incoming ASP parameter or PDU... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.4 AnyOrOmit | AnyOrOmit is a special symbol for matching that can be used on values of all types, provided that the ASP parameter or PDU field is declared as optional. In both tabular and ASN.1 constraints AnyOrOmit is denoted by "*". NOTE: The symbol "*" is used for both AnyOrOmit and AnyOrNone. Ambiguity in interpretation is resol... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.5 ValueList | ValueList can be used on values of all types. In both tabular and ASN.1 constraints. ValueLists are denoted by a parenthesized list of values separated by commas. A constraint ASP parameter or PDU field that uses a ValueList matches the corresponding incoming ASP parameter or PDU field if, and only if, the incoming ASP... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.6 Range | Ranges shall be used only on values of INTEGER type. A range is denoted by two boundary values, separated by ".." or TO, enclosed by parentheses. A boundary value shall be either a) INFINITY or -INFINITY; b) an expression that evaluates to a specific INTEGER value. ETSI TR 101 666 V1.0.0 (1999-05) 92 The lower boundary... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.7 SuperSet | SuperSet is an operation for matching that shall be used only on values of SET OF type. SuperSet shall be used only in ASN.1 constraints. SuperSet is denoted by SUPERSET. A constraint ASP parameter or PDU field that uses SuperSet matches the corresponding incoming ASP parameter or PDU field if, and only if, the incomin... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.4.8 SubSet | SubSet is an operation for matching that can be used only on values of SET OF type. SubSet shall be used only in ASN.1 constraints. SubSet is denoted by SUBSET. A constraint ASP parameter or PDU field that uses SubSet matches the corresponding incoming ASP parameter or PDU field if, and only if, the incoming ASP parame... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.5 Inside Values | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.5.1 AnyOne | AnyOne is a special symbol for matching that can be used within values of string types, SEQUENCE OF and SET OF. In both tabular and ASN.1 constraints AnyOne is denoted by "?". ETSI TR 101 666 V1.0.0 (1999-05) 93 Inside a string, SEQUENCE OF or SET OF a "?" in place of a single element means that any single element will... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.5.2 AnyOrNone | AnyOrNone is a special symbol for matching that can be used within values of string types, SEQUENCE OF and SET OF. In both tabular and ASN.1 constraints AnyOrNone is denoted by "*". If a "*" appears at the highest level inside a value of string type, SEQUENCE OF or SET OF, it shall be interpreted as AnyOrNone. NOTE: Th... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.5.3 Permutation | Permutation is an operation for matching that can be used only on values inside a value of SEQUENCE OF type. Permutation shall be used only in ASN.1 constraints. Permutation is denoted by PERMUTATION. Permutation in place of a single element means that any series of elements is acceptable provided it contains the same ... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.6 Attributes of values | |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.6.1 Length | Length is an operation for matching that can be used only as an attribute of the following mechanisms: Complement, AnyValue, AnyOrOmit, AnyOne, AnyOrNone, Permutation, SuperSet and SubSet. It can be used in conjunction with the IfPresent attribute. In both tabular and ASN.1 constraints, length may be specified as an ex... |
0ff16a1353d18c9835694e27515ee034 | 101 666 | 12.6.6.2 IfPresent | IfPresent is a special symbol for matching that can be used as an attribute of all the matching mechanisms, provided the type is declared as optional. In both tabular and ASN.1 constraints IfPresent is denoted by IF_PRESENT. ETSI TR 101 666 V1.0.0 (1999-05) 95 A constraint ASP parameter or PDU field that uses an IfPres... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.