1 Scope
This document specifies the end-to-end communication protocols in M2M service systems, including communication protocols between M2M end devices and service platforms and between service platforms and applications.
This document applies to M2M service systems.
2 Normative References
There are no normative references in this document.
3 Terms, definitions and abbreviations
3.1 Terminology and definitions
The following terms and definitions apply to this document.
4 Overview of the agreement
4.1 General overview
The M2M Application Communication Protocol is an application layer protocol designed to implement the data communication process between M2M end devices and M2M service platforms and between M2M service platforms and M2M applications in M2M services.
5 Protocols between M2M end devices and M2M service platforms
5.1 Protocol Message Description
5.1.1 Protocol Message Structure
5.1.1.1 Message Composition
For different M2M services, e.g. video-based high data volume services, other protocols such as http, Ftp, etc. are considered, and for higher processing power end devices, different protocols may be used for different bandwidths and different types of services.
This document is intended to be a lightweight protocol for terminal management data and small data volume service data between M2M terminal devices and M2M service platforms.
Unless otherwise stated, the protocol uses synchronous message interaction and each request message shall be answered by an answer message. The message consists of a message header and a message body. The structure of the message is shown in Figure 5, see A.1 in Appendix A.
5.2 Basic principles of protocol interaction
5.2.1 Logical Connection
The concept of a logical connection (hereinafter referred to as a connection) is used in the communication protocol between the M2M Terminal Equipment and the M2M Service Platform. A logical connection is a complete message interaction between an M2M Terminal Equipment and an M2M Service Platform. The M2M Terminal Equipment logs in to the M2M Service Platform with a login request message, after which the M2M Service Platform authenticates and sends a login reply message, and ends when one end of the communication initiates an exit request and the other end sends an exit reply. During this interaction, communication can take the form of SMS, data-based TCP or UDP, or a mixed mode where the communication can be switched between logical connections. It should be noted, however, that for a pair of requests and answers, they should be done in the same communication mode.
5.2.2 Long connection and short connection
When using IP-based communication methods for bearing, according to whether the IP link connection between the M2M terminal equipment and the M2M service platform has always existed, there are two types of connection: long connection and short connection.
A long connection means that multiple data messages can be sent continuously during a connection and if no data messages are sent, a heartbeat message needs to be sent by the M2M end device to maintain the connection. A short connection is a connection process that is established when data is exchanged between two parties and is disconnected when the data has been sent.
5.3 Protocol functions and their interaction
5.3.1 Registration of terminal equipment
5.3.1.1 M2M terminal device number acquisition
5.3.2 Terminal device login
Only registered terminals can perform login operations. Before a terminal can interact with the M2M Service Platform, if its status is not logged in, it needs to log in to the M2M Service Platform. The M2M Service Platform does not accept messages from terminals that are not logged in. Therefore, M2M Terminals shall first send a login request message prior to data interaction with the M2M Service Platform. See F.2 for details.
The login process for M2M Terminals is shown in Figure 11.
5.3.3 Terminal Device Logout
When the M2M Terminal no longer requires the existing connection to transmit data, it actively notifies the M2M Service Platform to close the connection. Upon receipt of the logout request, the service platform returns an answer, clears the terminal connection information and records the log.
The M2M Service Platform may also forcibly request the M2M Terminal to log out. Upon receipt of the control request, the terminal shall also send a logout message to the service platform. See F.3 for details.
In the case of a communication failure between the M2M Terminal and the M2M Service Platform, the Terminal and the Service Platform may decide directly that the Terminal has entered the Logout state, or the following strategy may be used: The party that first detects the communication failure (i.e. either the M2M Terminal or the M2M Service Platform) sends a Logout message to the other party and reports the communication failure via the status word of the Logout message. After the logout has been sent by the requesting party, the requesting party shall release the connection upon receipt of the logout response or reception timeout.
Disconnection/exit of the M2M Device from the system is a synchronous interaction event.
5.3.4 Connection Detection
In long connection mode, if the terminal does not send data for a certain period of time, the M2M terminal shall send a connection detection message to the M2M service platform indicating that the M2M terminal device is in operation and the M2M service platform shall respond upon receipt. See F.4 for details.
If the M2M Terminal does not receive a heartbeat response message from the M2M Service Platform for a threshold number of consecutive times, the M2M Terminal may be in a communication fault state with the MM Service Platform and the M2M Terminal shall be alerted by an indicator light; if the M2M Service Platform does not receive a connection detection message from the M2M Terminal within a specified period of time, the M2M Terminal is faulty.
If the M2M Service Platform does not receive consecutive heartbeat messages, the M2M Service Platform considers that the M2M End Device may be in a communication failure state with the M2M Service Platform.
The M2M Endpoint Device Connection Detection message is a Synchronous Interaction Event.
5.3.5 Terminal Information Reporting
The M2M Terminal Equipment may report information to the M2M Service Platform as required, and the M2M Service Platform shall respond upon receipt. See F.5 for details.
The information reported by the M2M Terminal Equipment refers to information managed by the M2M Service Platform, such as configuration information, alarm information, statistics, etc. M2M Terminal Equipment may send configuration parameters to the M2M Service Platform when it detects changes in its own parameters or when requested by the M2M Service Platform; M2M Terminal Equipment may send alarm information to the M2M Service Platform when it detects changes in external states, alarm states or when information collected exceeds a set threshold; M2M Terminal Equipment may report statistical data as required by the M2M Service Platform, Terminals are required to record their monthly service usage flags and report to the M2M service platform whether they are using the service. In addition, it should be noted that M2M end devices can report alarms to the M2M Service Platform directly by SMS without logging in, due to certain communication failures.
6 Protocols between the M2M Service Platform and M2M Applications
6.1 Protocol Interaction Mechanism
6.1.1 Protocol Interface and Message Structure
This protocol supports two connection methods; the standard HTTP based WEBService method and the long connection method. See Appendix H for details.
6.2 Protocol Security Mechanisms 6.2.1 Data Security
Interaction messages between the M2M service platform and the M2M application require a digest field which takes as input the message header, message body, user name and password.
The user name and password are assigned by the M2M Service Platform to the M2M Application. Messages sent from the M2M Application to the M2M Service Platform and messages sent from the M2M Service Platform to the M2M Application require the digest to be calculated using the algorithm described above.
The interaction between the M2M Application and the M2M Service Platform consists of two types of keys: the Base Key and the Session Key.
Appendix A (Informative) Protocol Message Structure between M2M End Device and M2M Service Platform
Appendix B (Informative) TLV Description
Appendix C (Informative) Command Code Definition between M2M End Device and M2M Service Platform
Appendix D (Informative) Sub-Packet Interaction Mechanism
Appendix E (Informative) Synchronous Interaction Messages and Asynchronous Interaction Messages
Appendix F (Informative) Definition of Protocol Messages between M2M Terminal Equipment and M2M Service Platforms
Appendix G (Informative) Protocol Interaction Mechanisms between M2M Terminal Equipment and M2M Service Platforms
Appendix H (Informative) Description of protocols between M2M Service Platforms and M2M Applications
Appendix I (Informative) Definition of Protocol Messages between M2M Service Platforms and M2M Applications
Foreword
1 Scope
2 Normative References
3 Terms, definitions and abbreviations
4 Overview of the agreement
5 Protocols between M2M end devices and M2M service platforms
6 Protocols between the M2M Service Platform and M2M Applications
Appendix A (Informative) Protocol Message Structure between M2M End Device and M2M Service Platform
Appendix B (Informative) TLV Description
Appendix C (Informative) Command Code Definition between M2M End Device and M2M Service Platform
Appendix D (Informative) Sub-Packet Interaction Mechanism
Appendix E (Informative) Synchronous Interaction Messages and Asynchronous Interaction Messages
Appendix F (Informative) Definition of Protocol Messages between M2M Terminal Equipment and M2M Service Platforms
Appendix G (Informative) Protocol Interaction Mechanisms between M2M Terminal Equipment and M2M Service Platforms
Appendix H (Informative) Description of protocols between M2M Service Platforms and M2M Applications
Appendix I (Informative) Definition of Protocol Messages between M2M Service Platforms and M2M Applications
Standard
GB/Z 41383-2022 Technical requirements of M2M service communication protocol (English Version)
Standard No.
GB/Z 41383-2022
Status
valid
Language
English
File Format
PDF
Word Count
82500 words
Price(USD)
3075.0
Implemented on
2022-11-1
Delivery
via email in 1~10 business day
Detail of GB/Z 41383-2022
Standard No.
GB/Z 41383-2022
English Name
Technical requirements of M2M service communication protocol
1 Scope
This document specifies the end-to-end communication protocols in M2M service systems, including communication protocols between M2M end devices and service platforms and between service platforms and applications.
This document applies to M2M service systems.
2 Normative References
There are no normative references in this document.
3 Terms, definitions and abbreviations
3.1 Terminology and definitions
The following terms and definitions apply to this document.
4 Overview of the agreement
4.1 General overview
The M2M Application Communication Protocol is an application layer protocol designed to implement the data communication process between M2M end devices and M2M service platforms and between M2M service platforms and M2M applications in M2M services.
5 Protocols between M2M end devices and M2M service platforms
5.1 Protocol Message Description
5.1.1 Protocol Message Structure
5.1.1.1 Message Composition
For different M2M services, e.g. video-based high data volume services, other protocols such as http, Ftp, etc. are considered, and for higher processing power end devices, different protocols may be used for different bandwidths and different types of services.
This document is intended to be a lightweight protocol for terminal management data and small data volume service data between M2M terminal devices and M2M service platforms.
Unless otherwise stated, the protocol uses synchronous message interaction and each request message shall be answered by an answer message. The message consists of a message header and a message body. The structure of the message is shown in Figure 5, see A.1 in Appendix A.
5.2 Basic principles of protocol interaction
5.2.1 Logical Connection
The concept of a logical connection (hereinafter referred to as a connection) is used in the communication protocol between the M2M Terminal Equipment and the M2M Service Platform. A logical connection is a complete message interaction between an M2M Terminal Equipment and an M2M Service Platform. The M2M Terminal Equipment logs in to the M2M Service Platform with a login request message, after which the M2M Service Platform authenticates and sends a login reply message, and ends when one end of the communication initiates an exit request and the other end sends an exit reply. During this interaction, communication can take the form of SMS, data-based TCP or UDP, or a mixed mode where the communication can be switched between logical connections. It should be noted, however, that for a pair of requests and answers, they should be done in the same communication mode.
5.2.2 Long connection and short connection
When using IP-based communication methods for bearing, according to whether the IP link connection between the M2M terminal equipment and the M2M service platform has always existed, there are two types of connection: long connection and short connection.
A long connection means that multiple data messages can be sent continuously during a connection and if no data messages are sent, a heartbeat message needs to be sent by the M2M end device to maintain the connection. A short connection is a connection process that is established when data is exchanged between two parties and is disconnected when the data has been sent.
5.3 Protocol functions and their interaction
5.3.1 Registration of terminal equipment
5.3.1.1 M2M terminal device number acquisition
5.3.2 Terminal device login
Only registered terminals can perform login operations. Before a terminal can interact with the M2M Service Platform, if its status is not logged in, it needs to log in to the M2M Service Platform. The M2M Service Platform does not accept messages from terminals that are not logged in. Therefore, M2M Terminals shall first send a login request message prior to data interaction with the M2M Service Platform. See F.2 for details.
The login process for M2M Terminals is shown in Figure 11.
5.3.3 Terminal Device Logout
When the M2M Terminal no longer requires the existing connection to transmit data, it actively notifies the M2M Service Platform to close the connection. Upon receipt of the logout request, the service platform returns an answer, clears the terminal connection information and records the log.
The M2M Service Platform may also forcibly request the M2M Terminal to log out. Upon receipt of the control request, the terminal shall also send a logout message to the service platform. See F.3 for details.
In the case of a communication failure between the M2M Terminal and the M2M Service Platform, the Terminal and the Service Platform may decide directly that the Terminal has entered the Logout state, or the following strategy may be used: The party that first detects the communication failure (i.e. either the M2M Terminal or the M2M Service Platform) sends a Logout message to the other party and reports the communication failure via the status word of the Logout message. After the logout has been sent by the requesting party, the requesting party shall release the connection upon receipt of the logout response or reception timeout.
Disconnection/exit of the M2M Device from the system is a synchronous interaction event.
5.3.4 Connection Detection
In long connection mode, if the terminal does not send data for a certain period of time, the M2M terminal shall send a connection detection message to the M2M service platform indicating that the M2M terminal device is in operation and the M2M service platform shall respond upon receipt. See F.4 for details.
If the M2M Terminal does not receive a heartbeat response message from the M2M Service Platform for a threshold number of consecutive times, the M2M Terminal may be in a communication fault state with the MM Service Platform and the M2M Terminal shall be alerted by an indicator light; if the M2M Service Platform does not receive a connection detection message from the M2M Terminal within a specified period of time, the M2M Terminal is faulty.
If the M2M Service Platform does not receive consecutive heartbeat messages, the M2M Service Platform considers that the M2M End Device may be in a communication failure state with the M2M Service Platform.
The M2M Endpoint Device Connection Detection message is a Synchronous Interaction Event.
5.3.5 Terminal Information Reporting
The M2M Terminal Equipment may report information to the M2M Service Platform as required, and the M2M Service Platform shall respond upon receipt. See F.5 for details.
The information reported by the M2M Terminal Equipment refers to information managed by the M2M Service Platform, such as configuration information, alarm information, statistics, etc. M2M Terminal Equipment may send configuration parameters to the M2M Service Platform when it detects changes in its own parameters or when requested by the M2M Service Platform; M2M Terminal Equipment may send alarm information to the M2M Service Platform when it detects changes in external states, alarm states or when information collected exceeds a set threshold; M2M Terminal Equipment may report statistical data as required by the M2M Service Platform, Terminals are required to record their monthly service usage flags and report to the M2M service platform whether they are using the service. In addition, it should be noted that M2M end devices can report alarms to the M2M Service Platform directly by SMS without logging in, due to certain communication failures.
6 Protocols between the M2M Service Platform and M2M Applications
6.1 Protocol Interaction Mechanism
6.1.1 Protocol Interface and Message Structure
This protocol supports two connection methods; the standard HTTP based WEBService method and the long connection method. See Appendix H for details.
6.2 Protocol Security Mechanisms 6.2.1 Data Security
Interaction messages between the M2M service platform and the M2M application require a digest field which takes as input the message header, message body, user name and password.
The user name and password are assigned by the M2M Service Platform to the M2M Application. Messages sent from the M2M Application to the M2M Service Platform and messages sent from the M2M Service Platform to the M2M Application require the digest to be calculated using the algorithm described above.
The interaction between the M2M Application and the M2M Service Platform consists of two types of keys: the Base Key and the Session Key.
Appendix A (Informative) Protocol Message Structure between M2M End Device and M2M Service Platform
Appendix B (Informative) TLV Description
Appendix C (Informative) Command Code Definition between M2M End Device and M2M Service Platform
Appendix D (Informative) Sub-Packet Interaction Mechanism
Appendix E (Informative) Synchronous Interaction Messages and Asynchronous Interaction Messages
Appendix F (Informative) Definition of Protocol Messages between M2M Terminal Equipment and M2M Service Platforms
Appendix G (Informative) Protocol Interaction Mechanisms between M2M Terminal Equipment and M2M Service Platforms
Appendix H (Informative) Description of protocols between M2M Service Platforms and M2M Applications
Appendix I (Informative) Definition of Protocol Messages between M2M Service Platforms and M2M Applications
Contents of GB/Z 41383-2022
Foreword
1 Scope
2 Normative References
3 Terms, definitions and abbreviations
4 Overview of the agreement
5 Protocols between M2M end devices and M2M service platforms
6 Protocols between the M2M Service Platform and M2M Applications
Appendix A (Informative) Protocol Message Structure between M2M End Device and M2M Service Platform
Appendix B (Informative) TLV Description
Appendix C (Informative) Command Code Definition between M2M End Device and M2M Service Platform
Appendix D (Informative) Sub-Packet Interaction Mechanism
Appendix E (Informative) Synchronous Interaction Messages and Asynchronous Interaction Messages
Appendix F (Informative) Definition of Protocol Messages between M2M Terminal Equipment and M2M Service Platforms
Appendix G (Informative) Protocol Interaction Mechanisms between M2M Terminal Equipment and M2M Service Platforms
Appendix H (Informative) Description of protocols between M2M Service Platforms and M2M Applications
Appendix I (Informative) Definition of Protocol Messages between M2M Service Platforms and M2M Applications
