WO2013166645A1

WO2013166645A1 - Data transmission method, device, and system

Info

Publication number: WO2013166645A1
Application number: PCT/CN2012/075151
Authority: WO
Inventors: 舒林; 张艳平; 于益俊
Original assignee: 华为技术有限公司
Priority date: 2012-05-07
Filing date: 2012-05-07
Publication date: 2013-11-14
Also published as: CN103563416A; CN103563416B

Abstract

Embodiments of the present invention provide a data transmission method, device, and system, which relate to the field of communications, and specifically comprise: saving second correlation information between a second correlation identifier and a target MTC-IWF; receiving a first uplink message sent by a UE and containing the second correlation identifier and uplink Machine-Type Communications (MTC) data; according to the saved second correlation information, determining the target MTC-IWF corresponding to the second correlation identifier; and sending to the target MTC-IWF a second uplink message containing the uplink MTC data, so that the target MTC-IWF sends the uplink MTC data to a target MTC server. By means of the present invention, it is guaranteed that a UE can accurately send uplink MTC data to an MTC server that initiates an MTC device trigger request, so as to ensure correctness, reliability, and safety of data communications between an MTC server and a UE.

Description

Method, device and system for data transmission

The present invention relates to the field of communications, and in particular, to a method, device and system for data transmission. Background technique

M2M (Machine-to-Machine, communication between machine and machine) is an idea, compared with H2H (Human-to-Human), which is widely used at present, machine and machine. Inter-communication is also defined as MTC (Machine-Type Communications).

Many communication between people is also realized by machines, for example, communication between machines such as mobile phones, telephones, computers, and fax machines to achieve human-to-human communication. But currently only computers, mobile phones and other IT-like devices have this communication and networking capability. Numerous ordinary machines and equipment have almost no networking and communication capabilities, such as home appliances, vehicles, vending machines, factory equipment, and so on. The goal of MTC technology is to integrate all the machines in the world into a single communication network, so that all machines and equipment can be connected and communicated, and all machines can be intelligent and interconnected.

As a means of wireless communication between machines and machines, MTC provides a new solution to the informationization of manufacturing. For example: Install a module that can monitor the operating parameters of the distribution network in the power equipment to realize real-time monitoring, control, management and maintenance of the power distribution system; install a module that can collect information on the operation of the oil well in the petroleum equipment, and adjust the oil well equipment remotely. And control, timely and accurate understanding of the working conditions of the oil well equipment; equipped with vehicle information terminal, remote monitoring system, etc., to achieve vehicle operating status monitoring. Therefore, MTC technology is of great significance, with broad market and application prospects, and promotes a new round of social production and lifestyle changes.

3GPP (3rd Generation Partnership Project) launched MTC's international standardization work as early as the beginning of 2009, aiming to lead the standardization of MTC technology in the entire communications industry. At present, MTC device triggering is one of the issues discussed by the 3GPP. The MTC device trigger is designed to allow the MTC server to trigger the UE (User Equipment) to initiate communication to the MTC server to implement data exchange, and between the MTC server and the UE. The process of data communication is as follows:

First, the MTC server sends the MTC device trigger request to the MTC-IWF (MTC Inter Working Function) in the form of a short message or a small data, and the MTC-IWF sends the MTC device trigger request to the MTC-IWF. The mobility management network element, the mobility management network element sends the MTC device trigger request to the UE through the non-access stratum.

Then, after receiving the MTC device triggering request sent by the mobility management network element, the UE sends the uplink MTC data required by the MTC server to the mobility management network element, and the mobility management network element sends the uplink MTC data to the MTC. -IWF, And transmitting, by the MTC-IWF, the uplink MTC data to the corresponding destination MTC server.

In the prior art, after the UE sends the uplink MTC data to the mobility management network element, the mobility management network element may send the uplink MTC data to the wrong destination MTC-IWF, and the incorrect destination MTC-IWF receives the uplink MTC data. After that, the uplink MTC data may be transmitted to the wrong MTC server or the uplink MTC data may be sent to the destination MTC server, thereby causing the misdirection of the uplink MTC data and the leakage of the data content, thereby reducing the reliability of data communication between the MTC server and the UE. Sex and safety. Summary of the invention

The invention provides a method, a device and a system for data transmission. The invention can ensure that the UE can accurately transmit the uplink MTC data to the MTC server that initiates the MTC device trigger request.

The invention provides a method for data transmission, and the specific technical solutions adopted are as follows:

Saving second association information between the second association identifier and the destination MTC-IWF;

Receiving, by the UE, a first uplink message that includes the second association identifier and the uplink MTC data;

Determining, according to the saved second association information, a destination MTC-IWF corresponding to the second association identifier;

The second uplink message including the uplink MTC data is sent to the destination MTC-IWF, so that the destination MTC-IWF sends the uplink MTC data to the destination MTC server.

Applying the foregoing method, the mobility management network element can accurately send the uplink MTC data sent by the UE to the destination according to the second association information between the saved second association identifier and the destination MTC-IWF, and ensure the correctness of the uplink data communication. Reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission in the prior art.

The invention also provides another method for data transmission, and the specific technical solutions adopted are as follows:

Saving first association information between the first association identifier and the destination MTC server;

Receiving, by the mobility management network element, a first uplink message that includes the first association identifier and the uplink MTC data; determining, according to the saved first association information, a destination MTC server corresponding to the first association identifier;

The uplink MTC data is sent to the destination MTC server.

Applying the foregoing method, the MTC-IWF can accurately send the received uplink MTC data to the destination according to the first association information between the saved first association identifier and the destination MTC server, to ensure the correctness and reliability of the uplink data communication. Security, thereby effectively solving the problem of mis-transmission and data content leakage in the uplink MTC number transmission in the prior art. The present invention provides a mobility management network element, including:

a saving unit, configured to save second association information between the second association identifier and the destination MTC-IWF;

a first uplink receiving unit, configured to receive a first uplink message that is sent by the UE and includes the second association identifier and the MTC data; a first determining unit, configured to determine, according to the saved second association information, a destination MTC-IWF corresponding to the second association identifier, where the first uplink sending unit is configured to send the second uplink message that includes the uplink MTC data to the destination MTC- The IWF, so that the destination MTC-IWF sends uplink MTC data to the destination MTC server.

The above mobility management network element may perform the above corresponding data transmission method.

The present invention also provides an MTC interworking function network element, including:

a saving unit, configured to save first association information between the first association identifier and the destination MTC server;

a first uplink receiving unit, configured to receive a first uplink message that is sent by the mobility management network element and includes the first association identifier and the MTC data;

a first determining unit, configured to determine, according to the saved first association information, a destination MTC server corresponding to the first association identifier;

The first uplink sending unit is configured to send the uplink MTC data to the destination MTC server.

The above MTC interoperation function network element can perform the above corresponding data transmission method. The present invention provides a system for data transmission, including the mobility management network element, the MTC interworking function network element, the UE, and the MTC server;

The MTC server is configured to send an MTC device trigger request.

The UE is configured to receive the MTC device trigger request, and send uplink MTC data to the MTC server according to the MTC device trigger request. The method, device, and system for data transmission provided by the present invention, when the UE receives the MTC device trigger request sent by the MTC server, and sends the first uplink message including the second association identifier and the uplink MTC data to the MTC server, And determining, by the second association information of the saved second identifier and the second association information of the MTC-IWF, the destination MTC-IWF corresponding to the second association identifier, and sending the second uplink message that includes the uplink MTC data to the destination MTC- The destination MTC-IWF may determine the destination MTC server corresponding to the associated identifier according to the saved first association identifier and the first association information of the MTC server, and send the uplink MTC data to the destination MTC server. It can be seen that the method, the device and the system for data transmission provided by the present invention ensure that the UE can accurately send the uplink MTC data to the MTC server that initiates the trigger request of the MTC device, and ensure the correctness and reliability of the data communication between the MTC server and the UE. With security, the problem of mis-transmission and data content leakage of uplink MTC number transmission between the UE and the MTC server in the prior art is effectively solved. DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in view of the drawings. 1 is a schematic flowchart of a method for data transmission provided by Embodiment 1 of the present invention;

2 is a schematic flowchart of another method for data transmission provided by Embodiment 1 of the present invention;

3 is a schematic flowchart of a method for data transmission provided by Embodiment 2 of the present invention;

4 is a schematic flowchart of a method for data transmission provided by Embodiment 3 of the present invention;

5 is a schematic flowchart of a method for data transmission provided by Embodiment 4 of the present invention;

6 is a schematic flowchart of a method for data transmission provided by Embodiment 5 of the present invention;

7 is a schematic structural diagram of a mobility management network element provided by Embodiment 6 of the present invention;

8 is a schematic structural diagram of another mobility management network element provided by Embodiment 6 of the present invention;

9 is a schematic structural diagram of a third mobility management network element provided by Embodiment 6 of the present invention;

10 is a schematic structural diagram of a fourth mobility management network element provided by Embodiment 6 of the present invention;

11 is a schematic structural diagram of a fifth mobility management network element provided by Embodiment 6 of the present invention;

12 is a schematic structural diagram of a sixth mobility management network element provided by Embodiment 6 of the present invention;

13 is a schematic structural diagram of an MTC interworking function network element provided by Embodiment 7 of the present invention;

14 is a schematic structural diagram of another MTC interworking function network element provided by Embodiment 7 of the present invention:

15 is a schematic structural diagram of a third MTC interworking function network element provided by Embodiment 7 of the present invention:

16 is a schematic structural diagram of a fourth MTC interworking function network element provided by Embodiment 7 of the present invention:

17 is a schematic structural diagram of a system for data transmission provided by Embodiment 7 of the present invention. detailed description

In order to make the objects, the technical solutions and the advantages of the present invention more apparent, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

In the embodiment of the present invention, the UE may be any one of the following, and may be static or mobile. Specifically, the terminal may include: a terminal (mobile terminal), a mobile station (mobi le station), a subscriber unit (or subscriber unit) or Station ^ cel lular phone PDA, wireless modem, wireless communication device, handheld, laptop computer A cordless phone or a wireless local loop (WLL) station, etc., may be distributed throughout the wireless network. Example 1

As shown in FIG. 1 , a method for data transmission provided by the present invention includes: -11: A mobility management network saves a second association identifier between a second association identifier and a destination MTC-IWF 12: The mobility management network element receives the first uplink message that is sent by the UE and includes the second association identifier and the uplink MTC data.

13: The mobility management network element determines, according to the saved second association information, a destination MTC_IWF corresponding to the second association identifier. The mobility management network element may create and save the second association information of the second association identifier and the MTC-IWF when the MTC server initiates the downlink MTC device trigger request to the UE.

14: The mobility management network element sends a second uplink message including the uplink MTC data to the destination MTC-IWF, so that the destination MTC-IWF sends the uplink MTC data to the destination MTC server.

It should be noted that, when the MTC server initiates a downlink MTC device trigger request to the UE, the second association identifier may be allocated by the mobility management network element;

Or, when the MTC server initiates a downlink MTC device trigger request to the UE, the second association identifier may be obtained by the mobility management network element from the downlink MTC device trigger request forwarded by the MTC-IWF;

Or, when the MTC server initiates a downlink MTC device trigger request to the UE, the second association identifier may be sent by the mobility management network element from the MTC-IWF, where the second association identifier and the MTC device trigger request are sent in the first downlink message. Obtain.

Applying the foregoing method described in FIG. 1 , the mobility management network element may determine, according to the saved second association information, a destination MTC-IWF corresponding to the second association identifier, and send a second uplink message including the uplink MTC data to the destination MTC. The IWF, so that the destination MTC-IWF sends uplink MTC data to the destination MTC server. It can be seen that, compared with the prior art, the data transmission method provided in this embodiment ensures that the UE can accurately transmit the uplink MTC data to the destination, and ensures the correctness, reliability, and security of the uplink data communication, thereby effectively solving the problem. The problem of mis-transmission and data content leakage in the uplink MTC number transmission in the prior art.

As shown in FIG. 2, the embodiment further provides a data transmission method, including:

21: The MTC-IWF saves the first association information between the first association identifier and the destination MTC server.

22: The MTC-IWF receives the first uplink message that is sent by the mobility management network element and includes the first association identifier and the uplink MTC data.

23: The MTC-IWF determines the destination MTC server corresponding to the first association identifier according to the saved first association information. The MTC-IWF may create and save the first association information of the first association identifier and the destination MTC server when the MTC server initiates a downlink MTC device trigger request to the UE.

24: The MTC-IWF sends the upstream MTC data to the destination MTC server.

It should be noted that, when the MTC server initiates a downlink MTC device trigger request to the UE, the first association identifier may be allocated by the MTC-IWF.

Alternatively, when the MTC server initiates a downlink MTC device trigger request to the UE, the association identifier may be obtained by the MTC-IWF from the downlink MTC device trigger request sent by the MTC server. It should be noted that, in this embodiment, the uplink MTC data sent by the UE may include uplink report or acknowledgement information, so that the MTC server knows that the UE successfully receives the MTC device trigger request.

Applying the method described in FIG. 2, the MTC-IWF can accurately send the received uplink MTC data to the destination according to the first association information between the saved first association identifier and the destination MTC server, and ensure the correctness of the uplink data communication. Reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission in the prior art.

Applying the method of FIG. 1 and FIG. 2, after the UE receives the MTC device trigger request sent by the MTC server, and after the UE sends the first uplink message including the second association identifier and the uplink MTC data, the mobility management network element may Determining, according to the second associated information, the destination MTC-IWF corresponding to the second associated identifier, and sending the second uplink message that includes the uplink MTC data to the destination MTC-IWF, where the destination MTC-IWF may be based on the pre-stored first associated information. Determining a destination MTC server corresponding to the first association identifier, and transmitting uplink MTC data to the destination MTC server. It can be seen that, compared with the prior art, the data transmission method provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensure the correct data communication between the MTC server and the UE. Sex, reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission between the UE and the MTC server in the prior art. Example 2

This embodiment provides a method for data transmission. It should be noted that, in this embodiment, the mobility management network element may be an MSC (Mobile Switching Centre) or an MME (Mobility Management Entity, mobile). Management entity) or SGSN (Serving GPRS Support Node).

For convenience of description, the mobility management network element in this embodiment is specifically described by taking an MSC as an example.

As shown in FIG. 3, a data transmission method provided by this embodiment includes the following steps:

201: The MTC server sends an MTC device trigger request to trigger the UE to initiate uplink MTC data transmission.

202: After receiving the MTC device trigger request, the MTC-IWF allocates the first association identifier.

The triggering request from the MTC server to the UE can be identified by the first association identifier.

203: The MTC-IWF creates and saves the first association information between the first association identifier and the MTC server that sends the MTC device trigger request.

Specifically, the first association information may be a correspondence between the first association identifier allocated by the MTC-IWF and the attribute information of the MTC server.

204: The MTC-IWF sends the first downlink message that includes the first association identifier and the MTC device trigger request to the MSC. Specifically, the first association identifier and the MTC device trigger request may be separately encapsulated in the first downlink message. Step 204: The MTC-IWF sends the first downlink message that includes the MTC device trigger request to the MSC, where the MTC device trigger request includes the first association identifier. Specifically, the MTC-IWF may write the first association identifier into a preset field in the trigger request of the MTC device to form a first downlink message that includes the trigger request of the MTC device.

205: After receiving the first downlink message that includes the first association identifier and the MTC device trigger request, the MSC creates and saves second association information between the first association identifier and the MTC-IWF.

Specifically, the second association information may be a correspondence between the first association identifier and the attribute information of the MTC-IWF. In this embodiment, for the MSC, the first association identifier may correspond to the second association identifier in 11 of FIG.

The MSC uses the first association identifier as the second association identifier, and creates and saves the second association information between the second association identifier and the MTC-IWF.

206: The MSC sends a first downlink message that includes the first association identifier and the MTC device trigger request to the UE.

207: After receiving the first downlink message, the UE initiates transmission of the uplink MTC data, and sends a first uplink message including the first association identifier and the uplink MTC data to the MSC.

The first association identifier in the first uplink message is a first association identifier that is acquired by the UE from the first downlink message, and the UE may add the first association identifier to the header or the tail of the uplink MTC data to form the The first uplink identifier of the first association identifier and the uplink MTC data.

208: After receiving the first uplink message that is sent by the UE and includes the first association identifier and the uplink MTC data, the MSC determines, according to the second association information between the saved first association identifier and the MTC-IWF, the first association identifier. Purpose

MTC- IWF.

Specifically, in the foregoing step 205, the MSC has created and saved the second association information of the first association identifier and the MTC-IWF that sends the MTC trigger request, so the MSC according to the saved first association identifier and the MTC-IWF The second association information may determine a destination MTC_IWF corresponding to the first association identifier.

209: The MSC sends a second uplink message including the first association identifier and the uplink MTC data to the destination MTC_IWF.

After receiving the second uplink message that is sent by the MSC and including the first association identifier and the uplink MTC data, the MTC-IWF determines, according to the first association information between the saved first association identifier and the MTC server, that the identifier is associated with the first association identifier. The purpose of the MTC server.

Specifically, in the foregoing step 203, the MTC-IWF has created and saved the first association information between the first association identifier and the MTC server that sends the MTC device trigger request, so according to the saved first association identifier and the MTC server. The first association information may determine a destination MTC server corresponding to the first association identifier.

211: The MTC-IWF sends the uplink MTC data to the destination MTC server.

It should be noted that, in this embodiment, the uplink MTC data sent by the UE may include uplink report or acknowledgement information, so that the MTC server knows that the UE successfully receives the MTC device trigger request. In this embodiment, only one MTC server initiates an MTC device trigger request to a UE at the same time. The method is also applicable to different MTC servers initiating an MTC device trigger request to the same UE at the same time. The MTC-IWF allocates a unique first association identifier for each MTC device trigger request to ensure that the request is triggered by different MTC devices. The processing method is the same as the above method, and details are not described herein.

In this embodiment, the MTC-IWF allocates a unique association identifier for each downlink MTC device trigger request. The advantages of the allocation mode are as follows: (1) The MTC-IWF can send the first association identifier without relying on the MTC server. The first association information with the MTC server is established to facilitate the independence of the MTC-IWF function, and conforms to the principle of layered design of the communication protocol; (2) the first association identifier assigned by the MTC-IWF is a temporary dynamic identifier. The MTC-IWF may delete the allocated first association identifier after the end of the MTC device trigger request lifetime, so as to release the repeated allocation of the storage resources and associated identifiers of the MTC-IWF. , optimized the use of resources. In this embodiment, after receiving the trigger request of the MTC device, the MTC-IWF allocates a first association identifier for each downlink MTC device trigger request, and creates and stores the first association information of the first association identifier and the MTC server, and The first downlink message that includes the first association identifier and the MTC device triggering request is sent to the MSC; the MSC creates and saves the second association information of the first association identifier and the MTC-IWF, and sends the first downlink message to the UE; After receiving the first downlink message, sending a first uplink message that includes the first association identifier and the uplink MTC data; and when the MSC receives the first uplink message, the second association between the saved first association identifier and the MTC-IWF Determining the destination MTC-IWF, and transmitting the second uplink message that includes the first association identifier and the uplink MTC data to the destination MTC-IWF; the destination MTC-IWF is further determined according to the saved first association identifier and the first association information of the MTC server. The destination MTC server sends the uplink MTC data to the selected destination MTC server. It can be seen that, compared with the prior art, the data transmission method provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensure the correct data communication between the MTC server and the UE. Sex, reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission between the UE and the MTC server in the prior art. Example 3

This embodiment provides a method for data transmission. It should be noted that, in this embodiment, the mobility management network element may be any one of MS (:, MME, or SGSN).

As shown in FIG. 4, a method for data transmission is provided in this embodiment. The method includes the following steps: 301: The MTC server sends an MTC device trigger request to trigger the UE to initiate uplink MTC data transmission.

302: After receiving the trigger request of the MTC device, the MTC-IWF allocates the first association identifier. The triggering request from the MTC server to the UE can be identified by the first association identifier.

303: The MTC-IWF creates and saves the first association information between the first association identifier and the MTC server that sends the MTC device trigger request.

304: The MTC-IWF sends a first downlink message including the first association identifier and the MTC device trigger request to the MSC. Specifically, the first association identifier and the MTC device trigger request may be separately encapsulated in the first downlink message and sent to

MSC.

Step 304: The MTC-IWF sends the first downlink message that includes the MTC device trigger request to the MSC, where the MTC device trigger request includes the first association identifier. Specifically, the MTC-IWF may encapsulate the first association identifier in the MTC device trigger request to form a first downlink message that includes the MTC device trigger request.

305: After receiving the first downlink message that includes the first association identifier and the MTC device trigger request, the MSC allocates the second association identifier.

306: The MSC creates and saves second association information between the second association identifier and the MTC-IWF.

Specifically, the second association information may be a correspondence between the second association identifier allocated by the MSC and the MTC-IWF attribute information.

307: The MSC sends a second downlink message that includes the first association identifier, the second association identifier, and the MTC device trigger request to the UE.

Specifically, the MSC may encapsulate the first association identifier, the second association identifier, and the MTC device trigger request in the second downlink message, respectively.

In step 307, the MSC may also write the second association identifier into a preset field in the trigger request of the MTC device to form a second downlink message that includes an MTC device trigger request.

308: After receiving the second downlink message sent by the MSC, the UE initiates transmission of the uplink MTC data, and sends a first uplink message including the first association identifier, the second association identifier, and the uplink MTC data to the MSC.

The first association identifier and the second association identifier in the first uplink message are respectively obtained by the UE from the received second downlink message, and the UE may add the first association identifier and the second association identifier to the uplink simultaneously or separately. The head or tail of the MTC data.

309: After receiving the first uplink message sent by the UE, the MSC determines, according to the saved second association identifier and the second association information of the MTC-IWF, the destination MTC_IWF corresponding to the second association identifier.

Specifically, in the foregoing step 306, the MSC has created and saved the second association information of the second association identifier and the MTC-IWF, so according to the saved second association identifier and the second of the MTC-IWF that sends the MTC trigger request. The association information may determine the destination MTC_IWF of the second association identifier. 310: The MSC sends a second uplink message that includes the first association identifier and the uplink MTC data to the destination MTC_IWF.

311: After receiving the second uplink message that includes the first association identifier and the uplink MTC data, the MTC-IWF determines the destination MTC server corresponding to the first association identifier according to the saved first association identifier and the first association information of the MTC server.

Specifically, in step 303, the MTC-IWF has created and saved the first association identifier and the first association information of the MTC server that sends the MTC device trigger request, so according to the saved first association identifier and the sending MTC device trigger request. The first association information of the MTC server may determine a destination MTC server corresponding to the first association identifier.

312: The MTC-IWF sends the uplink MTC data to the destination MTC server.

It should be noted that, in this embodiment, the uplink MTC data sent by the UE may include uplink report or acknowledgement information, so that the MTC server knows that the UE successfully receives the MTC device trigger request.

In this embodiment, only one MTC server initiates an MTC device trigger request to a UE at the same time. The method is also applicable to different MTC servers initiating an MTC device trigger request to the same UE at the same time. The MSC allocates a second association identifier for each MTC device trigger request, and the MTC-IWF allocates a first association identifier for each MTC device trigger request to ensure that the triggering request is triggered for different MTC devices, and the processing method and the foregoing method The same, no longer repeat them.

In this embodiment, the MTC-IWF allocates an association identifier for each downlink MTC device triggering request. The advantages of the allocation mode are as follows: (1) The MTC-IWF can be established without relying on the MTC server to deliver the first association identifier. The first association information with the MTC server is used to facilitate the independence of the MTC-IWF function implementation, and conforms to the principle of layered design of the communication protocol; (2) the first association identifier assigned by the MTC-IWF is a temporary dynamic identifier, only in the The MTC-IWF can delete the allocated first association identifier after the end of the MTC device trigger request lifetime, so as to release the repeated allocation of the storage resources and associated identifiers of the MTC-IWF. The use of resources.

In addition, in this embodiment, the MSC allocates a second association identifier for each MTC device trigger request, and the advantage of the allocation manner is the same as the advantage that the foregoing MTC-IWF allocates an association identifier for each downlink MTC device trigger request. No longer. In this embodiment, after receiving the trigger request of the MTC device, the MTC-IWF allocates a first association identifier for each downlink MTC device trigger request, and creates and stores the first association information of the first association identifier and the MTC server, and The first downlink message that includes the first association identifier and the MTC device trigger request is sent to the MSC. The MSC allocates a second association identifier after receiving the first downlink message, and creates and saves the second association identifier and the MTC-IWF. Transmitting, by the second association information, the second downlink message that includes the first association identifier, the second association identifier, and the MTC device trigger request to the UE; after receiving the second downlink message, the UE sends the foregoing first association identifier, and the second a first uplink message of the association identifier and the uplink MTC data; when receiving the first uplink message, the MSC determines the destination according to the saved second association identifier and the second association information of the MTC-IWF The MTC-IWF sends a second uplink message including the first association identifier and the uplink MTC data to the destination MTC-IWF; the destination MTC-IWF determines the destination MTC according to the saved first association identifier and the first association information of the MTC server. The server sends the uplink MTC data to the selected destination MTC server. It can be seen that, compared with the prior art, the data transmission method provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensures the correct data communication between the MTC server and the UE. Sex, reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission between the UE and the MTC server in the prior art. Example 4

As shown in FIG. 5, a method for data transmission is provided in this embodiment. The method specifically includes the following steps:

401: The MTC server sends an MTC device trigger request to trigger the UE to initiate uplink MTC data transmission.

Specifically, the device identifier is included in the triggering request of the MTC device, and the device identifier may be a fixed attribute information of the device, such as a UE identifier, an MTC server identifier, an MTC server domain name, an MTC application domain name, or an MTC device trigger request reference number. For example, the device identifier is taken as an example of the UE identifier as an example.

402: After receiving the MTC device trigger request, the MTC-IWF creates and saves the first association information of the UE identifier and the MTC server that sends the MTC device trigger request.

Specifically, the first association information may be a correspondence between the UE identifier created by the MTC-IWF and the attribute information of the MTC server, and the MTC-IWF obtains the UE identifier from the MTC device trigger request.

403: The MTC-IWF sends an MTC device trigger request to the MSC.

404: After receiving the MTC device trigger request, the MSC creates and saves the second association information of the UE identifier and the MTC-IWF that sends the MTC device trigger request.

Specifically, the second association information may be a correspondence between the UE identifier created by the MSC and the MTC-IWF attribute information, and the MTC-IWF obtains the UE identifier from the MTC device trigger request.

405: The MSC sends the received MTC device trigger request to the UE.

406: After receiving the MTC device triggering request, the UE initiates transmission of the uplink MTC data, and sends a first uplink message including the UE identifier and the uplink MTC data to the MSC.

Specifically, the UE identifier in the first uplink message that includes the UE identifier and the uplink MTC data is obtained by the UE from the received MTC device trigger request, and the UE may add the UE identifier in the MTC device trigger request to the uplink MTC data. The header or the tail forms a first uplink message including the UE identity and the uplink MTC data. 407: After receiving the first uplink message that is sent by the UE and including the UE identifier and the uplink MTC data, the MSC determines the destination MTC_IWF corresponding to the UE identifier according to the saved UE identifier and the second association information of the MTC-IWF.

Specifically, in the foregoing step 404, the MSC has created and saved the second association information of the UE identifier and the MTC-IWF, and the destination MTC_IWF corresponding to the UE identifier may be determined according to the second association information of the UE identifier and the MTC-IWF. .

It should be noted that the foregoing step 404-step 407 can also be replaced by the following steps 404'-step 407', which are as follows:

404 ′: After receiving the MTC device trigger request, the MSC allocates a second association identifier, and creates and saves the second association identifier and the second association information of the MTC-IWF that sends the MTC device trigger request.

Specifically, the second association information may be a correspondence between the second association identifier created by the MSC and the MTC-IWF attribute information.

405 ': The MSC sends a second downlink message including the second association identifier and the MTC device trigger request to the UE.

406 ′: After receiving the second downlink message that includes the second association identifier and the MTC device triggering request, the UE initiates transmission of the uplink MTC data, and sends the first uplink message that includes the UE identifier, the second association identifier, and the uplink MTC data to the UE. MS (:.

Specifically, the UE identifier in the first uplink message is obtained by the UE from the received MTC device trigger request, and the UE may add the UE identifier and the second association identifier to the head or the tail of the uplink MTC data simultaneously or separately. The first uplink message includes a UE identifier, a second association identifier, and uplink MTC data.

407 ′: After receiving the first uplink message that is sent by the UE and including the UE identifier, the second association identifier, and the uplink MTC data, the MSC determines, according to the saved second association identifier and the second association information of the MTC-IWF, the second association identifier. Corresponding purpose MTC-IWF.

Specifically, in the foregoing step 404 ′, the MSC has created and saved the second association information of the second association identifier and the MTC-IWF, and therefore, according to the second association identifier of the second association identifier and the MTC-IWF, the second association information may be determined. The destination MTC_IWF corresponding to the second association identifier.

408: The MSC sends a second uplink message including the UE identifier and the uplink MTC data to the selected destination MTC_IWF.

409: After receiving the second uplink message that is sent by the MSC and including the UE identifier and the uplink MTC data, the MTC-IWF determines the destination MTC server corresponding to the UE identifier according to the saved UE identifier and the first association information of the MTC server.

Specifically, in step 402, the MTC-IWF has created and saved the first association information of the UE identifier and the MTC server that sends the MTC device trigger request in the process of triggering the request sending of the MTC device, so according to the saved UE identifier. The first association information with the MTC server may determine a destination MTC server corresponding to the UE identity.

410: The MTC-IWF sends the uplink MTC data to the destination MTC server.

It should be noted that, in this embodiment, the uplink MTC data sent by the UE may include uplink report or acknowledgement information, so that the MTC server knows that the UE successfully receives the MTC device trigger request. In this embodiment, only one MTC server initiates an MTC device trigger request to a UE at the same time as an example. The method is also applicable to different MTC servers initiating an MTC device trigger request to the same UE at the same time. In the scenario, each MTC server initiates an MTC device trigger request to the same UE by using different device identifiers, and is used to distinguish different MTC device trigger requests, so that when the destination MTC-IWF receives multiple device identifiers and uplink MTC data. In the second uplink message, the destination MTC-IWF can find the destination MTC server corresponding to each device identifier according to each device identifier, and send each uplink MTC data to the corresponding destination MTC server, and the processing method is the same as above. This will not be repeated here.

In this embodiment, after receiving the trigger request of the MTC device, the MTC-IWF creates the first association information with the MTC server according to the UE identifier, and sends an MTC device trigger request to the MSC; the MSC creates the first and the MTC-IWF according to the UE identifier. The second association information is sent to the UE, and the UE sends the MTC device trigger request to the UE. After receiving the MTC device trigger request, the UE sends the first uplink message including the UE identifier and the uplink MTC data. When the MSC receives the first uplink message, the MSC saves according to the MSC. The second association information of the UE identifier and the MTC-IWF determines the destination MTC-IWF corresponding to the UE identifier, and sends a second uplink message including the UE identifier and the uplink MTC data to the destination MTC-IWF; the destination MTC-IWF is further based on The first association information of the saved UE identifier and the MTC server determines the destination MTC server corresponding to the UE identifier, and sends the uplink MTC data to the destination MTC server. It can be seen that, compared with the prior art, the data transmission method provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensure the correct data communication between the MTC server and the UE. Sex, reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission between the UE and the MTC server in the prior art. Example 5

As shown in FIG. 6, the method for data transmission is provided in this embodiment. The method includes the following steps: 501: The MSC saves pre-configured routing information of uplink MTC data transmission from the UE to the MTC-IWF.

502: The MTC server sends an MTC device trigger request to the UE, to trigger the UE to initiate uplink MTC data transmission. Specifically, the MTC device triggering request may include a device identifier, where the device identifier may be a fixed attribute information of the device, such as a UE identifier, an MTC server identifier, an MTC server domain name, an MTC application domain name, or an MTC device trigger request reference number, and the like. For example, the device identifier is taken as an example of the UE identifier as an example.

503: After receiving the trigger request of the MTC device, the MTC-IWF creates and saves association information between the UE identifier and the MTC server that sends the MTC device trigger request. Specifically, the association information may be a correspondence between the UE identifier created by the MTC-IWF and the attribute information of the MTC server, and the MTC-IWF obtains the UE identifier from the MTC device trigger request.

The foregoing steps 502 and 503 may be replaced by the following steps 502 ' and 503 ' as follows: 502 ': The MTC-IWF saves the pre-configured routing information of the uplink MTC data transmission from the UE to the destination MTC server.

503 ': The MTC server sends an MTC device trigger request to the UE to trigger the UE to initiate uplink MTC data transmission.

The MTC device triggering request may include a device identifier, where the device identifier may be a fixed attribute information of the device, such as a UE identifier, an MTC server identifier, an MTC server domain name, an MTC application domain name, or an MTC device trigger request reference number, or In this embodiment, only the device identifier is used as the UE identifier as an example for specific description.

504: The MTC-IWF sends an MTC device trigger request to the MSC.

505: The MSC forwards the MTC device trigger request to the UE.

506: After receiving the MTC device triggering request, the UE initiates transmission of the uplink MTC data, and sends a first uplink message including the UE identifier and the uplink MTC data to the MSC.

Specifically, the UE identifier in the first uplink message that includes the UE identifier and the uplink MTC data may be obtained by the UE from the received MTC device trigger request, and the UE may add the UE identifier in the MTC device trigger request to the uplink MTC data. The header or trailer forms a first uplink message containing the UE identity and the uplink MTC data. The identifier of the UE included in the first uplink message may also be an identifier stored by the UE itself.

507: After receiving the first uplink message that is sent by the UE and including the UE identifier and the uplink MTC data, the MSC queries the pre-configured routing information that is sent by the UE to the MTC-IWF uplink MTC data according to the UE identifier, and determines the destination corresponding to the UE identifier. MTC-IWF.

Specifically, in step 501, the pre-configured routing information of the UE to the MTC-IWF uplink MTC data transmission has been saved in the MSC, so that the UE identifier can be transmitted in the pre-configured uplink MTC data from the UE to the MTC-IWF according to the UE identifier. The destination MTC_IWF corresponding to the UE identifier is found in the routing information.

508: The MSC sends a second uplink message including the UE identifier and the uplink MTC data to the destination MTC_IWF.

509: After receiving the second uplink message that is sent by the MSC and including the UE identifier and the uplink MTC data, the MTC-IWF determines the destination MTC server corresponding to the UE identifier according to the saved UE identifier and the association information of the MTC server.

Specifically, in the foregoing step 503, since the MTC-IWF has created and saved the association information of the UE identifier and the MTC server that sends the MTC trigger request, the association information of the saved UE identifier and the MTC server may be determined to correspond to the UE identifier. MTC server. Step 509 is further as follows: After receiving the second uplink message that is sent by the MSC and including the UE identifier and the uplink MTC data, the MTC-IWF determines, according to the pre-configured routing information of the uplink MTC data transmitted by the UE to the destination MTC server, the identifier corresponding to the identifier of the UE. The purpose of the MTC server.

510: The MTC-IWF sends the uplink MTC data to the destination MTC server.

In this embodiment, only one MTC server initiates an MTC device trigger request to a UE at the same time as an example. The method is also applicable to different MTC servers initiating an MTC device trigger request to the same UE at the same time. In the scenario, each MTC server initiates an MTC device trigger request to the same UE by using different device identifiers, and is used to distinguish different MTC device trigger requests, so that when the destination MTC-IWF receives multiple device identifiers and uplink MTC data. In the second uplink message, the destination MTC-IWF can find the destination MTC server corresponding to each device identifier according to each device identifier, and send each uplink MTC data to the corresponding destination MTC server, and the processing method and the steps in this embodiment The same, the details are not described here, and the processing method is the same as the above method, and will not be described again.

In this embodiment, the MSC pre-configures the routing information that is transmitted by the UE to the MTC-IWF uplink MTC data. After receiving the MTC device trigger request, the MTC-IWF creates the association information between the UE identifier and the MTC server, and triggers the MTC device to trigger the request. Sending to the MSC; the MSC forwards the MTC device trigger request to the UE; after receiving the MTC device trigger request, the UE sends a first uplink message including the UE identifier and the uplink MTC data; when the MSC receives the first uplink message, according to the saved Determining, by the UE, the routing information of the MTC-IWF uplink MTC data, the destination MTC-IWF corresponding to the UE identifier, and transmitting the second uplink message including the UE identifier and the uplink MTC data to the destination MTC-IWF; the destination MTC-IWF And determining, according to the saved UE identifier and the association information of the MTC server, the destination MTC server corresponding to the UE identifier, and sending the uplink MTC data to the destination MTC server. It can be seen that, compared with the prior art, the data transmission method provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensure the correct data communication between the MTC server and the UE. Sex, reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission between the UE and the MTC server in the prior art.

A person skilled in the art can easily obtain the combination of the foregoing method embodiments from the above method embodiments. For example, the MTC-IWF processing part and the MTC processing part can be combined with each other in different embodiments, and the mutual steps between different steps in different embodiments. In combination, these combinations can also perform data transmission between the UE and the MTC, between the MTC and the MTC-IWF, between the MTC-IWF and the MTC server. For these combinations, they will not be described here.

Example 6

This embodiment provides a mobility management network element, which may be an MS (:, SGSN, or MME. As shown in FIG. 7, the mobility management network element includes: The saving unit 601 is configured to save the second association information between the second association identifier and the destination MTC-IWF. The first uplink receiving unit 602 is configured to receive the first uplink that is sent by the UE and includes the second association identifier and the uplink MTC data. Message

The first determining unit 603 is configured to determine, according to the saved second association information, a destination MTC-IWF corresponding to the second association identifier;

The first uplink sending unit 604 is configured to send the second uplink message that includes the uplink MTC data to the destination MTC-IWF, so that the destination MTC-IWF sends the uplink MTC data to the destination MTC server.

For the operation process of the mobility management network element shown in FIG. 7, refer to the implementation process of the method in Embodiment 1 above. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

Further, as shown in FIG. 8, the mobility management network element further includes:

The first downlink receiving unit 605 is configured to receive the first downlink message sent by the destination MTC-IWF before the saving unit 601 saves the second association information, where the first downlink message includes an MTC device trigger request, and the MTC device trigger request includes Second associated identifier;

The first processing unit 607 is configured to acquire a second association identifier in the first downlink message, and create second association information between the second association identifier and the destination MTC-IWF.

The first downlink sending unit 609 is configured to send the first downlink message to the UE before the first uplink receiving unit 602 receives the first uplink message;

The second uplink message further includes a second association identifier.

For the operation process of the mobility management network element shown in Fig. 8, refer to the implementation process of the methods in the above embodiments 2 and 4. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

Further, as shown in FIG. 9, the mobility management network element may further include:

The second downlink receiving unit 611 is configured to receive the first downlink message sent by the destination MTC-IWF before the saving unit 601 saves the second association information, where the first downlink message includes the second association identifier and the MTC device trigger request.

The second processing unit 613 is configured to acquire a second association identifier included in the first downlink message, and create and save second association information between the second association identifier and the destination MTC-IWF.

The second downlink sending unit 615 is configured to send the first downlink message to the UE before the first uplink receiving unit 602 receives the first uplink message.

The second uplink message further includes a second association identifier.

For the operation process of the mobility management network element shown in FIG. 9, refer to the implementation process of the method in Embodiment 2 above. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

Further, as shown in FIG. 10, the mobility management network element may further include: The third downlink receiving unit 617 is configured to receive the first downlink message sent by the destination MTC-IWF before the saving unit 601 saves the second association information, where the first downlink message includes an MTC device trigger request, and the MTC device trigger request includes An associated identifier;

a first allocation unit 619, configured to allocate a second association identifier;

The first creating unit 621 is configured to create second association information between the second association identifier and the destination MTC-IWF. The third downlink sending unit 623 is configured to send the UE to the UE before the first uplink receiving unit 602 receives the first uplink message. Sending a second downlink message, where the second downlink message includes a second association identifier and an MTC device trigger request;

The first uplink message further includes the first association identifier, and the second uplink message further includes the first association identifier.

For the operation process of the mobility management network element shown in FIG. 10, refer to the implementation process of the method in Embodiment 4 above. In the above device embodiment, the same terms as in the method embodiment have the same meanings.

Further, as shown in FIG. 11, the mobility management network element may further include:

The fourth downlink receiving unit 625 is configured to receive the first downlink message sent by the destination MTC-IWF before the saving unit 601 saves the second association information, where the first downlink message includes the first association identifier and the MTC device trigger request.

a second allocation unit 627, configured to allocate a second association identifier;

The second creating unit 629 is configured to create second association information between the second association identifier and the destination MTC-IWF. The fourth downlink sending unit 631 is configured to send the UE to the UE before the first uplink receiving unit 602 receives the first uplink message. Sending a second downlink message, where the second downlink message includes a second association identifier, a first association identifier, and an MTC device trigger request, where the first uplink message further includes a first association identifier, and the second uplink message further includes The first associated identifier. For the operation process of the mobility management network element shown in FIG. 11, refer to the implementation process of the method in Embodiment 3 above. In the above device embodiment, the same terms as in the method embodiment have the same meanings.

The foregoing second association identifier may be at least one of a UE identifier, an MTC server identifier, an MTC server domain name, an MTC application domain name, or an MTC device trigger request reference number.

Further, as shown in FIG. 12, the foregoing saving unit 601 is specifically configured to save routing information of the uplink MTC data transmission from the UE to the destination MTC-IWF, where the second association information is routing information, and the second association identifier is The identity of the UE;

The mobility management network element may further include:

a fifth downlink receiving unit 633, configured to receive an MTC device trigger request sent by the destination MTC-IWF;

The fifth downlink sending unit 635 is configured to send an MTC device trigger request to the UE before the first uplink receiving unit 602 receives the first uplink message.

The second uplink message further includes a second association identifier. For the operation process of the mobility management network element shown in FIG. 12, refer to the implementation process of the method in Embodiment 5 above. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

The mobility management network element provided in this embodiment is configured to: when the UE receives the MTC device trigger request sent by the MTC server, and after the UE sends the first uplink message that includes the second association identifier and the uplink MTC data, And determining, by the second association information of the saved second identifier and the second association information of the MTC-IWF, the destination MTC-IWF corresponding to the second association identifier, and sending the second uplink message that includes the uplink MTC data to the destination MTC- The IWF, so that the destination MTC-IWF sends uplink MTC data to the destination MTC server. It can be seen that, compared with the prior art, the mobility management network element provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensures data communication between the MTC server and the UE. Correctness, reliability and security, thus effectively solving the problem of mis-transmission and data content leakage of uplink MTC number transmission between UE and MTC server in the prior art. Example 7

As shown in FIG. 13, this embodiment provides an MTC interworking function network element, including:

The saving unit 701 is configured to save the first association information between the first association identifier and the destination MTC server, where the first uplink receiving unit 702 is configured to receive the first association identifier and the uplink MTC data that are sent by the mobility management network element. First uplink message;

The first determining unit 703 is configured to determine, according to the saved first association information, a destination MTC server corresponding to the first association identifier.

The first uplink sending unit 704 is configured to send the uplink MTC data to the destination MTC server.

For the operation process of the MTC interoperation function network element shown in Figure 13, refer to the implementation process of the method in Embodiment 1 above. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

Further, as shown in FIG. 14, the MTC interworking function network element may further include:

The first downlink receiving unit 705 is configured to receive an MTC device trigger request sent by the destination MTC server before the saving unit 701 saves the first association information.

a first allocation unit 707, configured to allocate a first association identifier;

The first creating unit 709 is configured to create first association information between the first association identifier and the destination MTC server. The first downlink sending unit 711 is configured to include, before the first uplink receiving unit 702 receives the first uplink message. The first downlink identifier of the first association identifier and the MTC device trigger request is sent to the mobility management network element.

For the operation process of the MTC interoperation function network element shown in Figure 14, refer to the implementation process of the methods in the above embodiments 2 and 3. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

Further, as shown in FIG. 15, the MTC interoperation function network element may further include: The second downlink receiving unit 713 is configured to receive an MTC device trigger request sent by the destination MTC server before the saving unit 701 saves the first association information, where the MTC device trigger request includes the first association identifier;

The first obtaining unit 715 is configured to acquire a first association identifier in the MTC device trigger request.

The second creating unit 717 is configured to create first association information of the first association identifier and the destination MTC server, and the second downlink sending unit 719 is configured to trigger the MTC device to trigger the request before the first uplink receiving unit 702 receives the first uplink message. Send to the mobility management network element.

For the operation process of the MTC interoperation function network element shown in Figure 15, refer to the implementation process of the methods in the above embodiments 4 and 5. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

The first association identifier may be at least one of a UE identifier, an MTC server identifier, an MTC server domain name, an MTC application domain name, or an MTC device trigger request reference number.

Further, as shown in FIG. 16, the saving unit 701 may be specifically configured to save routing information of the uplink MTC data transmission from the UE to the destination MTC server, where the first association information is routing information, and the first association identifier is used. The identity of the UE;

The MTC interworking function network element may further include:

The third downlink receiving unit 721 is configured to receive an MTC device trigger request sent by the destination MTC server, where the third downlink sending unit 723 is configured to send the MTC device trigger request to the mobile before the first uplink receiving unit 702 receives the first uplink message. Sex management network element.

Figure 16 shows the operation process of the MTC interoperation function network element. See the implementation process of the method in the above embodiment 5. In the above device embodiments, the same terms as in the method embodiments have the same meanings.

The MTC interworking function network element provided by the embodiment, after receiving the second uplink message that is sent by the mobility management network element and includes the first association identifier and the uplink MTC data, according to the saved first association identifier and the MTC server The first association information selects the destination MTC server corresponding to the first association identifier, and sends the uplink MTC data to the destination MTC server. It can be seen that, compared with the prior art, the MTC interworking function network element provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensures data communication between the MTC server and the UE. The correctness, reliability and security of the prior art effectively solve the problem of mis-transmission and data content leakage in the uplink MTC number transmission between the UE and the MTC server in the prior art. As shown in FIG. 17, the present invention further provides a system for data transmission, which specifically includes the mobility management network element 600 in the foregoing embodiment 6, and the MTC interoperation function network element 700, UE800, and MTC in the foregoing seventh embodiment. Server 900.

The UE 800 is configured to receive an MTC device trigger request sent by the mobility management network element 600. The UE 800 is further configured to: after receiving the downlink MTC device trigger request sent by the MTC server 900, initiate uplink MTC data transmission according to the MTC device trigger request, and send the first uplink message including the association identifier and the uplink MTC data to the mobility. Management network element 600;

The mobility management network element 600 is configured to: after receiving the first uplink message that includes the association identifier and the uplink MTC data, determine, according to the saved association identifier, the second association information of the MTC interoperation function network element 700, and the association identifier. Corresponding MTC interoperation function network element 700, and sending a second uplink message including the association identifier and the uplink MTC data to the MTC interoperation function network element 700;

The MTC interoperation function network element 700 is configured to: after receiving the second uplink message that includes the uplink MTC data, determine, according to the saved association identifier, the first association information of the MTC server 900, the MTC server 900 corresponding to the association identifier, And sending the uplink MTC data to the MTC server 900;

The MTC server 900 is configured to send a downlink MTC device trigger request, and is further configured to receive the uplink MTC data sent by the MTC interworking function network element 700 after sending the MTC device trigger request.

The present invention provides a data transmission system, so that after receiving the MTC device trigger request sent by the MTC server, the UE sends a first uplink message including the association identifier and the uplink MTC data, and the mobility management network element according to the saved association. Determining, by the second association information of the MTC interoperation function network element, the destination MTC interoperation function network element corresponding to the association identifier, and sending the second uplink message including the uplink MTC data to the destination MTC interoperation function network element, the destination MTC The interworking function network element may determine the destination MTC server corresponding to the association identifier according to the saved association identifier and the first association information of the MTC server, and send the uplink MTC data to the destination MTC server. It can be seen that, compared with the prior art, the data transmission system provided in this embodiment ensures that the UE can accurately send the uplink MTC data to the MTC server that initiates the MTC device trigger request, and ensures the correct data communication between the MTC server and the UE. Sex, reliability and security, which effectively solves the problem of mis-transmission and data content leakage in the uplink MTC number transmission between the UE and the MTC server in the prior art.

Those skilled in the art can understand that the device embodiments in the embodiments of the present invention may be used to implement the method described in the method embodiments. The system embodiments in the embodiments of the present invention may be implemented by using the devices in the device embodiments, or may be used. The method described in the method embodiment is performed. A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are included in the spirit and principles of the present invention, should be included in the scope of the present invention. Inside.

Claims

claims

1. A data transmission method, characterized by including:

Save the second association information between the second association identifier and the destination machine type communication interoperability function network element MTC-IWF; receive the first uplink sent by the user equipment UE including the second association identifier and the uplink machine type communication MTC data. information;

Determine the destination MTC-IWF corresponding to the second association identifier according to the saved second association information;

The second uplink message containing the uplink MTC data is sent to the destination MTC-IWF, so that the destination MTC-IWF sends the uplink MTC data to the destination MTC server.

2. The method according to claim 1, characterized in that, before saving the second association information between the second association identifier and the destination MTC-IWF, further comprising - receiving the first message sent by the destination MTC-IWF. A downlink message, the first downlink message includes an MTC device trigger request, and the MTC device trigger request includes the second association identifier;

Obtain the second association identifier in the first downlink message, create the second association identifier and the destination

The second association information between MTC-IWF;

Before receiving the first uplink message containing the second association identifier and uplink machine type communication MTC data sent by the user equipment UE, the method further includes:

Send the first downlink message to the UE;

Wherein, the second uplink message also includes the second association identifier.

3. The method according to claim 1, characterized in that, before saving the second association information between the second association identifier and the target MTC-IWF, further comprising:

Receive the first downlink message sent by the destination MTC-IWF, where the first downlink message includes the second association identifier and the MTC device trigger request;

Obtain the second association identifier contained in the first downlink message, and create the second association identifier and the destination

The second association information between MTC-IWF; before receiving the first uplink message sent by the user equipment UE containing the second association identifier and uplink machine type communication MTC data, further includes:

Send the first downlink message to the UE;

4. The method according to claim 1, characterized in that, before saving the second association information between the second association identifier and the target MTC-IWF, further comprising:

Receive the first downlink message sent by the destination MTC-IWF, the first downlink message includes an MTC device trigger request, and the MTC device trigger request includes a first association identifier;

assign the second association identifier;

Create the second association information between the second association identifier and the destination MTC-IWF;

Send a second downlink message to the UE, where the second downlink message includes the second association identifier and the MTC device trigger request;

Wherein, the first uplink message further includes the first association identifier, and the second uplink message further includes the first association identifier.

5. The method according to claim 1, characterized in that, before saving the second association information between the second association identifier and the target MTC-IWF, further comprising:

Receive the first downlink message sent by the destination MTC-IWF, where the first downlink message includes the first association identifier and the MTC device trigger request;

assign the second association identifier;

Send a second downlink message to the UE, where the second downlink message includes the second association identifier, the first association identifier, and the MTC device trigger request;

6. The method according to claim 1, characterized in that said saving the second association information between the second association identifier and the target MTC-IWF includes - saving the pre-configured link from the UE to the target MTC - Routing information for IWF's uplink MTC data transmission, wherein the second association information is the routing information, and the second association identifier is the identifier of the UE; Before receiving the first uplink message containing the second association identifier and uplink machine type communication MTC data sent by the user equipment UE, the method further includes:

Receive the MTC device trigger request sent by the destination MTC-IWF;

Send the MTC device trigger request to the UE;

7. The method according to any one of claims 1 to 5, characterized in that the second association identifier includes a UE identifier,

At least one of the MTC server identification, MTC server domain name, MTC application domain name, or MTC device trigger request reference number.

8. A data transmission method, characterized by including:

Save the first association information between the first association identifier and the destination machine type communication MTC server;

Receive the first uplink message containing the first association identifier and uplink machine type communication MTC data sent by the mobility management network element;

Determine the destination MTC server corresponding to the first association identifier according to the saved first association information; send the uplink MTC data to the destination MTC server.

9. The method according to claim 8, characterized in that, before saving the first association information between the first association identifier and the destination MTC server, it includes:

Receive the MTC device trigger request sent by the destination MTC server;

Assign the first association identifier;

Create first association information between the first association identifier and the destination MTC server;

Before receiving the first uplink message containing the first association identifier and uplink machine type communication MTC data sent by the mobility management network element, further including:

Send a first downlink message including the first association identifier and the MTC device trigger request to the mobility management network element.

10. The method according to claim 8, characterized in that, before saving the first association information between the first association identifier and the destination MTC server, it includes: Receive an MTC device trigger request sent by the destination MTC server, where the MTC device trigger request includes the first association identifier;

Obtain the first association identifier in the MTC device trigger request;

Send the MTC device trigger request to the mobility management network element.

11. The method according to claim 8, wherein said saving the first association information between the first association identifier and the destination MTC server includes:

Save preconfigured routing information for uplink MTC data transfer from the UE to the destination MTC server, wherein the first association information is the routing information, and the first association identifier is the identifier of the UE;

Before receiving the first uplink message containing the first association identifier and uplink machine type communication MTC data sent by the mobility management network element, further including: receiving an MTC device trigger request sent by the destination MTC server;

Send the MTC device trigger request to the mobility management network element.

12. The method according to any one of claims 8 to 10, characterized in that the first association identifier includes a UE identifier,

13. A mobility management network element device, characterized in that it includes:

A storage unit configured to save the second association information between the second association identifier and the destination machine type communication interoperability function network element MTC-IWF;

A first uplink receiving unit configured to receive a first uplink message containing the second association identifier and uplink machine type communication MTC data sent by the user equipment UE;

A first determination unit, configured to determine the destination MTC-IWF corresponding to the second association identifier according to the saved second association information;

A first uplink sending unit, configured to send a second uplink message containing the uplink MTC data to the destination.

MTC-IWF, so that the destination MTC-IWF sends the uplink MTC data to the destination MTC server.

14. The device according to claim 13, further comprising:

The first downlink receiving unit is configured to receive the destination before the saving unit saves the second associated information.

The first downlink message sent by MTC-IWF, the first downlink message includes an MTC device trigger request, and the MTC device trigger request includes the second association identifier;

A first processing unit, configured to obtain the second association identifier in the first downlink message, and create the second association information between the second association identifier and the destination MTC-IWF;

A first downlink sending unit, configured to send the first downlink message to the UE before the first uplink receiving unit receives the first uplink message;

15. The device according to claim 13, further comprising:

The second downlink receiving unit is configured to receive the destination before the saving unit saves the second associated information.

The first downlink message sent by MTC-IWF, the first downlink message includes the second association identifier and the MTC device trigger request;

A second processing unit, configured to obtain the second association identifier contained in the first downlink message, and create the second association information between the second association identifier and the destination MTC-IWF;

A second downlink sending unit, configured to send the first downlink message to the UE before the first downlink receiving unit receives the first uplink message;

16. The device according to claim 13, further comprising:

The third downlink receiving unit is configured to receive the destination before the saving unit saves the second associated information.

The first downlink message sent by MTC-IWF, the first downlink message includes an MTC device trigger request, and the MTC device trigger request includes a first association identifier;

A first allocation unit, configured to allocate the second association identification;

A first creation unit, configured to create the second association information between the second association identifier and the target MTC-IWF;

A third downlink sending unit, configured to send a second downlink message to the UE before the first uplink receiving unit receives the first uplink message, where the second downlink message includes the second association identifier and the MTC device trigger request; Wherein, the first uplink message further includes the first association identifier, and the second uplink message further includes the first association identifier.

17. The device according to claim 13, further comprising:

The fourth downlink receiving unit is configured to receive the first downlink message sent by the destination MTC-IWF, where the first downlink message includes the first association identifier and the MTC device trigger request;

a second allocation unit, configured to allocate the second association identifier;

A second creation unit, configured to create the second association information between the second association identifier and the target MTC-IWF;

A fourth downlink sending unit, configured to send a second downlink message to the UE before the first uplink receiving unit receives the first uplink message, where the second downlink message includes the second association identifier, The first association identifier, and the MTC device trigger request;

18. The device according to claim 13, characterized in that:

The saving unit is configured to save preconfigured routing information for uplink MTC data transmission from the UE to the destination MTC-IWF, where the second association information is the routing information, and the second association The identifier is the identifier of the UE; further including:

The fifth downlink receiving unit is used to receive the MTC device trigger request sent by the destination MTC-IWF;

A fifth downlink sending unit, configured to send the MTC device trigger request to the UE before the first uplink receiving unit receives the first uplink message;

19. The apparatus according to any one of claims 13 to 17, wherein the second association identifier includes a UE identifier, an MTC server identifier, an MTC server domain name, an MTC application domain name, or an MTC device trigger request reference number. at least one.

20. A machine type communication MTC interoperability function network element device, which is characterized by including:

A saving unit, configured to save the first association information between the first association identifier and the destination machine type communication MTC server; A first uplink receiving unit configured to receive a first uplink message containing the first association identifier and uplink machine type communication MTC data sent by the mobility management network element;

A first determination unit, configured to determine the destination MTC server corresponding to the first association identification according to the saved first association information;

The first uplink sending unit is used to send the uplink MTC data to the destination MTC server.

21. The device according to claim 20, further comprising:

The first downlink receiving unit is configured to receive the MTC device trigger request sent by the destination MTC server before the saving module saves the first association information;

A first allocation unit, configured to allocate the first association identifier;

A first creation unit, configured to create first association information between the first association identifier and the destination MTC server; A first downlink sending unit, configured to receive the first uplink in the first receiving module Before the message, a first downlink message including the first association identifier and the MTC device trigger request is sent to the mobility management network element.

22. The device according to claim 20, further comprising:

The second downlink receiving unit is configured to receive the MTC device trigger request sent by the destination MTC server before the storage unit saves the first association information, where the MTC device trigger request includes the first association identifier;

A first acquisition unit, configured to acquire the first association identifier in the MTC device trigger request;

a second creation unit, configured to create first association information between the first association identifier and the destination MTC server; a second downlink sending unit, configured to receive the first uplink message before the first uplink receiving unit will be described

The MTC device trigger request is sent to the mobility management network element.

23. The device according to claim 20, characterized in that:

The saving unit is configured to save preconfigured routing information for uplink MTC data transfer from the UE to the destination MTC server, where the first association information is the routing information, and the first association identifier is the identity of the UE;

Further includes:

The third downlink receiving unit is configured to receive the MTC device trigger request sent by the destination MTC server; the third downlink sending unit is configured to send the MTC device to the first uplink message before the first uplink receiving unit receives the first uplink message. The trigger request is sent to the mobility management network element.

24. The apparatus according to any one of claims 20 to 22, wherein the first association identifier includes a UE identifier, an MTC server identifier, an MTC server domain name, an MTC application domain name, or an MTC device trigger request reference number. at least one.

25. A data transmission system, characterized in that the system includes the mobility management network element described in any one of claims 13-19, and the MTC interoperability described in any one of claims 20-24. Functional network element, user equipment UE and MTC server;

The MTC server is used to send a machine type communication MTC device trigger request;

The UE is configured to receive the MTC device trigger request, and send uplink MTC data to the MTC server according to the MTC device trigger request.