Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
TS-Example
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Specifications
Technical Specifications
TS-Example
Commits
90af50f9
Commit
90af50f9
authored
3 months ago
by
Miguel Angel Reina Ortega
Browse files
Options
Downloads
Patches
Plain Diff
Add example 4 of grid table
parent
c0dcb1e5
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
TS-Example.md
+80
-0
80 additions, 0 deletions
TS-Example.md
with
80 additions
and
0 deletions
TS-Example.md
+
80
−
0
View file @
90af50f9
...
@@ -96,6 +96,86 @@ Example Grid Table 3
...
@@ -96,6 +96,86 @@ Example Grid Table 3
|Note:
*
with population density of 100 or fewer persons per square mile |
|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
# 2 Pipe table examples
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment