Commit 29c18f64 authored by Filipe Ferreira's avatar Filipe Ferreira
Browse files

MEC 013 v2.0.3 updates.

parent 22f83985
Loading
Loading
Loading
Loading
+129 −0
Original line number Diff line number Diff line
/*
Copyright (c) ETSI 2018.

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 plat_mp1_ue_area_subscription {

   import all from MEC_Common;


   /*
    * UE Area Subscribe (AREASUB)
    */

    Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_AREASUB_BV_001"

      Test objective
         "Check that the IUT acknowledges the UE area change subscription request when
         commanded by a MEC Application and notifies it when the UE enters the specified circle"

      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.11"

      Config Id Config_MEC_1

      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state
      }

      // MEC 013, clause 5.3.11
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vPOST containing
                  Uri indicating value "location/v2/subscriptions/area/circle",
                  body containing
                     circleNotificationSubscription containing 
                        clientCorrelator indicating value CLIENT_ID, 
                        callbackReference indicating value CALLBACK_URL,
                        address indicating value IP_ADDRESS
                     ;
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 013, clause 7.3.11.2
               the IUT entity sends a HttpMsg containing
                  status_code set to "201 Created"
                  body containing
                     circleNotificationSubscription containing 
                        clientCorrelator indicating value CLIENT_ID, 
                        callbackReference indicating value CALLBACK_URL,
                        address indicating value IP_ADDRESS
                     ;
                  ;
               ;
               to the MEC_APP entity
               
               // TODO: do we have the notification as a separate test? If so, do we have initial conditions
               // set to circleNotificationSubscription above? how? how do we check the proper call to CALLBACK_URL?
               and
               // MEC 013, clause 7.3.11.3
               the IUT entity sends a vPOST containing
                  body containing
                     subscriptionNotification containing
                        terminalLocation containing
                           address set to IP_ADDRESS
                        ;
                     ;
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }

   Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_AREASUB_BV_002"
   
      Test objective
      "Check that the IUT acknowledges the cancellation of UE area change notifications  
      when commanded by a MEC Application"
   
      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.6"
   
      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 IUT entity having a subscriptions containing 
            subscriptionId indicating value SUBSCRIPTION_ID
         ;
      }
   
      // MEC 013, clause 5.3.6
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vDELETE containing
                  Uri indicating value "location/v2/subscriptions/area/circle/{SUBSCRIPTION_ID}" 
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 013, clause 7.3.6.6
               the IUT entity sends a HttpMsg containing
                  status_code set to "204 No Content"
               ;
               to the MEC_APP entity
            }
         }
   }

}
+22 −21
Original line number Diff line number Diff line
@@ -13,23 +13,22 @@ copyright notice shall be included in all copies of whole or part of this
file and shall not imply any sub-license right.
*/

Package plat_mp1_ue_area {
Package plat_mp1_ue_distance_lookup {

   import all from MEC_Common;


   /*
    * UE Area Subscribe (AREA)
    * UE Distance Lookup (DISTLOOK)
    */

   Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_AREA_BV_001"
      TP Id "TP_MEC_PLAT_MP1_DISTLOOK_BV_001"
   
      Test objective
         "Check that the IUT acknowledges the subscription by a MEC Application
         to the notifications on UE movement in relation to a geographic area"
      "Check that the IUT responds with the distance to a UE
      when queried by a MEC Application"
   
      Reference "ETSI GS MEC 013 V1.5.0, clause 7.3.11"
      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.9"
   
      Config Id Config_MEC_1
   
@@ -39,24 +38,26 @@ Package plat_mp1_ue_area {
         the IUT entity being_in idle_state
      }
   
      // MEC 013, clause 5.3.11
      // MEC 013, clause 5.3.9
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vPOST containing
                  Uri indicating value "location/v2/subscriptions/area/circle",
                  body containing
                     circleNotificationSubscription indicating value any_value 
               the IUT entity receives a vGET containing
                  Uri indicating value "location/v2/queries",
                  query_parameters containing
                     address indicating value any_value,
                     latitude indicating value any_value,
                     longitude indicating value any_value
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 013, clause 7.3.11.2
               // MEC 013, clause 7.3.9.2
               the IUT entity sends a HttpMsg containing
                  status_code set to "201 Created"
                  status_code set to "200 OK"
                  body containing
                     circleNotificationSubscription set to any_value 
                     terminalDistance set to any_value
                  ;
               ;
               to the MEC_APP entity
+132 −0
Original line number Diff line number Diff line
@@ -13,23 +13,23 @@ copyright notice shall be included in all copies of whole or part of this
file and shall not imply any sub-license right.
*/

Package plat_mp1_ue_distance {
Package plat_mp1_ue_distance_subscription {

   import all from MEC_Common;


   /*
    * UE Distance Subscribe (DIST)
    * UE Distance Subscribe (DISTSUB)
    */

    Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_DIST_BV_001"
      TP Id "TP_MEC_PLAT_MP1_DISTSUB_BV_001"

      Test objective
         "Check that the IUT acknowledges the subscription by a MEC Application
         to the notifications on UE distance"
         "Check that the IUT acknowledges the UE distance subscription request when commanded by a
         MEC Application and notifies it when (all) the requested UE(s) is (are) within the specified distance"

      Reference "ETSI GS MEC 013 V1.5.0, clause 7.3.10"
      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.10"

      Config Id Config_MEC_1

@@ -46,7 +46,12 @@ Package plat_mp1_ue_distance {
               the IUT entity receives a vPOST containing
                  Uri indicating value "location/v2/subscriptions/distance",
                  body containing
                     distanceNotificationSubscription indicating value any_value
                     distanceNotificationSubscription containing
                        clientCorrelator indicating value CLIENT_ID, 
                        callbackReference indicating value CALLBACK_URL,
                        monitoredAddress indicating value MONITORED_IP_ADDRESS,
                        referenceAddress indicating value IP_ADDRESS
                     ;
                  ;
               ;
               from the MEC_APP entity
@@ -56,8 +61,68 @@ Package plat_mp1_ue_distance {
               the IUT entity sends a HttpMsg containing
                  status_code set to "201 Created"
                  body containing
                     distanceNotificationSubscription set to any_value
                     distanceNotificationSubscription containing
                        clientCorrelator indicating value CLIENT_ID, 
                        callbackReference indicating value CALLBACK_URL,
                        monitoredAddress indicating value MONITORED_IP_ADDRESS,
                        referenceAddress indicating value IP_ADDRESS
                     ;
                  ;
               ;
               to the MEC_APP entity

               // TODO: do we have the notification as a separate test? If so, do we have initial conditions
               // set to distanceNotificationSubscription above? how? how do we check the proper call to CALLBACK_URL?
               and
               // MEC 013, clause 7.3.10.3
               the IUT entity sends a vPOST containing
                  Uri set to CALLBACK_URL 
                  body containing
                     subscriptionNotification containing
                        terminalLocation containing
                           address set to IP_ADDRESS
                        ;
                     ;
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }

   Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_DISTSUB_BV_002"
   
      Test objective
      "Check that the IUT acknowledges the cancellation of UE distance notifications  
      when commanded by a MEC Application"
   
      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.6"
   
      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 IUT entity having a subscriptions containing 
            subscriptionId indicating value SUBSCRIPTION_ID
         ;
      }
   
      // MEC 013, clause 5.3.6
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vDELETE containing
                  Uri indicating value "location/v2/subscriptions/distance/{SUBSCRIPTION_ID}" 
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 013, clause 7.3.6.5
               the IUT entity sends a HttpMsg containing
                  status_code set to "204 No Content"
               ;
               to the MEC_APP entity
            }
+3 −3
Original line number Diff line number Diff line
@@ -19,17 +19,17 @@ Package plat_mp1_ue_information_lookup {


   /*
    * UE Information Lookup (INF)
    * UE Information Lookup (INFLOOK)
    */

   Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_INF_BV_001"
      TP Id "TP_MEC_PLAT_MP1_INFLOOK_BV_001"

      Test objective
         "Check that the IUT responds with the information pertaining to one or more UEs in a particular location
         when queried by a MEC Application"

      Reference "ETSI GS MEC 013 V1.5.0, clause 7.3.3",
      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.3",
         "https://forge.etsi.org/gitlab/mec/gs013-location-api/blob/master/LocationAPI.yaml#/definitions/UserList"

      Config Id Config_MEC_1
+130 −0
Original line number Diff line number Diff line
/*
Copyright (c) ETSI 2018.

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 plat_mp1_ue_information_subscription {

   import all from MEC_Common;

   /*
    * UE Information Subscription (INFSUB)
    */

   Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_INFSUB_BV_001"
   
      Test objective
      "Check that the IUT acknowledges the UE information change subscription request
      when commanded by a MEC Application and notifies it when the location changes"
   
      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.5",
         "https://forge.etsi.org/gitlab/mec/gs013-location-api/blob/master/LocationAPI.yaml#/definitions/zonalTrafficSubscription"
   
      Config Id Config_MEC_1
   
      PICS Selection PIC_MEC_PLAT and PIC_SERVICES

      Initial conditions  with {
         the IUT entity being_in idle_state
      }
   
      // MEC 013, clause 5.3.5
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vPOST containing
                  Uri indicating value "location/v2/subscriptions/zonalTraffic" 
                  body containing
                     zonalTrafficSubscription containing
                        clientCorrelator indicating value CLIENT_ID, 
                        callbackReference indicating value CALLBACK_URL,
                        zoneId indicating value ZONE_ID
                     ;
                  ;
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 013, clause 7.3.5.2
               the IUT entity sends a HttpMsg containing
                  status_code set to "201 Created"
                  body containing
                     zonalTrafficSubscription containing
                        clientCorrelator indicating value CLIENT_ID, 
                        callbackReference indicating value CALLBACK_URL,
                        zoneId indicating value ZONE_ID
                     ;
                  ;
               ;
               to the MEC_APP entity

               // TODO: do we have the notification as a separate test? If so, do we have initial conditions
               // set to zonalTrafficSubscription above? how? how do we check the proper call to CALLBACK_URL?
               and
               // MEC 013, clause 7.3.5.3
               the IUT entity sends a vPOST containing
                  Uri set to CALLBACK_URL 
                  body containing
                     zonalPresenceNotification containing
                        clientCorrelator set to CLIENT_ID, 
                        zoneId indicating value ZONE_ID
                     ;
                  ;
               ;
               to the MEC_APP entity
            }
         }
   }


   Test Purpose {
      TP Id "TP_MEC_PLAT_MP1_INFSUB_BV_002"
   
      Test objective
      "Check that the IUT acknowledges the cancellation of UE information change notifications  
      when commanded by a MEC Application"
   
      Reference "ETSI GS MEC 013 V2.0.3, clause 7.3.6"
   
      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 IUT entity having a subscriptions containing 
            subscriptionId indicating value SUBSCRIPTION_ID
         ;
      }
   
      // MEC 013, clause 5.3.6
      Expected behaviour
         ensure that {
            when {
               the IUT entity receives a vDELETE containing
                  Uri indicating value "location/v2/subscriptions/zonalTraffic/{SUBSCRIPTION_ID}" 
               ;
               from the MEC_APP entity
            }
            then {
               // MEC 013, clause 7.3.6.3
               the IUT entity sends a HttpMsg containing
                  status_code set to "204 No Content"
               ;
               to the MEC_APP entity
            }
         }
   }

}
Loading