Community Computing Method for Heterogeneous Device Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the ubiquitous computing environment, existing technologies face challenges in integrating and collaborating heterogeneous devices and services, resolving conflicts between entities with varying intelligence and self-control, ensuring security for personal information, and providing context-aware services across diverse user and instrument contexts.
Innovation Solution
A community computing method and system that forms, activates, deactivates, and terminates communities based on defined goals, policies, and context information, using a community manager, situation manager, and meta-service repository to facilitate collaboration, security, and context-aware service delivery across dispersed objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If heterogeneous devices and services are integrated in ubiquitous computing environment, then service functionality and collaboration capability are improved, but system complexity and conflict resolution difficulty increase
Solution Approach 1:
The patent segments the ubiquitous computing system into autonomous communities, where each community is a self-contained unit with its own management system. This segmentation allows heterogeneous devices to be organized into manageable groups, reducing overall system complexity while maintaining service functionality. Each community handles its own internal conflicts and operations independently.
Solution Approach 2:
The patent introduces community managers as intermediary entities that mediate between heterogeneous devices and services within a community. These managers handle protocol translation, conflict resolution, and coordination, allowing diverse devices to collaborate without directly interacting with each other's complexity.
2Productivity
If community members are dynamically organized and activated, then service responsiveness and context-awareness are improved, but management overhead and operational complexity increase
Solution Approach 1:
The patent implements self-service mechanisms where community members automatically discover each other, negotiate their roles, and activate/deactivate based on context conditions. The community management system autonomously organizes members without manual intervention, reducing management overhead while maintaining dynamic responsiveness to contextual changes.
Solution Approach 2:
The patent establishes community formation templates and pre-defined activation conditions in advance. When contextual conditions are met, pre-organized communities can be quickly activated without ad-hoc management overhead, improving service responsiveness while maintaining ease of operation through prior preparation.
3Adaptability or versatility
If context information is monitored and shared across communities, then service personalization and user experience are improved, but information security and privacy protection challenges increase
Solution Approach 1:
The patent segments context information into community-level and individual-level data, with different sharing policies for each. Sensitive personal information remains confined to individual communities or specific members, while only aggregated or anonymized context data is shared across communities. This segmentation enables service personalization through context awareness while protecting individual privacy.
Solution Approach 2:
The patent introduces context managers as intermediary entities that handle context information collection, processing, and sharing. These managers apply privacy protection rules, anonymize sensitive data, and control information flow between communities, enabling personalized services while mitigating privacy exposure risks.
Data Source
AI summary
The present invention provides a community computing method and system comprising a step of community formation forming a community by defining a goal, policies, members, operations among the members, an operation situation of the community and an idle situation of the community, a step of community standby both waiting for an operation starting timing and organizing an actual community member, after the step of community formation, a step of community activation both being self activated and starting an operation, when the community operation situation is ready while the community monitors a context information, after the step of community standby, a step of community deactivation both temporarily stopping an operation for itself and waiting for a next community operation, when the community satisfies the goal of the community, or a situation to deactivate comes in, after the step of community activation; and, a step of community termination terminating all operations for itself in case the community does not need to operate any more.