Seventh-Amended-Bylaws-Open-Connectivity-Foundation_06152016
Search Results for: UPnP-arch-DeviceArchitecture-v2.0.pdf/wp-content/uploads/2016/06/OCF-Basic-Membership-Agreement_06152016.pdf
Seventh-Amended-Bylaws-Open-Connectivity-Foundation_06152016
UPnP Certification
How To Certify A UPnP Device
- Gain UPnP Certification rights by doing one of the following:
- Become an OCF Member, and pay the applicable annual membership fee (e.g. $2,000 USD for Gold Membership), and sign the UPnP Certification Testing and Licensing Agreement.
- Become a Non-Member Licensee by signing the UPnP Certification Testing and Licensing Agreement, Application Form, and paying the $5,000 USD annual fee.
- Access the certification test tool via the UPnP Certification Site.
- Run the test tool at your own facility or at a 3rd party test house.
- Submit the test logs, along with Web-based device registration form, to the Test Reviewer.
Note: Your company must submit a device registration form for each device. Visit the UPnP Certification Site for additional information. - Once you have submitted the test logs and device registration forms, the Test Reviewer reviews the test logs and contacts you with testing results.
Note: The review may require up to five (5) working days; however, two working days is our goal. - If the device passes, your company receives a certificate of conformity for that particular device. The certificate authorizes your company to use the certification mark on the certified device and in associated marketing material, according to the Implementer Membership Addendum and the Logo Usage Guidelines document and FAQ, which are accessible via the UPnP Certification Site.
If the device fails, your company is notified of the failure and reason, no certificate is issued, and your company may not market the device as UPnP-certified. Your company is welcome to alter the device and retest.
UPnP Certification FAQs
If you are associated with an OCF member company, or a Non-Member Licensee, and would like further information about the UPnP certification process, you can register for an account on the UPnP Certification Management System and read more about the process by clicking on “UPnP.”
UPnP General Compliance FAQ's
UPnP+ Certification
Read about the UPnP+ initiative here. Note that the UPnP+ certification process follows the same certification process as standard UPnP products.
The goal of UPnP+-certified products is to certify a more reliable, secure, and diverse family of products. Benefits included in UPnP+ certification include:
- Interoperability
- Security
- Evolving standards (e.g., HTML5, IPv6)
- Cloud-based features
- New services
In support of this effort, OCF has updated the UPnP Certification Test Tool (UCTT) for enhanced testing and expanded its testing program to improve the quality of open source implementations.
The following are the requirements for UPnP+ certification compared to UPnP certification for all UPnP certified devices.
Specification |
UPnP Certification |
UPnP+ Certification |
UDA |
|
|
IPv6 Annex |
|
|
UDA Cloud Annex |
|
|
The following are the requirements for UPnP+ certification compared to UPnP certification for floating services. These services can be added to other device types.
Service |
UPnP Certification |
UPnP+ Certification |
DeviceProtection |
|
|
FriendlyInfoUpdate |
|
|
EnergyManagement |
|
|
BasicManagementService |
|
|
ConfigurationManagementService |
|
|
SoftwareManagementService |
|
|
QOS |
|
|
QOS |
|
|
UPnP Pre-certification
The UPnP Test Vendors (UTVs) are OCF members and provide pre-certification testing services on behalf of Members looking to obtain UPnP® certification. See above for the UPnP certification process.
Notes for UPnP Licensees:
-
-
- Although UTVs can perform testing on your behalf, it is your responsibility to submit passing test logs and the product details using the online Device Registration form to achieve UPnP® Certification.
- Test results generated by UTVs may be shared with OCF and will be treated confidentially.
-
UPnP Test Vendors
Vendor name | Contact information |
---|---|
Allion Labs, Inc | http://www.allion.com/ [email protected] Tel: +886-2-2655-7877 |
CESI Technology Co., Ltd | http://www.adtc.org.cn [email protected] [email protected] [email protected] Tel: +86-10-67831802 ext 30 |
If you are a UTV and not listed above but would like to request to be added, please contact the OCF UPnP Certification Administrator at [email protected]. OCF membership is required.
Pre-Certification UPnP Cloud Interoperability Testing
The below listed UPnP Test Vendors provide pre-certification testing services specifically for the Cloud on behalf of Members looking to obtain UPnP® or UPnP+® Certification. The process for certifying devices can be found here.
Notes for UPnP Licensees:
- Although these UPnP Test Vendors can perform testing on your behalf, it is your responsibility to submit passing test logs and the product details using the online Device Registration form to achieve UPnP® or UPnP+® Certification.
- Test results generated by UPnP Test Vendors may be shared with OCF and will be treated confidentially.
Independent Cloud Interoperability Service Vendors:
Vendor name | Contact information |
---|---|
ConnectingYourThings (CYT) | http://www.cytiot.com/ [email protected]: +1 650-466-7011 |
Comarch Technologies | http://technologies.comarch.com
Email: [email protected] |
If you are a Cloud Interoperability Service Vendor and not listed above but would like to request to be added, please contact the OCF UPnP Certification Administrator at [email protected]. As noted above, OCF membership is required.
Disclaimer of Non-endorsement: This page contains links to other sites which the Open Connectivity Foundation (OCF) provides for informational and convenience purposes only. OCF does not control or monitor these sites, nor does their inclusion mean that OCF recommends or endorses these sites, the organizations or companies that run the sites or anything contained within the sites. OCF in no manner endorses, sponsors, recommends, certifies or approves these Independent Certification Vendors and/or their products or offerings.
Have a question that
wasn’t addressed above?
FAQ
Background Information
Membership Information
Technical Information
Open Source Projects
OCF Certification
Learn More Here
OCF Announces Mark Trayer as OCF Chairman of the Board
The OCF Board of Directors (BoD) is made up of leading experts from innovative tech manufacturers including CableLabs, Cascoda, Haier, LG Electronics, and Samsung. These representatives are key decision makers and work to ensure the organization operations run smoothly and are in-line with OCF’s vision for the IoT. Last month, OCF was proud to welcome Mark Trayer to the BoD as Chairman of the Board. Mark brings a wealth of industry experience to the BoD and has been involved with OCF since its early inception in 2014.
We spoke with Mark about his professional background, his objectives as new BoD Chair, and his outlook on the future of OCF. Get to know the OCF BoD Chair below:
Please give us a brief introduction to yourself – what is your professional background, particularly within the IoT space?
I’ve been involved with “connectivity” the entirety of my professional career in Samsung, and prior to that, Nortel (originally BNR). Initially, I worked on the implementation of “old school” SS7 signaling systems in Digital Telephone, which evolved into architecting protocol stacks as part of Multi-media over IP solutions. I subsequently became more “residential” and user focused, working on in-home content distribution (personal content and provided content), and then into spaces that acted as a precursor to some of the early Smart Device/Smart Home solutions (Smart Energy, Smart Appliances, and associated Energy Star definitions).
I was part of the teams that worked on initial Smart Home enabling technologies for Samsung products. From there, in 2014 I was part of the launch of the Open Interconnect Consortium, which subsequently became what we know today as Open Connectivity Foundation (OCF). I have been heavily involved in contributing to OCF since that point.
As the newly elected OCF BoD Chair, how do you aim to use this role to advance OCF technology?
As OCF BoD Chair my role is to advance OCF technology through working with the other BoD members and the OCF Work Groups (WGs) to engender two key items: awareness and adoption.
For awareness, I work with other BoD members and OCF WG Chairs in active initiatives on stakeholder value, as well as the ongoing efforts of the Marketing Communications WG to position OCF effectively. We do this with targeted messaging advocating OCF as the Secure IP Device Framework of choice for the IoT.
For adoption, I work to ensure that OCF effectively supports member companies looking to bring products to market, as well as support ongoing initiatives taking place in different regions to deploy OCF technology.
Could you tell us about your history with OCF?
Samsung is a “day #1” member of OCF (originally OIC). I attended the kick-off Face-to-Face meeting in Manhattan Beach, CA, and was co-chair at that time of the original Smart Home group (with Wouter van der Beek, OCF Director). I have continued to chair the Smart Home Work Group since that very first meeting, and have also taken on the role of Core Technology Working Group Chair and Core Technology Steering Committee Chair.
I have been heavily involved in the development of the device and resource models that have been defined by OCF, working with people like Wouter van der Beek and Clarke Stevens on the tooling that accompanies these models that enables automated creation of spec material, and also automated creation of running code that realizes OCF devices.
I was also part of the key set of contributors that saw the realization of the OCF Universal Cloud Interface (C2C API) from a Power Point concept to a certifiable reality (with at least three certifications to date).
Why is OCF the standard of choice to propel IoT security to new heights?
OCF has endorsed security as a key element of its work and has a dedicated Security Work Group to maintain and update the OCF Secure IP Device Framework.
The OCF Secure IP Device Framework is a vertical agnostic infrastructure that enables secure IP communication through a standardized framework. It is also backed by an open-source implementation, which is compliant to the standard and meets the implementation verifications of our Certification Program. The framework includes network device discovery, resource/service discovery on the device, secure connectivity using DTLS for proximal (device-device) communication, onboarding on the secure domain and Access control lists.
This framework is compliant with most of the known IoT security baseline requirements – including those from NIST, CTAC, ENISA, UK, IASME and ETSI. The OCF Security Work Group has measured the OCF Secure IP Device Framework against these IoT security baselines so that you don’t have to – essentially allowing you to “compile your compliance” for regulatory IoT security requirements.
OCF offers a comprehensive Certification Program for its members. What are the benefits of OCF Certification and how does OCF Certification simplify a product’s time to market?
OCF provides a rich suite of tools to support members in bringing certified products to market. The Certification Test Tool (CTT) itself is available for free to all members, thus allowing in-house test and validation of an implementation before bringing it to an ATL for formal certification. In conjunction with this, Iotivity Lite provides an open-source implementation of the specifications that realizes the mandatory requirements, and against which each CTT release is regressed, thus ensuring alignment between specifications, code, and certification for every release.
To help in the development of a certifiable implementation and greatly simplify the associated effort, OCF also provides tools and toolchains to create running code for a device in an extremely time efficient manner, the OCF Developer Program provides tutorials and details to get started.
Could you give us a preview of what’s to come for OCF?
OCF is driving down three key paths:
- First, promoting the proven, open, Secure IP Device Framework that is defined by the Core and Core Security specifications as a fundamental element for an IoT solution or deployment. This is agnostic of the data models also defined by OCF, meaning that anyone who requires a secure, open standards-based, IP framework can take what OCF has developed (including much of the associated tooling) and build thereon.
- Second, OCF will continue to drive and support adoption of OCF as the IoT enabler for Smart Home and Smart Residential solutions. OCF ensures that any gaps in modeling or capability are met, and works with OCF member companies and the regional forums in supporting deployments, product development, certification programs, inter-operability events and more.
- Third, supporting efforts and work of the Smart Commercial Building Work Group in realizing products, solutions, and commercial deployments of OCF technology in this space.
All three of these initiatives provide the pillars of success for OCF moving forward.
Printer Device V 1.0 and Printer Basic Service V 1.0
The following files contain the standardized device and service descriptions for the Printer Device and Printer Basic Service. These standards passed the 45-day UPnP Forum member review and was approved by the Steering Committee on July 29, 2002.
XML Data Files for Testing *
* In order to preserve consistency, the XML files for PrintBasic and PrintEnhanced are identical. Implementations that only use PrintBasic can ignore the parts of the XML file that are specific to PrintEnhanced.