Skip to content
Snippets Groups Projects

TDE-2024-0007_TS-0019-ATS_v4.2.0_baseline

Open Miguel Angel Reina Ortega requested to merge TS-0019-ATS_v4.2.0_baseline into R4
![~~CAPTION~~](media/image1.png)
@@ -6,17 +5,27 @@
|**oneM2M**<br />**Technical** **Specification** |**oneM2M**<br />**Technical** **Specification** |
|-|-|
|Document Number |oneM2M-TS-0019-V-4.1.1 |
|Document Name: |Abstract Test Suite and Implementation eXtra Information for Test |
|Date: |2024 March 1 |
|Abstract: |Abstract Test Suite and Implementation eXtra Information for Test consists of :<br />- Definition of the Abstract Protocol Tester (APT)<br />- Definition of TTCN-3 test architecture<br />- Development of TTCN-3 test suite, e.g. naming conventions, code documentation, test case structure.<br />- IXIT proforma;<br /> |
|Template Version:23 February 2015 (Do not modify) |Template Version:23 February 2015 (Do not modify) |
+----------------------------------------------------------------+
|**oneM2M** **Technical** \ |
|**Specification** |
+:================+:=============================================+
|Document Number |oneM2M-TS-0019-V-4&lowbar;2&lowbar;0 |
+-----------------+----------------------------------------------+
|Document Name: |Abstract Test Suite and Implementation |
| |eXtra Information for Test |
+-----------------+----------------------------------------------+
|Date: |2024 March 1 |
+-----------------+----------------------------------------------+
|Abstract: |- Definition of the Abstract Protocol Tester |
| | (APT) |
| |- Definition of TTCN-3 test architecture |
| |- Development of TTCN-3 test suite, e.g. |
| | naming conventions, code documentation, test|
| | case structure. |
| |- IXIT proforma; |
+-----------------+----------------------------------------------+
|Template Version:23 February 2015 (Do not modify) |
+----------------------------------------------------------------+
@@ -325,18 +334,31 @@ Both primitives contain another parameters that permits to dynamically configure
- Serialization
- ForceFields: used to force invalid or empty values to certain attributes. This behaviour shall be implemented by the System Adaptor.
Adding a grid table for testing
**Table 5.4.1-1: Mapping of TTCN-3 Primitives to oneM2M Service Primitives**<a name="table_5.4.1-1"></a>
|TTCN-3 Primitive |oneM2M Message |Direction |IUT |
|-|-|-|-|
|M2MRequestPrimitive |Request Primitive |<=> |AE |
|M2MRequestPrimitive |Request Primitive |<=> |CSE |
|M2MResponsePrimitive |Response Primitive |<=> |AE |
|M2MResponsePrimitive |Response Primitive |<=> |CSE |
+----------------------+-------------------+-----------+-----+
|TTCN-3 Primitive |oneM2M Message | Direction | IUT |
+:====================:+:=================:+:=========:+:===:+
| | | <=> | AE |
| M2MRequestPrimitive |Request Primitive +-----------+-----+
| | | <=> | CSE |
+----------------------+-------------------+-----------+-----+
| | | <=> | AE |
| M2MResponsePrimitive |Respomse Primitive +-----------+-----+
| | | <=> | CSE |
+----------------------+-------------------+-----------+-----+
Adding some equations:
$\left[\int_{-infty}^{\infty} f(x) \; dx\right]$
$\log(x)$
$\lim_{x \to \infty} f(x)$
$\displaystyle \frac{\partial f}{\partial x}$
### 5.4.2 mcnPort, mcnPortIn
These ports are used to send and receive the following message sets:
@@ -357,8 +379,6 @@ Two primitives are currently defined for these ports indicated:
Further primitives might be defined to support other underlying networks.
### 5.4.3 mccPortInternal
This port is used to send and receive the following message sets between TTCN-3 components:
@@ -470,11 +490,17 @@ The rules for defining UtTrigger and UtTriggerAck primitives are:
**Table 5.4.4.2.2-3: Definition of ResponseStatusCode for UtTriggerAck primitive**<a name="table_5.4.4.2.2-3"></a>
|Response Status Code Description |Response Status Code Value |Interpretation |
|-|-|-|
|OK |2000 |The SUT receives successfully the triggering message from Test System |
|BAD\_REQUEST |4000 |The SUT does not interpret correctly the UtTrigger primitive |
|NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |
+---------------------------------+---------------------------+-----------------------------------------------+
|Response Status Code Description |Response Status Code Value |Interpretation |
+:================================+:==========================+:==============================================+
|OK |2000 |The SUT receives successfully the triggering |
| | |message from Test System |
+---------------------------------+---------------------------+-----------------------------------------------+
|BAD\_REQUEST |4000 |The SUT does not interpret correctly the |
| | |UtTrigger primitive |
+---------------------------------+---------------------------+-----------------------------------------------+
|NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |
+-------------------------------------------------------------------------------------------------------------+
Loading