Functional Alias Resolution in Mission Critical Push to Talk Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless communication networks, particularly in Future Railways Mobile Communication Systems (FRMCS), the existing technologies face challenges in efficiently routing calls using Functional Aliases (FAs), which are activated by users, to Mission Critical Push to Talk (MCPTT) identifiers.

Innovation Solution

An apparatus and method that receive a call request with address information containing a Functional Alias, send a request to a server to resolve the FA to MCPTT identifiers, receive the identifiers, and then send a call request to the intended clients using these identifiers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If Functional Alias is used for call routing, then ease of operation is improved, but device complexity increases due to resolution requirements

Engineering Contradiction:
Improvecall routingVSAvoidresolution process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a resolution server as an intermediary component that handles the translation between Functional Aliases and MCPTT identifiers. This mediator absorbs the complexity of the resolution process, allowing the client devices to simply use Functional Aliases without needing to implement complex resolution logic themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The resolution functionality is extracted from the client devices and placed in a dedicated resolution server. This separation allows client devices to remain simple while the server handles the complex task of resolving Functional Aliases to actual MCPTT identifiers, effectively moving the complexity burden from endpoints to the network infrastructure.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If Functional Alias resolution is implemented, then adaptability is improved, but loss of time increases due to resolution overhead

Engineering Contradiction:
Improvecall routingVSAvoidresolution time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-establishing the resolution infrastructure and maintaining ready-to-use resolution mappings on the server side. When a call needs to be routed, the resolution process can begin immediately without waiting for setup, reducing the perceived delay despite the additional resolution step required.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The resolution server maintains continuous operation and keeps resolution mappings readily available, ensuring that the resolution process can proceed without interruption once initiated. This continuous readiness minimizes the time penalty by eliminating setup delays and ensuring immediate processing capability.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12309214B2Apparatus, method and computer program
Publication Date: 2025.05.20 NOKIA TECHNOLOGIES OY
  • US12309214B2 patent drawing
  • US12309214B2 patent drawing
  • US12309214B2 patent drawing

AI summary

An apparatus comprising means for performing: receiving, from a first client, a call request comprising address information for calling at least one second client, the address information comprising a Functional Alias, wherein the Functional Alias is activated by the at least one second client; in response to receiving the call request at the apparatus, sending, to a server, a request to resolve the Functional Alias to at least one Mission Critical Push to Talk Identifier of the at least one second client that has activated the Functional Alias; receiving, at the apparatus from the server, the at least one Mission Critical Push to Talk Identifier of the at least one second client; sending, from the apparatus, a call request to the at least one second client using the at least one Mission Critical Push to Talk Identifier of the at least one second client.