CN102238617B - Machine-type communication event report method and system - Google Patents

Abstract

The invention discloses a kind of machine-type communication event report method and system.Wherein, this machine-type communication event report method comprises: the address obtaining the MTC server corresponding with this MTC device according to the identification information of MTC device; The MTC event report of this MTC device is sent to above-mentioned MTC server.By the present invention, MTC event report can be ensured to be sent to correct MTC server.

Description

Machine type communication event reporting method and system

Technical Field

The invention relates to the field of communication, in particular to a method and a system for reporting a machine type communication event.

Background

With the development of mobile network services and automation control technologies, a Machine Type Communication (MTC) method, also called a machine to machine (M2M) communication method, has appeared, in which both parties of communication are machine devices.

In M2M communication, the communication behavior is automatically controlled, i.e., the control of the initiation, termination, and some admission and restriction during communication are all automated behaviors. This behavior is tied to the constraints and controls on the behavior of the machines (i.e., terminals in M2M communications) in M2M communications, the behavior of the terminals in M2M communications is tied to the service subscription data, and the network manages the terminals in M2M communications according to the service subscription data.

The most typical communication method in machine-type communication is communication between a terminal called an MTC terminal (mtcu), and an application server called an MTC server (MTCServer).

Under 2G/3G/LTE access, M2M communication mainly uses a Packet Service (PS) network as a bottom bearer network, and implements service layer communication between an MTC terminal and an MTC server. Specifically, the M2M communication entity may be accessed to an Evolved Packet System (EPS) network through an evolved universal mobile telecommunications system terrestrial radio access network (evolved universal terrestrial radio access network, abbreviated as E-UTRAN), or may be accessed to a general radio packet service (GPRS) through a GSM/EDGE radio access network (GSM/EDGE radio access network, abbreviated as GERAN)/UTRAN network, where fig. 1 is a schematic diagram of an architecture in which the M2M communication entity is accessed to the EPS according to the related art. As shown in fig. 1, the mtserver may serve as an application function entity (AF) connected to a Policy and Charging Rules Function (PCRF) through an Rx interface to control bearers. In addition, the MTCServer may play a role of a SIPAS, connected with a Home Subscriber Server (HSS) through an Sh interface to access application service data.

In fig. 1, the mtue is accessed to the EPS network through E-utran (enodeb), and after being allocated with an IP address, an IP channel may be established between the mtue and the mtserver, thereby implementing upper layer service communication with the mtserver. The IP channel established between the MTCU and the MTCServer is a logical IP channel, and the physical path of the IP channel passes through: an eNodeB, a serving gateway (S-GW, or SGW), a packet data network gateway (PDNGW, or P-GW, or PGW).

In practical application, the MTCServer needs to monitor the operating state of the mtccus, dynamically acquire the current state of the mtccus in time, and acquire the MTCServer in time when the current state of the mtccus changes. Wherein the state change of the mtcu may include: the mtue is detached from the network, the mtue enters a non-connected state, the mtue releases a radio connection, the current location of the mtue changes, and the like. The change of the status of the mtue, which may be referred to as an MTC event, may generally define an MTC event to be monitored in MTC subscription data of a Home Location Register (HLR)/HSS, and is issued by the HLR/HSS to a serving general packet radio service support node (SGSN)/MME through a procedure of the mtue attaching to a network. For the detection of the MTC event, a network entity of the core network is usually required to detect the MTC event, for example, in the EPS network, the network element responsible for detecting the MTC event may be: MME/SGW/PGW, for example, in a GPRS network, a network element responsible for detecting an MTC event may be an SGSN/gateway GPRS support node (GGSN, for short), and the like. When the MTC event is detected, it is usually reported to the MTCServer, so that the MTCServer can timely know the operation status of the mtue.

In the related art, a reporting scheme that an MME/SGSN serves as an MTC event detection entity or a GGSN/PGW serves as an MTC event detection entity is proposed.

When the MME/SGSN serves as an MTC event detection entity and an MTC event is detected by the current MME/SGSN, the MTC event report may be sent to the MTCGW in the following manners, and then the MTCGW sends the MTC event report to the mtserver: (1) if a direct interface exists between the SGSN/MME and the MTCGW, the SGSN/MME is used as an MTC event execution entity to directly send the MTC event report to the MTCGW; (2) the SGSN/MME sends the MTC event report to the GGSN/PGW by using a GTP-C message between the SGSN/MME and the GGSN/SGW/PGW, and the GGSN/PGW serves as an MTC event report entity and sends the MTC event report to the MTCGW by using an MTCI interface with the MTCGW; (3) the SGSN/MME sends the MTC event report to the GGSN/PGW by using a GTP-C message, the GGSN/PGW sends the MTC event report to the PCRF by using a Gx interface between the GGSN/PGW and the PCRF serves as an MTC event report entity and sends the MTC event report to the MTCGW by using an Rx interface between the PCRF and the MTCGW.

When the GGSN/PGW is an MTC event detection entity and when the current GGSN/PGW detects that an MTC event occurs, the mtcsgw may send the MTC event report to the mtcsgw in the following two ways, and then the mtcsgw sends the MTC event report to the MTCServer: (1) GGSN/PGW as event report entity sends MTC event report to MTCI interface between MTCI and MTCI GW; (2) the GGSN/PGW sends the MTC event report to the PCRF by using a Gx interface between the GGSN/PGW and the PCRF, and the PCRF serves as an event reporting entity and sends the MTC event report to the MTCGW by using an Rx interface between the GGSN/PGW and the MTCGW.

The inventor finds that, in the related art, when the MTC event detection entity reports the MTC event report, it is not specified to which MTCServer the MTC event report is sent, so that the MTC event report is sent to the wrong MTCServer, and the MTCServer cannot effectively monitor the mtcces.

Disclosure of Invention

The present invention is directed to a method and system for reporting an MTC event, so as to solve at least one of the above problems.

According to an aspect of the present invention, there is provided an MTC event reporting method, including: acquiring the address of an MTC server corresponding to the MTC equipment according to the identification information of the MTC equipment; and sending the MTC event report of the MTC equipment to the MTC server.

According to another aspect of the present invention, there is provided a machine type communication system including: the MTC event detection entity is used for detecting the MTC event of the MTC equipment and sending an MTC event report to the MTC event report entity, wherein the MTC event report carries the identification information of the MTC equipment; the MTC event report entity is used for sending the MTC event report to an MTC access gateway; the MTC access gateway is used for analyzing the identification information of the MTC equipment from the MTC event report, acquiring the address of an MTC server corresponding to the MTC equipment according to the identification information, and sending the MTC event report to the MTC server.

According to still another aspect of the present invention, there is provided another machine type communication system including: the MTC event detection entity is used for detecting the MTC event of the MTC equipment, constructing a full domain name for discovering an MTC server corresponding to the MTC equipment by using the identification information of the MTC equipment, acquiring the address of the MTC server from the domain name server according to the full domain name, carrying the address of the MTC server in an MTC event report and sending the MTC event report to the MTC event report entity; and the MTC event reporting entity is used for sending the MTC event report to the MTC server corresponding to the address.

According to still another aspect of the present invention, there is provided another machine type communication system including: the MTC event detection entity is used for detecting the MTC event of the MTC equipment and sending the MTC event report to the MTC event report entity; the MTC event report entity is used for analyzing the identification information of the MTC equipment from the MTC event report, constructing a full domain name for discovering an MTC server corresponding to the MTC equipment by using the identification information, acquiring the address of the MTC server from the domain name server according to the full domain name, and sending the MTC event report to the MTC server corresponding to the address.

According to the invention, when the MTC event report is reported to the MTC server, the address of the MTC server corresponding to the MTC equipment is obtained according to the identification information of the MTC equipment, so that the MTC event report is sent to the correct MTC server, the problem that the MTC event report is sent to the wrong MTC server due to the fact that no specific MTC server is specified in the related technology is solved, and the effectiveness of monitoring the MTC equipment by the MTC server is further ensured.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is an architecture diagram of an M2M communication entity accessing an EPS according to the related art;

fig. 2 is a schematic structural diagram of a machine type communication system according to a first embodiment of the present invention;

fig. 3 is a schematic structural diagram of an alternative machine type communication system according to a first embodiment of the present invention;

fig. 4 is a schematic structural diagram of another alternative machine type communication system according to the first embodiment of the present invention;

fig. 5 is a flowchart of a MTC event reporting method according to a first embodiment of the present invention;

fig. 6 is a schematic structural diagram of a machine type communication system according to a second embodiment of the present invention;

fig. 7 is a flowchart of an MTC event reporting method according to a second embodiment of the present invention;

fig. 8 is a flowchart of an MTC event reporting method according to a third embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

Example one

Fig. 2 is a schematic structural diagram of a machine type communication system according to an embodiment of the present invention, where the system includes: an MTC event detection entity 10, an MTC event reporting entity 20 and an MTC access gateway 30. In this embodiment, the MTC event detection entity 10, the MTC event reporting entity 20 and the MTC access gateway 30 are located in the same network, that is, all located in a home network of the MTC device, or all located in a visited network of the MTC device.

The MTC event detection entity 10 is configured to detect an MTC event of the MTC device 1, and send an MTC event report to the MTC event reporting entity, where the MTC event report carries identification information of the MTC device 1; an MTC event reporting entity 20, configured to send an MTC event report to an MTC access gateway 30; the MTC access gateway 30 is configured to parse the identifier information of the MTC device 1 from the MTC event report, obtain an address of the MTC server 2 corresponding to the MTC device 1 according to the identifier information, and send the MTC event report to the MTC server 2.

In the system of the embodiment, when receiving the MTC event report, the MTC access gateway 30 parses the identification information of the MTC device from the MTC event report, acquires the address of the MTC server corresponding to the MTC device according to the identification information, and then sends the MTC event report to the corresponding MTC server, so as to ensure that the MTC event report is sent to the correct MTC server.

Fig. 3 is a schematic structural diagram of a machine type communication system according to an alternative embodiment of the embodiment shown in fig. 2, in which an MTC event detection entity 10 acquires an address of an MTC server corresponding to an MTC device according to identification information of the MTC device, and sends the address of the MTC server carried in an MTC event report to an MTC event reporting entity 20, and the MTC event reporting entity 20 sends the MTC event report to the MTC server corresponding to the address.

Fig. 4 is a schematic structural diagram of a machine type communication system according to another alternative embodiment of the embodiment shown in fig. 2, in this embodiment, when detecting an MTC event of an MTC device 1, an MTC event detecting entity 10 sends an MTC event report to an MTC event reporting entity 20, the MTC event reporting entity 20 parses identification information of the MTC device 1 from the MTC event report, acquires an address of an MTC server 2 corresponding to the MTC device 1 according to the identification information, and sends the MTC event report to the MTC server 2 corresponding to the address.

In the embodiments shown in fig. 2 to fig. 4, the MTC event detecting entity 10, the MTC event reporting entity 20, or the MTC access gateway 30 may construct a full domain name (FQDN) for discovering the MTC server 2 by using the identification information of the MTC device, and obtain the address of the MTC server 2 from a Domain Name Server (DNS) according to the full domain name. By acquiring the address of the MTC server 2 in this way, the MTC event detection entity 10, the MTC event reporting entity 20 and the MTC access gateway 30 may be located in a home network of the MTC device or a visited network of the MTC device.

Or, if the MTC event detecting entity 10, the MTC event reporting entity 20 and the MTC access gateway 30 are located in the home network of the MTC device, a database may be set, where the database stores the correspondence between the identification information of the MTC device in the current network and the address of the MTC server corresponding to the MTC device, the database may be configured on the MTC access gateway in the home network of the MTC device, or may be configured on a subscription data server of the MTC device, for example, an HLR of a GPRS network or an HSS of an EPS network, or may be used as an independent third-party database, and the MTC access gateway 30 may access the database to query the address of the MTC server corresponding to the analyzed identification information of the MTC device. Therefore, in the embodiment shown in fig. 2, the MTC access gateway 30 may also obtain, from the pre-configured correspondence, the address of the MTC server 2 corresponding to the identification information of the MTC device 1 analyzed from the MTC event report. Therefore, the interaction between the MTC access gateway 30 and the DNS can be reduced, and the reporting efficiency of the MTC event report is improved.

Preferably, if the database is configured on a subscription data server of the MTC device, the MTC access gateway 30 may send an inquiry request carrying the identification information of the MTC device 1 to the subscription data server, and after receiving the inquiry request, the subscription data server inquires the stored correspondence, obtains the address of the MTC server 2 corresponding to the identification information of the MTC device 1 from the stored correspondence, and returns the address of the MTC server to the MTC access gateway 30, so that the MTC access gateway 30 obtains the address of the MTC server 2 corresponding to the MTC device 1. It should be noted that in practical applications, the MTC access gateway 30 may also obtain the address of the MTC server 2 from the subscription data server in other manners, for example, the MTC access gateway 30 requests the subscription data server for the correspondence, stores the correspondence locally, and then queries the address of the MTC server corresponding to the MTC device 1 from the correspondence.

Preferably, the identification information of the MTC device may be an Identification (ID) of the MTC device, or may also be a group identification (group ID) of an MTC device group to which the MTC device belongs, so that a FQDN may be constructed for one MTC device group, or only an MTC server corresponding to the MTC device group may be stored in the correspondence, thereby reducing the number of constructing the FQDN or reducing a storage space occupied by the correspondence.

Preferably, in the embodiment shown in fig. 3 or fig. 4, if an interface directly connected between the MTC event reporting entity 20 and the MTC server 2 exists, the MTC event reporting entity 20 may directly send the MTC event report to the MTC server 2 according to an address of the MTC server 2, otherwise, the MTC event reporting entity 20 may send the MTC event report to the MTC access gateway 30, where the MTC event report carries the address of the MTC server 2, and the MTC access gateway 30 sends the MTC event report to the MTC server 2 corresponding to the address.

Preferably, in the embodiments shown in fig. 2 to fig. 5, the MTC event detecting entity 10 and the MTC event reporting entity 20 may be integrated, for example, the MTC event detecting entity 10 and the MTC event reporting entity 20 may be an SGSN in a GPRS network or an MME in an EPS network.

Fig. 5 is a flowchart of a method for reporting an MTC event according to a first embodiment of the present invention, where the method mainly includes the following steps (step S502-step S504):

step S502, obtaining the address of the MTC server 2 corresponding to the MTC equipment 1 according to the identification information of the MTC equipment 1;

for example, the MTC event detection entity 10, the MTC event reporting entity 20, or the MTC access gateway 30 may obtain the address of the MTC server 2 corresponding to the MTC device 1 according to the identification information of the MTC device 1.

For example, the identification information may be an ID of the MTC device 1, or may be a group ID of an MTC device group to which the MTC device 1 belongs.

For example, the MTC event detection entity 10, the MTC event reporting entity 20, or the MTC access gateway 30 may construct an FQDN for discovering the MTCServer by using the ID of the MTC device 1, for example, MTC-UE-id.mtc-server.mnc.mcc, where MNC is the network number of the network to which the mtue belongs, MCC is the country number of the network to which the mtue belongs, and both MNC and MCC may be obtained from the ID of the MTC device 1 (for example, if the ID of the mtue is IMSI, the IMSI includes MNC and MCC). Then, the MTC event detection entity 10, the MTC event reporting entity 20 or the MTC access gateway 30 performs a DNS request to obtain the address of the server 2 from the DNS. Alternatively, the MTC event detection entity 10, the MTC event reporting entity 20 or the MTC access gateway 30 may construct an FQDN discovering the MTCServer by using the group ID of the MTC group to which the mtue belongs: MTC-GROUP-id.mtc-server.mnc.mcc. Then, the MTC event detection entity 10, the MTC event reporting entity 20 or the MTC access gateway 30 performs a DNS request to obtain the address of the MTC server 2 from the DNS. If the address of the MTC server 2 is acquired in this way, it is applicable whether the MTC device 1 is currently located in a home network or a visited network.

Alternatively, if the MTC device 1 is currently located in the home network, the MTC access gateway 30 may also obtain the address of the MTC server 2 corresponding to the identification information of the MTC device 1 from a pre-configured database.

Step S504, the MTC event report of the MTC device 1 is sent to the MTC server 2.

For example, if the MTC event detecting entity 10 acquires the address of the MTC server 2 in step S502, the MTC event detecting entity 10 carries the address in the MTC event report and sends the MTC event report to the MTC event reporting entity 20, and the MTC event reporting entity 20 sends the MTC event report to the MTC server 2 corresponding to the address.

In the related art, the MTC event detection entity 10, the MTC event reporting entity 20, or the MTC access gateway 30 does not perform the step of discovering the MTC server when reporting the MTC event report, so that the MTC event report may be sent to an erroneous MTC server, but in the above system of this embodiment, when reporting the MTC event report, the MTC event detection entity 10, the MTC event reporting entity 20, or the MTC access gateway 30 obtains the address of the MTC server corresponding to the MTC device according to the identification information when receiving the MTC event report, and then sends the MTC event report to the corresponding MTC server, so that it can be ensured that the MTC event report is sent to a correct MTC server.

Example two

Fig. 6 is a schematic structural diagram of a machine type communication system according to a second embodiment of the present invention, which is different from the first embodiment in that in the present embodiment, the MTC event detecting entity 10 and the MTC event reporting entity 20 are located in a visited network of the MTC device, and the MTC access gateway 30 is located in a home network of the MTC device.

As shown in fig. 6, in the present embodiment, the MTC event reporting entity 20 may directly send the MTC event report to the MTC access gateway 30 located in the home network. In practical applications, the specific location of the MTCGW of the home network of the MTC equipment (i.e. the MTC access gateway 30 located in the home network) may be registered in a roaming agreement, and the MTC event reporting entity 20 may obtain the address information of the MTC access gateway 30 located in the home network from the roaming agreement, so as to directly send the MTC event report to the MTC access gateway 30 located in the home network. By adopting the scheme, even if the MTCGW is not set in the visiting network, the MTC event report can be sent to the correct MTC server.

Or, if the visited network of the MTC device is configured with an MTC access gateway (i.e. the visited network MTC access gateway 40 in the figure), the MTC event reporting entity 20 may also send the MTC event report to the visited network MTC access gateway 40, and the visited network MTC access gateway 40 sends the MTC event report to the MTC access gateway 30 located in the home network.

In this embodiment, after receiving the MTC event report, the MTC access gateway 30 located in the home network may acquire the MTC server corresponding to the MTC device in the following two ways, so as to send the MTC event report to the MTC server:

in a first manner, the MTC access gateway 30 in the home network may query and acquire the address of the MTC server corresponding to the identifier information of the MTC device analyzed from the MTC event report from the preconfigured correspondence between the identifier information of the MTC device in the current network and the address of the MTC server corresponding to the MTC device, specifically, similar to the first embodiment, the correspondence may be stored in the HLR/HSS, or may be configured on the MTC access gateway 30 in the home network, or may be stored as a third-party database.

In the second way, the MTC access gateway 30 in the home network may also use the identification information of the MTC device to construct an FQDN used for discovering the MTC server 2, and obtain the address of the MTC server 2 from the DNS, which is the same as that in the first embodiment and is not described herein.

Preferably, similar to the first embodiment, the identification information of the MTC device in this embodiment may be an ID of the MTC device or a group ID of an MTC device group to which the MTC device belongs.

By the system of the embodiment, when the MTC device roams, the MTC event report is sent to the MTC access gateway 30 of the home network, and the MTC access gateway 30 of the home network obtains the address of the MTC server corresponding to the MTC device according to the identifier information of the MTC device in the MTC event report, so as to send the MTC event report of the MTC device to the MTC server.

Fig. 7 is a flowchart of an MTC event reporting method according to a second embodiment of the present invention, where the method mainly includes the following steps:

s701, after the MTC event detection entity detects the MTC event, an MTC event report is generated and sent to the MTC event report entity;

s702, the MTC event reporting entity sends the MTC event report to an MTC access gateway in the network;

for example, the MTC event detection entity may be SGSN/MME, the MTC event reporting entity may be GGSN/PGW, and then the SGSN/MME sends the MTC event report to the GGSN/PGW through a GTP-C message.

In the embodiment, the mtcree is in a roaming condition, the GGSN/PGW is located in the visited network, and the GGSN/MME sends the MTC event report to the MTC access gateway, i.e. the V-MTCGW, in the visited network.

For the roaming situation, after the MTC access gateway (i.e., the V-MTCGW) of the visited network receives the MTC event report, the V-MTCGW may adopt two processing schemes to send the MTC event report, where the first scheme is the following steps S703a1 to S703a2, and the second scheme is the following steps S703b1 to S703b 3.

S703a1, after the V-mtcrew receives the MTC event report, acquiring identification information of the mtcre in the MTC event report, for example, an ID of the mtcre or a group ID of an MTC device group to which the mtcre belongs, and querying an address of an mtserver corresponding to the mtcre using the identification information;

specifically, in this step, the V-mtcsgw may obtain the address of the MTCServer by:

A) the V-MTCGW may construct an FQDN for discovering the MTCServer using the MTCUE ID, in the form of: MTC-UE-ID, MTC-server, MNC, MCC, where MNC is the network number of the network to which the mtue belongs, MCC is the country number of the network to which the mtue belongs, and both MNC and MCC can be obtained from the ID of the mtue (if the ID is IMSI, the IMSI includes MNC and MCC). The V-MTCGW then performs a DNS request to obtain the MTCServer's address. Or,

B) the V-mtcsgw may construct an FQDN for discovering the MTCServer using the group ID of the MTC group to which the mtue belongs, which may take the form of: MTC-GROUP-id.mtc-server.mnc.mcc. The V-MTCGW then performs a DNS request to obtain the MTCServer's address.

S703a2, after obtaining the MTCServer address, the V-MTCSGW sends the MTC event report to the MTCServer;

s703b1, the MTC access gateway (namely V-MTCGW) of the visited network forwards the MTC event report to the MTC access gateway (namely H-MTCGW) of the home network;

in this step, the V-MTCGW may obtain an address of an MTC access gateway, i.e., an H-MTCGW, of the home network according to a roaming agreement signed by the visited network and the home network, thereby transmitting an MTC event report to the H-MTCGW.

S703b2, after the H-MTCGW receives the MTC event report, the method used by the V-MTCGW in the step S703a1 can be adopted to obtain the MTCServer, and the following method can also be adopted to obtain the MTCServer information:

A) the H-MTCGW locally configures the mapping relation between the MTCUs and the MTCServers, or configures the mapping relation in a background database, and the H-MTCGW inquires the mapping table to obtain the MTCServer address information corresponding to the MTCUs. Or,

B) the H-MTCGW and the HLR/HSS have an interface, the HLR/HSS stores the corresponding relation between the ID or the group ID of the MTCUE and the address of the MTC server, and the H-MTCGW queries the HLR/HSS by using the ID of the MTCUE or the group ID of the MTC equipment group to which the MTCUE belongs, which is analyzed from the MTC event report, and obtains the information of the MTCServer, wherein the information can be the address of the MTCServer.

S703b3, after the H-MTCGW finds the MTCServer, the H-MTCGW sends the MTC event report to the MTCServer.

Through the method of the embodiment, the MTC access gateway of the home network of the MTC device may discover the MTCServer and send the MTC event report to the MTCServer, so that the MTC event report may be sent to the correct MTCServer.

EXAMPLE III

In this embodiment, when the MTC device roams, only the MTCGW exists in the home network of the MTC device, and the MTCGW is not deployed in the visited network. In this case, the MTC event reporting entity of the visited network directly transmits the MTC event report to the MTCGW of the home network.

Fig. 8 is a signaling flow chart of MTC event report reporting in this embodiment, and as shown in fig. 8, the difference between this embodiment and the flow shown in fig. 7 is that an MTC event reporting entity directly sends an MTC event report to an mtgw of a home network, instead of sending the MTC event report through an mtgw of a visited network.

In this embodiment, a specific location of the MTCGW of the home network may be registered in the roaming agreement, so that an MTC event reporting entity (e.g., SGSN/MME, GGSN/PGW, etc.) of the visited network may obtain an address of the MTCGW located in the home network, thereby sending an MTC event report to the MTCGW.

By the embodiment, the MTC event report of the MTC equipment in the visited network can be sent to the correct MTC server under the condition that the MTCGW is not deployed in the visited network.

As can be seen from the above description, in the embodiment of the present invention, when reporting the MTC event report to the MTC server, the address of the MTC server corresponding to the MTC device is obtained according to the identification information of the MTC device, so that the MTC event report is sent to the correct MTC server, which solves the problem in the related art that the MTC event report is sent to the wrong MTC server due to no specific MTC server being specified, and further ensures the effectiveness of the MTC server in monitoring the MTC device.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A Machine Type Communication (MTC) event reporting method is characterized by comprising the following steps:

acquiring an address of an MTC server corresponding to MTC equipment according to identification information of the MTC equipment;

sending an MTC event report of the MTC equipment to the MTC server;

wherein the MTC event comprises: the MTC equipment enters a non-connection state, releases wireless connection or changes the current position of the MTC equipment;

acquiring the address of the MTC server corresponding to the MTC device according to the identification information comprises:

the MTC event detection entity, the MTC event report entity or the MTC access gateway constructs a full domain name for discovering the MTC server by using the identification information;

the MTC event detection entity, the MTC event report entity or the MTC access gateway acquires the address of the MTC server from a domain name server according to the full domain name; or,

the MTC access gateway of the home network of the MTC equipment receives the MTC event report, and the identification information of the MTC equipment is analyzed from the MTC event report;

the MTC access gateway of the home network inquires the address of the MTC server corresponding to the analyzed identification information from the preset corresponding relation between the identification information of the MTC equipment and the address of the MTC server.

2. The method of claim 1, wherein receiving the MTC event report by an MTC access gateway of the home network comprises:

and the MTC event reporting entity reports the MTC event reporting entity to an MTC access gateway of the home network, wherein the MTC event reporting entity is positioned in the home network or a visited network of the MTC equipment.

3. The method of claim 1, wherein receiving the MTC event report by an MTC access gateway of the home network comprises:

an MTC event reporting entity of a visited network of the MTC equipment sends the MTC event report to an MTC access gateway of the visited network;

and the MTC access gateway of the visited network sends the received MTC event report to the MTC access gateway of the home network.

4. The method according to any one of claims 1 to 3, wherein the correspondence is stored at a subscription data server of the MTC device; the inquiring, by the MTC access gateway of the home network, the address of the MTC server corresponding to the resolved identification information from the correspondence includes:

the MTC access gateway of the home network sends a query request carrying the analyzed identification information to the signing data server;

the signed data server acquires the address of the MTC server corresponding to the identification information carried in the query request from the corresponding relation;

and the signed data server returns a query response to the MTC access gateway of the home network, wherein the query response carries the address of the MTC server.

5. The method according to any one of claims 1 to 3, wherein sending the MTC event report to the MTC server comprises: and the MTC access gateway of the home network sends the MTC event report to the MTC server.

6. The method according to any one of claims 1 to 3, wherein the identification information comprises: the identification of the MTC equipment and/or the group identification of the MTC equipment group to which the MTC equipment belongs.

7. A machine type communication system, comprising:

the MTC event detection entity is used for detecting an MTC event of MTC equipment and sending an MTC event report to an MTC event report entity, wherein the MTC event report carries identification information of the MTC equipment;

the MTC event reporting entity is used for sending the MTC event report to an MTC access gateway;

the MTC access gateway is used for analyzing the identification information from the MTC event report, acquiring the address of an MTC server corresponding to the MTC equipment according to the identification information, and sending the MTC event report to the MTC server;

wherein the MTC event comprises: the MTC equipment enters a non-connection state, releases wireless connection or changes the current position of the MTC equipment;

the MTC event reporting entity is located in a home network or a visited network of the MTC equipment, the MTC access gateway is located in the home network, and the MTC access gateway is used for inquiring an address of an MTC server corresponding to the analyzed identification information from a preset corresponding relation between the identification information of the MTC equipment and the address of the MTC server; or,

the MTC access gateway is used for constructing a full domain name used for discovering the MTC server by using the identification information carried in the MTC event report, and acquiring the address of the MTC server from a domain name server according to the full domain name.

8. The machine type communication system of claim 7, wherein the MTC event reporting entity is located in the visited network; the machine type communication system also comprises an MTC access gateway positioned in the visit network; and the MTC event reporting entity sends the MTC event report to an MTC access gateway located in a home network through the MTC access gateway located in the visited network.

9. A machine type communication system, comprising:

the MTC event detection entity is used for detecting an MTC event of MTC equipment, constructing a full domain name for discovering an MTC server corresponding to the MTC equipment by using identification information of the MTC equipment, acquiring an address of the MTC server from a domain name server according to the full domain name, carrying the address of the MTC server in an MTC event report and sending the MTC event report to the MTC event report entity;

the MTC event reporting entity is used for sending the MTC event report to the MTC server corresponding to the address;

wherein the MTC event comprises: the MTC equipment enters a non-connection state, the MTC equipment releases wireless connection or the current position of the MTC equipment changes.

10. A machine type communication system, comprising:

the MTC event detection entity is used for detecting the MTC event of the MTC equipment and sending the MTC event report to the MTC event report entity;

the MTC event report entity is used for analyzing the identification information of the MTC equipment from the MTC event report, constructing a full domain name for discovering an MTC server corresponding to the MTC equipment by using the identification information, acquiring the address of the MTC server from a domain name server according to the full domain name, and sending the MTC event report to the MTC server corresponding to the address;

wherein the MTC event comprises: the MTC equipment enters a non-connection state, the MTC equipment releases wireless connection or the current position of the MTC equipment changes.