1 / 10

Open Source PDT approval for UPnP-Bridge Library

Open Source PDT approval for UPnP-Bridge Library. Rick Bell(SSG-OTC). Description of the functionality. Media App. Smart Home App. IoTivity. IoTivity FWK.

shawnnas
Download Presentation

Open Source PDT approval for UPnP-Bridge Library

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Open Source PDT approval for UPnP-Bridge Library Rick Bell(SSG-OTC)

  2. Description of the functionality Media App Smart Home App IoTivity IoTivity FWK • UPnP-Bridge integrates Legacy UPnP devices into IoTivity. UPnP-Bridge discover existing UPnP devices/services. UPnP-Bridge translates UPnP devices/services/actions into IoTivity devices/services and registers them as IoTivity devices through Resource Container. This allows existing UPnP devices/services/action to be managed and used through IoTivity like any other IoTivity device. Resource Container Services UPnP-Bridge gupnp-av gupnp gssdp libsoup glib UPnP Devices Device Discovery & Messaging REST/CoAP Connectivity Abstraction Layer

  3. Why we want this functionality • To allow for smooth transition for Legacy UPnP to IoTivity. Support of Legacy UPnP devices is seen to be required for 4-5 years while companies transition their products from UPnP devices to IoTivity devices. • Discover, translates, register, manage, and use existing UPnP devices/services in IoTivity. • Provides UPnP Audio/Video functionality (i.e. Media Server, Media Render, Media Control Point, and etc.). This one of the key functionality UPnP has large deployment and maturity over IoTivity. • Provide open-source solution that can be leveraged for various uses case models. • Use Case Example: IoTivity-UPnP-bridge service could be used IoTivity gateway or server as central manager for UPnP devices

  4. Distributing Linux • Not distributing Linux.

  5. Description of the software components and licenses

  6. Intel IP exposure risk • <Is there any Intel or 3rd party proprietary IP exposed? Is this public information yet? When will it be? Which BU’s or 3rd parties need to approve this exposure?> No Intel IP, everything based on public information from UPnP Specification, OIC Specifications, GNOME Documentation, and IoTivity Documentation • <do you include media codecs, or other implementations of IP defined by a standards group or SIG? If so, which ones?> No codecs

  7. PR / Publication plan • Source published to a separate project ssh://gerrit.iotivity.org/iotivity-upnp-bridge instead of under ssh://gerrit.iotivity.org/iotivityproject • No binaries • Article explaining implementation to https://www.iotivity.org/ • Article may be picked up in other news • There should be a press release for the OIC UPnP Bridge functionality. Will need to work with Mike Richmond.

  8. Library Bill of Material

  9. DRM / trusted computing • Does the project use DRM, secure boot, signed binaries or similar technologies that make it hard for end users to replace the software? No

  10. Approval request • Does the Linux PDT approve releasing the software project using the licenses as described in the table • Yes / No

More Related