AP ID Validation for UE-Associated Logical Connections

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing technologies face challenges in efficiently handling and routing messages with Application Protocol Identifiers (AP IDs) in wireless communication networks, particularly due to high costs and performance impacts associated with error case detection, as specified in 3GPP specifications TS 38.413 and TS 38.423.

Innovation Solution

The proposed solution involves a network node that receives messages with paired UE identifiers, validating the message if the local AP ID is known, and only checking the remote AP ID for consistency with the established signaling connection, thereby reducing the complexity and computational load of AP ID handling, especially in distributed UE context management scenarios.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If strict AP ID error detection is performed according to 3GPP specifications, then message routing reliability is improved, but network node performance deteriorates due to high computational cost

Engineering Contradiction:
Improvemessage routing reliabilityVSAvoidnetwork node performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the AP ID validation process into two distinct parts: (1) validation of the local AP ID generated by the receiving node, and (2) validation of the remote AP ID received from the sending node. By separating these validation tasks, the patent applies different validation strictness to each part, reducing overall computational burden while maintaining essential reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial validation action by performing full validation only on the local AP ID (which the receiving node generates and controls) while applying minimal or no validation on the remote AP ID (which comes from the peer node). This partial approach avoids the excessive computational cost of validating both IDs equally, thereby improving network node performance while maintaining sufficient routing reliability.

Inventive Principle:
Principle #16Partial or excessive action

2Difficulty of detecting and measuring

If uniqueness checking of remote AP ID is performed, then error detection capability is improved, but computational load increases negatively impacting performance

Engineering Contradiction:
Improveerror detection capabilityVSAvoidcomputational load
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent extracts and removes the uniqueness checking step for remote AP IDs from the validation process. Since the receiving node cannot efficiently verify whether a remote AP ID is unique across the network, the patent eliminates this computationally expensive operation while retaining validation of local AP IDs, thereby reducing computational load without significantly compromising error detection capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary approach where the sending node is trusted to provide valid remote AP IDs, and the receiving node accepts these IDs without performing expensive uniqueness verification. This intermediary trust model acts as a mediator between strict validation requirements and computational constraints, reducing complexity while maintaining acceptable error detection through local ID validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11832339B2Handling application protocol identity for a UE-associated logical connection
Publication Date: 2023.11.28 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US11832339B2 patent drawing
  • US11832339B2 patent drawing
  • US11832339B2 patent drawing

AI summary

A network node (300a) receives, over an interface between the network node (300a) and a further network node (300b), a message comprising paired user equipment (UE) identifiers for UE identification over the interface to the network node (300a) and further network node (300b), respectively. Responsive to determining that the identifier for UE identification to the network node (300a) uniquely identifies a UE (150) to the network node (300a), the network node (300a) validates the message irrespective of whether the identifier for UE identification to the further network node (300b) uniquely identifies the UE (150) to the further network node (300b).