LPP Message Compatibility Level Negotiation for Wireless Positioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless network technologies face challenges in supporting positioning for terminals with different capabilities, as they operate with various versions of positioning protocols, leading to compatibility issues and inefficient communication.

Innovation Solution

The implementation of a message structure that includes a protocol version and compatibility level, allowing for the transmission and reception of messages that adapt to different protocol versions, ensuring interoperability between terminals and network servers, even if they support different versions of the LTE Positioning Protocol (LPP) or its extensions (LPPe).

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If terminals use different versions of positioning protocols, then positioning functionality can be supported for diverse terminal capabilities, but compatibility issues arise and communication efficiency deteriorates

Engineering Contradiction:
Improvepositioning capability supportVSAvoidprotocol compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

A compatibility level field is introduced as an intermediary element in the LPP message structure. This field acts as a mediator between terminals with different protocol versions, enabling them to understand each other by negotiating compatibility levels. The compatibility level field serves as a common ground that allows terminals to identify mutually supported protocol versions without requiring exact version matching.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The protocol version parameter is extended by adding a compatibility level field, transforming it from a simple version identifier to a multi-dimensional parameter that includes both version number and compatibility information. This parameter change allows the system to represent multiple protocol version combinations in a structured way, enabling terminals to select appropriate protocol versions based on their capabilities while maintaining compatibility.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If protocol versions are differentiated without compatibility information, then version-specific functionality is enabled, but communication efficiency and interoperability decrease

Engineering Contradiction:
Improveprotocol version flexibilityVSAvoidcommunication efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

Compatibility level information is exchanged preliminarily during the capability negotiation phase before actual positioning measurements begin. By establishing the compatibility level in advance, terminals can optimize their communication protocols for the specific interaction, avoiding unnecessary retransmissions and ensuring efficient data exchange throughout the positioning procedure.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The receiving terminal provides feedback about its supported compatibility levels in response to capability requests. This feedback mechanism enables the initiating terminal to adapt its protocol version selection based on the response, creating an efficient negotiation process that optimizes communication between terminals with different capabilities.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9398442B2Supporting version negotiation for positioning for terminals in a wireless network
Publication Date: 2016.07.19 QUALCOMM INC
  • US9398442B2 patent drawing
  • US9398442B2 patent drawing
  • US9398442B2 patent drawing

AI summary

Techniques for supporting positioning for terminals in a wireless network are described. In an aspect, a message is prepared and transmitted with a message segment including a version of a protocol used to encode the message and a compatibility level associated with inter-operable protocol versions, wherein different compatibility levels indicate non-compatibility between protocol versions. In another aspect, a message is received with a message segment including a version of a protocol used to encode the message and a compatibility level associated with inter-operable protocol versions, wherein different compatibility levels indicate non-compatibility between protocol versions. The compatibility level included in the received message is compared to an internal compatibility level and a response message is prepared and transmitted with a message segment including the internal compatibility level.