hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
20009f29037fee90802044e2e10edcce | 101 874 | 5.40.2 List of field values | The list of field values should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.40.3 Encoding specified per field | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.40.4 Structured type reference | The PDU reference field should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.40.5 Derivation path | The derivation path should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.40.6 Encoding variation | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.40.7 Parameterization | The parameter list should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.40.8 Group reference | The group reference should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.41 CM Constraints Declaration | |
20009f29037fee90802044e2e10edcce | 101 874 | 5.41.1 Single tabular constraint | The CM constraint should be converted into a TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.41.2 List of field values | The list of field values should be copied into the body of the TTCN-3 tabular template proforma. ETSI ETSI TR 101 874 V1.1.1 (2000-12) 23 |
20009f29037fee90802044e2e10edcce | 101 874 | 5.41.3 Structured type reference | The type reference field should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.41.4 Derivation path | The derivation path should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.41.5 Parameterization | The parameter list should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.41.6 Group reference | The group reference should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42 ASN.1 Type Constraint Declaration | |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.1 Single constraint | The ASN.1 Type constraint should be converted into a TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.2 List of field values | The list of field values should be converted into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.3 Encoding specified per field | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.4 ASN.1 type reference | The type reference field should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.5 Derivation path | The derivation path should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.6 Encoding variation | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.7 Parameterization | The parameter list should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.42.8 Group reference | The group reference should be copied into the relevant field of the TTCN-3 tabular template proforma. ETSI ETSI TR 101 874 V1.1.1 (2000-12) 24 |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43 ASN.1 ASP Constraint Declaration | |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43.1 Single constraint | The ASN.1 ASP constraint should be converted into a TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43.2 List of field values | The list of field values should be converted into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43.3 Encoding specified per field | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43.4 ASN.1 type reference | The type reference field should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43.5 Derivation path | The derivation path should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43.6 Parameterization | The parameter list should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.43.7 Group reference | The group reference should be copied into the relevant field of the TTCN-3 tabular template proforma. 5.44 ASN.1 PDU Constraint Declaration |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.1 Single constraint | The ASN.1 PDU constraint should be converted into a TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.2 List of field values | The list of field values should be converted into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.3 Encoding specified per field | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.4 ASN.1 type reference | The type reference field should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.5 Derivation path | The derivation path should be copied into the relevant field of the TTCN-3 tabular template proforma. ETSI ETSI TR 101 874 V1.1.1 (2000-12) 25 |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.6 Encoding variation | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.7 Parameterization | The parameter list should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.44.8 Group reference | The group reference should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45 ASN.1 CM Constraint Declaration | |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45.1 Single constraint | The ASN.1 CM constraint should be converted into a TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45.2 List of field values | The list of field values should be converted into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45.3 Encoding specified per field | Should be copied into the body of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45.4 ASN.1 CM reference | The type reference field should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45.5 Derivation path | The derivation path should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45.6 Parameterization | The parameter list should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.45.7 Group reference | The group reference should be copied into the relevant field of the TTCN-3 tabular template proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46 Test case Dynamic Behaviour | The testcase dynamic behaviour must be converted into a TTCN-3 tabular Testcase proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.1 Sequential behaviour | In TTCN-2 sequential behaviour is described by successively incremented levels of indentation: A B C ETSI ETSI TR 101 874 V1.1.1 (2000-12) 26 In TTCN-3 sequential behaviour is expressed by a sequence of statements: A; B; C; |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.2 Alternative behaviour | Alternative behaviour in TTCN-2: A B C is translated to: alt { [] A; [] B; [] C; } In general a TTCN-2 statement line Event [Qualifier] (AssignmentList) TimerOps will be translated to alt { : [Qualifier] Event { AssignmentList ; TimerOps } : } If the statement line specifies a qualifier and is the only alternative on i... |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.3 Events | It is required to have the TTCN-2 constraints appropriately mapped to TTCN-3 templates. It is also necessary that TTCN-3 ports are defined that reflect the corresponding TTCN-2 PCOs and CPs. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.3.1 Receive | The RECEIVE event: A?B with constraint C is translated to: A.receive(C); With C referring to a (parameterised) TTCN-3 template the data type (B) must not be specified: A?B without a constraint; ETSI ETSI TR 101 874 V1.1.1 (2000-12) 27 is translated to: A.receive(B:*); |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.3.2 Send | The SEND event: A!B with constraint C; is translated to: A.send(C); With C referring to a (parameterized) TTCN-3 template the data type (B) must not be specified. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.3.3 The IMPLICIT SEND event | The corresponding TTCN-3 construct is the sut.action statement. It allows a (parameterised) template or an arbitrary text string to be passed to the system under test. <IUT!B> with constraint C is translated to: sut.send(C). |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.3.4 Otherwise | The OTHERWISE event: A?OTHERWISE; is translated to: A.receive. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.3.5 Timeout | The TIMEOUT event: ?TIMEOUT T; is translated to: T.timeout. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.3.6 Done | The DONE event: ?DONE(PTC1); could be translated to: PTC1.done. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.4 Timer operations | In TTCN-3 timer operations are normal behaviour statements. ETSI ETSI TR 101 874 V1.1.1 (2000-12) 28 |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.4.1 The START operation | Starting two timers with default durations: START T0, START T1 is translated to: T0.start; T1.start; Starting a timer with a duration value overriding the default duration: START T0 (V0) is translated to T0.start(V0); Whereas in TTCN-2 V0 had to evaluate to a positive, non-zero INTEGER, it must evaluate to a value of t... |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.4.2 The CANCEL operation | A running timer is stopped by means of the stop operation: STOP T0 is translated to T0.stop; |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.4.3 The READTIMER operation | READTIMER T0 (PASSED_TIME) is translated to: PASSED_TIME := T0.read; Whereas in TTCN-2 the type of the PASSED_TIME variable had to be INTEGER, it must be float in TTCN-3. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.5 Other constructs | |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.5.1 The ATTACH construct | In TTCN-2 the attached sub-tree can be a local sub-tree of the attaching test step or it can be a test step itself. Whenever it is possible to translate the sub-tree to a named alternative (named alt) in TTCN-3, this should be done. If the ATTACH construct appears within sequential behaviour, it will be translated as f... |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.5.2 Labels and the GOTO statement | If a TTCN-2 behaviour line contains an entry in the Label column, it is translated by defining the label first: LABEL A!B C is translated to label LABEL; A.send(C); Within an alt-construct, a label definition must not occur outside a statement block. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.5.3 The REPEAT statement | REPEAT STEP1 UNTIL [FLAG] is translated to do { STEP1; } while (not FLAG); |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.5.4 The RETURN statement | The TTCN-2 RETURN statement shall only be used in a Default trees. RETURN is translated to the TTCN-3 statement goto alt; |
20009f29037fee90802044e2e10edcce | 101 874 | 5.46.5.5 Default behaviour | The ACTIVATE statement The TTCN-2 RETURN statement shall only be used in a Default trees. ACTIVATE(DEF1,DEF2) is translated to the TTCN-3 statements deactivate; activate(DEF1,DEF2); The deactivate statement is necessary, because the TTCN-2 ACTIVATE implicitly deactivates all previously activated default behaviour. ETSI... |
20009f29037fee90802044e2e10edcce | 101 874 | 5.47 Test Step Dynamic Behaviour | The teststep dynamic behaviour should be converted into the TTCN-3 tabular Named Alternative proforma or under certain circumstances a TTCN-3 tabular Function proforma (see 4.45.5.1 for clarification). |
20009f29037fee90802044e2e10edcce | 101 874 | 5.47.1 List of behaviour statements in tree structure | The behaviour is translated as specified for testcases in clause 4.45. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.47.2 Parameterization | The parameters are copied to the parameter list of the relevant TTCN-3 proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.47.3 Purpose | The field should be copied to the purpose field of the named alternative or the comment field of the function proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.47.4 Group reference | This field should be copied into the group field of the relevant TTCN-3 tabular proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.48 Default Dynamic Behaviour | The default behaviour should be converted into the TTCN-3 tabular default behaviour proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.48.1 List of behaviour statements in tree structure | The behaviour is translated as specified for testcases in clause 4.45. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.48.2 Parameterization | The parameters are copied to the parameter list of the Named Alternative TTCN-3 proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.48.3 Purpose | The field should be copied to the purpose field of the named alternative proforma. |
20009f29037fee90802044e2e10edcce | 101 874 | 5.48.4 Group reference | This field should be copied into the group field of the named Alternative TTCN-3 tabular proforma. Proformas (48) to (51) in [2] are not considered since they can be handled in an analogous way to the first four TTCN-2 proformas. ETSI ETSI TR 101 874 V1.1.1 (2000-12) 31 History Document history V1.1.1 December 2000 Pub... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 1 Scope | The present document gives guidance in selecting charging parameters and the appropriate charging mechanisms in the IP (Internet Protocol) based networks of the future. In the today's Internet there is no detailed collection of charges implemented. Users are charged by the Internet Service Provider (ISP) either: • a fl... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 3 Definitions and abbreviations | |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 3.1 Definitions | Many definitions relevant for the present document are already contained in ETSI TR 101 619 [2]. The most important ones are repeated here. For the purposes of the present document, the following definitions apply: Accounting: revenue sharing amongst operators. NOTE 1: Also known as "settlement" and "revenue accounting... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATM Asynchronous Transfer Mode B-ISDN Broadband Integrated Services Digital Network CL Connectionless DIFFSERV Differentiated services DS Differentiated Services (field) ID Identification IntServ Integrated services IP Internet Protocol ISP In... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 4 Reference Configuration | |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 4.1 Network aspect | Figure 1 shows the reference configuration of the network the further considerations are based on as well as the flow of charges. It consists of an Access Network to the IP based network and the IP based network itself. ETSI ETSI TR 101 734 V1.1.1 (1999-09) 9 Access Network IP based Network Access Network charges for a... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 4.2 Charging reference model | The relationship between all actions related to charging is shown in Figure 3. Three main areas can be distinguished: • the area with strategic and market relevance - this relates to tariffing; • the area with administrative relevance - this relates to charging, accounting and billing; • the area with technical relevan... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 4.3 Service Aspect | The Internet Protocol is connectionless in its nature and currently supports only a service type which does not guarantee any Quality of Service. This is called "best effort" service. With the emerging of applications which need a kind of guarantee (so called Real Time Services) new mechanisms are necessary. The answer... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 5 Charging principles applied to IP based networks | In order to better understand which network capabilities are necessary, the following principles for charging are assumed: • There will be not only one charging principle in IP based networks but a variety depending on the needs and policies of the network operator. • A "basket" of charging parameters will be provided ... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 6.1 List of parameters | Collection of IP charging information can be based on parameters and service related events recorded by the IP network in real time. Weighting factors may influence the conversion of parameters into charges to the service subscriber. Which parameters are used and how they are weighted is a matter of tariffing and outsi... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 6.2 Description of the parameters | This subclause describes the parameters listed in subclause 6.1 in detail and gives some examples of possible measurements. ETSI ETSI TR 101 734 V1.1.1 (1999-09) 17 A1) Type of access This parameter is related to the capacity provided by the network operator, the maintenance, the redundancy, etc. (e.g. number of links ... |
fba21a1f64d99750ffcd167e0856bd3d | 101 734 | 7 Charging mechanisms required in IP based networks | The following functions and capabilities are part of the charging entity in the network element: • functions for the measuring of the parameters or for monitoring of the charge related events; • an activity generating charging records from the measured and monitored data and reports for the management system; • a stora... |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 1 Scope | The present document gives guidance for workers at fixed radio transmitter sites where the electromagnetic fields in the frequency range from 9 kHz up to 300 GHz may exceed the levels defined for the general public either in the ICNIRP guidelines [1] or in the guidelines laid down by European or National Authorities. T... |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 2 References | For the purposes of this Technical Report (TR), the following reference applies: [1] International Commission on Non-Ionising Radiation Protection - Guidelines for limiting exposure in time-varying electric, magnetic, and electromagnetic fields (up to 300 GHz), Health Physics Volume 74, Number 4, April 1998, pp. 496-52... |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 3 Definitions and abbreviations | |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. Basic restrictions: restrictions on exposure to time-varying electric, magnetic and electromagnetic fields NOTE 1: Depending on the frequency of the field, the physical quantities used to specify these restrictions are current density ... |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply. EM ElectroMagnetic EMF ElectroMagnetic Field ICNIRP International Commission on Non-Ionizing Radiation Protection RF Radio Frequency SAR Specific Absorption Rate |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 4 General Policies | |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 4.1 General Position | • It is the intention that no-one will be exposed to EMF at levels exceeding those stated in the Relevant Recommendations. Access for the general public to areas exceeding the Relevant Recommendations should be prevented. ETSI ETSI TR 101 870 V1.1.1 (2001-11) 8 • Workers may be exposed, during the course of their dutie... |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 4.2 Classification of workers | To qualify as an EM worker or non-EM worker, training and/or instructions should be given as defined in clauses 4.2.1 and 4.2.2 respectively. |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 4.2.1 EM workers | Appropriate training for EM workers should include at least the following: • Being brought up to date on Relevant Recommendations and understanding the potential exposure risks. • Instruction on the operation of all necessary measuring instruments/equipment and • Interpretation of instrument indications/measurement res... |
89e7acbbf7c885a99263890058a04f00 | 101 870 | 4.2.2 Non-EM Worker | The following applies for non-EM Workers: • The individual in question must be provided with appropriate instructions. These should include information about precautions, access procedures and the potential risks from exposure to EMF. • Non-EM Worker classification is only valid for the period that the worker works at ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.