|Re: Usage of NSCL [message #1403812 is a reply to message #1403081]
||Mon, 28 July 2014 00:53
| Mahdi Ben Alaya
Registered: November 2013
The NSCL can do all the primitive procedures provided by the GSCL and more, especially that the NSCL knows the ip addresses of all authenticated GSCLs.
Here are some interesting procedures provided by the NSCL:
1) The NSCL acts as proxy to retarget NA requests to the right GSCL. NA sends request to NSCL (e.g GET http://NSCL-IP:NSCL-PORT/om2m/GSCL-ID), NSCL retargets request to GSCL, GSCL sends back response to NSCL, and NSCL retargets back response to NA. The retarget mechanism is seamless for NA. NA don't care of the GSCL IP and port.
2)The NSCL can act as proxy between several GSCLs. If we have GSCL1 and GSCL2 both authenticated to the NSCL, then a sensor connected to GSCL1 is able to send a request to an actuator connected to GSCL2 via the NSCL. GSCL1 don't care of GSCL2 IP and port (and vice versa).
3) NA can create a container on the NSCL, and use it as contactURI to subscribe to GSCL resource. The notifications will be retargeted from GSCL to NSCL and stored on the NA container.
4) A constraint GSCL can announce some applications on the NSCL. Announced resources will be created under NSCL-ID/scls collection. The GSCL benefits of an external data base to store its data. (e.g A smart meter can create all its measuring data on to NSCL)
5) A GSCL can announce some resources on the NSCL to advertise them in order to simplify their discovery by NAs. NAs will easily find, on the NSCL, links to original resources located on the GSCL.
Powered by FUDForum
. Page generated in 0.01830 seconds