UPnP Data Model Access Control via Role-Based Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current UPnP device management systems lack effective access control for viewing, reading, and modifying configuration information, leading to unprotected sensitive data exposure.

Innovation Solution

A method and system that utilize role-based access control and Access Control Lists (ACLs) to secure access to UPnP data models, ensuring only authorized control points can access or modify configuration information by determining and enforcing recommended roles and permissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If device protection service provides entire configuration information to control point, then control point gets access to all configuration data, but sensitive and irrelevant information is exposed

Engineering Contradiction:
Improveaccess to configuration informationVSAvoidexposure of sensitive information
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent segments the configuration information in UPnP data models into protected and unprotected portions using Access Control Lists (ACLs). Each node in the data model can have associated ACLs that specify which control points can access which portions of the configuration information, thereby dividing the information access rights into discrete controllable units rather than providing blanket access.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing different access control policies to be applied to different nodes within the UPnP data model. Each node can have its own ACLs with customized permissions, enabling fine-grained control where sensitive nodes have restricted access while non-sensitive nodes remain accessible, thus tailoring the security properties to the specific characteristics of each configuration element.

Inventive Principle:
Principle #3Local quality

2Reliability

If role-based access control is implemented with ACLs, then access to configuration information is secured, but system complexity increases

Engineering Contradiction:
Improvesecurity of configuration informationVSAvoidaccess control mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal access control framework that can be applied to any UPnP device and control point regardless of vendor or specific implementation. The ACL mechanism provides a standardized, multi-functional approach that works across different UPnP services and data models, reducing the need for device-specific security implementations while maintaining comprehensive security coverage.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent applies preliminary action by pre-configuring Access Control Lists on UPnP data model nodes before access requests occur. The ACLs are established in advance with defined permissions for different control points, allowing the system to quickly evaluate access requests against pre-computed policies rather than making security decisions in real-time, thus reducing operational complexity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2591574B1Method and system for securing access to configuration information stored in universal plug and play data models
Publication Date: 2018.09.05 SAMSUNG ELECTRONICS CO LTD
  • EP2591574B1 patent drawingFigure 1
  • EP2591574B1 patent drawingFigure 2
  • EP2591574B1 patent drawingFigure 3

AI summary

The present invention provides a method and system for securing access to configuration information stored in universal plug and play data models. In one embodiment, a request to operate on node(s) of a data model is received from a control point (CP). The data model includes a plurality of nodes and each of the plurality of nodes represents configuration information. A role associated with the CP is determined. It is determined whether the role of CP is in a recommended role list. If the role is present, then the CP is allowed to operate on the node(s). If the role is not present, then it is determined whether the CP is having an appropriate role to operate on the node(s) based on ACL data associated with the node(s). Accordingly, the CP is allowed to operate on the node(s) or an error message is returned on the display of the CP.