1 Grid table examples

Example Grid Table 1

Use cases
Characteristic parameter (KPI) Influence quantity Remarks
Max allowed end-to-end latency
Service bit rate: user- experienced data rate Reliability
Message size (byte)
UE Speed
Service Area

Immersive multi-modal VR (UL: device → application server)
5 ms (note 2)
16 Kbit/s -2 Mbit/s (without haptic compression encoding)
0.8 - 200 Kbit/s (with haptic encoding)
99.9% (without haptic compression encoding)
99.999% (with haptic encoding)
1 DoF:2-8 3 DoFs:6-24 6 DoFs:12-48 More DoFs can be supported by the haptic device
Stationary or pedestrian
typically < 100 Km2
Haptic feedback
5 ms
< 1 Mbit/s
99.99% [40]
1500
Sensing information e.g. position and view information generated by the VR glasses
Immersive multi-modal VR (DL: application server → device)
10 ms (note 1)
1-100 Mbit/s
99.9% [40]
1500
Stationary or pedestrian
typically < 100 Km2 (note 5)
Video
10 ms
5-512 Mbit/s
99.9% [40] 50
Audio
5 ms
16 Kbit/s-2 Mbit/s (without haptic) 99.9% (with haptic compression) 1 DoF:2-8 3 DoFs:6-24 6 DoFs:12-48 6 DoFs:12-48 Haptic feedback

Example Grid Table 2

Name DedicatedBearerCnf
Port IPCANctl
Comment
ASP type which returns the result of the execution of DedicatedBearerReq, when it is ocmpleted
Parameter Name Parameter Type Comment
status Status

Example Grid Table 3


Antenna HAAT (meters/feet)
ERP (watts) ERP (watts/MHz)
Emission BW $\leq$ 1 MHz Emission BW > 1MHz
Non-rural areas Rural areas* Non-rural areas Rural areas*
Higher than 1372 (4500) 65 130 65 130
1220 (4000) to 1372(4500) 70 140 70 140
1067 (3500) to 1220 (4000) 75 150 75 150
915 (3000) to 1067(3500) 100 200 100 200
763 (2500) to 915 (3000) 140 280 140 280
610 (2000) to 763 (2500) 200 400 200 400
458 (1500) to 610 (2000) 350 700 350 700
305 (1000) to 458 (1500) 600 1200 600 1200
Up to 305 (1000) 1000 2000 1000 2000
Note:* with population density of 100 or fewer persons per square mile

Example grid table 4

Ut Control Primitive message Mapping to oneM2M data types Description
Reference
Triggering Message
HTTP
UtTrigger Primitive
requestPrimitive
ONLY essential parameters included for certain test case
See NOTE 1
oneM2M TS-0004 <a href="#_ref_2">[2]</a>
EXAMPLE 1: If the test objective is to test _"Test triggers_ IUT to execute a test case for creation of < AE > with abels attribute under a CSEBase resource\", then triggering message would be serialized as following.
Request
{
"m2m:rqp" :{
"op": 1, //indicate CREATE operation
"ty": 2, //indicate AE resource type
"to": {TEST\_SYSTEM\_ADDRESS},
"pc": {
"m2m:ae": {
"lbl":"UNINITIALIZED" //indicate that attribute labels needs to be included
},
}
"rvi": "2a" \ } }
}
Request
POST /{SUT\_UT\_APPLICATION\_URL} HTTP/1.1
Host: {SUT\_IP\_ADDRESS:PORT}
Content-Length: {PAYLOAD\_LENGTH}
Content-Type: application/json

{"m2m:rqp" :{
"op": 1, //indicate CREATE operation
"ty": 2, //indicate AE resource type
"to": {TEST\_SYSTEM\_ADDRESS},
"pc": {
"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
{
"m2m:rqp" :{
"op": 4, //indicate DELETE operation
"to":{TARGET\_AE\_RESOURCE\_ADDRESS},
//indicate Target AE resource address "rvi": "2a"
}
}
Request
POST /{SUT\_UT\_APPLICATION\_URL} HTTP/1.1
Host: {SUT\_IP\_ADDRESS:PORT}
Content-Length: {PAYLOAD\_LENGTH}
Content-Type: application/json

{"m2m:rqp" :{
"op": 4, //indicate DELETE peration
"to":{TARGET\_AE\_RESOURCE\_ADDRESS},
//indicate Target AE resource address
"rvi": "2a"
}
}
N/A
Special upper tester commands
N/A
"RESET"
Request
POST /{SUT\_UT\_APPLICATION\_URL} HTTP/1.1
Host : {SUT\_IP\_ADDRESS:PORT}
X-M2M-UTCMD: Reset
UtTrigger Ack Primitive
responsePrimitive
ONLY responseStatusCode attribute included

See Note 2.
oneM2M TS-0004 <a href="#_ref_2">[2]</a>
Response
{
"m2m:rsp": {
"rsc": 2000
}
}

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.
Response
HTTP/1.1 200 OK
X-M2M-RSC: 2000
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.