WO2015021608A1 - 发送触发消息的方法及设备 - Google Patents

发送触发消息的方法及设备 Download PDF

Info

Publication number
WO2015021608A1
WO2015021608A1 PCT/CN2013/081429 CN2013081429W WO2015021608A1 WO 2015021608 A1 WO2015021608 A1 WO 2015021608A1 CN 2013081429 W CN2013081429 W CN 2013081429W WO 2015021608 A1 WO2015021608 A1 WO 2015021608A1
Authority
WO
WIPO (PCT)
Prior art keywords
trigger message
party
message
trigger
address
Prior art date
Application number
PCT/CN2013/081429
Other languages
English (en)
French (fr)
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 EP13891523.6A priority Critical patent/EP3021601B1/en
Priority to PCT/CN2013/081429 priority patent/WO2015021608A1/zh
Publication of WO2015021608A1 publication Critical patent/WO2015021608A1/zh
Priority to US15/042,317 priority patent/US20160165379A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/106—Mapping addresses of different types across networks, e.g. mapping telephone numbers to data network addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • the present invention belongs to the field of mobile communication technologies, and in particular, to a method and a device for sending a trigger message.
  • Machine communication (English: Machine-to-machine Communications, referred to as M2M, is a networked application and service centered on machine intelligence interaction. It embeds wireless or wired communication modules and application processing logic inside the machine to realize data communication without manual intervention. User information needs for monitoring, command and dispatch, data acquisition and measurement.
  • M2M communication can be based on wired and wireless methods, and wireless methods include cellular networks and short-distance transmission, among which the third-generation partnership program (The 3rd Generation Partnership Project, 3GPP) cellular networks are a widely used approach.
  • 3GPP Third-generation partnership program
  • 3GPP supports three M2M modes including direct mode, indirect mode and mixed mode.
  • Direct mode is the M2M application server (English: Application Server, abbreviation: AS) and Gateway GPRS Support Node (GGSN)/Packet Data Network Gateway (English: Packet Data Network Gateway (referred to as: PDN Gateway) directly communicates; indirect mode is AS through SCS and GGSN/PDN Gateway communication, Service Capability in indirect mode Server, SCS) may be controlled by 3GPP operators or may be controlled by M2M service providers; mixed mode exists both direct mode and indirect mode.
  • AS Application Server
  • GGSN Gateway GPRS Support Node
  • PDN Gateway Packet Data Network Gateway
  • SCS Service Capability in indirect mode Server
  • Figure 1 is a European Telecommunications Standardization Association for machine communication provided by the prior art (English: European) Telecommunications Standards Institute, abbreviation: ETSI) supports the direct mode architecture of M2M network and 3GPP network interworking, one of which is M2M at the left end of Figure 1.
  • the UE has access to the 3GPP network and accesses a device trigger application server (English: Device Trigger-Application Server, referred to as DT-AS), the DT-AS belongs to the 3GPP network, and the DT-AS is the machine type communication that the operator controls one server and the carrier network (Machine Type)
  • the Communications, MTC) device can first establish a user plane bearer with the DT-AS.
  • the DT-AS can be a separate logical entity, and the functions of the DT-AS can also be set in the GGSN/PGW.
  • the third-party AS does not belong to the 3GPP network, when the third-party AS needs and the M2M
  • the third-party AS needs to send a trigger message to the M2M UE.
  • the third-party AS must first send the M2M to the DT-AS.
  • Trigger (English: trigger) information of the UE, so that the DT-AS forwards the trigger information to the M2M UE through the existing connection, M2M
  • the UE acquires the identifier of the third-party AS according to the received trigger information, and establishes a connection with the third-party AS.
  • the DT-AS cannot identify the trigger message sent by the third-party AS, so that the trigger message cannot be routed to the M2M.
  • the UE causes the M2M UE to fail to establish a connection with the third-party AS.
  • An embodiment of the present invention provides a method for transmitting a trigger message, which is to solve the problem of sending a third-party AS trigger message to M2M.
  • the UE is configured to establish a connection between the M2M UE and the third-party AS.
  • a method of transmitting a trigger message comprising:
  • the third-party application server AS needs to communicate with the machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device trigger application server DT-AS.
  • the trigger message includes at least a machine communication user equipment M2M Determining, by the DT-AS, whether the M2M UE is registered in the DT-AS according to the M2M UE identifier, and if yes, sending the trigger message to the M2M Receiving, by the UE, a response message of the trigger message sent by the M2M UE, and sending a response message of the trigger message to the third-party AS;
  • the UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the method before the third party AS sends a trigger trigger message to the DT-AS, the method further includes:
  • the IP address and/or the port number of the DT-AS in the configuration trigger message are respectively a preset IP address and a port number, so that the DT-AS receives the message through the preset IP address and port number.
  • the message can be identified as a trigger message.
  • the third-party AS acquires an IP address of the DT-AS and/or the DT-AS Port number, including:
  • the IP address is sent to the DNS to be sent to the DNS to obtain the IP address of the DT-AS.
  • the third-party AS and the The DT-AS communicates via the diameter protocol or the HTTP protocol.
  • a second aspect is a method of sending a trigger message, the method comprising:
  • the device triggers the application server DT-AS to receive the trigger message sent by the third-party application server AS.
  • the trigger message is sent to the M2M UE corresponding to the M2M UE identifier
  • the trigger message includes at least a machine communication user terminal M2M UE identifier
  • the UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the method further includes:
  • the DT-AS recognizes that the message is a trigger message when receiving a message with a preset IP address and/or port number.
  • the third-party AS and the DT-AS pass the diameter protocol or the HTTP protocol. Communication.
  • an application server includes:
  • the third-party AS sends a trigger trigger message to the device trigger application server DT-AS.
  • the trigger message includes at least a machine communication user equipment M2M Determining, by the DT-AS, whether the M2M UE is registered in the DT-AS according to the M2M UE identifier, and if yes, sending the trigger message to the M2M Receiving, by the UE, a response message of the trigger message sent by the M2M UE, and sending a response message of the trigger message to the third-party AS;
  • a receiving unit configured to receive a response message of the trigger message sent by the DT-AS
  • the UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the application server further includes an acquiring unit and a setting unit;
  • the obtaining unit is specifically configured to:
  • the setting unit is specifically configured to:
  • the IP address and/or the port number of the DT-AS in the configuration trigger message are respectively a preset IP address and a port number, so that the DT-AS receives the message through the preset IP address and port number.
  • the message can be identified as a trigger message.
  • the acquiring unit is specifically configured to:
  • the IP address is sent to the DNS to be sent to the DNS to obtain the IP address of the DT-AS.
  • the three-party AS and the DT-AS communicate through a diameter protocol or an HTTP protocol.
  • a device triggers an application server, where the device triggers an application server, including:
  • a first receiving unit configured to receive a trigger message sent by a third-party application server AS, where the trigger message includes at least a machine communication user terminal M2M UE identifier;
  • a determining unit configured to determine, according to the M2M UE identifier, whether the M2M UE is registered in the DT-AS;
  • a sending unit if yes, sending the trigger message to the M2M corresponding to the M2M UE identifier UE;
  • a second receiving unit configured to receive the M2M a response message of the trigger message sent by the UE, sending a response message of the trigger message to the third-party AS;
  • the UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the device triggering application server further includes an identifying unit, where the identifying unit is specifically configured to:
  • the message is identified as a trigger message when the message is received at a preset IP address and/or port number.
  • the third-party AS and the DT-AS pass the diameter protocol or the HTTP protocol. Communication.
  • the present invention provides a method for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE is configured to establish a connection between the M2M UE and the third-party AS.
  • FIG. 1 is a schematic diagram of an ETSI-supported M2M network and a 3GPP network interworking direct mode architecture provided by the prior art
  • FIG. 2 is a network architecture diagram of an M2M provided by the prior art
  • FIG. 3 is a schematic diagram of a network architecture of a prior art 2G/3G/Long Term Evolution (LTE) network supporting an M2M network;
  • LTE Long Term Evolution
  • FIG. 5 is an interaction diagram of a sending trigger message according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for sending a trigger message according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for sending a trigger message according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for sending a trigger message according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of an application server according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a device trigger application server according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of an M2M UE according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of an application server according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a device trigger application server according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a device communication user equipment according to an embodiment of the present invention.
  • FIG. 2 is a network architecture diagram of an M2M provided by the prior art.
  • M2M at the left end of Figure 1 Application and D/GSCL (Device /gateway service capability Layer)
  • the architecture communicated through the dla interface is equivalent to the architecture of the M2M Application and DSCL communicating at the left end of Figure 2 through the dla interface.
  • the M2M at the right end of Figure 1 The architecture of Application and NSCL communicating through the mla interface is equivalent to the M2M on the right end of Figure 2.
  • Application and NSCL architecture through the mla interface is equivalent to the M2M on the right end of Figure 2.
  • M2M network application English: Network application, referred to as: NA
  • M2M NSCL communicates via the mIa interface
  • ETSI European Telecommunications Standards Institute for Machine Communication
  • M2M communication can be based on wired mode and wireless mode, and wireless mode includes cellular network and short-distance transmission, and 3GPP cellular network is a widely used method.
  • FIG. 3 is a prior art 2G/3G/long-term evolution (English: Long Term) Evolution, referred to as LTE) network support M2M network network architecture diagram.
  • LTE Long Term Evolution
  • the UE at the left end of FIG. 3 is replaced by the M2M architecture at the left end of FIG. 2, and the AS at the right end of FIG. 3 is replaced with the M2M architecture at the right end of FIG. 2 to form the network architecture diagram of FIG.
  • the relevant node of the user plane in the direct mode, the relevant node of the user plane.
  • 3G core network mainly includes general packet radio service (English: General Packet Radio Service (GPRS) Support Node (English: Serving GPRS Support Node, SGSN for short) Serving Gateway, packet data network gateway (English: Packet Data Network Gateway, referred to as: PDN Gateway)
  • GPRS General Packet Radio Service
  • SGSN Serving GPRS Support Node
  • PDN Gateway Packet Data Network Gateway
  • the DT-AS is an operator that controls a server.
  • the MTC device of the carrier network can first establish a user plane bearer with the DT-AS.
  • the DT-AS can be a separate logical entity or it can be combined with the GGSN/PGW.
  • the AS is an external third-party server, which is mapped to ETCL's NSCL plus Application in the present invention.
  • 3GPP supports three M2M modes including direct mode, indirect mode and mixed mode.
  • the invention relates to a direct mode, the direct mode is AS and GGSN/PDN
  • the Gateway communicates directly.
  • FIG. 4 is an interaction diagram of a sending trigger message provided by the prior art.
  • M2M The UE establishes a network connection with the DT-AS
  • the DT-AS is a server in the 3GPP network
  • the third-party AS is an M2M server outside the 3GPP network
  • the M2M The UE is pre-registered in the third-party AS
  • the third-party AS stores related information of the M2M UE, including the identifier of the M2M UE.
  • the third party AS triggers a trigger message.
  • Step 401 The M2M UE establishes a network connection with the DT-AS.
  • Step 402 when the third party AS needs to be associated with M2M
  • the third-party AS triggers a trigger message, and sends the trigger message to the DT-AS, where the DT-AS receives the trigger message sent by the third-party AS.
  • Step 403 the DT-AS sends the trigger message to the M2M UE.
  • Step 404 the M2M UE establishes a connection with the third-party AS.
  • step 402 the DT-AS cannot identify the trigger message sent by the AS, so that the trigger message cannot be sent to the M2M UE, so that the M2M
  • the UE establishes a network connection with a third party AS.
  • the UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • FIG. 5 is an interaction diagram of a sending trigger message according to an embodiment of the present invention.
  • M2M The UE establishes a network connection with the DT-AS, the DT-AS is a server in the 3GPP network, and the third-party AS is an M2M server outside the 3GPP network, the M2M The UE is pre-registered in the third-party AS, and the third-party AS stores related information of the M2M UE, including the identifier of the M2M UE.
  • the third party AS triggers a trigger message when the UE's data.
  • the third-party AS is a server of the meter company
  • the trigger message needs to be triggered, and the identifier of the user equipment is carried in the trigger message.
  • sending the trigger message to the DT-AS where the DT-AS determines, according to the identifier of the certain user equipment, whether the certain user equipment is already registered in the 3GPP network, and if yes, The DT-AS sends the trigger message to the M2M
  • the UE is configured to establish a connection between the M2M UE and the third-party AS, so that the server of the electric meter company can perform data reading on the electric meter of the one of the user equipments.
  • FIG. 6 is a flowchart of a method for sending a trigger message according to an embodiment of the present invention. As shown in FIG. 6, the method includes the following steps:
  • Step 601 when the third-party application server AS needs to communicate with the machine user equipment M2M When the UE establishes a connection, the third-party AS sends a trigger trigger message to the device trigger application server DT-AS.
  • the trigger message includes at least a machine communication user equipment M2M Determining, by the DT-AS, whether the M2M UE is registered in the DT-AS according to the M2M UE identifier, and if yes, sending the trigger message to the M2M Receiving, by the UE, a response message of the trigger message sent by the M2M UE, and sending a response message of the trigger message to the third-party AS;
  • the third-party application server AS needs to communicate with the machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device trigger application server DT-AS.
  • the DT-AS determines the M2M according to the M2M UE identifier If the UE is not registered in the DT-AS, the DT-AS returns a response to the third-party AS, and the failure reason is carried in the response.
  • Step 602 Receive a response message of the trigger message sent by the DT-AS.
  • the third-party AS pre-stores the M2M UE identifier, where the M2M The UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the third-party AS stores the M2M in advance.
  • the identity of the UE is registered in the third-party AS.
  • the method before the sending, by the third-party AS, the trigger message to the DT-AS, the method further includes:
  • the IP address and/or the port number of the DT-AS in the configuration trigger message are respectively a preset IP address and a port number, so that the DT-AS receives the message through the preset IP address and port number.
  • the message can be identified as a trigger message.
  • the third-party AS may set the IP address of the third party in the trigger message to 1.1.0.0, and the DT-AS and the third-party AS pre-approve that when the IP address of the third party is 1.1.0.0, the DT -AS can recognize that the message is a trigger message.
  • the third-party AS may set the port number of the DT-AS in the trigger message to 1.
  • the DT-AS and the third-party AS pre-approve that when the port number of the DT-AS in the trigger message is 1,
  • the DT-AS can recognize that the message is a trigger message.
  • the third-party AS may set the IP address and port number of the DT-AS in the trigger message to 1.1.1.1 and 0 respectively, and the DT-AS receives the trigger message by using the IP address 1.1.1.1 and the port number 0. , you can recognize that the message is a trigger message.
  • the third-party AS acquires the IP address of the DT-AS and/or the port number of the DT-AS, including:
  • the IP address is sent to the DNS to be sent to the DNS to obtain the IP address of the DT-AS.
  • the present invention provides a method for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 7 is a flowchart of a method for sending a trigger message according to an embodiment of the present invention. As shown in FIG. 7, the method includes the following steps:
  • Step 701 The device triggers the application server DT-AS to receive a trigger message sent by the third-party application server AS, where the trigger message includes at least a machine communication user terminal M2M.
  • the trigger message includes at least a machine communication user terminal M2M.
  • Step 702 Determine, according to the M2M UE identifier, whether the M2M UE is registered in the DT-AS.
  • the trigger message carries an identifier of the M2M UE, and the DT-AS is according to the M2M.
  • the identity of the UE determines whether the M2M UE is registered in the network where the DT-AS is located.
  • Step 703 if yes, sending the trigger message to the M2M corresponding to the M2M UE identifier.
  • Step 704 receiving the M2M a response message of the trigger message sent by the UE, sending a response message of the trigger message to the third-party AS;
  • the third-party AS pre-stores the M2M UE identifier, where the M2M The UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the method further includes:
  • the DT-AS recognizes that the message is a trigger message when receiving a message with a preset IP address and/or port number.
  • the DT-AS and the third-party AS pre-approve that when the trigger message carries the specific identifier A, the DT is -AS can recognize that the message is a trigger message.
  • the third-party AS may set the IP address of the third party in the trigger message to 1.1.0.0, and the DT-AS and the third-party AS pre-approve that when the IP address of the third party is 1.1.0.0, the DT-AS may The message is identified as a trigger message.
  • the third-party AS may set the port number of the DT-AS in the trigger message to 1.
  • the DT-AS and the third-party AS pre-approve that when the port number of the DT-AS in the trigger message is 1,
  • the DT-AS can recognize that the message is a trigger message.
  • the third-party AS may set the IP address and port number of the DT-AS in the trigger message to 1.1.1.1 and 0 respectively, and the DT-AS receives the trigger message by using the IP address 1.1.1.1 and the port number 0. , you can recognize that the message is a trigger message.
  • the present invention provides a method for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 8 is a flowchart of a method for sending a trigger message according to an embodiment of the present invention. As shown in FIG. 8, the method includes the following steps:
  • Step 801 machine communication user equipment M2M
  • the UE receiving device triggers a trigger message sent by the application server DT-AS;
  • the M2M The UE receives the trigger message.
  • Step 802 Establish a connection with the third-party AS according to the identifier of the third-party application server AS carried in the trigger message.
  • the trigger message includes at least a machine communication user terminal M2M UE identifier
  • the third-party AS pre-stores the M2M UE identifier, where the M2M The UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the present invention provides a method for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 9 is a schematic structural diagram of an application server according to an embodiment of the present invention.
  • the application server includes:
  • the sending unit 901 is configured to: when the third-party application server AS needs to communicate with the machine, the user equipment M2M When the UE establishes a connection, the third-party AS sends a trigger trigger message to the device triggering application server DT-AS.
  • the trigger message includes at least a machine communication user equipment M2M Determining, by the DT-AS, whether the M2M UE is registered in the DT-AS according to the M2M UE identifier, and if yes, sending the trigger message to the M2M Receiving, by the UE, a response message of the trigger message sent by the M2M UE, and sending a response message of the trigger message to the third-party AS;
  • the third-party application server AS needs to communicate with the machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device trigger application server DT-AS.
  • the receiving unit 902 is configured to receive a response message of the trigger message sent by the DT-AS.
  • the third-party AS pre-stores the M2M UE identifier, where the M2M The UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the third-party AS stores the M2M in advance.
  • the identity of the UE is registered in the third-party AS.
  • the application server further includes an obtaining unit 903 and a setting unit 904;
  • the obtaining unit 903 is specifically configured to:
  • the setting unit 904 is specifically configured to:
  • the IP address and/or the port number of the DT-AS in the configuration trigger message are respectively a preset IP address and a port number, so that the DT-AS receives the message through the preset IP address and port number.
  • the message can be identified as a trigger message.
  • the third-party AS may set the IP address of the third party in the trigger message to 1.1.0.0, and the DT-AS and the third-party AS pre-approve that when the IP address of the third party is 1.1.0.0, the DT -AS can recognize that the message is a trigger message.
  • the third-party AS may set the port number of the DT-AS in the trigger message to 1.
  • the DT-AS and the third-party AS pre-approve that when the port number of the DT-AS in the trigger message is 1,
  • the DT-AS can recognize that the message is a trigger message.
  • the third-party AS may set the IP address and port number of the DT-AS in the trigger message to 1.1.1.1 and 0 respectively, and the DT-AS receives the trigger message by using the IP address 1.1.1.1 and the port number 0. , you can recognize that the message is a trigger message.
  • the obtaining unit 903 is specifically configured to:
  • the IP address is sent to the DNS to be sent to the DNS to obtain the IP address of the DT-AS.
  • the present invention provides a device for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 10 is a schematic structural diagram of a device trigger application server according to an embodiment of the present invention.
  • the device triggering an application server includes:
  • the first receiving unit 1001 is configured to receive a trigger message sent by the third-party application server AS, where the trigger message includes at least a machine communication user terminal M2M UE identity;
  • the determining unit 1002 is configured to determine, according to the M2M UE identifier, the M2M Whether the UE is registered in the DT-AS;
  • the trigger message carries an identifier of the M2M UE, and the DT-AS is according to the M2M.
  • the identity of the UE determines whether the M2M UE is registered in the network where the DT-AS is located.
  • the sending unit 1003 is configured to: if yes, send the trigger message to the M2M corresponding to the M2M UE identifier. UE;
  • a second receiving unit 1004 configured to receive the M2M a response message of the trigger message sent by the UE, sending a response message of the trigger message to the third-party AS;
  • the third-party AS pre-stores the M2M UE identifier, where the M2M The UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the device triggering application server further includes an identifying unit 1005, and the identifying unit 1005 is specifically configured to:
  • the message is identified as a trigger message when the message is received at a preset IP address and/or port number.
  • the DT-AS and the third-party AS pre-approve that when the trigger message carries the specific identifier A, the DT is -AS can recognize that the message is a trigger message.
  • the third-party AS may set the IP address of the third party in the trigger message to 1.1.0.0, and the DT-AS and the third-party AS pre-approve that when the IP address of the third party is 1.1.0.0, the DT-AS may The message is identified as a trigger message.
  • the third-party AS may set the port number of the DT-AS in the trigger message to 1.
  • the DT-AS and the third-party AS pre-approve that when the port number of the DT-AS in the trigger message is 1,
  • the DT-AS can recognize that the message is a trigger message.
  • the third-party AS may set the IP address and port number of the DT-AS in the trigger message to 1.1.1.1 and 0 respectively, and the DT-AS receives the trigger message by using the IP address 1.1.1.1 and the port number 0. , you can recognize that the message is a trigger message.
  • the present invention provides a device for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 11 is a schematic structural diagram of an M2M UE according to an embodiment of the present invention.
  • the M2M The UE includes:
  • the receiving unit 1101 is configured to receive a trigger message sent by the device triggering application server DT-AS.
  • the M2M The UE receives the trigger message.
  • the establishing unit 1102 is configured to establish a connection with the third-party AS according to the identifier of the third-party application server AS carried in the trigger message.
  • the trigger message includes at least a machine communication user terminal M2M UE identifier
  • the third-party AS pre-stores the M2M UE identifier, where the M2M The UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the present invention provides a device for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 12 is a schematic structural diagram of an application server according to an embodiment of the present invention.
  • FIG. 12 is an application server 1200 according to an embodiment of the present invention.
  • the specific implementation of the application server does not limit the specific implementation of the application server.
  • the application server 1200 includes:
  • processor English: processor
  • communication interface English: Communications
  • memory English: memory
  • the processor 1201, the communication interface 1202, and the memory 1203 complete communication with each other through the bus 1204.
  • a communication interface 1202 configured to communicate with a device trigger application server
  • the processor 1201 is configured to execute a program.
  • the program can include program code, the program code including computer operating instructions.
  • the processor 1201 may be a central processing unit (English: central processing) Unit, abbreviation: CPU.
  • the memory 1203 is configured to store a program.
  • the memory 1203 can be a volatile memory (English: volatile Memory), such as random access memory (English: random-access memory, abbreviation: RAM), or non-volatile memory (English: non-volatile Memory), such as flash memory (English: flash memory), hard disk (English: hard disk Drive, abbreviation: HDD) or solid state drive (English: solid-state Drive, abbreviation: SSD).
  • the processor 1201 performs the following methods according to the program instructions stored in the memory 1203:
  • the third-party application server AS needs to communicate with the machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device trigger application server DT-AS.
  • the trigger message includes at least a machine communication user equipment M2M Determining, by the DT-AS, whether the M2M UE is registered in the DT-AS according to the M2M UE identifier, and if yes, sending the trigger message to the M2M Receiving, by the UE, a response message of the trigger message sent by the M2M UE, and sending a response message of the trigger message to the third-party AS;
  • the UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the method further includes: before the third party AS sends a trigger trigger message to the DT-AS, the method further includes:
  • the IP address and/or the port number of the DT-AS in the configuration trigger message are respectively a preset IP address and a port number, so that the DT-AS receives the message through the preset IP address and port number.
  • the message can be identified as a trigger message.
  • the third-party AS acquires the IP address of the DT-AS and/or the port number of the DT-AS, including:
  • IP address of the DT-AS pre-configured on the third-party AS, and sending the IP address of the DT-AS to the DNS to obtain the IP address of the DT-AS.
  • the present invention provides a method for transmitting a trigger message, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 13 is a schematic structural diagram of a device trigger application server according to an embodiment of the present invention.
  • FIG. 13 is a device triggering application server 1300 according to an embodiment of the present invention.
  • the specific embodiment of the present invention does not limit the specific implementation of the device triggering the application server.
  • the device triggering the application server 1300 includes:
  • the processor 1301, the communication interface 1302, and the memory 1303 complete communication with each other via the bus 1304.
  • a communication interface 1302 configured to communicate with an application server and a machine communication user equipment
  • the processor 1301 is configured to execute a program.
  • the program can include program code, the program code including computer operating instructions.
  • the processor 1301 may be a central processing unit (English: central processing) Unit, abbreviation: CPU.
  • the memory 1303 is configured to store a program.
  • the memory 1303 can be a volatile memory (English: volatile Memory), such as random access memory (English: random-access memory, abbreviation: RAM), or non-volatile memory (English: non-volatile Memory), such as flash memory (English: flash memory), hard disk (English: hard disk Drive, abbreviation: HDD) or solid state drive (English: solid-state Drive, abbreviation: SSD).
  • the processor 1301 performs the following methods according to the program instructions stored in the memory 1303:
  • the trigger message is sent to the M2M UE corresponding to the M2M UE identifier
  • the trigger message includes at least a machine communication user terminal M2M UE identifier
  • the UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the method further includes:
  • the DT-AS recognizes that the message is a trigger message when receiving a message with a preset IP address and/or port number.
  • the present invention provides a device trigger application server, when a third-party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.
  • FIG. 14 is a schematic structural diagram of a device communication user equipment according to an embodiment of the present invention.
  • FIG. 14 is a machine communication user equipment 1400 according to an embodiment of the present invention.
  • the specific embodiment of the present invention does not limit the specific implementation of the machine communication user equipment.
  • the machine communication user equipment 1400 includes:
  • the processor 1401, the communication interface 1402, and the memory 1403 complete communication with each other through the bus 1404.
  • a communication interface 1402 configured to communicate with an application server and a device trigger application server;
  • the processor 1401 is configured to execute a program.
  • the program can include program code, the program code including computer operating instructions.
  • the processor 1401 may be a central processing unit (English: central processing) Unit, abbreviation: CPU.
  • the memory 1403 is configured to store a program.
  • the memory 1403 can be a volatile memory (English: volatile Memory), such as random access memory (English: random-access memory, abbreviation: RAM), or non-volatile memory (English: non-volatile Memory), such as flash memory (English: flash memory), hard disk (English: hard disk Drive, abbreviation: HDD) or solid state drive (English: solid-state Drive, abbreviation: SSD).
  • the processor 1401 performs the following methods according to the program instructions stored in the memory 1403:
  • the receiving device triggers a trigger message sent by the application server DT-AS;
  • the trigger message includes at least a machine communication user terminal M2M UE identifier
  • the third-party AS pre-stores the M2M UE identifier, where the M2M The UE is connected in a network where the DT-AS is located, the DT-AS is a server in a 3GPP network, and the third-party AS is an M2M server in a 3GPP external network.
  • the present invention provides a machine communication user equipment, when a third party application server AS needs to communicate with a machine user equipment M2M
  • the third-party AS sends a trigger trigger message to the device triggering application server DT-AS, where the trigger message includes at least the machine communication user equipment M2M. Determining, according to the M2M UE identity, whether the M2M UE is registered in the network where the DT-AS is located, and if yes, sending the trigger message to the M2M.
  • the UE thereby implementing the DT-AS identification tirgger message, so that the M2M UE and the third party AS establish a connection.

Abstract

本发明提供一种发送触发消息的方法及设备，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。

Description

发送触发消息的方法及设备 技术领域
本发明属于移动通信技术领域，尤其涉及一种发送触发消息的方法及设备。
背景技术
机器通信（英文：Machine-to-machine Communications，简称：M2M）是一种以机器智能交互为核心的，网络化的应用与服务，其通过在机器内部嵌入无线或有线通信模块以及应用处理逻辑，实现无需人工干预的数据通信，以满足用户对监控、指挥调度、数据采集和测量等方面的信息化需求。
　　　目前M2M通信可以基于有线方式和无线方式，无线方式包括蜂窝网和短距离传输，其中第三代伙伴计划（The 3rd Generation Partnership Project，3GPP）蜂窝网是广泛使用的一种方式。目前3GPP支持3种M2M模式包括直接模式、间接模式和混合模式。直接模式就是M2M应用服务器（英文：Application Server，简称：AS）与网关GPRS支持节点（Gateway GPRS Support Node，GGSN）/分组数据网络网关（英文：Packet Data Network Gateway，简称：PDN Gateway）直接进行通信；间接模式是AS通过SCS与GGSN/PDN Gateway通信，在间接模式下业务能力服务器（Service Capability Server，SCS）可能是3GPP运营商控制也可能是M2M业务提供商控制；混合模式就是直接模式和间接模式都存在。
　　　图1是现有技术提供的机器通信的欧洲电信标准化协会（英文：European Telecommunications Standards Institute，简称：ETSI）支持M2M网络与3GPP网络互通直接模式架构，其中一种方式为图1左端的M2M UE已经接入3GPP网络并且接入到一个设备触发应用服务器(英文：Device Trigger-Application Server，简称：DT-AS)，该DT-AS归属所述3GPP网络 ，DT-AS是运营商控制一个服务器，运营商网络的机器类型通讯（Machine Type Communications，MTC）设备可以先建立与DT-AS的用户面承载。DT-AS可以是一个单独的逻辑实体，也可以将DT-AS所具有的功能设置在GGSN/PGW中。
　　　第三方AS对应图中的网络服务能力层（Network Service capability layer，NSCL）及机器通信应用（英文：M2M Application），该第三方AS不归属所述3GPP网络，当所述第三方AS需要和所述M2M UE建立连接时，所述第三方AS需要向所述M2M UE发送trigger消息，根据现有信令流程，第三方AS必须先向DT-AS发送所述M2M UE的触发（英文：trigger）信息，以使得DT-AS通过现有连接把所述trigger信息转发给M2M UE，M2M UE根据接收到的trigger信息获取第三方AS的标识，向所述第三方AS建立连接。但是现有技术存在问题是，DT-AS无法识别第三方AS发送的trigger消息，以至于无法将所述trigger消息路由到M2M UE，导致所述M2M UE无法和所述第三方AS建立连接。
 技术问题
本发明实施例提供一种传递触发消息的方法，旨在解决将第三方AS的trigger消息发送到M2M UE，以便于所述M2M UE和所述第三方AS建立连接。
技术解决方案
第一方面，一种发送触发消息的方法，所述方法包括：
　　　当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息；
　　　其中，所述trigger消息至少包括机器通信用户设备M2M UE标识，以使得所述DT-AS根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册，若是，则将所述trigger消息发送到所述M2M UE，并接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　接收所述DT-AS发送的所述trigger消息的响应消息；
　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　结合第一方面，在第一方面的第一种可能的实现方式中，所述方法在所述第三方AS向所述DT-AS发送触发trigger消息之前，还包括：
　　　所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号；
　　　配置trigger消息中的第三方AS的IP地址和/或所述DT-AS的端口号为预先配置的值，所述预先配置的值用于所述DT-AS识别出所述trigger消息；或者，
　　　配置trigger消息中的所述DT-AS的IP地址和/或端口号分别为预先设置的IP地址和端口号，使得所述DT-AS通过所述预先设置的IP地址和端口号接收到消息时能识别出所述消息为trigger消息。
　　　结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号，包括：
　　　获取预先配置在第三方AS上的所述DT-AS的IP地址和/或端口号；或者，
　　　获取预先配置在第三方AS上的所述M2M UE的外接External IP地址，将所述外接IP地址发送到DNS上解析获取所述DT-AS的IP地址。
　　　结合第一方面或者第一方面的第一种可能的实现方式或者第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　第二方面，一种发送触发消息的方法，所述方法包括：
　　　设备触发应用服务器DT-AS接收第三方应用服务器AS发送的trigger消息；
　　　根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册；
　　　若是，则将所述trigger消息发送到所述M2M UE标识所对应的M2M UE；
　　　接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　结合第二方面，在第二方面的第一种可能的实现方式中，所述方法在所述DT-AS接收所述第三方AS发送的trigger消息之后，还包括：
　　　根据所述trigger消息中携带预先设定的特定标识识别出所述trigger消息；或者，
　　　根据所述trigger消息中的预先设定的第三方AS的IP地址和/或所述DT-AS的端口号识别出所述trigger消息；或者，
　　　DT-AS在预先设定的IP地址和/或端口号接收消息时识别出所述消息为trigger消息。
　　　结合第二方面或者第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　第三方面，一种应用服务器，所述应用服务器包括：
　　　发送单元，用于当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息；
　　　其中，所述trigger消息至少包括机器通信用户设备M2M UE标识，以使得所述DT-AS根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册，若是，则将所述trigger消息发送到所述M2M UE，并接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　接收单元，用于接收所述DT-AS发送的所述trigger消息的响应消息；
　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　结合第三方面，在第三方面的第一种可能的实现方式中，所述应用服务器还包括获取单元和设置单元；
　　　所述获取单元，具体用于：
　　　获取所述DT-AS的IP地址和/或所述DT-AS的端口号；
　　　所述设置单元，具体用于：
　　　配置trigger消息中的第三方AS的IP地址和/或所述DT-AS的端口号为预先配置的值，所述预先配置的值用于所述DT-AS识别出所述trigger消息；或者，
　　　配置trigger消息中的所述DT-AS的IP地址和/或端口号分别为预先设置的IP地址和端口号，使得所述DT-AS通过所述预先设置的IP地址和端口号接收到消息时能识别出所述消息为trigger消息。
　　　结合第三方面的第一种可能的实现方式，在第三方面的第二种可能的实现方式中，所述获取单元，具体用于：
　　　获取预先配置在第三方AS上的所述DT-AS的IP地址和/或端口号；或者，
　　　获取预先配置在第三方AS上的所述M2M UE的外接External IP地址，将所述外接IP地址发送到DNS上解析获取所述DT-AS的IP地址。
　　　结合第三方面或者第三方面的第一种可能的实现方式或者第三方面的第二种可能的实现方式，在第三方面的第三种可能的实现方式中，其特征在于，所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　第四方面，一种设备触发应用服务器，所述设备触发应用服务器包括：
　　　第一接收单元，用于接收第三方应用服务器AS发送的trigger消息，所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　判断单元，用于根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册；
　　　发送单元，用于若是，则将所述trigger消息发送到所述M2M UE标识所对应的M2M UE；
　　　第二接收单元，用于接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　结合第四方面，在第四方面的第一种可能的实现方式中，所述设备触发应用服务器还包括识别单元，所述识别单元具体用于：
　　　根据所述trigger消息中携带预先设定的特定标识识别出所述trigger消息；或者，
　　　根据所述trigger消息中的预先设定的第三方AS的IP地址和/或所述DT-AS的端口号识别出所述trigger消息；或者，
　　　在预先设定的IP地址和/或端口号接收消息时识别出所述消息为trigger消息。
　　　结合第四方面或者第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
 有益效果
本发明提供一种发送触发消息的方法，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，以便于所述M2M UE和所述第三方AS建立连接。
 附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
　　　图1是现有技术提供的ETSI支持M2M网络和3GPP网络互通直接模式架构图；
　　　图2是现有技术提供的一种M2M的网络架构图；
　　　图3是现有技术2G/3G/长期演进LTE网络支持M2M网络网络架构图；
　　　图4是现有技术提供的一种发送触发消息的交互图；
　　　图5是本发明实施例提供的一种发送触发消息的交互图；
　　　图6是本发明实施例提供的一种发送触发消息的方法流程图；
　　　图7是本发明实施例提供的一种发送触发消息的方法流程图；
　　　图8是本发明实施例提供的一种发送触发消息的方法流程图；
　　　图9是本发明实施例提供的一种应用服务器的结构示意图；
　　　图10是本发明实施例提供的一种设备触发应用服务器的结构示意图；
　　　图11是本发明实施例提供的一种M2M UE的结构示意图；
　　　图12是本发明实施例提供的一种应用服务器的结构示意图；
　　　图13是本发明实施例提供的一种设备触发应用服务器的结构示意图；
　　　图14是本发明实施例提供的一种机器通信用户设备的结构示意图。
 本发明的实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
　　　参考图2，图2是现有技术提供的一种M2M的网络架构图。图1中左端的M2M Application和D/GSCL(Device /gateway service capability layer)通过dla接口通信的架构相当于图2中左端的M2M Application和DSCL通过dla接口通信的架构，图1右端的M2M Application和NSCL通过mla接口通信的架构相当于图2中右端的M2M Application和NSCL通过mla接口通信的架构。在M2M终端（英文：User Equipment，简称：UE）上，M2M 设备应用（英文：Device Application，简称：DA）与M2M设备服务性能层（英文：Device Service Capability Layer，简称：DSCL）通过dIa接口通信，在M2M网络侧，M2M 网络应用（英文：Network application，简称：NA）与M2M NSCL通过mIa接口通信，机器通信的欧洲电信标准化协会（英文：European Telecommunications Standards Institute，简称：ETSI）定义了DSCL和NSCL之间的mId接口，M2M NA可以通过mId接口访问、装载M2M UE上面的M2M DA。
　　　目前M2M通信可以基于有线方式和无线方式，无线方式包括蜂窝网和短距离传输，其中3GPP蜂窝网是广泛使用的一种方式。
　　　参考图3，图3是现有技术2G/3G/长期演进（英文：Long Term Evolution，简称：LTE）网络支持M2M网络网络架构图。在图3的网络架构基础上，用图2的左端的M2M架构代替图3左端的UE，用图2的右端的M2M架构代替图3右端的AS，形成图1的网络架构图。如图3所示，直接模式下，用户面的相关节点。3G的核心网主要包含通用分组无线服务（英文：General Packet Radio Service，GPRS）支持节点（英文：Serving GPRS Support Node，简称SGSN） Serving Gateway、分组数据网络网关（英文：Packet Data Network Gateway，简称：PDN Gateway）三个逻辑功能体。DT-AS是运营商控制一个服务器，运营商网络的MTC设备可以先建立与DT-AS的用户面承载。DT-AS可以是一个单独的逻辑实体，也可以与GGSN/PGW合设在一起。
　　　AS是外部的第三方服务器，在本发明中映射为ETSI的NSCL加Application。
　　　目前3GPP支持3种M2M模式包括直接模式、间接模式和混合模式。本发明涉及到直接模式，直接模式就是AS 与GGSN/PDN Gateway直接进行通信。
　　　参考图4，图4是现有技术提供的一种发送触发消息的交互图。如图4所示， M2M UE和DT-AS建立网络连接，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP网络外的M2M服务器，所述M2M UE预先注册在第三方AS中，所述第三方AS存储该M2M UE的相关信息，包括M2M UE的标识。当第三方AS需要与M2M UE建立连接时，所述第三方AS触发trigger消息。
　　　步骤401，M2M UE和DT-AS建立网络连接；
　　　步骤402，当第三方AS需要与M2M UE建立连接时，第三方AS触发trigger消息，并将所述trigger消息发送到DT-AS，所述DT-AS接收第三方AS发送的trigger消息；
　　　步骤403，DT-AS将所述trigger消息发送到所述M2M UE；
　　　步骤404，M2M UE和所述第三方AS建立连接。
　　　在步骤402中，所述DT-AS无法识别AS发送的trigger消息，以至于无法将该trigger消息发送到M2M UE，使得M2M UE建立和第三方AS的网络连接。
　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　参考图5，图5是本发明实施例提供的一种发送触发消息的交互图。如图5所示，M2M UE和DT-AS建立网络连接，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP网络外的M2M服务器，所述M2M UE预先注册在第三方AS中，所述第三方AS存储该M2M UE的相关信息，包括M2M UE的标识。当第三方AS需要获取所述M2M UE的数据时，所述第三方AS触发trigger消息。举例来说，假设第三方AS是电表公司的服务器，当电表公司需要对某一用户设备的电表进行上报数据时，需要触发trigger消息，在所述trigger消息中携带所述某一用户设备的标识，将所述trigger消息发送到所述DT-AS，所述DT-AS根据所述某一用户设备的标识判断所述某一用户设备是否已经注册在所述3GPP网络中，若是，则所述DT-AS将所述trigger消息发送到所述M2M UE，以便于所述M2M UE和所述第三方AS建立连接，使得所述电表公司的服务器可以对所述某一个用户设备的电表进行数据读取。
　　　参考图6，图6是本发明实施例提供的一种发送触发消息的方法流程图。如图6所示，所述方法包括以下步骤：
　　　步骤601，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息；
　　　其中，所述trigger消息至少包括机器通信用户设备M2M UE标识，以使得所述DT-AS根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册，若是，则将所述trigger消息发送到所述M2M UE，并接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　具体的，参考图5所示，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息。
可选地，当所述DT-AS根据所述M2M UE标识判断所述M2M UE未在所述DT-AS中注册，则所述DT-AS向所述第三方AS返回response，在所述response中携带失败原因。
　　　步骤602，接收所述DT-AS发送的所述trigger消息的响应消息；
　　　其中，所述第三方AS预先存储所述M2M UE标识，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　具体的，所述M2M UE注册在所述第三方AS时，第三方AS会预先存储所述M2M UE的标识。
　　　可选地，所述方法在所述第三方AS向所述DT-AS发送触发trigger消息之前，还包括：
　　　所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号；
　　　配置trigger消息中的第三方AS的IP地址和/或所述DT-AS的端口号为预先配置的值，所述预先配置的值用于所述DT-AS识别出所述trigger消息；或者，
　　　配置trigger消息中的所述DT-AS的IP地址和/或端口号分别为预先设置的IP地址和端口号，使得所述DT-AS通过所述预先设置的IP地址和端口号接收到消息时能识别出所述消息为trigger消息。
　　　具体的，第三方AS可以将trigger消息中的第三方的IP地址设置为1.1.0.0，所述DT-AS和所述第三方AS预先约定当第三方的IP地址为1.1.0.0时，则DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的DT-AS的端口号设置为1，所述DT-AS和所述第三方AS预先约定当所述trigger消息中的DT-AS的端口号为1时，则DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的所述DT-AS的IP地址和端口号分别设置为1.1.1.1和0，所述DT-AS通过IP地址为1.1.1.1和端口号0接收到trigger消息时，则可以识别出该消息为trigger消息。
　　　所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号，包括：
　　　获取预先配置在第三方AS上的所述DT-AS的IP地址和/或端口号；或者，
　　　获取预先配置在第三方AS上的所述M2M UE的外接External IP地址，将所述外接IP地址发送到DNS上解析获取所述DT-AS的IP地址。
　　　所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　本发明提供一种发送触发消息的方法，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　参考图7，图7是本发明实施例提供的一种发送触发消息的方法流程图。如图7所示，所述方法包括以下步骤：
　　　步骤701，设备触发应用服务器DT-AS接收第三方应用服务器AS发送的trigger消息，所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　具体的，参考图5，当第三方AS需要访问M2M UE时，第三方AS触发trigger消息，并将所述trigger消息发送到DT-AS，所述DT-AS接收所述第三方AS的trigger消息。
　　　步骤702，根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册；
　　　具体的，所述trigger消息中携带M2M UE的标识，所述DT-AS根据所述M2M UE的标识判断该M2M UE是否注册到所述DT-AS所在的网络中。
　　　步骤703，若是，则将所述trigger消息发送到所述M2M UE标识所对应的M2M UE；
　　　步骤704，接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　其中，所述第三方AS预先存储所述M2M UE标识，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　可选地，所述方法在所述DT-AS接收所述第三方AS发送的trigger消息之后，还包括：
　　　根据所述trigger消息中携带预先设定的特定标识识别出所述trigger消息；或者，
　　　根据所述trigger消息中的预先设定的第三方AS的IP地址和/或所述DT-AS的端口号识别出所述trigger消息；或者，
　　　DT-AS在预先设定的IP地址和/或端口号接收消息时识别出所述消息为trigger消息。
具体的，所述第三方AS在所述trigger消息中携带特定的标识A时，所述DT-AS和所述第三方AS预先约定当所述trigger消息中携带特定标识A时，则所述DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的第三方的IP地址设置为1.1.0.0，所述DT-AS和所述第三方AS预先约定当第三方的IP地址为1.1.0.0时，则DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的DT-AS的端口号设置为1，所述DT-AS和所述第三方AS预先约定当所述trigger消息中的DT-AS的端口号为1时，则DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的所述DT-AS的IP地址和端口号分别设置为1.1.1.1和0，所述DT-AS通过IP地址为1.1.1.1和端口号0接收到trigger消息时，则可以识别出该消息为trigger消息。
　　　所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　本发明提供一种发送触发消息的方法，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　参考图8，图8是本发明实施例提供的一种发送触发消息的方法流程图。如图8所示，所述方法包括以下步骤：
　　　步骤801，机器通信用户设备M2M UE接收设备触发应用服务器DT-AS发送的trigger消息；
　　　具体的，参考图5，DT-AS将trigger消息发送到M2M UE时，则所述M2M UE接收所述trigger消息。
　　　步骤802，根据所述trigger消息中携带的第三方应用服务器AS的标识，和所述第三方AS建立连接；
　　　所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　其中，所述第三方AS预先存储所述M2M UE标识，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　本发明提供一种发送触发消息的方法，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　参考图9，图9是本发明实施例提供的一种应用服务器的结构示意图。如图9所示，所述应用服务器包括：
　　　发送单元901，用于当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，第三方AS向设备触发应用服务器DT-AS发送触发trigger消息；
　　　其中，所述trigger消息至少包括机器通信用户设备M2M UE标识，以使得所述DT-AS根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册，若是，则将所述trigger消息发送到所述M2M UE，并接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　具体的，参考图5所示，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息。
　　　接收单元902，用于接收所述DT-AS发送的所述trigger消息的响应消息；
　　　其中，所述第三方AS预先存储所述M2M UE标识，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　具体的，所述M2M UE注册在所述第三方AS时，第三方AS会预先存储所述M2M UE的标识。
　　　所述应用服务器还包括获取单元903和设置单元904；
　　　所述获取单元903，具体用于：
　　　获取所述DT-AS的IP地址和/或所述DT-AS的端口号；
　　　所述设置单元904，具体用于：
　　　配置trigger消息中的第三方AS的IP地址和/或所述DT-AS的端口号为预先配置的值，所述预先配置的值用于所述DT-AS识别出所述trigger消息；或者，
　　　配置trigger消息中的所述DT-AS的IP地址和/或端口号分别为预先设置的IP地址和端口号，使得所述DT-AS通过所述预先设置的IP地址和端口号接收到消息时能识别出所述消息为trigger消息。
　　　具体的，第三方AS可以将trigger消息中的第三方的IP地址设置为1.1.0.0，所述DT-AS和所述第三方AS预先约定当第三方的IP地址为1.1.0.0时，则DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的DT-AS的端口号设置为1，所述DT-AS和所述第三方AS预先约定当所述trigger消息中的DT-AS的端口号为1时，则DT-AS可以识别出该消息为trigger消息。
第三方AS可以将trigger消息中的所述DT-AS的IP地址和端口号分别设置为1.1.1.1和0，所述DT-AS通过IP地址为1.1.1.1和端口号0接收到trigger消息时，则可以识别出该消息为trigger消息。
　　　所述获取单元903，具体用于：
　　　获取预先配置在第三方AS上的所述DT-AS的IP地址和/或端口号；或者，
　　　获取预先配置在第三方AS上的所述M2M UE的外接External IP地址，将所述外接IP地址发送到DNS上解析获取所述DT-AS的IP地址。
　　　所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　本发明提供一种发送触发消息的设备，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　参考图10，图10是本发明实施例提供的一种设备触发应用服务器的结构示意图。如图10所示，所述设备触发应用服务器包括：
　　　第一接收单元1001，用于接收第三方应用服务器AS发送的trigger消息，所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　具体的，参考图5，当第三方AS需要访问M2M UE时，第三方AS触发trigger消息，并将所述trigger消息发送到DT-AS，所述DT-AS接收所述第三方AS的trigger消息。
　　　判断单元1002，用于根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册；
　　　具体的，所述trigger消息中携带M2M UE的标识，所述DT-AS根据所述M2M UE的标识判断该M2M UE是否注册到所述DT-AS所在的网络中。
　　　发送单元1003，用于若是，则将所述trigger消息发送到所述M2M UE标识所对应的M2M UE；
　　　第二接收单元1004，用于接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　其中，所述第三方AS预先存储所述M2M UE标识，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　所述设备触发应用服务器还包括识别单元1005，所述识别单元1005具体用于：
　　　根据所述trigger消息中携带预先设定的特定标识识别出所述trigger消息；或者，
　　　根据所述trigger消息中的预先设定的第三方AS的IP地址和/或所述DT-AS的端口号识别出所述trigger消息；或者，
　　　在预先设定的IP地址和/或端口号接收消息时识别出所述消息为trigger消息。
　　　具体的，所述第三方AS在所述trigger消息中携带特定的标识A时，所述DT-AS和所述第三方AS预先约定当所述trigger消息中携带特定标识A时，则所述DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的第三方的IP地址设置为1.1.0.0，所述DT-AS和所述第三方AS预先约定当第三方的IP地址为1.1.0.0时，则DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的DT-AS的端口号设置为1，所述DT-AS和所述第三方AS预先约定当所述trigger消息中的DT-AS的端口号为1时，则DT-AS可以识别出该消息为trigger消息。
　　　第三方AS可以将trigger消息中的所述DT-AS的IP地址和端口号分别设置为1.1.1.1和0，所述DT-AS通过IP地址为1.1.1.1和端口号0接收到trigger消息时，则可以识别出该消息为trigger消息。
　　　所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　本发明提供一种发送触发消息的设备，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　参考图11，图11是本发明实施例提供的一种M2M UE的结构示意图。如图11所示，所述M2M UE包括：
　　　接收单元1101，用于接收设备触发应用服务器DT-AS发送的trigger消息；
　　　具体的，参考图5，DT-AS将trigger消息发送到M2M UE时，则所述M2M UE接收所述trigger消息。
　　　建立单元1102，用于根据所述trigger消息中携带的第三方应用服务器AS的标识，和所述第三方AS建立连接；
所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　其中，所述第三方AS预先存储所述M2M UE标识，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　本发明提供一种发送触发消息的设备，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　参考图12，图12是本发明实施例提供的一种应用服务器的结构示意图。参考图12，图12是本发明实施例提供的一种应用服务器1200，本发明具体实施例并不对所述应用服务器的具体实现做限定。所述应用服务器1200包括：
　　　处理器(英文：processor)1201，通信接口(英文：Communications Interface)1202，存储器(英文：memory)1203，总线1204。
　　　处理器1201，通信接口1202，存储器1203通过总线1204完成相互间的通信。
　　　通信接口1202，用于与设备触发应用服务器进行通信；
　　　处理器1201，用于执行程序。
　　　具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。
　　　处理器1201可能是一个中央处理器（英文：central processing unit，缩写：CPU。
　　　存储器1203，用于存储程序。存储器1203可以是易失性存储器（英文：volatile memory），例如随机存取存储器（英文：random-access memory，缩写：RAM），或者非易失性存储器（英文：non-volatile memory），例如快闪存储器（英文：flash memory），硬盘（英文：hard disk drive，缩写：HDD）或固态硬盘（英文：solid-state drive，缩写：SSD）。处理器1201根据存储器1203存储的程序指令，执行以下方法：
　　　当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息；
　　　其中，所述trigger消息至少包括机器通信用户设备M2M UE标识，以使得所述DT-AS根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册，若是，则将所述trigger消息发送到所述M2M UE，并接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　接收所述DT-AS发送的所述trigger消息的响应消息；
　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　所述方法在所述第三方AS向所述DT-AS发送触发trigger消息之前，还包括：
　　　所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号；
　　　配置trigger消息中的第三方AS的IP地址和/或所述DT-AS的端口号为预先配置的值，所述预先配置的值用于所述DT-AS识别出所述trigger消息；或者，
　　　配置trigger消息中的所述DT-AS的IP地址和/或端口号分别为预先设置的IP地址和端口号，使得所述DT-AS通过所述预先设置的IP地址和端口号接收到消息时能识别出所述消息为trigger消息。
　　　所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号，包括：
　　　获取预先配置在第三方AS上的所述DT-AS的IP地址和/或端口号；或者，
　　　获取预先配置在第三方AS上的所述M2M UE的外接External IP地址，将所述外接IP地址发送到DNS上解析获取所述DT-AS的IP地址；或者，
　　　获取预先配置在第三方AS上的所述DT-AS的IP地址，将所述DT-AS的IP地址发送到DNS上解析获取所述DT-AS的IP地址。
　　　所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　本发明提供一种发送触发消息的方法，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
参考图13，图13是本发明实施例提供的一种设备触发应用服务器的结构示意图。参考图13，图13是本发明实施例提供的一种设备触发应用服务器1300，本发明具体实施例并不对所述设备触发应用服务器的具体实现做限定。所述设备触发应用服务器1300包括：
　　　处理器(英文：processor)1301，通信接口(英文：Communications Interface)1302，存储器(英文：memory)1303，总线1304。
　　　处理器1301，通信接口1302，存储器1303通过总线1304完成相互间的通信。
　　　通信接口1302，用于与应用服务器及机器通信用户设备进行通信；
　　　处理器1301，用于执行程序。
　　　具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。
　　　处理器1301可能是一个中央处理器（英文：central processing unit，缩写：CPU。
　　　存储器1303，用于存储程序。存储器1303可以是易失性存储器（英文：volatile memory），例如随机存取存储器（英文：random-access memory，缩写：RAM），或者非易失性存储器（英文：non-volatile memory），例如快闪存储器（英文：flash memory），硬盘（英文：hard disk drive，缩写：HDD）或固态硬盘（英文：solid-state drive，缩写：SSD）。处理器1301根据存储器1303存储的程序指令，执行以下方法：
　　　接收第三方应用服务器AS发送的trigger消息，所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册；
　　　若是，则将所述trigger消息发送到所述M2M UE标识所对应的M2M UE；
　　　接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
　　　所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　所述方法在所述DT-AS接收所述第三方AS发送的trigger消息之后，还包括：
　　　根据所述trigger消息中携带预先设定的特定标识识别出所述trigger消息；或者，
　　　根据所述trigger消息中的预先设定的第三方AS的IP地址和/或所述DT-AS的端口号识别出所述trigger消息；或者，
　　　DT-AS在预先设定的IP地址和/或端口号接收消息时识别出所述消息为trigger消息。
　　　所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
　　　本发明提供一种设备触发应用服务器，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　参考图14，图14是本发明实施例提供的一种机器通信用户设备的结构示意图。参考图14，图14是本发明实施例提供的一种机器通信用户设备1400，本发明具体实施例并不对所述机器通信用户设备的具体实现做限定。所述机器通信用户设备1400包括：
　　　处理器(英文：processor)1401，通信接口(英文：Communications Interface)1402，存储器(英文：memory)1403，总线1404。
　　　处理器1401，通信接口1402，存储器1403通过总线1404完成相互间的通信。
　　　通信接口1402，用于与应用服务器及设备触发应用服务器进行通信；
　　　处理器1401，用于执行程序。
　　　具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。
　　　处理器1401可能是一个中央处理器（英文：central processing unit，缩写：CPU。
　　　存储器1403，用于存储程序。存储器1403可以是易失性存储器（英文：volatile memory），例如随机存取存储器（英文：random-access memory，缩写：RAM），或者非易失性存储器（英文：non-volatile memory），例如快闪存储器（英文：flash memory），硬盘（英文：hard disk drive，缩写：HDD）或固态硬盘（英文：solid-state drive，缩写：SSD）。处理器1401根据存储器1403存储的程序指令，执行以下方法：
　　　接收设备触发应用服务器DT-AS发送的trigger消息；
　　　根据所述trigger消息中携带的第三方应用服务器AS的标识，和所述第三方AS建立连接；
　　　所述trigger消息至少包括机器通信用户终端M2M UE标识；
　　　其中，所述第三方AS预先存储所述M2M UE标识，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
　　　本发明提供一种机器通信用户设备，当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息，所述trigger消息至少包括机器通信用户设备M2M UE标识，所述DT-AS根据所述M2M UE标识判断所述M2M UE是否注册在所述DT-AS所在的网络中，若是，则将所述trigger消息发送到所述M2M UE，从而实现DT-AS识别tirgger消息，以便于所述M2M UE和所述第三方AS建立连接。
　　　以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等，均应包含在本发明的保护范围之内。

Claims (14)

  1. 一种发送触发消息的方法，其特征在于，所述方法包括：
    　　　当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息；
    　　　其中，所述trigger消息至少包括机器通信用户设备M2M UE标识，以使得所述DT-AS根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册，若是，则将所述trigger消息发送到所述M2M UE，并接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
    　　　接收所述DT-AS发送的所述trigger消息的响应消息；
    　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
  2. 根据权利要求1所述的方法，其特征在于，所述方法在所述第三方AS向所述DT-AS发送触发trigger消息之前，还包括：
    　　　所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号；
    　　　配置trigger消息中的第三方AS的IP地址和/或所述DT-AS的端口号为预先配置的值，所述预先配置的值用于所述DT-AS识别出所述trigger消息；或者，
    　　　配置trigger消息中的所述DT-AS的IP地址和/或端口号分别为预先设置的IP地址和端口号，使得所述DT-AS通过所述预先设置的IP地址和端口号接收到消息时能识别出所述消息为trigger消息。
  3. 　　　根据权利要求2所述的方法，其特征在于，所述第三方AS获取所述DT-AS的IP地址和/或所述DT-AS的端口号，包括：
    　　　获取预先配置在第三方AS上的所述DT-AS的IP地址和/或端口号；或者，
    　　　获取预先配置在第三方AS上的所述M2M UE的外接External IP地址，将所述外接IP地址发送到DNS上解析获取所述DT-AS的IP地址。
  4. 根据权利要求1-3任意一项所述的方法，其特征在于，
    　　　所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
  5. 一种发送触发消息的方法，其特征在于，所述方法包括：
    　　　设备触发应用服务器DT-AS接收第三方应用服务器AS发送的trigger消息，所述trigger消息至少包括机器通信用户终端M2M UE标识；
    　　　根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册；
    　　　若是，则将所述trigger消息发送到所述M2M UE标识所对应的M2M UE；
    　　　接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
    　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
  6. 　　　根据权利要求5所述的方法，其特征在于，所述方法在所述DT-AS接收所述第三方AS发送的trigger消息之后，还包括：
    　　　根据所述trigger消息中携带预先设定的特定标识识别出所述trigger消息；或者，
    　　　根据所述trigger消息中的预先设定的第三方AS的IP地址和/或所述DT-AS的端口号识别出所述trigger消息；或者，
    　　　DT-AS在预先设定的IP地址和/或端口号接收消息时识别出所述消息为trigger消息。
  7. 　　　根据权利要求5或6所述的方法，其特征在于，所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
  8. 　　　一种应用服务器，其特征在于，所述应用服务器为第三方应用服务器AS，包括：
    　　　发送单元，用于当第三方应用服务器AS需要与机器通信用户设备M2M UE建立连接时，所述第三方AS向设备触发应用服务器DT-AS发送触发trigger消息；
    　　　其中，所述trigger消息至少包括机器通信用户设备M2M UE标识，以使得所述DT-AS根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册，若是，则将所述trigger消息发送到所述M2M UE，并接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
    　　　接收单元，用于接收所述DT-AS发送的所述trigger消息的响应消息；
    　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
  9. 　　　根据权利要求8所述的应用服务器，其特征在于，所述应用服务器还包括获取单元和设置单元；
    　　　所述获取单元，具体用于：
    　　　获取所述DT-AS的IP地址和/或所述DT-AS的端口号；
    　　　所述设置单元，具体用于：
    　　　配置trigger消息中的第三方AS的IP地址和/或所述DT-AS的端口号为预先配置的值，所述预先配置的值用于所述DT-AS识别出所述trigger消息；或者，
    　　　配置trigger消息中的所述DT-AS的IP地址和/或端口号分别为预先设置的IP地址和端口号，使得所述DT-AS通过所述预先设置的IP地址和端口号接收到消息时能识别出所述消息为trigger消息。
  10. 据权利要求9所述的应用服务器，其特征在于，所述获取单元，具体用于：
    　　　获取预先配置在第三方AS上的所述DT-AS的IP地址和/或端口号；或者，
    　　　获取预先配置在第三方AS上的所述M2M UE的外接External IP地址，将所述外接IP地址发送到DNS上解析获取所述DT-AS的IP地址。
  11. 　　　根据权利要求8-10任意一项所述的应用服务器，其特征在于，所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
  12. 　　　一种设备触发应用服务器，其特征在于，所述设备触发应用服务器包括：
    　　　第一接收单元，用于接收第三方应用服务器AS发送的trigger消息，所述trigger消息至少包括机器通信用户终端M2M UE标识；
    　　　判断单元，用于根据所述M2M UE标识判断所述M2M UE是否在所述DT-AS中注册；
    　　　发送单元，用于若是，则将所述trigger消息发送到所述M2M UE标识所对应的M2M UE；
    　　　第二接收单元，用于接收所述M2M UE发送的所述trigger消息的响应消息，向所述第三方AS发送所述trigger消息的响应消息；
    　　　所述trigger消息至少包括机器通信用户终端M2M UE标识；
    　　　其中，所述M2M UE连接在所述DT-AS所在的网络中，所述DT-AS是3GPP网络中的服务器，所述第三方AS是3GPP外部网络中的M2M服务器。
  13. 根据权利要求12所述的设备触发应用服务器，其特征在于，所述设备触发应用服务器还包括识别单元，所述识别单元具体用于：
    　　　根据所述trigger消息中携带预先设定的特定标识识别出所述trigger消息；或者，
    　　　根据所述trigger消息中的预先设定的第三方AS的IP地址和/或所述DT-AS的端口号识别出所述trigger消息；或者，
    　　　在预先设定的IP地址和/或端口号接收消息时识别出所述消息为trigger消息。
  14. 根据权利要求12或13所述的设备触发应用服务器，其特征在于，所述第三方AS和所述DT-AS之间通过diameter协议或者HTTP协议通信。
PCT/CN2013/081429 2013-08-14 2013-08-14 发送触发消息的方法及设备 WO2015021608A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP13891523.6A EP3021601B1 (en) 2013-08-14 2013-08-14 Method and device for sending trigger message
PCT/CN2013/081429 WO2015021608A1 (zh) 2013-08-14 2013-08-14 发送触发消息的方法及设备
US15/042,317 US20160165379A1 (en) 2013-08-14 2016-02-12 Method for Sending Trigger Message and Device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/081429 WO2015021608A1 (zh) 2013-08-14 2013-08-14 发送触发消息的方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/042,317 Continuation US20160165379A1 (en) 2013-08-14 2016-02-12 Method for Sending Trigger Message and Device

Publications (1)

Publication Number Publication Date
WO2015021608A1 true WO2015021608A1 (zh) 2015-02-19

Family

ID=52467927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/081429 WO2015021608A1 (zh) 2013-08-14 2013-08-14 发送触发消息的方法及设备

Country Status (3)

Country Link
US (1) US20160165379A1 (zh)
EP (1) EP3021601B1 (zh)
WO (1) WO2015021608A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6364069B2 (ja) 2013-05-06 2018-07-25 コンヴィーダ ワイヤレス， エルエルシー デバイストリガ
US9866645B2 (en) * 2013-09-13 2018-01-09 Visa International Service Association Actionable notifications apparatuses, methods and systems

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625291A (zh) * 2011-01-31 2012-08-01 中兴通讯股份有限公司 机器类型通信服务器向机器类通信终端通信的方法和系统
CN102740452A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 机器类通信终端触发方法及装置
CN102958025A (zh) * 2011-08-24 2013-03-06 中兴通讯股份有限公司 发送mtc设备触发信息的方法、系统和目标用户设备
CN103096264A (zh) * 2011-10-31 2013-05-08 中兴通讯股份有限公司 设置触发信息有效时间方法、系统和用户设备
WO2013113186A1 (zh) * 2012-02-03 2013-08-08 中兴通讯股份有限公司 一种mtc用户设备触发信息的发送方法、系统和用户设备

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7931784B2 (en) * 2008-04-30 2011-04-26 Xyleco, Inc. Processing biomass and petroleum containing materials
CN103534960B (zh) * 2011-05-11 2017-08-08 Lg电子株式会社 用于无线通信系统中的mtc的方法和设备
US9392396B2 (en) * 2011-11-13 2016-07-12 Lg Electronics Inc. Method and device for triggering machine-type communication MTC in wireless communication system
CN104039659A (zh) * 2012-01-06 2014-09-10 雀巢产品技术援助有限公司 包括容器和具有铰接盖的帽罩的包装
CN103248608B (zh) * 2012-02-03 2017-11-21 中兴通讯股份有限公司 一种发送触发信息的方法、系统及装置
CN103517230B (zh) * 2012-06-19 2018-05-08 中兴通讯股份有限公司 触发信息发送和协议转换的方法及系统
WO2014109988A2 (en) * 2013-01-08 2014-07-17 Ingterdigital Patent Holdings, Inc. Method and apparatus for triggering devices and delivering small data
EP3000248B1 (en) * 2013-05-22 2021-10-13 Convida Wireless, LLC Network assisted bootstrapping for machine-to-machine communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625291A (zh) * 2011-01-31 2012-08-01 中兴通讯股份有限公司 机器类型通信服务器向机器类通信终端通信的方法和系统
CN102740452A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 机器类通信终端触发方法及装置
CN102958025A (zh) * 2011-08-24 2013-03-06 中兴通讯股份有限公司 发送mtc设备触发信息的方法、系统和目标用户设备
CN103096264A (zh) * 2011-10-31 2013-05-08 中兴通讯股份有限公司 设置触发信息有效时间方法、系统和用户设备
WO2013113186A1 (zh) * 2012-02-03 2013-08-08 中兴通讯股份有限公司 一种mtc用户设备触发信息的发送方法、系统和用户设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3021601A4 *

Also Published As

Publication number Publication date
US20160165379A1 (en) 2016-06-09
EP3021601A1 (en) 2016-05-18
EP3021601B1 (en) 2021-12-22
EP3021601A4 (en) 2016-07-20

Similar Documents

Publication Publication Date Title
WO2021010693A1 (en) Method and apparatus for identifying user in ran communication system
WO2011147358A1 (zh) 机器类型通讯设备的业务控制方法和相关装置及系统
WO2015194890A1 (en) Method and apparatus for establishing user plane bearer
WO2015016654A1 (en) Method for maintaining service continuity in heterogeneous communications system
WO2013009053A2 (en) Method and apparatus for supporting mobility of user equipment
WO2016024695A1 (en) Method and apparatus for profile download of group devices
WO2016006969A1 (en) Inter-menb handover method and device in a small cell system
WO2016021870A1 (en) Methods for supprting access and paging of low complexity user equipment
WO2017119723A1 (en) A method for ue context and ue connection resume
WO2011142567A2 (en) Handover method supporting terminal mobility
WO2014185708A1 (en) System and method for ip session continuity in device-to-device communication system
WO2012108660A2 (ko) 이동통신 네트워크 내에서 제어 평면을 담당하는 서버 및 그 서버에서 서비스를 제어하는 방법
WO2013118978A1 (ko) 무선 통신 시스템에서 small data를 효율적으로 전송하는 방법 및 장치
WO2020218843A1 (en) Method and system for providing non-access stratum (nas) message protection
WO2015137637A1 (en) Method for supporting proximity-based service configuring for ue
WO2012106982A1 (zh) 一种快速校验国际移动设备标识的方法及系统
WO2015037909A1 (ko) 통신 시스템에서 푸쉬 서비스 제공을 위한 방법 및 장치
WO2017222344A1 (en) Data transmission supporting method and apparatus
WO2018174427A1 (en) Method and device for controlling data transmission state
WO2009134064A2 (en) Method and device to support interworking between 3g system and sae system
CN103718640A (zh) 一种控制和转发解耦下协议处理方法及控制面设备、转发面设备
WO2018030861A1 (en) Method for performing light connection control on user equipment and corresponding equipment
WO2015174806A1 (ko) 음성 호 서비스 품질을 높이는 방법 및 장치
WO2012165805A2 (ko) 2 이상의 네트워크 기반 데이터 동시 전송 서비스 방법 및 장치
WO2015020488A1 (ko) 인증 정보를 얻는 방법 및 장치

Legal Events

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

Ref document number: 13891523

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2013891523

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE