Lakhasly

different scenario, where a smart object S2 (i.e., reachable at an IPv6 address) in a sensor network directly provides a remote CoAP service ServiceB.Since the smart object is usually a sensor or an embedded device with limited computational and storage capabilities (and there- fore, as previously described, does not implement a complex logic like OAuth), it delegates the verification of the incoming request to the OAuth service.Since the smart object is usually a sensor or an embedded device with limited computational and storage capabilities (and there- fore, as previously described, does not implement a complex logic like OAuth), it delegates the verification of the incoming request to the OAuth service.Since all the involved entities can use the same protocol, in this case the network gateway acts only as a router without the need to translate incoming and outgoing mes- sages between the external world and the sensor network.

different scenario, where a smart object S2 (i.e., reachable at an IPv6 address) in a sensor network directly provides a remote CoAP service ServiceB. Since different scenario, where a smart object S2 (i.e., reachable at an IPv6 address) in a sensor network directly provides a remote CoAP service ServiceB. Since all the involved entities can use the same protocol, in this case the network gateway acts only as a router without the need to translate incoming and outgoing mes- sages between the external world and the sensor network. The CoAP client CC sends securely and directly to the smart object a request R containing its OAuth credentials and the reference for ServiceB pro- vided by S2. Since the smart object is usually a sensor or an embedded device with limited computational and storage capabilities (and there- fore, as previously described, does not implement a complex logic like OAuth), it delegates the verification of the incoming request to the OAuth service. S2 sends a verification request to IoT-OAS over CoAPs to check R. The IoT-OAS validates the request based on CC’s creden- tials and the type of requested service; it then informs the smart object S2 about whether R can be served or not. S2, according to the response of IoT-OAS, replies to the requesting client with the service outcome or, if the CC is not allowed to access ServiceB, with an error message. all the involved entities can use the same protocol, in this case the network gateway acts only as a router without the need to translate incoming and outgoing mes- sages between the external world and the sensor network. The CoAP client CC sends securely and directly to the smart object a request R containing its OAuth credentials and the reference for ServiceB pro- vided by S2. Since the smart object is usually a sensor or an embedded device with limited computational and storage capabilities (and there- fore, as previously described, does not implement a complex logic like OAuth), it delegates the verification of the incoming request to the OAuth service. S2 sends a verification request to IoT-OAS over CoAPs to check R. The IoT-OAS validates the request based on CC’s creden- tials and the type of requested service; it then informs the smart object S2 about whether R can be served or not. S2, according to the response of IoT-OAS, replies to the requesting client with the service outcome or, if the CC is not allowed to access ServiceB, with an error message.