Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [om2m-dev] OM2M - Request for Info
Hi Sheetal,

1) By default, there is no resource replication. Each SCL (GSCL or NSCL) has its own resources accessible to users directly or via retargeting. Examples:
  • If we request to create a resource on the GSCL and target the GSCL address: One instance of the resource will be created directly on the GSCL.
  • If we request to create a resource on the NSCL and target the GSCL address: One instance of the resource will be created on the NSCL using retargeting (The GSCL acts as a proxy to forward the request).
  • -> these scenarios still valid if we replace "NSCL" by "GSCL".
2) A Network Application can subscribe to a Gateway Application (or vice-versa) and replicate some data in the NSCL using notifications.

3) Each GSCL has the possibility to announce resources to the NSCL (or vice versa) to:
  • Simplify the discovery of resources by advertising the original GSCL resource reference to the NSCL,
  • Benefit from a remote storage space on the NSCL and create GSCL resources there.
  • -> in both cases, there is no replication, the resource will be created on the NSCL or GSCL.

I hope this helps to clarify this point.
Mahdi

Le 26/06/2014 12:18, Sheetal Kadam a écrit :

Hi,

 

Could you please provide me some info about gscl resource replication on nscl?

Eg: Once gscl registers to nscl, anything you post on gscl should also get replicated on nscl->gscl?

 

Is there something that  I am missing on?

 

Thanks,

Sheetal

DISCLAIMER: This email message and all attachments are confidential and may contain information that is Privileged, Confidential or exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited.  If you have received this email in error, please notify us immediately by return email to mailadmin@xxxxxxxxxxxxxxxx and destroy the original message.  Opinions, conclusions and other information in this message that do not relate to the official of SPAN, shall be understood to be nether given nor endorsed by SPAN.



_______________________________________________
om2m-dev mailing list
om2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/om2m-dev

Back to the top