FAQ

/FAQ

This FAQ Page shall explain in more details what IoT Certifications & Compliances such as PTCRB, FCC, MQTT, etc., required for IoT Wireless Connectivity Solutions refer to.

If you have other IoT Certifications and Compliances that you would like to get some information about or that, in your opinion, we should add to our FAQ Page, please do not hesitate to contact us.

PTCRB provides a certification framework for GERAN (GSM), UTRAN (UMTS) and E-UTRAN (LTE) mobile devices and modules for usage on PTCRB operator networks.

It was established in 1997 by North American cellular network operators.

PTCRB certification ensures compliance with a set of cellular network standards. Without PTCRB certification, manufacturers run the risk that their devices are being blocked from North American networks.

For whom are the PTCRB certification rules mandatory?

Module manufacturers as well as end-product manufacturers, who implement PTCRB-certified modules, are obliged to follow the PTCRB certification processes.

PTCRB certification is applicable for devices operating in the 850, 1900 MHz bands for GSM, the FDD Bands II, IV, V for UMTS and all PTCRB relevant eFDD bands for LTE.

What happens if I use a pre-certified module?

For North American markets, manufacturers who integrate a pre-certified module into their GSM/UMTS wireless M2M device, must submit their “end-product” in its final (production) form factor to a PTCRB-authorized test laboratory for testing & certification. Only a minimal amount of testing is requested in these cases, because the majority of the test cases have already been completed when the module was initially certified. These tests are carried out to ensure that the interfaces associated with the integration will meet performance requirements expected by the PTCRB.

Certification standards

PTCRB certification is based on standards developed by 3rd Generation Partnership Project (3GPP), Open Mobile Alliance (OMA) and other standards-developing organizations(SDOs) recognized by the PTCRB. In some cases, PTCRB certification may accommodate North American standards and additional requirements from the U.S. Federal Communications Commission (FCC), Industry Canada or any other government agency that may have jurisdiction and/or competence in the matter.

The database containing the standards for PTCRB certification is based on InterLab, this online database accessible through the PTCRB website, updates the status of RFT’s (Request for Testing), Change Requests, Test Case status and Test Platforms.

By obtaining PTCRB Certification on a mobile device, it ensures compliance with cellular network standards within the PTCRB Operators’ networks. Consequently, PTCRB Operators may block devices from their network, if they are not PTCRB certified.

The CTIA – The Wireless Association has been assigned as the administrator for the PTCRB Certification process and is also responsible for the administration of PTCRB issued IMEIs.

The PTCRB Validation Group (PVG) is a group of test laboratory organizations working in the field of PTCRB associated technologies. The PVG group meets on a regular basis to discuss technical issues and the resolution of problems in a harmonized way. PVG works on open PTCRB RfTs and the validation of Test Platforms and Test Cases for the relevant PTCRB operating frequencies. Full and Observer membership categories reflect the status and scopes of organisations working within the group. The Chair of the PVG is held by Thomas Jaeger of 7Layers, Germany.

 

Source : Wikipedia

FCC Certification – The FCC Declaration of Conformity[1] or the FCC label or the FCC mark is a certification mark employed on electronic products manufactured or sold in the United States which certifies that the electromagnetic interference from the device is under limits approved by the Federal Communications Commission.[1][2][3][4][5][6][7] The FCC label is found even on products sold outside the US territory, because they are either products manufactured in the US and had been exported, or they are also sold in the US. This makes the FCC label recognizable worldwide even to people to whom the name of the agency Federal Communications Commission is not familiar.[8][9]

The Federal Communications Commission established the regulations on electromagnetic interference under Part 15 of the FCC rules in 1975. After several amendments over the years, these regulations were reconstituted as the Declaration of Conformity and Certification procedures in 1998.

By the regulation, the FCC DoC certification mark is mandatory for devices classified under part 15 (IT equipment like computers, switched-mode power supplies, monitors etc., television receivers, cable system devices, low-power transmitters, un-licensed personal communication devices) and part 18 (industrial, scientific, and medical (ISM) devices that emit RF radiation) of the FCC regulations.

The certification mark is a stand-alone logo (as shown above) for the part 18 class of devices while, for the part 15 class, along with the logo, the label should display other data viz, the trade name of the product, the model number, and information whether the device was tested after assembling, or assembled from tested components.[2][10]

As of January 2012, there are 279 test firms worldwide, accredited with the Commission who are qualified to issue the declaration of conformity certificate.[11]

Even though most of the nations exporting electronic equipment into the US market have their own standards for EMI as well as independent certification and conformity marks (e.g.: The CCC certification mark for China, the VCCI (Voluntary Council for Control of Interference) mark for Japan, the KCC mark by the Korea Communications Commission for South Korea, and the BSMI mark for Taiwan), most of the products still sold in these markets hold the FCC label. Electronic products sold in parts of Asia and Africa hold the FCC label even though it holds no legal significance, and also without any means to verify whether they actually conform to the specified standards or not.

Source : Wikipedia

MQTT-Ready : MQTT stands for MQ Telemetry Transport. It is a publish/subscribe, extremely simple and lightweight messaging protocol, designed for constrained devices and low-bandwidth, high-latency or unreliable networks. The design principles are to minimise network bandwidth and device resource requirements whilst also attempting to ensure reliability and some degree of assurance of delivery. These principles also turn out to make the protocol ideal of the emerging “machine-to-machine” (M2M) or “Internet of Things” world of connected devices, and for mobile applications where bandwidth and battery power are at a premium.

Who invented MQTT?

MQTT was invented by Dr Andy Stanford-Clark of IBM, and Arlen Nipper of Arcom (now Eurotech), in 1999.

Where is MQTT in use?

MQTT has been widely implemented across a variety of industries since 1999. A few of the more interesting examples are listed on the Projects page.

Is MQTT a standard?

As of March 2013, MQTT is in the process of undergoing standardisation at OASIS.

The protocol specification has been openly published with a royalty-free license for many years, and companies such as Eurotech (formerly known as Arcom) have implemented the protocol in their products.

In November 2011 IBM and Eurotech announced their joint participation in the Eclipse M2M Industry Working Group and donation of MQTT code to the proposed Eclipse Paho project.

How does MQTT relate to SCADA protocol and MQIsdp?

The “SCADA protocol” and the “MQ Integrator SCADA Device Protocol” (MQIsdp) are both old names for what is now known as the MQ Telemetry Transport (MQTT). The protocol has also been known as “WebSphere MQTT” (WMQTT), though that name is also no longer used.

What is WebSphere MQ Telemetry?

This is a product from IBM which implements the MQTT protocol in a very scalable manner and which interoperates directly with the WebSphere MQ family of products.

There are other implementations of MQTT listed on the Software page.

Are there standard ports for MQTT to use?

Yes. TCP/IP port 1883 is reserved with IANA for use with MQTT. TCP/IP port 8883 is also registered, for using MQTT over SSL.

Does MQTT support security?

You can pass a user name and password with an MQTT packet in V3.1 of the protocol. Encryption across the network can be handled with SSL, independently of the MQTT protocol itself (it is worth noting that SSL is not the lightest of protocols, and does add significant network overhead). Additional security can be added by an application encrypting data that it sends and receives, but this is not something built-in to the protocol, in order to keep it simple and lightweight.

Where can I find out more?

The specification and other documentation are available via the Documentation page.

Ask questions via one of the methods on the Community page.

Try code via one of the projects on the Software page.

 

Source : Wikipedia

Terms of Use

By downloading 3D model you are agree with:

  1. This 3D model is provided "as is", entirely at your own risk.
  2. Briowirelss Inc. doesn't accept any claims regarding quality of 3D model or any standards conformity.
  3. This model may be used in any commercial way only if it is a part of artwork or project. Single reselling or redistribution of this model is prohibited.
  4. This model may be freely modificated or elaborated.

I have read, understood, and agree.

Agree and Download Disagree with Terms .