CN102149190B - Registration method and system of machine type communications (MTC) equipment - Google Patents

Abstract

The embodiment of the present invention relates to a registration method and system of a machine type communication device, wherein the method includes: receiving a first registration request message sent by a 3GPP network device, the first registration request message includes MTC terminal identification information, wherein the The first registration request message is sent by the 3GPP network device according to receiving the second registration request message sent by the MTC device corresponding to the MTC terminal identification information, and the second registration request message includes the MTC terminal identification information; according to The first registration request message returns a registration acceptance message to the MTC device through the 3GPP network device, and the registration acceptance message includes the MTC terminal identification information. In the embodiment of the present invention, the network side can trigger the MTC terminal to send data in a network triggering manner according to the information of the MTC terminal, so as to ensure the normal operation of the MTC service.

Description

Registration method and system for machine type communication equipment

technical field

The embodiments of the present invention relate to the technical field of communication, and in particular to a registration method and system for a machine type communication device.

Background technique

Machine Type Communications (Machine Type Communications, referred to as: MTC) application refers to the application technology of network communication between one or more network elements without human participation, such as: traffic control and management, factory monitoring, remote Applications such as meter reading. According to the preliminary estimates of some organizations, terminals used for Human To Human (H2H) communication in the future may only account for 1/3 of the entire terminal market, while a larger amount of communication is Machine To Machine (Machine To Machine, Abbreviation: M2M) communication service. In fact, the number of machines is at least 4 times that of human beings at present, so M2M has huge market potential. However, the current mobile network is mainly optimized and constructed for H2H applications, and optimizes M2M applications, Machine To Human (M2H) applications, and Human To Machine (H2M) applications. And building very little. In an MTC application, multiple M2Ms with the same MTC application form a whole, which is called a group, and network operators or industry users can manage or control the group as a whole. In the current network architecture design, one or more MTC terminals can be connected to the 3GPP network through an MTC gateway (GateWay, GW for short).

Currently, the MTC terminal cannot be triggered to send data, resulting in unrealized services.

Contents of the invention

Embodiments of the present invention provide a registration method and system for a machine type communication device.

A method for registering a machine type communication device provided by an embodiment of the present invention includes:

Receiving a first registration request message sent by a 3GPP network device, the first registration request message including MTC terminal identification information, wherein the first registration request message is the corresponding MTC terminal identification information of the 3GPP network device according to receiving the MTC terminal identification information sent by the second registration request message sent by the MTC device, where the second registration request message includes the MTC terminal identification information;

According to the first registration request message, return a registration acceptance message to the MTC device through the 3GPP network device, where the registration acceptance message includes the MTC terminal identification information.

The registration system of the machine type communication device provided by the embodiment of the present invention includes:

The MTC device is configured to send a second registration request message, where the second registration request message includes MTC terminal identification information; receive a registration acceptance message, where the registration acceptance message includes the MTC terminal identification information;

A 3GPP network device, configured to receive the second registration request message sent by the MTC device, and send a first registration request message according to the second registration request message, where the first registration request message includes MTC terminal identification information; Forwarding the received registration acceptance message to the MTC device;

The MTC server is configured to receive the first registration request message sent by the 3GPP network device; and send the registration acceptance message to the 3GPP network device according to the first registration request message.

The registration method and system of the machine type communication device provided by the embodiment of the present invention, in the 3GPP network, the network side can obtain the MTC terminal identification information, and then obtain the information of the MTC terminal according to the MTC terminal identification information, and the network side can according to the information, Trigger the MTC terminal to send data to ensure the normal operation of the MTC service.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the accompanying drawings that need to be used in the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without making creative efforts.

FIG. 1 is a flow chart of a registration method for a machine type communication device provided in Embodiment 1 of the present invention;

FIG. 2 is a flow chart of a registration method for a machine type communication device provided in Embodiment 2 of the present invention;

FIG. 3 is a flow chart of a method for registering a machine-type communication device provided in Embodiment 3 of the present invention;

FIG. 4 is a flowchart of a registration method for a machine type communication device provided in Embodiment 4 of the present invention;

FIG. 5 is a flow chart of a registration method for a machine-type communication device provided in Embodiment 5 of the present invention;

FIG. 6 is a flowchart of a method for registering a machine type communication device provided in Embodiment 6 of the present invention;

FIG. 7 is a flowchart of a method for registering a machine-type communication device provided in Embodiment 7 of the present invention;

FIG. 8 is a flow chart of a method for registering a machine type communication device provided in Embodiment 7 of the present invention;

FIG. 9 is a flowchart of a method for registering a machine-type communication device provided in Embodiment 9 of the present invention;

FIG. 10 is a flowchart of a registration method for a machine type communication device provided in Embodiment 10 of the present invention;

FIG. 11 is a flow chart of a method for registering a machine-type communication device provided in Embodiment 11 of the present invention;

FIG. 12 is a flow chart of a method for registering a machine-type communication device provided in Embodiment 12 of the present invention;

FIG. 13 is a flow chart of a method for registering a machine-type communication device according to Embodiment 13 of the present invention;

FIG. 14 is a flow chart of a method for registering a machine type communication device according to Embodiment 14 of the present invention;

FIG. 15 is a flow chart of a registration method for a machine type communication device provided in Embodiment 15 of the present invention;

FIG. 16 is a flow chart of a method for registering a machine type communication device according to Embodiment 16 of the present invention;

FIG. 17 is a schematic structural diagram of a machine-type communication server provided by Embodiment 17 of the present invention;

FIG. 18 is a schematic structural diagram of a machine-type communication device provided by Embodiment 18 of the present invention;

FIG. 19 is a schematic structural diagram of a registration system for a machine type communication device provided by Embodiment 19 of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

From the perspective of M2M service characteristics, the network side needs to know the information of the MTC terminal. However, in the existing network architecture, the MTC terminals under the MTC GW do not have the information of the MTC terminals in the 3GPP network, but only the information of the MTC GWs connected to these MTC terminals. Therefore, the network side cannot normally trigger these MTC terminals to send data, resulting in failure to realize services.

In the following embodiments, the 3GPP network equipment includes equipment located in the 3GPP network.

FIG. 1 is a flow chart of a method for registering a machine type communication device according to Embodiment 1 of the present invention. As shown in Figure 1, this embodiment includes the following parts.

101. Receive a first registration request message sent by a 3GPP network device, where the first registration request message includes MTC terminal identification information; where the first registration request message is sent by the 3GPP network device according to the MTC device corresponding to the received MTC terminal identification information The second registration request message includes the MTC terminal identification information.

In the embodiment of the present invention, the MTC terminal identification information may be used to uniquely identify an MTC terminal. For example, the MTC terminal identification information may be MTC terminal identification information, or may be network address information of the MTC terminal.

The execution subject of this embodiment may specifically be the MTC server.

Wherein, the MTC device initiates a registration process, sends the second registration request message to the 3GPP network device, and the 3GPP network device sends the first registration request message to the MTC server according to the second registration request message. The first registration request message includes MTC terminal identification information, and the MTC terminal identification information is an identifier of the MTC terminal.

102. According to the first registration request message, return a registration acceptance message to the MTC device through the 3GPP network device, where the registration acceptance message includes the MTC terminal identification information.

The MTC server sends the registration acceptance message to the 3GPP network device, and the 3GPP network device returns the registration acceptance message to the MTC device, thereby completing the registration process.

In this embodiment, after receiving the first registration request message, the MTC server may save the MTC terminal identification information.

Further, this embodiment may be applicable to the situation where the MTC terminal directly accesses the 3GPP network, or the MTC terminal accesses the 3GPP network through the MTC GW.

If the MTC terminal directly accesses the 3GPP network, the above-mentioned MTC equipment includes the MTC terminal. The first registration request message may also include MTC device location information, specifically, the MTC device location message is MTC terminal location information.

If the MTC terminal accesses the 3GPP network through the MTC GW, the above-mentioned MTC equipment includes the MTC terminal and the MTC GW. The first registration request message may also include MTC device location information, specifically, the MTC device location information is MTC GW location information. Further, the first registration request message and the second registration request message may also include the MTC GW identifier, and the registration acceptance message may also include the MTC GW identifier. Since one MTC GW can manage several MTC terminals, a certain MTC terminal belongs to the management of a certain MTC GW. In this embodiment, the MTC GW location information indicates the location of the MTC GW, and the MTC server knows the MTC terminal identification information and the MTC

After the GW location information, the MTC GW can be found according to the MTC GW location information, and then the MTC terminal can be found according to the MTC terminal identification information within the scope managed by the MTC GW. Therefore, the MTC server knowing the MTC terminal identification information and the MTC GW location information is equivalent to knowing the location of the MTC terminal.

As another implementation, the location information of the MTC device can be stored in the Home Location Register (Home Location Register, referred to as: HLR) or other servers, and the 3GPP network device can obtain the MTC device corresponding to the MTC terminal identification information from the HLR or other servers. Location information, the 3GPP network equipment sends the location information of the MTC device to the MTC server.

From the above analysis, it can be seen that in the 3GPP network, the MTC server on the network side can obtain the information of the MTC terminal, such as the identification information of the MTC terminal and the location information of the MTC device. , to ensure the normal operation of the MTC service.

FIG. 2 is a flow chart of a registration method for a machine type communication device provided in Embodiment 2 of the present invention. As shown in Figure 2, this embodiment includes the following parts.

201. Send a second registration request message to the 3GPP network device, where the second registration request message includes MTC terminal identification information, for the 3GPP network device to send a first registration request message to the MTC server according to the second registration request message, where the first registration The request message includes MTC terminal identification information.

The execution subject of this embodiment may specifically be an MTC device.

Wherein, the MTC device initiates a registration process, and sends the second registration request message to the 3GPP network device, so that the 3GPP network device sends the first registration request message to the MTC server according to the second registration request message. The first registration request message includes MTC terminal identification information, where the MTC terminal identification information is an identifier of the MTC terminal.

202. Receive a registration acceptance message, where the registration acceptance message includes MTC terminal identification information.

The MTC server sends the registration acceptance message to the 3GPP network device, and the 3GPP network device returns the registration acceptance message to the MTC device, thereby completing the registration process.

Further, this embodiment may be applicable to the situation where the MTC terminal directly accesses the 3GPP network, or the MTC terminal accesses the 3GPP network through the MTC GW.

If the MTC terminal directly accesses the 3GPP network, the above-mentioned MTC equipment includes the MTC terminal. The first registration request message may also include MTC device location information, specifically, the MTC device location message is MTC terminal location information.

If the MTC terminal accesses the 3GPP network through the MTC GW, the above-mentioned MTC equipment includes the MTC terminal and the MTC GW. The first registration request message may also include MTC device location information, specifically, the MTC device location information is MTC GW location information. Further, the first registration request message and the second registration request message may also include the MTC GW identifier, and the registration acceptance message may also include the MTC GW identifier. Since one MTC GW can manage several MTC terminals, a certain MTC terminal belongs to the management of a certain MTC GW. In this embodiment, the MTC GW location information indicates the location of the MTC GW. After the MTC server obtains the MTC terminal identification information and the MTCGW location information, it can find the MTC GW according to the MTC GW location information, and then locate the MTC GW in the range managed by the MTCGW. , find the MTC terminal according to the MTC terminal identification information. Therefore, the MTC server knowing the MTC terminal identification information and the MTC GW location information is equivalent to knowing the location of the MTC terminal.

As another implementation, the MTC device location information can be stored in the HLR or other servers, and the 3GPP network device can obtain the MTC device location information corresponding to the MTC terminal identification information from the HLR or other servers, and the MTC device location information can be saved by the 3GPP network device. The information is sent to the MTC server.

From the above analysis, it can be seen that in the 3GPP network, the MTC server on the network side can obtain the information of the MTC terminal, such as the identification information of the MTC terminal and the location information of the MTC device. , to ensure the normal operation of the MTC service.

FIG. 3 is a flow chart of a method for registering an MTC device according to Embodiment 3 of the present invention. In this embodiment, the MTC device includes an MTC terminal and an MTC GW, and the MTC terminal accesses the 3GPP network through the MTC GW, and the location information of the MTC device is specifically the location information of the MTC GW; the 3GPP network device may specifically include a Service GPRS Support Node (Service GPRS Support Node) , referred to as: SGSN) and Gateway GPRS Support Node (Gateway GPRS Support Node, referred to as: GGSN); the first registration request message is sent by the 3GPP network device according to the second registration request message sent by the MTC device through signaling.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The MTC terminal adds the subscription information to the registration request message and uploads it to the MTC server, that is, the first registration request message and the second registration request message. The registration request messages all include the subscription information of the MTC terminal.

As shown in Figure 3, this embodiment includes the following parts:

301. The MTC terminal adds the MTC terminal identification information and the MTC terminal subscription information to the second registration request message, and sends it to the MTC GW.

Wherein the MTC terminal identification information can specifically be the International Mobile Station Equipment Identity (International Mobile Station Equipment Identity, referred to as: IMEI) or other identification, the embodiment of the present invention does not limit this, and the identification number that can identify the MTC terminal can be used as the MTC Terminal identification information. The description about the MTC terminal identification information is also applicable to other embodiments described below.

The subscription information of the MTC terminal may specifically include information such as a group identifier and/or a service type of the MTC terminal and/or a controllable time for data transmission.

Further, if the MTC terminal corresponds to an MTC server, then this embodiment may initiate registration with the MTC server by default, and the second registration request message may or may not include the MTC server address; if the MTC terminal corresponds to For several MTC servers, the second registration request message and the first registration request message need to include the MTC server address, and the MTC server address is added to the second registration request message by the MTC terminal. This description is also applicable to other embodiments described below.

302. The MTC GW adds the MTC GW identifier and the MTC GW location information to the second registration request message, and passes the second registration request message including the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW location information through Send it to SGSN in signaling mode.

Wherein, the MTC GW identifier can specifically be the MTC GW identification number or the IP address of the MTC GW.

The location information of the MTC GW may specifically be at least one of the identifier of the routing area (Routing Area, RA) where the MTC GW is located and the identifier of the cell where the MTC GW is located. The MTC GW location information can indicate the location information of the MTC terminal. Specifically, if the MTC GW location information is the RA identifier where the MTC GW is located, it indicates that the MTC terminal is located in the RA, and the network side can search within the range of the RA based on the MTC terminal identification information. To the MTC terminal; if the MTC GW location information is the information of the cell where the MTC GW is located, it indicates that the MTC terminal is located in the cell, and the network side can search for the MTC terminal within the range of the cell according to the MTC terminal identification information. Preferably, the MTC GW location information is the information of the cell where the MTC GW is located, because the cell range is relatively small, and it is easier to search for the MTC terminal. This description is also applicable to other embodiments described below.

303. The SGSN sends the second registration request message including the MTC terminal identification information, the MTC terminal subscription information, the MTC GW identifier, and the MTC GW location information to the GGSN.

Optionally, the second registration request message may also include an SGSN identifier, and the SGSN may add the SGSN identifier to the second registration request message. Specifically, if the MTC GW identifier is the MTCGW identification number, the SGSN will add the SGSN identifier to the second registration request message, and the SGSN will include the MTC terminal identification information, MTC terminal subscription information, MTC GW identification number, MTC GW location information and The second registration request message identified by the SGSN is sent to the GGSN.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can address it according to the IP address of the MTC GW, so the SGSN does not need to add the SGSN identifier; there is another possibility that the MTC server can obtain the SGSN identifier through other means, At this time, the SGSN may not add the SGSN identifier. In this way, the SGSN sends the second registration request message including the MTC terminal identification information, the subscription information of the MTC terminal, the IP address of the MTC GW and the location information of the MTC GW to the GGSN.

304. The GGSN obtains the first registration request message including the MTC terminal identification information, the MTC terminal subscription information, the MTC GW identifier, and the MTC GW location information according to the second registration request message, and sends it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Specifically, if the MTC GW identifier is the MTC GW identification number, the GGSN will add the GGSN identifier to the second registration request message to obtain the first registration request message, and the GGSN will include the MTC terminal identification information, MTC terminal subscription information, MTC GW The first registration request message of the identification number, MTC GW location information, SGSN identification and GGSN identification is sent to the MTC server. It can also be said that the first registration request message is obtained by the SGSN adding the SGSN identifier to the second registration request message, and the GGSN adding the GGSN identifier to the second registration request message.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can be addressed according to the IP address of the MTC GW, so the GGSN does not need to add the GGSN identifier; in this case, the first registration request message and the second registration request message are the same , the GGSN sends the first registration request message including the MTC terminal identification information, the subscription information of the MTC terminal, the IP address of the MTC GW and the location information of the MTC GW to the MTC server. Another possible situation is that the MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

305. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW location information.

The MTC GW location information can be used as the MTC terminal location information. If the MTC GW identification is the IP address of the MTC GW, then the MTC GW IP address is used as the routing information of the MTC terminal. If the MTC GW identification is the MTC GW identification number, the first registration The request message also includes at least one of the SGSN identifier and the GGSN identifier, so the MTC GW identification number, the SGSN identifier and the GGSN identifier are jointly used as the routing information of the MTC terminal.

306. The MTC server sends a registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the GGSN.

307. The GGSN forwards the registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the SGSN.

308. The SGSN sends a registration acceptance message including the MTC GW identifier and MTC terminal identification information to the MTC GW according to the MTC GW identifier.

309. The MTC GW forwards the registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

As another implementation, the SGSN can learn the location information of the MTC GW. For example, the SGSN can learn which RA or cell the message comes from according to the message sent by the MTC GW, so that the SGSN can obtain the location information of the MTC GW. In this case, in 302, the MTC GW may not add the MTC GW location information to the second registration request message, but in 303, the SGSN adds the MTC GW location information to the second registration request message.

Through the above registration process, the location information, routing information and subscription information of the MTC terminal are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 4 is a flow chart of a method for registering an MTC device according to Embodiment 4 of the present invention. In this embodiment, the MTC device includes an MTC terminal and an MTC GW, and the MTC terminal accesses the 3GPP network through the MTC GW, and the location information of the MTC device is specifically the location information of the MTC GW; the 3GPP network device may specifically include an SGSN and a GGSN; the first registration request message It is sent by the 3GPP network device according to receiving the second registration request message sent by the MTC device through signaling.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The difference from Embodiment 3 is that the GGSN or SGSN obtains the subscription information of the MTC terminal from the HLR or other servers. The subscription information is added to the second registration request message to obtain the first registration request message, and uploaded to the MTC server.

As shown in Figure 4, this embodiment includes the following parts:

401. The MTC terminal adds the MTC terminal identification information to the second registration request message, and sends it to the MTC gateway.

402. The MTC GW adds the MTC GW identifier and the MTC GW location information to the second registration request message, and sends the second registration request message including the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information to the SGSN through signaling .

Wherein, the MTC GW identifier can specifically be the MTC GW identification number or the IP address of the MTC GW.

403. The SGSN sends the second registration request message including the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information to the GGSN.

Optionally, the second registration request message may also include an SGSN identifier, and the SGSN may add the SGSN identifier to the second registration request message. Specifically, if the MTC GW identification is the MTCGW identification number, the SGSN will add the SGSN identification to the second registration request message, and the SGSN will include the MTC terminal identification information, the MTC GW identification number, the MTC GW location information, and the second registration of the SGSN identification. The request message is sent to GGSN.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can address it according to the IP address of the MTC GW, so the SGSN does not need to add the SGSN identifier; there is another possibility that the MTC server can obtain the SGSN identifier through other means, At this time, the SGSN may not add the SGSN identifier. In this way, the SGSN sends the second registration request message including the MTC terminal identification information, the IP address of the MTC GW and the location information of the MTC GW to the GGSN.

404. After receiving the second registration request message, the GGSN sends a subscription information request message to the HLR or other servers storing the subscription information.

405. The HLR or other servers send the subscription information of the MTC terminal to the GGSN according to the subscription information request message.

The subscription information may specifically include information such as group identifiers and/or service types of the MTC terminals and/or data sending controllable time.

406. The GGSN adds the received subscription information of the MTC terminal to the second registration request message to obtain the first registration request message, which will include the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW position information. A registration request message is sent to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Specifically, if the MTC GW identifier is the MTC GW identification number, the GGSN will add the GGSN identifier to the second registration request message to obtain the first registration request message, and the GGSN will include the MTC terminal identification information, MTC terminal subscription information, MTC GW The first registration request message of the identification number, MTC GW location information, SGSN identification and GGSN identification is sent to the MTC server. It can also be said that the first registration request message is obtained by the SGSN adding the SGSN identifier to the second registration request message, and the GGSN adding the GGSN identifier to the second registration request message.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can be addressed according to the IP address of the MTC GW, so the GGSN does not need to add the GGSN identifier. In this case, the first registration request message is the same as the second registration request message, and the GGSN will send the first registration request message including the MTC terminal identification information, the subscription information of the MTC terminal, the IP address of the MTC GW, and the location information of the MTC GW to the MTC server. Another possible situation is that the MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

407. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW location information.

The MTC GW location information can be used as the MTC terminal location information. If the MTC GW identification is the IP address of the MTC GW, then the MTC GW IP address is used as the routing information of the MTC terminal. If the MTC GW identification is the MTC GW identification number, the first registration The request message also includes at least one of the SGSN identifier and the GGSN identifier, so the MTC GW identification number, the SGSN identifier and the GGSN identifier are jointly used as the routing information of the MTC terminal.

408. The MTC server sends a registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the GGSN.

409. The GGSN forwards the registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the SGSN.

410. The SGSN sends a registration acceptance message including the MTC GW identifier and MTC terminal identification information to the MTC GW according to the MTC GW identifier.

411. The MTC GW forwards the registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

As another implementation, the SGSN can learn the location information of the MTC GW. For example, the SGSN can learn which RA or cell the message comes from according to the message sent by the MTC GW, so that the SGSN can obtain the location information of the MTC GW. In this case, in 402, the MTC GW may not add the MTC GW location information to the second registration request message, but in 403, the SGSN adds the MTC GW location information to the second registration request message.

Through the above registration process, the location information, routing information and subscription information of the MTC terminal are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 5 is a flow chart of a method for registering an MTC device according to Embodiment 5 of the present invention. As shown in Figure 5, the difference between this embodiment and the fourth embodiment above lies in 403 to 406, which can be replaced by:

403'. After receiving the second registration request message sent by the MTC GW, the SGSN sends a subscription information request message to the HLR or other servers storing the subscription information;

404', HLR or other servers send the subscription information of the MTC terminal to the SGSN according to the subscription information request message;

405', the SGSN adds the received subscription information of the MTC terminal to the second registration request message, and the SGSN sends the second registration request message including the MTC terminal identification information, the MTC terminal subscription information, the MTC GW identifier and the MTC GW location information Sent to GGSN.

Optionally, the SGSN may add the SGSN identifier to the second registration request message, and related descriptions may refer to Embodiment 4.

406'. The GGSN obtains the first registration request message including the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW location information according to the second registration request message, and sends the first registration request message to the MTC server.

Optionally, the GGSN may add the GGSN identifier to the second registration request message to obtain the first registration request message. For related descriptions, refer to Embodiment 4.

Through the registration process provided by this embodiment, the location information, routing information and subscription information of the MTC terminal are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 6 is a flow chart of a method for registering an MTC device according to Embodiment 6 of the present invention. In this embodiment, the MTC device includes an MTC terminal and an MTC GW, and the MTC terminal accesses the 3GPP network through the MTC GW, and the location information of the MTC device is specifically the location information of the MTC GW; the 3GPP network device may specifically include an SGSN and a GGSN; the first registration request message It is sent by the 3GPP network device according to receiving the second registration request message sent by the MTC device through signaling.

Different from Embodiment 3 and Embodiment 4, the subscription information of the MTC terminal is stored in the MTC server, and there is no need to upload the subscription information.

As shown in Figure 6, this embodiment includes the following parts:

501. The MTC terminal adds the MTC terminal identification information to the second registration request message, and sends it to the MTC GW.

502. The MTC GW adds the MTC GW identifier and the MTC GW location information to the second registration request message, and sends the second registration request message including the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information to the SGSN through signaling .

Wherein, the MTC GW identifier can specifically be the MTC GW identification number or the IP address of the MTC GW.

503. The SGSN sends the second registration request message including the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information to the GGSN.

Optionally, the second registration request message may also include an SGSN identifier, and the SGSN may add the SGSN identifier to the second registration request message. Specifically, if the MTC GW identification is the MTCGW identification number, the SGSN will add the SGSN identification to the second registration request message, and the SGSN will include the MTC terminal identification information, the MTC GW identification number, the MTC GW location information, and the second registration of the SGSN identification. The request message is sent to GGSN.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can address it according to the IP address of the MTC GW, so the SGSN does not need to add the SGSN identifier; there is another possibility that the MTC server can obtain the SGSN identifier through other means, At this time, the SGSN may not add the SGSN identifier. In this way, the SGSN sends the second registration request message including the MTC terminal identification information, the IP address of the MTC GW and the location information of the MTC GW to the GGSN.

504. The GGSN obtains the first registration request message including the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information according to the second registration request message, and sends it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Specifically, if the MTC GW identification is the MTC GW identification number, the GGSN adds the GGSN identification to the second registration request message to obtain the first registration request message, and the GGSN will include the MTC terminal identification information, the MTC GW identification number, and the MTC GW location information , the first registration request message of the SGSN identifier and the GGSN identifier is sent to the MTC server. It can also be said that the first registration request message is obtained by the SGSN adding the SGSN identifier to the second registration request message, and the GGSN adding the GGSN identifier to the second registration request message.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can be addressed according to the IP address of the MTC GW, so the GGSN does not need to add the GGSN identifier. In this case, the first registration request message is the same as the second registration request message, and the GGSN sends the first registration request message including the MTC terminal identification information, the IP address of the MTC GW and the location information of the MTC GW to the MTC server. Another possible situation is that the MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

505. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information.

The MTC GW location information can be used as the MTC terminal location information, and the contract information saved by the MTC server is the MTC terminal’s contract information. If the MTC GW identifier is the MTC GW’s IP address, then the MTC GW’s IP address is used as the MTC terminal’s routing information. The MTC GW identification is the MTC GW identification number, and the first registration request message also includes at least one of the SGSN identification and the GGSN identification, so the MTC GW identification number, the SGSN identification and the GGSN identification are jointly used as the routing information of the MTC terminal.

506. The MTC server sends a registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the GGSN.

507. The GGSN forwards the registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the SGSN.

508. The SGSN sends a registration acceptance message including the MTC GW identifier and MTC terminal identification information to the MTC GW according to the MTC GW identifier.

509. The MTC GW forwards the registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

As another implementation, the SGSN can learn the location information of the MTC GW. For example, the SGSN can learn which RA or cell the message comes from according to the message sent by the MTC GW, so that the SGSN can obtain the location information of the MTC GW. In this case, in 502, the MTC GW may not add the MTC GW location information to the second registration request message, but in 503, the SGSN adds the MTC GW location information to the second registration request message.

Through the above registration process, the location information and routing information of the MTC terminal are reported to the MTC server, and the MTC server itself stores the subscription information of the MTC terminal. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 7 is a flow chart of a method for registering an MTC device according to Embodiment 7 of the present invention. In this embodiment, the MTC device includes an MTC terminal and an MTC GW, and the MTC terminal accesses the 3GPP network through the MTC GW, and the location information of the MTC device is specifically the location information of the MTC GW; the 3GPP network device may specifically include a GGSN; the first registration request message is 3GPP It is sent by the network device according to receiving the second registration request message sent by the MTC device in a user plane bearer manner.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The MTC terminal adds the subscription information to the registration request message and uploads it to the MTC server, that is, the first registration request message and the second registration request message. The registration request messages all include the subscription information of the MTC terminal. In this embodiment, before the MTC device registers, it is necessary to establish a user plane bearer between the MTC GW and the GGSN.

As shown in Figure 7, this embodiment includes the following parts:

601. The MTC terminal adds the MTC terminal identification information and the subscription information of the MTC terminal to the second registration request message, and sends it to the MTC gateway.

The subscription information of the MTC terminal may specifically include information such as a group identifier and/or a service type of the MTC terminal and/or a controllable time for data transmission.

602. The MTC GW adds the MTC GW identifier and the MTC GW location information to the second registration request message, encapsulates the content in the second registration request message into a data packet, and sends the second registration request message to the GGSN.

Wherein, the MTC GW identifier can specifically be the MTC GW identification number or the IP address of the MTC GW.

603. After receiving the second registration request message in the form of a data packet sent by the MTC GW, the GGSN obtains the first registration information including the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW location information according to the second registration request message. Registration request message, sent to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Specifically, if the MTC GW identifier is the MTC GW identification number, the GGSN will add the GGSN identifier to the second registration request message to obtain the first registration request message, and the GGSN will include the MTC terminal identification information, MTC terminal subscription information, MTC GW The first registration request message of the identification number, MTC GW location information and GGSN identifier is sent to the MTC server. It can also be said that the first registration request message is obtained by the GGSN adding the GGSN identifier to the second registration request message.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can be addressed according to the IP address of the MTC GW, so the GGSN does not need to add the GGSN identifier. In this case, the content of the first registration request message and the second registration request message are the same, and the GGSN will include the MTC terminal identification information, MTC terminal subscription information, MTC GW IP address and MTC GW location information in the first registration request The message is sent to the MTC server. Another possible situation is that the MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

604. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW location information.

The MTC GW location information can be used as the MTC terminal location information. If the MTC GW identification is the IP address of the MTC GW, then the MTC GW IP address is used as the routing information of the MTC terminal. If the MTC GW identification is the MTC GW identification number, the first registration The request message also includes the GGSN identifier, so the MTC GW identification number and the GGSN identifier are jointly used as the routing information of the MTC terminal.

605. The MTC server sends a registration acceptance message including the MTC GW identifier and MTC terminal identification information to the GGSN.

606. The GGSN sends the message content of the received registration acceptance message to the MTC GW through the user plane bearer according to the MTC GW identifier.

607. The MTC GW sends a registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

Through the above registration process, the location information, routing information and subscription information of the MTC terminal are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 8 is a flow chart of a method for registering an MTC device according to Embodiment 8 of the present invention. In this embodiment, the MTC device includes an MTC terminal and an MTC GW, and the MTC terminal accesses the 3GPP network through the MTC GW, and the location information of the MTC device is specifically the location information of the MTC GW; the 3GPP network device may specifically include a GGSN; the first registration request message is 3GPP It is sent by the network device according to receiving the second registration request message sent by the MTC device in a user plane bearer manner.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The difference from Embodiment 7 is that the GGSN obtains the subscription information from the HLR or other servers that store the subscription information of the MTC terminal. , add the subscription information to the second registration request message to obtain the first registration request message, and upload it to the MTC server. Before the MTC device registers, it is necessary to establish the user plane bearer between the MTC GW and the GGSN.

As shown in Figure 8, this embodiment includes the following parts:

701. The MTC terminal adds the MTC terminal identification information to the second registration request message, and sends it to the MTC gateway.

702. The MTC GW adds the MTC GW identifier and the MTC GW location information to the second registration request message, encapsulates the content in the second registration request message into a data packet, and sends the second registration request message to the GGSN.

Wherein, the MTC GW identifier can specifically be the MTC GW identification number or the IP address of the MTC GW.

703. After receiving the second registration request message in the form of a data packet sent by the MTC GW, the GGSN sends a subscription information request message to the HLR or other servers storing the subscription information.

704. The HLR or other servers send the subscription information of the MTC terminal to the GGSN according to the subscription information request message.

The subscription information may specifically include information such as group identifiers and/or service types of the MTC terminals and/or data sending controllable time.

705. The GGSN adds the received subscription information of the MTC terminal to the second registration request message to obtain the first registration request message, which will include the MTC terminal identification information, the MTC terminal subscription information, the MTC GW identifier, and the MTC GW location information. A registration request message is sent to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Specifically, if the MTC GW identifier is the MTC GW identification number, the GGSN will add the GGSN identifier to the second registration request message to obtain the first registration request message, and the GGSN will include the MTC terminal identification information, MTC terminal subscription information, and MTC GW identification information. No., MTC GW location information and the first registration request message identified by the GGSN are sent to the MTC server. It can also be said that the first registration request message is obtained by the GGSN adding the GGSN identifier to the second registration request message.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can be addressed according to the IP address of the MTC GW, so the GGSN does not need to add the GGSN identifier. The GGSN sends the first registration request message including the MTC terminal identification information, the subscription information of the MTC terminal, the IP address of the MTC GW and the location information of the MTC GW to the MTC server. Another possible situation is that the MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

706. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, MTC terminal subscription information, MTC GW identifier, and MTC GW location information.

The MTC GW location information can be used as the MTC terminal location information. If the MTC GW identification is the IP address of the MTC GW, then the MTC GW IP address is used as the routing information of the MTC terminal. If the MTC GW identification is the MTC GW identification number, the first registration The request message also includes the GGSN identifier, so the MTC GW identification number and the GGSN identifier are jointly used as the routing information of the MTC terminal.

707. The MTC server sends a registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the GGSN.

708. The GGSN sends the message content of the received registration acceptance message to the MTC GW through the user plane bearer according to the MTC GW identifier.

709. The MTC GW sends a registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

Through the above registration process, the location information, routing information and subscription information of the MTC terminal are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 9 is a flow chart of a registration method for a machine type communication device provided in Embodiment 9 of the present invention. In this embodiment, the MTC device includes an MTC terminal and an MTC GW, and the MTC terminal accesses the 3GPP network through the MTC GW, and the location information of the MTC device is specifically the location information of the MTC GW; the 3GPP network device may specifically include a GGSN; the first registration request message is 3GPP It is sent by the network device according to receiving the second registration request message sent by the MTC device in a user plane bearer manner.

Different from Embodiment 7 and Embodiment 8, the subscription information of the MTC terminal is stored in the MTC server, and there is no need to upload the subscription information. Before the MTC device registers, it is necessary to establish the user plane bearer between the MTC GW and the GGSN.

As shown in Figure 9, this embodiment includes the following parts:

801. The MTC terminal adds the MTC terminal identification information to the second registration request message, and sends it to the MTC gateway.

802. The MTC GW adds the MTC GW identifier and the MTC GW location information to the second registration request message, encapsulates the content in the second registration request message into a data packet, and sends the second registration request message to the GGSN.

Wherein, the MTC GW identifier can specifically be the MTC GW identification number or the IP address of the MTC GW.

803. After receiving the second registration request message in the form of a data packet sent by the MTC GW, the GGSN obtains the first registration request message including the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information according to the second registration request message, and sends it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Specifically, if the MTC GW identification is the MTC GW identification number, the GGSN will add the GGSN identification to the second registration request message to obtain the first registration request message, and the GGSN will include the MTC terminal identification information, the MTC GW identification number, and the MTC GW location The information and the first registration request message identified by the GGSN are sent to the MTC server. It can also be said that the first registration request message is obtained by the GGSN adding the GGSN identifier to the second registration request message.

If the MTC GW identifier is the IP address of the MTC GW, the MTC server can be addressed according to the IP address of the MTC GW, so the GGSN does not need to add the GGSN identifier. In this case, the contents of the first registration request message and the second registration request message are the same, and the GGSN sends the first registration request message including the MTC terminal identification information, the IP address of the MTC GW and the location information of the MTC GW to the MTC server. Another possible situation is that the MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

804. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, the MTC GW identifier, and the MTC GW location information.

The MTC GW location information can be used as the location information of the MTC terminal. If the MTC GW identification is the IP address of the MTC GW, then the MTC GW IP address is used as the routing information of the MTC terminal. If the MTC GW identification is the MTC GW identification number, the first The registration request message also includes the GGSN identifier, so the MTC GW identification number and the GGSN identifier are jointly used as the routing information of the MTC terminal.

805. The MTC server sends a registration acceptance message including the MTC GW identifier and the MTC terminal identification information to the GGSN.

806. The GGSN sends the message content of the received registration acceptance message to the MTC GW through the user plane bearer according to the MTC GW identifier.

807. The MTC GW sends the registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

Through the above registration process, the location information and routing information of the MTC terminal are reported to the MTC server, and the MTC server itself stores the subscription information of the MTC terminal. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 10 is a flow chart of a registration method for a machine type communication device provided by Embodiment 10 of the present invention. In this embodiment, the MTC device includes an MTC terminal, and the MTC terminal is directly connected to the 3GPP network, and the location information of the MTC device is specifically the location information of the MTC terminal; the 3GPP network device may specifically include an SGSN and a GGSN; the first registration request message is a 3GPP network device according to It is sent by receiving the second registration request message sent by the MTC terminal in a signaling manner.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The MTC terminal adds the subscription information to the registration request message and uploads it to the MTC server, that is, the first registration request message and the second registration request message. The registration request messages all include the subscription information of the MTC terminal.

As shown in Figure 10, this embodiment includes the following parts:

901. The MTC terminal adds the MTC terminal identification information, the MTC terminal location information, and the MTC terminal subscription information to the second registration request message, and sends the second registration request message to the SGSN through signaling.

The location information of the MTC terminal may specifically be at least one of an identifier of an RA where the MTC terminal is located and an identifier of a cell.

The subscription information of the MTC terminal may specifically include information such as a group identifier and/or a service type of the MTC terminal and/or a controllable time for data transmission.

902. The SGSN sends the second registration request message including the identification information of the MTC terminal, the subscription information of the MTC terminal, and the location information of the MTC terminal to the GGSN.

Optionally, the second registration request message may also include an SGSN identifier, and the SGSN may add the SGSN identifier to the second registration request message. The SGSN sends the second registration request message including the MTC terminal identification information, the MTC terminal subscription information, the MTC terminal location information and the SGSN identifier to the GGSN. The MTC server may obtain the SGSN identifier through other means, and at this time, the SGSN may not add the SGSN identifier.

903. The GGSN obtains the first registration request message including the identification information of the MTC terminal, the subscription information of the MTC terminal, and the location information of the MTC terminal according to the second registration request message, and sends it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. The GGSN sends the first registration request message including the MTC terminal identification information, the subscription information of the MTC terminal, the location information of the MTC terminal, the SGSN identifier and the GGSN identifier to the MTC server. The MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

904. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, the MTC terminal location information, and the MTC terminal subscription information.

905. The MTC server sends a registration acceptance message including the identification information of the MTC terminal to the GGSN.

906. The GGSN forwards the registration acceptance message including the MTC terminal identification information to the SGSN.

907. The SGSN sends the registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

As another embodiment, the SGSN can obtain the location information of the MTC terminal. For example, the SGSN can know which RA or cell the message comes from according to the message sent by the MTC terminal, so that the SGSN can obtain the location information of the MTC terminal. In this case, in 901, the MTC terminal may not add the MTC terminal location information to the second registration request message, but in 902, the SGSN adds the MTC terminal location information to the second registration request message.

Through the above registration process, the MTC terminal location information, subscription information and routing information (at least one of the MTC terminal identification information, SGSN identifier and GGSN identifier) are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 11 is a flow chart of a method for registering a machine type communication device according to Embodiment 11 of the present invention. In this embodiment, the MTC device includes an MTC terminal, and the MTC terminal is directly connected to the 3GPP network, and the location information of the MTC device is specifically the location information of the MTC terminal; the 3GPP network device may specifically include an SGSN and a GGSN; the first registration request message is a 3GPP network device according to It is sent by receiving the second registration request message sent by the MTC terminal in a signaling manner.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The difference from Embodiment 10 is that the SGSN or GGSN obtains the subscription information of the MTC terminal from the HLR or other servers. The subscription information is added to the second registration request message to obtain the first registration request message, and uploaded to the MTC server.

As shown in Figure 11, this embodiment includes the following parts:

1001. The MTC terminal adds the MTC terminal identification information and the MTC terminal location information to the second registration request message, and sends the second registration request message to the SGSN through signaling.

The location information of the MTC terminal may specifically be at least one of an identifier of an RA where the MTC terminal is located and an identifier of a cell.

1002. The SGSN sends a second registration request message including the identification information of the MTC terminal and the location information of the MTC terminal to the GGSN.

Optionally, the second registration request message may also include an SGSN identifier, and the SGSN may add the SGSN identifier to the second registration request message. The SGSN sends the second registration request message including the MTC terminal identification information, the MTC terminal location information and the SGSN identifier to the GGSN. The MTC server may obtain the SGSN identifier through other means, and at this time, the SGSN may not add the SGSN identifier.

1003. After receiving the second registration request message, the GGSN sends a subscription information request message to the HLR or other servers storing the subscription information.

1004. The HLR or other servers send the subscription information of the MTC terminal to the GGSN according to the subscription information request message.

The subscription information may specifically include information such as group identifiers and/or service types of the MTC terminals and/or data sending controllable time.

1005. The GGSN adds the received subscription information of the MTC terminal to the second registration request message to obtain the first registration request message, and sends the first registration request message including the identification information of the MTC terminal, the subscription information of the MTC terminal, and the location information of the MTC terminal Send it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. The GGSN sends the first registration request message including the MTC terminal identification information, the subscription information of the MTC terminal, the location information of the MTC terminal, the SGSN identifier and the GGSN identifier to the MTC server. The MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

1006. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, MTC terminal location information, and MTC terminal subscription information.

1007. The MTC server sends a registration acceptance message including the identification information of the MTC terminal to the GGSN.

1008. The GGSN forwards the registration acceptance message including the MTC terminal identification information to the SGSN.

1009. The SGSN sends a registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

As another embodiment, the SGSN can obtain the location information of the MTC terminal. For example, the SGSN can know which RA or cell the message comes from according to the message sent by the MTC terminal, so that the SGSN can obtain the location information of the MTC terminal. In this case, in 1001, the MTC terminal may not add the MTC terminal location information to the second registration request message, but in 1002, the SGSN adds the MTC terminal location information to the second registration request message.

Through the above registration process, the MTC terminal location information, subscription information and routing information (at least one of the MTC terminal identification information, SGSN identifier and GGSN identifier) are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 12 is a flow chart of a registration method for a machine type communication device provided in Embodiment 12 of the present invention. As shown in Figure 12, the difference between this embodiment and the above eleventh embodiment lies in 1002 to 1005, which can be replaced by:

1002'. After receiving the second registration request message sent by the MTC terminal, the SGSN sends a subscription information request message to the HLR or other servers storing the subscription information;

1003', HLR or other servers send the subscription information of the MTC terminal to the SGSN according to the subscription information request message;

1004', the SGSN adds the received subscription information of the MTC terminal to the second registration request message, and the SGSN sends the second registration request message including the identification information of the MTC terminal, the location information of the MTC terminal and the subscription information of the MTC terminal to the GGSN;

Optionally, the SGSN may add the SGSN identifier to the second registration request message, and related descriptions may refer to Embodiment 11.

1005', GGSN obtains the first registration request message including MTC terminal identification information, MTC terminal subscription information and MTC terminal location information according to the second registration request message, and sends the first registration request message to the MTC server.

Optionally, the GGSN may add the GGSN identifier to the second registration request message to obtain the first registration request message. For related descriptions, refer to Embodiment 11.

Through the registration process provided by this embodiment, the MTC terminal location information, subscription information and routing information (at least one of the MTC terminal identification information, SGSN identifier and GGSN identifier) are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 13 is a flow chart of a method for registering a machine type communication device according to Embodiment 13 of the present invention. In this embodiment, the MTC device includes an MTC terminal, and the MTC terminal is directly connected to the 3GPP network, and the location information of the MTC device is specifically the location information of the MTC terminal; the 3GPP network device may specifically include an SGSN and a GGSN; the first registration request message is a 3GPP network device according to It is sent by receiving the second registration request message sent by the MTC terminal in a signaling manner.

Different from Embodiment 10 and Embodiment 11, the subscription information of the MTC terminal is stored in the MTC server, and there is no need to upload the subscription information.

As shown in Figure 13, this embodiment includes the following parts:

1101. The MTC terminal adds the MTC terminal identification information and the MTC terminal location information to the second registration request message, and sends the second registration request message to the SGSN in a signaling manner.

The location information of the MTC terminal may specifically be at least one of an identifier of an RA where the MTC terminal is located and an identifier of a cell.

1102. The SGSN sends the second registration request message including the identification information of the MTC terminal and the location information of the MTC terminal to the GGSN.

Optionally, the second registration request message may also include an SGSN identifier, and the SGSN may add the SGSN identifier to the second registration request message. The SGSN sends the second registration request message including the MTC terminal identification information, the MTC terminal location information and the SGSN identifier to the GGSN. The MTC server may obtain the SGSN identifier through other means, and at this time, the SGSN may not add the SGSN identifier.

1103. The GGSN obtains the first registration request message including the MTC terminal identification information and the MTC terminal location information according to the second registration request message, and sends it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. The GGSN sends the first registration request message including the MTC terminal identification information, the MTC terminal location information, the SGSN identifier and the GGSN identifier to the MTC server. The MTC server may obtain the GGSN identifier through other means, and at this time, the GGSN may not add the GGSN identifier.

1104. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information and the MTC terminal location information.

1105. The MTC server sends a registration acceptance message including the identification information of the MTC terminal to the GGSN.

1106. The GGSN forwards the registration acceptance message including the identification information of the MTC terminal to the SGSN.

1107. The SGSN sends the registration acceptance message including the MTC terminal identification information to the MTC terminal according to the MTC terminal identification information.

As another embodiment, the SGSN can obtain the location information of the MTC terminal. For example, the SGSN can know which RA or cell the message comes from according to the message sent by the MTC terminal, so that the SGSN can obtain the location information of the MTC terminal. In this case, in 1101, the MTC terminal may not add the MTC terminal location information to the second registration request message, but in 1102, the SGSN adds the MTC terminal location information to the second registration request message.

Through the above registration process, the MTC terminal location information and routing information (at least one of the MTC terminal identification information, the SGSN identifier and the GGSN identifier) are reported to the MTC server. When the MTC server dispatches the MTC terminal in a network-triggered manner, the location information, routing information, and subscription information saved by the MTC server can be carried in the scheduling message, so that it can be routed to the MTC terminal and trigger the MTC terminal to send data , to ensure the normal operation of the MTC service.

FIG. 14 is a flow chart of a method for registering a machine type communication device according to Embodiment 14 of the present invention. In this embodiment, the MTC device includes an MTC terminal, and the MTC terminal is directly connected to the 3GPP network, and the location information of the MTC device is specifically the location information of the MTC terminal; the 3GPP network device may specifically include a GGSN; the first registration request message is that the 3GPP network device receives the MTC It is sent by the terminal through the second registration request message sent in a bearer mode on the user plane.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The MTC terminal adds the subscription information to the registration request message and uploads it to the MTC server, that is, the first registration request message and the second registration request message. The registration request messages all include the subscription information of the MTC terminal. In this embodiment, before the MTC terminal registers, it is necessary to establish a user plane bearer between the MTC terminal and the GGSN.

As shown in Figure 14, this embodiment includes the following parts:

1201. The MTC terminal adds the MTC terminal identification information, MTC terminal location information, and MTC terminal subscription information to the second registration request message, and sends the second registration request message to the GGSN in a user plane bearer manner.

The location information of the MTC terminal may specifically be at least one of an identifier of an RA where the MTC terminal is located and an identifier of a cell.

The subscription information of the MTC terminal may specifically include information such as a group identifier and/or a service type of the MTC terminal and/or a controllable time for data transmission.

1202. The GGSN obtains the first registration request message including the MTC terminal identification information, the MTC terminal location information, and the MTC terminal subscription information according to the second registration request message, and sends it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Wherein, the MTC terminal identification information and the GGSN identification are used as routing information.

Since the user plane bearer has been established, the MTC server can obtain routing information according to the user plane bearer, so the GGSN may not add the GGSN identifier, so that the first registration request message is the same as the second registration request message.

1203. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, the MTC terminal location information, and the MTC terminal subscription information.

1204. The MTC server sends a registration acceptance message including the identification information of the MTC terminal to the GGSN.

1205. The GGSN forwards the registration acceptance message including the identification information of the MTC terminal to the MTC terminal.

Through the above registration process, the MTC terminal location information and subscription information are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 15 is a flow chart of a registration method for a machine type communication device provided by Embodiment 15 of the present invention. In this embodiment, the MTC device includes an MTC terminal, and the MTC terminal is directly connected to the 3GPP network, and the location information of the MTC device is specifically the location information of the MTC terminal; the 3GPP network device may specifically include a GGSN; the first registration request message is that the 3GPP network device receives the MTC It is sent by the terminal through the second registration request message sent in a bearer mode on the user plane.

Specifically, the subscription information of the MTC terminal is stored in the HLR or other servers, but not in the MTC server. The difference from Embodiment 14 is that the GGSN obtains the subscription information from the HLR or other servers that store the subscription information of the MTC terminal. Information, add the subscription information to the second registration request message to obtain the first registration request message, and upload it to the MTC server.

As shown in Figure 15, this embodiment includes the following parts:

1301. The MTC terminal adds the MTC terminal identification information and the MTC terminal location information to the second registration request message, and sends the second registration request message to the GGSN in a user plane bearer manner.

The location information of the MTC terminal may specifically be at least one of an identifier of an RA where the MTC terminal is located and an identifier of a cell.

1302. After receiving the second registration request message, the GGSN sends a subscription information request message to the HLR or other servers storing the subscription information.

1303. The HLR or other servers send the subscription information of the MTC terminal to the GGSN according to the subscription information request message.

The subscription information may specifically include information such as group identifiers and/or service types of the MTC terminals and/or data sending controllable time.

1304. The GGSN adds the received subscription information of the MTC terminal to the second registration request message to obtain the first registration request message, and sends the first registration request message including the MTC terminal identification information, the MTC terminal location information, and the MTC terminal subscription information Send it to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Wherein, the MTC terminal identification information and the GGSN identification are used as routing information.

Since the user plane bearer has been established, the MTC server can obtain routing information according to the user plane bearer, so the GGSN does not need to add the GGSN identifier.

1305. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information, the MTC terminal location information, and the MTC terminal subscription information, and optionally, the GGSN identifier.

1306. The MTC server sends a registration acceptance message including the identification information of the MTC terminal to the GGSN.

1307. The GGSN forwards the registration acceptance message including the identification information of the MTC terminal to the MTC terminal.

Through the above registration process, the MTC terminal location information and subscription information are reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 16 is a flow chart of a method for registering an MTC device according to Embodiment 16 of the present invention. In this embodiment, the MTC device includes an MTC terminal, and the MTC terminal is directly connected to the 3GPP network, and the location information of the MTC device is specifically the location information of the MTC terminal; the 3GPP network device may specifically include a GGSN; the first registration request message is that the 3GPP network device receives the MTC It is sent by the terminal through the second registration request message sent in a bearer mode on the user plane.

Different from Embodiment 14 and Embodiment 15, the subscription information of the MTC terminal is stored in the MTC server, and there is no need to upload the subscription information.

As shown in Figure 16, this embodiment includes the following parts:

1401. The MTC terminal adds the MTC terminal identification information and the MTC terminal location information to the second registration request message, and sends the second registration request message to the GGSN in a user plane bearer manner.

The location information of the MTC terminal may specifically be at least one of an identifier of an RA where the MTC terminal is located and an identifier of a cell.

1402. The GGSN obtains the first registration request message including the MTC terminal identification information and the MTC terminal location information according to the second registration request message, and sends the message to the MTC server.

Optionally, the first registration request message may also include a GGSN identifier, and the GGSN may add the GGSN identifier to the second registration request message, thereby obtaining the first registration request message. Wherein, the MTC terminal identification information and the GGSN identification are used as routing information.

Since the user plane bearer has been established, the MTC server can obtain routing information according to the user plane bearer, so the GGSN may not add the GGSN identifier, so that the first registration request message is the same as the second registration request message.

1403. After receiving the first registration request message sent by the GGSN, the MTC server saves the MTC terminal identification information and the MTC terminal location information, and optionally, the GGSN identifier.

1404. The MTC server sends a registration acceptance message including the identification information of the MTC terminal to the GGSN.

1405. The GGSN forwards the registration acceptance message including the identification information of the MTC terminal to the MTC terminal.

Through the above registration process, the location information of the MTC terminal is reported to the MTC server. When the MTC server schedules the MTC terminal in a network-triggered manner, it can carry the location information, routing information and subscription information of the MTC terminal in the scheduling message, so that it can route to the MTC terminal, trigger the MTC terminal to send data, and ensure the MTC service of normal operation.

FIG. 17 is a schematic structural diagram of a machine type communication server provided by Embodiment 17 of the present invention. As shown in Figure 17, this embodiment specifically includes: a receiving module 11 and a sending module 12, wherein:

The receiving module 11 is configured to receive a first registration request message sent by a 3GPP network device, the first registration request message including MTC terminal identification information; wherein, the first registration request message is the MTC device corresponding to the received MTC terminal identification information of the 3GPP network device Sent by the second registration request message sent, the second registration request message includes the MTC terminal identification information;

The sending module 12 is configured to return a registration acceptance message to the MTC device through the 3GPP network device according to the first registration request message, and the registration acceptance message includes MTC terminal identification information.

For the implementation process of the specific functions of the modules of the MTC server provided in this embodiment, reference may be made to the foregoing method embodiments, and details are not repeated here.

FIG. 18 is a schematic structural diagram of a machine-type communication device provided by Embodiment 18 of the present invention. As shown in Figure 18, this embodiment specifically includes: a sending module 21 and a receiving module 22, wherein:

The sending module 21 is configured to send a second registration request message to the 3GPP network device, the second registration request message including MTC terminal identification information, for the 3GPP network device to send the first registration request message to the MTC server according to the second registration request message, the The first registration request message includes MTC terminal identification information and MTC device location information;

The receiving module 22 is configured to receive a registration acceptance message, and the registration acceptance message includes MTC terminal identification information.

The sending module 21 is specifically configured to send the second registration request message to the 3GPP network device through signaling; or send the second registration request message to the 3GPP network device through the user plane bearer method.

For the implementation process of the specific functions of each module of the MTC device provided in this embodiment, reference may be made to the foregoing method embodiments, and details are not repeated here.

FIG. 19 is a schematic structural diagram of a registration system for a machine type communication device provided by Embodiment 19 of the present invention. As shown in Figure 19, this embodiment specifically includes: MTC equipment 31, 3GPP network equipment 32 and MTC server 33, wherein:

The MTC device 31 is configured to send a second registration request message, the second registration request message includes MTC terminal identification information; receive a registration acceptance message, the registration acceptance message includes the MTC terminal identification information;

The 3GPP network device 32 is configured to receive the second registration request message sent by the MTC device 31, and send a first registration request message according to the second registration request message, where the first registration request message includes the MTC terminal identification information; forward the received registration acceptance message to the MTC device 31;

The MTC server 33 is configured to receive the first registration request message sent by the 3GPP network device 32; and send a registration acceptance message to the 3GPP network device 32 according to the first registration request message.

For the realization process of the specific functions of each device in the registration system of the machine type communication device provided in this embodiment, reference may be made to the above-mentioned method embodiments, and details will not be repeated here.

The various devices provided by the embodiments of the present invention enable the network side to know the information of the MTC terminal in the 3GPP network, such as the location of the MTC terminal, and the network side can trigger the MTC terminal to send data in a network-triggered manner according to the information to ensure the MTC service of normal operation.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the The steps of the above-mentioned method embodiments are included, and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, not to limit them; although the embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand : It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical aspects of the embodiments of the present invention. The spirit and scope of the programme.

Claims (9)

1. A registration method of a machine type communication device, characterized in that, comprising: Receiving a first registration request message sent by a 3GPP network device, the first registration request message including MTC terminal identification information, wherein the first registration request message is the corresponding MTC terminal identification information of the 3GPP network device according to receiving the MTC terminal identification information The second registration request message sent by the MTC device, the second registration request message includes the MTC terminal identification information; the first registration request message also includes the MTC device location information; the MTC device includes the MTC terminal and MTC gateway, the location information of the MTC device is the location information of the MTC gateway, the first registration request message and the second registration request message also include the MTC gateway identifier, and the registration acceptance message also includes the MTC gateway identifier; or, the MTC The equipment includes an MTC terminal, and the location information of the MTC equipment is the location information of the MTC terminal; According to the first registration request message, return a registration acceptance message to the MTC device through the 3GPP network device, where the registration acceptance message includes the MTC terminal identification information. the 2. The registration method of the machine type communication device according to claim 1, wherein the 3GPP network device includes SGSN and GGSN; The first registration request message is sent by the 3GPP network device according to receiving the second registration request message sent by the MTC device through signaling; When the MTC device includes an MTC terminal and an MTC gateway, the MTC gateway identifier is added by the MTC gateway to the second registration request message, and the MTC gateway location information is the MTC gateway or the SGSN added to the second registration request message; When the MTC device includes an MTC terminal, the MTC terminal location information is added by the MTC terminal or the SGSN to the second registration request message. the 3. The registration method of the machine type communication device according to claim 1, wherein the 3GPP network device comprises a GGSN; The first registration request message is sent by the 3GPP network device according to receiving the second registration request message sent by the MTC device through the user plane bearer mode; When the MTC device includes an MTC terminal and an MTC gateway, the MTC gateway identifier and the MTC gateway location information are added by the MTC gateway to the second registration request message; When the MTC device includes an MTC terminal, the MTC terminal location information is added by the MTC terminal to the second registration request message. the 4. The registration method of the machine type communication device according to claim 2 or 3, characterized in that: The first registration request message and the second registration request message also include the subscription information of the MTC terminal, and the subscription information of the MTC terminal is added by the MTC terminal to the second registration request message; Alternatively, the first registration request message further includes the subscription information of the MTC terminal, the first registration request message is that the GGSN acquires the subscription information of the MTC terminal from a server storing the subscription information, and the The subscription information of the MTC terminal is added to the second registration request message. the Alternatively, the first registration request message further includes the subscription information of the MTC terminal, the first registration request message is that the SGSN obtains the subscription information of the MTC terminal from a server storing the subscription information, and the The subscription information of the MTC terminal is added to the second registration request message. the 5. The method for registering an MTC device according to claim 2, wherein the first registration request message further includes at least one of an SGSN identifier and a GGSN identifier. the 6. The method for registering an MTC device according to claim 3, wherein the first registration request message further includes a GGSN identifier. the 7. The registration method of a machine type communication device according to claim 1, wherein the first registration request message and the second registration request message further include an MTC server address. the 8. The registration method of a machine type communication device according to claim 1, wherein the MTC gateway location information includes at least one of the location area RA identifier where the MTC gateway is located and the cell identifier where the MTC gateway is located The MTC terminal location information includes at least one of the location area RA identifier where the MTC terminal is located and the cell identifier where the MTC terminal is located. the 9. A registration system for machine-type communication equipment, characterized in that it includes: The MTC device is configured to send a second registration request message, where the second registration request message includes MTC terminal identification information; receive a registration acceptance message, where the registration acceptance message includes the MTC terminal identification information; A 3GPP network device, configured to receive the second registration request message sent by the MTC device, and send a first registration request message according to the second registration request message, where the first registration request message includes MTC terminal identification information; The received registration acceptance message is forwarded to the MTC device; The MTC server is configured to receive the first registration request message sent by the 3GPP network device; send the registration acceptance message to the 3GPP network device according to the first registration request message; the first registration request message Also includes MTC device location information; the MTC device includes an MTC terminal and an MTC gateway, the MTC device location information is MTC gateway location information, and the first registration request message and the second registration request message also include an MTC gateway identifier , the registration acceptance message further includes an MTC gateway identifier; or, the MTC device includes an MTC terminal, and the location information of the MTC device is the location information of the MTC terminal. the

Images