SNPN UE Onboarding and Remote Provisioning via OPF
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for provisioning user equipment (UE) in standalone non-public networks (SNPNs) are costly and lack remote provisioning capabilities, particularly for devices without universal subscriber identity modules (USIM) or embedded SIMs (eSIMs, as they require manual configuration by operators.
Innovation Solution
Introduce an onboarding and provisioning function (OPF) to manage UE provisioning, including storing provisioning data, distributing it, and performing authentication and authorization, with a network architecture that supports UE identity, credentials, and configuration data management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual configuration is used for SNPN UE provisioning, then the UE can be configured without USIM/eSIM, but the provisioning process becomes complex and costly requiring operator intervention
Solution Approach 1:
The patent introduces an Onboarding and Provisioning Function (OPF) entity as an intermediary between the SNPN UE and the network. The OPF entity stores provisioning data and distributes it to UEs, enabling automated provisioning without requiring manual operator intervention. This mediator resolves the contradiction by providing a systematic approach that maintains adaptability while reducing process complexity.
Solution Approach 2:
The patent enables SNPN UEs to perform self-provisioning by automatically obtaining configuration data from the OPF entity. The UE can autonomously complete the provisioning process without requiring manual configuration by operators, thereby reducing both complexity and cost while maintaining full provisioning capability.
2Extent of automation
If remote provisioning is implemented for SNPN UE, then operator intervention is reduced, but the network architecture becomes more complex requiring additional functions
Solution Approach 1:
The OPF entity serves as a dedicated intermediary component that handles all remote provisioning operations. By centralizing provisioning data storage and distribution in this specialized function, the network achieves automated remote provisioning capabilities without requiring complex distributed provisioning logic across multiple network elements.
Solution Approach 2:
The patent segments the provisioning function from the core network operations by introducing a separate OPF entity. This segmentation allows remote provisioning to be implemented as a distinct, manageable function rather than integrating complexity into the core network architecture, thereby enabling automation while controlling overall system complexity.
3Reliability
If SNPN operator provisions each UE manually, then security can be maintained, but the provisioning cost and time increase significantly
Solution Approach 1:
The patent enables secure automated provisioning where UEs autonomously obtain their configuration data from the OPF entity through authenticated requests. This self-service mechanism eliminates time-consuming manual operations while maintaining security through the authenticated interaction between UE and OPF, resolving the contradiction between security and provisioning speed.
Solution Approach 2:
The OPF entity pre-stores provisioning data for multiple UEs before they need to connect to the network. When a UE needs provisioning, it can immediately retrieve pre-prepared configuration data without waiting for manual setup, significantly reducing provisioning time while maintaining security through the pre-established trusted relationship between the operator and the OPF entity.
Data Source
AI summary
Embodiments of the present application are directed to a method and apparatus for providing onboarding and provisioning services. A method according to an embodiment of the present application may include: receiving a registration request for a user equipment (UE), wherein the register request indicates an identity of the UE, an onboarding and provisioning flag, and an onboarding and provisioning function (OPF) identity; selecting an OPF entity at least based on the OPF identity in the case of an onboarding request being supported for the UE; and transmitting the onboarding request at least indicating the identity of the UE to the selected OPF entity.