LCS Message Routing via NAS Encapsulation and Routing ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless network technologies face inefficiencies in routing and managing messages for location services (LCS) in LTE networks, particularly in maintaining state information and ensuring secure, privacy-compliant communication between User Equipment (UE) and location centers.
Innovation Solution
The use of Non-Access Stratum (NAS) messages to encapsulate LCS-related messages and the implementation of a routing identifier (ID) to associate messages with location sessions, allowing for efficient transport and simplifying operations across network entities without the need for maintaining state information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional message routing methods are used for LCS in LTE networks, then network entities can maintain state information for message tracking, but the implementation complexity and operational overhead increase significantly
Solution Approach 1:
The patent introduces a routing identifier as an intermediary element that mediates between LCS messages and location sessions. Instead of network entities maintaining complex state information, the routing identifier acts as a mediator that carries session identification information through the message exchange process, enabling reliable message routing without increasing device complexity
Solution Approach 2:
The patent extracts the session identification function from the network entity's state information and embeds it directly into the message structure via the routing identifier. This extraction removes the need for network entities to maintain external state, reducing implementation complexity while preserving message routing reliability
2Loss of information
If network entities maintain state information for LCS message management, then message routing can be tracked, but the operational overhead and processing burden increase
Solution Approach 1:
The routing identifier is established in advance as part of the location session setup and is then embedded in subsequent LCS messages. This preliminary action ensures that message association information is available before messages are exchanged, eliminating the need for network entities to maintain state information during the message exchange process
3Productivity
If existing protocols are used without modification, then implementation is simpler, but the ability to efficiently route LCS messages is reduced
Solution Approach 1:
The routing identifier is nested within the existing NAS message structure, allowing LCS messages to be transported efficiently through the LTE network using existing protocols. The routing identifier is embedded as an additional field within the message structure, enabling enhanced functionality without requiring separate protocol implementations
Solution Approach 2:
The routing identifier serves multiple functions: it identifies the location session, enables message routing, and maintains message association information. This multi-functionality improves LCS message transport efficiency while minimizing the need for separate mechanisms, thereby limiting the increase in implementation complexity
Data Source
AI summary
Techniques for transporting messages for location services (LCS) are described. A Mobility Management Entity (MME) may have a location session with an Evolved Serving Mobile Location Center (E-SMLC) to provide location services for a User Equipment (UE). The UE may exchange LCS-related messages with the E-SMLC to obtain location services. In an aspect, LCS-related messages exchanged between the UE and the E-SMLC may be encapsulated in Non-Access Stratum (NAS) messages and transported via the MME and a base station. In another aspect, a routing identifier (ID) may be used to associate messages exchanged between the UE and the MME with the location session between the MME and the E-SMLC for the UE. Each NAS message exchanged between the MME and the UE may include the routing ID, which may enable the MME to associate each NAS message from the UE with the location session between the MME and the E-SMLC.