Open Connectivity Foundation (OCF)

Open Connectivity Foundation (OCF)

Contact Us

Search Results For: 二元期权是什么上选富达cpyx18.com

Search Results for: 二元期权是什么上选富达cpyx18.com

OCF Ambassador Program

The goal of the OCF Ambassadors program is to sustain and grow the worldwide OCF community. OCF Ambassadors are enthusiastic experts who know and can speak to the OCF Specification, IoTivity code, and who are willing to share that knowledge with others around the world.

OCF Ambassadors represent the work being conducted throughout OCF and provide a point of contact for those looking to get involved in developing products within their local community.

OCF Meetups

OCF Meetup Groups are led by OCF Ambassadors, where participants can discuss the OCF Specification and reference implementation code. These events can often be your best resource in learning how to implement OCF in your language, all at a time and location that is convenient for you.

The participants in these meetup groups share knowledge, discuss best practices and technical challenges, recruit and onboard new developers, as well as create greater awareness around OCF and the OCF Specifications and reference implementation code.

map

Get Involved

Apply to become an OCF Ambassador here.
Join an OCF Meetup in your area.
Want to start a Meetup or have a question – contact OCF at [email protected].

Europe

Ankara
Coordinator: Fatih Aksel
Website: http://www.meetup.com/OCF-Ankara/

Budapest
Coordinator: Ondrej Tomcik
Website :https://www.meetup.com/OCF-Budapest/

Czech Republic
Coordinator: Ondrej Tomcik
Website: https://www.meetup.com/OCF-Czech-Republic/

France
Website: https://www.meetup.com/OCF-France/

Germany
Coordinator: Oliver Fischer
Website: http://www.meetup.com/OCF-Germany/

Italy
Coordinator: Mirco Vanini
Website: http://www.meetup.com/OCF-Italy/

Slovakia
Coordinator: Ondrej Tomcik
Website: https://www.meetup.com/OCF-slovakia/

Switzerland
Coordinator: Ondrej Tomcik
Website: https://www.meetup.com/OCF-switzerland/

North America

Boston
Coordinator: Brad Kemp
Website: http://www.meetup.com/OCF-Boston

Nashville
Coordinator: Ian Lee
Website: http://www.meetup.com/OCF-Nashville/

Asia

Beijing
Coordinator: Mu (Betty Zhao)
Website: https://www.meetup.com/OCF-Beijing/

Seoul
Coordinator: Subeom Lee
Website: http://www.meetup.com/OCF-Seoul/

Shenzhen
Coordinator: Jun Zhang
Website: http://www.meetup.com/OCF-Shenzhen/

Taipei
Coordinator: Yuping Tseng, Kelven Pan
Website: http://www.meetup.com/OCF-Taipei/

Necessary IP Declarations – MediaServer:4 and MediaRenderer:3

Necessary IP Declarations – MediaServer:4 and MediaRenderer:3 (Revision 31 March 2013)

Capitalized terms are defined in the UPnP Forum Membership Agreement.

Pursuant to the requirements of section 3.8(a) and 3.8(f) of the UPnP Forum Membership Agreement, the following Members have made the indicated declarations related to Necessary IP that is not the Member’s Member Input that is incorporated in the above named Standardized DCPs and their willingness to license such Necessary IP.

By providing this information, the UPnP Forum makes no representation regarding the accuracy or validity of this information nor its relevance to the UPnP Forum, DCPs, Proposed or Approved DCP Frameworks, test configuration files, Reference Implementations, Reference Implementation test logs, or to UPnP Compliant Devices. Consistent with Section 3.6(a)(D) of the UPnP Forum Membership Agreement, no Member, including Steering Committee representatives and working committee chairs, has undertaken on behalf of the UPnP Forum or its Members, any patent search with respect to the Proposed or Approved DCP Frameworks, Proposed DCPs, Standardized DCPs, Reference Implementations and associated test configuration files.

Members that now discover they have or acquire Necessary IP that is included in these Standardized DCPs have a disclosure obligation under Section 3.8(f) and must submit its Declaration through the forms linked below.

UPnP Patent Disclosure Guidelines

Disclosure Form B: UPnP Post-Comment and Disclosure Period Patent Declaration Form Amendment: Changing a RAND Declaration to a RAND-Z Declaration

Disclosure Form C: UPnP Post-Comment and Disclosure Period Patent Declaration Form for Later-Acquired and/or Later-Discovered Necessary IP

Questions or concerns regarding the disclosure processes and guidelines may be referred to the Legal Inquiry Taskforce using this online form.

Declarations

Member: Intel Corporation
Proposed DCP or DCP Framework: ScheduledRecording:2 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:57 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: RenderingControl:3 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:55 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: MediaServer:4 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:54 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: MediaRenderer:3 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:52 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: ContentDirectory:4 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Prograqm Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:50 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: ConnectionManager:3 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:49 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: AVTransport:3 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prarie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:47 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: AVDataStructureTemplate:1 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:45 AM
Patent License Option: (ii) RAND terms and conditions

Member: Intel Corporation
Proposed DCP or DCP Framework: AVArchitecture:2 Revision Dated 31 March 2013
Signatory Name: Scott Lofgren
Title: Program Manager
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 7/23/2013 11:43 AM
Patent License Option: (ii) RAND terms and conditions

Contributors

The UPnP Forum in no way guarantees the accuracy or completeness of these contributors lists and in no way implies any rights for or support from those members listed. Members contributing to these DCPs, but not included in the list below should notify the Forum Administrator.

MediaServer:4
Echostar
Intel
Nokia
Panasonic
Pioneer
Philips
Samsung Electronics
Sony

MediaRenderer:3
Allegrosoft
Echostar
HP
Intel
LG Electronics
Microsoft
Nokia
Panasonic
Pioneer
Philips
Samsung Electronics
Sony
Toshiba

AVArchitecture:2
Intel Corporation
Microsoft Corporation
Philips

AVDataStructureTemplate:1
Allegrosoft
Echostar
HP
Intel
LGE Electronics
Microsoft
Nokia
Panasonic
Philips
Pioneer
Samsung Electronics
Sony
Toshiba

AVTransport:3
Intel
LG Electronics
Nokia
PacketVideo
Philips
Samsung
TP Vision

ConnectionManager:3
Intel
LG Electronics
Nokia
Philips
Samsung
TP Vision

ContentDirectory:4
Intel
LG Electronics
Nokia
PacketVideo
Philips
Samsung
TP Vision

RenderingControl:3
Intel
LG Electronics
Nokia
Philips
Samsung
TP Vision

ScheduledRecording:2
Intel
LG Electronics
Nokia
Philips
Samsung
TP Vision

OCF Developer Program

About the OCF Developer Program

The OCF Developer Program consists of:

Getting Started with IoTivity Lite

For detailed information on how to get started with IoTivity Lite, please visit this page: https://iotivity.org/getting-started

Instructions on how to build, run, generate OCF server code, and interact with sample applications for OCF servers are outlined in the getting started guide.

Developer Training

The OCF Developer Training will show you how to set up an IoTivity development environment on a Raspberry Pi 3 board via the Getting Started Guide. The OCF Developer Kit includes a Raspberry Pi 3 board and additional hardware to get you started with IoT development using IoTivity APIs and interacting with sensor/actuator devices.

OCF Developer Training Instruction:

To watch OCF experts presenting the above materials, please click here to go to the OCF YouTube page.

OCF Developer Training Slides in Mandarin:

Development Resources and Solutions (alphabetical by name)

Building blocks for developers building OCF devices and services:

If you have an OCF compatible solution, developer kit, or service that you would like to list here, please contact [email protected] to submit your request for consideration.

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 open source providers and/or their products or offerings.

UPnP Certification

UPnP+
UPnP Pre-certification

How To Certify A UPnP Device

  1. Gain UPnP Certification rights by doing one of the following:
  2. Access the certification test tool via the UPnP Certification Site.
  3. Run the test tool at your own facility or at a 3rd party test house.
  4. 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.
  5. 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.
  6. 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

Back to top

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
  • UPnP version 1.0 is a minimum requirement
  • UPnP version 1.1 is optional
  • UPnP version 2.0 is a minimum requirement
IPv6 Annex
  • UPnP certification requires IPv4 support
  • IPv6 support is optional and the currently published IPv6 annex is out of date
  • UPnP+ certification requires dual-stack (IPv4/IPv6) implementation as described in the new UPnP UDA annex
UDA Cloud Annex
  • UDA V1.0 devices cannot be certified as cloud devices, however legacy UDA V1.0 devices can be bridged to the cloud using a UPnP+ certified CPDev Cloud Proxy device
  • UPnP cloud device support (UCCD) is mandatory for UPnP+ device certification
  • UPnP cloud control point support (UCC-CP) is mandatory for UPnP+ control point certification

 

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
  • DeviceProtection:1 is optional
  • DeviceProtection:1 is required for UPnP+ certification
  • http://sourceforge.net/projects/upnpdm/ - an open source implementation from Orange (includes DeviceProtection, DeviceManagement: BMS & CMS & SMS)
FriendlyInfoUpdate
  • FriendlyInfoUpdate:1 support is optional
  • FriendlyInfoUpdate:1 support is mandatory for UPnP+ certification
EnergyManagement
  • EnergyManagement:1 is optional
  • EnergyManagement:1 support is mandatory in UPnP+ certification
  • EnergyManagement proxy is mandatory for mains powered devices
BasicManagementService
  • BasicManagementService:1 is optional
  • BasicManagementService:2 is mandatory
ConfigurationManagementService
  • ConfigurationManagement Service:1 is optional
  • ConfigurationManagementService:2 is optional
SoftwareManagementService
  • SoftwareManagement Service:1 is optional
  • SoftwareManagementService:2 is optional
QOS
  • QOS:2 is optional
  • QOS:2 is optional
QOS
  • QOS:3 is optional
  • QOS:3 is optional

Back to top

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]
and [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.

Back to top

View the technical FAQ here.

Have a question that
wasn’t addressed above?


CONTACT US

OCF-over-Thread is Now Available to Simplify Highly Secure, Scalable, Low-Power IP-based IoT Product Development

Posted on:

Collaboration between IoT standards bodies — implemented by Cascoda — helps ensure a secure and interoperable IoT for the future

Beaverton, OR – November 18, 2019 – The Open Connectivity Foundation (OCF), a leading Internet of Things (IoT) standards body, and the Thread Group, an alliance addressing interoperability, security, power, and architecture challenges at the network layer, today announced the readiness of  OCF-over-Thread. Developed by Cascoda, a leading manufacturer of IoT semiconductors, OCF-over-Thread is now a certifiable solution that simplifies the development of end-to-end products for smart home, and smart commercial buildings.  The Cascoda solution offers built-in interoperability and scalable security controls for both large and small IoT applications…. [Read More]