WO2013113186A1 - 一种mtc用户设备触发信息的发送方法、系统和用户设备 - Google Patents

一种mtc用户设备触发信息的发送方法、系统和用户设备 Download PDF

Info

Publication number
WO2013113186A1
WO2013113186A1 PCT/CN2012/073344 CN2012073344W WO2013113186A1 WO 2013113186 A1 WO2013113186 A1 WO 2013113186A1 CN 2012073344 W CN2012073344 W CN 2012073344W WO 2013113186 A1 WO2013113186 A1 WO 2013113186A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
trigger information
iwf
short message
trigger
Prior art date
Application number
PCT/CN2012/073344
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 US14/350,158 priority Critical patent/US9467508B2/en
Priority to EP12867127.8A priority patent/EP2753106B1/en
Publication of WO2013113186A1 publication Critical patent/WO2013113186A1/zh

Links

Classifications

    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events

Definitions

  • the present invention relates to a wireless communication technology, and more particularly to a method, system, and user equipment for transmitting MTC user equipment trigger information. Background technique
  • Machine to Machine (M2M) technology refers to all the techniques and means of establishing a connection between machines.
  • the M2M concept emerged in the 1990s, but only stayed in the theoretical stage.
  • mobile communication technology mobile communication technology has become possible to realize the networking of machine equipment.
  • the M2M business appeared on the market and developed rapidly in the following years, becoming the focus of many communication equipment vendors and telecom operators. At present, the number of machines in the world is much larger than that of people, so it is foreseeable that M2M technology has a good market prospect.
  • the existing mobile communication networks are mainly designed for communication between people, and the communication between machines and machines, people and machines is insufficiently optimized.
  • how operators can provide M2M communication services at low cost is also the key to the successful deployment of M2M communication.
  • the solution is to maximize the reuse of existing networks, reducing the impact of a large number of M2M communications on the network and the complexity of operational maintenance.
  • MTC Machine Type Communication
  • H2H Human to Human
  • MTC Machine to Man communication services
  • the 3GPP Evolved Packet System includes radio access networks (such as UMTS, Universal Terrestrial Radio Access Network (UTRAN), evolved UTRAN (E-UTRAN, Evolved UTRAN), GSM/EDGE Wireless access network (GERAN, GSM/EDGE Radio Access Network) and core network.
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • SG Serving Gateway
  • PDN Packet Data Network Gateway
  • other network elements in the GPRS core network comprises a serving GPRS support node (SGSN, serving GPRS support node) and other network elements; included in the E-UTRAN evolved node B (eNB, evolved node B) 0
  • the triggering of the MTC user equipment is one of the basic requirements for the MTC system.
  • the problem of the requirement is that the MTC server (Server) can be used to control the communication of the MTC user.
  • the polling is initiated by means of polling.
  • the MTC server is sometimes required to poll the data from the MTC UE. If the MTC server fails to query or the IP address of the MTC UE is unavailable, the MTC server may trigger establishment of communication with the MTC UE through the MTC UE.
  • the network reports to the MTC server that the MTC UE triggers the failure, and the MTC UE triggers the implementation in 3GPP through control plane signaling.
  • the MTC UE triggers the mobile originating (MO, Mobile Originated) and mobile called (MT, Mobile Terminating) services, that is, the MTC UE transmits or receives information.
  • the proposed solution includes: sending the trigger information of the MTC UE by short (SMS), or sending the trigger information of the MTC UE through the control plane signaling, or sending the data through the user plane.
  • MTC trigger information For the manner in which the MTC UE trigger information is sent by the control plane signaling, the MTC server sends the control plane signaling including the MTC UE trigger information to the MTC Interworking Function (MTC-IWF, MTC InterWorking Function), and the MTC-IWF selects the T5 or T4 interface.
  • the MTC server sends the MTC UE trigger information to the MTC-IWF, and the MTC-IWF obtains the IP address of the MTC UE, and sends the MTC UE trigger information to the MTC UE by using the user.
  • the MTC architecture in 3GPP is shown in Figure 1.
  • the application on the MTC UE communicates with the MTC server through the API interface, or directly with the gateway GPRS support node (GGSN in the 3GPP network through the Gi/SGi interface).
  • GGSN gateway GPRS support node
  • MTC server communicates with GGSN/PGW through Gi/SGi interface; GGSN/PGW communicates with MTC UE through Radio Access Network (RAN);
  • MTC server passes Tsp The interface sends control plane signaling including the trigger information of the MTC UE to the MTC-IWF, and the MTC-IWF sends the control plane signaling to the MME and/or the SGSN and/or the MSC (MME/SGSN/MSC) or the SMS service center (SMSC, The Short Message Service Center ) is sent to the MTC UE through the RAN.
  • MME Mobility Management Entity
  • FIG. 2 is a schematic diagram of the MTC server transmitting the trigger information including the MTC UE on the T5 interface by using the MTC-IWF, where the MTC server directly sends the control plane signaling including the trigger information of the MTC UE to the MTC-IWF through the Tsp interface, and the MTC-IWF passes
  • the T5 interface sends the MTC UE trigger information to the MME/SGSN/MSC, and further sends the information to the MTC UE.
  • the MTC UE may trigger the information according to the MTC UE. Show, communicate with the MTC server, such as establishing a user plane bearer, or communicating with the MTC server through SMS.
  • the main purpose of the embodiments of the present invention is to provide a method, a system, and a user equipment for transmitting MTC UE trigger information, and determining a manner for transmitting the trigger information of the MTC UE through the T5 interface.
  • An embodiment of the present invention provides a method for sending trigger information of an MTC UE, including:
  • the MTC server sends the MTC UE trigger information to the MTC-IWF.
  • the MTC-IWF encapsulates the trigger information into a short message, and sends the information to the service node of the MTC UE through a T5 interface;
  • the service node that receives the trigger information sent by the MTC-IWF by using a short message sends the trigger information to the MTC UE by using control signaling or a short message.
  • the MTC UE triggering information sent by the MTC server includes: the MTC UE external identifier and the application ID.
  • the method further includes: the MTC-IWF authenticating the MTC server, and determining that it is an MTC server authorized to send trigger information;
  • the trigger information sent by the MTC server performs load control.
  • the MTC-IWF encapsulates the trigger information of the MTC UE into a short message, and includes: converting the content included in the trigger information into a corresponding field in the short message, and expanding a field in the short message for indicating the content of the short message, so that It is used to indicate that the content of the short message is trigger information, and And replacing the MTC UE external identifier in the trigger information with an MTC UE internal identifier; the MTC UE internal identifier is obtained by the MTC-IWF according to the MTC UE external identifier from an HSS query.
  • the MTC-IWF sends the short message to the service node of the MTC UE through the T5 interface, including:
  • the MTC-IWF queries the HSS for the T5 address of the service node of the MTC UE according to the external identifier of the MTC UE, and sends the short message to the corresponding service node according to the T5 address obtained by the query.
  • the method further includes:
  • the MTC-IWF When the trigger information in the short message includes a single transmission field set by the MTC-IWF, the MTC-IWF does not store the short message; the trigger information in the short message does not include a single transmission field, but includes The valid time field, the MTC-IWF stores the short message.
  • the method further includes:
  • the MTC-IWF sends the short message to the service node by using a parallel or serial manner.
  • the method further includes: the serving node performing load control on the trigger information sent by the MTC-IWF.
  • the serving node sends the trigger information to the MTC UE by using control signaling or a short message, which is:
  • the serving node determines that both the self and the MTC UE support the short message
  • the service sends the trigger message to the MTC UE by using a short message; otherwise, the trigger message is sent to the MTC UE by using control signaling.
  • the method further includes: the serving node modifying the destination address of the short message from the MTC-IWF to the internal identifier of the MTC UE, and forwarding the identifier to the MTC UE.
  • the method further includes:
  • the service node parses the trigger information from the short message from the MTC-IWF, and sends the trigger information to the MTC UE by using control signaling; the destination address of the control signaling is the MTC
  • control signaling is NAS signaling or dedicated control signaling.
  • the service node comprises: an MME and/or an SGSN and/or an MSC.
  • the method further includes: sending, by the serving node and the MTC-IWF, the trigger information transmission report to the MTC server by using the MTC UE;
  • the application ID in the information identifies an application that needs to be triggered, and activates the application to establish application layer communication with the MTC server.
  • the embodiment of the present invention further provides a system for transmitting MTC UE trigger information, including: an MTC server, an MTC UE, an MTC-IWF, and a service node of the MTC UE, where:
  • the MTC server is configured to send MTC UE trigger information to the MTC-IWF, where the MTC-IWF is configured to encapsulate the trigger information into a short message, and send the message to the service node by using a T5 interface;
  • the service node is configured to send the trigger information to the MTC UE by using a control signaling or a short message after receiving the trigger information sent by the MTC-IWF by using a short message;
  • the MTC UE is configured to receive the trigger information.
  • the MTC-IWF is further configured to: after receiving the trigger information, perform identity verification on the MTC server, determine that it is an MTC server that is authorized to send trigger information; and send the MTC server to the MTC server.
  • the trigger information is used for load control; and is further configured to send a trigger information transmission report to the MTC server after the trigger information is received by the MTC UE.
  • the MTC-IWF is further configured to convert the content included in the trigger information into a corresponding field in the short message, and expand a field in the short message for indicating the content of the short message, so that the content of the short message is used to indicate that the short message content is Triggering information, and replacing the MTC UE external identifier in the trigger information with an MTC UE internal identifier;
  • the MTC-IWF is further configured to obtain the internal identifier of the MTC UE.
  • the MTC-IWF is further used by the MTC UE external identifier to query the HSS for the T5 address of the serving node, and send the short message to the corresponding service node according to the T5 address obtained by the query.
  • the service node is further configured to perform load control on the trigger information sent by the MTC-IWF, and is further configured to send a trigger information transmission to the MTC-IWF after the MTC UE receives the trigger information. report.
  • the serving node is further configured to: when the user and the MTC UE support the short message, send the trigger message to the MTC UE by using a short message; otherwise, send the control message to the MTC UE.
  • the trigger message when the user and the MTC UE support the short message, send the trigger message to the MTC UE by using a short message; otherwise, send the control message to the MTC UE.
  • the trigger message when the user and the MTC UE support the short message, send the trigger message to the MTC UE by using a short message; otherwise, send the control message to the MTC UE.
  • the control signaling is NAS signaling or dedicated control signaling.
  • the MTC UE is further configured to send a trigger information transmission report to the MTC server by using the serving node and the MTC-IWF; and pass the trigger information.
  • the application ID identifies an application that needs to be triggered, and activates the application to establish application layer communication with the MTC server.
  • An embodiment of the present invention further provides an MTC UE, including: a receiving unit, a sending unit, and a setting unit; wherein:
  • the receiving unit is configured to receive trigger information sent by the MTC server by using the MTC-IWF and the service node;
  • a sending unit configured to: after receiving the trigger information, return a trigger information transmission report to the MTC server by using the service node and the MTC-IWF;
  • the setting unit is configured to set the trigger information transmission report content.
  • the MTC UE further includes an application unit, configured to establish application layer communication with the MTC server.
  • the MTC-IWF receives the trigger information sent by the MTC server, and the MTC-IWF encapsulates the trigger information into a short message, and sends the trigger information to the MME/SGSN/MSC through the T5 interface.
  • the MME/SGSN/MSC that receives the trigger information sends the trigger information to the MTC UE through control signaling or short message. In this way, the trigger information can be sent on the T5 interface, and the signaling flow of the trigger information of the T5 interface is determined.
  • FIG. 1 is a schematic diagram of an MTC architecture in a prior art 3GPP
  • FIG. 2 is a schematic diagram of sending trigger information by the MTC-IWF through the T5 interface in the prior art
  • FIG. 3 is a schematic flowchart of sending trigger information through the T5 interface according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of sending trigger information through a T5 interface according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a triggering message sent by a service node by using a short message according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a triggering message sent by a serving node by using a control signaling according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of sending trigger information by using a T5 interface according to an embodiment of the present invention
  • System structure diagram detailed description
  • the MTC UE trigger information is simply referred to as trigger information.
  • the basic idea of transmitting the trigger information of the MTC UE through the T5 interface in the embodiment of the present invention is as shown in FIG. 3, which includes:
  • Step 101 The MTC Server sends the trigger information to the MTC-IWF.
  • the trigger information includes at least: the MTC UE external identifier and the application ID.
  • the MTC Server described in the embodiment of the present invention includes: an MTC service capability server and an MTC application server, as shown in FIG. 1 .
  • the MTC-IWF After receiving the trigger information, the MTC-IWF first authenticates the identity of the MTC Server that sends the trigger information to determine that the MTC Server is the MTC Server that is authorized to send trigger information. At the same time, the MTC-IWF also performs load control on the trigger information sent by the MTC Server to avoid network congestion or node overload.
  • the specific implementation of the encapsulation is: converting the content included in the trigger information into a corresponding field in the short message, and expanding a field in the short message for indicating the content of the short message, so that the content of the short message is used as the trigger information, and the trigger information is
  • the MTC UE external identifier is replaced with the MTC UE internal identifier.
  • the MTC UE internal identifier is obtained from the HSS query according to the MTC UE external identifier.
  • the MTC-IWF sends the short message to the serving node of the MTC UE through the T5 interface, including: the MTC-IWF queries the HSS for the T5 address of the serving node of the MTC UE according to the external identifier of the MTC UE, and sends the T5 address obtained according to the query to the corresponding service node. send messages.
  • the MTC-IWF When sending to the service node of the MTC UE: If the trigger information in the short message includes a single transmission field set by the MTC-IWF, the MTC-IWF does not store the short message; if the trigger information in the short message does not include a single transmission field, However, if the valid time field is included, the MTC-IWF stores the short message.
  • the single-send field indicates that the MTC-IWF only sends a short message to the service node; the valid time field indicates that the MTC-IWF can repeatedly send a short message to the service node in the valid time field.
  • the MTC-IWF can also send short messages to the service node by using parallel or serial.
  • Step 103 The serving node that receives the trigger information sent by the MTC-IWF by using the short message sends the trigger information to the MTC UE by using control signaling or a short message.
  • the service node needs to perform load control on the trigger information sent by the MTC-IWF to avoid or reduce Light network congestion or node overload.
  • the serving node determines that both the self and the MTC UE support the short message
  • the service node sends a trigger message to the MTC UE by using the short message; otherwise, the trigger message is sent to the MTC UE by using the control signaling.
  • the service node modifies the destination address of the short message from the MTC-IWF to the MTC UE internal identifier, and then forwards the message to the MTC UE.
  • the serving node parses the trigger information from the short message from the MTC-IWF, and sends the trigger information to the MTC UE through the control signaling; the destination address of the control signaling is the MTC UE internal identifier.
  • the control signaling is NAS signaling or dedicated control signaling.
  • the MTC UE After receiving the trigger information, the MTC UE identifies the application that needs to be triggered by using the application ID in the trigger information, and activates the application to establish application layer communication with the MTC server.
  • the above service nodes include: MME and / or SGSN and / or MSC.
  • Step 201 The MTC Server sends trigger information to the MTC-IWF.
  • the MTC server When the MTC server needs to trigger an MTC UE to establish application layer communication with it, generate a trigger information, where the trigger information includes at least the MTC UE external identifier (ext-ID) and an application ID, and the application ID is used for the MTC.
  • the UE identifies the application that needs to be triggered; the MTC Server queries the DNS for the IP address of the MTC-IWF according to the external identifier of the MTC UE.
  • the MTC server sends trigger information to the MTC-IWF through the Tsp interface.
  • Step 202 After receiving the trigger information, the MTC-IWF authenticates and authorizes the MTC Server. If the MTC server is legal, the MTC-IWF accepts the trigger information, otherwise the MTC-IWF discards the trigger information.
  • Step 203 The MTC-IWF queries the T5 address of the serving node of the MTC UE.
  • the MTC-IWF queries the HSS for the T5 address of the serving node of the MTC UE according to the MTC UE external identifier.
  • the service node includes: an MME and/or an SGSN and/or an MSC.
  • the MTC-IWF can query the T5 address of one or more of the MME, SGSN, and MSC.
  • the MTC-IWF converts the content included in the trigger information into a corresponding field in the short message according to the format requirement of the short message specified by the protocol.
  • the existing short message structure has a field for indicating the content of the short message, and the field is expanded. It is used to indicate that the content of the short message is trigger information.
  • the MTC-IWF encapsulates the trigger message, it also needs to replace the MTC UE external identifier with the internal identifier.
  • the MTC UE internal identifier is MTC-IWF and is obtained from the HSS query according to the MTC UE external identifier.
  • the implementation of the method in the embodiment of the present invention is that the MTC-IWF sends the trigger information through the T5 interface.
  • the MTC-IWF needs to send the trigger information through the T5 interface according to the local policy and the information queried from the HSS.
  • the trigger information is not sent through the T5 interface, and the process ends.
  • the local policy for example: local network deployment, service node type of the MTC UE, local operator preference scheme, etc.; information queried from the HSS, for example: T5 address of the serving node of the MTC UE, internal identifier of the MTC UE (better It is the IMSI of the MTC UE, and the subscription information of the MTC UE, and the like.
  • Step 205 The MTC-IWF sends a short message to the corresponding server node (MME and/or SGSN and/or MSC) according to the queried T5 address.
  • the MTC-IWF sends the short message to the SGSN through the T5a interface; and/or sends the short message to the MME through the T5b interface; and/or sends the short message to the MSC through the T5c interface.
  • the MTC-IWF If the trigger information indicates that the triggering information is sent in a single transmission, the MTC-IWF does not need to store the trigger information. Otherwise, the MTC-IWF stores the trigger information. Specifically, the stored trigger information is the encapsulated short message. , and send SMS repeatedly.
  • the MTC-IWF may set a single-send field in the trigger information to indicate that the trigger information is sent through the T5 interface in a single transmission; otherwise, the trigger information may be set. a valid time period field in which the MTC-IWF repeatedly transmits the short message as long as the MTC-IWF does not receive the response that the trigger information is successfully sent; until the MTC-IWF receives the response that the trigger information is successfully sent. After that, stop sending, and delete the text message.
  • the manner in which the MTC-IWF sends short messages to the MME and/or the SGSN and/or the MSC may be sent in parallel or serially, and is specifically determined by the MTC-IWF based on a comprehensive measurement of the local policy and the information queried from the HSS.
  • the local policy for example: local network deployment, service node type of the MTC UE, local operator preference scheme, etc.;
  • the information that is queried from the HSS for example, the T5 address of the serving node of the MTC UE, the internal identifier of the MTC UE (preferably the IMSI of the MTC UE), and the subscription information of the MTC UE.
  • Step 206 The service node performs step 207 by determining to send a trigger message by using a short message. When it is determined that the trigger message is sent by using the control signaling, step 208 is performed.
  • the service node determines, according to the local policy and the subscription information of the MTC UE, that both the self and the MTC UE support the short message, and determines that the trigger message is sent by using the short message; otherwise, determining that the trigger message is sent by using the control signaling.
  • the service node requests the MTC-IWF to obtain the subscription information of the MTC UE, and the MTC-IWF queries the HSS for the subscription information of the MTC UE and returns.
  • Step 207 The service node sends a trigger message by using a short message.
  • the method specifically includes: Step 2071: The serving node modifies the destination address in the short message sent by the MTC-IWF from the T5 address to the internal identifier of the MTC UE, and then forwards the message to the MTC. UE.
  • Step 2072 the MTC UE returns a trigger information transmission report to the service node.
  • the MTC UE After receiving the short message, the MTC UE parses the trigger information and returns a trigger information transmission report to the service node, indicating that the MTC UE receives the trigger information, that is, the trigger information is successfully sent.
  • the trigger information transmission 4 can be sent by SMS or control signaling.
  • the service node sets a message waiting identifier, waits for the MTC-IWF to resend the short message and forwards it to the MTC UE until receiving the trigger information transmission report returned by the MTC UE.
  • the reason for the failure to send the trigger information may be: the service node receives the failure response sent by the MTC UE, or the valid time specified by the valid time field expires, or the service node finds that the MTC UE is unreachable.
  • Step 2073 The service node sends a trigger information transmission report to the MTC-IWF.
  • the serving node forwards the trigger information transmission report from the MTC UE to the MTC-IWF, indicating
  • the MTC UE receives the trigger information, that is, the trigger information is successfully sent.
  • step 2074 the MTC-IWF sends a trigger information transmission message to the MTC server.
  • the MTC-IWF forwards the trigger information transmission report from the service node to the MTC server, indicating that the trigger information is successfully sent, and then proceeds to step 209.
  • Step 208 The service node sends a trigger message by using control signaling, as shown in FIG. 6, specifically:
  • Step 2081 The service node parses the trigger information from the short message, and sends the information to the MTC UE by using control signaling.
  • the control signaling may be NAS signaling or dedicated control signaling, etc.
  • the destination address of the control signaling is an internal identifier of the MTC UE.
  • Step 2082 the MTC UE returns a response message to the serving node.
  • the MTC UE After receiving the control signaling, the MTC UE parses the trigger information and returns a response message to the serving node, indicating that the MTC UE receives the trigger information, that is, the trigger information is successfully sent.
  • step 206 when the serving node determines that both the self and the MTC UE support the short message, it is determined that the trigger message is sent by using the short message; otherwise, it is determined that the trigger message is sent by the control signaling. Therefore, the MTC UE needs to return a response message to the serving node through control signaling.
  • Step 2083 The serving node sends a trigger information transmission report to the MTC-IWF. After receiving the response information of the MTC UE, the serving node generates a trigger information transmission report,
  • the MTC-IWF sends a message indicating that the trigger information is sent successfully.
  • the trigger information transmission report can be carried by SMS or control signaling.
  • Step 2084 The MTC-IWF sends a trigger information transmission report to the MTC server.
  • the MTC-IWF forwards the trigger information transmission report from the service node to the MTC server, indicating that the trigger information is successfully sent, and then proceeds to step 209.
  • Step 209 The MTC UE establishes application layer communication with the MTC Server, and the process ends.
  • the application layer communication means that the MTC UE identifies the application that needs to be triggered by using the application ID included in the trigger information, and activates the application to establish communication with the MTC server.
  • the embodiment of the present invention further provides a system, as shown in FIG. 7, including: a service node of an MTC server, an MTC UE, an MTC-IWF, and an MTC UE, where: an MTC server, used to the MTC- The IWF sends the MTC UE trigger information.
  • the MTC-IWF is configured to encapsulate the trigger information into a short message, and send the message to the service node through the T5 interface;
  • a service node configured to send, by using a short message, the trigger information sent by the MTC-IWF, and send the trigger information to the MTC UE by using control signaling or a short message;
  • the MTC UE is configured to receive trigger information.
  • the MTC-IWF is further configured to: after receiving the trigger information, perform identity verification on the MTC server, determine that it is an MTC server that is authorized to send trigger information; and perform load control on the trigger information sent by the MTC server; And after the MTC UE receives the trigger information, sends a trigger information transmission report to the MTC server.
  • the MTC-IWF is further configured to convert the content included in the trigger information into a corresponding field in the short message, and expand a field in the short message for indicating the content of the short message, so that the content of the short message is used to indicate the content of the short message, and the trigger information is used.
  • the MTC UE external identifier is replaced with the MTC UE internal identifier;
  • the MTC-IWF is also used to obtain the internal identifier of the MTC UE.
  • the MTC-IWF is also used to query the HSS for the T5 address of the service node to the HSS, and send a short message to the corresponding service node according to the T5 address obtained by the query.
  • the service node is further configured to perform load control on the trigger information sent by the MTC-IWF, and is further configured to send a trigger information transmission report to the MTC-IWF after the MTC UE receives the trigger information.
  • the serving node is further configured to send a trigger message to the MTC UE by using a short message when the self and the MTC UE support the short message; otherwise, send a trigger message to the MTC UE by using the control signaling; the control signaling is a NAS signaling or a dedicated control signal. make.
  • the MTC UE After receiving the trigger information, the MTC UE is further configured to send a trigger information transmission message to the MTC server through the service node and the MTC-IWF, and identify an application that needs to be triggered by using the application ID in the trigger information, and activate the application. Establish application layer communication with the MTC server.
  • An embodiment of the present invention further provides an MTC UE, including: a receiving unit, a sending unit, and a setting unit; wherein:
  • a receiving unit configured to receive trigger information sent by the MTC server through the MTC-IWF and the service node;
  • a sending unit configured to: after receiving the trigger information, return a trigger information transmission report to the MTC server by using the service node and the MTC-IWF;
  • a setting unit configured to set the trigger information transmission report content.
  • the MTC UE also includes an application unit for establishing application layer communication with the MTC server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种MTC UE触发信息的发送方法包括：MTC服务器向MTC-IWF发送MTC UE触发信息；所述MTC-IWF将所述触发信息封装为短信，并通过T5接口向所述MTC UE的服务节点发送；通过短信接收到所述MTC-IWF发送的触发信息的所述服务节点，通过控制信令或短信向所述MTC UE发送所述触发信息；本发明还公开了一种发送MTC UE触发信息的系统和MTC UE。通过本发明能够实现通过T5接口向MTC UE发送MTC UE触发信息。

Description

一种 MTC用户设备触发信息的发送方法、 系统和用户设备 技术领域
本发明涉及无线通信技术，特别是指一种 MTC用户设备触发信息的发 送方法、 系统和用户设备。 背景技术
机器对机器 ( M2M, Machine to Machine )技术指机器之间建立连接的 所有技术和手段。 M2M理念在上个世纪九十年代就出现了， 但是只停留在 理论阶段。 2000年以后， 随着移动通信技术的发展， 移动通信技术实现机 器设备的联网成为可能。 2002年左右 M2M业务就在市场上出现， 并在随 后的几年迅速发展， 成为众多通信设备商和电信运营商的关注焦点。 目前 全球的机器数量比人的数量要多很多，因此可以预见到 M2M技术良好的市 场前景。
对 M2M通信应用场景的研究表明在移动网络上提供 M2M通信具有潜 在的市场前景。但 M2M业务对系统提出了很多新的要求， 为了增强移动网 络在这方面的竟争力， 有必要对现有的移动网络进行优化， 以更有效的支 持 M2M通信。
现有的移动通信网络主要针对人与人的通信进行设计， 而对机器与机 器、人与机器的通信则优化不足。此外，运营商如何能够以低成本提供 M2M 通信服务， 也是 M2M通信部署成功的关键。
基于以上情况，有必要研究移动网络支持 M2M通信的解决方案。解决 方案要最大限度重用现有网络，降低大量 M2M通信对网络造成的影响以及 运营维护的复杂度。
目前电信市场竟争日趋激烈， 资费不断下降， 运营商利润空间不断减 小， 以人为基础的通信市场正在趋于饱和， M2M对运营商来说是全新的发 展机遇。
为了有效地利用移动网络资源， 第三代合作伙伴计划 （3GPP , 3rd Generation Partnership Project )提出了机器类型通信 ( MTC, Machine Type Communication ), 包括 M2M、 机器 ^人 ( Machine to Man )进行通讯的业 务， 其业务范围远远超出了以往人对人（H2H, Human to Human )之间的 通讯， MTC在接入控制、计费、安全性、服务质量（QoS, Quality of Service ), 业务模式等方面与现在的 H2H通讯模式有很大的区别。
3GPP演进分组系统（ EPS , Evolved Packet System )包括了无线接入网 (如 UMTS陆地无线接入网 （UTRAN, Universal Terrestrial Radio Access Network ), 演进的 UTRAN ( E-UTRAN, Evolved UTRAN )、 GSM/EDGE 无线接入网络 ( GERAN, GSM/EDGE Radio Access Network ) )和核心网。 在演进的分组核心网（ EPC, Evolved Packet Core )中有移动管理实体（ MME, Mobility Management Entity )、 月良务网关（ SG, Serving Gateway )、 分组数据 网 （PDN ) 网关 （PGW, PDN Gateway )等网元； 在 GPRS核心网中包括 服务 GPRS 支持节点 （SGSN, Serving GPRS Support Node )等网元； 在 E-UTRAN中包括演进的节点 B ( eNB, evolved Node B )0
MTC用户设备 (即具有 MTC功能的用户设备 )触发是对 MTC系统的 基本要求之一，该要求所关注的问题是：为了控制 MTC用户设^ MTC UE ) 的通信， 可以采用由 MTC服务器（Server )发起轮询（poll )的方式进行通 信， 对于 MTC UE发起的通信， 有时也需要 MTC服务器从 MTC UE轮询 数据。 如果 MTC服务器查询失败或者 MTC UE的 IP地址不可用， 则 MTC 服务器可以通过 MTC UE触发与 MTC UE建立通信。 如果网络不能触发 MTC UE, 则网络向 MTC服务器报告 MTC UE触发失败， MTC UE触发在 3GPP中通过控制面信令实现。 MTC UE触发包括移动主叫（ MO, Mobile Originated )和移动被叫（ MT, Mobile Terminating )业务， 即包括 MTC UE发送或者接收信息。
为了实现 MTC UE触发信息的有效传输， 已提出的方案包括： 通过短 it ( SMS, Short Message Service )发送 MTC UE触发信息， 或者通过控制 面信令发送 MTC UE触发信息， 或者通过用户面数据发送 MTC触发信息。 对于通过控制面信令发送 MTC UE触发信息的方式， MTC服务器发送包含 MTC UE 触发信息的控制面信令到 MTC 互联功能 （MTC-IWF, MTC InterWorking Function ), MTC-IWF选择通过 T5或 T4接口发送 MTC UE触 发信息到 MTC UE。 对于通过用户面数据发送 MTC UE触发信息的方式， MTC服务器发送 MTC UE触发信息到 MTC-IWF, MTC-IWF获取 MTC UE 的 IP地址 , 通过用户面向 MTC UE发送 MTC UE触发信息。
3GPP 中的 MTC 架构如图 1 所示， 在用户面， MTC UE 上的应用 ( Application )通过 API接口与 MTC服务器通信，或者通过 Gi/SGi接口直 接与 3GPP网络中的网关 GPRS支持节点 ( GGSN, Gateway GPRS Support Node ) /PGW通信； MTC服务器通过 Gi/SGi接口与 GGSN/PGW通信； GGSN/PGW通过无线接入网 （RAN, Radio Access Network )与 MTC UE 通信；在控制面， MTC服务器通过 Tsp接口向 MTC-IWF发送包含 MTC UE 触发信息的控制面信令， MTC-IWF将控制面信令发送到 MME和 /或 SGSN 和 /或 MSC ( MME/SGSN/MSC )或短信业务中心 （ SMSC, Short Message Service Center ), 进而通过 RAN发送到 MTC UE。
图 2为 MTC服务器通过 MTC-IWF在 T5接口上发送包含 MTC UE触 发信息的示意图， 其中， MTC服务器通过 Tsp接口直接发送包含 MTC UE 触发信息的控制面信令到 MTC-IWF, MTC-IWF通过 T5接口发送 MTC UE 触发信息到 MME/SGSN/MSC, 进一步发送到 MTC UE。
MTC UE收到 MTC UE触发信息后， 可以根据 MTC UE触发信息的指 示， 与 MTC服务器进行通信， 如建立用户面承载， 或者通过 SMS和 MTC 服务器通信。
在对现有技术的研究和实践过程中发现现有技术存在以下问题： MTC-IWF选择通过 T5接口发送 MTC UE触发信息时， 在 T5接口采用什 么方式封装 MTC UE触发信息， MME/SGSN/MSC收到 MTC UE触发信息 后， 采用什么方式向 MTC UE发送等问题还没有明确规定。 发明内容
有鉴于此， 本发明实施例的主要目的在于提供一种 MTC UE触发信息 的发送方法、 系统和用户设备，确定了通过 T5接口发送 MTC UE触发信息 的方式。
为达到上述目的， 本发明实施例的技术方案是这样实现的：
本发明实施例提供了一种 MTC UE触发信息的发送方法， 包括：
MTC服务器向 MTC-IWF发送 MTC UE触发信息；
所述 MTC-IWF将所述触发信息封装为短信， 并通过 T5接口向所述 MTC UE的服务节点发送；
通过短信接收到所述 MTC-IWF发送的触发信息的所述服务节点，通过 控制信令或短信向所述 MTC UE发送所述触发信息。
较佳的， 所述 MTC服务器发送的 MTC UE触发信息中至少包括： 所 述 MTC UE外部标识和应用 ID。
较佳的， 所述 MTC-IWF接收到所述触发信息后， 该方法还包括： 所述 MTC-IWF对所述 MTC服务器进行身份鉴定， 确定其为授权发送触发信息 的 MTC服务器； 同时，对所述 MTC服务器发送的触发信息进行负载控制。
较佳的， 所述 MTC-IWF将 MTC UE触发信息封装为短信， 包括： 将所述触发信息包含的内容转化成短信中的对应字段， 对短信中用于 指示短信内容的字段进行扩展， 使其用于指示短信内容为触发信息， 以及 将所述触发信息中的所述 MTC UE外部标识替换为 MTC UE内部标识； 所述 MTC UE内部标识为所述 MTC-IWF根据所述 MTC UE外部标识 从 HSS查询获得。
较佳的， MTC-IWF将短信通过 T5接口向所述 MTC UE的服务节点发 送， 包括：
MTC-IWF根据所述 MTC UE外部标识向 HSS查询 MTC UE的服务节 点的 T5地址，并根据查询获得的 T5地址向对应的服务节点发送所述短信。
较佳的， MTC-IWF将短信向所述 MTC UE的服务节点发送时，该方法 还包括：
所述短信中的触发信息中包含所述 MTC-IWF设置的单次发送字段时， 所述 MTC-IWF不存储所述短信；所述短信中的触发信息中不包含单次发送 字段、 但包含有效时间字段时， 所述 MTC-IWF存储所述短信。
较佳的， MTC-IWF将短信向所述 MTC UE的服务节点发送时，该方法 还包括：
所述 MTC-IWF通过采用并行或串行的方式向所述服务节点发送所述 短信。
较佳的，所述服务节点通过短信接收到所述 MTC-IWF发送的触发信息 后，该方法还包括： 所述服务节点对所述 MTC-IWF发送的触发信息进行负 载控制。
较佳的， 所述服务节点通过控制信令或短信向所述 MTC UE发送所述 触发信息， 为：
所述服务节点确定自身和所述 MTC UE都支持短信时， 通过短信发送 向所述 MTC UE发送所述触发消息； 否则， 通过控制信令向所述 MTC UE 发送所述触发消息。
较佳的 ,所述服务节点通过短信向所述 MTC UE发送所述触发消息时 , 该方法还包括：所述服务节点将来自所述 MTC-IWF的短信的目的地址修改 为所述 MTC UE内部标识后 , 转发给所述 MTC UE。
较佳的， 所述服务节点通过控制信令向所述 MTC UE发送所述触发消 息时， 该方法还包括：
所述服务节点从来自所述 MTC-IWF的短信中解析出所述触发信息，并 通过控制信令向所述 MTC UE发送；所述控制信令的目的地址为所述 MTC
UE内部标识；
较佳的， 所述控制信令为 NAS信令或专用控制信令。
较佳的， 所述服务节点包括： MME和 /或 SGSN和 /或 MSC。
较佳的， 所述 MTC UE接收到所述触发信息后， 该方法还包括： 所述 MTC UE通过所述服务节点和 MTC-IWF向所述 MTC服务器发送 触发信息传送报告； 并通过所述触发信息中的所述应用 ID, 识别出需要被 触发的应用， 并激活所述应用和所述 MTC server建立应用层通信。
本发明实施例还提出了一种发送 MTC UE触发信息的系统，包括： MTC 服务器、 MTC UE、 MTC-IWF和所述 MTC UE的服务节点， 其中：
所述 MTC服务器， 用于向所述 MTC-IWF发送 MTC UE触发信息； 所述 MTC-IWF, 用于将所述触发信息封装为短信， 并通过 T5接口向 所述服务节点发送；
所述服务节点， 用于通过短信接收到所述 MTC-IWF发送的触发信息 后， 通过控制信令或短信向所述 MTC UE发送所述触发信息；
所述 MTC UE, 用于接收所述触发信息。
较佳的， 所述 MTC-IWF, 还用于在接收到所述触发信息后， 对所述 MTC服务器进行身份鉴定， 确定其为授权发送触发信息的 MTC服务器； 同时， 对所述 MTC服务器发送的触发信息进行负载控制； 还用于在所述 MTC UE接收到触发信息后， 向所述 MTC服务器发送触发信息传送报告。 较佳的， 所述 MTC-IWF, 还用于将所述触发信息包含的内容转化成短 信中的对应字段， 对短信中用于指示短信内容的字段进行扩展， 使其用于 指示短信内容为触发信息， 以及将所述触发信息中的 MTC UE外部标识替 换为 MTC UE内部标识；
相应的， 所述 MTC-IWF , 还用于获取所述 MTC UE内部标识。
较佳的， 所述 MTC-IWF, 还用于所述 MTC UE外部标识向 HSS查询 所述服务节点的 T5地址， 并根据查询获得的 T5地址向对应的所述服务节 点发送所述短信。
较佳的，所述服务节点，还用于对所述 MTC-IWF发送的触发信息进行 负载控制； 还用于在所述 MTC UE接收到触发信息后， 向所述 MTC-IWF 发送触发信息传送报告。
较佳的， 所述服务节点， 还用于确定自身和所述 MTC UE都支持短信 时， 通过短信发送向所述 MTC UE发送所述触发消息； 否则， 通过控制信 令向所述 MTC UE发送所述触发消息；
所述控制信令为 NAS信令或专用控制信令。
较佳的， 所述 MTC UE在接收到所述触发信息后， 还用于通过所述服 务节点和所述 MTC-IWF向所述 MTC服务器发送触发信息传送报告； 并通 过所述触发信息中的应用 ID, 识别出需要被触发的应用， 并激活所述应用 和所述 MTC server建立应用层通信。
本发明实施例还提供了一种 MTC UE, 包括： 接收单元、 发送单元和 设置单元； 其中：
所述接收单元， 用于接收 MTC服务器通过 MTC-IWF和服务节点发送 的触发信息；
发送单元， 用于接收到触发信息后， 通过所述服务节点和 MTC-IWF 向所述 MTC服务器返回触发信息传送报告； 所述设置单元， 用于设置所述触发信息传送报告内容。
较佳的， 所述 MTC UE还包括应用单元， 用于和所述 MTC server建立 应用层通信。
本发明实施例在 T5 接口发送 MTC UE触发信息的方法和系统中： MTC-IWF收到 MTC server发送的触发信息， MTC-IWF将触发信息封装为 短信， 并通过 T5 接口向 MME/SGSN/MSC 发送； 收到触发信息的 MME/SGSN/MSC通过控制信令或短信向 MTC UE发送触发信息。 如此能 够实现 T5接口上触发信息的发送， 确定了 T5接口触发信息的信令流程。 附图说明
图 1为现有技术 3GPP中的 MTC架构示意图；
图 2为现有技术中 MTC-IWF通过 T5接口发送触发信息示意图； 图 3为本发明实施例通过 T5接口发送触发信息流程示意图；
图 4为本发明实施例中通过 T5接口发送触发信息示意图；
图 5为本发明实施例中服务节点通过短信发送触发信息示意图； 图 6为本发明实施例中服务节点通过控制信令发送触发信息示意图； 图 7为本发明实施例通过 T5接口发送触发信息的系统结构示意图。 具体实施方式
为了方便描述本发明实施例中，将 MTC UE触发信息简称为触发信息。 本发明实施例通过 T5接口发送 MTC UE触发信息的基本思想如图 3 所示， 包括：
步驟 101 , MTC Server向 MTC-IWF发送触发信息； 其中， 触发信息中 至少包括： 所述 MTC UE外部标识和应用 ID。
本发明实施例中所述的 MTC Server包括： MTC服务能力服务器和 MTC 应用服务器， 如图 1所示。 步驟 102, MTC-IWF将触发信息封装为短信，并通过 T5接口向 MTC UE 的服务节点发送。
MTC-IWF接收到触发信息后， 首先对发送触发信息的 MTC Server的 身份进行鉴定， 以确定 MTC Server为授权发送触发信息的 MTC Server。 同 时， MTC-IWF还对 MTC Server发送的触发信息进行负载控制， 以避免网 络拥塞或节点过载。
封装的具体实现为： 将触发信息包含的内容转化成短信中的对应字段， 对短信中用于指示短信内容的字段进行扩展， 使其用于指示短信内容为触 发信息，以及将触发信息中的 MTC UE外部标识替换为 MTC UE内部标识。 其中 , MTC UE内部标识为 MTC-IWF根据 MTC UE外部标识从 HSS查询 获得。
MTC-IWF将短信通过 T5接口向 MTC UE的服务节点发送， 包括： MTC-IWF根据 MTC UE外部标识向 HSS查询 MTC UE的服务节点的 T5 地址， 并根据查询获得的 T5地址向对应的服务节点发送短信。
在向 MTC UE 的服务节点发送时： 如果短信中的触发信息中包含 MTC-IWF设置的单次发送字段， 则 MTC-IWF不存储短信； 如果短信中的 触发信息中不包含单次发送字段、但包含有效时间字段， 则 MTC-IWF存储 短信。 其中， 单次发送字段表示 MTC-IWF只向服务节点发送一次短信； 有 效时间字段表示在该有效时间字段内， MTC-IWF可以重复向服务节点发送 短信。
另外， MTC-IWF还可以通过采用并行或串行的方式向服务节点发送短 信。
步驟 103 , 通过短信接收到 MTC-IWF发送的触发信息的服务节点， 通 过控制信令或短信向 MTC UE发送所述触发信息。
服务节点需要对 MTC-IWF发送的触发信息进行负载控制，以避免或减 轻网络拥塞或节点过载。
服务节点确定自身和 MTC UE都支持短信时，通过短信发送向 MTC UE 发送触发消息； 否则， 通过控制信令向 MTC UE发送触发消息。
当通过短信发送触发消息时，服务节点将来自 MTC-IWF的短信的目的 地址修改为 MTC UE内部标识后 , 转发给 MTC UE。
当通过控制信令发送触发消息时，服务节点从来自 MTC-IWF的短信中 解析出触发信息， 并通过控制信令向 MTC UE发送； 控制信令的目的地址 为 MTC UE内部标识。 其中， 控制信令为 NAS信令或专用控制信令。
当 MTC UE接收到触发信息后， MTC UE通过触发信息中的应用 ID, 识别出需要被触发的应用 ,并激活所述应用和 MTC server建立应用层通信。
上述的服务节点包括： MME和 /或 SGSN和 /或 MSC。
下面通过具体的实施例对上述方案进行详细的描述， 如图 4所示： 步驟 201 , MTC Server向 MTC-IWF发送触发信息。
当 MTC Server需要触发某个 MTC UE, 与之建立应用层通信时， 生成 一个触发信息， 该触发信息中至少包括该 MTC UE外部标识（ ext-ID )和应 用 ID, 该应用 ID用于供 MTC UE识别需要被触发的应用； MTC Server根 据 MTC UE外部标识向 DNS查询 MTC-IWF的 IP地址。
MTC server通过 Tsp接口向 MTC-IWF发送触发信息。
步驟 202, MTC-IWF接收到触发信息后， 对 MTC Server进行认证、授 权，如果 MTC server是合法的，则 MTC-IWF接受触发信息，否则 MTC-IWF 丟弃触发信息。
步驟 203, MTC-IWF查询 MTC UE的服务节点的 T5地址。
MTC-IWF根据 MTC UE外部标识向 HSS查询 MTC UE的服务节点的 T5地址。 其中， 服务节点包括： MME和 /或 SGSN和 /或 MSC。 MTC-IWF 可以查询 MME、 SGSN和 MSC中一个或多个的 T5地址。 步驟 204, MTC-IWF通过 T5接口发送触发信息， 并将触发信息封装 成短信。
MTC-IWF按照协议规定的短信的格式要求，将触发信息包含的内容转 化成短信中的对应字段； 另外， 现有短信结构中有一个用于指示短信内容 的字段，对该字段进行扩展，使其用于指示短信内容为触发信息。 MTC-IWF 在封装触发消息时， 还需要将其中的 MTC UE外部标识替换为内部标识。
MTC UE内部标识为 MTC-IWF根据 MTC UE外部标识从 HSS查询获 付。
本发明实施例方法的实现前提为 MTC-IWF通过 T5接口发送触发信 息， 在实际应用中， MTC-IWF还需要根据本地策略和从 HSS查询到的信 息决策是否通过 T5接口发送触发信息， 如果决策不通过 T5接口发送触发 信息， 那么流程结束。
其中， 本地策略， 例如： 本地网络部署、 MTC UE的服务节点类型、 本地运营商优选方案等； 从 HSS查询到的信息， 例如： MTC UE的服务节 点的 T5地址、 MTC UE内部标识（较佳为 MTC UE的 IMSI )、以及 MTC UE 的签约信息等。
步驟 205, MTC-IWF根据查询到的 T5地址向对应的服务器节点（ MME 和 /或 SGSN和 /或 MSC )发送短信。
其中， MTC-IWF通过 T5a接口向 SGSN发送该短信； 和 /或通过 T5b 接口向 MME发送该短信； 和 /或通过 T5c接口向 MSC发送该短信。
如果触发信息中指明了通过 T5接口发送触发信息的方式为单次发送， 则 MTC-IWF不需要存储触发信息； 否则， MTC-IWF存储触发信息， 具体 的， 存储的触发信息为封装后的短信， 并重复发送短信。
其中， MTC-IWF可以在触发信息中设置一个单次发送的字段， 以指示 通过 T5接口发送触发信息的方式为单次发送； 否则， 可在触发信息中设置 一个有效时间段的字段，在该有效时间段内， 只要 MTC-IWF没有接收到触 发信息发送成功的响应， 那么 MTC-IWF重复发送该短信； 直到 MTC-IWF 接收到触发信息发送成功的响应的后， 停止发送， 并删除短信。
MTC-IWF向 MME和 /或 SGSN和 /或 MSC发送短信的方式可以是并行 发送或串行发送， 具体的由 MTC-IWF根据本地策略和从 HSS查询到的信 息等综合衡量后决定。
其中， 本地策略， 例如： 本地网络部署、 MTC UE的服务节点类型、 本地运营商优选方案等；
从 HSS查询到的信息，例如： MTC UE的服务节点的 T5地址、 MTC UE 内部标识（较佳为 MTC UE的 IMSI )、 以及 MTC UE的签约信息等。
步驟 206,服务节点通过确定通过短信发送触发消息时，执行步驟 207; 确定通过控制信令发送触发消息时， 执行步驟 208。
服务节点根据本地策略和 MTC UE的签约信息， 确定自身和 MTC UE 都支持短信时， 确定通过短信发送触发消息； 否则， 确定通过控制信令发 送触发消息。
其中，服务节点向 MTC-IWF请求获取 MTC UE的签约信息， MTC-IWF 向 HSS查询 MTC UE的签约信息并返回。
步驟 207, 服务节点通过短信发送触发消息， 如图 5所示， 具体包括： 步驟 2071 ,服务节点将 MTC-IWF发送的短信中的目的地址由 T5地址 修改为 MTC UE内部标识 , 然后转发给 MTC UE。
步驟 2072, MTC UE向服务节点返回触发信息传送报告。
MTC UE收到短信后， 从中解析出触发信息， 并向服务节点返回触发 信息传送报告， 表明 MTC UE收到触发信息、 即触发信息发送成功。
其中 , 触发信息传送 4艮告可以采用短信或控制信令^ ^载。
另外， 如果触发信息发送失败， 且触发信息中不包含单次发送的字段， 则服务节点设置消息等待标识，等待 MTC-IWF重新发送短信并转发给 MTC UE, 直到接收到 MTC UE返回的触发信息传送报告。 其中， 造成触发信息 发送失败的原因， 可能是： 服务节点收到 MTC UE发送的失败响应， 或者， 上述有效时间字段规定的有效时间超时， 或者服务节点发现 MTC UE不可 达等。
步驟 2073 , 服务节点向 MTC-IWF发送触发信息传送报告。
服务节点将来自 MTC UE的触发信息传送报告转发给 MTC-IWF,表明
MTC UE收到触发信息、 即触发信息发送成功。
步驟 2074, MTC-IWF向 MTC server发送触发信息传送 4艮告。
MTC-IWF将来自服务节点的触发信息传送报告转发给 MTC server,表 明触发信息发送成功， 然后转入步驟 209。
步驟 208, 服务节点通过控制信令发送触发消息， 如图 6所示， 具体包 括：
步驟 2081 , 服务节点从短信中解析出触发信息， 并通过控制信令向 MTC UE发送。 其中， 控制信令可以是 NAS信令或专用控制信令等； 控制 信令的目的地址为 MTC UE内部标识。
步驟 2082, MTC UE向服务节点返回响应消息。
MTC UE收到控制信令后， 从中解析出触发信息， 并向服务节点返回 响应消息， 表明 MTC UE收到触发信息、 即触发信息发送成功。
由于步驟 206中指出： 服务节点确定自身和 MTC UE都支持短信时， 确定通过短信发送触发消息； 否则， 确定通过控制信令发送触发消息。 因 此， 这里 MTC UE需要通过控制信令向服务节点返回响应消息。
另外， 如果触发信息发送失败， 且触发信息中不包含单次发送的字段， 则服务节点设置消息等待标识，等待 MTC-IWF重新发送短信并转发给 MTC UE, 直到接收到 MTC UE返回的响应消息。 步驟 2083 , 服务节点向 MTC-IWF发送触发信息传送报告。 服务节点收到 MTC UE 的响应信息后， 生成触发信息传送报告， 向
MTC-IWF发送， 表明触发信息发送成功。 触发信息传送报告可以采用短信 或控制信令承载。
步驟 2084, MTC-IWF向 MTC server发送触发信息传送报告。
MTC-IWF将来自服务节点的触发信息传送报告转发给 MTC server,表 明触发信息发送成功， 然后转入步驟 209。
步驟 209, MTC UE与 MTC Server建立应用层通信， 流程结束。
应用层通信是指 MTC UE通过触发信息中包含的应用 ID, 识别出需要 被触发的应用， 并激活应用和 MTC server建立通信。
为了实现上述方法， 本发明实施例还提出了一种系统， 如图 7所示， 包括： MTC服务器、 MTC UE、 MTC-IWF和 MTC UE的服务节点， 其中： MTC服务器， 用于向 MTC-IWF发送 MTC UE触发信息；
MTC-IWF, 用于将触发信息封装为短信， 并通过 T5接口向服务节点 发送；
服务节点， 用于通过短信接收到所述 MTC-IWF发送的触发信息后，通 过控制信令或短信向 MTC UE发送触发信息；
MTC UE, 用于接收触发信息。
其中， MTC-IWF, 还用于在接收到所述触发信息后， 对 MTC服务器 进行身份鉴定，确定其为授权发送触发信息的 MTC服务器； 同时，对 MTC 服务器发送的触发信息进行负载控制； 还用于在 MTC UE接收到触发信息 后， 向 MTC服务器发送触发信息传送报告。
MTC-IWF, 还用于将触发信息包含的内容转化成短信中的对应字段， 对短信中用于指示短信内容的字段进行扩展， 使其用于指示短信内容为触 发信息，以及将触发信息中的 MTC UE外部标识替换为 MTC UE内部标识； 相应的 , MTC-IWF, 还用于获取 MTC UE内部标识。
MTC-IWF,还用于 MTC UE外部标识向 HSS查询服务节点的 T5地址， 并根据查询获得的 T5地址向对应的服务节点发送短信。
服务节点，还用于对 MTC-IWF发送的触发信息进行负载控制；还用于 在 MTC UE接收到触发信息后， 向 MTC-IWF发送触发信息传送报告。
服务节点， 还用于确定自身和 MTC UE都支持短信时， 通过短信发送 向 MTC UE发送触发消息；否则，通过控制信令向 MTC UE发送触发消息； 控制信令为 NAS信令或专用控制信令。
MTC UE在接收到触发信息后， 还用于通过服务节点和 MTC-IWF向 MTC Server发送触发信息传送 ^艮告， 并通过触发信息中的应用 ID, 识别出 需要被触发的应用， 并激活应用和 MTC server建立应用层通信。
本发明实施例还提出了一种 MTC UE, 包括： 接收单元、 发送单元和 设置单元； 其中：
接收单元， 用于接收 MTC服务器通过 MTC-IWF和服务节点发送的触 发信息；
发送单元，用于接收到触发信息后，通过服务节点和 MTC-IWF向 MTC 服务器返回触发信息传送报告；
设置单元， 用于设置所述触发信息传送报告内容。
MTC UE还包括应用单元， 用于和 MTC server建立应用层通信。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种 MTC UE触发信息的发送方法， 其特征在于， 包括：
MTC服务器向 MTC-IWF发送 MTC UE触发信息；
所述 MTC-IWF将所述触发信息封装为短信， 并通过 T5接口向所述 MTC UE的服务节点发送；
通过短信接收到所述 MTC-IWF发送的触发信息的所述服务节点，通 过控制信令或短信向所述 MTC UE发送所述触发信息。
2、根据权利要求 1所述 MTC UE触发信息的发送方法，其特征在于， 所述 MTC服务器发送的 MTC UE触发信息中至少包括： 所述 MTC UE 外部标识和应用 ID。
3、根据权利要求 2所述 MTC UE触发信息的发送方法，其特征在于， 所述 MTC-IWF接收到所述触发信息后， 该方法还包括： 所述 MTC-IWF 对所述 MTC服务器进行身份鉴定， 确定其为授权发送触发信息的 MTC 服务器； 同时， 对所述 MTC服务器发送的触发信息进行负载控制。
4、根据权利要求 3所述 MTC UE触发信息的发送方法，其特征在于， 所述 MTC-IWF将 MTC UE触发信息封装为短信， 包括：
将所述触发信息包含的内容转化成短信中的对应字段， 对短信中用 于指示短信内容的字段进行扩展， 使其用于指示短信内容为触发信息， 以及将所述触发信息中的所述 MTC UE外部标识替换为 MTC UE内部标 识；
所述 MTC UE内部标识为所述 MTC-IWF根据所述 MTC UE外部标 识从 HSS查询获得。
5、根据权利要求 4所述 MTC UE触发信息的发送方法，其特征在于， MTC-IWF将短信通过 T5接口向所述 MTC UE的服务节点发送， 包括：
MTC-IWF根据所述 MTC UE外部标识向 HSS查询 MTC UE的服务 节点的 T5地址， 并根据查询获得的 Τ5地址向对应的服务节点发送所述 短信。
6、根据权利要求 5所述 MTC UE触发信息的发送方法，其特征在于， MTC-IWF将短信向所述 MTC UE的服务节点发送时 , 该方法还包括： 所述短信中的触发信息中包含所述 MTC-IWF设置的单次发送字段 时， 所述 MTC-IWF不存储所述短信； 所述短信中的触发信息中不包含单 次发送字段、 但包含有效时间字段时， 所述 MTC-IWF存储所述短信。
7、根据权利要求 5所述 MTC UE触发信息的发送方法，其特征在于， MTC-IWF将短信向所述 MTC UE的服务节点发送时 , 该方法还包括： 所述 MTC-IWF通过采用并行或串行的方式向所述服务节点发送所 述短信。
8、 根据权利要求 6或 7所述 MTC UE触发信息的发送方法， 其特征 在于， 所述服务节点通过短信接收到所述 MTC-IWF发送的触发信息后， 该方法还包括：所述服务节点对所述 MTC-IWF发送的触发信息进行负载 控制。
9、根据权利要求 8所述 MTC UE触发信息的发送方法，其特征在于， 所述服务节点通过控制信令或短信向所述 MTC UE发送所述触发信息， 为：
所述服务节点确定自身和所述 MTC UE都支持短信时， 通过短信发 送向所述 MTC UE发送所述触发消息； 否则， 通过控制信令向所述 MTC UE发送所述触发消息。
10、 根据权利要求 9所述 MTC UE触发信息的发送方法， 其特征在 于， 所述服务节点通过短信向所述 MTC UE发送所述触发消息时， 该方 法还包括：所述服务节点将来自所述 MTC-IWF的短信的目的地址修改为 所述 MTC UE内部标识后， 转发给所述 MTC UE。
11、 根据权利要求 9所述 MTC UE触发信息的发送方法， 其特征在 于， 所述服务节点通过控制信令向所述 MTC UE发送所述触发消息时， 该方法还包括：
所述服务节点从来自所述 MTC-IWF的短信中解析出所述触发信息， 并通过控制信令向所述 MTC UE发送； 所述控制信令的目的地址为所述 MTC UE内部标识；
所述控制信令为 NAS信令或专用控制信令。
12、 根据权利要求 10或 11所述 MTC UE触发信息的发送方法， 其 特征在于， 所述服务节点包括： MME和 /或 SGSN和 /或 MSC。
13、根据权利要求 12所述 MTC UE触发信息的发送方法， 其特征在 于， 所述 MTC UE接收到所述触发信息后， 该方法还包括：
所述 MTC UE通过所述服务节点和 MTC-IWF向所述 MTC服务器发 送触发信息传送报告； 并通过所述触发信息中的所述应用 ID, 识别出需 要被触发的应用， 并激活所述应用和所述 MTC服务器建立应用层通信。
14、 一种发送 MTC UE触发信息的系统， 其特征在于， 包括： MTC 服务器、 MTC UE、 MTC-IWF和所述 MTC UE的服务节点， 其中：
所述 MTC服务器， 用于向所述 MTC-IWF发送 MTC UE触发信息； 所述 MTC-IWF, 用于将所述触发信息封装为短信， 并通过 T5接口 向所述服务节点发送；
所述服务节点，用于通过短信接收到所述 MTC-IWF发送的触发信息 后， 通过控制信令或短信向所述 MTC UE发送所述触发信息；
所述 MTC UE, 用于接收所述触发信息。
15、 根据权利要求 14所述发送 MTC UE触发信息的系统， 其特征在 于，
所述 MTC-IWF, 还用于在接收到所述触发信息后， 对所述 MTC服 务器进行身份鉴定， 确定其为授权发送触发信息的 MTC服务器； 同时， 对所述 MTC服务器发送的触发信息进行负载控制； 还用于在所述 MTC UE接收到触发信息后， 向所述 MTC服务器发送触发信息传送报告。
16、根据权利要求 15所述发送 MTC UE触发信息的系统， 其特征在 于，
所述 MTC-IWF, 还用于将所述触发信息包含的内容转化成短信中的 对应字段， 对短信中用于指示短信内容的字段进行扩展， 使其用于指示 短信内容为触发信息， 以及将所述触发信息中的 MTC UE外部标识替换 为 MTC UE内部标识；
相应的， 所述 MTC-IWF , 还用于获取所述 MTC UE内部标识。
17、 根据权利要求 16所述发送 MTC UE触发信息的系统， 其特征在 于，
所述 MTC-IWF, 还用于所述 MTC UE外部标识向 HSS查询所述服 务节点的 T5地址， 并根据查询获得的 T5地址向对应的所述服务节点发 送所述短信。
18、 根据权利要求 17所述发送 MTC UE触发信息的系统， 其特征在 于，
所述服务节点，还用于对所述 MTC-IWF发送的触发信息进行负载控 制； 还用于在所述 MTC UE接收到触发信息后， 向所述 MTC-IWF发送 触发信息传送报告。
19、 根据权利要求 18所述发送 MTC UE触发信息的系统， 其特征在 于，
所述服务节点， 还用于确定自身和所述 MTC UE都支持短信时， 通 过短信发送向所述 MTC UE发送所述触发消息； 否则， 通过控制信令向 所述 MTC UE发送所述触发消息； 所述控制信令为 NAS信令或专用控制信令。
20、 根据权利要求 19所述发送 MTC UE触发信息的系统， 其特征在 于，
所述 MTC UE在接收到所述触发信息后， 还用于通过所述服务节点 和所述 MTC-IWF向所述 MTC服务器发送触发信息传送报告； 并通过所 述触发信息中的应用 ID, 识别出需要被触发的应用， 并激活所述应用和 所述 MTC服务器建立应用层通信。
21、 一种 MTC UE, 其特征在于， 包括： 接收单元、 发送单元和设 置单元； 其中：
所述接收单元， 用于接收 MTC服务器通过 MTC-IWF和服务节点发 送的触发信息；
发送单元， 用于接收到触发信息后， 通过所述服务节点和 MTC-IWF 向所述 MTC服务器返回触发信息传送报告；
所述设置单元， 用于设置所述触发信息传送报告内容。
22、 根据权利要求 21所述 MTC UE, 其特征在于， 所述 MTC UE还 包括应用单元， 用于和所述 MTC服务器建立应用层通信。
PCT/CN2012/073344 2012-02-03 2012-03-30 一种mtc用户设备触发信息的发送方法、系统和用户设备 WO2013113186A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/350,158 US9467508B2 (en) 2012-02-03 2012-03-30 Method and system for sending trigger message to MTC UE, and MTC UE
EP12867127.8A EP2753106B1 (en) 2012-02-03 2012-03-30 Method and system for sending a trigger message to a mtc ue, and mtc ue

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210024564.X 2012-02-03
CN201210024564.XA CN103249013B (zh) 2012-02-03 2012-02-03 一种mtc用户设备触发信息的发送方法、系统和用户设备

Publications (1)

Publication Number Publication Date
WO2013113186A1 true WO2013113186A1 (zh) 2013-08-08

Family

ID=48904389

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/073344 WO2013113186A1 (zh) 2012-02-03 2012-03-30 一种mtc用户设备触发信息的发送方法、系统和用户设备

Country Status (4)

Country Link
US (1) US9467508B2 (zh)
EP (1) EP2753106B1 (zh)
CN (1) CN103249013B (zh)
WO (1) WO2013113186A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015021608A1 (zh) * 2013-08-14 2015-02-19 华为技术有限公司 发送触发消息的方法及设备

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3211933A1 (en) 2011-10-28 2017-08-30 NEC Corporation Secure method for mtc device triggering
TWI619368B (zh) * 2012-05-11 2018-03-21 內數位專利控股公司 與短訊息相關聯的路由的方法及sms服務中心(sms-sc)
CN103684824B (zh) * 2012-09-13 2017-09-12 华为终端有限公司 一种事件上报的方法及系统
US9713071B2 (en) * 2012-09-28 2017-07-18 Nokia Solutions And Networks Oy Provisioning external identifiers
CN103813276A (zh) * 2012-11-06 2014-05-21 中兴通讯股份有限公司 信息的发送方法、mtc服务器、用户设备及mtc系统
IN2015DN04224A (zh) * 2012-12-06 2015-10-16 Nec Corp
CN103906023B (zh) * 2012-12-28 2019-06-18 中兴通讯股份有限公司 机器类型设备mtc设备的触发信息的处理方法及装置
WO2015026109A1 (ko) * 2013-08-18 2015-02-26 엘지전자 주식회사 무선 통신 시스템에서 디바이스 트리거 취소 방법 및 장치
US9986367B2 (en) * 2013-11-22 2018-05-29 Nec Corporation Communication system, relay apparatus, communication method, and non-transitory computer readable medium storing program
JP6406814B2 (ja) * 2013-11-29 2018-10-17 株式会社Ｎｔｔドコモ 通信システム、サービス制御装置、ｍｔｃユーザ装置、ゲートウェイ装置及び通信方法
US20150195717A1 (en) * 2014-01-06 2015-07-09 Puneet K. Jain Techniques for communication between interworking function and short message service nodes for device trigger replacement/recall
CN104104713B (zh) * 2014-02-24 2018-03-23 中兴通讯股份有限公司 设备触发消息处理方法、承载网网元、m2m节点及系统
CN105393567B (zh) * 2014-06-26 2020-07-21 华为技术有限公司 数据的安全传输方法和设备
WO2017022644A1 (ja) 2015-08-05 2017-02-09 日本電気株式会社 通信システム、通信制御装置、通信制御方法、及びプログラム
US10506403B2 (en) 2017-02-27 2019-12-10 Oracle International Corporation Methods, systems and computer readable media for providing integrated service capability exposure function (SCEF), service capability server (SCS) and application server (AS) services
US10405158B2 (en) 2017-02-27 2019-09-03 Oracle International Corporation Methods, systems and computer readable media for providing service capability exposure function (SCEF) as a diameter routing agent (DRA) feature
US10530599B2 (en) 2017-02-27 2020-01-07 Oracle International Corporation Methods, systems and computer readable media for providing service capability exposure function (SCEF) as a cloud service
US10448449B2 (en) 2017-07-13 2019-10-15 Oracle International Corporation Methods, systems, and computer readable media for dynamically provisioning session timeout information in a communications network
US10334419B2 (en) 2017-08-16 2019-06-25 Oracle International Corporation Methods, systems, and computer readable media for optimizing machine type communication (MTC) device signaling
US10313883B2 (en) 2017-11-06 2019-06-04 Oracle International Corporation Methods, systems, and computer readable media for using authentication validation time periods
US11146577B2 (en) 2018-05-25 2021-10-12 Oracle International Corporation Methods, systems, and computer readable media for detecting and mitigating effects of abnormal behavior of a machine type communication (MTC) device
US10616802B2 (en) 2018-09-04 2020-04-07 Oracle International Corporation Methods, systems and computer readable media for overload and flow control at a service capability exposure function (SCEF)
US11381955B2 (en) 2020-07-17 2022-07-05 Oracle International Corporation Methods, systems, and computer readable media for monitoring machine type communications (MTC) device related information
US11700510B2 (en) 2021-02-12 2023-07-11 Oracle International Corporation Methods, systems, and computer readable media for short message delivery status report validation

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118700A (zh) * 2009-12-31 2011-07-06 中兴通讯股份有限公司 机器类通信消息传输方法及系统
CN102238477A (zh) * 2010-04-30 2011-11-09 华为终端有限公司 触发一组mtc设备与mtc服务器通信的方法及mtc设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7774008B2 (en) 2006-12-22 2010-08-10 Cellco Partnership MDN-less SMS messaging (network solution) for wireless M2M application
CN103392372B (zh) * 2011-02-23 2018-02-06 瑞典爱立信有限公司 无线电网络节点和用户设备之间的接入限制信息的传送
EP2732565A4 (en) * 2011-07-14 2015-03-25 Intel Corp COMMUNICATIONS BETWEEN MACHINERY (M2M) USING SMS SERVICES
CN104106285A (zh) * 2011-09-29 2014-10-15 诺基亚通信公司 装置触发解决方案

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118700A (zh) * 2009-12-31 2011-07-06 中兴通讯股份有限公司 机器类通信消息传输方法及系统
CN102238477A (zh) * 2010-04-30 2011-11-09 华为终端有限公司 触发一组mtc设备与mtc服务器通信的方法及mtc设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Services and System Aspects; Architecture Enhancements to facilitate communications with Packet Data Networks and Applications (Release 11)", 3GPP TS 23.682 V0.1.0, November 2011 (2011-11-01), XP050575130 *
ERICSSON ET AL.: "Device Trigger security", 3GPP TSG SA WG3 (SECURITY) MEETING #66 S3-120178, 30 January 2012 (2012-01-30), pages 3 - 120178, XP050577518, Retrieved from the Internet <URL:http://isearch.3gpp.org/isysquery/f55b7eba-2ace-4c41-9b2a-636acf0e607e/11-20/list> *
See also references of EP2753106A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015021608A1 (zh) * 2013-08-14 2015-02-19 华为技术有限公司 发送触发消息的方法及设备

Also Published As

Publication number Publication date
US9467508B2 (en) 2016-10-11
EP2753106B1 (en) 2018-08-08
CN103249013A (zh) 2013-08-14
EP2753106A4 (en) 2015-04-15
CN103249013B (zh) 2018-08-03
EP2753106A1 (en) 2014-07-09
US20140317195A1 (en) 2014-10-23

Similar Documents

Publication Publication Date Title
WO2013113186A1 (zh) 一种mtc用户设备触发信息的发送方法、系统和用户设备
US10652085B2 (en) Method for setting configuration of non-IP data delivery (NDID) in wireless communication system and device for same
KR102048046B1 (ko) 무선 통신 시스템에서 ladn 이용 방법 및 이를 위한 장치
JP6138058B2 (ja) サーバ及び通信端末
EP2768251B1 (en) Data transmission method, mobility management entity and mobile terminal
US9225399B2 (en) Method to enable optimization for small data in an evolved packet core (EPC)
US9215550B2 (en) Method and system for sending MTC device trigger information, and target user equipment
WO2013040962A1 (zh) 数据发送和接收方法及设备
JP2015519790A (ja) マシンツーマシンデバイストリガリングのためのシステム、方法、および装置
WO2013056486A1 (zh) 一种消息类型的指示方法、系统及装置
WO2012151963A1 (zh) 一种触发信息中有效时间的处理方法和系统
US9204273B2 (en) Method and system for trigger information transmission and protocol conversion
US20150215725A1 (en) Method, system, and equipment for sending trigger message
WO2018137152A1 (zh) 短消息传输方法、设备和系统
WO2014180114A1 (zh) 实现mtc监控的方法及装置
JP6191768B2 (ja) 移動無線通信装置からのデータ転送
WO2014048173A1 (zh) 一种小数据发送方法、系统及用户设备
WO2012155808A1 (zh) 设备触发方法及网元设备
CN103096264B (zh) 设置触发信息有效时间方法、系统和用户设备
US9854382B2 (en) Method and unit for processing triggering information of MTC devices
WO2014071758A1 (zh) 信息的发送方法、mtc服务器、用户设备及mtc系统
WO2011032522A1 (zh) 一种实现本地接入的系统及方法
WO2013102316A1 (zh) 响应触发信息的方法、系统和mtc用户设备
WO2011082524A1 (zh) 机器到机器的数据传输方法、系统及移动性管理网元装置
KR20130107381A (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: 12867127

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012867127

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 14350158

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE