Commit 690acaeb authored by Philip Makedonski's avatar Philip Makedonski
Browse files

* removed examples (already copied to examples repository)

parent a1b00e77

examples/org.etsi.mts.tdl.examples/.project

deleted100644 → 0
+0 −17
Original line number Diff line number Diff line 
<?xml version="1.0" encoding="UTF-8"?>

<projectDescription>

	<name>org.etsi.mts.tdl.examples</name>

	<comment></comment>

	<projects>

	</projects>

	<buildSpec>

		<buildCommand>

			<name>org.eclipse.xtext.ui.shared.xtextBuilder</name>

			<arguments>

			</arguments>

		</buildCommand>

	</buildSpec>

	<natures>

		<nature>org.eclipse.xtext.ui.shared.xtextNature</nature>

	</natures>

</projectDescription>

examples/org.etsi.mts.tdl.examples/es_20311901v010401p4/AnnexB2.tdlan2

deleted100644 → 0
+0 −149
Original line number Diff line number Diff line 
//Translated from [i.5], Section 7.1.3.

Package Layer_2_DL_SCH_Data_Transfer {

  //Procedures carried out by a component of a test configuration 

  //or an actor during test execution

  Action preCondition : "Pre-test Conditions: 

            RRC Connection Reconfiguration" ;

  Action preamble : "Preamble:

          The generic procedure to get UE in test state Loopback 

          Activated (State 4) according to TS 36.508 clause 4.5 

          is executed, with all the parameters as specified in the 

          procedure except that the RLC SDU size is set to return no 

          data in uplink. 

          (reference corresponding behavior once implemented" ;



  //User-defined verdicts

  //Alternatively the predefined verdicts may be used as well 

  Type Verdict ;

  Verdict PASS;

  Verdict FAIL;

  

  //User-defined annotation types

  Annotation TITLE ;         //Test description title

  Annotation STEP ;          //Step identifiers in source documents

  Annotation PROCEDURE ;     //Informal textual description of a test step 

  Annotation PRECONDITION ;  //Identify pre-condition behaviour

  Annotation PREAMBLE ;      //Identify preamble behaviour. 

  

  //Test objectives (copied verbatim from source document)

  Test Objective TP1 {

    from : "36523-1-a20_s07_01.doc::7.1.3.1.1 (1)" ;

    description : "with { UE in E-UTRA RRC_CONNECTED state }

             ensure that {

               when { UE receives downlink assignment on the PDCCH 

                      for the UE’s C-RNTI and receives data in the 

                  associated subframe and UE performs HARQ 

                  operation }

                 then { UE sends a HARQ feedback on the HARQ 

                  process }

                   }" ;

  }

  Test Objective TP2 {

    from : "36523-1-a20_s07_01.doc::7.1.3.1.1 (2)" ;

    description : "with { UE in E-UTRA RRC_CONNECTED state }

             ensure that {

               when { UE receives downlink assignment on the PDCCH 

                      with a C-RNTI unknown by the UE and data is 

                  available in the associated subframe }

               then { UE does not send any HARQ feedback on the 

                  HARQ process }

             }" ;

  }



  //Relevant data definitions

  Type PDU; 

  PDU mac_pdu ;

  

  Type ACK ;

  ACK harq_ack ;



  Type C_RNTI;

  C_RNTI ue;

  C_RNTI unknown; 

  

  Type PDCCH (optional c_rnti of type C_RNTI);

  PDCCH pdcch();



  Type CONFIGURATION;

  CONFIGURATION RRCConnectionReconfiguration ;

  

  //User-defined time units

  Time Second;

  Second five;

  

  //Gate type definitions

  Gate Type defaultGT accepts ACK, PDU, PDCCH, C_RNTI, CONFIGURATION ;



  //Component type definitions

  Component Type defaultCT having {

    gate g of type defaultGT;

  }

  

  //Test configuration definition

  Test Configuration defaultTC {

    create Tester SS of type defaultCT;

    create SUT UE of type defaultCT ;

    connect UE.g to SS.g ;

  }

  

  //Test description definition

  Test Description TD_7_1_3_1 uses configuration defaultTC {

    //Pre-conditions and preamble from the source document

    perform action preCondition with { PRECONDITION ; } ;

    perform action preamble  with { PREAMBLE ; } ;

      

    //Test sequence

    SS.g sends pdcch (c_rnti=ue) to UE.g with { 

      STEP : "1" ;

      PROCEDURE : "SS transmits a downlink assignment 

             including the C-RNTI assigned to 

             the UE" ;

    } ;

    SS.g sends mac_pdu to UE.g with {

      STEP : "2" ;

      PROCEDURE : "SS transmits in the indicated 

             downlink assignment a RLC PDU in 

             a MAC PDU" ;

    } ;

    UE.g sends harq_ack to SS.g with {

      STEP : "3" ;

      PROCEDURE : "Check: Does the UE transmit an 

             HARQ ACK on PUCCH?" ;

      test objectives : TP1 ;

    } ;

    set verdict to PASS ;

    SS.g sends pdcch (c_rnti=unknown) to UE.g with {

      STEP : "4" ;

      PROCEDURE : "SS transmits a downlink assignment 

               to including a C-RNTI different from 

             the assigned to the UE" ;  

    };

    SS.g sends mac_pdu to UE.g with {

      STEP : "5" ; 

      PROCEDURE : "SS transmits in the indicated 

             downlink assignment a RLC PDU in 

             a MAC PDU" ;

    } ;

      

    //Interpolated original step 6 into an alternative behaviour,

    //covering both the incorrect and the correct behaviours of the UE 

    alternatively {

      UE.g sends harq_ack to SS.g ;

        set verdict to FAIL ;

    } or {

        gate SS.g is quiet for five ;

      set verdict to PASS ;

    } with {

            STEP : "6" ;

            PROCEDURE : "Check: Does the UE send any HARQ ACK 

                       on PUCCH?" ;

            test objectives : TP2 ;

    }

  } with {

    Note  : "Note 1: For TDD, the timing of ACK/NACK is not

         constant as FDD, see Table 10.1-1 of TS 36.213." ;

  }

} with {

  Note : "Taken from 3GPP TS 36.523-1 V10.2.0 (2012-09)" ;

  TITLE : "Correct handling of DL assignment / Dynamic case" ;

}
 
 No newline at end of file

examples/org.etsi.mts.tdl.examples/es_20311901v010401p4/AnnexB2.tdlan2.tdl

deleted100644 → 0
+0 −129
Original line number Diff line number Diff line 
<?xml version="1.0" encoding="UTF-8"?>

<tdl:Package xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tdl="http://www.etsi.org/spec/TDL/1.4.1" name="Layer_2_DL_SCH_Data_Transfer">

  <comment body="&quot;Taken from 3GPP TS 36.523-1 V10.2.0 (2012-09)&quot;"/>

  <annotation value="&quot;Correct handling of DL assignment / Dynamic case&quot;" key="//@packagedElement.5"/>

  <packagedElement xsi:type="tdl:Action" name="preCondition" body="&quot;Pre-test Conditions: &#xA;            RRC Connection Reconfiguration&quot;"/>

  <packagedElement xsi:type="tdl:Action" name="preamble" body="&quot;Preamble: &#xA;          The generic procedure to get UE in test state Loopback &#xA;          Activated (State 4) according to TS 36.508 clause 4.5 &#xA;          is executed, with all the parameters as specified in the &#xA;          procedure except that the RLC SDU size is set to return no &#xA;          data in uplink. &#xA;          (reference corresponding behavior once implemented&quot;"/>

  <packagedElement xsi:type="tdl:SimpleDataType" name="Verdict"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="PASS" dataType="//@packagedElement.2"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="FAIL" dataType="//@packagedElement.2"/>

  <packagedElement xsi:type="tdl:AnnotationType" name="TITLE"/>

  <packagedElement xsi:type="tdl:AnnotationType" name="STEP"/>

  <packagedElement xsi:type="tdl:AnnotationType" name="PROCEDURE"/>

  <packagedElement xsi:type="tdl:AnnotationType" name="PRECONDITION"/>

  <packagedElement xsi:type="tdl:AnnotationType" name="PREAMBLE"/>

  <packagedElement xsi:type="tdl:TestObjective" name="TP1" description="&quot;with { UE in E-UTRA RRC_CONNECTED state }&#xA;             ensure that {&#xA;               when { UE receives downlink assignment on the PDCCH &#xA;                      for the UE’s C-RNTI and receives data in the &#xA;                  associated subframe and UE performs HARQ &#xA;                  operation }&#xA;                 then { UE sends a HARQ feedback on the HARQ &#xA;                  process }&#xA;                   }&quot;">

    <objectiveURI>&quot;36523-1-a20_s07_01.doc::7.1.3.1.1 (1)&quot;</objectiveURI>

  </packagedElement>

  <packagedElement xsi:type="tdl:TestObjective" name="TP2" description="&quot;with { UE in E-UTRA RRC_CONNECTED state }&#xA;             ensure that {&#xA;               when { UE receives downlink assignment on the PDCCH &#xA;                      with a C-RNTI unknown by the UE and data is &#xA;                  available in the associated subframe }&#xA;               then { UE does not send any HARQ feedback on the &#xA;                  HARQ process }&#xA;             }&quot;">

    <objectiveURI>&quot;36523-1-a20_s07_01.doc::7.1.3.1.1 (2)&quot;</objectiveURI>

  </packagedElement>

  <packagedElement xsi:type="tdl:SimpleDataType" name="PDU"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="mac_pdu" dataType="//@packagedElement.12"/>

  <packagedElement xsi:type="tdl:SimpleDataType" name="ACK"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="harq_ack" dataType="//@packagedElement.14"/>

  <packagedElement xsi:type="tdl:SimpleDataType" name="C_RNTI"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="ue" dataType="//@packagedElement.16"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="unknown" dataType="//@packagedElement.16"/>

  <packagedElement xsi:type="tdl:StructuredDataType" name="PDCCH">

    <member name="c_rnti" dataType="//@packagedElement.16" isOptional="true"/>

  </packagedElement>

  <packagedElement xsi:type="tdl:StructuredDataInstance" name="pdcch" dataType="//@packagedElement.19"/>

  <packagedElement xsi:type="tdl:SimpleDataType" name="CONFIGURATION"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="RRCConnectionReconfiguration" dataType="//@packagedElement.21"/>

  <packagedElement xsi:type="tdl:Time" name="Second"/>

  <packagedElement xsi:type="tdl:SimpleDataInstance" name="five" dataType="//@packagedElement.23"/>

  <packagedElement xsi:type="tdl:GateType" name="defaultGT" dataType="//@packagedElement.14 //@packagedElement.12 //@packagedElement.19 //@packagedElement.16 //@packagedElement.21"/>

  <packagedElement xsi:type="tdl:ComponentType" name="defaultCT">

    <gateInstance name="g" type="//@packagedElement.25"/>

  </packagedElement>

  <packagedElement xsi:type="tdl:TestConfiguration" name="defaultTC">

    <componentInstance name="SS" type="//@packagedElement.26" role="Tester"/>

    <componentInstance name="UE" type="//@packagedElement.26"/>

    <connection>

      <endPoint component="//@packagedElement.27/@componentInstance.1" gate="//@packagedElement.26/@gateInstance.0"/>

      <endPoint component="//@packagedElement.27/@componentInstance.0" gate="//@packagedElement.26/@gateInstance.0"/>

    </connection>

  </packagedElement>

  <packagedElement xsi:type="tdl:TestDescription" name="TD_7_1_3_1" testConfiguration="//@packagedElement.27">

    <behaviourDescription>

      <behaviour xsi:type="tdl:CompoundBehaviour">

        <comment body="&quot;Note 1: For TDD, the timing of ACK/NACK is not&#xA;         constant as FDD, see Table 10.1-1 of TS 36.213.&quot;"/>

        <block>

          <behaviour xsi:type="tdl:ActionReference" action="//@packagedElement.0">

            <annotation key="//@packagedElement.8"/>

          </behaviour>

          <behaviour xsi:type="tdl:ActionReference" action="//@packagedElement.1">

            <annotation key="//@packagedElement.9"/>

          </behaviour>

          <behaviour xsi:type="tdl:Message" sourceGate="//@packagedElement.27/@connection.0/@endPoint.1">

            <target targetGate="//@packagedElement.27/@connection.0/@endPoint.0">

              <annotation value="&quot;1&quot;" key="//@packagedElement.6"/>

              <annotation value="&quot;SS transmits a downlink assignment &#xA;             including the C-RNTI assigned to &#xA;             the UE&quot;" key="//@packagedElement.7"/>

            </target>

            <argument xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.20">

              <argument parameter="//@packagedElement.19/@member.0">

                <dataUse xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.17"/>

              </argument>

            </argument>

          </behaviour>

          <behaviour xsi:type="tdl:Message" sourceGate="//@packagedElement.27/@connection.0/@endPoint.1">

            <target targetGate="//@packagedElement.27/@connection.0/@endPoint.0">

              <annotation value="&quot;2&quot;" key="//@packagedElement.6"/>

              <annotation value="&quot;SS transmits in the indicated &#xA;             downlink assignment a RLC PDU in &#xA;             a MAC PDU&quot;" key="//@packagedElement.7"/>

            </target>

            <argument xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.13"/>

          </behaviour>

          <behaviour xsi:type="tdl:Message" testObjective="//@packagedElement.10" sourceGate="//@packagedElement.27/@connection.0/@endPoint.0">

            <annotation value="&quot;3&quot;" key="//@packagedElement.6"/>

            <annotation value="&quot;Check: Does the UE transmit an &#xA;             HARQ ACK on PUCCH?&quot;" key="//@packagedElement.7"/>

            <target targetGate="//@packagedElement.27/@connection.0/@endPoint.1"/>

            <argument xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.15"/>

          </behaviour>

          <behaviour xsi:type="tdl:VerdictAssignment">

            <verdict xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.3"/>

          </behaviour>

          <behaviour xsi:type="tdl:Message" sourceGate="//@packagedElement.27/@connection.0/@endPoint.1">

            <target targetGate="//@packagedElement.27/@connection.0/@endPoint.0">

              <annotation value="&quot;4&quot;" key="//@packagedElement.6"/>

              <annotation value="&quot;SS transmits a downlink assignment &#xA;               to including a C-RNTI different from &#xA;             the assigned to the UE&quot;" key="//@packagedElement.7"/>

            </target>

            <argument xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.20">

              <argument parameter="//@packagedElement.19/@member.0">

                <dataUse xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.18"/>

              </argument>

            </argument>

          </behaviour>

          <behaviour xsi:type="tdl:Message" sourceGate="//@packagedElement.27/@connection.0/@endPoint.1">

            <target targetGate="//@packagedElement.27/@connection.0/@endPoint.0">

              <annotation value="&quot;5&quot;" key="//@packagedElement.6"/>

              <annotation value="&quot;SS transmits in the indicated &#xA;             downlink assignment a RLC PDU in &#xA;             a MAC PDU&quot;" key="//@packagedElement.7"/>

            </target>

            <argument xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.13"/>

          </behaviour>

          <behaviour xsi:type="tdl:AlternativeBehaviour" testObjective="//@packagedElement.11">

            <annotation value="&quot;6&quot;" key="//@packagedElement.6"/>

            <annotation value="&quot;Check: Does the UE send any HARQ ACK &#xA;                       on PUCCH?&quot;" key="//@packagedElement.7"/>

            <block>

              <behaviour xsi:type="tdl:Message" sourceGate="//@packagedElement.27/@connection.0/@endPoint.0">

                <target targetGate="//@packagedElement.27/@connection.0/@endPoint.1"/>

                <argument xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.15"/>

              </behaviour>

              <behaviour xsi:type="tdl:VerdictAssignment">

                <verdict xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.4"/>

              </behaviour>

            </block>

            <block>

              <behaviour xsi:type="tdl:Quiescence" gateReference="//@packagedElement.27/@connection.0/@endPoint.1">

                <period xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.24"/>

              </behaviour>

              <behaviour xsi:type="tdl:VerdictAssignment">

                <verdict xsi:type="tdl:DataInstanceUse" dataInstance="//@packagedElement.3"/>

              </behaviour>

            </block>

          </behaviour>

        </block>

      </behaviour>

    </behaviourDescription>

  </packagedElement>

</tdl:Package>

examples/org.etsi.mts.tdl.examples/es_20311901v010401p4/AnnexB3.tdlan2

deleted100644 → 0
+0 −129
Original line number Diff line number Diff line 
//Translated from [i.6], Section 4.5.1.

Package IMS_NNI_General_Capabilities {

    //Procedures carried out by a component of a test configuration 

    //or an actor during test execution

    Action preConditions : "Pre-test conditions:

                 - HSS of IMS_A and of IMS B is configured according to table 1

                 - UE_A and UE_B have IP bearers established to their respective

                   IMS networks as per clause 4.2.1

                 - UE_A and IMS_A configured to use TCP for transport

                 - UE_A is registered in IMS_A using any user identity

                 - UE_B is registered user of IMS_B using any user identity

                 - MESSAGE request and response has to be supported at II-NNI 

                   (ETSI TS 129 165 [16]

                 see tables 6.1 and 6.3)" ;



  //User-defined verdicts

  //Alternatively the predefined verdicts may be used as well 

  Type Verdict ;

    Verdict PASS ;

    Verdict FAIL ; 



    //User-defined annotation types

    Annotation TITLE ;         //Test description title

    Annotation STEP ;          //Step identifiers in source documents

    Annotation PROCEDURE ;     //Informal textual description of a test step 

    Annotation PRECONDITION ;  //Identify pre-condition behaviour

    Annotation PREAMBLE ;      //Identify preamble behaviour. 

    Annotation SUMMARY ;       //Informal textual description of test sequence



    //Test objectives (copied verbatim from source document)

    Test Objective TP_IMS_4002_1 {

        //Location in source document

        from : "ts_18601102v030101p.pdf::4.5.1.1 (CC 1)" ;

        //Further reference to another document

        from : "ETSI TS 124 229 [1], clause 4.2A, paragraph 1" ;

        description : "ensure that {

                           when { UE_A sends a MESSAGE to UE_B

                                  containing a Message_Body greater than 1 300 

                                  bytes } 

                           then { IMS_B receives the MESSAGE containing the 

                                  Message_Body greater than 1 300 bytes }

                         }" ;

    }

    Test Objective UC_05_I {

        //Only a reference to corresponding section in the source document

        from : "ts_18601102v030101p.pdf::4.4.4.2" ;

    }

    

    //Relevant data definitions

    Type MSG (optional TCP of type CONTENT);

    MSG MESSAGE() ;

    MSG DING() ;

    MSG DELIVERY_REPORT() ;

    MSG M_200_OK();

    

    Type CONTENT ;

    CONTENT tcp;

    

    Time Second;

    Second default_timeout;



    //Gate type definitions.

    Gate Type defaultGT accepts MSG, CONTENT ;

    

    //Component type definitions

    //In this case they may also be reduced to a single component type

    Component Type USER having {

        gate g of type defaultGT ;

    }

    Component Type UE having {

        gate g of type defaultGT ;

    }

    Component Type IMS having {

        gate g of type defaultGT ;

    }

    Component Type IBCF having {

        gate g of type defaultGT ;

    }



    //Test configuration definition

    Test Configuration CF_INT_CALL {

      create Tester USER_A of type USER;

      create Tester UE_A of type UE;

      create Tester IMS_A of type IMS;

      create Tester IBCF_A of type IBCF;

      create Tester IBCF_B of type IBCF;

      create SUT IMS_B of type IMS;

      create Tester UE_B of type UE;

      create Tester USER_B of type USER;

        connect USER_A.g to UE_A.g ;

        connect UE_A.g to IMS_A.g ;

        connect IMS_A.g to IBCF_A.g ;

        connect IBCF_A.g to IBCF_B.g ;

        connect IBCF_B.g to IMS_B.g ;

        connect IMS_B.g to UE_B.g ;

        connect UE_B.g to USER_B.g ;

    }



    //Test description definition

    Test Description TD_IMS_MESS_0001 uses configuration CF_INT_CALL {

            //Pre-conditions from the source document

            perform action preConditions with { PRECONDITION ; };

            

            //Test sequence

            USER_A.g sends MESSAGE to UE_A.g with { STEP : "1" ; } ;

            UE_A.g sends MESSAGE to IMS_A.g with { STEP : "2" ; } ;

            IMS_A.g sends MESSAGE to IBCF_A.g with { STEP : "3" ; } ;

            IBCF_A.g sends MESSAGE to IBCF_B.g with { STEP : "4" ; } ;

            IBCF_B.g sends MESSAGE (TCP = tcp) to IMS_B.g with { STEP : "5" ; } ;

            IMS_B.g sends MESSAGE to UE_B.g with { STEP : "6" ; } ;

            UE_B.g sends DING to USER_B.g with { STEP : "7" ; } ;

            UE_B.g sends M_200_OK to IMS_B.g with { STEP : "8" ; } ;

            IMS_B.g sends M_200_OK to IBCF_B.g with { STEP : "9" ; } ;

            IBCF_B.g sends M_200_OK to IBCF_A.g with { STEP : "10" ; } ;

            IBCF_A.g sends M_200_OK to IMS_A.g with { STEP : "11" ; } ;

            IMS_A.g sends M_200_OK to UE_A.g with { STEP : "12" ; } ;

            alternatively {

                UE_A.g sends DELIVERY_REPORT to USER_A.g with { STEP : "13" ; } ;

            } or {

                gate USER_A.g is quiet for default_timeout;

            } 

    } with {

        SUMMARY : "IMS network shall support SIP messages greater than

                           1 500 bytes" ;

    }

} with {

    Note : "Taken from ETSI TS 186 011-2 [i.3] V3.1.1 (2011-06)" ;

    TITLE : "SIP messages longer than 1 500 bytes" ;

}

examples/org.etsi.mts.tdl.examples/es_20311901v010401p4/AnnexB3.tdlan2.tdl

deleted100644 → 0
+0 −187

File deleted.

Preview size limit exceeded, changes collapsed.