[Fiware-iot] High-level description of Ericsson Gateway

[Farkas, Lorant (NSN - HU/Budapest)]

Hi Tarek,

 

Answers inline.

 

Br,

 

Lorant

 

From: ext T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] 
Sent: Thursday, April 26, 2012 5:55 PM
To: Farkas, Lorant (NSN - HU/Budapest); jakob.saros at ericsson.com
Cc: fiware-iot at lists.fi-ware.eu
Subject: RE: High-level description of Ericsson Gateway

 

Hello Lorant,

 

My initial understanding from "Device Frontend" is that handles interaction between device and gateway. So why should it be in the backend? 

"FI-WARE IoT compliant" devices should be able to connect directly to the backend.

 

...Or what is meant by "device" is really the gateway representing the devices...?

Yes. Gateways should also be handled by the device frontent in the backend.

 

Is there any reference to what functionalities are expected from a "device frontend" at this moment?

All we have is what is described in the Wiki in the architecture specifications deliverable.

 

One final comment: device frontend as a GE might cease to exist, as we are discsussing now about the streamlined architecture.

 

Best regards,

Tarek

 

 

 

From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] 
Sent: 26 April 2012 07:22
To: Elsaleh T Mr (Electronic Eng); jakob.saros at ericsson.com
Cc: fiware-iot at lists.fi-ware.eu
Subject: RE: High-level description of Ericsson Gateway

 

Hello Tarek,

 

The action item is a bit outdated, device handler as GE will not exist under this name any more (pending on approval, of course).

Last week we were discussing the issue that there is no owner for the device handler GE and device frontend GE. Payam volunteered to take a look at one of these GE. 

The additional issue with the device frontend is that the Ericsson asset (gateway asset) speaks a proprietary REST interface on the northbound, implemented by their http server and http-coap proxy, whereas on the backend there is noone to implement the component (earlier this was called device frontend) that discusses with the gateway over this interface.

 

I think it was wrongly captured in the minutes that Payam volunteered to take a look at the device handler, I think he was meaning device frontend.

 

In the new architecture both device frontend and device handler functionalitites should become part of the backend core functionalities GE, I think.

 

The biggest question now is who will implement/specify backend core functionalities GE and your contribution would be welcome here from the frontend perspective because Telefonica will likely not have an interface that discusses with the Ericsson gateway. 

FYI we were announced yesterday that there is one person from Telefonica dedicated to IoT and also a team will be set up on their side. We will discuss with them next week Thursday or Friday and it would be good if you Tarek could also participate in this call, if you are interested in/can contribute to this GE.

 

Including the alternative gateway middleware solution from your side requires further discussions, but the first step would be for you to share document describing the features and its availability as an asset.

 

Thanks & Br,

 

Lorant

 

 

 

From: ext T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] 
Sent: Wednesday, April 25, 2012 7:18 PM
To: Farkas, Lorant (NSN - HU/Budapest); jakob.saros at ericsson.com
Cc: fiware-iot at lists.fi-ware.eu
Subject: RE: High-level description of Ericsson Gateway

 

Hello Lorant, Jakob,

 

I would like to follow up on the action point regarding:

 

IoT04_18042012: "AP Payam to look at the GW description and check if USurrey could contribute to the Device Handler in the backend (open specs, implementation)."

 

As I have been away last week, I would like to clarify what exactly is required here. UoS does have an alternative gateway middleware solution, but what is required exactly from us in order to contribute to the "Device Handler"? is it wrt "gateway-to-backend" (northbound) or "gateway-to-device" (southbound)? 

 

By the way, isn't the Device Handler GE in the Gateway?

 

In terms of compatibility, is this with respect to CoAP, OSGi, or both? In either case, we currently don't support either of them, but can be considered for near future, as we are interested in using CoAP.

 

 

Best regards,

Tarek

 

Tarek Elsaleh

Research Assistant

Centre for Commuication Systems Research (CCSR)

Department of Electronic Engineering

University of Surrey

Guildford, GU2 7XH

Tel: 01483 689485

 

 

 

From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest)
Sent: 18 April 2012 13:06
To: fiware-iot at lists.fi-ware.eu
Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway

 

Dear All,

 

FYI (especially Payam/Tarek).

 

Thanks & Br,

 

Lorant

 

 

From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] 
Sent: Friday, April 13, 2012 6:15 PM
To: Fici Gian Piero; Guerra Sabrina; thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest)
Cc: Jan Höller
Subject: High-level description of Ericsson Gateway

 

Hi,

 

Attached is a description of the Ericsson Gateway for further discussions. Please note that this is a DRAFT! The document includes information of gateway components, i.e. OSGi bundles, and interfaces northbound/southbound. I look forward to hearing your comments.

 

BR/Jakob

 

 

________________________________

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: 04/20/12

________________________________

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2411/4958 - Release Date: 04/25/12

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120427/8d5c2eeb/attachment.html>