WO2011134370A1

WO2011134370A1 - Machine type communication event reporting method and system thereof

Info

Publication number: WO2011134370A1
Application number: PCT/CN2011/073186
Authority: WO
Inventors: 李志军; 谢宝国
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-04-30
Filing date: 2011-04-22
Publication date: 2011-11-03
Also published as: CN102238617B; CN102238617A

Abstract

A machine type communication event reporting method and system thereof are provided by the present invention. Wherein, the machine type communication event reporting method includes the following steps: according to identifier information of a Machine Type Communication (MTC) apparatus, an address of a MTC server corresponding to the MTC apparatus is obtained; a MTC event of the MTC apparatus is reported to the MTC server. According to the present invention, the MTC event can be ensured to report to the correct MTC server.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to the field of communications, and in particular to a method and system for a machine type communication event. BACKGROUND With the development of mobile network services and automatic control technologies, a machine type communication (MTC) mode, also called a machine to machine (M2M) communication mode, has appeared. In this communication method, both parties to the communication are machine devices. In M2M communication, the communication behavior is automatically controlled, that is, the initiation and termination of communication and the control of some admission and restriction in the communication process are automated behaviors. This behavior depends on the constraints and control of the behavior of the machine (ie, the terminal in the M2M communication) in the M2M communication. The behavior of the terminal in the M2M communication is constrained by the service subscription data, and the network is in the M2M communication according to the service subscription data. The terminal is managed. The most typical communication method in machine type communication is the communication between the terminal and the application server. The terminal is called MTC User Equipment (MTC UE), and the application server is called MTC server. ( MTC Server ). Under the 2G/3G/LTE access, the M2M communication mainly uses the Packet Service (PS) network as the underlying bearer network to implement service layer communication between the MTC terminal and the MTC server. Specifically, the M2M communication entity can access the Evolved Packet System (EPS) network through an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The GSM/EDGE Radio Access Network (GERAN)/UTRAN network can also be used to access the General Packet Radio Service (GPRS). Figure 1 is the basis for the data packet. Schematic diagram of the architecture of the related art M2M communication entity accessing to the EPS. As shown in Figure 1, the MTC Server can function as an Application Function (AF). The Rx interface is connected to the Policy and Charging Rules Function (PCRF). To achieve control of the bearer. In addition, the MTC Server can act as a SIP AS and connect to the Home Subscriber Server (HSS) through the Sh interface to access application service data. In FIG. 1, the MTC UE accesses the EPS network through the E-UTRAN (eNodeB). After the IP address is assigned, an IP channel can be established between the MTC UE and the MTC Server, thereby implementing an upper layer with the MTC Server. Business communication. The IP channel established between the MTC UE and the MTC Server is a logical IP channel, and its physical path passes through: eNodeB, Serving Gateway (S-GW, or SGW), and packet data network gateway ( Packet Data Network Gateway, referred to as PDN GW, or P-GW, or PGW). In an actual application, the MTC Server needs to monitor the running status of the MTC UE, and dynamically learn the current state of the MTC UE in time, and the MTC Server knows the time when the current state of the MTC UE changes. The status change of the MTC UE may include: the MTC UE detaches from the network, the MTC UE enters the non-connected state, the MTC UE releases the wireless connection, and the current location of the MTC UE changes. The change of the state of these MTC UEs may be referred to as an MTC event, and the MTC event that needs to be monitored may be defined in the MTC subscription data of the Home Location Register (HLR)/HSS, and the MTC UE is used. The process of attaching to the network is sent by the HLR/HSS to the Serving General Packet Radio Service Support Node (SGSN) / MME. For the detection of the MTC event, the network entity of the core network is usually required to detect. For example, in the EPS network, the network element responsible for detecting the MTC event may be: MME/SGW/PGW, etc., such as the GPRS network, the network responsible for detecting the MTC event. The element may be an SGSN/Gateway GPRS Support Node (GGSN). After the MTC event is detected, it usually needs to be sent to the MTC Server so that the MTC Server can know the running status of the MTC UE in time. In the related art, a reporting scheme is proposed in which an MME/SGSN is used as an MTC event detecting entity or a GGSN/PGW as an MTC event detecting entity. When the MME/SGSN is used as the MTC event detection entity, when the current MME/SGSN detects that an MTC event occurs, the MTC event 4 can be sent to the following methods.

After the MTC GW, the MTC GW sends the MTC event report to the MTC Server: (1) If

A direct interface exists between the SGSN/MME and the MTC GW, and the SGSN/MME acts as an MTC event execution entity to directly report the MTC event to the MTC GW. (2) SGSN/MME utilization and

The GTP-C message between the GGSN/SGW/PGW sends the MTC event report to the GGSN/PGW.

The GGSN/PGW acts as an MTC event reporting entity using the MTCi interface with the MTC GW to MTC The event report is sent to the MTC GW; (3) The SGSN/MME sends the MTC event report to the GGSN/PGW by using the GTP-C message, and the GGSN/PGW sends the MTC event 4 report to the PCRF by using the Gx interface with the PCRF, PCRF As the MTC event 4, the reporting entity sends an MTC event report to the MTC GW using the Rx interface with the MTC GW. When the GGSN/PGW is an MTC event detection entity, the current GGSN/PGW detects that there is

When the MTC event occurs, the MTC event 4 can be sent to the MTC GW in two ways. The MTC GW sends the MTC event report to the MTC Server: (1) The GGSN/PGW is used as the event reporting entity and the MTC GW. The MTCi interface sends the MTC event report to the MTC GW; (2) the GGSN/PGW sends the MTC event report to the PCRF by using the Gx interface with the PCRF, and the PCRF uses the Rx interface with the MTC GW as the event 4 reporting entity. Send the MTC event report to the MTC GW. The inventor has found that in the related art, when the MTC event detecting entity reports the MTC event report, it does not specify which MTC Server to send the MTC event report to, so that the MTC event report is sent to the wrong MTC Server, thereby causing the MTC. The Server cannot effectively monitor the MTC UE. SUMMARY OF THE INVENTION A primary object of the present invention is to provide an MTC event reporting method and system to solve at least one of the above problems. According to an aspect of the present invention, a method for an MTC event is provided, including: acquiring an address of an MTC server corresponding to the MTC device according to the identifier information of the MTC device; and sending the MTC event report of the MTC device to The above MTC server. The obtaining, by the identifier information, the address of the MTC server corresponding to the MTC device, includes: the MTC event detection entity, the MTC event 4 reporting entity, or the MTC access gateway constructing a discovery device by using the identifier information The full domain name of the MTC server; the MTC event detection entity, the MTC event reporting entity, or the MTC access gateway acquires the address of the MTC server from the domain name server according to the full domain name. The obtaining, by the identifier information, the address of the MTC server corresponding to the MTC device, the MTC access gateway of the home network of the MTC device receiving the MTC event report, and parsing out the MTC device from the MTC device Identification information; the MTC access gateway of the home network is from advance The address of the MTC server corresponding to the parsed identifier information is queried in the correspondence between the identifier information of the set MTC device and the address of the MTC server. The receiving, by the MTC access gateway of the home network, the MTC event report includes: the MTC event reporting entity reporting the MTC event reporting entity to the MTC access gateway of the home network, where the MTC event reporting entity Located in the home network or visited network of the MTC device. The receiving, by the MTC access gateway of the home network, the MTC event report includes: the MTC event of the visited network of the MTC device reporting the MTC event 4 to the MTC of the visited network An access gateway; the MTC access gateway of the visited network sends the received MTC event report to the MTC access gateway of the home network. The corresponding relationship is stored in the subscription data server of the MTC device; the MTC access gateway of the home network queries the address of the MTC server corresponding to the parsed identifier information from the corresponding relationship, including: The MTC access gateway of the home network sends a query request carrying the parsed identifier information to the subscription data server; the subscription data server obtains the identifier carried in the query request from the correspondence relationship The address of the MTC server corresponding to the information; the subscription data server returns a query response to the MTC access gateway of the home network, where the query response carries the address of the MTC server. The sending the MTC event report to the MTC server includes: sending, by the MTC access gateway of the home network, the MTC event report to the MTC server. The identifier information includes: an identifier of the MTC device and/or a group identifier of an MTC device group to which the MTC device belongs. According to another aspect of the present invention, a machine type communication system is provided, comprising: an MTC event detection entity configured to detect an MTC event of an MTC device, and send an MTC event report to an MTC event 4 reporting entity, the MTC event report Carrying the identification information of the MTC device; the MTC event reporting entity is configured to send the foregoing MTC event report to the MTC access gateway; and the MTC access gateway is configured to parse the identification information of the MTC device from the MTC event report, Obtain an address of the MTC server corresponding to the MTC device according to the identifier information, and send the foregoing MTC event report to the MTC server. The MTC event reporting entity is located in the home network or the visited network of the MTC device, the MTC access gateway is located in the home network, and the MTC access gateway is set to be pre-set. The address of the MTC server corresponding to the parsed identifier information is queried in the correspondence between the identifier information of the MTC device and the address of the MTC server. The MTC event reporting entity is located in the visited network; the machine type communication system further includes an MTC access gateway located in the visited network; and the MTC event reporting entity passes the MTC access gateway located in the visited network. The MTC event report is sent to the MTC access gateway located at the home network. The MTC access gateway is configured to use the identifier information carried in the MTC event report to construct a full domain name for discovering the MTC server, according to the full domain name from the domain name server. Get the address of the MTC server. According to still another aspect of the present invention, there is provided another machine type communication system, comprising: an MTC event detecting entity configured to detect an MTC event of the MTC device, and constructing a MTC for discovering the MTC by using the identification information of the MTC device The full domain name of the MTC server corresponding to the device, the address of the MTC server is obtained from the domain name server according to the full domain name, and the address of the MTC server is carried in the MTC event report and sent to the MTC event reporting entity; the MTC event report The entity is set to send the MTC event 4 report to the MTC server corresponding to the address. According to still another aspect of the present invention, another machine type communication system is provided, including: an MTC event detecting entity configured to detect an MTC event of an MTC device, and send an MTC event report to an MTC event reporting entity; an MTC event The reporting entity is configured to parse the identification information of the MTC device from the foregoing MTC event report, and use the identifier information to construct a full domain name for discovering the MTC server corresponding to the MTC device, and obtain the MTC service from the domain name server according to the reporting domain name. The address of the device, the above MTC event 4 is sent to the MTC server corresponding to the address. According to the present invention, when the MTC event report is reported 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 related art. The problem that the MTC event report is sent to the wrong MTC server without specifying a specific MTC server ensures the effectiveness of the MTC server to monitor the MTC device. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawing: 1 is a schematic structural 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 Embodiment 1 of the present invention; FIG. 3 is a replaceable embodiment according to the 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 schematic diagram of an MTC event according to the first embodiment of the present invention. FIG. 6 is a schematic structural diagram of a machine type communication system according to Embodiment 2 of the present invention; FIG. 7 is a flowchart of a method for performing an MTC event according to Embodiment 2 of the present invention; FIG. 8 is a flowchart of the present invention. A flow chart of the method of the MTC event of the third embodiment. 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. Embodiment 1 FIG. 2 is a schematic structural diagram of a machine type communication system according to Embodiment 1 of the present invention. The system includes: an MTC Event Detection Entity 10, an MTC Event 4 Reporting Entity 20, and an MTC Access Gateway 30. In this embodiment, the MTC event detection entity 10, the MTC event 4 reporting entity 20, and the MTC access gateway 30 are located in the same network, that is, both located in the home network of the MTC device, or both located in the visited network of the MTC device. The MTC event detecting 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 4 carries the identification information of the MTC device 1; the MTC event reporting entity 20, The MTC event report is sent to the MTC access gateway 30. The MTC access gateway 30 is configured to parse the identification information of the MTC device 1 from the MTC event 4 report, and obtain the MTC server corresponding to the MTC device 1 according to the identifier information. The address of 2 sends the MTC event report to the MTC server 2. In the related art, the MTC access gateway 30 does not perform the step of discovering the MTC server when receiving the MTC event report, so that the MTC event report may be sent to the wrong MTC server, and in the above system of the embodiment, the MTC is connected. Upon receiving the MTC event report, the ingress gateway 30 parses the identification information of the MTC device, obtains the address of the MTC server corresponding to the MTC device according to the identification information, and sends the MTC event report to the corresponding MTC server, so that Be sure to send the MTC event report 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 this embodiment, the MTC event detecting entity 10 acquires the address of the MTC server corresponding to the MTC device according to the identification information of the MTC device. And transmitting the address of the MTC server to the MTC event reporting entity 20 in the MTC event report, and the MTC event reporting entity 20 sends the MTC event 4 report to the MTC server corresponding to the address. 4 is a schematic structural diagram of a machine type communication system of another alternative embodiment of the embodiment shown in FIG. 2, in which the MTC event detecting entity 10 detects an MTC event of the MTC device 1 and reports to the MTC event. The reporting entity 20 sends an MTC event 4 report, and the MTC event reporting entity 20 parses the identification information of the MTC device 1 from the MTC event report, and obtains the address of the MTC server 2 corresponding to the MTC device 1 according to the identification information, and reports the MTC event. Send to the MTC server 2 corresponding to the address. In the foregoing embodiment 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 an MTC server 2 using the identification information of the MTC device. The Fully Qualified Domain Name (FQDN) is obtained from the Domain Name Server (DNS) for obtaining the address of the MTC server 2 based on the full domain name. In this way, the address of the MTC server 2 is obtained. The MTC event detection entity 10, the MTC event 4 reporting entity 20, and the MTC access gateway 30 may be located in the home network of the MTC device, or may be located in the visited network of the MTC device. Alternatively, if the MTC event detection entity 10, the MTC event 4 reporting entity 20, and the MTC access gateway 30 are located in the home network of the MTC device, a database may also be set, in which the identifier information of the MTC device of the current network is stored and The correspondence between the addresses of the MTC servers corresponding to the MTC device, the database may be configured on the MTC access gateway of the home network of the MTC device, or may be configured on the subscription data server of the MTC device, for example, on the HLR of the GPRS network, or On the HSS of the EPS network, or as an independent third-party database, the MTC access gateway 30 can access the database and query the address of the MTC server corresponding to the identifier information of the parsed MTC device. Therefore, in the embodiment shown in Figure 2, MTC The access gateway 30 may also acquire the address of the MTC server 2 corresponding to the identification information of the MTC device 1 parsed from the MTC event report from the pre-configured correspondence. This can reduce the interaction between the MTC access gateway 30 and the DNS, thereby improving the efficiency of the MTC event. Preferably, if the database is configured on the subscription data server of the MTC device, the MTC access gateway 30 may send a query request for carrying the identification information of the MTC device 1 to the subscription data server, and the subscription data server receives the query request. Then, the saved correspondence is obtained, the address of the MTC server 2 corresponding to the identifier information of the MTC device 1 is obtained, and the address of the MTC server is returned to the MTC access gateway 30, so that the MTC access gateway 30 is enabled. Obtain the address of the MTC server 2 corresponding to the MTC device 1. It should be noted that, in an actual application, the MTC access gateway 30 may 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 corresponding relationship from the subscription data server, and the corresponding correspondence is performed. The relationship is stored locally, and then the address of the MTC server corresponding to the MTC device 1 is queried therefrom. Preferably, the identifier information of the MTC device may be an identifier (ID) of the MTC device, or may be a group identifier (group ID) of the MTC device group to which the MTC device belongs, so that an FQDN may be constructed for one MTC device group. Alternatively, only the MTC server corresponding to the MTC device group may be stored in the foregoing correspondence relationship, so that the number of times the FQDN is constructed may be reduced, or the storage space occupied by the corresponding relationship may be reduced. Preferably, in the embodiment shown in FIG. 3 or FIG. 4, if there is a directly connected interface between the MTC event reporting entity 20 and the MTC server 2, the MTC event reporting entity 20 may be based on the address of the MTC server 2. The MTC event report is sent to the MTC server 2 directly. 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 embodiment shown in Figures 2-5 above, the MTC event detecting entity 10 and

The MTC event 4 reporting entity 20 can be set in one unit. For example, the MTC event detecting entity 10 and the MTC event 4 reporting entity 20 can be an SGSN in a GPRS network, or an MME in an EPS network. FIG. 5 is a flowchart of an MTC event method according to Embodiment 1 of the present invention, the method mainly includes the following steps (Step S502 - Step S504): Step S502, the address of the MTC server 2 corresponding to the MTC device 1 is obtained according to the identification information of the MTC device 1; for example, the MTC event detecting entity 10, the MTC event 4 reporting entity 20, or the MTC access gateway may be used. The address of the MTC server 2 corresponding to the MTC device 1 is obtained according to the identification information of the MTC device 1. For example, the identifier information may be the ID of the MTC device 1 or the group ID of the MTC device group to which the MTC device 1 belongs. For example, the MTC event detection entity 10, the MTC event 4 reporting entity 20 or the MTC access gateway 30 may use the ID of the MTC device 1 to construct an FQDN for discovering the MTC Server, for example, MTC-UE-ID.MTC-Server MNC.MCC, where the MNC is the network number of the network to which the MTC UE belongs, and the MCC is the country number of the network to which the MTC UE belongs, and the MNC and the MCC can be obtained from the ID of the MTC device 1 (for example, if the MTC UE The ID is IMSI, and the IMSI includes MNC and MCC. Then, the MTC event detecting entity 10, the MTC event 4 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 4 reporting entity 20, or the MTC access gateway 30 may construct a FQDN of the discovered MTC Server by using the group ID of the MTC group to which the MTC UE belongs: MTC-GROUP-ID.MTC- Server.MNC.MCC. Then, the MTC event detecting entity 10, the MTC event 4 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 obtained in this way, it is applicable regardless of whether the MTC device 1 is currently located in the home network or in the 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 the 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 4 report to the MTC event reporting entity 20, and the MTC event reporting entity 20 The MTC event report is sent to the MTC server 2 corresponding to the address. The MTC event detection entity 10, the MTC event 4 reporting entity 20, or the MTC access gateway 30 do not perform the steps of discovering the MTC server when reporting the MTC event report. Therefore, it is possible to send the MTC event report to the wrong MTC server. In the above system of the embodiment, when the last 4 MTC event 4 is reported, the MTC event detecting entity 10, the MTC event 4 reporting entity 20 or the MTC interface Upon receiving the MTC event report, the ingress gateway 30 obtains 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, thereby ensuring that the MTC event report is sent to the correct one. MTC service crying embodiment 2 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 this embodiment, the MTC event detecting entity 10 and the MTC event 4 report The entity 20 is located in the visited network of the MTC device, and the MTC access gateway 30 is located in the home network of the MTC device. As shown in FIG. 6, in this embodiment, the MTC event 4 reporting entity 20 can directly send the MTC event report to the MTC access gateway 30 located in the home network. In an actual application, the specific location of the MTC GW of the home network of the MTC device (ie, the MTC access gateway 30 located in the home network) may be registered in the roaming agreement, and the MTC event reporting entity 20 may obtain the attribution from the roaming agreement. The MTC of the network accesses the address information of the gateway 30, thereby transmitting the MTC event 4 report directly to the MTC access gateway 30 located at the home network. With this scheme, even if the visited network does not have the MTC GW set, the MTC event report can be sent to the correct MTC server. Alternatively, if the visited network of the MTC device is configured with an MTC access gateway (ie, the visited network MTC access gateway 40 in the figure), the MTC event 4 reporting entity 20 may also send the MTC event 4 report to the visited network MTC. The gateway 40 transmits the MTC event 4 to the MTC access gateway 30 located in the home network by the visited network MTC access gateway 40. In this embodiment, after receiving the MTC event 4, the MTC access gateway 30 located in the home network may obtain the MTC server corresponding to the MTC device by using the following two methods, so as to send the MTC event to the MTC. For example, the MTC access gateway 30 located in the home network may query and obtain the report from the MTC event from the correspondence between the pre-configured identifier information of the MTC device of the current network and the address of the MTC server corresponding to the MTC device. The address of the MTC server corresponding to the identifier information of the MTC device is parsed. Specifically, similar to the first embodiment, the correspondence may be stored in the HLR/HSS. Alternatively, it may be configured on the MTC access gateway 30 located in the home network, or may be stored as a third-party database. Manner 2, the MTC access gateway 30 located in the home network may also use the identifier information of the MTC device to construct an FQDN for discovering the MTC server 2, and obtain the address of the MTC server 2 from the DNS. The specific configuration is the same as that in the first embodiment. Not to mention. Preferably, the identifier information of the MTC device in this embodiment may be the ID of the MTC device or the group ID of the MTC device group to which the MTC device belongs. With the above system of the present embodiment, the MTC access gateway 30 can be sent to the MTC access gateway 30 of the home network by the MTC event 4 in the case of the MTC device roaming, according to the MTC access gateway 30 in the MTC event report. The identifier information of the MTC device acquires the address of the MTC server corresponding to the MTC device, so that the MTC event report of the MTC device is sent to the MTC server. FIG. 7 is a flowchart of an MTC event method according to Embodiment 2 of the present invention, where the method mainly includes the following steps:

5701. After detecting the MTC event, the MTC event detecting entity generates an MTC event 4 report and sends it to the MTC event 4 to report the entity;

5702, the MTC event 4 reporting entity sends the MTC event 4 report to the MTC access gateway in the network; for example, the MTC event detecting entity may be the SGSN/MME, and the MTC event 4 reporting entity may be the GGSN/PGW, The SGSN/MME sends the MTC event report to the GGSN/PGW through the GTP-C message. In an embodiment, the MTC UE is in a roaming situation, and the GGSN/PGW is located in the visited network, and the GGSN/MME sends the MTC event 4 to the MTC access gateway in the visited network, that is, the V-MTC GW. In the case of roaming, after the MTC access gateway (ie, the V-MTC GW) of the visited network receives the MTC event 4 report, the V-MTC GW can obtain two processing schemes to send an MTC event 4 report, where the first The scheme is the following step 4: S703al~S703a2, and the second scheme is the following steps S703b1 to S703b3. S703al: After receiving the MTC event 4, the V-MTC GW obtains the identifier information of the MTC UE in the MTC event report, for example, the ID of the MTC UE or the group ID of the MTC device group to which the MTC UE belongs, and uses the identifier. The information is used to query the address of the MTC server corresponding to the MTC UE. Specifically, in this step, the V-MTC GW can obtain the address of the MTC Server by:

A) The V-MTC GW can use the ID of the MTC UE to construct an FQDN for discovering the MTC Server, such as: MTC-UE-ID.MTC-Server.MNC.MCC, where the MNC is the network to which the MTC UE belongs. The network number, the MCC is the country number of the network to which the MTC UE belongs, and the MNC and the MCC can be obtained from the ID of the MTC UE (for example, if the ID is IMSI, the IMSI includes the MNC and the MCC). Then, the V-MTC GW performs a DNS request to obtain the address of the MTC Server. Or,

B) The V-MTC GW may construct an FQDN for discovering the MTC Server by using the group ID of the MTC group to which the MTC UE belongs, and the FQDN may be in the following form: MTC-GROUP-ID.MTC-Server.MNC.MCC . The V-MTC GW then performs a DNS request to obtain the address of the MTC Server.

S703a2, after obtaining the address of the MTC Server, the V-MTC GW sends an MTC event report to the MTC Server;

S703bl, the MTC access gateway of the visited network (ie, the V-MTC GW) forwards the MTC event report to the MTC access gateway of the home network (ie, the H-MTC GW); in this step, the V-MTC GW can be based on the visited network. The roaming agreement with the home network obtains the address of the H-MTC GW of the MTC access gateway of the home network, thereby transmitting the MTC event 4 report to the H-MTC GW.

S703b2, after receiving the MTC event 4, the H-MTC GW can obtain the MTC Server by using the method used by the V-MTC GW in step S703al, or obtain the MTC Server information by using the following method:

A). The H-MTC GW locally configures the mapping relationship between the MTC UE and the MTC Server, or the mapping relationship is configured in the background database, and the H-MTC GW queries the mapping table to obtain the MTC Server address information corresponding to the MTC UE. or, B). The H-MTC GW has an interface with the HLR/HSS. The HLR/HSS stores the correspondence between the ID or group ID of the MTC UE and the address of the MTC server, and the H-MTC GW uses the report from the MTC event 4. The ID of the MTC UE that is parsed or the group ID of the MTC device group to which the MTC UE belongs is queried by the HLR/HSS to obtain the information of the MTC Server, and the information may be the address of the MTC Server. S703b3, after the H-MTC GW discovers the MTC Server, sends an MTC event report to the MTC Server. Through the foregoing method in this embodiment, the MTC server can be discovered by the MTC access gateway of the home network of the MTC device, and the MTC event report is sent to the MTC Server, so that the MTC event 4 advertisement can be sent to the correct MTC Server. Embodiment 3 In this embodiment, when the MTC device roams, only the MTC GW exists in the home network of the MTC device, and the MTC GW is not deployed in the visited network. In this case, the MTC event reporting entity of the visited network directly sends the MTC event report to the MTC GW of the home network. FIG. 8 is a signaling flowchart of the MTC event report reported in the embodiment. As shown in FIG. 8 , the difference between the embodiment and the process shown in FIG. 7 is that the MTC event reporting entity directly sends the MTC event report to the home network. The MTC GW, rather than sending it through the MTC GW of the visited network. In this embodiment, the specific location of the MTC GW of the home network may be registered in the roaming protocol, so that the MTC event reporting entity (eg, SGSN/MME, GGSN/PGW, etc.) of the visited network can obtain the MTC GW located in the home network. The address is sent to the MTC GW by the MTC event report. In this embodiment, the MTC event report of the MTC device in the visited network can be sent to the correct MTC server if the visited network does not deploy the MTC GW. In the description of the present invention, in the embodiment of the present invention, when the MTC event report is reported 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, thereby the MTC event. The 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 because no specific MTC server is specified, thereby ensuring the effectiveness of the MTC server for monitoring the MTC device. 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. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of 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 scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. A machine type communication MTC event reporting method, including:

Obtaining an address of the MTC server corresponding to the MTC device according to the identifier information of the MTC device;

Sending an MTC event report of the MTC device to the MTC server.

2. The method according to claim 1, wherein the obtaining an address of the MTC server corresponding to the MTC device according to the identifier information comprises:

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

The MTC event detecting entity, the MTC event 4 advertising entity or the MTC access gateway obtains the address of the MTC server from the domain name server according to the full domain name.

The method of claim 1, wherein the obtaining the address of the MTC server corresponding to the MTC device according to the identifier information comprises:

The MTC access gateway of the home network of the MTC device receives the MTC event report, and parses the identifier information of the MTC device from the MTC access device;

The MTC access gateway of the home network queries the address of the MTC server corresponding to the parsed identifier information from the correspondence between the identifier information of the preset MTC device and the address of the MTC server.

The method according to claim 3, wherein the MTC access gateway of the home network receives the MTC event 4 report includes:

The MTC event reporting entity reports the MTC event reporting entity to the MTC access gateway of the home network, where the MTC event reporting entity is located in the home network or the visited network of the MTC device.

The MTC event reporting entity of the visited network of the MTC device sends the MTC event report to the MTC access gateway of the visited network; The MTC access gateway of the visited network sends the received MTC event report to the MTC access gateway of the home network.

The method according to any one of claims 3 to 5, wherein the correspondence relationship is stored in a subscription data server of the MTC device; the MTC access gateway of the home network queries from the correspondence relationship The address of the MTC server corresponding to the parsed identifier information includes:

The MTC access gateway of the home network sends a query request carrying the decomposed identifier information to the subscription data server;

Obtaining, by the subscription data server, an address of the MTC server corresponding to the identifier information carried in the query request, from the correspondence relationship;

The subscription data server returns a query response to the MTC access gateway of the home network, where the query response carries the address of the MTC server.

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

The method according to any one of claims 1 to 5, wherein the identification information comprises: an identifier of the MTC device and/or a group identifier of an MTC device group to which the MTC device belongs.

9. A machine type communication system comprising:

The MTC event detecting entity is configured to detect an MTC event of the MTC device, and send an MTC event 4 to the MTC event 4 advertising entity, where the MTC event 4 carries the identification information of the MTC device;

The MTC event reporting entity is configured to send the MTC event report to an MTC access gateway;

The MTC access gateway is configured to parse the identifier information from the MTC event report, obtain an address of the MTC server corresponding to the MTC device according to the identifier information, and send the MTC event report to the MTC server.

10. The machine type communication system according to claim 9, wherein the MTC event reporting entity is located in a home network or a visited network of the MTC device, and the MTC access gateway is located in the home network, the MTC The access gateway is set to the standard from the preset MTC device The address of the MTC server corresponding to the parsed identification information is queried in the correspondence between the information and the address of the MTC server.

11. The machine type communication system according to claim 10, wherein: the MTC event reporting entity is located in the visited network; the machine type communication system further comprises an MTC access gateway located in the visited network; the MTC The event reporting entity sends the MTC event report to the MTC access gateway located in the home network through an MTC access gateway located in the visited network.

12. The machine type communication system according to claim 9, wherein the MTC access gateway is configured to construct a full for discovering the MTC server by using the identification information carried in the MTC event report. The domain name, where the full domain name is obtained, obtains the address of the MTC server from the domain name server.

13. A machine type communication system, comprising:

The MTC event detection entity is configured to detect an MTC event of the MTC device, and use the identifier information of the MTC device to construct a full domain name for discovering the MTC server corresponding to the MTC device, and obtain the The address of the MTC server, and the address of the MTC server is carried in the MTC event report and sent to the MTC event reporting entity;

The MTC event reporting entity is configured to send the MTC event report to the MTC server corresponding to the address.

14. A machine type communication system comprising:

The MTC event detecting entity is configured to detect an MTC event of the MTC device, and send the MTC event report to the MTC event reporting entity;

The MTC event reporting entity is configured to parse the identification information of the MTC device from the MTC event report, and use the identifier information to construct a full domain name for discovering the MTC server corresponding to the MTC device, according to the The full domain name obtains the address of the MTC server from the domain name server, and sends the MTC event 4 to the MTC server corresponding to the address.