WO2014166257A1

WO2014166257A1 - Trigger message processing method, apparatus and communication system

Info

Publication number: WO2014166257A1
Application number: PCT/CN2013/087295
Authority: WO
Inventors: 于琦
Original assignee: 华为技术有限公司
Priority date: 2013-04-09
Filing date: 2013-11-18
Publication date: 2014-10-16
Also published as: CN104105051A

Abstract

Disclosed are a trigger message processing method, apparatus and communication system, which comprise the trigger message processing method for a network application end, the trigger message processing method for a network service capability layer server, the network application end and server for the trigger message processing method of the present invention, and an M2M communication system. By effectively designing the generation and interaction process of the trigger message between the network service capability layer server and the network application end, and reasonably configuring parameters, the present invention optimizes the device trigger function of the M2M network.

Description

Description of the invention trigger message processing method, device and communication system

The present invention relates to the field of computer and communication technologies, and in particular, to a trigger message processing method, apparatus, and communication system.

Background technique

Machine-to-Machine Communications (M2M communication) is a networked application and service centered on machine intelligent interaction. It can be embedded in the machine by embedding wireless or wired communication modules and application processing logic. The data communication of interventions meets the information needs of users in monitoring, command and dispatch, data collection and measurement.

The overall goal of the European Telecommunications Standards Institute for Machine-to-Machine Communications (ETSI M2M) standard is to create open standards for the business layer of M2M communication to facilitate the creation of an integrated The future network of services enables M2M services to be interoperable, and also enables M2M applications to share basic services and implement them independently of the network. Figure 1 is an M2M architecture diagram. The M2M Device Application (M2M DA) on the M2M Device (M2M Device) communicates with the M2M Device Service Capability Layer (M2M DSCL) through the dla interface. On the M2M network. The M2M Network Application (M2M NA) communicates with the M2M Network Service Capability Layer (M2M NSCL) through the M2M network; the ETSI M2M standard defines the mid interface between the M2M NSCL and the M2M DSCL, M2M NA The M2M DA loaded on the M2M device can be accessed through the mid interface.

At present, M2M communication can be based on wired mode and wireless mode, and wireless mode includes cellular network and short-distance, and 3GPP (The 3rd Generation Partnership Project) cellular network is a widely used method.

The architecture of the existing 2G/3G/LTE network supporting M2M is shown in Figure 2, where the core of the 2G network The network mainly includes a Mobile Service Switching Center (MSC); the core network of the 3G network mainly includes a Serving GPRS Support Node (SGSN), a Gateway GPRS Support Node (GGSN), and an LTE network. The core network mainly includes three logical functions: Mobility Management Entity (ΜΜΕ), Serving Gateway (S-GW), and Packet Data Network Gateway (P-GW). The switching center/service GPRS support node/mobile management entity is responsible for signaling and signaling encryption, roaming, tracking and other functions, assigning user temporary identity, security functions, etc., which corresponds to the current Universal Mobile Telecommunication System (UMTS). The control plane portion of the system internal service GPRS support node. The service gateway is responsible for the local mobility anchor and the mobility anchor inside the 3GPP system and the lawful interception related information; the mobile switching center/gateway GPRS support node/packet data network gateway is responsible for policy enforcement and charging and lawful interception related functions. . The Machine Type Communications Interworking Function (MTC-IWF) is an interface between the 3GPP network and the Service Capability Server (SCS); the Application Server (AS) sends the message to the machine through the service capability server. Type communication interaction device MTC-IWF. The application server corresponds to the M2M network application end on the ETSI M2M network, and the service capability server corresponds to the network service capability layer server on the ETSI M2M network. The User Equipment (UE) supporting the M2M application accesses the wireless network through a Radio Access Node (RAN).

Currently 3GPP supports 3 M2M modes, Direct Mode, Indirect Mode (Indirect

Model) and Hybrid Model. The direct mode is that the AS directly communicates with the GGSN/P-GW through the Gi or SGi interface; the indirect mode is that the AS communicates with the GGSN/P-GW through the SCS, and the SCS may be controlled by the 3GPP operator or the M2M service provider in the indirect mode; Mixed mode is the existence of both ways.

Device trigger is used by the SCS to send information to the UE through the 3GPP network for corresponding application layer processing, such as initiating communication with the SCS and AS in indirect or mixed mode. When there is no IP address of the UE on the SCS/AS, the UE is triggered to establish a connection to the SCS/AS through the message. However, for the ETSI M2M network system, how the device trigger request related parameters are generated between the network service capability layer server and the network application end, and the triggering interaction process is not currently defined.

Summary of the invention

The embodiment of the invention provides a method, a device and a communication system for triggering a message to solve the problem of how to generate a trigger message and how to interact with the ETSI M2M network between the network service capability layer server and the network application end.

The embodiment of the invention discloses the following technical solutions:

The first aspect provides a method for processing a trigger message of a network application, where the processing method includes the following steps:

Generating a trigger message for initiating a trigger device information interaction process, and sending the trigger message to a network service capability layer server; receiving a trigger report message generated by the network service capability layer server according to the trigger message, the trigger report The message is used to feedback whether the trigger device information interaction process is successful.

In a first possible implementation manner of the first aspect, the trigger message includes a device identification number parameter, where the device identification number parameter is used to identify a device to be triggered, and the type is an external identification number, and the mobile subscription international ISDN number Any of the International Mobile Subscriber Identity and the International Mobile Equipment Identity.

In a second possible implementation manner of the first aspect, the trigger message further includes any one or more of an application identifier parameter, a validity period parameter, and a trigger load parameter, where the application identifier number parameter is used to identify that The triggering process initiated by the network application end; the validity period parameter is a valid time when the triggering message set by the network application end expires; and the triggering load parameter includes information that is required by the network application end to be transmitted to the device by the 3GPP network.

In a third possible implementation manner of the first aspect, the triggering message includes a device identification number parameter or a reason parameter, where the reason parameter is used to identify whether the triggering process is successful or not.

The second aspect provides a method for processing a trigger message of a network service capability layer server, including The following steps:

After receiving the trigger message, generating a device trigger request message for transmitting the trigger message and sending the message to the machine type communication interaction device;

a device triggering report message sent by the receiver type communication interaction device, where the device trigger report message is generated according to the device trigger request message, and used to feedback whether the triggering process is successful;

After receiving the device trigger report message, the network application end sends a trigger report message for reporting whether the trigger process is successful to the network application end.

In a first possible implementation manner of the second aspect, the device trigger request message includes a device identification number parameter, a service capability server identification number parameter, a trigger reference number parameter, a validity period parameter, a priority parameter, and an application port identification number parameter. And the one or more of the triggering load parameters; wherein the device identification number parameter is used to identify the device to be triggered; the service capability server identification number parameter is used to identify a network service capability layer server that issues a device trigger request message; The trigger reference number parameter is an identity number of the device trigger request message; the validity period parameter is a valid time when the trigger message set by the network application end expires; and the priority parameter is used to identify a priority processing level of the device trigger request message. The application port identification number parameter is used to identify a network application end that initiates a triggering process; the triggering load parameter includes information that is required by the network application end to be transmitted to the device by the 3GPP network.

In a second possible implementation manner of the second aspect, the device trigger report message includes any one or more of a device identification number parameter, a trigger reference number parameter, and a cause parameter; wherein the device identification number parameter is used The device to be triggered is identified; the trigger reference number parameter is an identity number of the device trigger request message; and the cause parameter is used to identify whether the trigger process is successful or not.

In a third possible implementation manner of the second aspect, if the trigger message received by the network service capability layer server does not include the validity period parameter or the application port identifier number parameter, the network service capability layer server sets the self-set.

In a fourth possible implementation manner of the second aspect, after the network service capability layer server sends the device trigger request message to the machine type communication interaction device, the machine type communication interaction device supports the mechanism supported by the existing 3GPP network. Send a trigger request to the device. The third aspect provides a network application end, where the trigger message sending module is configured to send a trigger message to the network service capability layer server, where the trigger message is used by the network application end to trigger the device to perform information interaction; and the trigger report message receiving module is triggered. Used to receive a trigger report message returned by the network service capability layer server.

In a first possible implementation manner of the third aspect, the trigger message sent by the trigger message sending module includes a device identification number parameter, where the device identification number parameter is used to identify a device to be triggered, and the type is an external identification number. , mobile subscription international ISDN number, international mobile subscriber identity code and international mobile equipment identification code.

In a second possible implementation manner of the third aspect, the trigger message sent by the trigger message sending module further includes any one or more of an application identifier parameter, a validity period parameter, and a trigger load parameter, where the application identifier is The parameter is used to identify which network application initiates the triggering process; the validity period parameter is the effective time of the trigger message set by the network application end; the triggering load parameter includes the network application end constructing that needs to be transmitted to the device by the 3GPP network. Information.

In a third possible implementation manner of the third aspect, the trigger report message received by the trigger report message receiving module includes a device identifier parameter or a cause parameter, where the cause parameter is used to identify whether the trigger process is successful or not. .

In a fourth aspect, a server is provided, including a trigger message receiving module, configured to receive a trigger message sent by a network application end, where the trigger message is used by a network application end to trigger a device for information interaction; After receiving the trigger message, the generating device trigger request message is sent to the machine type communication interaction device; the device trigger report receiving module is configured to send a device trigger report message sent by the receiver type communication interaction device, and the device triggers the report message according to the device. The triggering request message is generated to be used to feedback whether the triggering process is successful. The triggering report message sending module is configured to return the triggering report message to the network application end.

In a first possible implementation manner of the fourth aspect, the device trigger request message sent by the device trigger request message sending module includes a device identification number parameter, a service capability server identification number parameter, a trigger reference number parameter, a validity period parameter, and a priority Level parameter, application port identification number parameter and trigger load Any one or more of the parameters; wherein the device identification number parameter is used to identify a device to be triggered; the service capability server identification number parameter is used to identify a network service capability layer server that issues a device trigger request message; The reference number parameter is an identity number of the device trigger request message; the validity period parameter is a valid time when the trigger message of the network application end expires; the priority parameter is used to identify a priority processing level of the device trigger request message; The application port identification number parameter is used to identify a network application end that initiates a triggering process; the triggering load parameter includes a network application end configuration requirement.

Information that the 3GPP network passes to the device.

In a second possible implementation manner of the fourth aspect, the device trigger report message received by the device trigger report receiving module includes any one or more of a device identification number parameter, a trigger reference number parameter, and a cause parameter; The device identification number parameter is used to identify the device to be triggered; the trigger reference number parameter is an identity number of the device trigger request message; and the reason parameter is used to identify whether the triggering process is successful or not.

In a third possible implementation manner of the fourth aspect, if the received trigger message does not include a valid period parameter or an application port identifier number parameter, the server sets the self-set.

In a fourth possible implementation manner of the fourth aspect, after the server sends the device trigger request message to the machine type communication interaction device, the machine type communication interaction device sends the trigger request by using an existing 3GPP network support mechanism. To the device.

In a fifth aspect, an M2M communication system is provided, the communication system comprising the network application end of the third aspect.

In a sixth aspect, an M2M communication system is provided, the communication system comprising the server of the fourth aspect.

In the embodiment of the present invention, the device triggering function of the M2M network is optimized by effectively designing a message generation and interaction process between the network service capability layer server and the network application end, and reasonable configuration parameters.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will be implemented. BRIEF DESCRIPTION OF THE DRAWINGS The drawings, which are used in the description of the prior art, are briefly described. It is obvious that the drawings in the following description are some embodiments of the present invention, and no one skilled in the art Further drawings can also be obtained from these drawings.

1 is a schematic diagram of an M2M system architecture defined by the prior art ETSI;

2 is a system architecture diagram of a prior art 2G/3G/LTE network supporting M2M;

FIG. 3 (including 3a, 3b, and 3c) is a schematic diagram of a trigger message processing flow of an embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly described in conjunction with the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are Some embodiments, rather than all of the embodiments, are invented. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The specific embodiments of the present invention are further described in detail below with reference to the drawings and embodiments. The following examples are intended to illustrate the invention but are not intended to limit the scope of the invention.

As shown in FIG. 3 (including 3a, 3b, and 3c), an embodiment of the trigger message processing method of the present invention includes, at the network application end, the following steps:

The network application end generates a trigger message for initiating a process of triggering the device information interaction, and sends the trigger message to the network service capability layer server.

52. Receive a trigger report message generated by the network service capability layer server according to the trigger message, where the trigger report message is used to feedback whether the trigger device information interaction process is successful.

The network application end can send a trigger message to the network service capability layer server through the mla interface. The trigger message may include a device identification number (Device id) parameter, where the device identification number parameter is used to identify a device to be triggered, and the type is an external identification number (External id), a mobile subscription international ISDN number (MSISDN), and an international Any one of Mobile Subscriber Identity (IMSI) and International Mobile Equipment Identity (IMEI).

In addition, the trigger message may further include an application identifier (Application id) parameter, which is effective. Any one or more of a validity period parameter and a trigger payload parameter; wherein the application identification number parameter is used to identify which network application end initiates a triggering process, and is used by the ETSI to identify the network. The number of the application end, assigned by the M2M service provider, is the only identifier in the world. The validity period parameter is a valid time when the trigger message set by the network application end expires. Specifically, it may be a period of time or a deadline, for example, the validity period is 30 minutes or valid before 5 曰 13 pm in 2012. When the 3GPP network is congested, the network element node may save the trigger information until the expiration date expires. The trigger load parameter includes information that is configured by the network application end and needs to be transmitted by the 3GPP network to the device (Device).

The trigger report message includes a device identifier (Device id) parameter or a cause (initial) parameter, and the cause parameter is used to identify whether the triggering process is successful or not.

Further, the server side of the network service capability layer includes:

After receiving the trigger message, the network service capability server generates a device trigger request message for transmitting the trigger message and sends the message to the machine type communication interaction device (MTC-IWF);

a device trigger report message sent by the receiver type communication interaction device, where the device trigger report message is generated according to the device trigger request message, and is used to feedback whether the triggering process is successful.

After receiving the device trigger report message, sending a trigger report message to the network application end for feeding back to the network application whether the triggering process is successful.

The network service capability layer server may send a device trigger request message to the machine type communication interaction device through the Tsp interface.

The device trigger request message may include a device identification number parameter, a service capability server identification number (SCS id ) parameter, a trigger reference number parameter, a validity period parameter, a priority parameter, and an application port identification number (Application) Any one or more of a port id parameter and a trigger payload parameter; wherein the device identification number parameter is used to identify a device to be triggered; and the service capability server identification number parameter is used to identify a device trigger request a network service capability layer server of the message; the trigger reference number parameter is an identity number of the device trigger request message; and the validity period parameter is a valid time when the trigger message set by the network application end expires; The priority parameter is used to identify a priority processing level of the device trigger request message; the application port identification number parameter is used to identify a network application end that initiates a triggering process; and the triggering load parameter includes a network application end configured to be transmitted by a 3GPP network to Device information.

The device trigger report message may include any one or more of a device identification number parameter, a trigger reference number parameter, and a cause parameter; wherein the device identification number parameter is used to identify a device to be triggered; The device triggers the identity number of the request message; the reason parameter is used to identify whether the triggering process is successful or not.

If the trigger message received by the network service capability layer server does not include the validity period parameter or the application port identification number parameter, the network service capability layer server sets itself, and the application port identification number parameter can be set as the application identification number, because the network service capability layer server The trigger message is received through the mla interface. The validity period parameter can be set by NSCL as needed.

After the network service capability layer server sends the device trigger request message to the machine type communication interaction device, the machine type communication interaction device sends the trigger request to the device through the mechanism supported by the existing 3GPP network. If the 3GPP network fails to send a trigger request, it also returns a device trigger report message and passes the reason for the failure in the reason parameter.

Based on the foregoing method, a network application end according to the third aspect of the present invention includes a trigger message sending module, configured to send a trigger message to a network service capability layer server, where the trigger message is used by the network application end to trigger the device to perform information interaction; The report message receiving module is configured to receive a trigger report message returned by the network service capability layer server.

The trigger message sent by the trigger message sending module may include a device identification number parameter, where the device identification number parameter is used to identify the device to be triggered, and the type is an external identification number, a mobile subscription international ISDN number, an international mobile subscriber identity code, and Any of the international mobile device identifiers.

The trigger message sent by the triggering message sending module may further include any one or more of an application identification number parameter, an expiration date parameter and a triggering load parameter; wherein the application identification number parameter is used to identify which network application end initiates the triggering The validity period parameter is a valid time when the trigger message set by the network application end expires; the trigger load parameter includes a network application end constructing requirement 3GPP Information that the network passes to the device.

The trigger report message received by the trigger report message receiving module may include a device identification number parameter or a cause parameter, where the cause parameter is used to identify whether the triggering process is successful or not.

The server according to the fourth aspect of the present invention includes a trigger message receiving module, configured to receive a trigger message sent by a network application end, where the trigger message is used by a network application end to trigger a device to perform information interaction; After the message sending module is configured to receive the trigger message, the generating device trigger request message is sent to the machine type communication interaction device; the device trigger report receiving module is configured to send the device trigger report message sent by the receiver type communication interaction device, and the device triggers the report message. And generating, according to the device trigger request message, a feedback triggering process, where the triggering report sending module is configured to return the triggering report message to the network application end.

The device trigger request message sent by the device trigger request message sending module may include a device identification number parameter, a service capability server identification number parameter, a trigger reference number parameter, a validity period parameter, a priority parameter, an application port identification number parameter, and a trigger load parameter. Any one or more of the device identifiers are used to identify the device to be triggered; the service capability server identification number parameter is used to identify a network service capability layer server that issues a device trigger request message; The parameter is an identity number of the device trigger request message; the validity period parameter is a valid time when the trigger message of the network application end expires; the priority parameter is used to identify a priority processing level of the device trigger request message; The identifier parameter is used to identify the network application end that initiates the triggering process. The triggering load parameter includes information that is required by the network application end to be transmitted to the device by the 3GPP network.

The device trigger report message received by the device trigger report receiving module may include any one or more of a device identification number parameter, a trigger reference number parameter, and a cause parameter; wherein the device identification number parameter is used to identify the device to be triggered; The trigger reference number parameter is an identity number of the device trigger request message; the cause parameter is used to identify whether the trigger process is successful or not.

If the received trigger message does not include the validity period parameter or the application port identification number parameter, it can be set by the server itself.

After the server sends a device trigger request message to the machine type communication interaction device, the machine class The type communication interaction device can send a trigger request to the device through a mechanism supported by the existing 3GPP network.

An M2M communication system according to the fifth aspect of the present invention, wherein the communication system comprises the network application end according to the third aspect.

A server based on the fourth aspect, the M2M communication system of the sixth aspect of the present invention, wherein the communication system comprises the server of the fourth aspect.

In the embodiment of the present invention, the device triggering function of the M2M network is optimized by effectively designing a trigger message generation and interaction process between the network service capability layer server and the network application end and reasonable configuration parameters.

Those of ordinary skill in the art will appreciate that aspects of the invention, or aspects of various aspects, may be embodied as a system, method, or computer program product. Thus, aspects of the invention, or possible implementations of various aspects, may be in the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, etc.), or a combination of software and hardware aspects, They are collectively referred to herein as "circuits," "modules," or "systems." Furthermore, aspects of the invention, or possible implementations of various aspects, may take the form of a computer program product, which is a computer readable program code stored on a computer readable medium.

The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing, such as random access memory (RAM), read only memory (ROM), Erase programmable read-only memory (EPROM or flash memory), optical fiber, portable read-only memory (CD-ROM:).

The processor in the computer reads the computer readable program code stored in the computer readable medium, such that the processor can perform the functional actions specified in each step or combination of steps in the flowchart; A device that functions as specified in each block, or combination of blocks.

The computer readable program code can be executed entirely on the user's computer, partly on the user's computer, as a separate software package, partly on the user's computer, and partly on the remote computer On, or entirely on a remote computer or server. It should also be noted that in some alternative implementations, the functions noted in the various steps of the flowcharts or in the blocks of the block diagrams may not occur in the order noted in the drawings. For example, two steps, or two blocks shown in succession may be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. The spirit and scope of the Ming. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

claims

1. A trigger message processing method on the network application side, characterized in that it includes the following steps: Generate a trigger message for initiating a trigger device information interaction process, and send the trigger message to the network service capability layer server; receive the The network service capability layer server generates a trigger report message based on the trigger message, and the trigger report message is used to feedback whether the trigger device information interaction process is successful.

2. The trigger message processing method of the network application side according to claim 1, characterized in that the trigger message includes a device identification number parameter, and the device identification number parameter is used to identify the device to be triggered, and its type is external identification. Any one of the number, international mobile subscription ISDN number, International Mobile Subscriber Identity Number and International Mobile Equipment Identity Number.

3. The trigger message processing method of the network application side according to claim 2, characterized in that the trigger message also includes any one or more of an application identification number parameter, a validity period parameter and a trigger load parameter; wherein the application The identification number parameter is used to identify which network application end initiates the triggering process; the validity period parameter is the validity time of the trigger message expiration set by the network application end; the trigger load parameter includes the data constructed by the network application end and needs to be passed to the 3GPP network Device information.

4. The trigger message processing method of the network application side according to claim 1, characterized in that the trigger report message includes a device identification number parameter or a cause parameter, and the cause parameter is used to identify whether the trigger process is successful and the reason for failure. .

5. A trigger message processing method for a network service capability layer server, characterized by including: after receiving the trigger message, generating a device trigger request message for transmitting the trigger message and sending it to the machine type communication interaction device; receiving A device trigger report message sent by a machine type communication interaction device, the device trigger report The message is generated according to the device trigger request message and is used to feedback whether the trigger process is successful; after receiving the device trigger report message, a trigger report message is sent to the network application end for feedback to the network application end whether the trigger process is successful.

6. The trigger message processing method of the network service capability layer server according to claim 5, characterized in that the device trigger request message includes a device identification number parameter, a service capability server identification number parameter, a trigger reference number parameter, and a validity period parameter. , any one or more of priority parameters, application port identification number parameters and trigger load parameters; wherein the device identification number parameter is used to identify the device to be triggered; the business capability server identification number parameter is used to identify the issuing device The network service capability layer server that triggers the request message; The trigger reference number parameter is the identity number of the device that triggers the request message; The validity period parameter is the validity time for the trigger message to expire set by the network application end; The priority parameter is used to Identifies the priority processing level of the device trigger request message; The application port identification number parameter is used to identify the network application end that initiates the trigger process; The trigger load parameter includes information constructed by the network application end that needs to be passed to the device by the 3GPP network.

7. The trigger message processing method of the network service capability layer server according to claim 5, wherein the device trigger report message includes any one or more of a device identification number parameter, a trigger reference number parameter and a cause parameter. ; The device identification number parameter is used to identify the device to be triggered; the trigger reference number parameter is the identity number of the device trigger request message; the cause parameter is used to identify whether the trigger process is successful and the reason for failure.

8. The trigger message processing method of the network service capability layer server according to claim 5, characterized in that if the trigger message received by the network service capability layer server does not include the validity period parameter or the application port identification number parameter, then the network service capability layer server The capability layer server sets itself.

9. The trigger message processing method of the network service capability layer server according to claim 5, characterized in that, after the network service capability layer server sends the device trigger request message to the machine type communication interaction device, the machine type communication interaction device Through mechanisms supported by existing 3GPP networks, the A trigger request is sent to the device.

10. A network application end, characterized in that it includes: a trigger message sending module for sending a trigger message to a network service capability layer server, where the trigger message is used for the network application end to trigger a device for information interaction; trigger report message reception The module is used to receive the trigger report message returned by the network service capability layer server.

11. The network application terminal according to claim 10, characterized in that, the trigger message sent by the trigger message sending module includes a device identification number parameter, and the device identification number parameter is used to identify the device to be triggered, and its type is Any one of the external identification number, the international mobile subscription ISDN number, the International Mobile Subscriber Identity and the International Mobile Equipment Identity.

12. The network application terminal according to claim 10, characterized in that, the trigger message sent by the trigger message sending module also includes any one or more of an application identification number parameter, a validity period parameter and a trigger load parameter; wherein The application identification number parameter is used to identify which network application end initiated the triggering process; the validity period parameter is the validity time of the trigger message expiration set by the network application end; the trigger load parameter includes the required 3GPP network constructed by the network application end. Information passed to the device.

13. The network application end of claim 10, wherein the trigger report message received by the trigger report message receiving module includes a device identification number parameter or a cause parameter, and the cause parameter is used to identify whether the trigger process is successful. and reasons for failure.

14. A server, characterized in that it includes: a trigger message receiving module, used to receive a trigger message sent by a network application end, where the trigger message is used by the network application end to trigger a device for information interaction; a device trigger request message sending module Used to generate device trigger request messages after receiving trigger messages. The device trigger report message is sent to the machine type communication interaction device; the device trigger report receiving module is used to receive the device trigger report message sent by the machine type communication interaction device. The device trigger report message is generated according to the device trigger request message and is used to feedback whether the trigger process is Success; The trigger report message sending module is configured to return the trigger report message to the network application end.

15. The server according to claim 14, wherein the device trigger request message sent by the device trigger request message sending module includes a device identification number parameter, a business capability server identification number parameter, a trigger reference number parameter, and a validity period parameter, Priority parameter, any one or more of the application port identification number parameter and the trigger load parameter; wherein the device identification number parameter is used to identify the device to be triggered; the business capability server identification number parameter is used to identify the issuing device trigger The network service capability layer server of the request message; The trigger reference number parameter is the identity number of the device triggering the request message; The validity period parameter is the validity time for the trigger message to expire set by the network application end; The priority parameter is used to identify The priority processing level of the device trigger request message; The application port identification number parameter is used to identify the network application end that initiates the trigger process; The trigger load parameter includes information constructed by the network application end that needs to be passed to the device by the 3GPP network.

16. The server according to claim 14, wherein the device trigger report message received by the device trigger report receiving module includes any one or more of a device identification number parameter, a trigger reference number parameter and a cause parameter; wherein The device identification number parameter is used to identify the device to be triggered; the trigger reference number parameter is the identity number of the device trigger request message; the cause parameter is used to identify whether the trigger process is successful and the reason for failure.

17. The server according to claim 14, characterized in that if the received trigger message does not include the validity period parameter or the application port identification number parameter, it is set by the server itself.

18. The server according to claim 14, characterized in that, after the server sends the device trigger request message to the machine type communication interaction device, the machine type communication interaction device passes the existing A mechanism supported by 3GPP networks to send trigger requests to devices.

19. An M2M communication system, characterized in that the communication system includes the network application end described in claim 10 and the server described in claim 11.