Re: [om2m-dev] [OM2M] Mecanisme of register GSCL to NSCL and NSCL to GSC

[Mahdi Ben Alaya <ben.alaya@xxxxxxx>]

Hello Hao,

I pushed an update on the git repository including the correct GSCL/NSCL 
authentication procedure as described by ETSI.
In the updated version: after starting, the GSCL sends a request to 
register to the NSCL, if successful, the GSCL creates locally the 
required remote NSCL resource based on the "config.ini" file parameters.
The registration request initiated by the NSCL to GSCL is now removed, 
which simplify and optimize the registration procedure.
Thank you for this remark.

Mahdi Ben Alaya,
LAAS-CNRS

Le 07/07/2014 10:09, hua.xu@xxxxxxxxxx a écrit :
> Hi Yassine,
> Thanks very much for your response.
> Could you tell me when you could do this update?
> Because I have to decide to wait for your update or do it in other ways.
>
> Hao XU
>
> -----Message d'origine-----
> De : om2m-dev-bounces@xxxxxxxxxxx [mailto:om2m-dev-bounces@xxxxxxxxxxx] De la part de Yassine Banouar
> Envoyé : vendredi 4 juillet 2014 19:27
> À : OM2M Developer discussions
> Objet : Re: [om2m-dev] [OM2M] Mecanisme of register GSCL to NSCL and NSCL to GSCL
>
> Hi Hao,
>
> What you said is correct, we implemented the registration mechanism using an other procedure. We will try to update the code, taking into account your remark, and push it in the OM2M GIT as soon as possible. An Email will be sent when this will be done.
>
> Thanks.
> Yassine Banouar.
>   
>   
> Le Mercredi 2 Juillet 2014 16:58 CEST, <hua.xu@xxxxxxxxxx> a écrit:
>   
> > 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.
> _______________________________________________
> om2m-dev mailing list
> om2m-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/om2m-dev
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
> _______________________________________________
> om2m-dev mailing list
> om2m-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/om2m-dev