oneM2M WI-0120Release Notes diff from v0.0.5 to v0.0.4Provide the schedule of tasks to be performed;
Document Type |
Document Number* |
Title
|
Schedule (TP No.) Start |
Schedule (TP No.) Change Control |
Schedule (TP No.) Freeze |
Schedule (TP No.) Approval |
Lead WG
|
Impacted WGs
|
Comments
|
|---|---|---|---|---|---|---|---|---|---|
TR
|
TR-0077
|
oneM2M and MEC integration scenario and mechanisms
|
TP#66
|
75
|
76
|
77
|
WG2
|
||
TS
|
TS-0042
|
oneM2M and MEC interworking and deployments
|
TP#66
|
75
|
76
|
WG2
| |||
TR
|
TR-0078
|
Developer Guide |
TP#68
|
75
|
76
|
WG | |||
TR
|
TR-0080
|
Features for oneM2M and MEC deployment scenarios
|
TP#70
|
71
|
71
|
71
|
WG2
|
||
T |
T |
TP# |
75
|
76
|
77
|
WG |
Impacted TS/TR |
CR number (when known)
|
Subject of the CR
|
Approved at plenary#
|
Impacted WGs
|
Comments
|
|---|---|---|---|---|---|
TR
|
TR-0001
|
Uses Cases
|
TP#77
|
WG2
|
|
TS
|
TS-0001
|
Functional Architecture
|
TP# |
WG2
| |
TS
|
TS-0004
|
Service Layer Core Protocol
|
TP# |
WG2
| |
TS
|
TS-0018
|
Test and conformance
|
TP# |
WG | |
TS
|
TS-0002
|
Requirements
|
TP# |
WG2
|