Commit 2d15d5a7 authored by Yann Garcia's avatar Yann Garcia
Browse files

Rename TP name in MEC015 and MEC030

parent cdf85160
Loading
Loading
Loading
Loading
+418 −0
Original line number Diff line number Diff line
/*
Copyright (c) ETSI 2018-2021.

This software is subject to copyrights owned by ETSI. Non-exclusive permission
is hereby granted, free of charge, to copy, reproduce and amend this file
under the following conditions: It is provided "as is", without warranty of any
kind, expressed or implied.

ETSI shall never be liable for any claim, damages, or other liability arising
from its use or inability of use.This permission does not apply to any documentation
associated with this file for which ETSI keeps all rights reserved. The present
copyright notice shall be included in all copies of whole or part of this
file and shall not imply any sub-license right.
*/

Package MEC_MEC015_SRV_MTS {

   import all from MEC_Common;


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_001_OK"

      Test objective
         "Check that the IUT responds with the Multi-access Traffic Steering information
         when queried by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.3.3.1"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having a bwInfo containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 7.2.4
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vGET containing
                  uri indicating value "mts/v1/mts_info"
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.3.3.1
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "200 OK"
                  body containing
                     mtsCapabilityInfo
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_002_OK"

      Test objective
        "Check that the IUT responds with the list of configured Multi-access Traffic Steering 
        when queried by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.5.3.1"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having a bwInfo containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 6.2.6
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vGET containing
                  uri indicating value "mts/v1/mts_sessions"
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.5.3.1
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "200 OK"
                  body containing
                     oneOrmore mtsList containing
                        mts containing
                            appInsId set to APP_INSTANCE_ID
                        ;
                     ;
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_003_OK"

      Test objective
        "Check that the IUT responds with a configured Multi-access Traffic Steering 
        when queried by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.4.3.1"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having an mtsSessionInfo containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 6.2.6
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vGET containing
                  uri indicating value "mts/v1/mts_sessions",
                    query_parameters containing
                       app_instance_id indicating value APP_INSTANCE_ID
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.4.3.1
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "200 OK"
                  body containing
                     mtsList containing
                        appInsId set to APP_INSTANCE_ID
                     ;
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_003_BR"

      Test objective
         "Check that the IUT responds with an error when
         a request with incorrect parameters is sent by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.4.3.1"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having an mtsSessionInfo containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 6.2.6
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vGET containing
                  uri indicating value "mts/v1/mts_sessions",
                    query_parameters containing
                       // Wrong parameter name should trigger an error response.
                       app_id indicating value APP_INSTANCE_ID
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.4.3.1
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "404 Not Found"
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_003_NF"

      Test objective
         "Check that the IUT responds with an error when
         a request with an unknown resource URI is sent by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.4.3.1"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having an mtsSessionInfo containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 6.2.6
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vGET containing
                  uri indicating value "mts/v1/mts_sessions",
                    query_parameters containing
                       app_id indicating value APP_UNKNOWN_INSTANCE_ID
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.4.3.1
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "400 Bad Request"
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_004_OK_01"

      Test objective
         "Check that the IUT responds with a registration and initialisation approval
         for the requested MTS session requirements sent by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.5.3.2"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having a app_instance containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 7.2.5 and Table 7.2.5-1: Elements of MtsSessionInfo
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vPOST containing
                  uri indicating value "bwm/v1/mts_sessions",
                  body containing
                     mtsSessionInfo containing
                        appInsId indicating value APP_INSTANCE_ID,
                        requestType indicating value 0, // APPLICATION_SPECIFIC_BW_ALLOCATION
                        flowFilter indicating value FLOW_FILTER,
                        qosD indicating value SOME_ALLOCATION,
                        mtsMode indicating value LOW_COST,
                        trafficDirection indicating value "00"
                     ;
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.5.3.2
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "201 Created",
                  Location set to LOCATION, // MEC 015 Table 9.5.3.2-2
                  body containing
                     mtsSessionInfo containing
                        appInsId indicating value APP_INSTANCE_ID,
                        requestType indicating value APPLICATION_SPECIFIC_BW_ALLOCATION,
                        flowFilter indicating value FLOW_FILTER,
                        qosD indicating value SOME_ALLOCATION,
                        mtsMode indicating value 0, // Low Cost
                        trafficDirection indicating value "00"
                     ;
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_004_OK_02"

      Test objective
         "Check that the IUT responds with a registration and initialisation approval
         for the requested MTS session requirements sent by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.5.3.2"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having a app_instance containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 7.2.5 and Table 7.2.5-1: Elements of MtsSessionInfo
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vPOST containing
                  uri indicating value "bwm/v1/mts_sessions",
                  body containing
                     mtsSessionInfo containing
                        appInsId indicating value APP_INSTANCE_ID,
                        requestType indicating value 1, // SESSION_SPECIFIC_BW_ALLOCATION
                        flowFilter indicating value FLOW_FILTER,
                        qosD indicating value SOME_ALLOCATION,
                        mtsMode indicating value 4, // QoS
                        trafficDirection indicating value "00"
                     ;
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.5.3.2
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "201 Created",
                  Location set to LOCATION, // MEC 015 Table 9.5.3.2-2
                  body containing
                     mtsSessionInfo containing
                        appInsId indicating value APP_INSTANCE_ID,
                        requestType indicating value APPLICATION_SPECIFIC_BW_ALLOCATION,
                        flowFilter indicating value FLOW_FILTER,
                        qosD indicating value SOME_ALLOCATION,
                        mtsMode indicating value LOW_COST,
                        trafficDirection indicating value "00"
                     ;
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_MEC016_SRV_MTS_004_NF"

      Test objective
         "Check that the IUT responds with an error when
         a request with incorrect parameters is sent by a MEC Application"

      Reference "ETSI GS MEC 015 V2.1.1, clause 9.5.3.2"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state and
         the MEC_APP entity having a app_instance containing
            appInsId indicating value APP_INSTANCE_ID
         ;
      }

      // MEC 015 Clause 7.2.5 and Table 7.2.5-1: Elements of MtsSessionInfo
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vPOST containing
                  uri indicating value "bwm/v0/mts_sessions", // Invalid version number
                  body containing
                     mtsSessionInfo containing
                        appInsId indicating value APP_INSTANCE_ID,
                        requestType indicating value 0, // APPLICATION_SPECIFIC_BW_ALLOCATION
                        flowFilter indicating value FLOW_FILTER,
                        qosD indicating value SOME_ALLOCATION,
                        mtsMode indicating value LOW_COST,
                        trafficDirection indicating value "00"
                     ;
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 015 Clause 9.5.3.2
               the IUT entity sends a HTTP_RESPONSE containing
                  status_code set to "404 Not Found"
               ;
               to the MEC_APP entity
            }
         }
   }


}
+1 −1
Original line number Diff line number Diff line
@@ -19,7 +19,7 @@ Package MEC_SRV_V2X {


   Test Purpose {
      TP Id "TP_MEC_SRV_V2X_001_OK"
      TP Id "TP_MEC_MEC030_SRV_V2X_001_OK"

      Test objective
        "Check that the IUT responds with the list of configured bandwidth allocations