WO2011082524A1

WO2011082524A1 - Method and system for machine-to-machine data transmission, and mobility management entity device

Info

Publication number: WO2011082524A1
Application number: PCT/CN2010/070049
Authority: WO
Inventors: 陈中平; 吴问付
Original assignee: 华为技术有限公司
Priority date: 2010-01-07
Filing date: 2010-01-07
Publication date: 2011-07-14
Also published as: CN102754472B; CN102754472A

Abstract

The invention relates to a method and system for machine-to-machine data transmission, and a Mobility Management Entity (MME) device. The method comprises: receiving an access request from a low data stream terminal; establishing a signaling connection from a Mobility Management Entity to a gateway equipment for the low data stream terminal; transmitting the data information of the low data stream terminal through the established signaling connection.

Description

Machine-to-machine data transmission method, system and mobility management network element device

The present invention relates to the field of machine-to-machine communication technology, and in particular, to a machine-to-machine data transmission method, system, and mobility management network element device. Background technique

Machine-to-machine (M2M) technology integrates communication and network technologies to connect machines and devices that are spread throughout people's daily lives into a network, making these devices more "smart" and thus creating rich Application brings a new round of changes to the way of daily life, industrial production and so on.

In M2M communication, the mobile network has become the most widely distributed and most promising technology for M2M information transmission and transmission because it does not need to be wired and has a wide coverage. Among them, Global System for Mobile Communications (GSM)/General Packet Radio Service (GPRS) I Universal Mobile Telecommunications System (UMTS) / Long Term Evolution (LTE) ) is the main long-distance connection technology in M2M communication. A machine type communication device (hereinafter referred to as a " Type2Μ terminal") is connected to a machine type communication server (Machine Type Communications Server, hereinafter referred to as an MTC server) through a carrier network, where the operator's network may be an LTE network. . The M2M terminal is different from the traditional human to human (H2H) terminal, and the application is relatively simple. In addition, the M2M terminal and the network interaction traffic are relatively small, and the interaction may be bursty, such as the current electronic meter reading service. We refer to this type of M2M terminal as a Low Data Usage terminal or a Small Data Transmissions terminal.

In the prior art, an LTE network is used as the M2M communication of the long-distance connection technology, and the MTC terminal device performs data transmission by means of bearer. In order to guarantee data transmission, LTE network needs Create a corresponding bearer for data transmission for the M2M terminal, and reserve data for the corresponding resource. That is, each terminal needs to activate the bearer in order to transmit data.

Since the number of M2M terminals is large, and the amount of data transmitted by each M2M terminal in one transmission is small, the use of bearer transmission data will occupy a large amount of network resources. Summary of the invention

The embodiment of the invention provides a machine-to-machine data transmission method and system, and a mobility management network element device, which uses the signaling plane to transmit data information of the M2M terminal, and occupies less network resources.

Embodiments of the present invention provide a machine-to-machine data transmission method, including:

An access request of a terminal receiving a low data stream;

Establishing a signaling connection from the mobility management network element to the gateway device for the terminal of the low data stream; and transmitting, by using the established signaling connection, the data information of the terminal of the low data stream. The embodiment of the invention further provides a mobility management network element device, including:

a receiving module, configured to receive an access request of a terminal with a low data stream;

a connection establishing module, configured to establish, after the receiving module receives the access request of the terminal of the low data stream, a signaling connection from the mobility management network element to the gateway device for the terminal of the low data flow;

And a transmission module, configured to transmit data information of the terminal of the low data stream by using a signaling connection established by the connection establishment module.

The embodiment of the present invention further provides a machine-to-machine data transmission system, including: a mobility management network element, configured to receive an access request of a terminal of a low data flow, and provide a service to a terminal that is the low data flow. The gateway device sends an association establishment request to establish a signaling connection between the mobility management network element and the gateway device, and transmits data information of the terminal of the low data flow through the established signaling connection;

The gateway device is configured to receive an association establishment request sent by the mobility management network element, and establish a signaling connection of the mobility management network element to the gateway device for the terminal of the low data flow. The embodiment of the invention further provides a terminal, including:

a sending unit, configured to send an access request to the mobility management network element;

a receiving unit, configured to receive an access response sent by the mobility management network element, where the access response includes a packet data network identifier PDN ID used in a signaling connection between the established mobility management network element and the gateway device. Information: or the access request response includes indication information for indicating that the terminal of the low data stream transmits data by signaling. DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings to be used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying creative labor.

1 is a flowchart of a data transmission method of a machine to a machine according to an embodiment of the present invention; FIG. 2A is a schematic diagram of an M2M communication network applied to a data transmission method of a machine to a machine according to an embodiment of the present invention;

2B is a schematic diagram of a carrier network in FIG. 2A;

3 is a schematic diagram of a terminal and a network element structure involved in a data transmission method of a machine to a machine according to an embodiment of the present invention;

4 is a signaling flowchart of establishing a signaling connection in a machine-to-machine data transmission method according to an embodiment of the present invention;

FIG. 5 is another signaling flowchart of establishing a signaling connection in a machine-to-machine data transmission method according to an embodiment of the present invention;

6 is a signaling flowchart of a data transmission process of a calling process in a machine-to-machine data transmission method according to an embodiment of the present invention;

FIG. 7 is a signaling flowchart of a called process transmission data in a machine-to-machine data transmission method according to an embodiment of the present invention; FIG. 8 is another signaling flowchart of data transmission by a calling process in a machine-to-machine data transmission method according to an embodiment of the present invention; FIG.

FIG. 9 is another signaling flowchart of a called process transmission data in a machine-to-machine data transmission method according to an embodiment of the present invention;

FIG. 10 is a signaling flowchart of transmitting alarm information in a machine-to-machine data transmission method according to an embodiment of the present invention;

Figure 11 is a schematic structural diagram of a mobility management network element device according to an embodiment of the present invention; Figure 12 is a schematic structural diagram of a device-to-machine data transmission system according to an embodiment of the present invention; Schematic. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a flowchart of a method for data transmission from a machine to a machine according to an embodiment of the present invention. The method includes:

Step 11. Receive an access request of the terminal with a low data stream.

The step may be performed by a mobility management network element, and the terminal may be a terminal of a low data stream, such as an M2M terminal. The access request may be an Attach Request or a PDN Connectivity Request. The mobility management network element receives an attach request message or a connection establishment request message sent by the M2M terminal.

The mobility management network element may be a Mobility Management Entity (ΜΜΕ) or a Serving GPRS Support Node (SGSN).

Step 12: Establish a letter from the mobility management network element to the gateway device for the terminal of the low data stream Make a connection;

The step may be performed by the mobility management network element. For example, after receiving the attach request message initiated by the M2M terminal, the mobility management network element initiates a signaling connection procedure for the M2M terminal to establish a gateway device to provide data transmission for the M2M terminal. Transmission channel.

And establishing, by the terminal of the low data flow, a signaling connection of the mobility management network element to the gateway device, including:

Obtaining a gateway device serving the terminal of the low data stream; initiating an association establishment request to the gateway device to establish a signaling connection between the mobility management network and the gateway device.

The initiating an association establishment request to the gateway device includes:

And in the case that the access request message includes indication information indicating that the terminal of the low data flow is a low data service type, initiating an association establishment request to the gateway device; or

In the case that the acquired subscription data includes indication information indicating that the terminal of the low data stream is a low data service type, an association establishment request is initiated to the gateway device.

Step 13. The data information of the terminal of the low data stream is transmitted through the established signaling connection.

The step is performed by the mobility management network element. For example, in the calling process, the mobility management network element receives the uplink data transmission message sent by the M2M terminal, and sends the uplink data to the MTC server through the established signaling connection.

The transmitting, by using the established signaling connection, the data information of the terminal of the low data stream includes:

(1) receiving an uplink non-access stratum service (NAS) transmission message including packet data network (PDN) ID information and machine type communication data in the form of an IP packet; according to the PDN ID information acquiring a gateway device serving the terminal of the low data stream; transmitting, by the signaling connection, machine type communication data in the form of the IP data packet to the gateway device, so that the gateway device will use the IP address Machine type communication data in the form of a packet is routed to the MTC server; or (2) receiving an uplink NAS transmission message including PDN ID information, destination address indication information, and machine type communication data; obtaining, by the PDN ID information, a gateway device of a terminal serving the low data stream; using the signaling connection Transmitting the machine type communication data to the gateway device, so that the gateway device assembles the machine type communication data into an IP data packet and routes to an MTC server; wherein a source address of the IP data packet is established from Obtaining in a context created during a signaling connection; the destination address of the IP data packet is obtained according to the destination address indication information; or

(3) receiving the machine type communication data in the form of an IP data packet sent by the gateway device, where the machine type communication data in the form of an IP data packet is sent by the MTC server to the gateway device; Transmitting, by the management network element, the machine type communication data in the form of an IP data packet to the terminal of the low data stream; or

(4) receiving a data packet identifiable by the terminal of the low data stream sent by the gateway device, where the data packet identifiable by the terminal of the low data stream is an IP sent by the gateway device according to the MTC server Obtained after reassembling the machine type communication data in the form of a packet; transmitting the data packet identifiable by the machine to the machine terminal to the terminal of the low data stream; or

(5) transmitting, when the terminal of the low data stream is abnormal, the abnormal information of the terminal of the low data flow to the gateway device by using the established signaling connection, so that the gateway device The abnormality information of the terminal of the low data stream is sent to the MTC server.

The technical solution provided by the embodiment provides a signaling connection and uses the established signaling connection to transmit data, thereby avoiding allocating network bearers to a large number of M2M terminals, and solving an M2M terminal having a low data flow application characteristic, such as an M2M terminal. The problem of large consumption and occupation of network resources improves data transmission efficiency and ensures the normal operation of H2H services.

2A is a schematic diagram of an M2M communication network applied to a machine-to-machine data transmission method according to an embodiment of the present invention. As shown in FIG. 2A, a plurality of MTC devices 21 communicate with the MTC server 22 via an operator network, including the transmission of data. Among them, the MTC device is the end of M2M 2B is a schematic diagram of the carrier network of FIG. 2A. The carrier network may be an LTE network, and mainly includes an MME 23, a Serving Gateway (S-GW), that is, an S-GW 24, and a Packet Data Network Gateway (PDN-GW), that is, a P-GW. -GW 25 Three logical functions. The MME has the functions of NAS signaling encryption, roaming, tracking, assigning user temporary identity, security functions, and the like, and corresponds to the control plane part of the current Servicing GPRS Support Node (SGSN) of the UMTS system. The S-GW is responsible for the local mobility anchor and the mobility anchor inside the 3GPP system and the lawful interception related information; the P-GW has the functions of policy enforcement and charging and lawful interception.

The embodiment of the present invention relates to an architecture diagram, as shown in FIG. 3, including: an MTC device 31, an access network 32, a mobility management network element 33, an HSS 34, a gateway device 35, and an MTC server 36. The mobility management network element 33 may be an MME or an SGSN, and may be used to establish a signaling connection between the mobility management network element 33 and the gateway device 35 for the MTC device 31, and the data transmission involving the MTC device 31 may be established. The signaling connection is made.

The signaling connection can be established in the attach procedure initiated by the MTC terminal or in the connection setup request procedure. The following is explained separately based on different processes.

A flowchart of establishing a signaling connection in an attaching process is shown in FIG. 4. FIG. 4 is a signaling flowchart of establishing a signaling connection in a machine-to-machine data transmission method according to an embodiment of the present invention. The process of establishing a signaling connection specifically includes:

Step 41: The M2M terminal sends an attach request (Attach Request) message to the mobility management network element. Here, the mobility management network element may be an SGSN or an MME. The indication request message may carry the indication information "Low Data Usage Indication" or "Online/Offline Small Data Transmission Indication", and the indication information indicates that the type of the M2M terminal is a low data service type, such as a low data traffic application or a small data transmission. (Small Data Transmissions) type.

Step 42: Perform an authentication process between the M2M terminal, the mobility management network element, and the HSS.

Step 43: The mobility management network element sends an Update Location Request message to the HSS. The update location request message includes M2M terminal identification information and mobility tube The physical network element identification information is SGSN Number or MME ID. The identifier information of the M2M terminal is at least one of the IMSI and the IMEI, and is used to uniquely identify the M2M terminal.

Step 44: The HSS returns an Update Location Ack message to the mobility management network element. The update location confirmation message carries the subscription data of the M2M terminal. The subscription data includes the default APN information and the default PDN subscription context. ₀ For the low data service type terminal, the M2M terminal's subscription data can indicate that the MTC feature is a low data service type. The mobility management network element can learn that the M2M terminal has the characteristics of a low data service type according to the obtained subscription data.

After receiving the subscription data, the mobility management network element initiates a signaling connection establishment process.

Step 45: The mobility management network element selects a gateway device for serving the M2M terminal, and saves information of the selected gateway device.

The mobility management network element may select the gateway device according to the APN information included in the subscription data, for example, obtain the IP address information of the gateway through the APN for DNS resolution, or may also sign the gateway device address according to the PDN subscription context associated with the APN information. Information selection gateway device.

The gateway device can be a Gateway GPRS Support Node (GGSN) or a P-GW. If it is a P-GW, the mobility management device also needs to select the S-GW. Of course, the S-GW can be physically integrated with the P-GW.

Step 46: The mobility management network element initiates an association establishment request to the selected gateway device, and establishes an association between the M2M terminal and the gateway device serving the M2M terminal, that is, a signaling connection.

For example, the mobility management network element sends a Create Binding Request message to the selected gateway device. If the S-GW exists, the Create Binding Request message is forwarded to the P-GW through the S-GW. The creating a binding request message may include at least one of the identification information of the M2M terminal, the APN information, the mobility management network element identification information, and the address information of the mobility management network element. The binding request message may also carry the indication information of the low data traffic application feature to indicate that the current signaling connection of the relevant network element such as the gateway device is used to deliver the low data flow service data.

The creation of the binding request message may further include PDN identification (ID) information, the PDN ID information. Uniquely corresponds to the obtained default APN.

Step 47: After receiving the binding request message, the gateway device creates a context for the M2M terminal. The terminal identification information of the M2M terminal, the mobility management network element information of the service M2M terminal, and the IP address information allocated to the M2M terminal may be saved in the context. The mobility management network element information includes at least one of identifier information of the mobility management network element and address information of the mobility management network element.

The gateway device may also select the MTC server address information according to the Access Point Name (APN) information included in the Create Binding Request message, for example, the gateway device may obtain the corresponding list according to the stored APN information and the MTC server address. The address of the MTC server corresponding to the APN; or, the gateway device can obtain the address of the MTC server by performing DNS resolution on the APN information.

Step 48: The gateway device returns a Create Binding Response message to the mobility management network element. The binding response message carries the IP address information assigned to the M2M terminal, that is, the IP address of the current PDN of the M2M terminal, corresponding to the current APN. The Create Binding Response message can also carry the MTC server address information configured by the gateway device.

Step 49: After receiving the binding response message, the mobility management network element completes establishment of an association between the mobility management network element of the M2M terminal and the gateway. The mobility management network element sends an Attach Accept message to the M2M terminal.

After the mobility management network element completes the establishment of the association between the mobility management network element of the M2M terminal and the gateway, the M2M terminal transmits the data packet to the mobility management network element, and the mobility management network element can be established. The association transmits the data packet to the gateway device; or the gateway device can send the downlink data packet to the mobility management network element by using the established association, and the mobility management network element sends the downlink data packet to the M2M terminal.

The attach accept message sent by the mobility management network element to the M2M terminal carries the default APN information and the IP address information allocated by the gateway device to the M2M terminal. The attach accept message may also carry a PDN ID information to identify the current PDN connection. The PDN ID information and the APN unique pair Should. The attach accept message may further carry an indication information for instructing the M2M terminal to perform network optimization based on the low data stream service. Specifically, the indication information may indicate that the terminal transmits data through NAS signaling instead of transmitting data through the bearer.

During the attaching process, the M2M terminal can obtain the MTC server address information, and the server corresponding to the MTC server address information is the MTC server that the M2M terminal needs to send data.

For example, the MTC server address information obtained by the mobility management network element from the subscription data of the M2M terminal may be sent to the M2M terminal through an attach accept message, or may be sent to the M2M terminal through other messages. The MTC server address information is signed in the subscription data. The address information can be either IP address information or a Fully Qualified Domain Name (FQDN). The mobility management NE obtains the MTC server address through DNS resolution.

Alternatively, if the gateway device sends the MTC server address information to the mobility management network element, the mobility management network element sends the message to the M2M terminal through the attach accept message, and may also send the message to the M2M terminal through other messages. In particular, the MTC server address information can be stored in a special cell PCO. This cell is only transmitted between the M2M terminal and the gateway device, transparent to the mobility management network element, and the mobility management network element is not parsed. At the same time, the IP address information assigned by the gateway device to the M2M terminal is also transmitted in the PCO, which is transparent to the mobility management network element.

The address information of the MTC server may be based on the granularity of the APN, or may be independent of the APN, and is not limited herein.

A flowchart for establishing a signaling connection in the connection establishment request flow is shown in FIG. 5. FIG. 5 is another signaling flow diagram of establishing a signaling connection in a machine-to-machine data transmission method according to an embodiment of the present invention. The process of establishing a signaling connection includes:

Step 51: The M2M terminal sends a connection establishment request (PDN Connectivity Request) to the mobility management network element. The connection establishment request message may carry the APN information, and may also carry indication information such as "Low Data Usage Indication", "Online/Offline Small Data Transmissions Indication", etc., the indication information indicating that the type of the M2M terminal is a low data service type, Such as low data traffic applications or small data transmission type terminals. Step 52: The mobility management network element learns from the subscription data acquired by the HSS that the M2M terminal has low data traffic application characteristics. Or, when the indication information is carried in the attach request message, the mobility management network element can obtain the signaling connection establishment procedure after the M2M terminal has the low data traffic application characteristic by using the attach request message.

Step 53: The mobility management network element selects a gateway device for serving the M2M terminal, and saves information of the selected gateway device. For example, the gateway device is selected according to the APN information requested by the UE, for example, the IP address information of the gateway is obtained through DNS resolution by the APN; or the gateway device is selected according to the signed gateway device address information in the PDN subscription information associated with the APN. The mobility management network element is required.

The gateway device may be a GGSN or a P-GW. If it is a P-GW, the mobility management device also needs to select the S-GW. Of course, the S-GW may be physically integrated with the P-GW.

Step 54: The mobility management network element initiates an association establishment request to the selected gateway device, and establishes an association between the M2M terminal and the gateway device serving the M2M terminal, that is, a signaling connection.

For example, the mobility management network element sends a create binding request message to the selected gateway device. If there is an S-GW, the Create Binding Request message is forwarded to the P-GW through the S-GW. The create binding request message may carry terminal identification information, APN information, and a mobility management network element identification letter. The binding request message may also carry the indication information of the low data traffic application feature to indicate that the current signaling connection of the relevant network element such as the gateway device is used to deliver the low data flow service data.

The PDN ID (ID) information may also be included in the Create Binding Request message to identify the current PDN connection. The PDN is created according to the acquired APN, and the PDN ID information uniquely corresponds to the APN.

Step 55: After receiving the create binding request message, the gateway device creates a context for the M2M terminal. The terminal identification information of the M2M terminal, the mobility management network element information of the service M2M terminal, the IP address information allocated for the M2M terminal, and the like may be saved in the context. The mobility management network element information includes at least one of identifier information and address information. The gateway device may also select the MTC server address information according to the Access Point Name (APN) information included in the Create Binding Request message. For details, refer to the description in Step 47. Step 56: The gateway device returns a create binding response message to the mobility management network element. The binding response message carries the IP address information assigned to the M2M terminal, that is, the IP address of the current PDN of the M2M terminal, corresponding to the current APN. The create binding response message may also carry the MTC server address information configured by the gateway device.

After receiving the binding response message, the mobility management network element completes the establishment of the association between the mobility management network element of the serving M2M terminal and the gateway. Afterwards, the M2M terminal transmits the data packet to the mobility management network element, and the mobility management network element can transmit the data packet to the gateway device through the established association; or the gateway device can send the downlink data packet to the mobility through the established association. The management network element, the mobility management network element sends the downlink data packet to the M2M terminal.

Step 57: The mobility management network element sends a PDN Connectivity Accept message to the M2M terminal. The connection establishment accept message carries the IP address information assigned by the gateway device to the M2M terminal. The connection establishment accept message may also carry a PDN ID information to identify the current PDN connection. This PDN ID information uniquely corresponds to the APN. In addition, the acceptance message may further carry an indication message for instructing the M2M terminal to perform network optimization based on the low data stream service. In addition, the accept message may further include indication information for instructing the M2M terminal to perform network optimization based on the low data stream service.

In the connection establishment request process, the M2M terminal can obtain the MTC server address.

For example, the MTC server address information obtained by the mobility management network element from the subscription data of the M2M terminal may be sent to the M2M terminal through the connection establishment acceptance message, or may be sent to the M2M terminal through other messages. The MTC server address information can be either IP address information or FQDN. The mobility management NE obtains the address of the MTC server through DNS resolution.

Alternatively, if the gateway device sends the MTC server address information to the mobility management network element, the mobility management network element may send the connection establishment message to the M2M terminal, or may send the message to the M2M terminal through other messages. In particular, the MTC server address information can be stored in a special cell PCO. The cell is only transmitted between the M2M terminal and the gateway device, and is transparent to the mobility management network element, and the mobility management network element is not parsed. At the same time, the IP address assigned by the gateway device to the M2M terminal The address information is also passed in the PCO and is transparent to the mobility management network element.

The PDN ID information is optional. If there is only one gateway device serving the M2M terminal, the PDN ID is not required to be configured. The address information of the MTC server may be based on the granularity of the APN or independent of the APN, and is not limited herein.

Through the foregoing signaling connection establishment process, the mobility management network element establishes a signaling connection relationship with the gateway device, and the M2M terminal obtains the IP address information allocated by the gateway device, and further the M2M terminal obtains the MTC server address information, Used for subsequent data transmission.

After the signaling connection establishment process is completed, the M2M terminal performs a process of transmitting data to the mobility management network element through NAS signaling according to its own configuration or network instructions.

FIG. 6 is a signaling flow chart of data transmission by a calling process in a machine-to-machine data transmission method according to an embodiment of the present invention. In this embodiment, the data transmission is based on the signaling connection established in the foregoing embodiment shown in FIG. 4 and FIG.

Step 61: The M2M terminal sends a service request (Service Request) message to the mobility management network element. The service request message may carry indication information such as "Low Data Usage indication" or "Small Data Transmissions Indication", and the indication information indicates that the data stream service executed by the M2M terminal is a low data service type. After receiving the service request message sent by the M2M terminal, the mobility management network element learns that the M2M terminal performs the low data flow characteristic service, so that the signaling connection can be maintained only with the M2M terminal without creating or restoring the bearer. This step can be omitted when the M2M terminal is in a non-idle state.

Step 62: The M2M terminal sends an Uplink NAS Transport message to the mobility management network element. The uplink NAS transport message carries the MTC data in the form of an IP data packet, where the source address in the IP data packet is an IP address that can be assigned by the gateway device to the UE, and the destination address is the address of the MTC server serving the M2M terminal. In addition, the PDN ID information can be carried in the uplink NAS transmission message.

Step 63: The mobility management network element receives the uplink NAS transmission message, and obtains the network associated with the PDN ID according to the PDN ID carried in the uplink NAS transmission message and the context saved by itself. Information about the device, that is, the gateway device that serves the terminal.

Step 64: The mobility management network element sends the IP data packet in the uplink NAS transmission message to the gateway device associated with the PDN ID according to the information of the gateway device obtained in step 63 through the signaling connection previously established with the gateway device.

Step 65: The gateway device receives the IP data packet forwarded by the mobility management network element, and routes an uplink MTC Data Transmission message including the IP data packet to the MTC server, that is, the destination address of the IP data packet. Corresponding MTC server.

Step 66: After receiving the IP data packet sent by the M2M terminal, the MTC server sends a transmission report to the M2M terminal through the Downlink Delivery Report Transmission message to inform the M2M terminal that the data transmission is successful. The transmission report is routed in the form of an IP packet to the gateway device serving the M2M terminal.

Step 67: The gateway device receives the transmission report, confirms the transmission object according to the saved terminal IP address information, and the destination address, and forwards the object. The gateway device retrieves the corresponding terminal context according to the saved terminal IP address information, confirms the mobility management network element information of the service M2M terminal, and the terminal identification information of the M2M terminal, and transmits the IP data packet of the transmission to the mobility management network. The signaling connection established by the element is forwarded to the mobility management network element. The forwarded message carries the IP data packet of the transmission report and the terminal identification information of the M2M terminal.

Step 68: The mobility management network element confirms that the transmission report message is sent to the M2M terminal according to the terminal identification information sent by the gateway device, and completes the data transmission in the calling process.

The technical solution provided by the embodiment implements data transmission of the calling process through the established signaling connection, and saves network resources and improves data transmission efficiency by transmitting data through the signaling connection.

FIG. 7 is a signaling flowchart of a called process transmission data in a machine-to-machine data transmission method according to an embodiment of the present invention. In this embodiment, the data transmission is based on the signaling connection established in the foregoing embodiment shown in FIG. 4 and FIG. Step 71: The MTC server sends a Downlink MTC Data Transmission message to the M2M terminal, and the downlink MTC data in the downlink MTC data transmission message is forwarded to the gateway device serving the M2M terminal in the form of an IP data packet.

Step 72: The gateway device receives downlink MTC data. The gateway device confirms the transmission object according to the saved terminal IP address information, and transmits the downlink MTC data by forwarding the Forward MTC Data message. Specifically, the gateway device retrieves the corresponding terminal context according to the saved terminal IP address information, confirms the mobility management network element information of the serving M2M terminal, and the terminal identification information of the M2M terminal, and establishes the IP data packet before establishing the mobility management network element. The signaling connection is forwarded to the mobility management network element. The forwarded MTC data message carries the IP data packet and the terminal identification information.

Step 73: The mobility management network element receives the message sent by the gateway device, and confirms the object M2M terminal that needs to be forwarded by using the terminal identifier information in the message. If the M2M terminal is in the idle state, the mobility management network element sends a paging message to the M2M terminal; otherwise, step 75 is directly executed. The paging message includes terminal identification information of the M2M terminal.

Step 74: The M2M terminal responds to the paging message, and sends a service request message to the mobility management network element. The service request message may carry indication information such as "Low Data Usage indication", "Small Data Transmissions Indication", etc., to instruct the mobility management network element terminal to perform low data flow service. After receiving the service request message sent by the terminal, the mobility management network element can learn that the M2M terminal performs the low data flow characteristic service by using the indication information, so that the signaling connection is maintained only with the M2M terminal, and the bearer is not created or restored.

Step 75: The mobility management network element confirms the object that the downlink data needs to be forwarded through the terminal identification information transmitted by the gateway device, and transmits the downlink data to the M2M terminal by using the downlink NAS transmission message.

Step 76: The M2M terminal receives the IP data packet sent by the MTC server from the mobility management network element, and sends a transmission report to the MTC server by using the uplink NAS transmission message. The transmission report may be included in the uplink NAS transmission message in the form of an IP data packet, and is transmitted by the M2M terminal to the mobility management network element. The source address of the IP data packet may be an IP address assigned to the M2M terminal by the gateway, and the destination address may be an MTC server address. In addition, the uplink NAS transport message can carry the PDN. ID information.

Step 77: The mobility management network element receives the uplink NAS transmission message, and confirms the information of the gateway device associated with the PDN ID according to the PDN ID carried in the uplink NAS transmission message and the saved context, and then passes the previously associated gateway. The signaling connection established by the device, which is included in step 78, the gateway device receives the transmission report in the form of an IP data packet forwarded by the mobility management network element, and transmits an uplink transmission report including the transmission report in the form of an IP data packet through the IP network. The Uplink Delivery Report Transmission message is routed to the MTC server to complete the data transfer in the called process.

The technical solution provided by the embodiment implements data transmission of the called process through the established signaling connection, and saves network resources and improves data transmission efficiency by transmitting data through the signaling connection.

In the process of establishing the signaling connection in Figure 4 and Figure 5 above, the IP address assigned by the gateway device to the M2M terminal may not be transmitted to the M2M terminal.

When the IP address assigned by the gateway device to the M2M terminal is not transmitted to the M2M terminal, the message sent by the gateway device for the M2M terminal does not carry the message sent by the gateway device in step 48, step 49, step 56, and step 57. Therefore, in the established signaling connection, the M2M terminal and the mobility management network element do not have the IP address information allocated by the gateway device for the M2M terminal. In this case, when the data is transmitted to the gateway device, it needs to be processed into an IP packet form recognizable by the MTC server, or processed into a packet form that the M2M terminal can recognize. The following description will be made by taking FIG. 8 and FIG. 9 as an example.

FIG. 8 is another signaling flowchart of data transmission by a calling process in a machine-to-machine data transmission method according to an embodiment of the present invention. The process of transferring data in the calling process includes:

Step 81: The M2M terminal sends a service request message to the mobility management network element. The service request message may carry indication information such as "Low Data Usage indication,", "Small Data Transmissions Indication", etc., to indicate the mobility management network element: the data flow service performed by the M2M terminal is a low data service type. The yuan receives the service sent by the M2M terminal. After the message is learned that the terminal performs the low data stream characteristic service, the signaling connection can be maintained only with the M2M terminal without creating or restoring the bearer. This step is omitted when the M2M terminal is in a non-idle state.

Step 82: The M2M terminal sends an uplink NAS transmission message to the mobility management network element. The uplink NAS transmission message carries MTC data, PDN ID information, and destination address indication information. The destination address indication information may be an MTC Server ID (MTC Server ID), that is, an FQDN, which is used to uniquely identify an MTC server, and may also be regarded as the name of the MTC server.

Step 83: The mobility management network element receives the uplink NAS transmission message, and obtains information about the gateway device associated with the PDN ID according to the PDN ID carried in the uplink NAS transmission message and the saved context. The MTC data contained in the upstream NAS transport message is sent to the gateway device associated with the PDN ID by a signaling connection previously established with the associated gateway device.

The forwarding message carries the terminal identification information of the M2M terminal and the destination address indication information. The terminal identification information is used to indicate the object to which the MTC data belongs.

In addition, the forwarding message carries PDN ID information or APN information corresponding to the PDN ID. Since the destination address that the M2M terminal can connect to, that is, the MTC server address information, can be used as part of the subscription data of the UE, when the M2M terminal completes registration with the mobility management network element, the mobility management network element obtains the subscription data of the M2M terminal. At the same time, the destination address information that the M2M terminal can connect to can be obtained. The destination address to which the M2M terminal can connect can be signed multiple. The destination address information that the M2M terminal can connect to may be the identifier of the MTC server and the corresponding IP address information, or may be only the identifier of the MTC server. The mobility management network element can obtain the address of the corresponding MTC server, that is, the IP address, by means of DNS resolution. In this way, the mobility management network element receives the uplink NAS transmission message sent by the M2M terminal, and after obtaining the destination address indication information, the mobility management network element can be configured according to the subscription data of the M2M terminal, and the destination address indication information provided by the M2M terminal is converted into the destination IP address. Specifically, if the signing form is the identifier of the MTC service and the corresponding IP address information, the mobility management network element obtains the corresponding destination IP address information by using the identifier of the MTC server provided by the M2M terminal; MTC service identity, then mobility management network The element performs DNS resolution according to the identifier of the MTC server provided by the M2M terminal, and obtains the destination IP address information.

When the mobility management network element confirms that the destination address indication information provided by the M2M terminal is legal, the MTC data and the destination IP address are forwarded. At this time, the forwarding message carries the terminal identification information of the M2M terminal and the destination IP address information, that is, the IP address information of the MTC server.

Step 84: The gateway device receives the MTC data forwarded by the mobility management network element by forwarding the message, assembles the data into an IP data packet, and routes the MTC data to the MTC server through the IP network. Specifically, the gateway device retrieves the IP address information of the M2M terminal corresponding to the PDN ID or the APN by using the PDN ID or the APN information provided by the mobility management network element in step 83 to retrieve the M2M terminal context.

For the IP address required to configure the IP packet, that is, the IP address assigned by the gateway device to the M2M terminal, the gateway device can obtain the context created and saved for the M2M terminal. The destination address required for configuring an IP packet can be obtained in the following ways:

1) The gateway device obtains the destination address information, that is, the IP address information of the MTC server, according to the destination address indication information provided by the M2M terminal, such as the identifier of the MTC server.

2) When the forwarded message carries the IP address information of the MTC server, it can be obtained directly from the forwarded message.

3) In the signaling connection establishment process, the mobility management network element transmits the destination address of the M2M terminal connectable in the acquired subscription data to the gateway device serving the M2M terminal, and the gateway device keeps it in the context of the UE. The gateway device obtains the destination address information according to the identifier of the MTC server provided by the M2M terminal. Specifically, if the signing mode is the identifier of the MTC service and the corresponding IP address information, the gateway device can obtain the corresponding destination address information by using the identifier of the MTC server provided by the M2M terminal; if the signing mode is only the identifier of the MTC service, the gateway The device performs DNS resolution according to the identifier of the MTC server provided by the M2M terminal, and obtains the destination IP address information.

4) The gateway device locally configures the address information (such as the IP address information) of the MTC server. The configuration may be performed based on the granularity of the PDN connection, such as configuring the address of the MTC server according to the APN. Information.

For the 3) mode, the gateway device also needs to confirm whether the destination address indication information provided by the M2M terminal is legal. Only after the legal situation can the subsequent assembly of the IP data packet be performed and sent to the MTC server.

For the 4) mode, the M2M terminal does not need to provide the destination address indication information. Specifically, the gateway device retrieves the address information of the MTC Server configured locally by using the PDN ID or APN information provided by the mobility management network element in step 83 to obtain an MTC Server address corresponding to the PDN ID or the APN.

Step 85: The MTC server receives the IP data packet sent by the gateway device, and sends a transmission report to the M2M terminal. The transmission report is routed in the form of an IP packet to the gateway device serving the M2M terminal.

Step 86: The gateway device receives the transmission report, and confirms the transmission object according to the destination address in the IP data packet where the transmission report is located and the saved terminal IP address information. The gateway device retrieves the corresponding terminal context according to the saved terminal IP address information, confirms the mobility management network element information of the service M2M terminal, and the terminal identification information of the M2M terminal, splits the IP data packet, and extracts the data part thereof, according to the M2M. The peer-to-peer protocol between the terminals re-encapsulates the data part into a peer-to-peer protocol format, that is, a data packet identifiable by the M2M terminal, and forwards the reassembled data packet to the mobile through a signaling connection previously established with the mobility management network element. Sex management network element. The forwarded message carries the reassembled data packet and the terminal identification information of the M2M terminal.

Step 87: The mobility management network element confirms the object that the transmission report needs to be forwarded through the terminal identification information transmitted by the gateway device, and transmits the transmission report to the M2M terminal through the downlink NAS transmission message.

FIG. 9 is another signaling flowchart of a called process transmission data in a machine-to-machine data transmission method according to an embodiment of the present invention. The process of transferring data in the called process includes: Step 91: The MTC server sends the downlink MTC data to the M2M terminal, and the downlink MTC data is forwarded to the gateway device serving the M2M terminal by using the downlink MTC data transmission message in the form of an IP data packet.

Step 92: The gateway device receives the downlink MTC data, confirms the transmission object according to the destination address, that is, the IP address of the terminal and the saved terminal IP address information, and transmits the downlink MTC data. Specifically, the gateway device retrieves the corresponding terminal context according to the saved terminal IP address information, confirms the mobility management network element information of the service M2M terminal, and the terminal identification information of the M2M terminal, and splits the data part in the IP data packet, according to The peer-to-peer protocol between the M2M terminals re-encapsulates the data portion into a peer-to-peer protocol format, that is, a data packet identifiable by the M2M terminal, and forwards the identifiable data packet through a signaling connection previously established with the mobility management network element. Give the mobility management network element. The forwarding message carries the data packet identifiable by the M2M terminal and the terminal identification information of the M2M terminal.

Step 93: The mobility management network element transmits the terminal identifier information of the M2M terminal through the gateway device to confirm the object that the downlink MTC data needs to be forwarded. If the M2M terminal is in an idle state, the mobility management network element sends a paging message to the M2M terminal; otherwise, step 95 is directly performed. The paging message includes terminal identification information of the M2M terminal.

Step 94: The M2M terminal responds to the paging message, and sends a service request message to the mobility management network element. The service request message may carry indication information such as "Low Data Usage indication", "Small Data Transmissions Indication", etc., and the indication information indicates that the M2M terminal performs low data flow service. After receiving the service request message sent by the terminal, the mobile mobility management network element can learn that the M2M terminal performs the low data flow characteristic service by using the indication information, so that only the signaling connection is maintained with the M2M terminal, and the bearer is not created or restored.

Step 95: The mobility management network element confirms the object of the downlink MTC data forwarding by using the terminal identification information of the M2M terminal transmitted by the gateway device, and transmits the downlink MTC data to the M2M terminal by using the downlink NAS transmission message.

Step 96: After receiving the downlink MTC data in the form of a data packet sent by the MTC server, the M2M terminal sends a transmission report to the MTC server by using the uplink NAS transmission message. In addition, the upstream NAS The transport message carries the PDN ID information.

Step 97: The mobility management network element receives the uplink NAS transmission message, and confirms the information of the gateway device associated with the PDN ID according to the PDN ID and the saved context in the uplink NAS transmission message, so as to pass the previously established signaling connection. A transmission report in the uplink NAS transport message is sent to the gateway device associated with the PDN ID. The uplink NAS transmission message carries the terminal identification information of the M2M terminal, and is used to indicate that the object to which the advertisement belongs is transmitted.

Step 98: The gateway device receives the transmission message forwarded by the mobility management network element, and routes it to the MTC server through the IP network. Specifically, the gateway device receives the transmission report forwarded by the mobility management network element, assembles it into an IP data packet, and routes it to the MTC server through the IP network. The source address of the IP data packet is the IP address assigned by the gateway device to the M2M terminal, and the gateway device obtains the address by using the context saved by the M2M terminal. The acquisition of the destination address is detailed in the description of the embodiment shown in FIG.

In the foregoing method embodiment, the destination address of the transmitted IP data packet may also be the IP address of the M2M terminal of the communication peer end, that is, the M2M terminal may also use a similar method to implement data transmission.

FIG. 10 is a signaling flowchart of transmitting alarm information in a machine-to-machine data transmission method according to an embodiment of the present invention. In some scenarios, the network side can also generate the number of streams that need to be passed to the MTC server. For example, the Machine Type Communication Monitoring (MTC Monitoring) scenario. In this scenario, when the network detects an abnormal behavior of the M2M terminal, an alarm is generated and the alarm information needs to be notified to the MTC server. In this embodiment, the data transmission is based on the signaling connection established in the foregoing embodiment shown in FIG. 4 and FIG.

Step 101: The mobility management network element monitors the behavior of the M2M terminal. When detecting that the behavior of the M2M terminal is abnormal, the mobility management network element sends the alarm information to the gateway device, where the mobility management acquires the gateway device serving the M2M terminal. The method can refer to the description of step 83 or step 63 and the like.

Which events (terminal behaviors) of the M2M terminal need to be monitored by the user to which they belong Make decisions and subscribe to operators. When the subscription is performed, the event to be monitored may be contracted in the subscription data of the M2M terminal, and the monitoring event may include at least one of the following methods:

1) Monitor the current location of the M2M terminal. For example, when the current location information of the M2M terminal does not match a certain reference information (the reference information is the monitoring event trigger point), the monitoring event needs to be triggered to be reported (for example, sending an alarm message, including and monitoring events in the message) relevant information);

2) Monitor the binding relationship between IMSI and IMEI of the M2M terminal. For example, when the binding relationship between the current IMSI and the IMEI of the M2M terminal does not match the certain reference information, the monitoring event needs to be triggered to be reported (for example, sending an alarm message, where the message includes information related to the monitoring event);

3) Monitor the capability information of the M2M terminal. For example, when the current capability information of the M2M terminal does not match a certain reference information, the monitoring event needs to be triggered to be reported (for example, sending an alarm message, and the message includes information related to the monitoring event);

4), monitoring the behavior of the M2M terminal to communicate with the corresponding machine type (MTC Feature(s)) and so on. For example, when the current behavior of the M2M terminal does not match a certain reference information, the monitoring event needs to be triggered to be reported (for example, an alarm message is sent, and the message includes information related to the monitoring event).

It should be noted that the above several methods may also be combined to determine whether the detection event of the M2M terminal occurs.

The HLR/HSS sends the subscription data including the subscribed monitoring event to the mobility management network element of the serving M2M terminal, and the mobility management network element monitors the behavior of the M2M terminal according to the subscribed monitoring event.

When reporting the alarm information to the gateway device on the mobility management NE, it can be based on different granularities, such as:

1) If the monitoring event is based on the UE granularity, that is, the monitoring event is associated with the subscription identifier (eg, IMSI) in the subscription data, the mobility management network will send an alarm through the saved signaling connection established with the gateway device for the UE. The information is sent to the gateway device.

2), if the monitoring event is based on PDN granularity, ie, monitoring events in the contract data with APN Correspondingly, the mobility management network element first confirms the PDN connection of the subscription monitoring event in the PDN connection established by the current UE; and then, for the PDN connection of the subscription monitoring event, the alarm information is established through the signaling connection previously established with the gateway device. Sent to the gateway device.

The embodiment of the present invention does not impose any limitation on the specific message format of the alarm information sent by the mobility management network element. Further, the message of the alarm information also needs to carry the PDN ID or the APN information corresponding to the PDN ID.

Step 102: The gateway device receives the alarm information sent by the mobility management network element, and sends the alarm information to the MTC server.

If the alarm information sent by the mobility management network element is sent by the IP data packet, the alarm information is sent to the MTC server. If the alarm information is not sent through the IP data packet, Then, the gateway device can assemble the alarm information into an IP data packet and then route it to the MTC server through the IP network. The gateway device assembles the alarm information into an IP data packet. Referring to the description in step 83. After receiving the alarm information sent by the mobility management network element, the gateway device constructs the alarm information that can be identified by the MTC server according to the peer protocol stack between the gateway device and the MTC server, and constructs the alarm message. The alarm message is sent to the MTC server.

Step 103: The MTC server receives the alarm information, and returns an alarm response to the gateway device. Step 104: The gateway device receives the alarm response, and confirms the transmission object according to the destination address in the IP data packet where the transmission report is located and the saved terminal IP address information.

Step 105: The gateway device retrieves the corresponding terminal context according to the saved terminal IP address information, confirms the mobility management network element information of the serving M2M terminal, and the terminal identification information of the M2M terminal, and uses the signaling connection previously established with the mobility management network element. , forward the alarm response to the mobility management network element.

The technical solution provided in this embodiment can timely recover the measures for remediating when the M2M terminal is abnormal by sending the alarm information, thereby ensuring the reliability of the data transmission.

FIG. 11 is a schematic structural diagram of a mobility management network element device according to an embodiment of the present invention. The device The method includes: a receiving module 111, a connection establishing module 112, and a transmitting module 113. The receiving module 111 is configured to receive an access request of the terminal of the low data stream. For details, refer to the description of step 11 above. The connection establishing module 112 is configured to receive, by the receiving module 111, the terminal of the low data stream. After the request, the signaling connection from the mobility management network element to the gateway device is established for the terminal of the low data stream. For details, refer to the description of step 12 above; the transmission module 113 is configured to use the terminal of the low data stream. The data information is transmitted through the signaling connection established by the connection establishing module 112. For details, refer to the description of step 13 above.

The connection establishment module 112 can include: a gateway device acquisition sub-module 115 and a setup sub-module 116. The gateway device obtaining sub-module 115 is configured to acquire a gateway device serving the terminal of the low data stream; the establishing sub-module 116 is configured to initiate an association establishment request to the gateway device to establish signaling with the gateway device. connection.

In another embodiment of the present invention, when the receiving module 111 is further configured to receive the response message of the association establishment request, the response message of the association establishment request includes a gateway device that allocates the terminal of the low data flow. When the information of the IP address is used, the mobility management network element device may further include: a first sending module, configured to: after the receiving module 111 receives the response message of the association establishment request, to the terminal of the low data stream Sending a response message of the access request message, where the response message of the access request message includes IP address information allocated by the gateway device for the terminal of the low data stream.

In another embodiment of the present invention, when the receiving module 111 is further configured to receive the response message of the association establishment request, the response message of the association establishment request includes machine type communication server address information, and the gateway device is When the IP address information of the terminal of the low data stream is allocated; the mobility management network element device may further include:

a second sending module, configured to send, after the receiving module 111 receives the response message of the association establishment request, a response message of the access request message to the terminal of the low data flow, where the access request message is sent The response message includes the IP address information and the machine type MTC server address information allocated by the gateway device for the terminal of the low data stream; the MTC server address information is The mobility management network element is obtained according to the subscription data.

The mobility management network element device provided by the embodiment of the present invention may further include: a detection module 117 and an alarm module 118. The detecting module 117 is configured to detect whether an abnormality occurs in the terminal of the low data stream, and the detecting module 117 can be configured to detect the terminal of the low data stream based on the terminal granularity or the PDN granularity. The alarm module 118 is configured to: when the detecting module 117 detects that the terminal of the low data stream is abnormal, send the abnormal information of the terminal of the low data stream to the gateway device by using the established signaling connection, so that The gateway device sends the abnormality information of the terminal of the low data stream to the MTC server.

In this embodiment, the mobility management network element device establishes a signaling connection and uses the established signaling connection to transmit data, thereby avoiding allocating network bearers to a large number of M2M terminals, saving network resources, and solving low data. The M2M terminal of the streaming application feature has a problem of large consumption and occupation of network resources, and improves data transmission efficiency.

FIG. 12 is a schematic structural diagram of a machine-to-machine data transmission system according to an embodiment of the present invention. The system includes a mobility management network element 121 and a gateway device 122, where the mobility management network element 121 can be any mobility management network element device provided by the foregoing device embodiment, and is used to receive a low data flow terminal. The access request, sending an association establishment request to the gateway device 122 that provides the service for the terminal of the low data flow, to establish a signaling connection between the mobility management network element 121 and the gateway device 122; The data information of the terminal of the low data stream is transmitted through the established signaling connection; the gateway device 122 is configured to receive an association establishment request sent by the mobility management network element 121, and establish the terminal for the low data flow. A signaling connection between the mobility management network element 121 and the gateway device 122.

Specifically, the mobility management network element 121 may be configured to receive an uplink non-access stratum service NAS transport message including PDN ID information and machine type communication data in the form of an IP data packet, and obtain the service according to the PDN ID information. The gateway device 122 of the terminal of the data stream transmits the machine type communication data in the form of the IP data packet to the gateway device 122 by using the signaling connection, so that the gateway device 122 takes the form of the IP data packet Machine type communication data routing to MTC service Server

Or

The mobility management network element 121 may be configured to receive an uplink NAS transmission message including PDN ID information, destination address indication information, and machine type communication data, and obtain, by the PDN ID information, a gateway device 122 of a terminal that serves the low data flow. Transmitting, by the signaling connection, the machine type communication data to the gateway device 122, so that the gateway device 122 assembles the machine type communication data into an IP data packet, and routes the data to the MTC server; The source address of the IP data packet is obtained from a context created in the process of establishing a signaling connection; the destination address of the IP data packet is obtained according to the destination address indication information;

Or

The mobility management network element 121 may be configured to receive the machine type communication data in the form of an IP data packet sent by the gateway device 122, where the machine type communication data in the form of an IP data packet is sent by an MTC server. The gateway device 122 sends the machine type communication data in the form of the IP data packet to the terminal of the low data stream through the management network element;

Or

The mobility management network element 121 may be configured to receive a data packet identifiable by the terminal of the low data stream sent by the gateway device 122, where the data packet recognized by the terminal of the low data stream is used by the gateway device 122 And obtaining, according to the reassembly of the machine type communication data in the form of an IP data packet sent by the MTC server, the data packet identifiable by the machine to the machine terminal to the terminal of the low data stream;

Or

The mobility management network element 121 may be configured to: when detecting that the terminal of the low data flow is abnormal, send the abnormal information of the terminal of the low data flow to the gateway device 122 by using the established signaling connection, so that The gateway device 122 sends the abnormality information of the terminal of the low data stream to the MTC server.

The mobility management network element 121 can also be used for subscription data of the terminal according to the low data flow. Parsing the destination address indication information into a destination address of the IP data packet; sending the destination address of the IP data packet to the gateway device 122, so that the gateway device 122 assembles the IP data packet;

Or

The mobility management network element 121 may be further configured to send the destination address indication information to the gateway device 122, so that the gateway device 122 parses the destination address indication information to obtain a destination address of the IP data packet. ;

Or

The mobility management network element 121 may be further configured to send the destination address indication information to the gateway device 122, so that the gateway device 122 indicates the destination address according to the subscription data of the terminal of the low data stream. The information is parsed into the destination address of the IP packet.

When the mobility management network element 121 is configured to detect that the location information and the reference information of the terminal of the low data flow are inconsistent, determine that the terminal of the low data flow is abnormal; or

When the mobility management network element 121 is configured to detect that the relationship between the IMSI and the IMEI of the terminal of the low data flow is inconsistent with the reference information, determine that the terminal of the low data flow is abnormal; or

When the mobility management network element 121 is configured to detect that the capability information and the reference information of the terminal of the low data flow are inconsistent, determine that an abnormality occurs in the terminal of the low data flow; or

When the mobility management network element 121 is configured to detect that the behavior of the terminal of the low data flow is inconsistent with the reference information, it is determined that the terminal of the low data flow has an abnormality.

The gateway device 122 is configured to receive an association establishment request sent by the mobility management network element 121, and establish a signaling connection between the mobility management network element and the gateway device for the terminal of the low data flow, as described in the foregoing method embodiment. instruction of.

In this embodiment, the machine-to-machine data transmission system establishes a signaling connection and uses the established signaling connection to transmit data, thereby avoiding allocating network bearers to a large number of M2M terminals, and solving the application characteristics with low data flow. M2M terminal consumes and consumes a large amount of network resources The problem, while ensuring the normal operation of the H2H business.

FIG. 13 is a schematic structural diagram of a terminal according to an embodiment of the present invention. The terminal includes: a transmitting unit 131 and a receiving unit 132. The sending unit 131 is configured to send an access request to the mobility management network element. The receiving unit 132 is configured to receive an access response sent by the mobility management network element, where the access response includes the established mobility management network element and the gateway device. The packet data network used in the signaling connection identifies the PDN ID information; or the access request response includes indication information for indicating that the terminal of the low data stream transmits data by signaling.

The terminal provided by the embodiment of the present invention may further include: a data transmission unit 133, where the data transmission unit 133 is configured to send, after the receiving unit receives the access response, data information, the data information, to the mobility management network element. The source address is an IP address assigned by the gateway device to the terminal of the low data stream. Alternatively, the data transmission unit 133 may be configured to send data information to the mobility management network element, where the source address of the data information is an IP address assigned by the gateway device to the terminal of the low data stream, and the destination address is received. The MTC server address information that provides the service to the terminal.

In this embodiment, the information obtained by the terminal through the receiving unit makes it possible to transmit data through the signaling connection, thereby avoiding allocating network bearers to a large number of M2M terminals, saving network resources, and solving the application characteristics with low data flow. The M2M terminal has a problem of large consumption and occupation of network resources, and improves data transmission efficiency.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A machine-to-machine data transmission method, comprising:

An access request of a terminal receiving a low data stream;

Establishing a signaling connection from the mobility management network element to the gateway device for the terminal of the low data stream; and transmitting, by using the established signaling connection, the data information of the terminal of the low data stream.

2. The machine-to-machine data transmission method according to claim 1, wherein establishing a signaling connection from the mobility management network element to the gateway device for the terminal of the low data stream comprises: obtaining the low Gateway device for terminal services of data streams;

An association establishment request is initiated to the gateway device to establish a signaling connection between the mobility management network and the gateway device.

The device-to-machine data transmission method according to claim 2, wherein the initiating the association establishment request to the gateway device comprises:

4. The machine-to-machine data transmission method of claim 2, further comprising:

Sending, by the terminal of the low data stream, the response message of the access request, where the response message of the access request includes a packet data network used in establishing a signaling connection between the mobility management network element and the gateway device. Identify the PDN ID information; or

The response message of the access request includes indication information for indicating that the terminal of the low data stream transmits data by signaling.

The device-to-machine data transmission method according to any one of claims 2 to 4, wherein the initiating an association establishment request to the gateway device comprises: And generating, to the gateway device, an association establishment request including indication information indicating that the terminal of the low data flow is a low data service type.

The machine-to-machine data transmission method according to any one of claims 2 to 4, further comprising:

Receiving the response message of the association establishment request, the response message of the association establishment request includes information of an IP address allocated to the terminal of the low data stream; and transmitting the access request message to the terminal of the low data flow a response message, the response message of the access request message includes IP address information allocated by the gateway device for the terminal of the low data stream; or

The response message of the association establishment request includes machine type communication server address information and IP address information allocated to the terminal of the low data stream, and sends a response message of the access request message to the terminal of the low data stream. The response message of the access request message includes IP address information and machine type MTC server address information allocated by the gateway device for the terminal of the low data stream; the MTC server address information is determined by the mobility management network element Obtained in the contract data.

The device-to-machine data transmission method according to claim 1, wherein the transmitting the data information of the terminal of the low data stream through the established signaling connection comprises: receiving the PDN ID information and An uplink non-access stratum service NAS transport message of the machine type communication data in the form of an IP packet, the gateway device of the terminal serving the low data stream is obtained according to the PDN ID information, and the IP data is used by using the signaling connection Transmitting machine type communication data in the form of a packet to the gateway device to cause the gateway device to route machine type communication data in the form of the IP data packet to an MTC server;

Or

Receiving an uplink NAS transmission message including PDN ID information, destination address indication information, and machine type communication data, obtaining a gateway device that serves the terminal of the low data stream according to the PDN ID information, and using the signaling connection to connect the machine Type communication data is sent to the gateway device to cause the gateway device to assemble the machine type communication data into an IP data packet and route to an MTC server, wherein a source address of the IP data packet is established from a signaling connection Context created during the process Obtaining, the destination address of the IP data packet is obtained according to the destination address indication information; or

Receiving the machine type communication data in the form of an IP data packet sent by the gateway device, where the machine type communication data in the form of an IP data packet is sent by the MTC server to the gateway device, and the IP data packet is sent Forming the machine type communication data by the management network element to the terminal of the low data stream;

Or

Receiving a data packet identifiable by the terminal of the low data stream sent by the gateway device, where the data packet identifiable by the terminal of the low data stream is in the form of an IP data packet sent by the gateway device according to the MTC server After the device type communication data is reassembled, the data packet identifiable by the machine to the machine terminal is sent to the terminal of the low data stream;

Or

When an abnormality occurs in the terminal of the low data stream, the abnormal information of the terminal of the low data stream is sent to the gateway device by using the established signaling connection, so that the gateway device uses the low data stream. The abnormality information of the terminal is sent to the MTC server.

The device-to-machine data transmission method according to claim 7, wherein when the NAS transmission message includes the destination address indication information, the method further includes:

Determining, by the subscription data of the terminal of the low data stream, the destination address indication information, so that the gateway device assembles the IP data packet; or

Sending the destination address indication information to the gateway device, so that the gateway device parses the destination address indication information to obtain a destination address of the IP data packet;

Or

Sending the destination address indication information to the gateway device, so that the gateway device parses the destination address indication information into a destination address of the IP data packet according to the subscription data of the terminal of the low data stream.

The device-to-machine data transmission method according to claim 7, wherein the abnormality of the terminal that detects the low data stream comprises:

When it is detected that a detection event occurs, it is determined that an abnormality has occurred in the terminal of the low data stream.

The device-to-machine data transmission method according to claim 9, wherein, when the detection event is detected, determining that the terminal of the low data stream has an abnormality comprises at least one of the following manners :

When the location information of the terminal that detects the low data flow is inconsistent with the reference information, it is determined that the terminal of the low data flow has an abnormality;

When the relationship between the international mobile subscriber identity IMSI of the terminal that detects the low data stream and the international mobile device identity code IMEI is inconsistent with the reference information, it is determined that the terminal of the low data stream is abnormal;

When the capability information and the reference information of the terminal that detects the low data stream are inconsistent, it is determined that the terminal of the low data stream is abnormal; and

When it is detected that the behavior of the terminal of the low data stream is inconsistent with the reference information, it is determined that the terminal of the low data stream has an abnormality.

11. A mobility management network element device, comprising:

The mobility management network element device according to claim 11, wherein the connection establishment module comprises:

a gateway device acquiring a sub-module, configured to acquire a gateway device serving the terminal of the low data stream, and a sub-module, configured to acquire, by the gateway device, the gateway device acquired by the sub-module to initiate association A request is established to establish a signaling connection with the gateway device.

The mobility management network element device according to claim 11, further comprising: a detecting module, configured to detect whether an abnormality occurs in the terminal of the low data stream;

And the transmitting module is configured to: when the detecting module detects that the terminal of the data stream is abnormal, send the abnormal information of the terminal of the low data flow to the gateway device by using the established signaling connection, so that the The gateway device sends the abnormal information of the terminal of the low data stream to the MTC server.

14. The mobility management network element device according to any one of claims 11 to 13, characterized in that

The receiving module is further configured to receive the response message of the association establishment request, where the response message of the association establishment request includes information of an IP address allocated by the gateway device to the terminal of the low data flow; the device further includes:

a first sending module, configured to send, after the receiving module receives the response message of the association establishment request, a response message of the access request message to a terminal of the low data flow, where the access request message is The response message includes IP address information allocated by the gateway device to the terminal of the low data stream;

Or

The receiving module is further configured to receive the response message of the association establishment request, where the response message of the association establishment request includes machine type communication server address information and IP address information allocated by the gateway device for the terminal of the low data stream; The device also includes:

a second sending module, configured to send, after the receiving module receives the response message of the association establishment request, a response message of the access request message to the terminal of the low data flow, where the access request message is The response message includes IP address information and machine type MTC server address information allocated by the gateway device for the terminal of the low data stream; and the MTC server address information is obtained by the mobility management network element according to the subscription data.

15. A machine-to-machine data transmission system, comprising: a mobility management network element, configured to receive an access request of the terminal of the low data flow, and send an association establishment request to the gateway device that provides the service for the terminal of the low data flow, to establish the mobility management network element and the a signaling connection between the gateway devices; transmitting, by the established signaling connection, the data information of the terminal of the low data stream;

And a gateway device, configured to receive an association establishment request sent by the mobility management network element, and establish, by the terminal of the low data flow, a signaling connection between the mobility management network element and the gateway device.

16. The machine-to-machine data transmission system according to claim 15, wherein the mobility management network element is configured to receive uplink non-access including machine type communication data in the form of PDN ID information and IP data packets. The layer service NAS transmits a message, and the gateway device that serves the terminal that serves the low data stream according to the PDN ID information, and sends the machine type communication data in the form of the IP data packet to the gateway device by using the signaling connection, Causing the gateway device to route machine type communication data in the form of the IP packet to the MTC server;

Or

And receiving an uplink NAS transmission message including the PDN ID information, the destination address indication information, and the machine type communication data, obtaining, by using the PDN ID information, a gateway device that serves the terminal of the low data flow, and using the signaling connection Transmitting machine type communication data to the gateway device, so that the gateway device assembles the machine type communication data into an IP data packet and routes to an MTC server; wherein the source address of the IP data packet is established from signaling Obtaining in a context created during the connection; the destination address of the IP data packet is obtained according to the destination address indication information;

Or

And the machine type communication data in the form of an IP data packet sent by the gateway device, where the machine type communication data in the form of an IP data packet is sent by the MTC server to the gateway device, where the IP is The machine type communication data in the form of a data packet is sent to the terminal of the low data stream by the management network element;

Or

a terminal identifiable data packet for receiving the low data stream sent by the gateway device, where The terminal identifiable data packet of the low data stream is obtained by the gateway device reassembling the machine type communication data in the form of an IP data packet sent by the MTC server, and the machine to machine terminal is identifiable a data packet is sent to the terminal of the low data stream;

Or

And sending, by the established signaling connection, abnormal information of the terminal of the low data stream to the gateway device, so that the gateway device uses the low data, when an abnormality occurs in the terminal that is used to detect the low data flow. The abnormality information of the streamed terminal is sent to the MTC server.

The machine-to-machine data transmission system according to claim 15, wherein the mobility management network element is further configured to parse the destination address indication information according to subscription data of a terminal of the low data stream. a destination address of the IP data packet; sending the destination address of the IP data packet to the gateway device, so that the gateway device assembles the IP data packet; or

And the method is further configured to send the destination address indication information to the gateway device, so that the gateway device parses the destination address indication information to obtain a destination address of the IP data packet.

Or

And the method is further configured to send the destination address indication information to the gateway device, so that the gateway device parses the destination address indication information into the IP data packet according to the subscription data of the terminal of the low data stream. address.

The machine-to-machine data transmission system according to claim 15, wherein the mobility management network element is configured to: when detecting that the location information and the reference information of the terminal of the low data flow are inconsistent, determine An abnormality has occurred in the terminal of the low data stream; or

When the relationship between the IMSI and the IMEI of the terminal for detecting the low data stream and the reference information are inconsistent, it is determined that the terminal of the low data stream is abnormal; or

When the capability information and the reference information of the terminal for detecting the low data stream are inconsistent, it is determined that the terminal of the low data stream is abnormal; or

Determining, when the behavior of the terminal for detecting the low data stream is inconsistent with the reference information An abnormality occurred in the terminal of the low data stream.

19. A terminal, comprising:

a receiving unit, configured to receive an access response sent by the mobility management network element, where the access response includes a packet data network identifier PDN ID used in a signaling connection between the established mobility management network element and the gateway device. Information: or the access request response includes indication information for indicating that the terminal of the low data stream transmits data by signaling.

The terminal according to claim 19, further comprising:

a data transmission unit, configured to send data information to the mobility management network element after the receiving unit receives the access response, where the source address of the data information is allocated by the gateway device for the terminal of the low data stream IP address.

The terminal according to claim 20, wherein the data transmission unit is configured to send data information to the mobility management network element, where a source address of the data information is that the gateway device is the low data stream The IP address assigned by the terminal, and the destination address is the received MTC server address information for providing services to the terminal.