WO2013110224A1

WO2013110224A1 - Method, device, and system for triggering mtc device

Info

Publication number: WO2013110224A1
Application number: PCT/CN2012/074125
Authority: WO
Inventors: 余万涛
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-01-29
Filing date: 2012-04-16
Publication date: 2013-08-01
Also published as: CN103227991A

Abstract

A method, device, and system for triggering a machine type communication (MTC) device. The method comprises: receiving a trigger request message transmitted by an MTC server; determining, on the basis of a preconfigured association relation between the MTC server and the MTC device, that the MTC device for which triggering is requested by the trigger request message is an MTC device associated with the MTC server; and triggering the MTC device to establish a secure connection to the MTC server. The present invention allows the MTC server to trigger only the MTC device that is associated with the MTC server, thus improving the security of communication between the MTC device and the MTC server.

Description

The present invention relates to the field of communications, and in particular to a method, device and system for triggering an MTC device. BACKGROUND OF THE INVENTION Machine Type Communication (referred to as MTC) refers to a series of technologies and combinations thereof that implement wireless communication technology to realize data communication and communication between machines and machines, machines and people. MTC includes two meanings: The first layer is the machine itself, which is called smart device in the embedded field; the second layer is the connection between the machine and the machine, connecting the machines together through the network. Machine-based communication is used in a wide range of applications, such as intelligent measurement, remote monitoring, tracking, medical, etc., to make human life more intelligent. Compared with traditional human-to-human communication, MTC devices have a large number of applications and a wide range of applications, which has great market prospects. In the MTC communication system as shown in FIGS. 1 to 3, the MTC device communicates with the MTC server through a 3GPP network and an MTC Interworking Function (MTC-IWF). For security reasons, when the MTC Server is located outside the 3GPP network, an MTC-Security GateWay (MTC-SGW) can be introduced to authenticate and authorize the MTC Server to ensure the security of the external interface. 4 is a schematic diagram of a connection system of an external interface of a machine type communication system that introduces an MTC security gateway according to the related art. As shown in FIG. 4, when the MTC server is outside the 3GPP network, the MTC security gateway is introduced as an MTC external interface. After (MTC-IWF), the security of the external interface is guaranteed. For many Machine to Machine (M2M) applications, since the MTC user needs to control communication with the MTC device, the MTC device is not allowed to access the MTC server at will. At the same time, due to security needs, a user's MTC server is only allowed to trigger the user's MTC device. However, the attacker may send a trigger command to the MTC device by impersonating the mobile communication network or the MTC server to trigger the MTC device to establish a connection with the MTC server. Therefore, security measures are required to ensure that the MTC device can only respond to trigger commands from a secure MTC server. SUMMARY OF THE INVENTION The present invention provides a method, apparatus, and system for triggering an MTC device to solve the above problems. According to an aspect of the present invention, a method for triggering an MTC device is provided, including: a trigger request message sent by a receiver-type communication MTC server; determining the trigger request message according to a preset relationship between an MTC server and an MTC device. The MTC device requesting the trigger is an MTC device associated with the MTC server; triggering the MTC device to establish a secure connection with the MTC server. Preferably, if the triggering request message requesting the triggered MTC device is not the MTC device associated with the MTC server, the method further comprises: rejecting the trigger request message. Preferably, rejecting the trigger request message comprises: sending a reject message to the MTC server indicating that the triggering of the MTC device is refused. Preferably, the triggering the MTC device to establish a secure connection with the MTC server comprises: sending a triggering instruction message to the MTC device; or forwarding the trigger request message to a predetermined network entity in the mobile communication network, The predetermined network entity sends a trigger instruction message to the MTC device according to the trigger request message. Preferably, after the triggering instruction message is sent to the MTC device, the method further includes: the MTC device receiving the triggering instruction message, and establishing the MTC device and the MTC server in response to the triggering instruction message Communication between the connections. Preferably, the association relationship includes: a correspondence between the MTC server and the MTC device; determining that the MTC device triggered by the trigger request message request is an MTC device associated with the MTC server includes: determining that the MTC server requests triggering Whether the MTC device is an MTC device corresponding to the MTC server, and if so, determining that the MTC device is an MTC device associated with the MTC server. Preferably, the information carried in the trigger request message includes: identity information of the MTC server and/or identity information of the MTC device and/or identity information of the MTC user; the corresponding relationship includes: Corresponding relationship between the identity information of the MTC server and the identity information of the MTC device; determining whether the MTC device requested by the MTC server is an MTC device corresponding to the MTC server includes: determining identity information of the MTC device Whether the identity information of the MTC server has the corresponding relationship; or the corresponding relationship includes: a correspondence between the identity information of the MTC server and the identity information of the MTC user; determining the MTC triggered by the MTC server request Whether the device is the MTC device corresponding to the MTC server includes: determining whether the identity information of the MTC user and the identity information of the MTC server have the corresponding relationship. Preferably, the association relationship includes: an association relationship between the MTC user, the MTC server, and the MTC device; determining that the MTC device triggered by the trigger request message request is an MTC associated with the MTC server The device includes: determining whether the MTC server and the MTC device are associated with the same MTC user, and if yes, determining that the MTC device is an MTC device associated with the MTC server. Preferably, the information carried in the trigger request message includes: identity information of the MTC server and/or identity information of the MTC device and/or identity information of an MTC user; determining the MTC server and the MTC device Whether it is associated with the same MTC user, the method includes: determining whether the identity information of the MTC device and the identity information of the MTC server are associated with the identity information of the same MTC user. Preferably, the identity information of the MTC device includes: an international mobile equipment identifier IMEI; the identity information of the MTC user includes: an international subscriber identity IMSI; and the identity information of the MTC server includes: the identity of the MTC server Logo. According to another aspect of the present invention, a triggering apparatus for an MTC device is provided, including: a receiving module, configured to be a trigger request message sent by a receiver-type communication (MTC) server; and a determining module configured to be according to a preset MTC server The MTC device that is triggered by the trigger request message request is an MTC device that is associated with the MTC server; and the triggering module is configured to trigger the MTC device to establish a secure connection with the MTC server. Preferably, the triggering module is configured to send a triggering instruction message to the MTC device, or forward the triggering request message to a predetermined network entity in the mobile communication network, and send, by the predetermined network entity, a triggering instruction to the MTC device. Message. Preferably, the association relationship includes: a correspondence between the MTC server and the MTC device; the determining module is configured to determine whether the MTC device requested by the MTC server is an MTC device corresponding to the MTC server, and if yes, Determining that the MTC device is an MTC device associated with the MTC server. Preferably, the association relationship includes: an association relationship between the MTC user, the MTC server, and the MTC device; the determining module is configured to determine the MTC server according to an association relationship between the MTC user, the MTC server, and the MTC device. Whether the MTC device is associated with the same MTC user, and if so, determining that the MTC device is an MTC device associated with the MTC server. According to still another aspect of the present invention, a triggering system for an MTC device is provided, including: an MTC server, configured to send a trigger request message to an MTC external interface function entity MTC-IWF; the MTC external interface function entity, including the foregoing The triggering device of the MTC device is configured to be a trigger request message sent by the MTC server of the receiver, and determined according to a preset relationship between the MTC server and the MTC device. The MTC device is an MTC device associated with the MTC server, and triggers the MTC device to establish a secure connection with the MTC server. Preferably, the MTC external interface function entity is further configured to: reject the trigger request message if the triggering request message requesting that the triggered MTC device is not the MTC device associated with the MTC server. With the present invention, the MTC external interface function entity sends a trigger instruction message to the MTC device, or forwards the trigger request to other network entities in the mobile communication network, when determining that the MTC device to be triggered by the request is an MTC device associated with the MTC server. And sending, by the network entity, the triggering instruction information to the MTC device, triggering the MTC device to establish a connection with the MTC server, and realizing that only the MTC server associated with the MTC device can trigger the MTC device to establish a connection with the MTC server, thereby improving the MTC. The security of the device communicating with the MTC server. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a machine type communication system architecture according to the related art; FIG. 2 is a schematic diagram of a machine type communication system architecture for a scenario of a home network route when an MTC device roams according to the related art; FIG. 4 is a schematic diagram of a connection system of an external interface of a machine type communication system that introduces an MTC security gateway according to the related art; FIG. 5 is a schematic diagram of a connection system of an external interface of a machine type communication system that introduces an MTC security gateway according to the related art; FIG. FIG. 6 is a schematic diagram of a triggering system of an MTC device according to a first preferred embodiment of the present invention; FIG. 7 is a triggering system of an MTC device according to a preferred mode 2 of the embodiment of the present invention; Figure 8 is a block diagram showing the structure of a triggering device of an MTC device according to an embodiment of the present invention; 9 is a flowchart of a method for triggering an MTC device according to an embodiment of the present invention; FIG. 10 is a flowchart of a method for triggering an MTC device according to Embodiment 1 of the present invention; FIG. 11 is a trigger of an MTC device according to Embodiment 2 of the present invention; Flowchart of the method; Figure 12 is a flow chart of a method of triggering an MTC device in accordance with an implementation of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. For the related art, how to securely trigger the MTC device to establish a secure connection between the MTC device and the MTC server, the embodiment of the present invention provides a triggering method, device, and system for the MTC device, and implements the security of the MTC device. The triggering, the MTC device can only be triggered by the MTC server associated with the MTC device. Preferably, the MTC server associated with the MTC device can be an MTC server belonging to the same MTC user as the MTC device, thereby implementing an MTC server of the MTC user only The MTC device that triggers the MTC user can improve the security of the MTC service. In the embodiment of the present invention, the MTC device refers to a device for machine-to-machine communication in a mobile communication network, and a mobile communication user identification card (UICC) is installed on the MTC device, and the user identification module (such as a customer identification module (Subscriber Identity) Module, referred to as SIM), USIM, ISIM, etc.) is located on the UICC. According to an embodiment of the present invention, a triggering system for an MTC device is provided. In the system, the MTC external interface function entity determines whether the MTC device requested to be triggered is an MTC device associated with the MTC server, and if yes, sends the MTC device to the MTC device. The instruction message is triggered, or the trigger request is forwarded to other network entities in the mobile communication network, and the triggering information is sent by the network entity to the MTC device. After receiving the trigger command message, the MTC device establishes a secure connection with the MTC server; if not, the MTC external interface function entity rejects the trigger request message, and implements an MTC server that can only trigger the MTC device associated with the MTC server, thereby improving the MTC. Business security. FIG. 5 is a schematic diagram of a triggering system of an MTC device according to an embodiment of the present invention. As shown in FIG. 5, the system may include: an MTC server 10 and an MTC external interface function entity 20. The MTC server 10 is configured to send a trigger request message to the MTC external interface function entity 20, and the MTC external interface function entity 20 is configured to send a trigger request message sent by the receiver MTC server 10 according to the preset MTC server and the MTC device. Correlation relationship, determining that the MTC device is an MTC device associated with the MTC server 10, and The trigger instruction message is sent to the MTC device, or the trigger request is forwarded to other network entities in the mobile communication network, and the trigger information is sent by the network entity to the MTC device. The other network entities in the foregoing mobile communication network include, but are not limited to, a short message center (SMS-SC/IP-SM-GW), an SGSN (GPRS Service Support Node), and an MME (Mobility Management Entity). In this embodiment, the association relationship between the MTC server and the MTC device may be established according to a predetermined rule. For example, the MTC device belonging to the same MTC user may be associated with the MTC server, or even the MTC device that is not the same MTC user. And the MTC server, as long as the MTC server is allowed to establish a connection with the MTC device, the association relationship between the MTC server and the MTC device can be established. According to the embodiment of the present invention, the MTC external interface function entity determines that the MTC device that is requested to be triggered is an MTC device associated with the MTC server, and sends a trigger instruction message to the MTC device, or forwards the trigger request to other network entities in the mobile communication network. The triggering information is sent by the network entity to the MTC device, and the MTC device is triggered to establish a connection with the MTC server, so that the MTC server only triggers the MTC device associated with the MTC server, thereby improving the security of communication between the MTC device and the MTC server. In a preferred embodiment of the present invention, the association relationship may be an association relationship between the MTC device, the MTC server, and the MTC user, and the MTC external interface function entity 20 receives the trigger request sent by the MTC server 10. When the message is received, it may be determined whether the MTC device triggered by the request and the MTC server are associated with the same MTC user, and if yes, sending a trigger instruction message to the MTC device, or forwarding the trigger request to other network entities in the mobile communication network, and These network entities send trigger instruction information to the MTC device. After receiving the trigger instruction message, the MTC device establishes a secure connection with the MTC server; if not, the MTC external interface function entity rejects the trigger request. In the foregoing preferred embodiment, the MTC device, the MTC device belonging to the MTC user, and the MTC server may be associated with each other in the association relationship between the MTC device, the MTC server, and the MTC user, so that an MTC user can be implemented. The MTC server can only trigger the MTC device of the MTC user, which further improves the security of the MTC service. With the above preferred embodiment of the present invention, the MTC external interface function entity determines that the MTC device requesting the trigger belongs to the same MTC user as the MTC server, and sends a trigger instruction message to the MTC device, or forwards the trigger request to other network entities in the mobile communication network. And the network entity sends the triggering instruction information to the MTC device, triggering the MTC device to establish a connection with the MTC server, and realizing that the MTC server only triggers the MTC device belonging to the same MTC user, thereby improving the security of communication between the MTC device and the MTC server. In a preferred embodiment of the embodiment of the present invention, the MTC external interface function entity 20 is further configured to reject the trigger request if the MTC device triggered by the trigger request message request is not the MTC device associated with the MTC server 10. Preferably, the MTC external interface function entity 20 may send a reject message to the MTC server indicating that the triggering of the MTC device is refused. With the preferred embodiment, the MTC device that is not associated with the MTC server is rejected, so that the MTC server only triggers the MTC device associated with the MTC server, which improves the security of the MTC system. In a preferred embodiment of the present invention, the MTC external interface function entity 20 is further configured to reject the trigger request if the MTC device triggered by the trigger request message request and the MTC server 10 do not belong to the same MTC user. Preferably, the MTC external interface function entity 20 may send a reject message indicating that the refusal to trigger the MTC device is sent to the MTC server. With the preferred embodiment, the MTC device that does not belong to the same MTC user as the MTC server is rejected, so that the MTC server only triggers the MTC device belonging to the same MTC user, which improves the security of the MTC system. In a preferred embodiment of the present invention, the foregoing relationship may be recorded by using the identity information of the MTC device, the identity information of the MTC server, and the identity information of the MTC user (in the case of including the MTC user) to record the MTC device and the MTC server. And the association of MTC users (in the case of MTC users). The identity information of the MTC device includes but is not limited to: an International Mobile Equipment Identity (IMEI) or other identity information used to identify the MTC device. The identity information of the MTC user includes but is not limited to: an International Subscriber Identity (IMSI) of the MTC user or other identity information used to identify the MTC user. Identity information of the MTC server include but are not limited to: the identity (MTC_Serv _er _ID) the MTC server or other server identification information for identifying the MTC. In an actual application, the MTC external interface function entity 20 may be an independent MTC security gateway, or may include an MTC security gateway and an MTC external interface function entity including an MTC security gateway function. The MTC external interface function entity that includes the MTC security gateway function is also an MTC security gateway in terms of functions and implementation. The above preferred embodiments are described below separately. In the first mode, the MTC external interface function entity 20 is a separate MTC security gateway, and the MTC security gateway is located between the mobile network and the MTC server. 6 is a schematic diagram of a trigger system of an MTC device according to a first preferred embodiment of the present invention, showing an external connection system architecture that triggers an MTC device. As shown in FIG. 6, the system may include: an MTC external interface function entity, an MTC server, a gateway GPRS support node (GGSN) / a packet data gateway (PGW), a local location register (HLR) / a local subscription data server (HSS), And a short message center (SMS-SC/IP-SM-GW) and a P SGSN (GPRS Service Support Node) / MME (Mobility Management Entity, Mobile Management Entity). The MTC external interface function entity, the MTC external interface function entity is an independent MTC security gateway, implements an external interface function, authenticates and authorizes the MTC server, ensures the security of the external interface communication, and can be used to shield the mobile communication system. Network topology, relay or processing signaling protocols. MTC server, used to provide MTC related services or services. In the system shown in FIG. 6, the MTC external interface is implemented by an independent MTC security gateway, and the MTC security gateway communicates with the short message center (SMS-SC/IP-SM-GW) through the T4 and MTCsms interfaces, that is, MTC security. The gateway supports both T4 and MTCsms communication protocols. At the same time, the MTC security gateway supports the triggering of the MTC device, that is, the MTC server only triggers the MTC device associated with it, or the MTC server only triggers the MTC device that belongs to the same MTC user. Mode 2 FIG. 7 is a schematic diagram of a trigger system of an MTC device according to a preferred mode 2 of the embodiment of the present invention, showing an external connection system architecture that triggers the MTC device. As shown in FIG. 7, the system includes: an MTC external interface function entity, an MTC server, a GGSN/PGW, an SGSN/MME, and an SMS-SC/IP-SM-GW. The MTC external interface function entity is composed of an MTC security gateway entity and an external interface entity including an MTC security gateway function, implements an external interface function, performs authentication and authorization on the MTC server, ensures security of external interface communication, and is used for shielding. The network topology of the mobile communication system, relaying or processing signaling protocols. MTC server, used to provide MTC related services or services. In the system architecture shown in Figure 7, the MTC external interface is implemented by the MTC security gateway and an external interface entity that includes the MTC security gateway function. The MTC security gateway communicates with the short message center through the MTCsms interface. The external interface entity including the MTC security gateway functions to communicate with the short message center through the T4 interface. The support for the T4 and MTCsms interfaces can be set according to actual conditions. At the same time, the MTC security gateway or the external interface entity that includes the MTC security gateway function supports the triggering of the MTC device, that is, the MTC server only triggers the MTC device associated with it, or the MTC server only triggers the MTC device that belongs to the same MTC user. The following description is made by way of specific embodiments. Embodiment 1 According to the embodiment of the present invention, a triggering system for an MTC device is provided for the MTC device and the mobile communication network to be triggered by the MTC device. The system includes:

The MTC device is a device used by the user for machine type communication, and the UICC card is installed in the MTC device. The mobile communication network is configured to send a trigger instruction to the MTC device, and the mobile communication network may include a 3GPP network and a 3GPP2 network. Specifically, the mobile communication network may include: GGSN/PGW (Gateway GPRS Support Node/Packet Data Gateway), HLR/HSS (Local Location Register/Local Subscription Data Server), SGSN/MME (GPRS Service Support Node/Mobile Management Entity) And the short message center (the SMS-SC/IP-SM-GW MTC external interface function entity, the MTC external interface function entity can be an independent MTC security gateway, implement the external interface function, authenticate and authorize the MTC server, guarantee the external The security of the interface communication can be used to shield the network topology of the mobile communication system, relay or process the signaling protocol. The MTC external interface function entity can also be composed of the MTC security gateway entity and an external interface entity (MTC) that includes the MTC security gateway function. -IWF (MTC Security Gateway)), implements external interface functions, authenticates and authorizes the MTC server, ensures the security of external interface communication, and can be used to shield the network topology of the mobile communication system, relay or process signaling protocols. .

The MTC server, the MTC server initiates a trigger request or instruction and provides an M2M service for the MTC user. In the embodiment of the present invention, the MTC device and the MTC server may belong to the same MTC user. In the embodiment of the present invention, when the MTC server of the MTC user communicates with an MTC device of the MTC user, the MTC device may be activated to establish a secure connection with the MTC server by triggering a request or an instruction. When the MTC server of the MTC user needs to receive information from an MTC device of the MTC user, the MTC server sends a trigger request or a trigger command to the MTC external interface function entity, and the MTC external interface function entity triggers according to the trigger request or the trigger instruction of the MTC server. A secure connection is established between the MTC device and the MTC server. To implement the MTC server of a user, only the MTC device of the user is triggered, and the MTC external interface function entity of the local network can save and manage the association information of the MTC user with the MTC device and the MTC server in the local network. Specifically, the association relationship between the MTC user identity information and the MTC device identity information and the MTC server identity information may be saved and maintained in the MTC external interface function entity, for example, the MTC user identity information IMSI and the MTC device identity information IMEI and the MTC server. form of identity MTC_Serv _er _ID relationship list associated with preservation, management and maintenance. In the embodiment of the present invention, the MTC device and the MTC server may also have some association relationship. In this case, in the embodiment of the present invention, when communicating with an MTC device, an MTC server may activate a corresponding MTC device to establish a secure connection with the MTC server by sending a trigger request or an instruction. When the MTC server needs to receive information from an MTC device, the MTC server sends a trigger request or a trigger command to the MTC external interface function entity, and the MTC external interface function entity triggers the trigger between the MTC device and the MTC server according to the trigger request or the trigger instruction of the MTC server. Establish a secure connection. In the embodiment of the present invention, the identity information related to the MTC device includes: identity information of the MTC device and identity information of the MTC device subscription user (ie, the MTC user). The MTC device signing user identity information is the MTC user identity information IMSI or other identity information used to identify the MTC user. In the embodiment of the present invention, the association relationship between the MTC device and the MTC server may be an association relationship between the identity information related to the MTC device and the MTC server identity information. Specifically, it can be a relationship subscriber identity MTC device IMSI information of the MTC server identity information MTC_Serv _er _ID can also be associated with the relationship between the MTC device identity IMEI and the MTC server identity information MTC_Serv _er _ID can also be MTC device other information related to the identity relationship with the MTC server identity information MTC_Serv _er _ID of. To implement an MTC server that only triggers the MTC device associated with the MTC server, the MTC external interface function entity of the local network can save and manage the association relationship between the MTC device and the MTC server in the local network. Specifically, the MTC-IWF entity, save manage and maintain relationships MTC device-related identity information with the MTC server identity information, such as related to subscriber identity MTC device IMSI information of the MTC server identity information MTC_Serv _er _ID of in the form of a list of relationship save, manage and maintain, or device identity information to MTC MTC server and IMEI identity information MTC_Serv _er in the form of a list of associated relations _ID preservation, management and maintenance. Preferably, the directed MTC device and associated relationships MTC server may be an MTC user identity information international subscriber identity another ¹ J code (International Mobile Subscriber Identification Number, abbreviated as IMSI) with the MTC device identity information of the International Mobile Equipment Identity (International The association relationship of the Mobile Equipment Identity (IMEI) is that the MTC device corresponding to the IMEI is a legal MTC device corresponding to the MTC user identity information IMSI. The association relationship may also be an association relationship between the MTC user identity information IMSI and the MTC server identity information MTC_Server_ID, and the MTC server corresponding to the MTC_Server_ID is a legal MTC server corresponding to the MTC user identity information IMSI. Further, the association relationship may be an association between the MTC user identity information IMSI and the MTC server identity information MTC_Server_ID and the MTC device identity information IMEI, and the MTC server corresponding to the MTC_Server_ID and the MTC device corresponding to the IMEI belong to the MTC user whose identity information is the IMSI. . When the MTC server needs to trigger the MTC device to communicate, the MTC server sends a trigger request or trigger command to the MTC external interface function entity of the local network. Related identity information and request instructions MTC_Serv _er _ID triggering request message or trigger comprises a trigger MTC MTC server equipment identity information, such as the IMEI and IMSI. After receiving the trigger request or the trigger instruction message, the MTC external interface function entity of the local network determines whether the trigger process needs to be performed. Specifically, the MTC external interface function entity of the local network determines, according to the association relationship between the stored MTC device and the MTC server, identity information related to the MTC device to be triggered, such as IMEI and MTC server identity information MTC_Server_ID, or IMSI and MTC server identity. Information MTC_Server_ID, whether there is an association relationship. If the MTC server is associated with the MTC device, the MTC external interface function entity of the local network sends the triggering command to the MTC device via the mobile communication network, or forwards the trigger request to other network entities in the mobile communication network, such as a short message center. (SMS-SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities send trigger instruction information to the MTC device. After receiving the trigger command, the MTC device starts and establishes a secure connection with the MTC server. If the MTC server does not have an association relationship with the MTC device, the MTC external interface function entity of the local network rejects the trigger request or the trigger instruction of the MTC server. Preferably, a reject message indicating that the refusal to trigger the MTC device may be sent to the MTC server. After receiving the trigger request or the trigger instruction message, the MTC external interface function entity of the local network determines whether the trigger process needs to be performed. Specifically, the MTC external interface function entity of the local network determines, according to the association relationship between the stored MTC user and the MTC device and the MTC server, whether the MTC device identity information IMEI and the MTC server identity information MTC_Server_ID to be triggered belong to the same MTC user. . If the MTC server and the MTC device belong to the same MTC user, the MTC external interface function entity of the local network sends a trigger command to the MTC device via the mobile communication network, or forwards the trigger request to other network entities in the mobile communication network, such as a short message. Center (SMS-SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities send trigger instruction information to the MTC device. After receiving the trigger command, the MTC device starts and establishes a secure connection with the MTC server. If the MTC server and the MTC device do not belong to the same MTC user, the MTC external interface function entity of the local network rejects the trigger request or trigger instruction of the MTC server. Preferably, a reject message indicating that the refusal to trigger the MTC device may be sent to the MTC server. According to the embodiment of the present invention, a triggering device for the MTC device is provided, and the MTC external interface function entity 20 provided in the embodiment of the present invention can implement the foregoing functions described in the embodiments of the present invention. FIG. 8 is a structural block diagram of a triggering apparatus of an MTC device according to an embodiment of the present invention. As shown in FIG. 8, the device may include: a receiving module 202, a determining module 204, and a sending module 206. The receiving module 202 is configured to be a trigger request message sent by a receiver-type communication (MTC) server. The determining module 204 is coupled to the receiving module 202, and is configured to determine a trigger according to a preset relationship between the MTC server and the MTC device. The MTC device triggered by the request message request is an MTC device associated with the MTC server that sends the trigger request message; the trigger module 206 is coupled to the determining module 204, and is configured to trigger the MTC device to establish a secure connection with the MTC server. Preferably, the triggering module 206 may send a triggering instruction message to the MTC device, or forward the triggering request to other network entities in the mobile communication network, such as a short message center (SMS-SC/IP-SM-GW) or an SGSN ( GPRS service support node) / MME (Mobility Management Entity), and these network entities send trigger instruction information to the MTC device. According to the embodiment of the present invention, the MTC external interface function entity determines that the MTC device that is requested to be triggered is an MTC device that is associated with the MTC server, and sends a trigger request message to the MTC device, triggering the MTC device to establish a connection with the MTC server, and the MTC server only triggers. The MTC device associated with the MTC server improves the security of communication between the MTC device and the MTC server. In a preferred embodiment of the embodiment of the present invention, if the determining module 204 determines that the MTC device triggered by the trigger request message request is not the MTC device associated with the MTC server 10, the sending module 206 rejects the trigger request message. Preferably, a reject message indicating that the refusal to trigger the MTC device may be sent to the MTC server. With the preferred embodiment, the MTC device that is not associated with the MTC server is rejected, so that the MTC server only triggers the MTC device associated with the MTC server, which improves the security of the external interface of the MTC system. In a preferred embodiment of the present invention, the association relationship includes: a correspondence between the MTC server and the MTC device; the determining module 204 is configured to determine whether the MTC device requested by the MTC server is an MTC device corresponding to the MTC server, if Yes, it is determined that the MTC device is an MTC device associated with the MTC server. In another preferred embodiment of the present invention, the foregoing relationship includes: an association relationship between the MTC user, the MTC server, and the MTC device. The determining module 204 is further configured to determine, according to the association relationship between the MTC user, the MTC server, and the MTC device, whether the MTC server and the MTC device are associated with the same MTC user, and if yes, determine the MTC device and the MTC that sends the trigger request message. The MTC device associated with the server. Preferably, the foregoing relationship may record an association relationship between the MTC user and the MTC server and the MTC device belonging to the MTC user. According to the preferred embodiment, according to the association relationship between the MTC user, the MTC server, and the MTC device, The MTC server and the MTC device belong to the same MTC user, and the trigger module 206 sends a trigger instruction message to the MTC device, or forwards the trigger request to the mobile communication. Other network entities in the network, such as Short Message Center (SMS-SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities to the MTC devices The triggering instruction information is sent, and the MTC server that belongs to the same MTC user only triggers the MTC device of the MTC user, which avoids the problem that the MTC server triggers the MTC device of other MTC users, and enhances the security of the MTC system. In the above preferred embodiment of the embodiment of the present invention, if the determining module 204 determines that the MTC device triggered by the trigger request message request and the MTC server 10 do not belong to the same MTC user, the trigger module 206 rejects the trigger request message. Preferably, a reject message indicating that the refusal to trigger the MTC device may be sent to the MTC server. With the preferred embodiment, the MTC device that does not belong to the same MTC user as the MTC server is rejected, so that the MTC server only triggers the MTC device that belongs to the same MTC user, which improves the security of the external interface of the MTC system. According to an embodiment of the present invention, a triggering method for an MTC device is provided corresponding to the foregoing system and apparatus provided by the embodiments of the present invention. FIG. 9 is a flowchart of a method for triggering an MTC device according to an embodiment of the present invention. As shown in FIG. 9, the method may include the following steps (step S902 to step S906): Step S902, MTC external interface function entity receiver class communication (MTC) The trigger request message sent by the server. Step S904: Determine, according to the association relationship between the preset MTC server and the MTC device, that the MTC device triggered by the trigger request message request is an MTC device associated with the MTC server that sends the trigger request message. Step S906, triggering the MTC device to establish a secure connection with the MTC server, for example, sending a trigger instruction message to the MTC device triggered by the trigger request message request, or forwarding the trigger request to other network entities in the mobile communication network, such as a short message center ( SMS-SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities send trigger instruction information to the MTC device. According to the embodiment of the present invention, the MTC external interface function entity determines that the MTC device that is requested to be triggered is an MTC device associated with the MTC server, and sends a trigger instruction message to the MTC device, or forwards the trigger request to other network entities in the mobile communication network. Such as a short message center (SMS-SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities send trigger instruction information to the MTC device, triggering MTC The device establishes a connection with the MTC server. The MTC server only triggers the MTC device associated with the MTC server, which improves the security of communication between the MTC device and the MTC server. In a preferred embodiment of the embodiment of the present invention, if the MTC device triggered by the trigger request message request is not the MTC device associated with the MTC server that sends the trigger request message, the trigger request message is rejected. Preferably, a reject message indicating that the refusal to trigger the MTC device may be sent to the MTC server. With the preferred embodiment, the MTC device that is not associated with the MTC server can be rejected, so that the MTC server only triggers the MTC device associated with the MTC server, which improves the security of the external interface of the MTC system. In another preferred embodiment of the present invention, the association relationship may record a correspondence between an MTC device to which an MTC server can establish a connection, or may associate an MTC server and an MTC device with an MTC user, that is, The association relationship between the MTC user, the MTC server, and the MTC device is established, and the association relationship is preset in the MTC external interface entity. In order to determine whether the MTC device triggered by the trigger request message request and the MTC server that sends the trigger request message belong to the same MTC user, it may be determined whether there is an association relationship between the MTC server, the MTC device, and the MTC user, and if yes, determine that the MTC device is The MTC server that sends the trigger request message belongs to the same MTC user, and sends a trigger instruction message to the MTC device, or forwards the trigger request to other network entities in the mobile communication network, such as a short message center (SMS-SC/IP-SM-GW) Or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities send trigger instruction information to the MTC device, triggering the MTC device to establish a connection with the MTC server. With the preferred embodiment, the MTC user, the MTC device, and the MTC server are associated, and the MTC server of the MTC user only triggers the MTC device of the MTC user, thereby improving the security of the external interface of the MTC system. In the above preferred embodiment of the embodiment of the present invention, if the MTC device triggered by the trigger request message request and the MTC server that sends the trigger request message do not belong to the same MTC user, the trigger request message is rejected. Preferably, a reject message indicating that the refusal to trigger the MTC device may be sent to the MTC server. With the preferred embodiment, the MTC device that does not belong to the same MTC user as the MTC server can be refused, so that the MTC server only triggers the MTC device belonging to the MTC user, which improves the security of the external interface of the MTC system. In the above preferred embodiment, when the information carried in the trigger request message carries the identity information of the MTC server and the identity information of the MTC device, the MTC server and the MTC server can be determined by determining whether the MTC device and the MTC server are associated with the same MTC user. Whether the MTC device belongs to the same MTC user. Preferably, the identity information of the MTC device may be an IMEI of the MTC device, and the identity information of the MTC user may be an IMSI. In the embodiment of the present invention, after the MTC device receives the trigger instruction message, the MTC device responds to the trigger instruction message, and establishes a communication connection between the MTC device and the MTC server. The following description is made by way of specific embodiments. The second embodiment corresponds to the system shown in FIG. 6. According to the embodiment of the present invention, a triggering method for the MTC device is provided, and in the system shown in FIG. 6, the trigger for limiting the MTC device can be implemented. 10 is a flowchart of a method for triggering an MTC device according to Embodiment 2 of the present invention. As shown in FIG. 10, the method may include the following steps (Step S1002 - Step S1008): Step S1002, the MTC server needs to trigger an MTC device. when communicating, the MTC server will trigger request, or triggering instruction information to the MTC-IWF entity in the local network, triggering request or trigger identity information instruction message includes MTC server (MTC_Serv _er _ID) and MTC device associated identity information (such as IMSI and IMEI). Step S1004: After receiving the trigger request or the trigger instruction message, the MTC external interface function entity in the local network determines whether the trigger process needs to be performed. Specifically, the MTC external interface function entity in the local network determines whether the MTC device and the MTC server to be triggered belong to the same MTC user according to the association relationship between the saved MTC user and the MTC device and the MTC server. Step S1006: If the MTC server and the MTC device belong to the same MTC user, the MTC external interface function entity in the local network sends a trigger command to the MTC device through the mobile communication network, or forwards the trigger request to other network entities in the mobile communication network. , such as a short message center (SMS-SC/IP-SM-GW) or an SGSN (GPRS Service Support Node) / MME (Mobility Management Entity, mobile management entity), and the triggering information is sent to the MTC device by these network entities, Go to step S1008. If the MTC server and the MTC device do not belong to the same MTC user, the MTC external interface function entity rejects the trigger request and ends the triggering process. Step S1008: After receiving the triggering instruction, the MTC device starts and establishes a secure connection with the MTC server. The third embodiment corresponds to the system shown in FIG. 7. According to the embodiment of the present invention, a triggering method for the MTC device is provided. In the system shown in FIG. 7, the trigger for limiting the MTC device can be implemented. 11 is a flowchart of a method for triggering an MTC device according to Embodiment 3 of the present invention. As shown in FIG. 11, the method may include the following steps (Step S1102 - Step S1108): Step S1102: The MTC server needs to trigger an MTC device to perform communication, MTC server triggers a request or trigger transmission instruction information to the MTC security gateway local network, triggering request or trigger identity information (MTC_Ser _Ver _ID) instruction message comprising MTC server and MTC related identity information apparatus (e.g., IMSI and IMEI). Step S1104: After receiving the trigger request or the trigger instruction message, the MTC security gateway in the local network determines whether the trigger process needs to be performed. Specifically, the MTC security gateway in the local network determines whether the MTC device and the MTC server to be triggered belong to the same MTC user according to the association relationship between the saved MTC user and the MTC device and the MTC server. Step S1106: If the MTC server and the MTC device belong to the same MTC user, the MTC security gateway in the local network sends a trigger command to the MTC device through the mobile communication network, or forwards the trigger request to other network entities in the mobile communication network, such as Short message center (SMS-SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities send trigger command information to the MTC device. S1208. If the MTC server and the MTC device do not belong to the same MTC user, the MTC security gateway rejects the trigger request and ends the triggering process. Step S1108: After receiving the triggering instruction, the MTC device starts and establishes a secure connection with the MTC server. The fourth embodiment corresponds to the system shown in FIG. 7. According to the embodiment of the present invention, a triggering method for the MTC device is provided. In the system shown in FIG. 7, the trigger for limiting the roaming MTC device can be implemented. 12 is a flowchart of a method for triggering an MTC device according to Embodiment 4 of the present invention. As shown in FIG. 12, the method may include the following steps (Step S1202 - Step S1208): Step S1202, the MTC server needs to trigger an MTC device to perform communication, MTC server will trigger request, or triggering instruction information to the external interface entity comprises MTC security gateway function of the local network, triggering request or trigger identity MTC_Serv _er _ID instruction message includes MTC server and the MTC device associated identity Information such as IMSI and IMEI. Step S1204: After receiving the trigger request or the trigger instruction message, the external interface entity that includes the MTC security gateway function in the local network determines whether the trigger process needs to be performed. Specifically, the MTC is included in the local network. The external interface entity of the security gateway function determines whether the MTC device and the MTC server to be triggered belong to the same MTC user according to the association relationship between the saved MTC user and the MTC device and the MTC server. Step S1206: If the MTC server and the MTC device belong to the same MTC user, the external interface entity in the local network that includes the MTC security gateway function sends a trigger command to the MTC device through the mobile communication network, or forwards the trigger request to the mobile communication network. Other network entities, such as Short Message Center (SMS-SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities will trigger the triggering of command information. To the MTC device, proceed to step S1208; if the MTC server and the MTC device do not belong to the same MTC user, the external interface entity including the MTC security gateway function rejects the trigger request and ends the triggering process. Step S1208: After receiving the triggering instruction, the MTC device starts and establishes a secure connection with the MTC server. From the above description, it can be seen that the present invention achieves the following technical effects:

The MTC external interface function entity determines that the MTC device that is requested to be triggered is an MTC device associated with the MTC server, and sends a trigger instruction message to the MTC device, or forwards the trigger request to other network entities in the mobile communication network, such as a short message center (SMS) -SC/IP-SM-GW) or SGSN (GPRS Service Support Node) / MME (Mobility Management Entity), and these network entities send trigger instruction information to the MTC device, triggering the MTC device to establish a connection with the MTC server. Implementing the MTC server only triggers the MTC device associated with the MTC server. Further, the MTC user, the MTC server, and the MTC device may be associated with each other. The MTC external interface function entity determines whether the MTC server and the MTC device are associated with the same MTC user. If yes, it is determined that the MTC device and the MTC server belong to the same MTC. The user sends a trigger command message to the MTC device, or forwards the trigger request to other network entities in the mobile communication network, such as a short message center (SMS-SC/IP-SM-GW) or SGSN (GPRS service support node) / The MME (Mobility Management Entity) sends the triggering instruction information to the MTC device, and triggers the MTC device to establish a connection with the MTC server. The MTC server of the MTC user can only trigger the MTC device of the MTC user. Improves the security of communication between the MTC device and the MTC server. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or separate them into individual integrated circuit modules, or Multiple of these modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. A method for triggering an MTC device, comprising:

Receiver class communication trigger request message sent by the MTC server;

Determining, according to a preset relationship between the MTC server and the MTC device, the MTC device triggered by the trigger request message request is an MTC device associated with the MTC server;

Triggering the MTC device to establish a secure connection with the MTC server.

2. The method according to claim 1, wherein, if the trigger request message requests the triggered MTC device to be not the MTC device associated with the MTC server, the method further includes:

The trigger request message is rejected.

The method according to claim 2, wherein the rejecting the trigger request message comprises: sending a reject message to the MTC server indicating that the triggering of the MTC device is refused.

4. The method according to claim 1, wherein the triggering the MTC device to establish a secure connection with the MTC server comprises:

Sending a trigger instruction message to the MTC device; or

The trigger request message is forwarded to a predetermined network entity in the mobile communication network, and the predetermined network entity sends a trigger instruction message to the MTC device according to the trigger request message.

The method according to claim 4, wherein, after the sending the trigger instruction message to the MTC device, the method further includes:

The MTC device receives the trigger instruction message, and in response to the trigger instruction message, establishes a communication connection between the MTC device and the MTC server.

The method according to any one of claims 1 to 5, wherein

The association relationship includes: a correspondence between an MTC server and an MTC device;

Determining that the MTC device that is triggered by the trigger request message request is an MTC device that is associated with the MTC server, including: determining whether the MTC device requested by the MTC server is an MTC device corresponding to the MTC server, and if yes, Determining that the MTC device is an MTC device associated with the MTC server.

7. The method according to claim 6, wherein

The information carried in the trigger request message includes: identity information of the MTC server and/or identity information of the MTC device and/or identity information of the MTC user;

The corresponding relationship includes: a correspondence between the identity information of the MTC server and the identity information of the MTC device; determining whether the MTC device requested by the MTC server is an MTC device corresponding to the MTC server, includes: determining Whether the identity information of the MTC device and the identity information of the MTC server have the corresponding relationship; or

The corresponding relationship includes: a correspondence between the identity information of the MTC server and the identity information of the MTC user; determining whether the MTC device requested by the MTC server is an MTC device corresponding to the MTC server, includes: determining Whether the identity information of the MTC user and the identity information of the MTC server have the corresponding relationship.

The method according to any one of claims 1 to 5, wherein

The association relationship includes: an association relationship between the MTC user, the MTC server, and the MTC device; determining that the MTC device triggered by the trigger request message request is an MTC device associated with the MTC server, includes: determining the MTC server Whether the MTC device is associated with the same MTC user, and if so, determining that the MTC device is an MTC device associated with the MTC server.

9. The method according to claim 8, wherein

And determining whether the MTC server and the MTC device are associated with the same MTC user, and determining whether the identity information of the MTC device and the identity information of the MTC server are associated with the identity information of the same MTC user.

10. The method according to claim 9, wherein the identity information of the MTC device comprises: an international mobile equipment identification code IMEI; the identity information of the MTC user comprises: an international user identification code IMSI; The identity information includes: an identity of the MTC server.

11. A trigger device for an MTC device, comprising:

a receiving module, configured to be a trigger request message sent by the receiver class communication MTC server; a determining module, configured to determine, according to a preset association relationship between the MTC server and the MTC device, that the MTC device triggered by the trigger request message request is an MTC device associated with the MTC server;

The triggering module is configured to trigger the MTC device to establish a secure connection with the MTC server.

12. The apparatus according to claim 11, wherein the triggering module is configured to send a triggering instruction message to the MTC device, or forward the triggering request message to a predetermined network entity in a mobile communication network, by the predetermined The network entity sends a trigger instruction message to the MTC device.

The device according to claim 11 or 12, wherein the association relationship comprises: a correspondence between an MTC server and an MTC device; the determining module is configured to determine whether the MTC device requested by the MTC server is a device The MTC device corresponding to the MTC server, if yes, determining that the MTC device is an MTC device associated with the MTC server.

The device according to claim 11 or 12, wherein the association relationship includes: an association relationship between an MTC user, an MTC server, and an MTC device; the determining module is configured to be based on an MTC user, an MTC server, and an MTC. The association relationship between the three devices determines whether the MTC server and the MTC device are associated with the same MTC user, and if yes, determines that the MTC device is an MTC device associated with the MTC server.

15. A trigger system for an MTC device, comprising:

The machine type communication MTC server is configured to send a trigger request message to the MTC external interface function entity MTC-IWF;

The MTC external interface function entity, comprising the device according to any one of claims 10 to 13, configured to receive a trigger request message sent by the MTC server of the receiver, according to a preset relationship between the MTC server and the MTC device. Determining that the MTC device is an MTC device associated with the MTC server, and triggering the MTC device to establish a secure connection with the MTC server.

The system according to claim 15, wherein the MTC external interface function entity is further configured to: if the trigger request message requesting the triggered MTC device is not the MTC device associated with the MTC server, The trigger request message is rejected.