diff --git a/TS-Example.md b/TS-Example.md
index 4befacdc0eba12878dda907fa028e04a2a7572d9..1772aff1b3f6a6e307ebf5b03287fd61014fe195 100644
--- a/TS-Example.md
+++ b/TS-Example.md
@@ -96,6 +96,86 @@ Example Grid Table 3
|Note:* with population density of 100 or fewer persons per square mile |
+-----------------------------------------------------------------------------------------------+
+Example grid table 4
+
++--------------------+-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
+|Ut Control Primitive|Mapping to oneM2M |Description |Reference |Triggering Message |HTTP |
+|message |data types | | | | |
++:===================+:==================+:=================+:========================+:======================================+:=======================================+
+|_UtTrigger_ |_requestPrimitive_ |ONLY essential |oneM2M TS-0004 |**EXAMPLE** **1:** If the test objective is to test **_"Test |
+|_Primitive_ | |parameters |<a href="#_ref_2">[2]</a>|triggers_ _IUT_ _to execute a test case for creation of <_ _AE_ _> |
+| | |included for | |with abels attribute under a_ _CSEBase_ _resource_\"**, then |
+| | |certain test | |triggering message would be serialized as following. |
+| | |case \ | | |
+| | |See NOTE 1 | | |
+| | | | +---------------------------------------+----------------------------------------+
+| | | | |**Request** \ |**Request** \ |
+| | | | |{ \ |**POST** /{SUT\_UT\_APPLICATION\_URL} |
+| | | | |"m2m:rqp" :{ \ |HTTP/1.1 \ |
+| | | | |"op": 1, //indicate CREATE operation \ |**Host**: {SUT\_IP\_ADDRESS:PORT} \ |
+| | | | |"ty": 2, //indicate AE resource type \ |**Content-Length**: {PAYLOAD\_LENGTH} \ |
+| | | | |"to": {TEST\_SYSTEM\_ADDRESS}, \ |**Content-Type**: **application/json** \|
+| | | | |"pc": { \ | \ |
+| | | | |"m2m:ae": { \ |{"m2m:rqp" :{ \ |
+| | | | |"lbl":"UNINITIALIZED" //indicate that |"op": 1, //indicate CREATE operation \ |
+| | | | |attribute labels needs to be included \|"ty": 2, //indicate AE resource type \ |
+| | | | |}, \ |"to": {TEST\_SYSTEM\_ADDRESS}, \ |
+| | | | |} \ |"pc": { \ |
+| | | | |"rvi": "2a" \ } |"m2m:ae": { \ |
+| | | | |} \ |"lbl":"UNINITIALIZED" //indicate that |
+| | | | |} |attribute labels needs to be included \ |
+| | | | | |} \ |
+| | | | | |}, \ |
+| | | | | |"rvi": "2a" \ |
+| | | | | |} \ |
+| | | | | |} \ |
+| | | | +---------------------------------------+----------------------------------------+
+| | | | |**EXAMPLE** **2:** If the test objective is to test **_"Test System |
+| | | | |triggers_ _IUT_ _to execute a test case for delete of <_ _AE_ _> |
+| | | | |_resource_\"**, then triggering message would be serialized as following. |
+| | | | +---------------------------------------+----------------------------------------+
+| | | | |**Request** \ |**Request** \ |
+| | | | |{ \ |**POST** /{SUT\_UT\_APPLICATION\_URL} |
+| | | | |"m2m:rqp" :{ \ |HTTP/1.1 \ |
+| | | | |"op": 4, //indicate DELETE operation \ |**Host**: {SUT\_IP\_ADDRESS:PORT} \ |
+| | | | |"to":{TARGET\_AE\_RESOURCE\_ADDRESS}, \|**Content-Length**: {PAYLOAD\_LENGTH} \ |
+| | | | |//indicate Target AE resource address |**Content-Type**: **application/json** \|
+| | | | |"rvi": "2a" \ | \ |
+| | | | |} \ |{"m2m:rqp" :{ \ |
+| | | | |} |"op": 4, //indicate DELETE peration\ |
+| | | | | |"to":{TARGET\_AE\_RESOURCE\_ADDRESS}, \ |
+| | | | | |//indicate Target AE resource address \ |
+| | | | | |"rvi": "2a" \ |
+| | | | | |} \ |
+| | | | | |} \ |
+| +-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
+| |N/A |Special upper |N/A |**"RESET"** |**Request** \ |
+| | |tester | | |**POST** /{SUT\_UT\_APPLICATION\_URL} |
+| | |commands | | |HTTP/1.1 \ |
+| | | | | |**Host** : {SUT\_IP\_ADDRESS:PORT} \ |
+| | | | | |**X-M2M-UTCMD: Reset** \ |
++--------------------+-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
+|_UtTrigger_ |_responsePrimitive_|ONLY |oneM2M TS-0004 |**Response** \ |**Response** \ |
+|_Ack_ _Primitive_ | |responseStatusCode|<a href="#_ref_2">[2]</a>|{ \ |HTTP/1.1 200 OK \ |
+| | |attribute | |"m2m:rsp": { \ |X-M2M-RSC: 2000 \ |
+| | | included \ | |"rsc": 2000 \ | |
+| | | \ | |} \ | |
+| | | See Note 2. | |} \ | |
+| | | | | \ | |
+| | | | |For any triggering response, it only | |
+| | | | |contains aresponse status code, and the| |
+| | | | |response status code for the triggering| |
+| | | | |operation can only be set to either | |
+| | | | |either 2000 (OK) or 4000 (BAD\_REQUEST)| |
+| | | | |according to the rules for triggering | |
+| | | | | operations. | |
++--------------------+-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
+|NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied. \ |
+|NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |
++----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+
+
# 2 Pipe table examples