Hi Manoj

In that case might I suggest looking at the Apache Felix UPnP project?

https://felix.apache.org/documentation/subprojects/apache-felix-upnp.html 
<https://felix.apache.org/documentation/subprojects/apache-felix-upnp.html>

It has been around for a while, so there’s probably some better linking to the 
docs on the old cwiki site 
https://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+UPnP 
<https://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+UPnP>

Regards,

Tim


> On 20 Oct 2016, at 08:43, manoj.vrajam...@wipro.com wrote:
> 
> Hi Tim,
>  
> I am looking for a proof of concept. So any protocol would suffice.. Do you 
> suggest any ready protocols? How about UPnP ?
> How do I achieve the same in UPnP?  (or any other – for that matter) J
>  
> Thanks,
> Manoj
> From: osgi-dev-boun...@mail.osgi.org <mailto:osgi-dev-boun...@mail.osgi.org> 
> [mailto:osgi-dev-boun...@mail.osgi.org 
> <mailto:osgi-dev-boun...@mail.osgi.org>] On Behalf Of Tim Ward
> Sent: 20 October 2016 13:09
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org 
> <mailto:osgi-dev@mail.osgi.org>>
> Subject: Re: [osgi-dev] Query
>  
> ** This mail has been sent from an external source **
> 
> Hi Manoj,
>  
> The ZigBee specification is very new (hence it is only available in draft) 
> and due to the ZigBee licensing model I don't imagine there are many Open 
> Source ZigBee drivers. 
>  
> It's possible that one of the domain experts from REG will have some options 
> for you, but I wouldn't expect a step-by-step guide. It's also possible that 
> you'll need to implement at least some part of the stack yourself.
>  
> Regards,
>  
> Tim
> 
> Sent from my iPhone
> 
> On 20 Oct 2016, at 08:26, <manoj.vrajam...@wipro.com 
> <mailto:manoj.vrajam...@wipro.com>> <manoj.vrajam...@wipro.com 
> <mailto:manoj.vrajam...@wipro.com>> wrote:
> 
> Hi,
>  
> I plan to discover and interact with Zigbee devices.
> Please help me with a step by step procedure to have/include a Zigbee 
> stack/bundle(base driver) in a simple getUpper QST Eclipse app (supposing I 
> have a Zigbee dongle to my laptop). I am on a Linux Laptop trying 
> Enroute/Bndtools.
>  
> Thanks,
> Manoj
>  
> From: osgi-dev-boun...@mail.osgi.org <mailto:osgi-dev-boun...@mail.osgi.org> 
> [mailto:osgi-dev-boun...@mail.osgi.org 
> <mailto:osgi-dev-boun...@mail.osgi.org>]On Behalf Of Timothy Ward
> Sent: 19 October 2016 16:35
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org 
> <mailto:osgi-dev@mail.osgi.org>>
> Subject: Re: [osgi-dev] Query
>  
> ** This mail has been sent from an external source **
> 
> Hi Manoj, 
>  
> If you’re looking for information about ZigBee then I suggest that you look 
> at the recent OSGi specification draft for the Residential R6 Supplement 
> (https://osgi.org/download/osgi.residential-supplement-6.0.0-earlydraft1.pdf 
> <https://osgi.org/download/osgi.residential-supplement-6.0.0-earlydraft1.pdf>).
>  UPnP is covered in chapter 111 of the existing OSGi Compendium/Residential 
> specifications. I’m sure that you’ll be able to use those as a basis for 
> finding further information about public implementations
>  
> Regards,
>  
> Tim
>  
> On 19 Oct 2016, at 09:33, manoj.vrajam...@wipro.com 
> <mailto:manoj.vrajam...@wipro.com> wrote:
>  
> Hi All,
>  
> Do we have an OSGi Bundle for AllJoyn Framework? Do we have an OSGi Bundle 
> for any other IoT Framework?
> Do we have an OSGi Bundle for any of the protocol stacks like 
> Zigbee/Wi-Fi/UPnP?
>  
> Thanks,
> Manoj
> The information contained in this electronic message and any attachments to 
> this message are intended for the exclusive use of the addressee(s) and may 
> contain proprietary, confidential or privileged information. If you are not 
> the intended recipient, you should not disseminate, distribute or copy this 
> e-mail. Please notify the sender immediately and destroy all copies of this 
> message and any attachments. WARNING: Computer viruses can be transmitted via 
> email. The recipient should check this email and any attachments for the 
> presence of viruses. The company accepts no liability for any damage caused 
> by any virus transmitted by this email. www.wipro.com 
> <http://www.wipro.com/>_______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>  
> The information contained in this electronic message and any attachments to 
> this message are intended for the exclusive use of the addressee(s) and may 
> contain proprietary, confidential or privileged information. If you are not 
> the intended recipient, you should not disseminate, distribute or copy this 
> e-mail. Please notify the sender immediately and destroy all copies of this 
> message and any attachments. WARNING: Computer viruses can be transmitted via 
> email. The recipient should check this email and any attachments for the 
> presence of viruses. The company accepts no liability for any damage caused 
> by any virus transmitted by this email.www.wipro.com <http://www.wipro.com/>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>The information contained in 
> this electronic message and any attachments to this message are intended for 
> the exclusive use of the addressee(s) and may contain proprietary, 
> confidential or privileged information. If you are not the intended 
> recipient, you should not disseminate, distribute or copy this e-mail. Please 
> notify the sender immediately and destroy all copies of this message and any 
> attachments. WARNING: Computer viruses can be transmitted via email. The 
> recipient should check this email and any attachments for the presence of 
> viruses. The company accepts no liability for any damage caused by any virus 
> transmitted by this email. www.wipro.com 
> <http://www.wipro.com/>_______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to