WO2012155808A1 - 设备触发方法及网元设备 - Google Patents

设备触发方法及网元设备 Download PDF

Info

Publication number
WO2012155808A1
WO2012155808A1 PCT/CN2012/075334 CN2012075334W WO2012155808A1 WO 2012155808 A1 WO2012155808 A1 WO 2012155808A1 CN 2012075334 W CN2012075334 W CN 2012075334W WO 2012155808 A1 WO2012155808 A1 WO 2012155808A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
network element
application trigger
trigger request
application
Prior art date
Application number
PCT/CN2012/075334
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 EP12786602.8A priority Critical patent/EP2699041B1/en
Publication of WO2012155808A1 publication Critical patent/WO2012155808A1/zh
Priority to US14/077,415 priority patent/US20140071945A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a device triggering method and a network element device. Background technique
  • H2H human to human
  • M2M machine to machine
  • the H2H application mainly refers to the communication of the human communication main body, such as telephone communication
  • the M2M application also refers to the machine type communication (MTC) application, which refers to the network communication between multiple network elements without any participation.
  • MTC machine type communication
  • M2M technology combines communication and network technologies to connect machines and equipment that are used in people's daily lives into a network, making these devices more "smart," and thus creating rich applications for everyday life, industrial production, etc.
  • the industry has proposed the characteristics of M2M device triggering. That is, the M2M application server needs M2M devices to perform with it. When communicating, the M2M device needs to be triggered first, and then the M2M device performs data interaction with the M2M application server through the network.
  • the device actively sends non-access stratum (NAS, Non-Access Stratum) signaling such as an attach request or a tracking area update request, and the core network receives the NAS message sent by the device.
  • NAS non-access stratum
  • the device application trigger request is sent to the device in response to the NAS signaling to complete the trigger of the device.
  • the device triggering method and the network element device are provided to improve the initiative and real-time performance of triggering on the M2M device or the H2H device.
  • the embodiment of the present invention provides the following technical solution:
  • a device triggering method includes:
  • the mobility management network element receives the device application trigger request; Sending, by the access network element, a request for carrying the device application trigger request, so that the access network element triggers the device;
  • a device triggering method includes:
  • the gateway network element receives a request from the mobility management network element for the mobile device application to trigger the request; and sends a data packet carrying the device application trigger request to the device to trigger the device.
  • a mobility management network element including:
  • a receiving module configured to receive a device application trigger request
  • a first sending module configured to send, to the access network element, a request for carrying the device application trigger request, so that the access network element triggers the device;
  • a second sending module configured to send, to the gateway network element, a request for carrying the device application trigger request, so that the gateway network element triggers the device.
  • a gateway network element including:
  • a second receiving module configured to receive a request for a device application trigger request from the mobility management network element
  • a fourth sending module configured to send, to the device, a data packet carrying the device application trigger request to trigger the device.
  • the mobility management network element of the embodiment of the present invention sends the device application trigger request to the access network element or the gateway network element by using the initiative originating request, so that The access network element or the gateway network element can send the device application trigger request to the corresponding device to trigger the device, and the mechanism relatively improves the initiative and real-time performance of the network-issued device application trigger request, thereby facilitating more timely Effectively trigger M2M device or H2H device and application server to exchange data.
  • FIG. 1 is a schematic flowchart of a device triggering method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of another device triggering method according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of still another device triggering method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of still another device triggering method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of still another device triggering method according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of another device triggering method according to an embodiment of the present invention
  • FIG. 7-b is a schematic structural diagram of another mobility management network element according to an embodiment of the present invention
  • FIG. 7-c is another mobile structure provided by an embodiment of the present invention
  • FIG. 8 is a schematic structural diagram of a gateway network element according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a communication system according to an embodiment of the present invention. detailed description
  • the device triggering method and the network element device are provided to improve the initiative and real-time performance of triggering on the M2M device or the H2H device.
  • the access network element in the embodiment of the present invention refers to an entity that can implement the radio access management function of the user equipment.
  • the mobility management network element in the embodiment of the present invention refers to the mobility management logic of the user equipment. Functional entities, while access network elements and mobility management network elements may have different names, locations, and product forms in different networks.
  • an access network element mentioned in the following embodiments of the present invention may be, for example, an evolved universal mobile.
  • UMTS Universal Mobile Telecommunications System
  • eNodeB evolved base station
  • HeNB home base station
  • E-UTRAN Evolved UMTS Territorial Radio Access Network
  • UMTS terrestrial radio a base station controller in a UTRAN (UMTS, GSM EDGE Radio Access Network) or a radio network controller (RNC) in the GSM EDGE Radio Access Network
  • RNC radio network controller
  • the mobility management network element mentioned in the embodiment of the present invention may refer to a mobility management entity MME connected to the E-UTRAN, and a general packet radio service serving node (SGSN, Serving GPRS (General Packet) connected to the UTRAN/GERAN. Radio Service ) Support Node ); or access gateway (AGW, Access Gateway) in non-3GPP networks, entity ePDG with mobility management logic function in WLAN, access service network gateway in global access WiMAX network for microwave access ( ASN GW, Access Service Network Gateway), or an entity in the CDMA network that has a high rate packet data access network HRPD-AN mobility management logic function, or an entity that implements user equipment mobility management logic functions in other networks.
  • SGSN Serving GPRS (General Packet) connected to the UTRAN/GERAN. Radio Service ) Support Node
  • AGW Access Gateway
  • entity ePDG with mobility management logic function in WLAN
  • access service network gateway in global access WiMAX network for microwave access ASN GW, Access Service Network Gateway
  • the home location server (HLR, Home Location Register) or (HSS, Home Subscriber Server) mentioned in the embodiment of the present invention.
  • the device in the embodiment of the present invention refers to an H2H device or an M2M device.
  • the solution in the embodiment of the present invention is used to trigger an H2H device or an M2M device.
  • An embodiment of the device triggering method of the present invention may include: the mobility management network element receives a device application trigger request from a home location server; and sends the device (such as an H2H device or an M2M device) Carrying the device application trigger request request (such as a control plane request) to trigger the device; or sending a request (such as a control plane request) carrying the device application trigger request to the access network element to enable the access network element to trigger The device sends a request (such as a control plane request) message carrying the device application trigger request to the gateway network element to enable the gateway network element to trigger the device.
  • the device such as an H2H device or an M2M device
  • Carrying the device application trigger request request request such as a control plane request
  • a request such as a control plane request
  • the device sends a request (such as a control plane request) message carrying the device application trigger request to the gateway network element to enable the gateway network element to trigger the device.
  • the specific steps may include:
  • the mobility management network element receives a device application trigger request.
  • the application server (Application Server) needs to trigger an M2M device or an H2H device to communicate with it (for example, the Application Server requires an M2M device to report certain types of data to it)
  • the Application Server can send the message to the home location server.
  • the device application trigger request (UE application trigger request) carries the device identifier of the M2M device or the H2H device to be triggered.
  • the Application Server may also send a high priority processing indication to the home location server while sending the UE application trigger request (the high priority processing indication may be included in the UE application trigger request, or may not be included).
  • the UE application trigger request is processed in time by the device indicating that the UE application trigger request is received.
  • the home location server may store the UE application trigger request; and carry the UE application trigger request in a Insert Subscriber Data Request or a Cancel Location request. Or sent to the mobility management network element in other requests or messages.
  • the home location server may further carry a high priority processing indication in the message carrying the UE application trigger request sent to the mobility management network element (wherein, if the Application Server sends the UE application trigger request to the home location server) If there is a high priority processing indication, the home location server may carry the UE application trigger request including the high priority processing indication in a message and send it to the mobility management network element, if the Application Server sends the UE application to the home location server.
  • the trigger request does not include the high priority processing indication, and the home location server may insert a high priority processing indication in the message carrying the UE application trigger request sent to the mobility management network element;), to indicate that the UE application trigger is received.
  • the requesting device processes the UE application trigger request in time. Step 120a or 120b or 120c is performed.
  • the mobility management network element sends a request (eg, a control plane request) carrying the device application trigger request to the device to trigger the device.
  • a request eg, a control plane request
  • control plane request refers to a control plane request initiated by the local end (the local end refers to the mobility management network element) (ie, the control plane origination request), and is not for other devices.
  • the requested response refers to a control plane request initiated by the local end (the local end refers to the mobility management network element) (ie, the control plane origination request), and is not for other devices.
  • the requested response refers to a control plane request initiated by the local end (the local end refers to the mobility management network element) (ie, the control plane origination request), and is not for other devices.
  • the requested response refers to a control plane request initiated by the local end (the local end refers to the mobility management network element) (ie, the control plane origination request), and is not for other devices.
  • the requested response refers to a control plane request initiated by the local end (the local end refers to the mobility management network element) (ie, the control plane origination request), and is not for other devices.
  • the requested response refers to a control
  • the mobility management network element may send a paging request or a detach request or the like that carries the device application trigger request to the device, such as an H2H device or an M2M device, to trigger the device.
  • the mobility management network element sends the The role of the detach request is not to indicate that the device is detached. Therefore, after receiving the detach request, the device can obtain the UE application trigger request without performing detachment, or the mobility management network element can be sent to the M2M device or the H2H device. Send another control plane request carrying the UE application trigger request to trigger the device.
  • the mobility management network element may carry the UE application trigger request in a non-critical extension field or other field of the paging request, and the device may obtain the UE from the non-critical extension field or other field of the paging request.
  • Application trigger request the device can interact with the Application Server based on this data.
  • the mobility management network element after receiving the UE application trigger request, the mobility management network element sends the UE application trigger request to the device through the active originating control plane request, thereby improving the mobility management network element to deliver the UE application trigger.
  • the initiative of the request is beneficial to ensure that the UE application trigger request arrives at the real-time nature of the H2H device or the M2M device.
  • the mobility management network element sends a request for carrying the device application trigger request to the access network element, so that the access network element triggers the device.
  • the mobility management network element may send, for example, a radio access bearer setup request carrying the UE application trigger request, or a radio access bearer modification request, or a radio access release request or other control plane to the access network element. request.
  • the access network element may correspondingly obtain the UE application trigger request from the request.
  • the mobility management network element may carry the received UE application trigger request in a radio access bearer setup request, or a radio access bearer modification request or a radio access bearer release.
  • Requested Evolved Packet System-Protocol Data Unit (EPS-PDU) or other field and the access network element receives the radio access bearer setup request, or the radio access bearer modification request, or After the radio access bearer release request, the UE application trigger request may be obtained from an evolved packet system-protocol data unit (EPS-PDU) or other field of the message.
  • EPS-PDU evolved packet system-protocol data unit
  • the mobility management network element may, for example, carry a high-priority processing indication in the request that carries the UE application trigger request, to indicate that the access network element that receives the request sends the UE application trigger request to the corresponding UE in time.
  • a device such as an H2H device or an M2M device to trigger the device.
  • the access network element may send, for example, a wireless connection reconfiguration request carrying the UE application trigger request to a device such as a corresponding H2H device or an M2M device (eg, the UE application trigger request may be carried in a future key of the wireless connection reconfiguration request) An extension field or other field) or other message, and if the device such as an H2H device or an M2M device receives the wireless connection reconfiguration request or other request or message, it can obtain from the future key extension field or other field of the request or message.
  • the UE application trigger request can establish a communication channel and perform data interaction with the Application Server.
  • the mobility management network element after receiving the UE application trigger request, the mobility management network element sends the UE application trigger request to the access network element by using the actively originating control plane request, so that the access network element can timely the UE
  • the application trigger request is sent to the device such as the H2H device or the M2M device to trigger the device. This improves the active '1' of the UE application trigger request, which is beneficial to ensure that the UE application trigger request reaches the H2H device or the M2M device. real-time.
  • the mobility management network element sends a request for carrying the device application trigger request to the gateway network element to enable the gateway network element to trigger the device.
  • the mobility management network element may send a bearer modification request or a bearer creation request that carries the device application trigger request to the gateway network element to enable the gateway network element to trigger the device (where the mobility management network element sends the bearer modification request)
  • the role of the bearer creation request does not necessarily mean that the gateway network element modifies the bearer or creates the bearer. Therefore, after receiving the bearer modification request or the bearer creation request, the gateway network element may The UE application trigger request is obtained, and the operation of modifying the bearer or creating the bearer may not be performed) or the mobility management network element may send another control plane request carrying the device application trigger request to the gateway network element to enable the gateway network element to trigger device.
  • the gateway network element can correspondingly obtain the UE application trigger request from the request.
  • the mobility management network element may carry the UE application trigger request in a protocol configuration option field or other field of the bearer modification request or the bearer creation request, and after receiving the bearer modification request or the bearer creation request, the gateway network element may The UE application trigger request is obtained from the protocol configuration option field or other field of the request.
  • the mobility management network element may further carry a high priority processing indication, for example, in the request for carrying the device application trigger request sent by the gateway network element, to indicate that the gateway network element that received the request message timely applies the UE application
  • the trigger request is sent to the corresponding H2H device or M2M device through the user plane packet to trigger the device.
  • the gateway network element may send, for example, a downlink data packet or other user plane data packet carrying the UE application trigger request to the corresponding M2M device, and the device may receive the downlink data packet or other user plane data.
  • the UE application trigger request is obtained from the data packet, and a communication channel and data interaction are established according to the Application Server.
  • the method may further include: determining, by the mobility management network element, whether the device corresponding to the device identifier has been detached; if not, sending a request to the device to trigger the device application triggering Or sending a request to the access network element to carry the device application trigger request to enable the access network element to trigger the device; or sending a request to the gateway network element to carry the device application trigger request to enable the gateway network element Triggering the device; if yes, sending a message to the home location server indicating that the device failed to trigger.
  • the mobility management network element may also default to the device not being detached, and send a request for the device to trigger the device to trigger the device; or send a request to the access network element to carry the device application trigger request. Enabling the access network element to trigger the device; or sending a request to the gateway network element to carry the device application trigger request, so that the gateway network element triggers the device, and does not perform determining whether the device corresponding to the device identifier has been detached A step of.
  • the mobility management network element can send the UE application trigger request to the gateway network element by using the actively originating control plane request, so that the network can be made
  • the off-network element can timely send the UE application trigger request to the H2H device or the M2M device through the user plane data packet to trigger the device, thereby improving the active application of the UE application trigger request by the network. It is beneficial to ensure the real-time performance of the UE application trigger request to the device to be triggered.
  • Another embodiment of the device triggering method provided by the embodiment of the present invention includes: a gateway network element receiving a request for a mobile device application trigger request from a mobility management network element; and sending, to the device, a data packet carrying the device application trigger request (for example, , downlink packet).
  • the mobility management network element for example, the gateway network element sends a bearer modification request or a bearer creation request that carries the device application trigger request, so that the gateway network element triggers the device (where the mobility management network element sends the bearer modification request or bearer)
  • the request to create a request does not necessarily mean that the gateway network element modifies the bearer or creates the bearer. Therefore, after receiving the bearer modification request or the bearer creation request, the gateway network element may obtain the UE application trigger request from the UE, but may not perform the tampering or creation.
  • the operation or the mobility management network element may send another control plane request carrying the device application trigger request to the gateway network element to enable the gateway network element to trigger the device.
  • the gateway network element may correspondingly obtain the UE application trigger request from the request message.
  • the mobility management network element may carry the UE application trigger request in a protocol configuration option field or other field of the bearer modification request or the bearer creation request, and after receiving the bearer modification request or the bearer creation request, the gateway network element may The UE application trigger request is obtained from a protocol configuration option field or other field of the request message.
  • the mobility management network element may further carry a high priority processing indication, for example, in the request for carrying the device application trigger request sent by the gateway network element, to indicate that the gateway network element that received the request message timely applies the UE application
  • the trigger request is sent to the corresponding H2H device or M2M device through the user plane packet to trigger the device.
  • the gateway network element may send, for example, a downlink data packet or other user plane data packet carrying the UE application trigger request to the corresponding device, and the H2H device or the M2M device may receive the downlink data packet. Or other user plane data packets, obtain the UE application trigger request from the data packet, and establish a communication channel with the Application Server according to this and perform the number According to the interaction.
  • the mobility management network element sends the device application trigger request to the device through the initiative originating request after receiving the device application trigger request, or accesses the request through the active originating request.
  • the network element or the gateway network element sends the device application trigger request, so that the access network element or the gateway network element can send the device application trigger request to the corresponding device to trigger the device, and the mechanism improves the network sending device.
  • the application triggers the initiative and real-time of the request, which in turn facilitates the timely and effective triggering of data exchange between the device and the application server such as the M2M device or the H2H device.
  • an application scenario in which an M2M device is triggered in an LTE (Long Term Evolution) system is taken as an example to illustrate an application that triggers an H2H device.
  • the scene can be pushed like this.
  • LTE Long Term Evolution
  • the Application Server sends a UE application trigger request to the HSS.
  • the Application Server can directly send the UE application trigger request to the HSS, or the UE application trigger request can be carried in a request or message to the HSS.
  • the UE application trigger request may carry the device identifier of the M2M device that needs to be triggered.
  • the Application Server may also send a UE application trigger request ⁇ to the HSS, and send a high priority processing indication to the HSS (the high priority processing indication may be included in the UE application trigger request, or may not be included).
  • the device that receives the UE application trigger request is processed in time to process the UE application trigger request 0
  • the HSS receives the concurrent application of the UE application trigger request
  • the HSS sends the UE application trigger request to the MME;
  • the HSS may send the UE application trigger request to the MME by carrying the Insert Subscriber Data Request or the Cancel Location request or other message.
  • the UE application trigger request is carried in the Insert Subscriber Data Request by the HSS and sent to the MME as an example.
  • the HSS may further carry a high priority processing indication in the message that is sent to the MME and that carries the UE application trigger request, to indicate that the UE application trigger is received.
  • the requesting device processes the UE application trigger request in time.
  • MME UE application trigger request from the HSS
  • the MME may, for example, receive an Insert Subscriber Data Request or Cancel Location request or other message from the HSS that carries the UE application trigger request, and obtain a UE application trigger request from the HSS.
  • the MME may send an Insert Subscriber Data answer or a Cancel Location ACK response or other corresponding response to the HSS, where the MME sends an Insert Subscriber Data answer to the HSS as an example.
  • the MME obtains a default bearer identity or a dedicated bearer identity and an S-GW identifier corresponding to the M2M device, so as to subsequently perform a modify bearer request or a bearer creation request (Create Bearer).
  • Request Send the UE application trigger request to the S-GW so that the S-GW can send it to the M2M device through the user plane bearer.
  • the MME sends a Modify Bearer Request or a Create Bearer Request to the S-GW.
  • the Modify Bearer Request or the Create Bearer Request sent by the MME to the S-GW carries the UE application trigger request, and carries the default bearer identity or the dedicated bearer identity. .
  • the UE application trigger request may be carried in, for example, a Protocol Configuration Option in the Create Bearer Request or the Modify Bearer Request, and may be carried in other fields.
  • the MME sends a Modify Bearer Request to the S-GW as an example.
  • the S-GW After receiving the Modify Bearer Request or the Create Bearer Request, the S-GW determines that the UE application trigger request is sent to the M2M device by using a default bearer or a dedicated bearer.
  • the role of the MME to send the bearer modification request or the bearer creation request herein does not necessarily indicate that the S-GW modifies the bearer or creates the bearer. Therefore, after receiving the bearer modification request or the bearer creation request, the S-GW can obtain the UE from the UE. Application trigger request, and may not perform operations to modify the bearer or create a bearer.
  • the S-GW sends a Modify Bearer Response or a Create Bearer Response to the MME;
  • the Modify Bearer Response is sent to the MME by the S-GW as an example.
  • Data carries UE application trigger request
  • the M2M device establishes a communication channel to the Application Server, and the Application Server and the M2M device perform data interaction.
  • the MME may delete the saved UE application trigger request, and may send a notification request (Notify Request) to the HSS, where the Notify Request may carry an ACK of UE application trigger request, indicating the UE application.
  • the trigger request has been successfully sent to the M2M device.
  • the HSS sends a notification response response (Notify Answer) to the MME, and deletes the stored UE application trigger request.
  • the MME after receiving the UE application trigger request sent by the HSS, the MME sends the UE application trigger request to the gateway network element by using the actively originating control plane request, and the gateway network element passes the user plane.
  • the data packet is sent to the corresponding device to send the UE application trigger request.
  • This mechanism improves the initiative and real-time performance of the UE application trigger request, which is beneficial to the device to interact with the application server in a timely and effective manner.
  • an application scenario in which an M2M device is triggered in an LTE system is taken as an example, and an application scenario that triggers an H2H device may be deduced.
  • the Application Server sends a UE application trigger request to the HSS.
  • the Application Server can directly send the UE application trigger request to the HSS, or the UE application trigger request can be carried in a message and sent to the HSS.
  • the UE application trigger request may carry the device identifier of the M2M device that needs to be triggered.
  • Application Server can also send UE application trigger request to HSS.
  • the high priority processing indication is sent to the HSS to indicate that the device receiving the UE application trigger request processes the UE application trigger request in time.
  • the HSS receives the concurrent application of the UE application trigger request
  • the HSS sends the UE application trigger request to the MME;
  • the HSS may send the UE application trigger request to the MME by carrying the Insert Subscriber Data Request or the Cancel Location Request or other message.
  • the UE application trigger request is carried by the HSS in the Insert Subscriber Data Request and sent to the MME as an example.
  • the HSS may further carry a high priority processing indication in the message that is sent to the MME to carry the UE application trigger request, to indicate that the device that receives the UE application trigger request processes the UE application trigger request in time.
  • MME UE application trigger request from the HSS
  • the MME may, for example, receive an Insert Subscriber Data Request or Cancel Location request or other message from the HSS that carries the UE application trigger request, and obtain a UE application trigger request from the HSS.
  • the MME may send an Insert Subscriber Data answer or a Cancel Location ACK response or other corresponding response to the HSS, where the MME sends an Insert Subscriber Data answer to the HSS as an example.
  • the MME may determine that a Paging request is sent to the M2M device according to the high priority processing indication, and the UE application trigger request is carried in the Paging request.
  • the UE application trigger request may, for example, be carried in a non-critical extension field or other field of the Paging request.
  • the MME sends the UE application trigger request to the M2M device through the Paging request.
  • the MME can also actively send the request to the M2M device through the Detach request or other control plane request.
  • UE application trigger request If the MME can also send the UE application trigger request to the M2M device through the Detach request message, the M2M device needs to return a Detach Reject response to the MME.
  • the role of the MME sending the Detach request is not to indicate that the device is detached, so the M2M device receives the Detach request.
  • the UE application trigger request can be obtained from it without performing the P payment.
  • the M2M device establishes a communication channel to the Application Server, and the Application Server and the M2M device perform data interaction.
  • the MME may delete the saved UE application trigger request, and may send a notification request (Notify Request) to the HSS, where the Notify Request may carry an ACK of UE application trigger request, indicating the UE application.
  • the trigger request has been successfully sent to the M2M device.
  • the HSS sends a notification response response (Notify Answer) to the MME.
  • the MME sends a Purging UE (Purge UE) request to the HSS, where the Purge UE request carries an indication of deleting the UE application trigger request.
  • Purging UE Purge UE
  • the HSS deletes the stored UE application trigger request, and sends a Delete Device Confirmation Response (Purge UE ACK) to the MME.
  • Purge UE ACK Delete Device Confirmation Response
  • the MME sends the UE application trigger request to the device through the active originating control plane request after receiving the UE application trigger request, and the mechanism improves the network application UE request trigger request. Proactive and real-time, which in turn helps the device to interact with Application Server more timely and efficiently.
  • an application scenario in which an M2M device is triggered in an LTE system is taken as an example, and an application scenario for triggering an H2H device may be deduced.
  • specific steps may include:
  • the Application Server sends a UE application trigger request to the HSS.
  • the Application Server can directly send the UE application trigger request to the HSS, or the UE application trigger request can be carried in a message and sent to the HSS.
  • the UE application trigger request may carry the device identifier of the M2M device that needs to be triggered.
  • the Application Server may also send a UE application trigger request to the HSS, and send a high priority processing indication to the HSS to indicate that the device receiving the UE application trigger request processes the UE application trigger request in time.
  • the HSS receives and stores the UE application trigger request;
  • the HSS sends the UE application trigger request to the MME;
  • the HSS may send the UE application trigger request to the MME by carrying the Insert Subscriber Data Request or the Cancel Location Request or other message.
  • the UE application trigger request is carried by the HSS in the Insert Subscriber Data Request and sent to the MME as an example.
  • the HSS may further carry a high priority processing indication in the request or message that is sent to the MME to carry the UE application trigger request, to indicate that the device that receives the UE application trigger request processes the UE application trigger request in time.
  • MME UE application trigger request from the HSS
  • the MME may, for example, receive an Insert Subscriber Data Request or Cancel Location request or other message from the HSS that carries the UE application trigger request, and obtain a UE application trigger request from the HSS.
  • the MME may send an Insert Subscriber Data answer or a Cancel Location ACK response or other corresponding response to the HSS, where the MME sends an Insert Subscriber Data answer to the HSS as an example.
  • the MME may determine, according to the UE application trigger request and the high priority processing indication, that an ETA installation request (E-RAB Setup Request) needs to be sent to the eNodeB, so as to complete the establishment of the radio resource link.
  • the device sends a UE application trigger request.
  • the MME actively sends the UE application trigger request to the eNodeB through the E-RAB Setup Request.
  • the MME can also use the E-RAB Modify Request or the E-RAB Modify Request.
  • a radio access bearer release request (E-RAB Release Request) or other control plane request is used to actively send a UE application trigger request to the eNodeB.
  • the UE application trigger request may be, for example, an Enhanced Packet System-Protocol Data Unit (EPS-PDU) or other field in an E-RAB Setup Request or an E-RAB Modify Request or an E-RAB Release Request. 405.
  • EPS-PDU Enhanced Packet System-Protocol Data Unit
  • the eNodeB sends a radio connection reconfiguration (RRC) request to the M2M device, where the RRC request carries the UE application trigger request.
  • RRC radio connection reconfiguration
  • the UE application trigger request may be, for example, a future Critical Extensions Future or other field of the RRC request.
  • the M2M device receives the RRC request and establishes an RRC link. After the RRC is established, the M2M device can return a corresponding response to the eNodeB.
  • the eNodeB returns an evolved radio access bearer setup response (S1-AP: E-RAB Setup Response) to the MME.
  • S1-AP E-RAB Setup Response
  • the M2M device establishes a communication channel with the Application Server, and the Application Server and the M2M device perform data interaction.
  • the M2M device has established a radio resource link with the eNodeB. At this point, only the communication channels of other segments need to be established between the M2M device and the Application Server.
  • the MME may delete the saved UE application trigger request, and may send a notification request (Notify Request) to the HSS, where the Notify Request may carry an ACK of UE application trigger request, indicating the UE application.
  • the trigger request has been successfully sent to the M2M device.
  • the HSS sends a notification response response (Notify Answer) to the MME, and deletes the stored UE application trigger request.
  • the MME sends the UE application trigger request to the access network element by using the actively originating control plane request after receiving the UE application trigger request sent by the HSS, and the access network element passes the access network element.
  • the user plane data packet is sent to the corresponding device to send the UE application trigger request.
  • an application scenario in which an M2M device fails to be triggered in an LTE system is taken as an example, and an application scenario in which an H2H device fails to be triggered may be deduced.
  • the Application Server sends a UE application trigger request to the HSS.
  • the Application Server can directly send the UE application trigger request to the HSS, or the UE application trigger request can be carried in a message and sent to the HSS.
  • the UE application trigger request may carry the device identifier of the M2M device that needs to be triggered.
  • the Application Server may also send a UE application trigger request ⁇ to the HSS, and send a high priority processing indication to the HSS to indicate that the device receiving the UE application trigger request processes the UE application trigger request in time.
  • the HSS receives and stores the UE application trigger request.
  • the HSS sends the UE application trigger request to the MME;
  • the HSS may send the UE application trigger request to the MME by carrying the Insert Subscriber Data Request or the Cancel Location Request or other message.
  • the UE application trigger request is carried by the HSS in the Insert Subscriber Data Request and sent to the MME as an example.
  • the HSS may further carry a high priority processing indication in the message that is sent to the MME to carry the UE application trigger request, to indicate that the device that receives the UE application trigger request processes the UE application trigger request in time.
  • the MME determines that the M2M device has been Detach.
  • the MME returns an Insert Subscriber Data Answer response to the HSS.
  • the response carries the indication of the trigger failure, and may also carry the reason for the trigger failure. For example, the device fails to be Detach.
  • the HSS deletes the stored UE application trigger request according to the received Insert Subscriber Data Answer response.
  • the HSS sends a notification request to the Application Server.
  • the notification request may carry an indication that the M2M device fails to be triggered, and may also carry the reason for the trigger failure. For example, the M2M device fails to be Detach.
  • the HSS after receiving the UE application trigger request sent by the HSS, if the MME determines that the device has Detach, the HSS is instructed to delete the stored UE application trigger request, and the HSS indicates the trigger to the Application Server. Failure, the mechanism Improve the initiative and real-time of Application Server to know the trigger results.
  • an application scenario in which the triggering of the M2M device fails in the LTE system is taken as an example, and an application scenario in which the H2H device fails to be triggered may be deduced.
  • the Application Server sends a UE application trigger request to the HSS.
  • the Application Server can directly send the UE application trigger request to the HSS, or the UE application trigger request can be carried in a message and sent to the HSS.
  • the UE application trigger request may carry the device identifier of the M2M device that needs to be triggered.
  • the Application Server may also send a UE application trigger request ⁇ to the HSS, and send a high priority processing indication to the HSS to indicate that the device receiving the UE application trigger request processes the UE application trigger request in time.
  • the HSS receives and stores the UE application trigger request.
  • the HSS sends the UE application trigger request to the MME;
  • the HSS may, for example, carry the UE application trigger request in an Insert Subscriber Data Request or a Cancel Location request or other request or message to the MME.
  • the UE application trigger request is carried by the HSS in the Insert Subscriber Data Request and sent to the MME as an example.
  • the HSS may further carry a high priority processing indication in the message that is sent to the MME to carry the UE application trigger request, to indicate that the device that receives the UE application trigger request processes the UE application trigger request in time.
  • the MME determines that the M2M device has been Detach.
  • the MME returns an Insert Subscriber Data Answer response to the HSS.
  • the response carries the indication of the trigger failure, and may also carry the reason for the trigger failure. For example, the device fails to be Detach.
  • the MME sends a Purging UE (Purge UE) request to the HSS, where the Purge UE request carries an indication to delete the UE application trigger request. 607.
  • the HSS deletes the stored UE application trigger request, and may send a Delete Device Confirmation Response (Purge UE ACK) to the UI.
  • the HSS sends a notification request to the Application Server, where the notification request may carry an indication that the M2M device fails to be triggered, and may also carry the reason for the trigger failure, such as the Detach of the M2M device failure.
  • the mobility management network element 700 provided by the embodiment of the present invention may include: a receiving module 710 and a first sending module 720, or a receiving module 710 and a second
  • the sending module 730 includes a receiving module 710 and a third sending module 740.
  • the receiving module 710 is configured to receive a device application trigger request.
  • the first sending module 720 is configured to send, to the access network element, a request for carrying the device application trigger request, so that the access network element triggers the device (such as an H2H device or an M2M device).
  • the second sending module 730 is configured to send, to the gateway network element, a request for carrying the device application trigger request, so that the gateway network element triggers the device (such as an H2H device or an M2M device).
  • the third sending module 740 is configured to send a request for carrying the device application trigger request to the device to trigger the device (such as an H2H device or an M2M device).
  • the third sending module 740 is specifically configured to: send a paging request that carries the device application trigger request to the device to trigger the device; or send the device to the device The device is triggered by a detach request that triggers the request.
  • the third sending module 740 can carry the UE application trigger request in a non-critical extension field or other field of the paging request, and the device can obtain the UE from the non-key extension field or other field of the paging request.
  • Application trigger request the device can interact with the Application Server based on this data.
  • the first sending module 720 is specifically configured to: send, to the access network element, a radio access bearer setup request that carries the device application trigger request, so that the access network element triggers the device; or The network element sends a radio access bearer modification request that carries the device application trigger request to enable the access network element to trigger the device; or sends a radio access 7-load release request that carries the device application trigger request to the access network element to Enable the access NE to trigger the device.
  • the first sending module 720 may carry the received UE application trigger request in an evolved packet system-protocol data unit of a radio access bearer setup request, or a radio access bearer modification request or a radio access bearer release request ( EPS-PDU or other field, and the access network element may receive the radio access bearer setup request, or the radio access bearer modification request, or the radio access bearer release request, from the evolved packet system-protocol of the message
  • EPS-PDU radio access bearer modification request
  • radio access bearer release request from the evolved packet system-protocol of the message
  • the data unit (EPS-PDU) or other field obtains the UE application trigger request 0
  • the second sending module 730 is specifically configured to: send, to the gateway network element, a bearer modification request that carries the device application trigger request, so that the gateway network element triggers the device; or send, to the gateway network element, the carrying The device application triggers the requesting bearer creation request to cause the gateway network element to trigger the device.
  • the second sending module 730 may carry the UE application trigger request in a protocol configuration option field or other field of the bearer modification request or the bearer creation request, and after receiving the bearer modification request or the bearer creation request, the gateway network element may The UE application trigger request is obtained from a protocol configuration option field or other field of the request message.
  • the mobility management network element 700 in this embodiment may be a mobility management network element (such as an MME) in the foregoing method embodiment, and the functions of the respective functional modules may be omitted in the foregoing method embodiments.
  • a mobility management network element such as an MME
  • the mobility management network element 700 receives the device application trigger request. And sending, by the active originating control plane, the device application trigger request to the device to trigger the device, or requesting the device application trigger request to the access network element or the gateway network element by using the actively originating control plane request,
  • the mechanism improves the initiative and real-time performance of the network-issued device application trigger request, thereby facilitating the Timely and effective triggering of data exchange between devices such as ⁇ 2 ⁇ devices or ⁇ 2 ⁇ devices and application servers.
  • the gateway network element 800 provided by the embodiment of the present invention may include: a second receiving module 810 and a fourth sending module 820.
  • the second receiving module 810 is configured to receive a request for a mobile device application trigger request from the mobility management network element.
  • the fourth sending module 820 is configured to send, to the device, a data packet (such as a downlink data packet) that carries the device application trigger request to trigger the device.
  • a data packet such as a downlink data packet
  • gateway network element 800 in this embodiment may be a gateway network element (such as an eNodeB) in the foregoing method embodiment, and the functions of the respective functional modules may be described in the method in the foregoing method embodiment.
  • a gateway network element such as an eNodeB
  • the mobility management network element of the embodiment sends the device application trigger request to the gateway network element 800 through the actively originating control plane request, and the gateway network element 800 corresponds to the corresponding
  • the device sends the device application trigger request to trigger the device.
  • This mechanism improves the initiative and real-time performance of the device sending request triggered by the network, thereby facilitating more timely and effective triggering of interaction between the M2M device or the H2H device and the application server. data.
  • the embodiment of the invention further provides a communication system, including:
  • the mobility management network element 700 or the gateway network element 800 includes: a mobility management network element 910 and a gateway network element 920.
  • the mobility management network element 910 is configured to receive a device application trigger request, and send a request to the gateway network element 920 to carry the device application trigger request.
  • the gateway network element 920 is configured to receive a request for a mobile device application trigger request from the mobility management network element 910, and send a data packet carrying the device application trigger request to the device to trigger the device.
  • the mobility management network element 910 of this embodiment can be as the mobility management network element 700, and the functions of the gateway network element 920, such as the gateway network element 800, the mobility management network element 910, and the gateway network element 920, can be
  • the method in the method embodiment is specifically implemented, and the specific implementation process may refer to the related description of the foregoing method embodiment, and details are not described herein again.
  • the mobility management network element in the embodiment of the present invention sends a device application trigger request to the device to trigger the device by using the actively originating control plane request, or
  • the originating control plane requests to send the device application trigger request to the access network element or the gateway network element, so that the access network element or the gateway network element can send the device application trigger request to the corresponding device to trigger the device.
  • the mechanism relatively improves the initiative and real-time performance of the device-issued device application trigger request, and is more beneficial for triggering the interaction data between the device and the application server such as the M2M device or the H2H device in a timely and effective manner.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Read-only memory, random access memory, disk or optical disk, etc.

Landscapes

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

Description

设备触发方法及网元设备 技术领域
本发明涉及通信技术领域， 具体涉及设备触发方法及网元设备。 背景技术
在现有的通信方式中， 主要存在人到人（H2H, Human to Human )和机器 到机器（M2M, Machine to Machine )等两种通信模型。
H2H应用主要指以人为通信主体的通信， 例如电话通信等； 而 M2M应用 也称机器类型通讯（ MTC , Machine Type Communications )应用是指多个网元 间在无人参与的情况下进行的网络通讯， 例如交通控制与管理、 远程抄表、 远 程监控、 移动支付、 定位跟踪、 医疗监护等应用。 M2M技术综合了通信和网 络技术， 可将遍布在人们日常生活中的机器设备连接成网络，使这些设备变得 更加 "智能，，， 从而可创造出丰富的应用， 给日常生活、 工业生产等的方式带 来新一轮的变革。 在未来的各种 M2M应用中， 为更好地实现网络侧对设备的 管理， 业内提出了 M2M设备触发的特性。 即 M2M应用服务器需要 M2M设备同 其进行通信时， 首先需对该 M2M设备进行触发， 然后该 M2M设备才会通过网 络同该 M2M应用服务器进行数据交互等。
现有 M2M设备或 H2H设备触发机制中， 设备先主动发送附着请求或跟踪 区更新请求等非接入层（NAS, Non-Access Stratum )信令， 而核心网在接收 到设备发送的该 NAS信令后，将设备应用触发请求携带对应该 NAS信令的响应 中发送给设备以完成该设备的触发。 发明内容
本发明实施例提供设备触发方法及网元设备， 以提高对 M2M设备或 H2H 设备触发的主动性和实时性。
为解决上述技术问题， 本发明实施例提供一下技术方案：
一种设备触发方法， 包括：
移动性管理网元接收设备应用触发请求； 向接入网元发送携带所述设备应用触发请求的请求以使所述接入网元触 发设备；
或者，
向网关网元发送携带所述设备应用触发请求的请求以使所述网关网元触 发设备。
一种设备触发方法， 包括：
网关网元接收来自移动性管理网元的携带设备应用触发请求的请求； 向设备发送携带所述设备应用触发请求的数据包以触发所述设备。
一种移动性管理网元， 包括：
接收模块， 用于接收设备应用触发请求；
第一发送模块，用于向接入网元发送携带所述设备应用触发请求的请求以 使所述接入网元触发设备；
或者，
第二发送模块，用于向网关网元发送携带所述设备应用触发请求的请求以 使所述网关网元触发设备。
一种网关网元， 包括：
第二接收模块，用于接收来自移动性管理网元的携带设备应用触发请求的 请求；
第四发送模块，用于向设备发送携带所述设备应用触发请求的数据包以触 发所述设备。
由上可见， 本发明实施例的移动性管理网元在接收到设备应用触发请求 后，由于是通过主动始发的请求向接入网元或网关网元下发该设备应用触发请 求，以使得该接入网元或网关网元能够向对应的设备下发该设备应用触发请求 以触发该设备，该机制相对提高了网络下发设备应用触发请求的主动性和实时 性， 进而有利于更及时有效的触发 M2M设备或 H2H设备和应用服务器交互数 据。 附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例描述所需要 使用的附图作筒单地介绍，显而易见地， 下面描述中的附图仅仅是本发明的一 些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动的前提下， 还 可以根据这些附图获得其他的附图。
图 1是本发明实施例提供的一种设备触发方法的流程示意图；
图 2是本发明实施例提供的另一种设备触发方法的流程示意图；
图 3是本发明实施例提供的又一种设备触发方法的流程示意图；
图 4是本发明实施例提供的再一种设备触发方法的流程示意图；
图 5是本发明实施例提供的还另一种设备触发方法的流程示意图； 图 6是本发明实施例提供的还另一种设备触发方法的流程示意图； 图 7-a是本发明实施例提供的一种移动性管理网元的结构示意图； 图 7-b是本发明实施例提供的再一种移动性管理网元的结构示意图； 图 7-c是本发明实施例提供的另一种移动性管理网元的结构示意图； 图 8本发明实施例提供的一种网关网元的结构示意图；
图 9本发明实施例提供的一种通信***的示意图。 具体实施方式
本发明实施例提供设备触发方法及网元设备， 以提高对 M2M设备或 H2H 设备触发的主动性和实时性。
为使得本发明的发明目的、 特征、优点能够更加的明显和易懂， 下面将结 合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、 完整地描 述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而非全部实施例。 基 于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获 得的所有其他实施例， 都属于本发明保护的范围。 首先说明的是，本发明实施例所指接入网元是指可实现用户设备无线接入 管理功能的实体，本发明实施例所指移动性管理网元是指可实现用户设备移动 性管理逻辑功能的实体，而接入网元和移动性管理网元在不同的网络中可能具 有不同的名称、 位置和产品形态。
举例来说， 本发明下述实施例中提及的接入网元例如可指： 演进通用移动 通信***（ UMTS, Universal Mobile Telecommunications System ) 陆地无线接 入网 （E-UTRAN, Evolved UMTS Territorial Radio Access Network ) 中的演进 基站 （eNodeB )、 家庭基站（ HeNB )或其它类型的基站； 或 UMTS陆地无线 接入网 （UTRAN, UMTS Territorial Radio Access Network ) / GSM EDGE无线 接入网 （GERAN, GSM EDGE Radio Access Network ) 中的基站控制器、 或无 线网络控制器（RNC, Radio Network Controller ); 或者也可指宽带码分多址接 入（ CDMA, Code Division Multiple Access ) 网络中具有高速率分组数据接入 网 （ HRPD- AN , High Rate Packet Data Access Network )接入网逻辑功能的实 体、 无线局域网 （WLAN, Wireless Local Area Network ) 中具有演进分组数据 网关（ EPDG , Evolved Packet Data Gateway )接入网逻辑功能的实体； 微波存 取全球互通 ( WiMAX, Worldwide Interoperability for Microwave Access ) 网络 中的接入服务网络基站（ASN-BS, Access Service Network Base Station )或其 它网络中实现终端无线接入管理的实体。
举例来说，本发明实施例提及的移动性管理网元可指与 E-UTRAN连接的 移动性管理实体 MME、 与 UTRAN/GERAN连接的通用分组无线业务服务节 点 （SGSN, Serving GPRS ( General Packet Radio Service ) Support Node ); 或 非 3GPP网络中的接入网关（ AGW, Access Gateway )、 WLAN中具有移动性 管理逻辑功能的实体 ePDG、 微波存取全球互通 WiMAX网络中的接入服务网 络网关（ ASN GW, Access Service Network Gateway )、 或 CDMA网络中具有 高速率分组数据接入网 HRPD-AN移动性管理逻辑功能的实体、或其它网络中 实现用户设备移动性管理逻辑功能的实体。
本发明实施例提及的归属位置服务器指 （HLR, Home Location Register ) 或者 ( HSS, Home Subscriber Server )等。
本发明实施例提及的设备指 H2H设备或 M2M设备， 本发明实施例的方 案用于触发 H2H设备或 M2M设备。
下面通过具体实施例进行详细说明。 本发明设备触发方法的一个实施例， 可包括： 移动性管理网元接收来自归 属位置服务器的设备应用触发请求； 向设备（如 H2H设备或 M2M设备）发送 携带该设备应用触发请求的请求（如控制面请求）以使触发该设备； 或者， 向 接入网元发送携带该设备应用触发请求的请求（如控制面请求 )以使该接入网 元触发设备； 或者， 向网关网元发送携带该设备应用触发请求的请求（如控制 面请求 ) 消息以使该网关网元触发设备。
参见图 1 , 具体步骤可包括：
110、 移动性管理网元接收设备应用触发请求；
在一种应用场景下， 应用服务器（ Application Server )若需触发某 M2M设 备或 H2H设备与其进行通信（如 Application Server需要某 M2M设备向其上报某 类数据）时， Application Server可向归属位置服务器发送设备应用触发请求（ UE application trigger request ), 该 UE application trigger request中携带有需触发的 M2M设备或 H2H设备的设备标识。
此外， Application Server还可在向归属位置服务器发送 UE application trigger request的同时， 向其发送高优先级处理指示（该高优先级处理指示可包 含在 UE application trigger request中， 或者亦可不包含其中）， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
归属位置月良务器在接收到 Application Server发送的 UE application trigger request后 , 可存储该 UE application trigger request; 并将该 UE application trigger request携带在***签约数据请求 ( Insert Subscriber Data Request )或者 Cancel Location请求或者其它请求或消息中发送给移动性管理网元。 此外， 归属位置 服务器还可在向移动性管理网元发送的携带该 UE application trigger request的 消息中携带高优先级处理指示 （其中， 若 Application Server向归属位置服务器 发送的该 UE application trigger request中包含有高优先级处理指示，则归属位置 服务器可将包含高优先级处理指示的 UE application trigger request携带在某个 消息中发送给移动性管理网元， 若 Application Server向归属位置服务器发送的 该 UE application trigger request中不包含高优先级处理指示，则归属位置服务器 可在向移动性管理网元发送的携带 UE application trigger request的消息中*** 高优先级处理指示；)， 以指示接收到该 UE application trigger request的设备及时 处理该 UE application trigger request。 执行步骤 120a或者 120b或者 120c。
120a,移动性管理网元向设备发送携带该设备应用触发请求的请求（例如， 控制面请求） 以触发该设备。
需要说明的是， 所述控制面请求是指由本端（该本端此处指移动性管理网 元）主动发起的控制面请求（即控制面始发请求）， 而并非是对来自其它设备 的请求的响应。
其中， 移动性管理网元例如可向设备（如 H2H设备或 M2M设备）发送携 带该设备应用触发请求的寻呼请求或者去附着请求等以触发该设备 (此处，移 动性管理网元发送该去附着请求的作用并非是指示设备去附着，因此设备接收 到该去附着请求后可从中获得 UE application trigger request, 而并不执行去附 着）， 或者移动性管理网元可向 M2M设备或 H2H设备发送携带该 UE application trigger request的其它控制面请求以触发该设备。
举例来说，移动性管理网元可将 UE application trigger request携带在寻呼请 求的非关键扩展字段或其它字段，而设备可对应的从该寻呼请求的非关键扩展 字段或其它字段获得该 UE application trigger request , 该设备可据此和 Application Server进行数据交互。
可见，移动性管理网元在接收到 UE application trigger request后，若通过主 动始发的控制面请求向设备下发该 UE application trigger request,这样也就提高 了移动性管理网元下发 UE application trigger request的主动性， 有利于保证 UE application trigger request到达如 H2H设备或 M2M设备的实时性。
120b、移动性管理网元向接入网元发送携带该设备应用触发请求的请求以 使该接入网元触发设备。
其中，移动性管理网元例如可向接入网元发送携带该 UE application trigger request的无线接入承载建立请求、 或者无线接入承载修改请求、 或者无线接入 ^^载释放请求或者其它控制面请求。 而接入网元可对应的从该请求中获得该 UE application trigger request。
举例来说，移动性管理网元可将接收到的 UE application trigger request携带 在无线接入承载建立请求、或者无线接入承载修改请求或者无线接入承载释放 请求的演进分组***-协议数据单元 （EPS-PDU , Evolved Packet System -Protocol Data Unit )或其它字段，而接入网元接收到该无线接入承载建立请求、 或者无线接入承载修改请求、或者无线接入承载释放请求后， 可从该消息的演 进分组***-协议数据单元（ EPS-PDU )或其它字段获得该 UE application trigger request。
进一步的，移动性管理网元例如还可以在携带 UE application trigger request 的请求中携带高优先级处理指示，用以指示接收到该请求的接入网元及时将该 UE application trigger request下发给对应的 H2H设备或 M2M设备等设备以触发 该设备。
此外， 接入网元例如可向对应的 H2H设备或 M2M设备等设备发送携带该 UE application trigger request的无线连接重配置请求 (如可将该 UE application trigger request携带在无线连接重配置请求的将来关键扩展字段或其它字段）或 其它消息， 而如 H2H设备或 M2M设备等设备接收到该无线连接重配置请求或 其它请求或消息后，可从该请求或消息的将来关键扩展字段或其它字段中获得 该 UE application trigger request, 并可据此和 Application Server建立通信通道并 进行数据交互。
可见，移动性管理网元在接收到 UE application trigger request后，若通过主 动始发的控制面请求向接入网元下发该 UE application trigger request,进而使得 接入网元能够及时的将该 UE application trigger request下发给如 H2H设备或 M2M设备以触发该设备， 这样也就提高了网络下发 UE application trigger request的主动 '1 "生, 有利于保证 UE application trigger request到达 H2H设备或 M2M设备的实时性。
120c,移动性管理网元向网关网元发送携带该设备应用触发请求的请求以 使该网关网元触发设备。
其中， 例如，移动性管理网元可向网关网元发送携带该设备应用触发请求 的承载修改请求或承载创建请求以使该网关网元触发设备（此处移动性管理网 元发送该承载修改请求或承载创建请求作用并非一定是指示网关网元修改承 载或创建承载， 因此网关网元接收到该承载修改请求或承载创建请求后， 可从 中获得 UE application trigger request, 而可并不执行修改承载或创建承载的操 作）或移动性管理网元可向网关网元发送携带该设备应用触发请求的其它控制 面请求以使该网关网元触发设备。 而网关网元可对应的从该请求中获得该 UE application trigger request。
举例来说，移动性管理网元可将 UE application trigger request携带在承载修 改请求或承载创建请求的协议配置选项字段或其它字段，而网关网元接收到该 承载修改请求或承载创建请求后，可从该请求的协议配置选项字段或其它字段 获得该 UE application trigger request。
进一步的 ,移动性管理网元例如还可以在向网关网元发送的携带该设备应 用触发请求的请求中携带高优先级处理指示，以指示接收到该请求消息的网关 网元及时将该 UE application trigger request通过用户面数据包下发给对应的 H2H设备或 M2M设备等设备以触发该设备。
此外， 网关网元例如可向对应的 M2M设备发送携带该 UE application trigger request的下行链路数据包或其它用户面数据包， 而设备则可在接收到该 下行链路数据包或其它用户面数据包后， 从该数据包中获得该 UE application trigger request , 并可据此和 Application Server建立通信通道并进行数据交互。
在实际应用中， 接收设备应用触发请求之后， 还可包括： 移动性管理网元 判断该设备标识对应的设备是否已去附着； 若否， 则向设备发送携带该设备应 用触发请求的请求以触发该设备； 或者， 向接入网元发送携带该设备应用触发 请求的请求以使该接入网元触发设备； 或者， 向网关网元发送携带该设备应用 触发请求的请求以使该网关网元触发设备； 若是， 则向归属位置服务器发送指 示设备触发失败的消息。 当然， 移动性管理网元亦可默认该设备未去附着， 而 向该设备发送携带该设备应用触发请求的请求以触发该设备； 或者， 向接入网 元发送携带该设备应用触发请求的请求以使该接入网元触发该设备； 或者， 向 网关网元发送携带该设备应用触发请求的请求以使该网关网元触发该设备，而 并不执行判断设备标识对应的设备是否已去附着的步骤。
可见，移动性管理网元在接收到 UE application trigger request后，若通过主 动始发的控制面请求向网关网元下发该 UE application trigger request,可使得网 关网元能够及时的将该 UE application trigger request通过用户面数据包下发给 H2H设备或 M2M设备等设备以触发该设备， 这样就提高了网络下发 UE application trigger request的主动' ί生 , 有利于保证 UE application trigger request到 达待触发设备的实时性。
下面从网关网元的角度进行描述。
本发明实施例提供的设备触发方法的另一个实施例， 包括： 网关网元接收 来自移动性管理网元的携带设备应用触发请求的请求；向设备发送携带该设备 应用触发请求的数据包（例如， 下行链路数据包）。
其中，移动性管理网元例如可网关网元发送携带该设备应用触发请求的承 载修改请求或承载创建请求以使该网关网元触发设备（此处移动性管理网元发 送该承载修改请求或承载创建请求作用并非一定是指示网关网元修改承载或 创建承载， 因此网关网元接收到该承载修改请求或承载创建请求后， 可从中获 得 UE application trigger request, 而可并不执行爹改 载或创建 载的操作 )或 移动性管理网元可向网关网元发送携带该设备应用触发请求的其它控制面请 求以使该网关网元触发设备。 而网关网元可对应的从该请求消息中获得该 UE application trigger request。
举例来说，移动性管理网元可将 UE application trigger request携带在承载修 改请求或承载创建请求的协议配置选项字段或其它字段，而网关网元接收到该 承载修改请求或承载创建请求后，可从该请求消息的协议配置选项字段或其它 字段获得该 UE application trigger request。
进一步的 ,移动性管理网元例如还可以在向网关网元发送的携带该设备应 用触发请求的请求中携带高优先级处理指示，以指示接收到该请求消息的网关 网元及时将该 UE application trigger request通过用户面数据包下发给对应的 H2H设备或 M2M设备等设备以触发该设备。
此夕卜， 网关网元例如可向对应的设备发送携带该 UE application trigger request的下行链路数据包或其它用户面数据包，而 H2H设备或 M2M设备则可在 接收到该下行链路数据包或其它用户面数据包后， 从该数据包中获得该 UE application trigger request,并可据此和 Application Server建立通信通道并进行数 据交互。
由上可见，本实施例中由于移动性管理网元是在接收到设备应用触发请求 后，通过主动始发的请求向设备下发该设备应用触发请求， 或者通过主动始发 的请求向接入网元或网关网元下发该设备应用触发请求，以使得该接入网元或 网关网元能够向对应的设备下发该设备应用触发请求以触发该设备，该机制提 高了网络下发设备应用触发请求的主动性和实时性，进而有利于更及时有效的 触发 M2M设备或 H2H设备等设备和应用服务器交互数据。 为便于更好的理解和实施本发明实施例的上述技术方案，下面以在长期演 进（ LTE , Long Term Evolution ) ***中触发 M2M设备的一种应用场景为例进 行说明， 而触发 H2H设备的应用场景可以此类推。
参见图 2, 具体步骤可以包括：
201、 Application Server向 HSS发送 UE application trigger request;
在实际应用中 , Application Server可直接将 UE application trigger request发 送给 HSS , 或者， 亦可将该 UE application trigger request携带在某条请求或消息 中发送给 HSS。其中，该 UE application trigger request可携带有需要触发的 M2M 设备的设备标识。
匕夕卜 , Application Server还可在向 HSS发送 UE application trigger request^ 同时， 向 HSS发送高优先级处理指示 （该高优先级处理指示可包含在 UE application trigger request中， 或者亦可不包含其中）， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request 0
202、 HSS接收并存者该 UE application trigger request;
HSS向 MME发送该 UE application trigger request;
在实际应用中， HSS例如可将该 UE application trigger request携带在***签 约数据请求（ Insert Subscriber Data Request )或者删除登录（ Cancel Location ) 请求或者其它消息中发送给 MME。 其中， 图 2中以 HSS将该 UE application trigger request携带在 Insert Subscriber Data Request中发送给 MME为例。
此夕卜， HSS还可在向 MME发送的携带该 UE application trigger request的消 息中进一步携带高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
203、 MME ：来自 HSS的 UE application trigger request;
其中， MME例如可接收来自 HSS的携带有 UE application trigger request的 Insert Subscriber Data Request或 Cancel Location请求或者其它消息，并从中获取 到来自 HSS的 UE application trigger request。
MME可向 HSS发送***签约数据响应 （Insert Subscriber Data answer )或 者 Cancel Location ACK响应或其它对应的响应， 其中， 图 2中以 MME向 HSS发 送 Insert Subscriber Data answer为例。
204、 MME获取 M2M设备对应的默认 7 载标识 ( default bearer identity )或 者专用承载标识（ dedicated bearer identity ) 以及 S-GW标识， 以便后续通过承 载修改请求（ Modify Bearer Request )或者承载创建请求（ Create Bearer Request ) 等将 UE application trigger request发送给 S-GW, 使得 S-GW可通过用户面承载 将其发送给 M2M设备。
205、 MME向 S-GW发送 Modify Bearer Request或 Create Bearer Request; 其中， MME向 S-GW发送的 Modify Bearer Request或 Create Bearer Request 携带有 UE application trigger request,并且其中还携带 default bearer identity或者 dedicated bearer identity。
在实际应用中, UE application trigger request例如可携带在 Create Bearer Request或 Modify Bearer Request中的协议配置选项字段 ( Protocol Configuration Option ) 中， 当然亦可能携带在其它字段中。
其中， 图 2中以 MME向 S-GW发送 Modify Bearer Request为例。
206、 S-GW接收到 Modify Bearer Request或 Create Bearer Request后， 确定 出需通过对应的默认承载（ default bearer )或者专用承载（ dedicated bearer )将 该 UE application trigger request发送给 M2M设备。
可以理解， 此处 MME发送该承载修改请求或承载创建请求的作用并非一 定是指示 S-GW修改承载或创建承载，因此 S-GW接收到该承载修改请求或承载 创建请求后，可从中获得 UE application trigger request, 而可并不执行修改承载 或创建承载的操作。 S-GW向 MME发送 Modify Bearer Response (承载修改响应） 或者 Create Bearer Response ( 载创建响应 );
其中， 图 2中以 S-GW向 MME发送 Modify Bearer Response为例。
Data中携带 UE application trigger request;
208、 M2M设备向 Application Server建立通信通道， Application Server和 M2M设备进行数据交互；
209、 M2M设备和 Application Server发起通信后， MME可删除其保存的 UE application trigger request, 可向 HSS发送通知请求 ( Notify Request ), 该 Notify Request中可携带 ACK of UE application trigger request, 指示该 UE application trigger request已经成功发送至 M2M设备；
210、 HSS向 MME发送通知应答响应 （Notify Answer ), 并可删除其存储 的该 UE application trigger request。
由上可见， 本实施例中由于 MME是在接收到 HSS发送的 UE application trigger request后，通过主动始发的控制面请求向网关网元下发该 UE application trigger request , 该网关网元通过用户面数据包向对应的设备下发该 UE application trigger request, 该机制提高了网络下发 UE application trigger request 的主动性和实时性， 进而有利于设备更及时有效的和应用服务器交互数据。 为便于更好的理解和实施本发明实施例的上述技术方案， 下面以在 LTE系 统中触发 M2M设备的另一种应用场景为例进行说明， 而触发 H2H设备的应用 场景可以此类推。
参见图 3、 具体步骤可以包括：
301、 Application Server向 HSS发送 UE application trigger request;
在实际应用中 , Application Server可直接将 UE application trigger request发 送给 HSS， 或者， 亦可将该 UE application trigger request携带在某条消息中发送 给 HSS。 其中， 该 UE application trigger request可携带有需要触发的 M2M设备 的设备标识。
匕夕卜 , Application Server还可在向 HSS发送 UE application trigger request^ 同时， 向 HSS发送高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
302、 HSS接收并存者该 UE application trigger request;
HSS向 MME发送该 UE application trigger request;
在实际应用中， HSS例如可将该 UE application trigger request携带在***签 约数据请求 ( Insert Subscriber Data Request )或者 Cancel Location请求或者其它 消息中发送给 MME。 其中， 图 3中以 HSS将该 UE application trigger request携带 在 Insert Subscriber Data Request中发送给 MME为例。
此外， HSS还可在向 MME发送的携带该 UE application trigger request的消 息中进一步携带高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
303、 MME ：来自 HSS的 UE application trigger request;
其中， MME例如可接收来自 HSS的携带有 UE application trigger request的 Insert Subscriber Data Request或 Cancel Location请求或其它消息，并从中获取到 来自 HSS的 UE application trigger request。
MME可向 HSS发送***签约数据响应 （Insert Subscriber Data answer )或 者 Cancel Location ACK响应或其它对应的响应， 其中， 图 3中以 MME向 HSS发 送 Insert Subscriber Data answer为例。
304、 MME根据高优先级处理指示可确定需出主动向 M2M设备发送寻呼 ( Paging )请求 , 且在该 Paging请求中携带 UE application trigger request。
其中，该 UE application trigger request例如可以携带在该 Paging请求的非关 键扩展字段 ( non Critical Extension )或其它字段。
可以理解， 图 3中是以 MME通过 Paging请求主动向 M2M设备下发 UE application trigger request为例的， 当然 MME亦可通过去附着 ( Detach )请求或 其它控制面请求， 来主动向 M2M设备下发 UE application trigger request。 若 MME亦可通过 Detach请求消息来主动向 M2M设备下发 UE application trigger request, 则 M2M设备需向 MME返回 Detach Reject响应。 此处， MME发送该 Detach请求的作用并非是指示设备去附着，因此 M2M设备接收到该 Detach请求 后可从中获得 UE application trigger request , 而并不执行去 P付着。
305、 M2M设备向 Application Server建立通信通道， Application Server和 M2M设备进行数据交互；
306、 M2M设备和 Application Server发起通信后， MME可删除其保存的 UE application trigger request, 可向 HSS发送通知请求 ( Notify Request ), 该 Notify Request中可携带 ACK of UE application trigger request, 指示该 UE application trigger request已经成功发送至 M2M设备；
307、 HSS向 MME发送通知应答响应 （ Notify Answer );
308、 MME向 HSS发送清除设备（Purge UE )请求， 该 Purge UE请求中携 带删除 UE application trigger request的指示；
309、 HSS删除其存储的该 UE application trigger request , 并可向 MME发送 删除设备确认响应 （ Purge UE ACK )。
由上可见， 本实施例中由于 MME是在接收到 UE application trigger request 后，通过主动始发的控制面请求向设备下发该 UE application trigger request,该 机制提高了网络下发 UE application trigger request的主动性和实时性，进而有利 于设备更及时有效的和 Application Server交互数据。 为便于更好的理解和实施本发明实施例的上述技术方案， 下面以在 LTE系 统中触发 M2M设备的又一种应用场景为例进行说明， 触发 H2H设备的应用场 景可以此类推。
参见图 4, 具体步骤可以包括：
401、 Application Server向 HSS发送 UE application trigger request;
在实际应用中 , Application Server可直接将 UE application trigger request发 送给 HSS， 或者， 亦可将该 UE application trigger request携带在某条消息中发送 给 HSS。 其中， 该 UE application trigger request可携带有需要触发的 M2M设备 的设备标识。
匕夕卜 , Application Server还可在向 HSS发送 UE application trigger request^ 同时， 向 HSS发送高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。 402、 HSS接收并存储该 UE application trigger request;
HSS向 MME发送该 UE application trigger request;
在实际应用中， HSS例如可将该 UE application trigger request携带在***签 约数据请求 ( Insert Subscriber Data Request )或者 Cancel Location请求或者其它 消息中发送给 MME。 其中， 图 4中以 HSS将该 UE application trigger request携带 在 Insert Subscriber Data Request中发送给 MME为例。
此外， HSS还可在向 MME发送的携带该 UE application trigger request的请 求或消息中进一步携带高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
403、 MME ：来自 HSS的 UE application trigger request;
其中， MME例如可接收来自 HSS的携带有 UE application trigger request的 Insert Subscriber Data Request或 Cancel Location请求或其它消息，并从中获取到 来自 HSS的 UE application trigger request。
MME可向 HSS发送***签约数据响应 （Insert Subscriber Data answer )或 者 Cancel Location ACK响应或其它对应的响应， 其中， 图 4中以 MME向 HSS发 送 Insert Subscriber Data answer为例。
404、 MME可根据 UE application trigger request及高优先级处理指示确定出 需要向 eNodeB发送演进的无线接入承载建立请求（ E-RAB Setup Request ), 从 而使得在建立无线资源链路的同时， 完成向设备下发 UE application trigger request
可以理解， 图 4中是以 MME通过 E-RAB Setup Request主动向 eNodeB下发 UE application trigger request为例的， 当然 MME亦可通过演进的无线接入 7 载 修改请求（ E-RAB Modify Request )或者无线接入承载释放请求（ E-RAB Release Request ) 或其它控制面请求， 来主动向 eNodeB下发 UE application trigger request。
其中 , 该 UE application trigger request例如可以在 E-RAB Setup Request或 E-RAB Modify Request或 E-RAB Release Request的增强的分组***-协议数据 单元（EPS-PDU )或其它字段。 405、 eNodeB向 M2M设备发送无线连接重配置（RRC, Radio Connection Reconfiguration )请求, 该 RRC请求中携带 UE application trigger request。
其中，该 UE application trigger request例如可以在 RRC请求的将来关键扩展 字段 ( critical Extensions Future )或其它字段。
M2M设备接收该 RRC请求， 并建立 RRC链路， 在建立 RRC后， M2M设备 可向 eNodeB返回相应的响应。
406、 eNodeB向 MME返回演进的无线接入承载建立响应 （ S1-AP:E-RAB Setup Response );
407、 M2M设备和 Application Server建立通信通道, Application Server和 M2M设备进行数据交互；
其中， 由于 M2M设备已经和 eNodeB已建立无线资源链路。 此时， M2M设 备和 Application Server之间只需建立其它段的通信通道。
408、 M2M设备和 Application Server进行通信后， MME可删除其保存的 UE application trigger request, 可向 HSS发送通知请求 ( Notify Request ), 该 Notify Request中可携带 ACK of UE application trigger request, 指示该 UE application trigger request已经成功发送至 M2M设备；
409、 HSS向 MME发送通知应答响应 （Notify Answer ), 并可删除其存储 的该 UE application trigger request。
由上可见， 本实施例中由于 MME是在接收到 HSS发送的 UE application trigger request后，通过主动始发的控制面请求向接入网元下发该 UE application trigger request , 该接入网元通过用户面数据包向对应的设备下发该 UE application trigger request, 该机制提高了网络下发 UE application trigger request 的主动性和实时性， 进而有利于设备更及时有效的和应用服务器交互数据。 为便于更好的理解和实施本发明实施例的上述技术方案， 下面以在 LTE系 统中触发 M2M设备失败的一种应用场景为例进行说明， 而触发 H2H设备失败 的应用场景可以此类推。
参见图 5、 具体步骤可以包括：
501 ~ 502、 M2M设备完成 Detach; 503、 Application Server向 HSS发送 UE application trigger request; 在实际应用中 , Application Server可直接将 UE application trigger request发 送给 HSS， 或者， 亦可将该 UE application trigger request携带在某条消息中发送 给 HSS。 其中， 该 UE application trigger request可携带有需要触发的 M2M设备 的设备标识。
匕夕卜 , Application Server还可在向 HSS发送 UE application trigger request^ 同时， 向 HSS发送高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
504、 HSS接收并存储该 UE application trigger request;
HSS向 MME发送该 UE application trigger request;
在实际应用中， HSS例如可将该 UE application trigger request携带在***签 约数据请求 ( Insert Subscriber Data Request )或者 Cancel Location请求或者其它 消息中发送给 MME。 其中， 图 5中以 HSS将该 UE application trigger request携带 在 Insert Subscriber Data Request中发送给 MME为例。
此外， HSS还可在向 MME发送的携带该 UE application trigger request的消 息中进一步携带高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
505、 MME判断得出该 M2M设备已经 Detach;
MME向 HSS返回 Insert Subscriber Data Answer响应， 响应中携带触发失败 的指示信息， 还可携带触发失败的原因， 如该 Μ2Μ设备失败已经 Detach等。
506、 HSS根据接收到 Insert Subscriber Data Answer响应， 删除其存储的 UE application trigger request;
HSS向 Application Server发送 Notification请求，该 Notification请求中可携带 触发 M2M设备失败的指示， 还可携带触发失败的原因， 如该 M2M设备失败已 经 Detach等。
由上可见， 本实施例中由于 MME是在接收到 HSS发送的 UE application trigger request后， 若判断得出该 Μ2Μ设备已经 Detach , 则指示 HSS删除存储的 UE application trigger request, HSS向 Application Server指示触发失败， 该机制 提高了 Application Server获知触发结果的主动性和实时性。 为便于更好的理解和实施本发明实施例的上述技术方案， 下面以在 LTE系 统中触发 M2M设备失败的另一种应用场景为例进行说明， 而触发 H2H设备失 败的应用场景可以此类推。
参见图 6、 具体步骤可以包括：
601 ~ 602、 M2M设备完成 Detach;
603、 Application Server向 HSS发送 UE application trigger request;
在实际应用中 , Application Server可直接将 UE application trigger request发 送给 HSS， 或者， 亦可将该 UE application trigger request携带在某条消息中发送 给 HSS。 其中， 该 UE application trigger request可携带有需要触发的 M2M设备 的设备标识。
匕夕卜 , Application Server还可在向 HSS发送 UE application trigger request^ 同时， 向 HSS发送高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
604、 HSS接收并存储该 UE application trigger request;
HSS向 MME发送该 UE application trigger request;
在实际应用中， HSS例如可将该 UE application trigger request携带在***签 约数据请求 ( Insert Subscriber Data Request )或者 Cancel Location请求或其它请 求或消息中发送给 MME。 其中， 图 6中以 HSS将该 UE application trigger request 携带在 Insert Subscriber Data Request中发送给 MME为例。
此外， HSS还可在向 MME发送的携带该 UE application trigger request的消 息中进一步携带高优先级处理指示， 以指示接收到该 UE application trigger request的设备及时处理该 UE application trigger request。
605、 MME判断得出该 M2M设备已经 Detach;
MME向 HSS返回 Insert Subscriber Data Answer响应， 响应中携带触发失败 的指示信息， 还可携带触发失败的原因， 如该 Μ2Μ设备失败已经 Detach等。
606、 MME向 HSS发送清除设备（Purge UE )请求， 该 Purge UE请求中携 带删除 UE application trigger request的指示； 607、 HSS删除其存储的该 UE application trigger request , 并可向 ΜΜΕ发送 删除设备确认响应 （ Purge UE ACK )。
608、 HSS向 Application Server发送 Notification请求， 该 Notification请求中 可携带触发 M2M设备失败的指示， 还可携带触发失败的原因， 如该 M2M设备 失败已经 Detach等。
由上可见， 本实施例中由于 MME是在接收到 HSS发送的 UE application trigger request后， 若判断得出该 Μ2Μ设备已经 Detach , 则指示 HSS删除存储的 UE application trigger request, HSS向 Application Server指示触发失败， 该机制 提高了 Application Server获知触发结果的主动性和实时性。
需要说明的是， 对于前述的各方法实施例， 为了筒单描述， 故将其都表述 为一系列的动作组合， 但是本领域技术人员应该知悉， 本发明并不受所描述 的动作顺序的限制， 因为依据本发明， 某些步骤可以采用其他顺序或者同 时进行。 其次， 本领域技术人员也应该知悉， 说明书中所描述的实施例均 属于优选实施例， 所涉及的动作和模块并不一定是本发明所必须的。
为便于更好的实施本发明实施例的技术方案，下面还提供用于实施上述方 法实施例的相关设备。 参见图 7-a、 图 7-b、 图 7-c、 本发明实施例提供的移动性管理网元 700, 可 包括： 接收模块 710和第一发送模块 720, 或者包括接收模块 710和第二发送模 块 730, 或者包括接收模块 710和第三发送模块 740。
其中， 接收模块 710, 用于接收设备应用触发请求；
第一发送模块 720, 用于向接入网元发送携带所述设备应用触发请求的请 求以使接入网元触发设备 (如 H2H设备或 M2M设备）。
第二发送模块 730, 用于向网关网元发送携带所述设备应用触发请求的请 求以使网关网元触发设备 (如 H2H设备或 M2M设备）。
第三发送模块 740, 用于向设备发送携带该设备应用触发请求的请求以触 发该设备 (如 H2H设备或 M2M设备）。
在一种应用场景下， 第三发送模块 740具体用于， 向设备发送携带所述设 备应用触发请求的寻呼请求以触发该设备； 或者， 向设备发送携带所述设备应 用触发请求的去附着请求以触发该设备。
举例来说， 第三发送模块 740可将 UE application trigger request携带在寻呼 请求的非关键扩展字段或其它字段，而设备可对应的从该寻呼请求的非关键扩 展字段或其它字段获得该 UE application trigger request , 该设备可据此和 Application Server进行数据交互。
在一种应用场景下， 第一发送模块 720具体用于， 向接入网元发送携带所 述设备应用触发请求的无线接入承载建立请求以使接入网元触发设备； 或者， 向接入网元发送携带所述设备应用触发请求的无线接入承载修改请求以使接 入网元触发设备； 或者， 向接入网元发送携带所述设备应用触发请求的无线接 入 7 载释放请求以使接入网元触发设备。
举例来说， 第一发送模块 720可将接收到的 UE application trigger request携 带在无线接入承载建立请求、或者无线接入承载修改请求或者无线接入承载释 放请求的演进分组***-协议数据单元（EPS-PDU )或其它字段， 而接入网元 接收到该无线接入承载建立请求、或者无线接入承载修改请求、或者无线接入 承载释放请求后， 可从该消息的演进分组***-协议数据单元（EPS-PDU )或 其它字段获得该 UE application trigger request 0
在一种应用场景下， 第二发送模块 730具体用于， 向网关网元发送携带所 述设备应用触发请求的承载修改请求以使网关网元触发设备； 或者， 向网关网 元发送携带所述设备应用触发请求的承载创建请求以使网关网元触发设备。
举例来说， 第二发送模块 730可将 UE application trigger request携带在承载 修改请求或承载创建请求的协议配置选项字段或其它字段，而网关网元接收到 该承载修改请求或承载创建请求后，可从该请求消息的协议配置选项字段或其 它字段获得该 UE application trigger request。
可以理解的是， 本实施例移动性管理网元 700可如上述方法实施例中的移 动性管理网元（如 MME ), 其各个功能模块的功能可以根据上述方法实施例中 不再赘述。
由上可见， 本实施例中移动性管理网元 700是在接收到设备应用触发请求 后， 通过主动始发的控制面请求向设备下发该设备应用触发请求以触发该设 备，或者通过主动始发的控制面请求向接入网元或网关网元下发该设备应用触 发请求，以使得该接入网元或网关网元能够向对应的设备下发该设备应用触发 请求以触发该设备，该机制提高了网络下发设备应用触发请求的主动性和实时 性， 进而有利于更及时有效的触发 Μ2Μ设备或 Η2Η设备等设备和应用服务器 交互数据。 参见图 8、 本发明实施例提供的网关网元 800, 可包括： 第二接收模块 810 和第四发送模块 820。
其中， 第二接收模块 810, 用于接收来自移动性管理网元的携带设备应用 触发请求的请求；
第四发送模块 820, 用于向设备发送携带所述设备应用触发请求的数据包 (如下行链路数据包） 以触发该设备。
可以理解的是， 本实施例中的网关网元 800可如上述方法实施例中的网关 网元（如 eNodeB ), 其各个功能模块的功能可以根据上述方法实施例中的方法 述。
由上可见， 本实施例移动性管理网元是在接收到设备应用触发请求后，通 过主动始发的控制面请求向网关网元 800下发该设备应用触发请求， 网关网元 800向对应的设备下发该设备应用触发请求以触发该设备， 该机制提高了网络 下发设备应用触发请求的主动性和实时性， 进而有利于更及时有效的触发 M2M设备或 H2H设备等设备和应用服务器交互数据。 本发明实施例还一种通信***， 包括：
移动性管理网元 700或网关网元 800。 参见图 9, 本发明实施例提供的另一种通信***， 包括： 移动性管理网元 910和网关网元 920。
移动性管理网元 910, 用于接收设备应用触发请求； 向网关网元 920发送携 带所述设备应用触发请求的请求。 网关网元 920,用于接收来自移动性管理网元 910的携带设备应用触发请求 的请求； 向设备发送携带该设备应用触发请求的数据包以触发该设备。
可以理解的是， 本实施例移动性管理网元 910可如移动性管理网元 700, 网 关网元 920可如网关网元 800 ,移动性管理网元 910和网关网元 920的功能可以根 据上述方法实施例中的方法具体实现，其具体实现过程可以参照上述方法实施 例的相关描述， 此处不再赘述。
在上述实施例中， 对各个实施例的描述都各有侧重， 某个实施例中没 有详述的部分， 可以参见其他实施例的相关描述。
综上， 本发明实施例的移动性管理网元在接收到设备应用触发请求后， 由 于是通过主动始发的控制面请求向设备下发该设备应用触发请求以触发该设 备， 或者， 通过主动始发的控制面请求向接入网元或网关网元下发该设备应用 触发请求，使得该接入网元或网关网元能够向对应的设备下发该设备应用触发 请求以触发该设备，该机制相对提高了网络下发设备应用触发请求的主动性和 实时性， 进而有利于更及时有效的触发 M2M设备或 H2H设备等设备和应用 服务器交互数据。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步 骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读 存储介质中， 存储介质可以包括： 只读存储器、 随机存储器、 磁盘或光盘等。
以上对本发明实施例所提供的设备触发方法及网元设备进行了详细介绍， 说明只是用于帮助理解本发明的方法及其核心思想； 同时，对于本领域的一般 技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处， 综上， 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种设备触发方法， 其特征在于， 包括：
移动性管理网元接收设备应用触发请求；
向接入网元发送携带所述设备应用触发请求的请求以使所述接 入网元触发设备；
或者，
向网关网元发送携带所述设备应用触发请求的请求以使所述网 关网元触发设备。
2、 根据权利要求 1所述的方法， 其特征在于， 所述向接入网元发 送携带所述设备应用触发请求的请求以使所述接入网元触发设备，包 括：
向所述接入网元发送携带所述设备应用触发请求的无线接入承 载建立请求以使所述接入网元触发设备；
或者，
向所述接入网元发送携带所述设备应用触发请求的无线接入承 载修改请求以使所述接入网元触发设备；
或者，
向所述接入网元发送携带所述设备应用触发请求的无线接入承 载释放请求以使所述接入网元触发设备。
3、 根据权利要求 2所述的方法， 其特征在于， 所述设备应用触发 请求携带在所述无线接入承载建立请求或无线接入承载修改请求或 无线接入承载释放请求的演进分组***-协议数据单元 EPS-PDIL
4、 根据权利要求 1所述的方法， 其特征在于， 所述向网关网元发 送携带所述设备应用触发请求的请求以使所述网关网元触发设备，包 括：
向所述网关网元发送携带所述设备应用触发请求的承载修改请 求以使所述网关网元触发设备； 或者，
向所述网关网元发送携带所述设备应用触发请求的承载创建请 求以使所述网关网元触发设备。
5、 根据权利要求 4所述的方法， 其特征在于， 所述设备应用触发 请求携带在所述承载修改请求或承载创建请求的协议配置选项字段。
6、 根据权利要求 1至 5任一项所述的方法， 其特征在于， 所述设备应用触发请求中包含有设备标识；
所述接收设备应用触发请求之后， 还包括：
判断所述设备标识对应的设备是否已去附着；
若否，则执行向所述接入网元发送携带所述设备应用触发请求的 请求以使所述接入网元触发设备的步骤； 或者， 执行向所述网关网元 发送携带所述设备应用触发请求的请求以使所述网关网元触发设备 的步骤；
若是， 则向归属位置服务器发送指示设备触发失败的消息。
7、 一种设备触发方法， 其特征在于， 包括：
网关网元接收来自移动性管理网元的携带设备应用触发请求的 请求；
向设备发送携带所述设备应用触发请求的数据包以触发所述设 备。
8、 一种移动性管理网元， 其特征在于， 包括：
接收模块， 用于接收设备应用触发请求；
第一发送模块，用于向接入网元发送携带所述设备应用触发请求 的请求以使所述接入网元触发设备；
或者，
第二发送模块，用于向网关网元发送携带所述设备应用触发请求 的请求以使所述网关网元触发设备。
9、 根据权利要求 8所述的移动性管理网元， 其特征在于， 所述第一发送模块包括以下至少一种模块： 第一发送子模块，用于向所述接入网元发送携带所述设备应用触 发请求的无线接入承载建立请求以使所述接入网元触发设备；
第二发送子模块，用于向所述接入网元发送携带所述设备应用触 发请求的无线接入承载修改请求以使所述接入网元触发设备；
第三发送子模块，用于向所述接入网元发送携带所述设备应用触 发请求的无线接入承载释放请求以使所述接入网元触发设备；
所述第二发送模块包括以下至少一种模块：
第三发送子模块，用于向所述网关网元发送携带所述设备应用触 发请求的承载修改请求以使所述网关网元触发设备；
第四发送子模块，用于向所述网关网元发送携带所述设备应用触 发请求的承载创建请求以使所述网关网元触发设备。
10、 一种网关网元， 其特征在于， 包括：
接收模块，用于接收来自移动性管理网元的携带设备应用触发请 求的请求；
发送模块，用于向设备发送携带所述设备应用触发请求的数据包 以触发所述设备。
PCT/CN2012/075334 2011-05-13 2012-05-11 设备触发方法及网元设备 WO2012155808A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP12786602.8A EP2699041B1 (en) 2011-05-13 2012-05-11 Equipment triggering method and network element equipment
US14/077,415 US20140071945A1 (en) 2011-05-13 2013-11-12 Device Triggering Method and Network Element Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110123607.5 2011-05-13
CN201110123607.5A CN102781068B (zh) 2011-05-13 2011-05-13 设备触发方法及网元设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/077,415 Continuation US20140071945A1 (en) 2011-05-13 2013-11-12 Device Triggering Method and Network Element Device

Publications (1)

Publication Number Publication Date
WO2012155808A1 true WO2012155808A1 (zh) 2012-11-22

Family

ID=47125783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/075334 WO2012155808A1 (zh) 2011-05-13 2012-05-11 设备触发方法及网元设备

Country Status (4)

Country Link
US (1) US20140071945A1 (zh)
EP (1) EP2699041B1 (zh)
CN (1) CN102781068B (zh)
WO (1) WO2012155808A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10638526B2 (en) * 2012-09-24 2020-04-28 Qualcomm Incorporated Transport of control protocol for trusted WLAN (TWAN) offload
CN104796922B (zh) * 2014-01-22 2019-07-09 中兴通讯股份有限公司 Cse的触发管理方法及装置、cse、承载网网元
GB2530552B (en) * 2014-09-26 2018-07-25 Telit Tech Cyprus Ltd System and method of controlling operation of connected devices
WO2017210941A1 (zh) * 2016-06-08 2017-12-14 华为技术有限公司 一种建立用户面承载的方法、装置及***
WO2022061659A1 (en) * 2020-09-24 2022-03-31 Telefonaktiebolaget Lm Ericsson (Publ) METHODS, ENTITIES, AND COMPUTER READABLE MEDIA FOR RELEASING SGs ASSOCIATION BETWEEN MME AND MSC

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1780474A (zh) * 2004-11-19 2006-05-31 ***通信集团公司 按用户漫游状态推送业务参数信息的方法
CN101959133A (zh) * 2009-07-15 2011-01-26 华为技术有限公司 M2m用户设备的操作控制方法、***和m2m用户设备
CN102045897A (zh) * 2009-10-10 2011-05-04 中兴通讯股份有限公司 群组标识上报方法及装置
CN102056265A (zh) * 2009-11-10 2011-05-11 中兴通讯股份有限公司 限制mtc设备接入和通信的方法、移动管理单元及网关单元

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080123660A1 (en) * 2006-08-09 2008-05-29 Interdigital Technology Corporation Method and apparatus for providing differentiated quality of service for packets in a particular flow
EP2213119B1 (en) * 2007-11-16 2014-01-08 Nokia Solutions and Networks Oy Mapping quality of service for intersystem handover
CN101945368A (zh) * 2009-07-06 2011-01-12 华为技术有限公司 群组计费方法、计费处理装置以及通信***
CN102036219B (zh) * 2009-09-30 2016-08-03 中兴通讯股份有限公司 本地连接信息的发送方法及装置
WO2011098150A1 (en) * 2010-02-15 2011-08-18 Telefonaktiebolaget L M Ericsson (Publ) Machine-to-machine device triggering using session initiation protocol uniform resourse identifier
EP2369890A1 (en) * 2010-03-26 2011-09-28 Panasonic Corporation Connection peak avoidance for machine-type-communication (MTC) devices
US8861535B2 (en) * 2010-05-21 2014-10-14 Cisco Technology, Inc. Multi-tiered paging support using paging priority

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1780474A (zh) * 2004-11-19 2006-05-31 ***通信集团公司 按用户漫游状态推送业务参数信息的方法
CN101959133A (zh) * 2009-07-15 2011-01-26 华为技术有限公司 M2m用户设备的操作控制方法、***和m2m用户设备
CN102045897A (zh) * 2009-10-10 2011-05-04 中兴通讯股份有限公司 群组标识上报方法及装置
CN102056265A (zh) * 2009-11-10 2011-05-11 中兴通讯股份有限公司 限制mtc设备接入和通信的方法、移动管理单元及网关单元

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN102781068A (zh) 2012-11-14
US20140071945A1 (en) 2014-03-13
EP2699041A4 (en) 2015-07-01
CN102781068B (zh) 2015-02-25
EP2699041A1 (en) 2014-02-19
EP2699041B1 (en) 2018-08-01

Similar Documents

Publication Publication Date Title
US11218904B2 (en) Method for applying reflective quality of service in wireless communication system, and device therefor
JP6972023B2 (ja) 無線通信システムの端末の方法、無線通信システムの基地局の方法、端末、及び基地局
CN110583095B (zh) 默认服务质量规则管理方法及用户设备
US20200252900A1 (en) Method for performing service request procedure and apparatus therefor in wireless communication system
JP7139382B2 (ja) 無線通信方法及びデバイス
JP7287431B2 (ja) ユーザ装置、通信装置、及び通信方法
US20230164537A1 (en) Reliable data delivery over non-access stratum
KR102048046B1 (ko) 무선 통신 시스템에서 ladn 이용 방법 및 이를 위한 장치
US20190028337A1 (en) Method for setting configuration of non-ip data delivery (nidd) in wireless communication system and device for same
WO2020103823A1 (en) Handling of mapped eps bearer context for invalid qos flow
WO2020173137A1 (zh) 一种数据传输方法、相关设备、程序产品以及存储介质
US20190132782A1 (en) Method and device for providing circuit switching service in wireless communication system
TWI792415B (zh) Ue和網路之間的多存取pdu會話狀態同步
WO2011109938A1 (zh) 无线接入网元信息上报方法、设备和***
WO2018137152A1 (zh) 短消息传输方法、设备和***
US20190349742A1 (en) Method and apparatus for utilizing ladn in wireless communication system
AU2018329060A1 (en) Session establishment method and apparatus
WO2012155808A1 (zh) 设备触发方法及网元设备
WO2013097337A1 (zh) 一种网络拥塞控制方法及***
WO2012174962A1 (zh) 用户本地访问业务的处理方法、装置和***

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: 12786602

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012786602

Country of ref document: EP