M2M Application Registration via CSE Identifier Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In M2M communication systems, there is no effective mechanism for the IN-CSE to acquire the M2M-Ext-ID, preventing the implementation of device triggering processes.
Innovation Solution
The proposed solution involves an application registration method where the IN-CSE receives a first registration request from an AE of an M2M SP, sending a second registration request to a NSE, and receiving a first registration response, which includes a binding relationship between the identifier of a CSE in a UE and the M2M-Ext-ID, enabling the IN-CSE to locally store this information and notify the AE of successful registration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the IN-CSE follows the traditional registration process without an effective mechanism, then the registration process is simple, but the IN-CSE cannot acquire the M2M-Ext-ID, preventing device triggering
Solution Approach 1:
The M2M-Ext-ID is bound to the CSE identifier in advance during the registration process. The IN-CSE receives the binding relationship between the CSE identifier and M2M-Ext-ID from the AE before initiating device triggering operations, ensuring the identifier is readily available when needed.
Solution Approach 2:
The patent introduces an intermediary binding relationship mechanism that connects the CSE identifier and M2M-Ext-ID through the registration process. This intermediary structure allows the IN-CSE to acquire the M2M-Ext-ID indirectly through the binding relationship rather than requiring direct access mechanisms.
2Adaptability or versatility
If the IN-CSE acquires M2M-Ext-ID through the new registration mechanism, then device triggering becomes possible, but the registration process becomes more complex
Solution Approach 1:
The registration mechanism is designed to serve multiple functions: it not only registers the CSE with the IN-CSE but also simultaneously establishes the binding relationship between CSE identifier and M2M-Ext-ID. This multi-functional approach enables device triggering capability without requiring separate mechanisms.
Solution Approach 2:
The AE performs the binding operation autonomously during the registration process by including the binding relationship between CSE identifier and M2M-Ext-ID in the registration request. The system self-configures the necessary identifiers without requiring additional manual configuration or complex external mechanisms.
3Loss of information
If binding relationship is included in registration request, then M2M-Ext-ID can be acquired for triggering, but information transmission volume increases
Solution Approach 1:
The binding relationship between CSE identifier and M2M-Ext-ID is merged into the existing registration request message. By combining multiple pieces of information (CSE registration data and identifier binding) into a single message exchange, the patent avoids additional separate transmissions while ensuring complete information availability.
Data Source
Figure 1~2
Figure 3~5
AI summary
Provided are application registration methods and apparatuses. In a registration method, a Common Services Entity in an Infrastructure Node (IN-CSE) receives a first registration request from an Application Entity (AE) of a Machine-to-Machine/Man Service Provider (M2M SP), wherein the first registration request carries a binding relationship between an identifier of a CSE in a User Equipment (UE) and an M2M External Identifier (M2M-Ext-ID) of the UE; the IN-CSE sends a second registration request to an underlying Network Services Entity (NSE); and the IN-CSE receives a first registration response from the NSE, wherein the first registration response is a response message corresponding to the second registration request. By means of the technical solution, the registration of an M2M application is implemented, and the technical problem in the related art that the processes such as device triggering cannot be triggered due to the lack of an effective mechanism for acquiring an M2M-Ext-ID is solved.