Device Trigger Server Message Routing via UE Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In machine-to-machine (M2M) communications, the Device Trigger-Application Server (DT-AS) within the 3GPP network cannot identify trigger messages sent by third-party Application Servers, preventing the establishment of connections between M2M User Equipment (UE) and these servers.
Innovation Solution
The proposed solution involves including an identifier of the M2M UE in the trigger message sent by the third-party Application Server to the DT-AS, allowing the DT-AS to determine if the UE is registered and routing the message accordingly, and using preset IP addresses and port numbers to ensure message identification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the third-party AS sends trigger message to DT-AS without including M2M UE identifier, then the signaling flow can be simplified, but the DT-AS cannot identify the trigger message and route it to the correct M2M UE
Solution Approach 1:
The M2M UE sends a registration message to the third-party AS in advance, obtaining an identifier that will be used in the trigger message. This preliminary action ensures that when the trigger message is sent, the DT-AS can immediately identify and route it to the correct UE without complex lookup procedures.
Solution Approach 2:
The patent introduces an identifier (such as ECGI or IMSI) as an intermediary element that bridges the third-party AS and the M2M UE. This identifier acts as a mediator that enables the DT-AS to recognize and forward the trigger message to the correct destination without requiring complex routing logic.
2Reliability
If the DT-AS stores and manages registration information for all M2M UEs, then trigger message routing can be achieved, but the device complexity and memory requirements increase
Solution Approach 1:
The patent extracts the identifier information from the M2M UE and places it directly in the trigger message sent by the third-party AS. This extraction eliminates the need for the DT-AS to store and manage comprehensive registration information, as the identifier is self-contained in the message itself.
Solution Approach 2:
The trigger message itself carries the necessary identifier information to enable routing, making the message self-sufficient. The DT-AS does not need to maintain external registration databases, as the trigger message contains all information needed for routing decisions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention provides a method for sending a trigger message, and a device. When a third-party application server AS needs to establish a connection with machine-to-machine communications user equipment M2M UE, the third-party AS sends a trigger trigger message to a device trigger application server DT-AS, where the trigger message includes at least an identifier of the machine-to-machine communications user equipment M2M UE. The DT-AS determines, according to the identifier of the M2M UE, whether the M2M UE has registered with a network at which the DT-AS is located, and if the M2M UE has registered with the network at which the DT-AS is located, sends the trigger message to the M2M UE, so as to implement that the DT-AS identifies the trigger message, so that the M2M UE establishes a connection with the third-party AS.