Northbound API Consent Mediation for Secure UE Resource Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack effective methods for user equipment (UE) to manage and authorize the sharing of resources with third parties through northbound application programming interfaces (APIs), particularly in scenarios where consent and authorization for information sharing are required.

Innovation Solution

A northbound API invoking method and apparatus that allows UE to receive and determine authorization requests, send response messages, and manage tokens for accessing target resources, ensuring user consent and authorization is integrated into the API invoking process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If northbound API is used to enable third-party access to UE resources, then service capability and connectivity are improved, but security and user consent control are compromised

Engineering Contradiction:
Improveservice capabilityVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a consent management function as an intermediary between the API consumer and UE resources. This mediator receives API requests, obtains user consent through a graphical user interface, and manages authorization tokens. The consent management function acts as a bridge that enables third-party access while maintaining security through user-controlled authorization and token-based authentication mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If traditional authorization methods are used, then security is maintained, but user control and consent management are insufficient

Engineering Contradiction:
ImprovesecurityVSAvoiduser control
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service authorization where users directly control access to their own resources through a graphical user interface. Users can view, approve, revoke, and manage consent for third-party access to their UE resources. The system empowers users to make their own authorization decisions without requiring manual intervention from network operators or administrators, thereby improving both security and user control.

Inventive Principle:
Principle #25Self-service

3Reliability

If comprehensive authorization management is implemented, then security and user control are improved, but system complexity increases

Engineering Contradiction:
Improveauthorization controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal consent management framework that can handle multiple types of UE resources (location, communication state, sensor data, etc.) through a single standardized interface. The consent management function serves multiple purposes: obtaining user consent, generating authorization tokens, validating requests, and revoking access. This multi-functional approach reduces overall system complexity by consolidating authorization management into one unified component rather than requiring separate mechanisms for each resource type.

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

Data Source

PatentUS20260056813A1Northbound application programming interface (API) invoking method and apparatus
Publication Date: 2026.02.26 BEIJING XIAOMI MOBILE SOFTWARE CO LTD
  • US20260056813A1 patent drawing
  • US20260056813A1 patent drawing
  • US20260056813A1 patent drawing

AI summary

The present disclosure provides a northbound application programming interface (API) invoking method and apparatus. The method comprises: receiving an authorization request message that is sent by a common API framework (CAPIF) verification and authorization function and that requests acquisition of a specified authorization (101), the specified authorization being an authorization corresponding to a target resource of UE; on the basis of the authorization request message, determining whether to allow an API invoker to acquire the target resource (102); and sending an authorization response message to the CAPIF verification and authorization function (103), the authorization response message being used to indicate whether the UE agrees to provide the specified authorization for the API invoker.