{"id":5932,"date":"2021-12-28T10:19:56","date_gmt":"2021-12-28T18:19:56","guid":{"rendered":"https:\/\/csa-iot.org\/?page_id=5932"},"modified":"2022-01-12T14:40:38","modified_gmt":"2022-01-12T22:40:38","slug":"rf4ce-faq","status":"publish","type":"page","link":"https:\/\/csa-iot.org\/all-solutions\/rf4ce\/rf4ce-faq\/","title":{"rendered":"Rf4ce FAQ"},"content":{"rendered":"\n
\n
\n

Rf4ce FAQ<\/h1>\n\n\n\n

Frequently asked questions about rf4ce Technology<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

\n
\"\"
<\/figcaption><\/figure>\n<\/div><\/div><\/div><\/div>\n<\/div><\/div><\/div><\/div>\n\n\n\n
<\/div>
\n

What is rf4ce? <\/strong><\/strong><\/strong><\/h3>\n\n\n\n

The Zigbee rf4ce specification offers an immediate, low-cost, easy-to-implement networking solution for Zigbee Remote Control and Zigbee Input Devices. Rf4ce is designed to provide low-power, low-latency control for a wide range of products including home entertainment devices, garage door openers, keyless entry systems and more. In combination with the Zigbee Remote Control and Input Device profiles, rf4ce results in remote controls without line-of-sight restrictions that also deliver two-way communication, longer range of use, and extended battery life.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What markets is rf4ce intended for? <\/strong><\/strong><\/strong><\/h3>\n\n\n\n

Smart Home<\/strong> – The Zigbee rf4ce specification provides multi-vendor, interoperable home entertainment solution for consumer electronics featuring a simple, robust and low-cost communication network for two-way wireless connectivity.
Commercial<\/strong> – Commercial uses for Rf4ce can include Entertainment devices, lighting, fan control, garage door openers, and keyless entry systems.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What are the main use cases that rf4ce addresses? <\/strong><\/strong><\/strong><\/h3>\n\n\n\n

The main use case for rf4ce cover remote device control and communications where infrared technology (IR) may have been previously used. Rf4ce is used to create remote controllers that communicate with Zigbee devices and Zigbee-based home automation systems with more robust communication than IR.<\/p>\n\n\n\n

<\/div>\n\n\n\n

How do I get my product certified?<\/strong><\/strong><\/h3>\n\n\n\n

Learn more about the Alliance certification programs<\/span><\/strong><\/a>.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What are rf4ce benefits? <\/strong><\/strong><\/h3>\n\n\n\n

Rf4ce is simple, low-cost, robust against interference, and low-latency. Rf4ce provides an ideal networking layer for remote control of Zigbee devices. <\/p>\n\n\n\n

<\/div>\n\n\n\n

What are the main features of rf4ce? <\/strong><\/strong><\/strong><\/h3>\n\n\n\n

Rf4ce is a thin, flexible, and future-proof networking layer, featuring secure communications, strong resistance to interference from WiFi and Bluetooth\u00ae, power-saving mechanisms, and simple and intuitive pairing between devices.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What kind of security does rf4ce use? <\/strong><\/strong><\/strong><\/h3>\n\n\n\n

The ZigBee rf4ce specification provides a cryptographic mechanism to protect the transmissions. This mechanism provides the following security services:<\/p>\n\n\n\n

  • Data confidentiality: To ensure that the data contained in a ZigBee rf4ce transmission can only be disclosed to the intended recipient.<\/li>
  • Data authenticity: To ensure that the intended recipient of a ZigBee rf4ce transmission knows that the data was sent from a trusted source and not modified during transmission.<\/li>
  • Replay protection: To ensure that a secure transmission cannot simply be repeated by an attacking device if overheard. 128-bit cryptographic keys are generated by each end of a pairing link and stored in the pairing table for future use. The keys can be updated at the user discretion if desired and supported by the application.<\/li><\/ul>\n\n\n\n
    <\/div>\n\n\n\n
    <\/div>\n<\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":0,"parent":5911,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"content-type":"","_relevanssi_hide_post":"","_relevanssi_hide_content":"","_relevanssi_pin_for_all":"","_relevanssi_pin_keywords":"","_relevanssi_unpin_keywords":"","_relevanssi_related_keywords":"","_relevanssi_related_include_ids":"","_relevanssi_related_exclude_ids":"","_relevanssi_related_no_append":"","_relevanssi_related_not_related":"","_relevanssi_related_posts":"","_relevanssi_noindex_reason":"","footnotes":""},"folder":[],"class_list":["post-5932","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/pages\/5932","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/comments?post=5932"}],"version-history":[{"count":0,"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/pages\/5932\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/pages\/5911"}],"wp:attachment":[{"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/media?parent=5932"}],"wp:term":[{"taxonomy":"folder","embeddable":true,"href":"https:\/\/csa-iot.org\/wp-json\/wp\/v2\/folder?post=5932"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}