From 66bb8aa9f39f750ce3b2bebce379437932ff68ba Mon Sep 17 00:00:00 2001 From: JaeSeung Song <jssong@sejong.ac.kr> Date: Sun, 10 Nov 2024 17:37:32 +0000 Subject: [PATCH 1/2] Update TS-0002-oneM2M-Requirements.md to add new requirements for consent management --- TS-0002-oneM2M-Requirements.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/TS-0002-oneM2M-Requirements.md b/TS-0002-oneM2M-Requirements.md index d2e31bf..e468df4 100644 --- a/TS-0002-oneM2M-Requirements.md +++ b/TS-0002-oneM2M-Requirements.md @@ -709,6 +709,9 @@ NOTE3: The solution would be complete and will be a part of the oneM2M core func |SER-082<br />See ARC--2018-0062 |The oneM2M System shall support M2M Service Subscriber and M2M Service User profiles specifying their restrictions (e.g. privacy restrictions, max number and/or types of applications and devices the M2M Service Subscriber and its authorized M2M Service Users are allowed to register to the M2M System, the maximum number of resources or bytes of data that the M2M Service Subscriber can store in the M2M System, etc.) and their default configurations (e.g. access control policies, expiration times, max number of content instances, etc.). | | |SER-083<br />See RDM-2019-0054R01 |The oneM2M System shall support access control and authorization mechanisms for the M2M Service Subscriber or M2M Service User information, based on dynamic parameters (e.g. on/off duty time schedule, location, role or job position etc.). |Rel-4 | |SER-084<br />See RDM-2019-0054R01 | The oneM2M System shall be able to access M2M Service Subscriber information or M2M Service User information based on dynamic parameters (e.g. on/off duty time schedule, location, role or job position, etc.) from M2M Applications. |Rel-4 | +|SER-0x1<br />See TR-0062 | The oneM2M System shall support the ability to obtain and record user consent for data processing activities associated with oneM2M resources, ensuring that consent is freely given, specific, informed, and unambiguous, in compliance with requirements from relevant regulations. |Rel-4 | +|SER-0x2<br />See TR-0062 | The oneM2M System shall provide mechanisms for managing consent information, including the ability to update or withdraw consent, specify the scope and purpose of processing activities, and associate each processing activity with one or more oneM2M resources. |Rel-4 | + NOTE 1: The above requirement does not cover items outside of the oneM2M System, e.g. Underlying Networks. -- GitLab From cc257891749dee298fb017a565fc3c2232ac6a8a Mon Sep 17 00:00:00 2001 From: JaeSeung Song <jssong@sejong.ac.kr> Date: Thu, 14 Nov 2024 14:55:24 +0000 Subject: [PATCH 2/2] Update TS-0002-oneM2M-Requirements.md --- TS-0002-oneM2M-Requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TS-0002-oneM2M-Requirements.md b/TS-0002-oneM2M-Requirements.md index e468df4..f06ea38 100644 --- a/TS-0002-oneM2M-Requirements.md +++ b/TS-0002-oneM2M-Requirements.md @@ -709,7 +709,7 @@ NOTE3: The solution would be complete and will be a part of the oneM2M core func |SER-082<br />See ARC--2018-0062 |The oneM2M System shall support M2M Service Subscriber and M2M Service User profiles specifying their restrictions (e.g. privacy restrictions, max number and/or types of applications and devices the M2M Service Subscriber and its authorized M2M Service Users are allowed to register to the M2M System, the maximum number of resources or bytes of data that the M2M Service Subscriber can store in the M2M System, etc.) and their default configurations (e.g. access control policies, expiration times, max number of content instances, etc.). | | |SER-083<br />See RDM-2019-0054R01 |The oneM2M System shall support access control and authorization mechanisms for the M2M Service Subscriber or M2M Service User information, based on dynamic parameters (e.g. on/off duty time schedule, location, role or job position etc.). |Rel-4 | |SER-084<br />See RDM-2019-0054R01 | The oneM2M System shall be able to access M2M Service Subscriber information or M2M Service User information based on dynamic parameters (e.g. on/off duty time schedule, location, role or job position, etc.) from M2M Applications. |Rel-4 | -|SER-0x1<br />See TR-0062 | The oneM2M System shall support the ability to obtain and record user consent for data processing activities associated with oneM2M resources, ensuring that consent is freely given, specific, informed, and unambiguous, in compliance with requirements from relevant regulations. |Rel-4 | +|SER-0x1<br />See TR-0062 | The oneM2M System shall be able to store, manage and access user's consent information for data processing activities associated with oneM2M resources in compliance with requirements from relevant regulations. |Rel-4 | |SER-0x2<br />See TR-0062 | The oneM2M System shall provide mechanisms for managing consent information, including the ability to update or withdraw consent, specify the scope and purpose of processing activities, and associate each processing activity with one or more oneM2M resources. |Rel-4 | -- GitLab