Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [leshan-dev] [cf-dev] REST Connector for CF
Hi,

I don't think the proxy will work as the devices will not generate the HTTP message. Please have a look and let me know if I am wrong.

It is all because of the Non IP support of the 3GPP NBIOT. All these devices will not have an IP address. These devices will communicate using Data Over NAS. Now, when the CoAP message generated by the device reaches SCEF(Service Capability Exposure Function 3GPP TS 23682), it will post the received CoAP message over HTTP REST to the CoAP server. So, what I am worried here is when SCEF  posts the CoAP message to over HTTP, how will it do. The entire CoAP message will be sent as a HTTP payload.
Now, how will the message structure look like?

[3GPP-TS_24.301] defines the transport of user data via the control plane procedure. Two dedicated NAS messages are specified for transferring small data via the MME, see CONTROL PLANE SERVICE REQUEST message and ESM DATA TRANSPORT message in 3GPP [3GPP-TS_24.301]. For initiation of user data transport via the control plane the CONTROL PLAN SERVICE REQUEST message is used which may include ESM DATA TRANSPORT message in its IE “ESM message container”. After the initiation of user data transport via control plane the separate ESM DATA TRANSPORT messages may be used for further transport of user data.


CoAP messages are placed into the IE “User data container” of the ESM DATA TRANSPORT message.


In case DTLS is used the same applies to the DTLS messages.




On Wed, Feb 15, 2017 at 5:30 PM, Hudalla Kai (INST/ESY1) <Kai.Hudalla@xxxxxxxxxxxx> wrote:
On Fri, 2017-02-10 at 23:12 +0530, Santos Das wrote:
> Hi,
>
> I am looking for transporting COAP message as a HTTP payload.
>
Is there a particular reason why you want to do that? CoAP has been designed as a
 "lightweight, binary" alternative to HTTP following similar paradigms like the
GET, POST, PUT etc semantics and headers (options in CoAP). My advice would be to
use the HTTP proxy to "bridge" between CoAP and HTTP ...

> Thanks. Santos
>
> On Thu, Feb 9, 2017 at 10:57 PM, Hudalla Kai (INST/ESY1) <Kai.Hudalla@bosch-si.
> com> wrote:
> > I am not familiar with the NB-IoT stuff envisioned for LWM2M 1.1.
> > If all you need to do is translating hence and forth between CoAP and HTTP
> > you
> > might consider taking a look at Californium's proxy component (californium-
> > proxy).
> >
> > This does not require/involve the implementation of a dedicated REST
> > Connector
> > but instead you simply send standard CoAP messages over UDP to the HTTP proxy
> > which then forwards the message payload via HTTP to the target endpoint.
> >
> > --
> > Mit freundlichen Grüßen / Best regards
> >
> > Kai Hudalla
> > Chief Software Architect
> >
> > Bosch Software Innovations GmbH
> > Schöneberger Ufer 89-91
> > 10785 Berlin
> > GERMANY
> > www.bosch-si.com
> >
> > Registered office: Berlin, Register court: Amtsgericht Charlottenburg,
> > HRB 148411 B;
> > Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
> >
> > On Thu, 2017-02-09 at 16:46 +0530, Santos Das wrote:
> > > Hi,
> > >
> > > To clarify more on this what I am looking is how to send CoAP over HTTP to
> > > SCEF.
> > >
> > > Thanks, Santos
> > >
> > > On Thu, Feb 9, 2017 at 2:55 PM, Santos Das <santos.das@xxxxxxxxx> wrote:
> > > > Hi,
> > > >
> > > > Can some one please help by providing some information on how to develop
> > a
> > > > REST based connector.
> > > >
> > > > Requirement - Send the LWM2M message to SCEF (3GPP TS 23.682)
> > > >
> > > > I have put the LWM2M over NBIOT picture from OMA-TS-LightWeightM2M-V1_1-
> > > > 20160902-D here for every ones reference.
> > > >
> > > > For example, let us consider how will we send the LWM2M message through
> > the
> > > > SCEF path which is REST based.
> > > >
> > > > I have few questions on the probable implementation.
> > > >
> > > > 1.  I see there are RFCs defined for CoAP transmission over TCP and UDP.
> > But,
> > > > I don't see one for Non-IP. Does anyone have it?
> > > >
> > > > 2.  Has there been any work already started on this?
> > > >
> > > > 3.  We have to build a REST connector to take the payload I believe after
> > > > DTLS and then sent it over REST.  Any help on how to build a connector? I
> > > > looked at the TCP connector but it seems a bit more complex. Any help on
> > this
> > > > would be appreciated.
> > > >
> > > >
> > > >
> > > >
> > > > Thanks, Santos
> > > >
> > >
> > > _______________________________________________
> > > cf-dev mailing list
> > > cf-dev@xxxxxxxxxxx
> > > To change your delivery options, retrieve your password, or unsubscribe
> > from
> > > this list, visit
> > > https://dev.eclipse.org/mailman/listinfo/cf-dev
> > _______________________________________________
> > cf-dev mailing list
> > cf-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/cf-dev
>
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cf-dev
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev

Back to the top