Enterprise SIM Remote Provisioning via Contextual Service Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current remote provisioning methods for Subscriber Identity Modules (SIMs) in enterprise settings are limited, as they often require manual intervention and do not efficiently accommodate multiple service profiles or contextual use scenarios, such as location or device capability indicators.

Innovation Solution

A system and method for remotely provisioning SIMs in mobile devices associated with enterprises, where an enterprise server selects and sends suitable service plan options based on characteristics like location, language, or device capabilities, allowing for dynamic profile configuration without physical card replacement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual intervention is used for SIM provisioning, then provisioning accuracy is improved, but operational efficiency deteriorates

Engineering Contradiction:
Improveprovisioning accuracyVSAvoidoperational efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system enables self-service provisioning where the mobile device automatically communicates with the enterprise server to obtain service plan options and completes SIM provisioning without manual intervention. The device sends its identifier, receives contextualized service plan recommendations, and automatically completes the provisioning process, eliminating the need for manual operator intervention while maintaining accuracy through automated verification.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The enterprise server pre-configures multiple service plan options with contextual information (location, device capabilities, language preferences) before the provisioning request. This preliminary preparation allows the system to quickly present appropriate options to the device, reducing the time required for provisioning while ensuring accurate matching of service plans to device contexts.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple service profiles are supported, then service versatility is improved, but system complexity deteriorates

Engineering Contradiction:
Improveservice versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service provisioning system segments service plans into distinct, context-specific options (e.g., location-based plans, device-type-specific plans, language-specific plans). Each service plan is a self-contained profile with defined parameters, allowing the system to manage multiple profiles through modular organization rather than complex interdependencies, reducing overall system complexity while maintaining versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The enterprise server acts as an intermediary that manages the complexity of multiple service profiles. It receives the mobile device's identifier and contextual information, processes the data against multiple service plan options, and presents simplified recommendations to the device. This intermediary layer shields the device from the complexity of managing multiple profiles while enabling access to diverse service options.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If contextual characteristics are considered, then service adaptability is improved, but processing time deteriorates

Engineering Contradiction:
Improveservice adaptabilityVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The enterprise server pre-configures service plan options with contextual parameters (location, device capabilities, language preferences) stored in its database. When a provisioning request arrives, the server quickly queries and filters pre-prepared options based on the device's identifier and basic context, rather than processing complex contextual analysis in real-time. This preliminary preparation significantly reduces processing time while maintaining high service adaptability.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If physical card replacement is eliminated, then operational convenience is improved, but provisioning security deteriorates

Engineering Contradiction:
Improveoperational convenienceVSAvoidprovisioning security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system replaces the mechanical process of physical SIM card insertion and replacement with electronic/digital provisioning. The mobile device communicates electronically with the enterprise server to receive provisioning data, which is then written to the SIM card through automated over-the-air updates. This eliminates the need for physical handling while maintaining security through encrypted communication channels and authenticated data transfer protocols.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10200837B1Remote provisioning of SIMs for enterprises
Publication Date: 2019.02.05 CISCO TECHNOLOGY INC
  • US10200837B1 patent drawing
  • US10200837B1 patent drawing
  • US10200837B1 patent drawing

AI summary

Techniques for use in remotely provisioning a Subscriber Identity Module (SIM) of a mobile device for an enterprise are described. In one illustrative example, at an enterprise server, a message is received from the mobile device or an operator in communication with the mobile device. In response, one or more enterprise service plan options are selected from a plurality of service plan options in a database (DB) and sent to the mobile device or the operator. One of the enterprise service plan options is selected for use in preparing a profile to be remotely provisioned on the SIM. The one or more enterprise service plan options may be selected based on one or more characteristics of a member of the enterprise and/or the member's association or relationship with the enterprise, and/or other characteristics indicative of intended contextual use (e.g. location or geography indicator, language indicator, device capability indicator such as for voice and/data communication capabilities), etc.).