M2M Response Type Parameter for Communication Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Machine-to-Machine (M2M) communication, there is no defined procedure for distinguishing between the transmission and reception of request messages and response information, leading to potential errors due to differing procedures among devices.
Innovation Solution
A method and apparatus for M2M devices to separate request message transmission from response information reception, using response type parameters such as blocking, synchronous non-blocking, and asynchronous non-blocking to manage the reception process based on the type of response expected.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a uniform procedure is used for transmitting request messages and receiving response information across all M2M devices, then device complexity is reduced, but communication errors occur due to incompatible procedures between devices
Solution Approach 1:
The patent applies parameter changes by introducing a response type parameter that can take different values (first value, second value, third value) to indicate different response receipt procedures. This allows the system to adapt the communication procedure dynamically based on the parameter value, resolving the contradiction between uniformity and compatibility by making the procedure configurable through parameter variation.
2Reliability
If different procedures are used for receiving response information based on device requirements, then communication reliability is improved, but device complexity increases due to multiple procedure implementations
Solution Approach 1:
The patent implements universality by creating a single M2M device capable of performing multiple response receipt procedures (first, second, and third procedures) based on the response type parameter value. The device universally supports different communication patterns without requiring separate specialized devices, thereby improving reliability through procedure differentiation while managing complexity through a unified multi-functional architecture.
3Measurement precision
If response information reception is separated from request message transmission procedures, then communication accuracy is improved, but system complexity increases due to separate procedure management
Solution Approach 1:
The patent applies segmentation by separating the request message transmission procedure from the response information receipt procedure. The response type parameter indicates which specific receipt procedure to use, allowing the system to segment the communication process into distinct phases with different handling methods. This improves communication accuracy by enabling precise procedure selection while managing complexity through structured separation.
Data Source
AI summary
Provided is a procedure for receiving response information in response to a request message in an M2M system. Such a procedure may include transmitting a request message; determining a response type parameter corresponding to the request message; and receiving response information according to the response type parameter, wherein one of blocking, synchronous non-blocking (nonBlockingRequestSynch) and asynchronous non-blocking (nonBlockingRequestAsynch) is set as the response type parameter.