Presentation is loading. Please wait.

Presentation is loading. Please wait.

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: 2014-05-22 Agenda Item: TS-0004.

Published byAlannah Miles Modified over 8 years ago

Similar presentations

Presentation on theme: "Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: 2014-05-22 Agenda Item: TS-0004."— Presentation transcript:

1 Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, phjacobs@cisco.com Meeting Date: 2014-05-22 Agenda Item: TS-0004 contribution PRO-2014-0208-Response_Status_Codes_Concepts

2 Response Code - Basic Ranges rs: response code: This parameter indicates whether the operation was successful, unsuccessful or is an acknowledgement Propose first numeric field of multi-field response code is 0000-9999 (constrained integer type) 0000-vvvv indicates successful operation wwww-xxxx indicates unsuccessful operation yyyy-zzzz indicates acknowledgement © 2014 oneM2M Partners PRO-2014-0208-Response_Status_Codes_Concepts 2

3 Response Code – Multi-Field Many response codes expected to only need encoded numeric field e.g. ACKs Some response codes may have additional fields for detailed parameters which are not encoded in response codes e.g. version Some successful response codes expected to have additional fields regarding Warnings Many unsuccessful response codes will have additional fields e.g. List of Request parameter names not supported PRO-2014-0208-Response_Status_Codes_Concepts

4 Mcc vs Mca Response Codes Many response codes will be used at the service level which are not exposed to AEs. – External Protocol/Device management related – Transport Protocol related AE response codes needed per AE Requests only – ROA and reserved numeric field ranges for SOA Plus other reserved numeric field ranges for future – Mcn and Mcc’ – Future releases – Additional protocols – Vendor extensions PRO-2014-0208-Response_Status_Codes_Concepts

5 Response Code – Basic Format Encoded number, oneM2M version, argument1, …, argumentN (TS-0004 data type: constrained integer, list of strings) Use “argument” used since we already use “parameters” and “attributes” All fields mandatory dependent upon encoded number Not included – Support for multiple response codes I.E. only first error/warning detected per validation procedures – Selection mechanism of lite vs. detailed response code Optimizations may be included in subsequent releases – Human readable description – Support for ARC TS “cn may be present in a Response to provide more error information” – Support for ARC TS “cs: status codes (e.g., authorization timeout, etc.).” Encoding of response codes is FFS, new TS-0004 clause and other stage 3 TS’s PRO-2014-0208-Response_Status_Codes_Concepts

Download ppt "Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: 2014-05-22 Agenda Item: TS-0004."

Similar presentations

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: 2014-05-07 Discussion  Source: OBERTHUR Technologies Information  Contact:

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:
Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 2013-12-9 Agenda Item:

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:
WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: 2014-07-28 to 2014-08-01.

WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.
HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: 2014-07-28 (PRO#12.0) Agenda Item: HTTP.

HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: (PRO#12.0) Agenda Item: HTTP.
Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: 2014-03-20 Agenda Item: TBD.

Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.
RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: 2013-10-21 Agenda Item:

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:
2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.
App-ID Use Cases, Syntax and Attributes SEC-2015-0508-App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,

App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,
Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, Meeting Date:

Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, Meeting Date:
OneM2M-ARC-2013-0591-Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.

OneM2M-ARC Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: 2013-11-19 Agenda Item:

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Announcement Resources ARC-2014-1255-Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: 2014-04-07 Agenda Item: Input Contribution.

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: 2015-03-25 Agenda Item:

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
WG 3 Progress Report at TP13 Group Name: oneM2M TP13 Source: Raymond Forbes, LM Ericsson, Meeting Date: 2014-09-22 to 2014-09-27.

WG 3 Progress Report at TP13 Group Name: oneM2M TP13 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
PRO-2014-0516R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,
WG-2 - ARC TP #16 Status Report Group Name: oneM2M TP #16 Source: WG2 Chair (Nicolas Damour – Meeting Date: 2015-03-27 Agenda.

WG-2 - ARC TP #16 Status Report Group Name: oneM2M TP #16 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.
HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: 2015-07-20 Agenda.

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: 2013-11-26 Agenda Item:

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

Similar presentations

Ads by Google