Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[om2m-dev] [OM2M] Mecanisme of register GSCL to NSCL and NSCL to GSCL

Hello, everyone

 

I have a question on the procedure to register a GSCL to NSCL.

 

First, what I have understood about the implementation of OM2M :

1.     GSCL send a RequestIndication to the NSCL and wait for ResponseConfirm primitive ;

2.     If successful, NSCL creates local resources for GSCL and sends back a successful response to GSCL, GSCL registers to NSCL successfully ;

3.     NSCL send a RequestIndication to the GSCL and wait for ResponseConfirm primitive ;

4.     If successful, GSCL creates resources for NSCL and sends back a successful response to NSCL, NSCL registers to GSCL successfully.

 

Second, what I have understood about the standard ETSI M2M :

1.     GSCL send a RequestIndication to the NSCL and wait for ResponseConfirm primitive ;

2.     If successful, NSCL creates resources for GSCL and sends back a successful response to GSCL, GSCL registers to NSCL successfully ;

3.     If GSCL receives a positive response, GSCL creates local resources for NSCL with  NSCL id and other default attributes ;

4.     GSCL sends a request to NSCL for its attributes and wait for response.

5.     If NSCL sends back its information, GSCL updates  the attributes locally.

 

The first two steps are the same, but the rest isn’t. Anyone could explain this ?

Thanks.

 

Hao XU

 

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

Back to the top