December 5, 2013 - 10:57am, 7181 views
thinking of developing a mHealth application - would you recommend to use a 2G or a 3G module?
It depends on where you deploy. 2G support in the US going away. If you are looking to the reset of the world 2G support highly available. You should also think about the future needs of your product. If 2G performance is acceptable now will it be acceptable for your application in 2, 3, 5 years? Is the development cost low enough to use 2G now and switch to 3G later?
Agree with @AAQUINO
You also need to consider that 2G java modules like EGS5 and TC65i will no longer be maintained. If this is not only cost based choice - it is better to go with 3G.
Walking on water and developing software from a specification are easy - if both are frozen.
Gemalto has chosen a strategy of common footprint for product families. The EHS5, EHS6 and BGS5 give the possibility of doing one hardware design that works for 2G or 3G. EHS5 allows to cost optimize to a dualband 3G solution for US/Europe or choose EHS6 to go global with 5 band 3G.
And Java allows you to reuse the software across all of them.
Good point! :)
I would go for 3G for eHealth. The main reason is the connectivity in the long term, the other reason is the global sales opportunities.
Please use Java, as the OTAP is very important for high volume, geographically spread unit updates, if necessary. Also remote configuration of mass produced, almost "blank" units makes it possible to tailor the units for the different customers and markets.
Communication and Mechatronics
Enkom Active Oy – www.enkom-active.fi
Upseerinkatu 3 A, 02600 Espoo, Finland
Mobile: +358 400 411368
Office: +358 10 204 0000
Fax: +358 10 204 0010
The most health applications work perfectly fine on 2G and don’t actually need the higher 3G speeds. But I also agree with AAQUINO. It depends on where you deploy.
Social networking software developer - read more
© 2013-2014 Gemalto M2M GmbH