OSGi Bundle Permission Management for Image Forming Apparatus
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing image forming apparatuses face challenges in managing fragment bundles, where insufficient permissions can lead to inconvenient and frequent updates of the permission definition file in the host bundle, affecting the functionality and usability of fragment bundles.
Innovation Solution
The solution involves an OSGi extension unit that manages permissions by generating a permission list for each bundle during installation and startup, allowing fragment bundles to be executed without modifying the host bundle's permission definition file, ensuring sufficient permissions are maintained without manual corrections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a fragment bundle is added to a host bundle to extend functionality, then the functionality and versatility of the image forming apparatus is improved, but the permission definition file in the host bundle becomes insufficient and requires frequent corrections
Solution Approach 1:
The permission management is segmented into two independent parts: host bundle permissions and fragment bundle permissions. Each fragment bundle carries its own permission definition file, separating the permission management from the host bundle and allowing independent configuration without affecting the host bundle's permission definition file.
Solution Approach 2:
The system introduces an intermediary permission checking mechanism that reads permission definition files from both the host bundle and the fragment bundle. This intermediary layer combines permissions from both sources and performs authorization checks, eliminating the need to modify the host bundle's permission definition file when adding fragment bundles.
2Reliability
If the permission definition file is corrected manually every time a fragment bundle is added, then sufficient permissions are maintained, but the complexity of permission management increases and usability decreases
Solution Approach 1:
The fragment bundle performs self-service by carrying its own permission definition file. When a fragment bundle is added to a host bundle, the system automatically detects and loads the fragment bundle's permission definition file, eliminating the need for manual correction of the host bundle's permission definition file and reducing management complexity.
Solution Approach 2:
The permission definition file is prepared in advance within each fragment bundle before it is added to the host bundle. This preliminary preparation ensures that all necessary permissions are already configured, and the system can automatically combine these permissions with the host bundle's permissions without requiring subsequent manual adjustments.
3Ease of operation
If fragment bundles inherit permissions from the host bundle, then permission management is simplified, but the fragment bundle may lack necessary specific permissions
Solution Approach 1:
The system merges permission sets from both the host bundle and the fragment bundle by loading and combining their respective permission definition files. The permission checking mechanism integrates permissions from both sources, ensuring that the fragment bundle inherits general permissions from the host bundle while also having access to its own specific permissions defined in its separate permission definition file.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A permission list for a host application associated with the host application is held, and a plug-in application is added to the host application a permission included in the plug-in application is added and updated to the permission list for the host application, and whether processing in the host application and the plug-in application is to be executed is determined based on the updated permission list.