The reality of IoT communications operations

In the field of Industrial IoT (IIoT), it is common for sensors and devices to be installed in remote​ ​locations where no one is present and to operate for long periods of time.
Many of these applications, such as river monitoring, equipment condition monitoring, energy-related equipment, and outdoor infrastructure, are not operated on-site.

In such an environment, initial setup, switching, and troubleshooting of communications
Operations such as "changing SIM cards locally" and "operating the terminal" are not realistic in terms of both cost and manpower.

eSIM was originally expected to be a technology that would solve these issues, but there were many situations in which the conventional eSIM standard did not suit the actual operational situation of industrial IoT​.

The premise of SGP.22 is "a terminal that can be operated by a person"

SGP.22 is a smartphone, tablet, etc. Consumer Devices Designed for eSIM It is a standard.
In this model, UI Depending on the operation and user action, eSIM It is assumed that you will be adding and switching profiles.

However, the following conditions are common for industrial IoT devices:

・Does not have a screen or operation UI​

・Deploy hundreds to tens of thousands of units at once

- No one can touch it after installation

・Changes in communication conditions may occur even after operation begins

Under these conditions, it must be said that the SGP.22 operational model, which is based on the premise that each unit will be operated by a human, is difficult to implement.

Another issue faced by the M2M model (SGP.02)

On the other hand, M2M models (SGP.01/SGP.02) have traditionally existed for industrial use.
However, this model requires a dedicated management infrastructure and complex configuration.

・High initial installation costs

・Operational design tends to be heavy

・Limited flexibility when expanding globally

There were also cases where this was an issue.

As a result, the situation in industrial IoT has been one in which "we want lightweight and flexible operation, but the current standards do not provide an optimal solution."​

SGP.32 is an eSIM standard designed for industrial IoT operations

Taking this background into consideration, SGP.32 is a new eSIM standard formulated with industrial IoT applications in mind.

The biggest feature is, Designed not to assume on-site terminal operation is located.
eSIM Manage and switch profiles on your device, not on your device. Completed remotely This is based on the premise that

This makes it easier to address the specific requirements of Industrial IoT, such as:

・Communication requirements differ between manufacturing and installation

- I want to change the carrier or communication conditions after installation.

- Want to manage a large number of devices at once

・I want to reduce the number of on-site maintenance visits as much as possible

How will communication operations change in industrial IoT?

By adopting SGP.32, communication design can be considered more from a service and operation perspective.

・Devices should be shipped in a "communication-ready" state.

・After installation, you can assign a communication profile according to the purpose and region.

・The communication environment can be changed without on-site work.

This is an industry IoT important in Scalability, maintainability, and reduced operational costs This is a point that is directly related to

Summary: SGP.32 is an eSIM design for Industrial IoT

SGP.32 is not simply an extension of existing eSIM standards.
This standard was designed by rethinking the very premise of "Who, where, and how will industrial IoT be operated?"

Considering the characteristics of industrial IoT, such as long-term operation, mass deployment, and no on-site operation,
SGP.32 will likely become an important option in future communications designs.

the next deployment

At present, operational models based on SGP.32 are in the process of being demonstrated and advanced initiatives are underway, and it is expected that the way in which they will be applied in industrial IoT settings will be clarified in the future.

In particular, in environments where large-scale deployment of equipment and long-term operation are assumed, the approach taken to designing the entire system, including communications, will have an impact on operational load and future scalability.

We will continue to consider how the SGP.32 standard should be positioned within actual industrial IoT systems.