Adding LTE to a Wearable is not as easy as adding Bluetooth to a Wearable. Mobilestack Inc has deep experience in adding cellular technology to a Wearable and launching it in a carrier network. In this article, I want to outline steps for adding LTE / CAT-M / NB-IoT or legacy 2G / 3G wireless technology to a Wearable.
Adding a cellular modem to a wearable is a very different wireless design lifecycle Vs Bluetooth integration into Wearable. In a way, Cellular Modem enabled Wearable is a completely separate category of device Vs Bluetooth enabled device. Bluetooth enabled Wearable design is limited to hardware and software engineering effort to make it work with smartphone application that is optimized to reduce battery consumption as much as possible without compromising on user experience. WiFi connectivity solution is little more complex Vs Bluetooth because of new WiFi-6 design for IoT devices or WiFi AP-setting for wearable device. Still, this is not as complex as adding cellular connectivity solution to a wearable.
Adding LTE to Wearable has many product dimensions and life-cycle steps. Steps involved from idea to launch for adding LTE to a Wearable device are as follows:
Step-1: Product Requirements Definition:
Requirements definition needs to capture answer of following questions:
What is the main business objective of adding LTE to Wearables? What if LTE / CAT-M / NB-IoT coverage is not available at a given location – Is there a need to support 3G/2G as fallback option? Target market? Engage with mobile operators in target market for Wearable support and develop business case for operator support and technical requirements. New device features such as device management requirements, SIM Vs eSIM, Firmware update, Device security, Supply chain impacts, Number sharing, Voice Support, Text Message support are good examples of device requirements that must be considered.
Mobilestack Inc is very familiar with details of device requirements and pros/cons of different features that must be planned for IoT device development.
Step-2: Wireless Technology Choices
Based on device requirements, Wireless Technology choices must be made.
Band support:- Which RF bands are supported by target device. It is not feasible to add all RF bands and device OEM may be required to pick and choose. This choice will define the global footprint in which OEM device will potentially work. In other areas (not supported by RF-bands of Wearable), only Bluetooth or WiFi will work and Cellular modem has to be disabled.
Wireless Technology Choice – There are few options to be considered: LTE-Only, LTE/3G/2G, CAT-M Only, CAT-M / NB-IoT, CAT-M / 3G, NB-IOT/3G, CAT-M/NB-IoT/3G etc.
SIM technology and form-factor choice – One major decision is SIM Vs eSIM. How about SIM-Swap support? What SIM form-factor is best suited – such as Industrial grade embedded, Commercial-grade Embedded SIM or Removable SIM?
Mobilestack Inc has deep expertise in wireless technology choices and we can help customers in this step.
Detailed planning is needed including discussion with all stakeholders- Sales, Supply Chain, Vendors, Mobile Operators as Partners, Engineering, Product Management and Operational teams that will be involved in any new wireless device development, launch, sales and operational processes. New testing and device activation work-flows have to be worked out to create expectation alignment of all stakeholders.
Mobilestack Inc can help customers in planning this project to ensure the success and eliminate cost-overrun due to bad planning.
Step-4: Supply Chain impact and Vendor Selection
By adding Cellular Wireless connectivity, new vendors for wireless module and SIM-card are added as part of supply chain. Also, operator certified Wireless Module + SIM-card must be tested (on operator network or stand-alone) before it is added to a target device. Since most of this supply chain process is done off-shore, there are challenges in achieving smooth process for this step.
There are ways to solve this issue and Mobilestack Inc can help.
Step-5: Product Design
This has two components i.e. Hardware design and software design
Hardware design – Main design considerations are: Antenna Placement, Battery Power Management, Wireless Module integration, SIM-card placement, Battery capacity augmentation
Software design – Power management, always best connected Solution switching between Bluetooth and Cellular, One number solution for Voice, messaging services, Firmware update (FOTA), Device Activation / change in ownership aspects, eSIM / SIM-Management aspects, future-proofing of solution to enable eSIM later-on, User Interface impacts.
Customer experience should be painless and simple for using and activating wearable device. Usability factor will drive customer adoption. Bad usability or complex device activation process will create customer returns of a good working device. This should be considered as key performance indicator of device success among others.
Mobilestack Inc has deep expertise in Wireless Design and Engineering services.
Execute on Wireless design identified in step-5 above. Development should use agile development process with measurable progress and DevOps development model for frequent integration testing.
Mobilestack Inc offers cost-effective Wireless Connectivity Design and Development Services to achieve faster time-to-market for our customers.
System level testing must be done after development is completed with focus on automation as much as possible. Also, field testing must be included as part of this testing in which device is tested at multiple different locations with specific focus on edge cases such as roaming (specially new device activation in roaming), coverage edge of 4G and 3G etc. Mobile Operator resources can be used for field device testing.
Mobilestack Inc has expertise in creating test-plans (or advice customers on test-planning) and actual testing of wireless devices.
Step-8: Device Certification
In this step, device is submitted to different device certification centers that are approved by Mobile Operators including any in-house device testing by Mobile Operator. Not all operators require in-house device certification testing. So, as part of device planning step, Device certification plan must be developed and executed as part of this step. Before device launch, as part of pre-launch testing, Mobile Operator requires test-devices in large number for internal testing by different stakeholders including network operation team and regional / nation-side device sales and marketing channels.
Step-9: Device On-boarding process
For launch, Operator defined device on-boarding process must be followed. This includes submission of millions of manufactured devices identity (IMEI) and SIM-card identity (ICCID) details of devices (going on future sale) to Operator for proper provisioning or device on-boarding. It is best to integrate this process as part of supply chain of Device Manufacturing process. In the case of e-SIM based development, this process will be slightly different.
Mobilestack Inc can help navigate this process for our customers.
Congratulations for reaching on the finish-line. First few days of launch should be spent in a device launch war room to help operators and all different sales channel trouble-shooting and support. This is the most rewarding phase of project and smooth launch will help elevate device OEMs image in the marketplace.
After a month of launch, Device OEM can do a project post-mortem analysis to identify lessons learnt during this journey for future improvements. Smooth device launch and good customer reviews help in building Device OEM’s brand equity. All efforts must be made to make launch successful in a timely manner specially around Nov-Dec timeframe when alot of OEMs are trying to launch their device and Mobile Operators are always very busy.
Please reach out to contact at Mobilestack.com for any feedback, comments or questions. Fill up the contact form.