WO2011082524A1 - Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité - Google Patents

Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité Download PDF

Info

Publication number
WO2011082524A1
WO2011082524A1 PCT/CN2010/070049 CN2010070049W WO2011082524A1 WO 2011082524 A1 WO2011082524 A1 WO 2011082524A1 CN 2010070049 W CN2010070049 W CN 2010070049W WO 2011082524 A1 WO2011082524 A1 WO 2011082524A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
gateway device
information
data
low data
Prior art date
Application number
PCT/CN2010/070049
Other languages
English (en)
Chinese (zh)
Inventor
陈中平
吴问付
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201080001635.3A priority Critical patent/CN102754472B/zh
Priority to PCT/CN2010/070049 priority patent/WO2011082524A1/fr
Publication of WO2011082524A1 publication Critical patent/WO2011082524A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents

Definitions

  • 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.
  • M2M Machine-to-machine
  • GSM Global System for Mobile Communications
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 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.
  • MTC server Machine Type Communications Server
  • the M2M terminal is different from the traditional human to human (H2H) terminal, and the application is relatively simple.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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
  • 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;
  • 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.
  • FIG. 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
  • FIG. 2B is a schematic diagram of a carrier network in FIG. 2A;
  • FIG. 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
  • 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
  • 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
  • FIG. 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. 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. 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. 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
  • 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).
  • ⁇ Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • 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.
  • the initiating an association establishment request to the gateway device includes:
  • 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;
  • 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.
  • 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:
  • NAS non-access stratum service
  • PDN packet data network
  • machine type communication data in the form of an IP packet
  • the gateway device 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
  • 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.
  • FIG. 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.
  • a plurality of MTC devices 21 communicate with the MTC server 22 via an operator network, including the transmission of data.
  • 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.
  • 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.
  • 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. 0
  • 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.
  • the mobility management network element 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.
  • GGSN Gateway GPRS Support Node
  • P-GW Packet Data Network
  • 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.
  • 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.
  • ID PDN identification
  • 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.
  • APN Access Point Name
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • API Access Point Name
  • 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.
  • the mobility management network element 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.
  • 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.
  • the accept message may further include indication information for instructing the M2M terminal to perform network optimization based on the low data stream service.
  • the M2M terminal can obtain the MTC server address.
  • 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.
  • the gateway device may send the connection establishment message to the M2M terminal, or may send the message to the M2M terminal through other messages.
  • 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.
  • 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.
  • the M2M terminal 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the IP address assigned by the gateway device to the M2M terminal may not be 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.
  • the data when 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.
  • 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.
  • 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.
  • the mobility management network element 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.
  • 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:
  • 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.
  • the forwarded message carries the IP address information of the MTC server, it can be obtained directly from the forwarded message.
  • 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.
  • 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.
  • 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.
  • 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.
  • the M2M terminal does not need to provide the destination address indication information.
  • 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.
  • 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. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the network side can also generate the number of streams that need to be passed to the MTC server.
  • MTC Monitoring Machine Type Communication Monitoring
  • 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.
  • 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:
  • 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);
  • 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);
  • 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).
  • MTC Feature(s) machine type
  • 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.
  • 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.
  • the subscription identifier eg, IMSI
  • 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.
  • 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.
  • 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.
  • the connection establishing module 112 is configured to receive, by the receiving module 111, the terminal of the low data stream.
  • the signaling connection from the mobility management network element to the gateway device is established for the terminal of the low data stream.
  • 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.
  • 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.
  • the receiving module 111 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.
  • 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.
  • the receiving module 111 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 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.
  • 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 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.
  • 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
  • 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;
  • 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;
  • 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;
  • 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;
  • 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. ;
  • 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.
  • 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;
  • 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
  • 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;
  • the mobility management network element 121 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.
  • 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.
  • 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.
  • 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.

Abstract

La présente invention se rapporte à un procédé et à un système pour la transmission de données de machine à machine. Elle se rapporte également à un dispositif formant entité de gestion de la mobilité (MME). Le procédé selon l'invention consiste : à recevoir une demande d'accès en provenance d'un terminal à faible débit de données ; à établir une connexion de signalisation, d'une entité de gestion de la mobilité à un équipement formant passerelle, pour le terminal à faible débit de données ; et à transmettre les informations de données du terminal à faible débit de données via la connexion de signalisation établie.
PCT/CN2010/070049 2010-01-07 2010-01-07 Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité WO2011082524A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201080001635.3A CN102754472B (zh) 2010-01-07 2010-01-07 机器到机器的数据传输方法、系统及移动性管理网元装置
PCT/CN2010/070049 WO2011082524A1 (fr) 2010-01-07 2010-01-07 Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/070049 WO2011082524A1 (fr) 2010-01-07 2010-01-07 Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité

Publications (1)

Publication Number Publication Date
WO2011082524A1 true WO2011082524A1 (fr) 2011-07-14

Family

ID=44305166

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/070049 WO2011082524A1 (fr) 2010-01-07 2010-01-07 Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité

Country Status (2)

Country Link
CN (1) CN102754472B (fr)
WO (1) WO2011082524A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9497566B2 (en) 2010-03-23 2016-11-15 Interdigital Patent Holdings, Inc. Efficient signaling for machine type communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374348A (zh) * 2007-08-14 2009-02-25 卢森特技术有限公司 无线电信网络中的切换方法及装置
CN101572929A (zh) * 2008-04-29 2009-11-04 大唐移动通信设备有限公司 一种在切换过程中传送消息的方法、装置及系统
CN101605353A (zh) * 2008-06-13 2009-12-16 上海华为技术有限公司 一种数据通讯方法及通讯系统以及相关装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7912486B2 (en) * 2005-03-28 2011-03-22 Tekelec Methods, systems, and computer program products for surveillance of messaging service messages in a communications network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374348A (zh) * 2007-08-14 2009-02-25 卢森特技术有限公司 无线电信网络中的切换方法及装置
CN101572929A (zh) * 2008-04-29 2009-11-04 大唐移动通信设备有限公司 一种在切换过程中传送消息的方法、装置及系统
CN101605353A (zh) * 2008-06-13 2009-12-16 上海华为技术有限公司 一种数据通讯方法及通讯系统以及相关装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9497566B2 (en) 2010-03-23 2016-11-15 Interdigital Patent Holdings, Inc. Efficient signaling for machine type communication
US9872228B2 (en) 2010-03-23 2018-01-16 Interdigital Patent Holdings, Inc. Efficient signaling for machine type communication
US10531366B2 (en) 2010-03-23 2020-01-07 Iot Holdings, Inc. Efficient signaling for machine type communication

Also Published As

Publication number Publication date
CN102754472A (zh) 2012-10-24
CN102754472B (zh) 2015-05-27

Similar Documents

Publication Publication Date Title
US11690130B2 (en) Network initiated release assistance information
US11540100B2 (en) Method and apparatus for communication of terminal in mobile communication system
US10826769B2 (en) Data processing method and device
US20190313468A1 (en) PDU Session Establishment for Cellular IoT
EP2448297B1 (fr) Procédé et système de traitement d'informations, et élément réseau de gestion de mobilité
EP2566199B1 (fr) Procédé et système pour transmettre des paquets de données de petite taille
US20180332462A1 (en) Method for transmitting data in ciot system and device therefor
TWI514818B (zh) A method of distributing group messages for machine class communication
KR102048046B1 (ko) 무선 통신 시스템에서 ladn 이용 방법 및 이를 위한 장치
WO2015104751A1 (fr) Entité mtc-iwf, entité pcrf et procédé de commande
WO2013113186A1 (fr) Procédé et système pour envoyer des informations de déclenchement d'équipement usager mtc et équipement usager
US20160198049A1 (en) Wireless communication system and method for charging control
JP2013017180A (ja) 時間インジケータを用いたトリガリング
WO2012130098A1 (fr) Procédé et système conçus pour obtenir l'adresse ip d'un dispositif de communication de type machine (mtc)
CN107438290B (zh) 一种小数据传输的连接建立方法、scef实体、mme
US8797856B1 (en) Feedback for machine to machine devices to account for failure of network elements
JP6191768B2 (ja) 移動無線通信装置からのデータ転送
WO2011134370A1 (fr) Procédé de rapport d'événement de communication de type machine et système associé
WO2011110022A1 (fr) Procédé, dispositif et système destinés à transmettre des données
WO2011082524A1 (fr) Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité
WO2011032522A1 (fr) Système et procédé de mise en œuvre d'accès local
GB2614303A (en) Communication system
WO2011124179A2 (fr) Procédé, appareil et système pour machine de type de communication

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080001635.3

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10841868

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10841868

Country of ref document: EP

Kind code of ref document: A1