Industrial IoT Router

Industrial IoT Router

The Meizo R68J is a rugged enterprise-gradeCategory 6 4G LTE Router with LTE-Advanced support. With 2 LAN ports and Extended Range WiFi, it provides more connectivity options and flexibility for those looking to get the most out of their high-speed internet experience. The router CPU is using...

Description

The Meizo R68J is a rugged enterprise-gradeCategory 6 4G LTE Router with LTE-Advanced support. With 2 LAN ports and Extended Range WiFi, it provides more connectivity options and flexibility for those looking to get the most out of their high-speed internet experience. The router CPU is using Broadcom chipset, integrated with Ethernet, SIM, VPN, VRRP, WiFi, and Serial port services. By owning hardware and software watchdog, ensures the router to access internet all the time.

 image001.jpg

Main Features

Hardware Specifications

Software Functions

● Support public and private APN network
● Dedicated hardware and software watchdog are designed to support system running reliable.
● ICMP detection and Heartbeat detection ensure the router to be always on line.
● Reboot the router remotely via SMS.
● Incorporate Virtual Router Redundancy Protocol (VRRP), facilitating 3G/4G WAN backup services to existing fixed line routers, providing both WAN and router redundancy to critical business applications.
● Offers business grade security and advanced routing features IPSec (3Des and AES), L2TP, PPTP, GRE as standard.
● Low-voltage, over current, over voltage, anti-reverse protection
● Wide Power Input DC7-36V
● Standard RS232/485 interface to connect with serial devices.
● Router Factory Default Settings can be configured freely.
● System logs can be viewed from local or remote.
● Support WLAN(300Mbps 802.11b/g/n)
● Support SNMP v1/v2/v3
● LEDS for status monitoring (showing Power, System, Internet, VPN, Signal strength).

CPU
● RAM:512Mbit FLASH:128Mbit
Power
● Input DC 7-36V(Standard DC12V)
Environment
● Storage temperature:-40℃~80℃
● Work temperature:-30℃~70℃
● Humidity:<95%
Dimension
● Unit size L*W*H:150*116.2*23.8mm
● Metal Shell, IP30
● Package weight:830g
Interface
● 1 SIM card slot
● 2 LAN 10/100Mb RJ45 port
● 1 RS232 or RS485 serial port
Antenna(female)
● ANT1 for Cell, ANT2,3 for WiFi
EMC
● Electrostatic discharge immunity:EN6100-4-2, level 2
● RFEMS:EN6100-4-3, level 2
● Surge:EN6100-4-3, level 2
● PFMF:EN6100-4-6, level 2
● Shockwave immunity:EN6100-4-8, Horizontal / vertical direction 400A/m(>level 2)
Physical property
● Shockproof:IEC60068-2-27
● Drop test:IEC60068-2-32
● Vibration test:IEC60068-2-6

VPN
● IPSec client
● PPTP client
● L2TP server and client
● GRE client
WIFI
● Transmitting power: 17dbm
● Distance:Cover a radius of 100 meters in open area test
● Allow 50 users to access in theory
NAT
● Port Mapping
● Port Triggering
● DMZ
Firewall
● IP filtering
● MAC filtering
● URL filtering
QOS
● Manage uplink/downlink bandwidth via port or IP
Management
● Web
● Telnet
● TR-069 platform
Routing
● Static Routing
● Policy-Based Routing.
● Dynamic Routing


Model

Frequency & Band

Bandwidth(UL/DL)

Consumption

WiFi (-W)

Serial(-S)

Power

R68J
(Japan network)

● FDD-LTE: 2100MHz(B1), 1800MHz(B3), 850MHz(B5), 2600MHz(B7), 900MHz(B8), 800MHz(B18), 800MHz(B19), 1500MHz(B21), 700MHz(B28),
● TDD-LTE: 2600MHz(B38), 1900MHz(B39), 2300MHz(B40), 2500MHz(B41)
● WCDMA: 2100MHz(B1), 850MHz(B5), 850MHz(B6), 900MHz(B8), 1700MHz(B9), 850MHz(B19)
● TD-SCDMA: B39

FDD-LTE:50Mbps/300Mbps
TDD-LTE:10Mbps/112Mbps
DC-HSPA+: 5.76Mbps/42Mbps

Work:0.46A@12V DC
Peak:0.58A@12V DC

802.11n 300Mbps

Option

RS232/RS485

Option

US/EU standard 

Input: AC100~240V
Output: DC12V

Option


what is M2M and what is IoT?

Some in the market associate M2M with Connectivity and Internet of Things with the Network and Application Layers, including Data Analytics. There is a good logic behind this approach, however, it positions M2M and IoT in two different planes with little, if any, common areas. In my opinion, associating M2M just with the connectivity layer implies an over-simplification of M2M. M2M is much more than connectivity. M2M involves many different components that enable the remote and automatic communication with a remote device. It includes the sensors in the device, the control software in the device, the communication module, the central system and software that establishes the logic to manage the devices remotely and the information gathered by them, ... So M2M is, in fact, much more than connectivity.


Others in the market limit both M2M and IoT to the connecctivity layer, taking out the Application Layer. However taking out the application layer over-simplifies both M2M and IoT, as explained before. The communication is enabled not only through the connectivity piece but also understanding the scope of the application and the needed logic in underlying layers down to connectivity. Furthermore, the different needs from different industries are to be considered in shaping the M2M and IoT connectivity layer, so my preference is not to completely unlink the application layer but keep it within the scope of both terms.

However the above, I can only agree with the intuitive line of thinking that derives from IoT a much higher level of complexity than that in the M2M World. But said that, I prefer to set M2M and IoT on the same plane, and rather establish the differences on two different areas that I explain below:


  • Centralized or decentralized processing engine.

  • Number of dimensions managed in M2M vs IoT applications. 


Let me try to explain both points. In M2M we talk about connecting and managing remote devices. No matter how Machine to Machine communication can be interpreted from a semantic point of view, the reality of M2M is that we talk about applications where in principle a given type of devices with a given purpose communicate and are managed by a central system. That is what I refer to when talking about a centralised processing engine. It is in fact a central system the one that provides a layer of intelligence on top of the device. Also, as we talk about one type of devices, we talk about one dimension.


In IoT, however, we are also connecting and managing devices. The key difference is that when we talk about IoT, we decentralize the intelligence and increase the number of dimensions. We talk about applications that are built on top of different devices and different sources of information, part of them coming from the devices but not necessarily all. Event processing becomes more complex, as events from one given area may trigger actions on different areas from the originating one. Also event management becomes more complex as there may be a combination of events from different devices or elements that combined together trigger a given action.


Following the line above, M2M Service Providers would not only be the connectivity providers, but there is an Ecosystem of Service Providers providing connectivity, functions built on connectivity modules and applications built on top of those functions. IoT requires a similar Ecosystem, more complex as per the decentralized intelligence and increased number of dimensions. Another element that increases the complexity is the fact that Internet of Things will probably be built on top of a potential big number of Subnet of Things, as per the different technologies. We will see early adopters in different markets and different areas, using different communication technologies, protocols, programming languages… before standardization organisms are able to bring certain level of consistency in IoT Applications.


The market is big and there is still a lot to see before the market consolidates and a market structure becomes clearer. We see many different players in this market, from well established and consolidated companies trying to build a position in this market to hundreds, if not thousands, of startups addressing one or more industries, all trying to define how to monetize the many different opportunities that these technology enablers open. Companies well positioned to adopt leading roles are Telecom Operators and companies with extensive experience in Data Management applications. Internet Service Providers, companies as Google or companies as IBM, Microsoft, Apple… are positioned at good starting points. But it will all depend on how they play their roles in the process of market consolidation.


In the case of Mobile Network Operators, addressing this market requires to review and adapt the Business Models, and as per the trends we see in the market, in some cases quite significantly. This change also depends on the role the MNO wants to adopt and the areas of the value chain to be targeted. Only looking at connectivity, there are already areas that need to be observed and adapted to the new needs generated by M2M and IoT applications, including: 

  • Network Technology, including considerations about network coverage and realiability.

  • Modules and Devices.

  • M2M Services (associated to connectivity).

  • Security needs.

  • Standardisation.


As the market evolves, we will think in grouping specific application needs for connectivity and beyond. Some of them may be relevant in more than one segment, some will be relevant across all industries. Upon this analysis, the MNOs shall decide the role and market approach, also based on key assets and potential to acquire new assets and integrate them in the company.



Hot Tags: industrial IoT router, suppliers, manufacturers, factory, buy, customized, price

Feedback

Related Products

Products List