hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9 Other Attribute characteristics | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9.1 Attribute life span | Three major attribute validity classes have been identified: 1) life lasting: the attribute is linked to the individual for his/her entire life; nevertheless the individual, under exceptional conditions, can be stripped of his/her attribute; examples can be: honorific position, professional position, like lawyer or phy... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9.2 Attribute certification period | 1) The Attribute life span is a main criterion to be used in order to know whether an attribute should be placed in a PKC or an AC. Once the decision to place it in an AC is taken, then the ACA has to decide how long it will accept to certify this attribute. This time period is called the Attribute certification period... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9.3 Attribute certificate validity period | Even if the life span of an attribute is large, it is not necessary to certify that attribute by issuing an attribute certificate for its whole life-span period. The attribute certificate validity period should not be confused with the attribute certification period. The attribute certificate validity period is the per... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9.4 Attribute revocation and Attribute Certificate revocation | In many cases, in order to avoid a revocation status check, which implies to query some server, attributes will be granted by an AA for a period of time that is short enough so that revocation is not considered to be meaningful. This can be hours, a day, a week or more. It should be noted that validity periods longer t... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9.5 Attribute privacy | Users may not necessarily want to always disclose all of their attributes. For that reason these attributes should not be included in PKCs but only included in ACs which are then only attached to the documents that need to take advantage of them. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9.6 Ways to acquire attributes | There are threeways to acquire attributes: • by default, when they are included in a PKC; • upon request, when they are included in an AC; • by getting them from ACs stored in a repository. In the first case, individuals do not ask themselves for their attributes, but have them by default assigned to them in PKCs. In t... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 9.7 Delegable attributes | Some attributes may only be directly assigned to an individual (and be non-transferable), while some others may be designated as delegable. It is not because an attribute is delegable that anyone that has the attribute type may be allowed to delegate it. Some individuals may be designated to have the right to delegate ... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 10 Placement of attributes in certificates | There are two ways to certify attributes. • using Public Key Certificates, • using Attribute Certificates. In any case a subject needs at least one PKC. Therefore a subject may end up owning: a) one or more PKCs, possibly issued under different certificate policies and with different validity periods each one with zero... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 10.1 Using Public Key Certificates | There is need to minimize the information to be kept on identity certificates. Public-key certificates can natively support some attributes. There are two means to do so: • using the Common Name attribute type (see [7]), and/or • using the Title attribute type (see [7]). The Common Name attribute type specifies an iden... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 10.2 Using Attribute Certificates | The authority for assignment of some attributes may be different from the authority issuing a public-key certificate and different attributes may be assigned by different Attribute Authorities (AA), hence a different authority is needed to grant these attributes. An Attribute Certificate is a data structure issued by a... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 11 Attribute Certificates management | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 11.1 Attribute verification by the ACA | The only liability provided on the CA in Directive [3] article 6(2), that may be applicable also for attribute verification, is "for failure to register revocation of the certificate unless the certification-service-provider proves that he has not acted negligently." Therefore a PKC issuing CA is not required to necess... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 11.2 Link with a PKC | Attribute Certificates contain attributes and are unambiguously linked to the subject's PKC by referencing it via the baseCertificateID as defined in [4]. The "baseCertificateID" indicates the Issuer name (and optionally its UniqueIdentifier) and the serial number of the certificate owner's PKC. When a subscriber appli... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 11.3 Attribute Certificate revocation management | When the AC validity is so short that the duration of the revocation process, leading to a status change, is such that the new status (i.e. "revoked") would be issued when the certificate has already expired, there is no need/usefulness to maintain an attribute certificate revocation status information. When the intrin... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 11.4 Attribute Certificate acquisition | Once attributes are registered, they need to be made available to subscribers in the form of an Attribute Certificate. In some cases, an individual would like to exercise a subset of its attributes. This relates to the principle of "least privileges", where only the privileges useful for an operation are presented. So ... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 11.5 Attribute delegation management | An attribute may be delegated during some period of time to another individual. When performing the delegation, the subscriber shall indicate that period of time and nominate the delegate by specify an unambiguous link to the certificate of that person. In addition the subscriber may wish to restrict the use of the att... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12 Recommendations | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12.1 Requirements for Attribute Certificate Policies | Whereas a PKC is always issued under a fixed set of Certificate Policies, every AC can be issued under a different Attribute Certificate Policy. So the same AA can support multiple policies but shall make sure that every grouping of attributes is done under a single coherent set of Attribute Certificate Policies. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12.1.1 Requirements for ACAs | The Attribute Certification Authority is liable for the accuracy of the attributes when they are initially registered. If it is a Qualified Certificate issuer it is legally required binding. It is up to the Attribute Certification Authority to choose how to ascertain the attribute accuracy for which it will be liable. ... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12.1.2 Requirements for AAs | Any kind of attribute (life lasting, long lasting, short lasting) may be included in an AC. An AA is liable for the accuracy of the attributes when they are initially registered. The AA shall indicate whether it handles revocation or not. If handled, it may simply continue to certify the attribute, i.e. accept to re-is... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12.2 Definition of cross-European roles | It would be adequate to conduct a study about the equivalence of some "useful" attributes, that have an equivalence among all the European countries. When a character string is being used, that string is language dependent and may only be easily understandable in one country. While this is certainly useful, this does n... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12.3 Attribute Certificate Profile for Electronic Signatures | IETF RFC 3281 [8] specifies an Internet Attribute Certificate Profile for Authorization. This means that this RFC is targeted to be used in the context of an access control service and not in the context of non repudiation nor data origin authentication services. In the previous clauses several enhancements to this cer... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12.4 Attribute Certificate Acquisition Protocol | There are two kinds of protocols to consider whether the Attribute Certificates are produced upon request or directly by the Attribute Authority. When Attribute Certificates are produced upon request, then they are returned to the requestor and a reference to these Attribute Certificates can be used to fetch them later... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 12.5 Criteria for using PKCs or ACs | Non-public attributes should only be included in ACs. For the reasons set forth in clause 8, life/long lasting attributes are preferably to be included in PKCs while short lasting attributes should be included in ACs: - If the attribute does not expire before the related PKC, the attribute may be included in the PKC. -... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 1 Introduction | ............................................................................................................................................32 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 2 Definitions | ..............................................................................................................................................32 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 3 Regulative references | .............................................................................................................................32 4 ROLE CERTIFICATION ......................................................................................................................33 4.1 ROLE CERTIFICATE PROFILE......................... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.1.1 Role Location and Structure | .......................................................................................................................33 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.1.2 Description in Natural Language | ................................................................................................................33 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.1.3 Numeric Code | .............................................................................................................................................33 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.1.4 Organization, Organization Unit, and Locality Fields | ................................................................................34 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.1.5 Relations with the Qualified Certificate | ......................................................................................................35 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.2 Unique role table | ..............................................................................................................................................35 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.3 Table update procedure | ....................................................................................................................................35 5 ORGANIZATIONAL PROCESSES .....................................................................................................36 5.1 CERTIFICATION AUTHORITY'S LIABILITY.................. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5.1.1 Foreword | .....................................................................................................................................................36 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5.1.2 Procedures for the Verification of the Existence of Powers, Offices, or Professional Qualifications | ........36 5.1.3 Annulment or Termination of Powers ........................................................................................................37 5.2 PRACTICE STATEMENTS............................................................................................................................37 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6 Dissemination of the solution | .................................................................................................................38 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.1 Relations between certification authority members | .........................................................................................38 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.1.1 Adoption of the Solution | .............................................................................................................................38 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.1.2 Interoperability Test | ....................................................................................................................................38 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.2 Relations with certification authority non-members | ........................................................................................39 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.2.1 Private Certification Authorities | .................................................................................................................39 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.2.2 RUPA Technical Center | .............................................................................................................................39 |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.3 Assocertificatori relations with third-parties | ....................................................................................................39 Appendix A: Examples of role indications...................................................................................................40 Appendix B: Unique role table................................................. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4 Role certification | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4.1 Role certificate profile | 4.1.1 Role Location and Structure The role attributes are inserted in the Role (R) sub-field of the Description field in the part of the certificate reserved to the Subject. The R field consists of the following parts: • Brief and accurate description in natural language of the role of the holder. • Numeric code that f... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5 Organizational processes | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5.1 Certification authority's liability | 5.1.1 Foreword The Italian Regulation outlines the level of liability that a Certification Authority, which does not comply with the identification and specification obligations of powers of representation, must take. The combined dispositions of the articles in the Italian Regulation assign the Certification Authority... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5.1.3 Annulment or termination of powers | The matters treated so far have important effects in case the titles or professional qualifications, offices, or powers of representation fail. As far as titles and offices are concerned, the Certification Authority must extend its verification until their validity terminates (only) if the Certification Authority guara... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5.2 Practice statements | The present clause includes hints and recommendations to define the proper procedures in the Practice Statements for the insertion of the role, with the purpose of guaranteeing a certain level of interoperability also between the organizational procedures, and to limit the liability of the Certification Authority withi... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 1 Scope | The present document provides the specification of the runtime interface for TTCN-3 test system implementations. The TTCN-3 Runtime Interface provides a standardized adaptation for timing and communication of a test system to a particular processing platform and the system under test, respectively. The purpose of the p... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 2 Compliance | The minimum required for a TRI compliant TTCN-3 test system is to adhere to the interface specification stated in the present document and one language mapping. For example, if a vendor supports Java, the TRI operation calls and implementations, which are part of the TTCN-3 executable, must comply with the IDL to Java ... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 3 References | For the purposes of this Technical Report (TR) the following references apply: [1] ISO/IEC 9646-3 (2nd edition): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular combined Notation (TTCN)". [2] ETSI ES 201 873-1: "Methods for Testing an... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 4 Definitions and abbreviations | |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 4.1 Definitions | For the purposes of the present document, the following terms and definitions apply: explicit timer: timer that is declared in a TTCN-3 ATS and that can be manipulated by a user using TTCN-3 timer operations implicit timer: system timer that is created by the TTCN-3 Executable to guard a TTCN-3 call or execute operatio... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 4.2 Definitions from ES 201 873-1 | The following definitions are taken from ES 201 873-1 [2]: communication port Implementation eXtra Information for Testing (IXIT) System Under Test (SUT) test case test system |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 4.3 Abbreviations | ATS Abstract Test Suite ETS Executable Test Suite IDL Interface Definition Language IXIT Implementation Extra Information for Testing MSC Message Sequence Chart MTC Main Test Component OMG Object Management Group PA Platform Adapter SA SUT Adapter SUT System Under Test TC Test Control TCI TTCN-3 Control Interface TE TT... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 5 Void | ETSI ETSI TR 102 043 V1.1.1 (2002-04) 8 |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6 General Structure of a TTCN-3 test system | A TTCN-3 test system can be thought of conceptually as a set of interacting entities where each entity corresponds to a particular aspect of functionality in a test system implementation. These entities manage test execution, interpret or execute compiled TTCN-3 code, realize proper communication with the SUT, implemen... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1 Entities in a TTCN-3 test system | The structure of a TTCN-3 test system implementation is illustrated in figure 1. It should be noted that the further refinement of TM into smaller entities, as shown in this figure and used in the following clauses of the present document, is purely an aid to define TTCN-3 test system interfaces. The part of the test s... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.1 Test Management (TM) | In the TM entity, we can distinguish between functionality related to test execution control and test event logging. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.1.1 Test Control (TC) | The TC entity is responsible for overall management of the test system. After the test system has been initialized, test execution starts within the TC entity. The entity is responsible for the proper invocation of TTCN-3 modules, i.e. propagating module parameters and/or IXIT information to the TE if necessary. Typica... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.1.2 Test Logging (TL) | The TL entity is responsible for maintaining the test log. It is explicitly notified to log test events by the TE. The TL entity has a unidirectional interface where any entity part of the TE may post a logging request to the TL entity. A TM internal interface may also be used to record test management information gene... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.2 TTCN-3 Executable (TE) | The TE entity is responsible for the interpretation or execution of the TTCN-3 ATS. Conceptually, the TE can be decomposed into three interacting entities: a Control, Behaviour, and Queue entity. Such a decomposition of the TE functionality results in the structure shown in figure 2. The following clauses outline the r... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.2.1 TTCN-3 Executable Control (TEC) | The TEC entity handles the control part specified for TTCN-3 modules. This entity performs all the actions necessary to properly sequence the execution of test cases or functions as well as the collection and resolution of associated verdicts as defined in [2]. The TEC entity is also responsible for resetting adapters ... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.2.2 TTCN-3 Executable Behaviour (TEB) | The TEB entity handles the execution or interpretation of test cases and functions as defined in the corresponding TTCN-3 modules [2]. It is therefore responsible for controlling the sequencing and matching of test events, the logging of test events during test case execution, as well as the creation and removal of TTC... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.2.3 TTCN-3 Executable Queue (TEQ) | The TTCN-3 Executable is required to maintain its own port queues (distinct from those which may be available in the SA or PA) for input test events to perform snapshots for receiving operations as defined in [2]. Timeout events, which are generated by TTCN-3 timer, call timer, or test case timer implementations, are t... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.2.4 Timers in the TTCN-3 Executable | Timers in the TE can be conceptually classified as explicit, that are TTCN-3 timers created and accessible within the TTCN-3 ATS, and implicit, that are timers created by the TE to guard TTCN-3 call or execute operations. Explicit as well as implicit timers are both created within the TE but implemented by the Platform... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.3 SUT Adapter (SA) | The SA adapts message and procedure based communication of the TTCN-3 test system with the SUT to the particular execution platform of the test system. It is aware of the mapping of the TTCN-3 test component communication ports to test system interface ports and implements the real test system interface as defined in [... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.1.4 Platform Adapter (PA) | The PA implements TTCN-3 external functions and provides a TTCN-3 test system with a single notion of time. In this entity external functions are to be implemented as well as all timers. Notice that timer instances are created in the TE. A timer in the PA can only be distinguished by its timer identification (TID). The... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.2 Interfaces in a TTCN-3 Test System | As previously depicted in figure 1, a TTCN-3 test system has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and Platform Adapter (PA) entities, respectively.... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 6.3 Execution Requirements for a TTCN-3 Test System | Each TRI operation call shall be treated as an atomic operation in the calling entity. The called entity, which implements a TRI operation, shall return control to the calling entity as soon as its intended effect has been accomplished or if the operation cannot be completed successfully. The called entity shall not bl... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7 TTCN-3 Runtime Interface and Operations | This clause defines TRI operations in terms of when they are to be used and what their effect is intended to be in a TTCN-3 test system implementation. Also a set of abstract data types is defined which is then used for the definition of TRI operations. This definition also includes a more detailed description of the i... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.1 Overview of the TRI | The TRI defines the interaction between the TTCN-3 Executable (TE), SUT Adapter (SA), and Platform Adapter (PA) entities within a TTCN-3 test system implementation. Conceptually, it provides a means for the TE to send test data to the SUT or manipulate timers, and similarly to notify the TE of received test data and ti... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.1.1 The triCommunication Interface | This interface consists of operations that are necessary to implement the communication of the TTCN-3 ETS with the SUT. It includes operations to initialize the Test System Interface (TSI), establish connections to the SUT, and handle message and procedure based communication with the SUT. In addition, the triCommunica... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.1.2 The triPlatform Interface | This interface includes all operations necessary to adapt the TTCN-3 Executable to a particular execution platform. The triPlatform interface offers means to start, stop, read a timer, enquire its status and to add timeout events to the expired timer list. In addition, it offers operations to call TTCN-3 external funct... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.1.3 Correlation between TTCN-3 and TRI Operation Invocations | For some TTCN-3 operation invocations there exists a direct correlation to one TRI operation invocation (or possibly two in the case of TTCN-3 execute and call operations) which is shown in table 2. For all other TRI operation invocations there may be no direct correlation. The shown correlation for TTCN-3 communicatio... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.2 Error handling | Explicit error handling is specified only for TRI operations called by the TTCN-3 Executable (TE). The SA or PA reports the status of a TRI operation in the return value of a TRI operation. The status value can either indicate the local success (TRI_OK) or failure (TRI_Error) of the TRI operation. Therefore, the TE may... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.3 Data Interface | In the TRI operations only encoded test data shall be passed. The TTCN-3 Executable (TE) is responsible for encoding test data to be sent and decoding received test data in the respective TRI operations since encoding rules can be specified for or within a TTCN-3 module [2]. Notice that the TE is required to encode tes... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.3.1 Connection | TriComponentIdType A value of type TriComponentIdType includes an identifier and the component type. The distinct value of the latter is the component type name as specified in the TTCN-3 ATS. This abstract type is mainly used to resolve TRI communication operations on TSI ports which have mappings to many test compone... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.3.2 Communication | TriMessageType A value of type TriMessageType is encoded test data which either is to be send to the SUT or has been received from the SUT. TriAddressType A value of type TriAddressType indicates a source or destination address within the SUT. This abstract type can be used in TRI communication operations and is an ope... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.3.3 Timer | TriTimerIdType A value of type TriTimerIdType specifies an identifier for a timer. This abstract type is required for all TRI timer operations. TriTimerDurationType A value of type TriTimerDurationType specifies the duration for a timer in seconds. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.3.4 Miscellaneous | TriTestCaseIdType A value of type TriTestCaseIdType is the name of a test case as specified in the TTCN-3 ATS. TriFunctionIdType A value of type TriFunctionIdType is the name of an external function as specified in the TTCN-3 ATS. TriActionTemplateType A value of type TriActionTemplateType is the encoded type and value... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.4 Operation Descriptions | All operation definitions are defined using the Interface Definition Language (IDL). Concrete language mappings are defined in clauses 8 and 9. For every TRI operation call all in, inout, and out parameters listed in the particular operation definition are mandatory. The value of an in parameter is specified by the cal... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.5 Communication Interface Operations | • triSAReset TE → → → →SA Signature TriStatusType triSAReset() In Parameters n.a. Out Parameters n.a. Return Value The return status of the triSAReset operation. The return status indicates the local success (TRI_OK) or failure (TRI_Error) of the operation. Constraints This operation can be called by the TE at any time... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.5.1 Connection Handling Operations | • triExecuteTestcase TE → → → →SA Signature TriStatusType triExecuteTestcase(in TriTestCaseIdType testCaseId, in TriPortIdListType tsiPortList) In Parameters testCaseId identifier of the test case that is going to be executed. tsiPortList a list of test system interface ports defined for the test system. Out Parameters... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.5.2 Message Based Communication Operations | • triSend TE → → → →SA Signature TriStatusType triSend(in TriComponentIdType componentId, in TriPortIdType tsiPortId, in TriAddressType SUTaddress, in TriMessageType sendMessage) In Parameters componentId identifier of the sending test component. tsiPortId identifier of the test system interface port via which the mess... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.5.3 Procedure Based Communication Operations | • triCall TE → → → →SA Signature TriStatusType triCall(in TriComponentIdType componentId, in TriPortIdType tsiPortId, in TriAddressType SUTaddress, in TriSignatureIdType signatureId, in TriParameterListType parameterList) In Parameters componentId identifier of the test component issuing the procedure call. tsiPortId i... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.5.4 Miscellaneous operations | • triSUTactionInformal TE → → → →SA Signature TriStatusType triSUTactionInformal(in string description) In Parameters description an informal description of an action to be taken on the SUT. Out Parameters n.a. Return Value The return status of the triSUTactionInformal operation. The return status indicates the local s... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.6 Platform Interface Operations | • triPAReset TE → → → →PA Signature TriStatusType triPAReset() In Parameters n.a. Out Parameters n.a. Return Value The return status of the triPAReset operation. The return status indicates the local success (TRI_OK) or failure (TRI_Error) of the operation. Constraints This operation can be called by the TE at any time... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.6.1 Timer Operations | • triStartTimer TE → → → →PA Signature TriStatusType triStartTimer(in TriTimerIdType timerId, in TriTimerDurationType timerDuration) In Parameters timerIdidentifier of the timer instance. timerDuration duration of the timer in seconds. Out Parameters n.a. Return Value The return status of the triStartTimer operation. T... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 7.6.2 Miscellaneous operations | • triExternalFunction TE → → → →PA Signature TriStatusType triExternalFunction (in TriFunctionIdType functionId, inout TriParameterListType parameterList, out TriParameterType returnValue) In Parameters functionId identifier of the external function. InOut Parameters parameterList a list of encoded parameters for the i... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8 Java Language Mapping | |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.1 Introduction | This clause introduces the TRI Java language mapping. For efficiency reasons a dedicated language mapping is introduced instead of using the OMG IDL to Java language. The Java language mapping for the TTCN-3 Runtime Interface defines how the IDL definitions described in clause 7 are mapped to the Java language. The lan... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.2 Names and Scopes | |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.2.1 Names | Although there are no conflicts between identifiers used in the IDL definition and the Java language some naming translation rules are applied to the IDL identifiers. • Java parameter identifiers shall start with a lower case letter, and subsequent part building the parameter identifier start with a capital letter. For... |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.2.2 Scopes | The IDL module triInterface is mapped to the Java package org.etsi.ttcn3.tri. All IDL type declarations within this module are mapped to Java classes or interface declarations within this package. |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3 Type Mapping | |
fb42dba998b384ed10bb43a68ab55611 | 102 043 | 8.3.1 Basic Type Mapping | Table 3 gives an overview on how the used basic IDL types are mapped to the Java types. Table 3: Basic type mappings IDL Type Java Type boolean org.etsi.ttcn.tri.TriBoolean string java.lang.String Other IDL basic types are not used within the IDL definition. ETSI ETSI TR 102 043 V1.1.1 (2002-04) 26 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.