WO2014067466A1 - 下行传输数据的方法和设备 - Google Patents

下行传输数据的方法和设备 Download PDF

Info

Publication number
WO2014067466A1
WO2014067466A1 PCT/CN2013/086261 CN2013086261W WO2014067466A1 WO 2014067466 A1 WO2014067466 A1 WO 2014067466A1 CN 2013086261 W CN2013086261 W CN 2013086261W WO 2014067466 A1 WO2014067466 A1 WO 2014067466A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
service node
information
mtc
iwf
Prior art date
Application number
PCT/CN2013/086261
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 EP13852149.7A priority Critical patent/EP2861000B1/en
Publication of WO2014067466A1 publication Critical patent/WO2014067466A1/zh
Priority to US14/586,095 priority patent/US9681257B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • 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]

Definitions

  • the present invention claims the priority of the Chinese Patent Application entitled “Method and Apparatus for Downstream Transmission of Data", which is filed on November 2, 2012, to the Chinese Patent Office, Application No. 201210433549. The entire contents are incorporated herein by reference.
  • the present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for downlink transmission of data. Background technique
  • M2M (Machine-to-Machine) Communication is a general term for a combination of technologies and technologies that apply various communication networks and information perception and processing to realize data communication and interaction between machines and machines, machines and people.
  • One communication scenario for M2M devices is small data transmission as defined by 3GPP. The small data indicates that the terminal UE (User Equipment) only transmits/receives a small amount of data.
  • a method for transmitting small data is defined, specifically between a generic NAS transport message between a UE and a serving node, and between a service node and an MTC gateway MTC-IWF (interoperable device for machine type communication)
  • the T5 interface, and the Tsp interface between the MTC-IWF and the server pass small data in the uplink or downlink direction.
  • the specific steps of the scheme for transmitting downlink small data are as follows:
  • the server sends a message carrying the small data in the downlink direction to the MTC_IWF through the Tsp interface.
  • the MTC-IWF After receiving the message sent by the server, the MTC-IWF queries the HLR (Home Locat Identifier)/HSS (Home Subscriber Server) to store the UE subscription data, and obtains the service node serving the UE. information.
  • HLR Home Locat Identifier
  • HSS Home Subscriber Server
  • the MTC-IWF sends a message carrying small data to the service node through the T5 interface between the service node and the service node.
  • the serving node sends a DOWNLINK_GENERIC_NAS_ TRANSPORT message to the UE, and the message carries small data that needs to be sent to the UE.
  • the MTC-IWF when the MTC-IWF sends small data to the UE, it needs to query the HLR/HSS to obtain the routing information of the UE. If the transmission frequency of the small data is relatively high, then it is frequent. In the scenario of sending downlink data, this will bring a lot of signaling load to the HLR/HSS. And if multiple such applications are running on the UE at the same time, multiple servers will continuously send small data to the UE frequently. If a large number of UEs are installed and used, the small data in the above solution is sent to the HLR/HSS. The signaling load caused by the query will be further increased, which may cause network congestion.
  • the present invention provides a method and an apparatus for downlink data transmission in order to solve the problem of frequent HLR/HSS query in downlink data transmission. The technical solution is as follows:
  • the first aspect provides a method for downlink data transmission, where the method includes: a machine type communication interoperation device MTC-IWF receives a first message sent by a server, where the first message includes a need to send to a user equipment. Downstream data; the MTC-IWF obtains the service node information of the user equipment that is stored locally, and sends a second message to the service node of the user equipment according to the service node information of the user equipment, where the second message includes And the downlink data that needs to be sent to the user equipment, so that the service node sends the downlink data to the user equipment.
  • MTC-IWF receives a first message sent by a server, where the first message includes a need to send to a user equipment. Downstream data; the MTC-IWF obtains the service node information of the user equipment that is stored locally, and sends a second message to the service node of the user equipment according to the service node information of the user equipment, where the second message includes And the downlink data that
  • the method before the MTC-IWF acquires the service node information of the user equipment that is stored locally, the method further includes: sending, by the MTC-IWF, the HLR/HSS to acquire the user a service node information of the device or a request for the subscription information; the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or the MTC-IWF receives the return of the HLR/HSS And signing the information response message, and saving the service node information of the user equipment carried in the subscription information response message.
  • the method includes: the MTC-IWF registering/subscribing/requesting the association between the user equipment and the service node of the user equipment, so that the HLR/HSS changes the service node of the user equipment.
  • the changed service node information of the user equipment can be returned.
  • the MTC-IWF initiates a request for acquiring the service node information or the subscription information of the user equipment to the HLR/HSS
  • the MTC-IWF sends a first create association/binding request to the service node of the user equipment, so that the service node of the user equipment returns a first create association/binding response; the MTC-IWF receiving station Determining, by the service node, a first create association/binding response, thereby establishing an association/binding relationship with the service node.
  • the method before the MTC-IWF obtains the service node information of the user equipment that is stored locally, the method further includes: sending, by the MTC-IWF, the serving node of the user equipment a second create association/binding request; the MTC-IWF sends a second create association/binding response to the service node to establish an association/binding relationship with the service node.
  • a second aspect provides a method for downlink data transmission, where the method includes: a machine type communication interoperation device MTC-IWF receives a first message delivered by a server, where the first message includes a need to send to a user equipment. Downstream data; the MTC-IWF acquires a channel between the local and the serving node of the user equipment, and sends a second message to the serving node of the user equipment by using the channel, where the second message includes the The downlink data that needs to be sent to the user equipment, so that the service node sends the downlink data to the user equipment.
  • the method before the acquiring, by the MTC-IWF, the channel between the local device and the serving node of the user equipment, the method further includes: the MTC-IWF to the home location/user register HLR/ The HSS sends a request for acquiring the service node information or the subscription information of the user equipment; the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or, the MTC-IWF receiving station
  • the subscription information response message returned by the HLR/HSS is stored, and the service node information of the user equipment carried in the subscription information response message is saved.
  • the MTC-IWF In a first possible implementation of the first possible implementation of the second aspect, the MTC-IWF
  • the method further includes: sending, by the MTC-IWF, a first creation session request to the service node of the user equipment, where the first creation session request is Carrying the address information of the MTC-IWF and the channel identifier of the MTC-IWF, so that the service node of the user equipment returns a first creation session response, and the first creation session response carries the service of the user equipment
  • the MTC-IWF receives the first created session response returned by the service node of the user equipment, thereby establishing a channel with the service node of the user equipment.
  • the method before the acquiring, by the MTC-IWF, the channel between the local device and the serving node of the user equipment, the method further includes: the MTC-IWF receiving the service node of the user equipment a second created session request, where the second created session request carries the address information of the serving node of the user equipment and the channel identifier of the serving node of the user equipment; the MTC-IWF is sent to the user equipment The service node returns a second create session response, and the second create session response carries the address information of the MTC-IWF and the channel identifier of the MTC-IWF, thereby establishing a channel with the service node of the user equipment.
  • the third aspect further provides a machine type communication interoperation device MTC-IWF, the device includes: a receiving module, configured to receive a first message sent by the server, where the first message includes a device that needs to be sent to the user equipment Downstream data;
  • a processing module configured to acquire service node information of the user equipment that is stored by the MTC-IWF, and send a second message to the service node of the user equipment according to the service node information of the user equipment, where the second message includes Determining downlink data that needs to be sent to the user equipment, so that the serving node sends the downlink data to the user equipment.
  • the device further includes: An obtaining module, configured to send, to the HLR/HSS, a request for acquiring the service node information or the subscription information of the user equipment, before the processing module acquires the service node information of the user equipment stored by the MTC-IWF; The service node information of the user equipment returned by the HLR/HSS is received; or, the subscription information response message returned by the HLR/HSS is received, and the service node information of the user equipment carried in the subscription information response message is saved.
  • An obtaining module configured to send, to the HLR/HSS, a request for acquiring the service node information or the subscription information of the user equipment, before the processing module acquires the service node information of the user equipment stored by the MTC-IWF; The service node information of the user equipment returned by the HLR/HSS is received; or, the subscription information response message returned by the HLR/HSS is received, and the service node information of the user equipment carried in the subscription information response message is saved.
  • the device further includes: a second registration/subscription module, configured to send, by the acquiring module, the user to the HLR/HSS After the service node information of the device or the request for the subscription information, registering/subscribing/requesting the association of the user equipment and the service node of the user equipment to the HLR/HSS, so that the HLR/HSS is aware of the user equipment
  • the service node information of the changed user equipment can be returned when the service node changes.
  • the device further includes: a first creating module, configured to initiate, by the acquiring module, the acquiring the user equipment to the HLR/HSS After the service node information or the request for the subscription information, the first creation association/binding request is sent to the service node of the user equipment, so that the service node of the user equipment returns a first creation association/binding response; receiving the service The first created association/binding response returned by the node, thereby establishing an association/binding relationship with the service node.
  • a first creating module configured to initiate, by the acquiring module, the acquiring the user equipment to the HLR/HSS After the service node information or the request for the subscription information, the first creation association/binding request is sent to the service node of the user equipment, so that the service node of the user equipment returns a first creation association/binding response; receiving the service The first created association/binding response returned by the node, thereby establishing an association/binding relationship with the service node.
  • the device further includes:
  • a second creating module configured to receive a second create association/binding request sent by the service node of the user equipment, before the processing module acquires service node information of the user equipment stored by the MTC-IWF;
  • the serving node sends a second create association/binding response to establish an association/binding relationship with the service node.
  • a machine type communication interoperating device MTC-IWF comprising:
  • a receiving module configured to receive a first message that is sent by the server, where the first message includes downlink data that needs to be sent to the user equipment;
  • a processing module configured to obtain a channel between the MTC-IWF and the service node of the user equipment, and send, by using the channel, a second message to the serving node of the user equipment, where the second message includes the need to send And sending, by the serving node, the downlink data to the user equipment.
  • the device further includes:
  • An obtaining module configured to send, to the HLR/HSS, a request for acquiring service node information or subscription information of the user equipment, before the processing module acquires a channel between the MTC-IWF and the serving node of the user equipment; Saving service node information of the user equipment returned by the HLR/HSS; or receiving the HLR/HSS return The subscription information response message, and the service node information of the user equipment carried in the subscription information response message is saved.
  • the device further includes: a first channel creating module, configured to initiate, by the acquiring module, the acquiring the user equipment to the HLR/HSS After the service node information or the request for the subscription information, the first creation session request is sent to the service node of the user equipment, where the first creation session request carries the address information of the MTC-IWF and the MTC-IWF Channel identifier, the service node of the user equipment is returned to the first creation session response, and the first creation session response carries the address information of the service node of the user equipment and the channel identifier of the service node of the user equipment; The first creation session response returned by the service node of the user equipment, thereby establishing a channel with the service node of the user equipment.
  • a first channel creating module configured to initiate, by the acquiring module, the acquiring the user equipment to the HLR/HSS After the service node information or the request for the subscription information, the first creation session request is sent to the service node of the user equipment, where the first creation session request carries
  • the device further includes:
  • a second channel creation module configured to receive a second create session request sent by the service node of the user equipment, before the processing module acquires a channel between the MTC-IWF and the service node of the user equipment, where the Transmitting, in the session request, the address information of the service node of the user equipment and the channel identifier of the service node of the user equipment; returning a second creation session response to the service node of the user equipment, where the second creation session response is And carrying the address information of the MTC-IWF and the channel identifier of the MTC-IWF, so as to establish a channel with the service node of the user equipment.
  • the MTC-IWF receives the first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment; Serving the node information, sending a second message to the serving node of the user equipment according to the service node information of the user equipment, or acquiring a channel between the local and the serving node of the user equipment, and using the channel to the user.
  • the serving node of the device sends a second message, so that the serving node sends the downlink data to the user equipment. Therefore, data can be transmitted to the service node without querying the HLR/HSS, which reduces the problem of frequent HLR/HSS query in downlink data transmission.
  • 1 is a flowchart of a method for downlink transmission of data according to an embodiment of the present invention
  • 2 is a flowchart of a method for downlink transmission data provided in an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for downlink transmission data provided in an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for downlink transmission data provided in an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for downlink transmission data according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for downlink transmission data provided in an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for downlink transmission data provided in an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of an MTC-IWF provided in an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of another MTC-IWF provided in an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of an MTC-IWF provided in an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another MTC-IWF provided in an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of an MTC-IWF provided in an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of another MTC-IWF provided in an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.
  • a method for downlink transmission of data is provided in this embodiment, where the method includes:
  • the MTC-IWF receives a first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment.
  • the MTC-IWF obtains the service node information of the user equipment that is stored locally, and sends a second message to the service node of the user equipment according to the service node information of the user equipment, where the second message includes Determining downlink data that needs to be sent to the user equipment, so that the serving node sends the downlink data to the user equipment.
  • the method further includes: sending, by the MTC-IWF, the service node information of the user equipment to the home location/user register HLR/HSS Or requesting the subscription information, and registering/subscribing/requesting the association between the user equipment and the service node of the user equipment to the HLR/HSS, so that the HLR/HSS changes the service node of the user equipment. And returning the changed service node information of the user equipment;
  • the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or, the MTC-IWF receives the subscription information response message returned by the HLR/HSS, and saves the subscription information.
  • the service node information of the user equipment carried in the response message.
  • the method further includes: sending, by the MTC-IWF, a request for acquiring the service node information or the subscription information of the user equipment to the HLR/HSS ;
  • the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or, the MTC-IWF receives the subscription information response message returned by the HLR/HSS, and saves the subscription information.
  • the service node information of the user equipment carried in the response message.
  • the method further includes:
  • the MTC-IWF registers/subscribes/requests the association of the user equipment and the service node of the user equipment to the HLR/HSS, so that the HLR/HSS can learn when the service node of the user equipment changes Returning the changed service node information of the user equipment.
  • the method further includes:
  • the MTC-IWF receives a first create association/binding response returned by the service node, thereby establishing an association/binding relationship with the service node.
  • the method further includes: receiving, by the MTC-IWF, a second creation association/binding request sent by the service node of the user equipment;
  • the MTC-IWF sends a second create association/binding response to the service node to establish an association/binding relationship with the service node.
  • the first message further includes indication information, where the indication information is: information indicating that the downlink data is small data or small data transmission, or indicating that the downlink data is frequent small data or frequent small data transmission.
  • the indication information confirms whether it is necessary to register/subscribe/request the service node information of the user equipment to the HLR/HSS, or to confirm whether an association/binding relationship needs to be established with the service node of the user equipment.
  • the MTC-IWF receives the first message sent by the server, where the first message includes the downlink data that needs to be sent to the user equipment, and the service node information of the user equipment is obtained locally, according to the The serving node information of the UE sends a second message to the serving node of the UE, so that the serving node sends the downlink data to the user equipment.
  • This allows data to be transferred to the service section without querying the HLR/HSS. Points, reducing the problem of frequent HLR/HSS queries in downlink data transmission.
  • a method for downlink transmission of data is provided, where the method includes:
  • the MTC-IWF receives a first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment.
  • the MTC-IWF obtains a channel between a local node and a service node of the user equipment, and sends a second message to the serving node of the user equipment by using the channel, where the second message includes the need to send And sending, by the serving node, the downlink data to the user equipment.
  • the method before the acquiring, by the MTC-IWF, the channel between the local device and the serving node of the user equipment, the method further includes:
  • the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or, the MTC-IWF receives the subscription information response message returned by the HLR/HSS, and saves the subscription information.
  • the service node information of the user equipment carried in the response message.
  • the MTC-IWF further includes:
  • the MTC-IWF sends a first create session request to the service node of the user equipment, where the first create session request carries the address information of the MTC-IWF and the channel identifier of the MTC-IWF, so that the The service node of the user equipment returns a first creation session response, where the first creation session response carries the address information of the service node of the user equipment and the channel identifier of the service node of the user equipment;
  • the MTC-IWF receives a first create session response returned by the service node of the user equipment, thereby establishing a channel with the service node of the user equipment.
  • the method before the acquiring, by the MTC-IWF, the channel between the local device and the serving node of the user equipment, the method further includes:
  • the MTC-IWF receives a second create session request sent by the service node of the user equipment, where the second create session request carries the address information of the service node of the user equipment and the channel of the service node of the user equipment.
  • the MTC-IWF returns a second create session response to the service node of the user equipment, where the second create session response carries the address information of the MTC-IWF and the channel identifier of the MTC-IWF, thereby
  • the service node of the user equipment establishes a channel.
  • the first message further includes indication information, where the first message further includes indication information, where the indication information is: information indicating that the downlink data is small data or small data transmission, or indicating the The downlink data is information of frequent small data or frequent small data transmission, or information indicating downlink small data after the downlink data, or information indicating that a channel is established, so that the MTC-IWF can confirm whether according to the indication information.
  • a channel needs to be established with the service node of the user equipment.
  • the MTC-IWF receives the first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment; and the channel between the local and the service node of the user equipment is obtained, And sending, by the channel, a second message to the serving node of the user equipment, so that the serving node sends the downlink data to the user equipment. Therefore, data can be transmitted to the service node without querying the HLR/HSS, which reduces the problem of frequent HLR/HSS query in downlink data transmission.
  • a method for downlink transmission of data is provided.
  • the MTC-IWF After receiving the small data sent by the service, the MTC-IWF registers/subscribes to the HLR/HSS, and registers/subscribes the association between the serving node of the UE and the UE, so that
  • the HLR/HSS notifies the MTC-IWF of the serving node information of the UE, and the MTC-IW saves or updates the UE serving node information, so that the downlink data transmission process In this case, it is no longer necessary to query the HLR/HSS for the service node information of the UE, thereby reducing the HLR/HSS signaling burden.
  • the relationship of the symbol "/" in the present embodiment and the following embodiment represents "or", which will not be further described in the following embodiments. Referring to Figure 3, the specific method flow includes:
  • the MTC-IWF receives the first message sent by the server.
  • the server includes an SCS (Service Capability Server) or an AS.
  • SCS Service Capability Server
  • AS Service Capability Server
  • Application Server application server
  • application server which is not specifically limited in this embodiment.
  • the first message sent by the server includes downlink data that needs to be sent to the UE, where the downlink data includes but is not limited to: downlink small data, application information, or device trigger information.
  • the first message may further carry an external identifier of the UE, which is used to query an internal identifier (IMSI) of the UE to identify the UE in the 3GPP network.
  • IMSI internal identifier
  • the first message further includes indication information, where the indication information includes: information indicating that the downlink data is small data or small data transmission, or indicating that the downlink data is frequent small data or frequent small data transmission.
  • the indication information confirms whether it is necessary to register/subscribe to the service node information of the UE to the HLR/HSS, or to confirm whether it needs to be associated with the service node of the UE. Establish an association/binding relationship, or confirm whether a channel needs to be established with the serving node of the UE.
  • the service node of the UE may also send the indication to the MTC-IWF when the UE attaches, or the HLR/HSS may send the foregoing to the MTC-IWF, in addition to the foregoing indication that the server sends the first message to the MTC-IWF. If the MTC-IWF receives the small data sent by the server and queries the HLR/HSS, the HLR/HSS may send the indication to the MTC-IWF. Specifically, the MTC-IWF obtains the indication information, which is not specifically limited in this embodiment.
  • the MTC-IWF determines whether there is local service node information of the UE. If yes, step 304 is performed; otherwise, step 303 is performed.
  • the service node of the UE includes: SGSN (Serving GPRS Support Node) / MME (Mobi Le Management Entity), the service node information refers to routing information of the UE, or information of the service node, or the core network. Service node information.
  • SGSN Server GPRS Support Node
  • MME Mobility Management Entity
  • the MTC-IWF sends a request for acquiring the service node information or the subscription information of the UE and the registration/subscription/requesting association of the UE and the service node of the UE to the HLR/HSS, so that the HLR/HSS can learn when the service node of the UE changes. Returns the service node information of the changed UE.
  • the HLR/HSS needs to first query the serving node information of the UE.
  • the method for querying the service node information of the UE to the HLR/HSS includes: the MTC-IWF sends a request for acquiring the service node information or the subscription information of the UE to the HLR/HSS, and receives and saves the returned by the HLR/HSS The service node information of the user equipment; or, the MTC-IWF receives the subscription information response message returned by the HLR/HSS, and saves the service node information of the user equipment carried in the subscription information response message.
  • the HLR/HSS may also register/subscribe/request the association of the user equipment and the service node of the user equipment, so that the HLR/HSS is aware of the UE.
  • the service node changes, the changed service node information of the UE can be returned.
  • registering/subscribing/requesting the association of the user equipment and the service node of the user equipment to the HLR/HSS so that the HLR/HSS is informed.
  • the serving node of the UE changes, the changed service node information of the UE can be returned.
  • the association between the user equipment and the service node of the user equipment refers to that the service node of the user equipment changes or the user equipment is served by another service node.
  • the HLR/HSS after the MTC-IWF registers with the HLR/HSS to register/subscribe/request the user equipment and the service node of the user equipment, when the serving node of the UE saved in the HLR/HSS changes, or the UE When attached, the HLR/HSS notifies the MTC-IWF of the service node information of the UE. For example, when the serving node of the UE changes during the location update RAU (Routing Area Update) / TAU (Tracking Area Update) of the UE, the new serving node acquires the context of the UE from the old serving node.
  • RAU Radio Area Update
  • TAU Tracking Area Update
  • the HLR/HSS sends a location update message to notify the current serving service node information of the UE; or when the UE attaches, the serving node of the UE also sends a location update message to the HLR/HSS, notifying the service service node information of the UE, HLR/HSS Knowing the change information of the service node sends the new service node information to the MTC_IWF.
  • the MTC-IWF acquires the service node information of the UE from the HLR/HSS
  • the external identifier of the UE is also carried in the query request, and the HLR/HSS is based on the UE.
  • the external identifier acquires the IMSI of the UE, and returns the IMSI and the service node information of the UE to the MTC_IWF.
  • this step is performed when the MTC-IWF receives the downlink data sent by the server to the UE for the first time. After the MTC-IWF has registered with the HLR/HSS, the MTC-IWF is not required to send the downlink to the UE every time. This step is performed when the data is used. This step is not required during the transmission of the downlink data.
  • the MTC-IWF acquires the serving node information of the UE, and sends a second message to the serving node of the UE according to the serving node information of the UE.
  • the MTC-IWF has already saved the service node information of the UE.
  • the MTC-IWF When receiving the downlink data, the MTC-IWF locally obtains the service node information of the UE.
  • the MTC-IWF may obtain the service node information of the UE according to the external identifier information of the UE carried in the first message.
  • the external identifier of the UE may be converted into an internal identifier, and the internal identifier of the UE is carried in the second message and sent to the serving node of the UE together with the downlink data.
  • the serving node of the UE sends the downlink data to the UE.
  • the serving node receives the downlink data sent by the MTC-IWF, and sends the downlink data to the UE, thereby completing the transmission of the downlink data. This step is similar to the prior art, and will not be further described in this embodiment.
  • the MTC-IWF can save/update the service node information of the UE, and when receiving the downlink small data sent to the UE next time, the message carrying the small data can be sent to the serving node of the UE, and No more queries to HLR/HSS.
  • a method for downlink transmission of data is provided.
  • the service node of the UE initiates an association/binding relationship between the service node and the MTC-IWF, and the established association/binding relationship is established.
  • the serving node and the MTC-IWF can learn each other's information, so that there is no need to query the HLR/HSS in the downlink data transmission.
  • the specific method flow includes:
  • the serving node of the UE sends an association/binding request to the MTC-IWF.
  • the scenario in which the serving node of the UE sends the association/binding request to the MTC-IWF includes: the serving node receives the attach message of the UE, or the uplink small data sent by the UE, or the frequent small data transmission on the UE.
  • the UE sends small data or frequent small data indication to the service node.
  • the serving node of the UE if the serving node of the UE does not establish an association/binding relationship with the MTC-IWF, the serving node of the UE sends the creation to the MTC-IWF. Association/binding request.
  • the method for obtaining the MTC-IWF information needs to be found before the serving node initiates the association/binding request to the MTC-IWF. Similar to the prior art, the method includes: the serving node of the UE interacts with the HLR/HSS, acquires the MTC-IWF information saved in the HLR/HSS, or the serving node of the UE obtains the MTC-IWF information from the indication of the UE, or the service of the UE. The node can also configure the MTC-IWF information locally. Which method is used to obtain the corresponding MTC-IWF is not specifically limited in this embodiment.
  • the service node of the UE and the HLR/HSS interaction may also obtain the identifier information of the UE, such as the IMSI of the UE and/or the external identifier of the UE, which is similar to the prior art, and this embodiment is no longer used in this embodiment. Narration.
  • the service node information is carried in the request message for creating the association/binding sent by the serving node of the UE, and may also carry the identifier information of the UE, for example, the IMS I of the UE and/or the external identifier of the UE, to identify the UE within the 3GPP network.
  • This embodiment is not specifically limited in this embodiment.
  • the scenario in which the serving node of another UE initiates an association/binding request to the MTC-IWF is:
  • the MTC-IWF sends a downlink small data notification to the serving node of the UE, and the serving node of the UE receives the MTC-IWF. After the notification is sent, an association/binding request is initiated.
  • the scenario in which the serving node of another UE initiates an association/binding request to the MTC-IWF is:
  • the MTC-IWF directly requests the serving node of the UE to initiate an association/binding request to establish an MTC-IWF and The association/binding relationship of the service node where the UE is located.
  • the MTC-IWF sends a create association/binding response to the serving node of the UE, so as to establish an association/binding relationship with the service node.
  • the response message carries the MTC-IWF information, so that the serving node of the UE associates/binds with the MTC-IWF according to the MTC-IWF information.
  • the MTC-IWF creates an association/binding relationship with the serving node of the UE
  • the serving node of the UE changes, for example, the service node may change during the location update RAU/TAU of the UE
  • the UE's new serving node acquires the context information of the UE from the old serving node of the UE.
  • the context information of the UE includes the association/binding information, that is, the information of the MTC-IWF, the old service node cancellation of the UE and the association/binding of the MTC-IWF, and the new service node of the UE sends the new service node information to the MTC-IWF.
  • the MTC-IWF the association/binding information
  • steps 401-402 are steps that need to be performed when the MTC-IWF has not established an association/binding relationship with the serving node of the UE, if the MTC-IWF has established association/binding with the serving node of the UE. For the relationship, steps 401-402 are not required to be performed during downlink data transmission.
  • the MTC-IW receives the first message sent by the server. This step is similar to the step 301 in the foregoing embodiment, and details are not described in this embodiment.
  • the MTC-IW locally obtains the serving node information of the UE, and sends a second message to the serving node of the UE according to the serving node information of the UE.
  • the MTC-IWF Since the MTC-IWF has established an association/binding relationship with the serving node of the UE, in the transmission of the downlink data, the MTC-IWF only needs to obtain the information of the serving node of the UE locally according to the external identifier of the UE, and does not need to Then check with HLR/HSS.
  • the external identifier of the UE may be converted into an internal identifier, and the internal identifier of the UE is carried in the second message and sent to the serving node of the UE together with the downlink data.
  • the serving node of the UE sends the downlink data to the UE.
  • This step is similar to step 305 in the above embodiment, and will not be further described in this embodiment.
  • the serving node of the UE may directly send the uplink data to the associated/bound MTC.
  • the transmission of the uplink data can also be transmitted according to the method of the prior art, which is not specifically limited in this embodiment.
  • the beneficial effects of this embodiment are: initiated by the serving node of the UE, establishing an association/binding relationship between the serving node of the UE and the MTC-IWF, and the service node and the MTC-IWF can be learned through the established association/binding relationship.
  • the information of each other so that there is no need to query the HLR/HSS in the downlink data transmission.
  • a method for transmitting data in the downlink is provided.
  • the MTC-IWF initiates an association/binding relationship between the serving node of the UE and the MTC-IWF, and the association/binding relationship is established.
  • the service node and the MTC-IWF can learn each other's information, so that there is no need to query the HLR/HSS in the downlink data transmission.
  • the specific method flow includes:
  • the MTC-IWF receives the first message sent by the server.
  • This step is similar to the step 301 in the foregoing embodiment, and details are not described in this embodiment.
  • the MTC-IWF determines whether there is local service node information of the UE, if yes, step 505 is performed, otherwise step 503 is performed.
  • the MTC-IWF sends a request for acquiring the service node information or the subscription information of the UE to the HLR/HSS.
  • the service node information of the UE needs to be acquired first from the HLR/HSS.
  • the specific acquisition method is similar to the acquisition method in step 303, and details are not described in this embodiment.
  • the MTC-IWF sends a create association/binding request to the serving node of the UE to establish with the serving node of the UE. Association/binding relationship.
  • the association/binding request is sent to the serving node of the UE, where the request message carries the MTC-IWF information, and may also carry the UE identification information;
  • the MTC-IWF After receiving the creation association/binding request sent by the MTC-IWF, the MTC-IWF returns an association/binding response, where the response message carries the service node information, and the MTC-IWF receives the creation association/tie returned by the service node. The response is determined to establish an association/binding relationship with the service node.
  • the MTC-IWF when the MTC-IWF sends the downlink data, if the MTC-IWF does not establish an association/binding relationship with the serving node of the UE, the MTC-IWF may initiate an association/binding request to the serving node of the UE, but this It is not the only trigger condition for the MTC-IWF to initiate the creation of an association/binding request. In other scenarios, the MTC-IWF may also be triggered to initiate the creation of an association/binding request.
  • the HLR/HSS After the HLR/HSS receives the location update message sent by the serving node of the new UE, the HLR/HSS notifies the MTC-IWF of the current serving node information of the UE, so that the MTC-IWF initiates association/binding to the new serving node of the UE. Or; when the UE is attached, the serving node of the UE sends a location update message to the HLR/HSS, and the HLR/HSS sends a message including the serving node information of the UE to the MTC-IWF, so that the MTC-IWF sends a new serving node to the UE. Initiate an association/binding request.
  • steps 503-504 are steps that need to be performed when the MTC-IWF and the serving node of the UE have not established an association/binding relationship. If the MTC-IWF has established an association/binding relationship with the serving node of the UE, Then, steps 503-504 need not be performed in the downlink data transmission.
  • the MTC-IWF obtains the serving node information of the UE, and sends a second message to the serving node of the UE according to the serving node information of the UE.
  • the serving node of the UE sends the downlink data to the UE.
  • the steps 505-506 are similar to the steps 404-405 in the foregoing embodiment, and are not further described in this embodiment.
  • the beneficial effects of this embodiment are: initiated by the MTC-IWF, establishing an association/binding relationship between the serving node of the UE and the MTC-IWF, and the service node and the MTC-IWF can learn from each other through the established association/binding relationship. The information so that there is no need to query the HLR/HSS in the downlink data transmission.
  • a method for downlink data transmission is provided, which is initiated by a serving node of a UE, and a channel is established between a serving node of the UE and an MTC-IWF, where the channel includes a user plane connection (or a user plane tunnel). Or control plane connection (or control plane tunnel), the UE's service node and the MTC-IWF transmit uplink/downlink data through the established channel. See Figure 6.
  • the specific method flow includes:
  • the serving node of the UE sends a create session request to the MTC-IWF.
  • the scenario in which the serving node of the UE sends a session creation request to the MTC-IWF includes: the service node receives The attach message of the UE, or the uplink small data sent by the UE, or the application of frequent small data transmission on the UE is turned on/on, and the UE sends small data or frequent small data indication to the service node.
  • the serving node of the UE does not establish a channel with the MTC-IWF, the serving node of the UE sends a create session request to the MTC-IWF.
  • the corresponding MTC-IWF needs to be found, and the method for acquiring the MTC-IWF information is similar to the prior art, including: The serving node and the HLR/HSS interact to obtain the MTC-IWF information stored in the HLR/HSS, or the serving node of the UE obtains the MTC-IWF information from the indication of the UE, or the serving node of the UE may also locally configure the MTC-IWF information. Which method is used to obtain the corresponding MTC-IWF is not specifically limited in this embodiment.
  • the service node of the UE and the HLR/HSS interaction may also obtain the identifier information of the UE, such as the IMSI of the UE and/or the external identifier of the UE, which is similar to the prior art, and this embodiment is no longer used in this embodiment. Narration.
  • the address and the channel identifier of the service node in the request message for creating a session sent by the serving node of the UE, where the user-side channel identifier or the control plane channel identifier may be used according to the created connection type, which is not used in this embodiment. Specifically limited.
  • the request message may further carry the identifier information of the UE, for example, the IMSI of the UE and/or the external identifier of the UE, to identify the UE in the 3GPP network, which is not specifically limited in this embodiment.
  • the channel identifier of the serving node of the UE may be a common channel identifier, or a channel identifier reserved for the small data transmission or specifically allocated, which is not specifically limited in this embodiment.
  • the scenario in which the service node of another UE initiates a session creation request to the MTC-IWF is:
  • the MTC-IWF sends a downlink small data notification to the serving node of the UE, and the serving node of the UE receives the notification sent by the MTC-IWF. After that, a create session request is initiated.
  • the scenario in which the serving node of another UE initiates a session creation request to the MTC-IWF is:
  • the MTC-IWF directly requests the serving node of the UE to initiate a create session request to establish a user of the MTC-IWF and the serving node where the UE is located. Face or control plane tunnel.
  • the MTC-IWF sends a create session response to the serving node of the UE, so as to establish a channel with the service node.
  • the response message carries the address information and the channel identifier of the MTC-IWF, and may be a user plane identifier or a control plane channel identifier according to the created type, so as to establish a channel with the serving node of the UE.
  • the channel identifier of the MTC-IWF may be a common channel identifier, or a channel identifier reserved for the small data transmission or specifically allocated, which is not specifically limited in this embodiment.
  • the MTC-IWF sends a session creation response to the serving node of the UE, and the process of establishing a channel with the service node is similar to the prior art, and is not described in this embodiment.
  • the new serving node of the UE acquires the context information of the UE from the old serving node of the UE.
  • the context information of the UE includes tunnel information, that is, address information and channel identification information of the MTC-IWF, the old service node of the UE is deactivated and the channel between the MTC-IWF, and the new service node of the UE sends a new one to the MTC-IWF.
  • steps 601-602 are steps that need to be performed when the MTC-IWF and the serving node of the UE have not established a channel. If the MTC-IWF and the serving node of the UE have established a channel, then during downlink data transmission. There is no need to perform steps 601-602.
  • the MTC-IW receives the first message sent by the server.
  • This step is similar to the step 301 in the foregoing embodiment, and details are not described in this embodiment.
  • the MTC-IW obtains a channel between the local and the serving node of the UE, and sends a second message to the serving node of the UE by using the channel.
  • the MTC-IWF and the UE's service node have established channels, in the downlink data transmission, the MTC-IWF only needs to find the channel between it and the UE's service node, and does not need to query the HLR/HSS.
  • the external identifier of the UE may be converted into an internal identifier, and the internal identifier of the UE is carried in the second message and sent to the serving node of the UE together with the downlink data.
  • the serving node of the UE sends the downlink data to the UE.
  • This step is similar to step 305 in the above embodiment, and will not be further described in this embodiment.
  • the serving node of the UE may send the uplink data to the MTC-IWF through the channel, of course, the uplink data.
  • the transmission may also be performed according to the method of the prior art, which is not specifically limited in this embodiment.
  • the beneficial effects of this embodiment are: starting from the serving node of the UE, establishing a channel between the serving node of the UE and the MTC-IWF, and transmitting the downlink data directly to the serving node of the UE through the channel, so that no query is needed in downlink data transmission.
  • HLR/HSS a method for downlink data transmission is provided.
  • the MTC-IWF initiates, and a channel is established between the serving node of the UE and the MTC-IWF, and the downlink data is directly sent to the serving node of the UE through the channel. Therefore, there is no need to query the HLR/HSS in the downlink data transmission. See Figure 7.
  • the specific method flow includes:
  • the MTC-IW receives the first message sent by the server.
  • This step is similar to the step 301 in the foregoing embodiment, and details are not described in this embodiment.
  • the MTC-IWF determines whether there is local service node information of the UE, if yes, step 705 is performed, otherwise step 703 is performed. 703.
  • the MTC-IWF sends a request for acquiring the service node information or the subscription information of the UE to the HLR/HSS.
  • the service node information of the UE needs to be acquired first from the HLR/HSS.
  • the specific acquisition method is similar to the query method in step 303, and is not described in this embodiment.
  • the MTC-IWF sends a create session request to the serving node of the UE to establish a channel with the serving node of the UE.
  • a request for creating a session is sent to the serving node of the UE, where the request message carries the address information and the channel identifier of the MTC-IWF, where the type of the user may be based on the created type.
  • Channel ID or control plane channel ID.
  • the request message may further carry the identifier information of the UE, such as the IMSI of the UE and/or the external identifier of the UE, to identify the UE in the 3GPP network, which is not specifically limited in this embodiment.
  • the serving node of the UE After receiving the creation session request sent by the MTC-IWF, the serving node of the UE returns a create session response to the MTC-IWF, where the response message carries the address information and the channel identifier of the service node, where the type of the created channel identifier may be the user plane channel identifier. , or control plane channel identification.
  • the MTC-IWF receives the create session response returned by the service node, and establishes a channel with the service node.
  • the specific MTC-IWF receiving UE sends a session creation response, and the process of establishing a channel with the service node is similar to the prior art, and is not described in this embodiment.
  • the channel identifier of the MTC-IWF can be a universal channel identifier or a channel identifier reserved or specially allocated for small data transmission.
  • the channel identifier of the service node of the UE may be a common channel identifier, or a channel identifier reserved for the small data transmission or specifically allocated, which is not specifically limited in this embodiment.
  • the MTC-IWF when the MTC-IWF sends downlink data, if the MTC-IWF does not establish a channel with the serving node of the UE, the MTC-IWF may initiate a session request to the serving node of the UE, but this is not the MTC-IWF initiated creation session.
  • the unique trigger condition of the request may trigger the MTC-IWF to initiate a create session request in other scenarios.
  • the HLR/HSS After the HLR/HSS receives the location update message sent by the serving node of the new UE, the HLR/HSS notifies the MTC-IWF of the current serving node information of the UE, so that the MTC-IWF initiates a session request to the new serving node of the UE; or
  • the serving node of the UE sends a location update message to the HLR/HSS, and the HLR/HSS sends a message containing the serving node information of the UE to the MTC-IWF, so that the MTC-IWF initiates a session request to the new serving node of the UE.
  • steps 703-704 are steps that need to be performed when the MTC-IWF and the serving node of the UE have not established a channel. If the MTC-IWF and the serving node of the UE have established a channel, it is not required for downlink data transmission. Steps 703-704 are performed again.
  • the MTC-IW obtains a channel between the local and the serving node of the user equipment, and sends a second message to the serving node of the user equipment by using the channel. 706.
  • the serving node of the UE sends the downlink data to the UE.
  • the steps 705-706 are similar to the steps 604-605 in the foregoing embodiment, and are not further described in this embodiment.
  • the beneficial effects of this embodiment are: initiated by the MTC-IWF, establishing a channel between the serving node of the UE and the MTC-IWF, and transmitting the downlink data directly to the serving node of the UE through the channel, so that there is no need to query the HLR in the downlink data transmission. /HSS.
  • an interoperability device MTC-IWF for machine type communication is provided in the embodiment, including: a receiving module 801 and a processing module 802.
  • the receiving module 801 is configured to receive a first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment;
  • the processing module 802 is configured to obtain the service node information of the user equipment that is stored by the MTC-IWF, and send a second message to the service node of the user equipment according to the service node information of the user equipment, where the second message includes And the downlink data that needs to be sent to the user equipment, so that the service node sends the downlink data to the user equipment.
  • the device further includes:
  • a first registration/subscription module 803, configured to send, to the home location/user register HLR/HSS, the service node information of the user equipment, before the processing module acquires the service node information of the user equipment stored by the MTC-IWF Or requesting the subscription information, and registering/subscribing/requesting the association between the user equipment and the service node of the user equipment to the HLR/HSS, so that the HLR/HSS changes the service node of the user equipment. And returning the changed service node information of the user equipment; receiving and saving the service node information of the user equipment returned by the HLR/HSS; or receiving the subscription information response message returned by the HLR/HSS And saving the service node information of the user equipment carried in the subscription information response message.
  • the device further includes:
  • the obtaining module 804 is configured to send, to the HLR/HSS, a request for acquiring the service node information or the subscription information of the user equipment, before the processing module acquires the service node information of the user equipment stored by the MTC-IWF; receiving and saving Receiving, by the HLR/HSS, the service node information of the user equipment; or receiving the subscription information response message returned by the HLR/HSS, and saving the service node information of the user equipment carried in the subscription information response message .
  • the device further includes:
  • a second registration/subscription module 805, configured to register/subscribe/request the HLR/HSS to the HLR/HSS after the obtaining module 804 sends a request for acquiring the service node information or the subscription information of the user equipment to the HLR/HSS.
  • the association between the device and the service node of the user equipment enables the HLR/HSS to return the changed service node information of the user equipment when the service node of the user equipment is changed.
  • the device further includes:
  • a first creating module 806, configured to send, after the obtaining module 804, a request for acquiring the service node information or the subscription information of the user equipment to the HLR/HSS, to send a first creation association/binding to the service node of the user equipment. Determining a request, causing the service node of the user equipment to return a first creation association/binding response; receiving a first creation association/binding response returned by the service node, thereby establishing an association/binding relationship with the service node.
  • the device further includes:
  • a second creating module 807 configured to: before the processing module 802 acquires the service node information of the user equipment that is stored by the MTC-IWF, receive a second create association/binding request sent by the service node of the user equipment; The service node sends a second create association/binding response to establish an association/binding relationship with the service node.
  • the first message further includes indication information, where the indication information is: information indicating that the downlink data is small data or small data transmission, or indicating that the downlink data is frequent small data or frequent small data transmission.
  • the indication information confirms whether it is necessary to register/subscribe/request the service node information of the user equipment to the HLR/HSS, or to confirm whether an association/binding relationship needs to be established with the service node of the user equipment.
  • the MTC-IWF receives the first message sent by the server, where the first message includes the downlink data that needs to be sent to the user equipment, and the service node information of the user equipment is obtained locally, according to the The serving node information of the UE sends a second message to the serving node of the UE, so that the serving node sends the downlink data to the user equipment. Therefore, data can be transmitted to the service node without querying the HLR/HSS, and the problem of frequent HLR/HSS query in the downlink data transmission is reduced.
  • a machine type communication interoperation device MTC-IWF is provided, and the device includes: a receiving module 901 and a processing module 902.
  • the receiving module 901 is configured to receive a first message that is sent by the server, where the first message includes downlink data that needs to be sent to the user equipment.
  • the processing module 902 is configured to obtain a channel between the MTC-IWF and the serving node of the user equipment, and send, by using the channel, a second message to the serving node of the user equipment, where the second message includes the requirement The downlink data sent to the user equipment, so that the service node sends the downlink data to the user equipment.
  • the device further includes:
  • the obtaining module 903 is configured to send, to the HLR/HSS, a request for acquiring service node information or subscription information of the user equipment, before the processing module 902 acquires a channel between the MTC-IWF and the serving node of the user equipment; Receiving and saving service node information of the user equipment returned by the HLR/HSS; or receiving a subscription information response message returned by the HLR/HSS, and saving the user equipment carried in the subscription information response message Service node information.
  • the device further includes:
  • the first channel creation module 904 is configured to send a first create session request to the service node of the user equipment after the obtaining module 903 initiates a request for acquiring the service node information or the subscription information of the user equipment to the HLR/HSS.
  • the first creation session request carries the address information of the MTC-IWF and the channel identifier of the MTC-IWF, so that the service node of the user equipment returns a first creation session response, and the first creation session response And carrying the address information of the service node of the user equipment and the channel identifier of the service node of the user equipment; receiving a first creation session response returned by the service node of the user equipment, thereby establishing with the service node of the user equipment aisle.
  • the device further includes:
  • a second channel creation module 904 configured to receive a second create session request sent by the service node of the user equipment, before the processing module 902 acquires a channel between the MTC-IWF and the serving node of the user equipment, where Address information of the service node carrying the user equipment and a channel identifier of the service node of the user equipment in the second creation session request; returning a second creation session response to the service node of the user equipment, the second creation The session response carries the address information of the MTC-IWF and the channel identifier of the MTC-IWF, so as to establish a channel with the service node of the user equipment.
  • the first message further includes indication information, where the indication information is: information indicating that the downlink data is small data or small data transmission, or indicating that the downlink data is frequent small data or frequent small data transmission.
  • the information, or the information indicating the downlink data after the downlink data, or the information indicating the establishment of the channel enables the MTC-IWF to confirm, according to the indication information, whether a channel needs to be established with the service node of the user equipment. .
  • the MTC-IWF receives the first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment; and the channel between the local and the service node of the user equipment is obtained, And sending, by the channel, a second message to the serving node of the user equipment, so that the serving node sends the downlink data to the user equipment. Therefore, the data can be transmitted to the service node without querying the HLR/HSS, and the problem of frequent HLR/HSS query in the downlink data transmission is reduced.
  • a machine type communication interoperation device MTC-IWF is provided, the device, The device includes: a processor 1001 and a memory 1002.
  • the storage unit 1002 is configured to store service node information of the user equipment.
  • the processor 1001 is configured to receive a first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment, and obtains service node information of the user equipment that is stored in the memory 1002, according to the The service node information of the user equipment sends a second message to the service node of the user equipment, where the second message includes the downlink data that needs to be sent to the user equipment, so that the service node sends the downlink data. To the user equipment.
  • the method further includes: sending, by the MTC-IWF, the service node information of the user equipment to the home location/user register HLR/HSS Or requesting the subscription information, and registering/subscribing/requesting the association between the user equipment and the service node of the user equipment to the HLR/HSS, so that the HLR/HSS changes the service node of the user equipment. And returning the changed service node information of the user equipment;
  • the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or, the MTC-IWF receives the subscription information response message returned by the HLR/HSS, and saves the subscription information.
  • the service node information of the user equipment carried in the response message.
  • the method before the acquiring, by the MTC-IWF, the service node information of the user equipment that is stored locally, the method further includes: sending, by the MTC-IWF, a request for acquiring the service node information or the subscription information of the user equipment to the HLR/HSS ;
  • the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or, the MTC-IWF receives the subscription information response message returned by the HLR/HSS, and saves the subscription information.
  • the service node information of the user equipment carried in the response message.
  • the method further includes:
  • the MTC-IWF registers/subscribes/requests the association of the user equipment and the service node of the user equipment to the HLR/HSS, so that the HLR/HSS can learn when the service node of the user equipment changes Returning the changed service node information of the user equipment.
  • the method further includes:
  • the method further includes: receiving, by the MTC-IWF, a second creation association/binding request sent by the service node of the user equipment;
  • the MTC-IWF sends a second create association/binding response to the service node to establish an association/binding relationship with the service node.
  • the first message further includes indication information, where the indication information is: information indicating that the downlink data is small data or small data transmission, or indicating that the downlink data is frequent small data or frequent small data transmission.
  • the indication information confirms whether it is necessary to register/subscribe/request the service node information of the user equipment to the HLR/HSS, or to confirm whether an association/binding relationship needs to be established with the service node of the user equipment.
  • a machine type communication interoperation device MTC-IWF is provided, and the device includes: a processor 2001 and a memory 2002.
  • the memory 2002 is configured to store address information and channel identification information of a service node of the user equipment, where the processor 2001 is configured to receive a first message that is sent by the server, where the first message includes the information that needs to be sent to the user equipment.
  • the downlink data is obtained, the channel between the MTC-IWF and the service node of the user equipment is obtained, and the second message is sent to the service node of the user equipment by using the channel, where the second message includes the need to send to
  • the downlink data of the user equipment is used by the serving node to send the downlink data to the user equipment.
  • the method before the acquiring, by the MTC-IWF, the channel between the local device and the serving node of the user equipment, the method further includes:
  • the MTC-IWF receives and saves the service node information of the user equipment returned by the HLR/HSS; or, the MTC-IWF receives the subscription information response message returned by the HLR/HSS, and saves the subscription information.
  • the service node information of the user equipment carried in the response message.
  • the MTC-IWF further includes:
  • the MTC-IWF sends a first create session request to the service node of the user equipment, where the first create session request carries the address information of the MTC-IWF and the channel identifier of the MTC-IWF, so that the The service node of the user equipment returns a first creation session response, where the first creation session response carries the service section of the user equipment Address information of the point and a channel identifier of the service node of the user equipment;
  • the MTC-IWF receives a first create session response returned by the service node of the user equipment, thereby establishing a channel with the service node of the user equipment.
  • the method before the acquiring, by the MTC-IWF, the channel between the local device and the serving node of the user equipment, the method further includes:
  • the MTC-IWF receives a second create session request sent by the service node of the user equipment, where the second create session request carries the address information of the service node of the user equipment and the channel of the service node of the user equipment.
  • the MTC-IWF returns a second create session response to the service node of the user equipment, where the second create session response carries the address information of the MTC-IWF and the channel identifier of the MTC-IWF, thereby The service node of the user equipment establishes a channel.
  • the first message further includes indication information, where the first message further includes indication information, where the indication information is: information indicating that the downlink data is small data or small data transmission, or indicating the The downlink data is information of frequent small data or frequent small data transmission, or information indicating downlink small data after the downlink data, or information indicating that a channel is established, so that the MTC-IWF can confirm whether according to the indication information.
  • a channel needs to be established with the service node of the user equipment.
  • the MTC-IWF receives the first message sent by the server, where the first message includes downlink data that needs to be sent to the user equipment; and the channel between the local and the service node of the user equipment is obtained, And sending, by the channel, a second message to the serving node of the user equipment, so that the serving node sends the downlink data to the user equipment. Therefore, data can be transmitted to the service node without querying the HLR/HSS, which reduces the problem of frequent HLR/HSS query in downlink data transmission.
  • the function distribution may be completed by different functional modules as needed.
  • the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • inter-operating device of the machine type communication provided by the foregoing embodiment is in the same concept as the method embodiment of the downlink data transmission, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

本发明公开了一种下行传输数据的方法和设备，属于通信技术领域。所述方法包括：MTC-IWF接收服务器发送的第一消息，所述第一消息中包括需要发送给用户设备的下行数据；MTC-IWF获取本地存储的所述用户设备的服务节点信息，根据所述UE的服务节点信息向所述UE的服务节点发送第二消息，所述第二消息中包括所述需要发送给所述用户设备的下行数据，使所述服务节点将所述下行数据发送给所述用户设备。

Description

下行传输数据的方法和设备 本申请要求于 2012年 11月 02日提交中国专利局、 申请号为 201210433549. 0、 发 明名称为 "下行传输数据的方法和设备"的中国专利申请的优先权， 其全部内容通过引 用结合在本申请中。 技术领域 本发明涉及通信技术领域， 特别涉及一种下行传输数据的方法和设备。 背景技术
M2M ( Machine-to-Machine , 机器间） 通信是指应用各种通信网络和信息感知、 处 理， 实现机器与机器、 机器与人之间进行数据通信和交互的一系列技术及技术组合的总 称。 M2M设备的一种通信场景是 3GPP定义的小数据传输。 小数据表示终端 UE ( User Equipment , 用户设备） 仅发送 /接收小量数据。
现有技术中， 定义了一种小数据的传输方法， 具体的通过 UE 和服务节点之间的 generic NAS transport消息、 及服务节点和 MTC网关 MTC-IWF (机器类型通信的互操 作设备） 之间的 T5接口、 以及 MTC-IWF和服务器之间的 Tsp接口传递上行或下行方向 的小数据。 该方案具体传输下行小数据的步骤如下：
1、 服务器通过 Tsp接口发送携带下行方向小数据的消息给 MTC_IWF。
2、 MTC-IWF收到服务器发送的消息后，查询存放 UE签约数据的 HLR ( Home Locat ion Regi ster , 归属位置寄存器） /HSS ( Home Subscriber Server , 归属用户服务器）， 获 取为 UE服务的服务节点信息。
3、 MTC-IWF通过和服务节点之间的 T5接口发送携带小数据的消息给服务节点。
4、 服务节点向 UE发送 DOWNLINK— GENERIC— NAS— TRANSPORT消息， 消息中携带需要 发送给 UE的小数据。
由上面的小数据传输方法可知， 现有技术中 MTC-IWF每次向 UE发送小数据时， 都 需要查询 HLR/HSS来获得 UE的路由信息， 如果小数据的发送频率比较高， 那么在频繁 发送下行数据的场景下， 这么做会给 HLR/HSS带来大量的信令负荷。 且如果 UE上同时 运行多个这样的应用， 就会有多个服务器不断向 UE频繁发送小数据， 如果大量的 UE都 安装使用这样的应用， 上述方案中发送小数据过程中， 对 HLR/HSS进行查询导致的信令 负荷将会进一步增大， 从而有可能引起网络拥塞。 发明内容 为了解决下行数据传输中对 HLR/HSS查询频繁的问题，本发明实施例提供了一种下 行数据传输的方法和设备。 所述技术方案如下：
第一方面， 提供了一种下行传输数据的方法， 所述方法包括： 机器类型通信的互操 作设备 MTC-IWF接收服务器发送的第一消息， 所述第一消息中包括需要发送给用户设备 的下行数据； 所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息， 根据所述用 户设备的服务节点信息向所述用户设备的服务节点发送第二消息，所述第二消息中包括 所述需要发送给所述用户设备的下行数据，使所述服务节点将所述下行数据发送给所述 用户设备。
在第一方面的第一种可能的实施方式中，所述 MTC-IWF获取本地存储的所述用户设 备的服务节点信息之前， 还包括： 所述 MTC-IWF向 HLR/HSS发送获取所述用户设备的服 务节点信息或者签约信息的请求； 所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用 户设备的服务节点信息；或，所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设备的服务节点信息。
在第一方面的第一种可能的实施方式中的第一种可能的实施方式中， 所述 MTC-IWF 向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请求之后， 还包括： 所述 MTC-IWF向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户设备的服务节点 的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能够返回所述变化 后的所述用户设备的服务节点信息。
在第一方面的第一种可能的实施方式中的第二种可能的实施方式中， 所述 MTC-IWF 向 HLR/HSS发起获取所述用户设备的服务节点信息或签约信息的请求之后， 还包括： 所 述 MTC-IWF 向所述用户设备的服务节点发送第一创建关联 /绑定请求， 使所述用户设备 的服务节点返回第一创建关联 /绑定响应； 所述 MTC-IWF接收所述服务节点返回的第一 创建关联 /绑定响应， 从而与所述服务节点建立关联 /绑定关系。
在第一方面的第二种可能的实施方式中，所述 MTC-IWF获取本地存储的所述用户设 备的服务节点信息之前， 还包括： 所述 MTC-IWF接收所述用户设备的服务节点发送的第 二创建关联 /绑定请求； 所述 MTC-IWF向所述服务节点发送第二创建关联 /绑定响应， 从 而与所述服务节点建立关联 /绑定关系。
第二方面， 提供了一种下行传输数据的方法， 所述方法包括： 机器类型通信的互操 作设备 MTC-IWF接收服务器下发的第一消息， 所述第一消息中包括需要发送给用户设备 的下行数据； 所述 MTC-IWF获取本地与所述用户设备的服务节点之间的通道， 通过所述 通道向所述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要发送给所 述用户设备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设备。
在第二方面的第一种可能实施方式中，所述 MTC-IWF获取本地与所述用户设备的服 务节点之间的通道之前， 还包括： 所述 MTC-IWF向归属位置 /用户寄存器 HLR/HSS发送 获取所述用户设备的服务节点信息或者签约信息的请求； 所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返 回的签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设备的服务节 点信息。
在第二方面的第一种可能实施方式中的第一中可能实施方式中， 所述 MTC-IWF 向
HLR/HSS发起获取所述用户设备的服务节点信息或者签约信息的请求之后， 还包括： 所 述 MTC-IWF向所述用户设备的服务节点发送第一创建会话请求，所述第一创建会话请求 中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识，使所述用户设备的服务节 点返回第一创建会话响应，所述第一创建会话响应中携带所述用户设备的服务节点的地 址信息和所述用户设备的服务节点的通道标识； 所述 MTC-IWF接收所述用户设备的服务 节点返回的第一创建会话响应， 从而与所述用户设备的服务节点建立通道。
在第二方面的第二种可能实施方式中，所述 MTC-IWF获取本地与所述用户设备的服 务节点之间的通道之前， 还包括： 所述 MTC-IWF接收所述用户设备的服务节点发送的第 二创建会话请求，所述第二创建会话请求中携带所述用户设备的服务节点的地址信息和 所述用户设备的服务节点的通道标识； 所述 MTC-IWF向所述用户设备的服务节点返回第 二创建会话响应， 所述第二创建会话响应中携带所述 MTC-IWF 的地址信息和所述 MTC-IWF的通道标识， 从而与所述用户设备的服务节点建立通道。
第三方面， 还提供了一种机器类型通信的互操作设备 MTC-IWF, 所述设备包括： 接收模块， 用于接收服务器发送的第一消息， 所述第一消息中包括需要发送给用户 设备的下行数据；
处理模块， 用于获取 MTC-IWF存储的所述用户设备的服务节点信息， 根据所述用户 设备的服务节点信息向所述用户设备的服务节点发送第二消息，所述第二消息中包括所 述需要发送给所述用户设备的下行数据，使所述服务节点将所述下行数据发送给所述用 户设备。
在第三方面的第一种可能实施方式中， 所述设备还包括： 获取模块，用于在所述处理模块获取 MTC-IWF存储的所述用户设备的服务节点信息 之前， 向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请求； 接收并 保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返回的 签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设备的服务节点信 息。
在第三方面的第一种可能实施方式中的第一种可能实施方式中， 所述设备还包括： 第二注册 /订阅模块， 用于在所述获取模块向 HLR/HSS发送获取所述用户设备的服 务节点信息或者签约信息的请求之后， 向所述 HLR/HSS注册 /订阅 /请求所述用户设备和 所述用户设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生 变化时能够返回所述变化后的所述用户设备的服务节点信息。
在第三方面的第一种可能实施方式中的第二种可能实施方式中， 所述设备还包括： 第一创建模块，用于在所述获取模块向 HLR/HSS发起获取所述用户设备的服务节点 信息或签约信息的请求之后， 向所述用户设备的服务节点发送第一创建关联 /绑定请求， 使所述用户设备的服务节点返回第一创建关联 /绑定响应； 接收所述服务节点返回的第 一创建关联 /绑定响应， 从而与所述服务节点建立关联 /绑定关系。
在第三方面的第二种可能实施方式中， 所述设备还包括：
第二创建模块，用于在所述处理模块获取 MTC-IWF存储的所述用户设备的服务节点 信息之前， 接收所述用户设备的服务节点发送的第二创建关联 /绑定请求； 向所述服务 节点发送第二创建关联 /绑定响应， 从而与所述服务节点建立关联 /绑定关系。
第四方面， 还提供了一种机器类型通信的互操作设备 MTC-IWF, 所述设备， 所述设 备包括：
接收模块， 用于接收服务器下发的第一消息， 所述第一消息中包括需要发送给用户 设备的下行数据；
处理模块， 用于获取 MTC-IWF与所述用户设备的服务节点之间的通道， 通过所述通 道向所述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要发送给所述 用户设备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设备。
在第四方面的第一种可能实施方式中， 所述设备还包括：
获取模块，用于在所述处理模块获取 MTC-IWF与所述用户设备的服务节点之间的通 道之前， 向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请求； 接收 并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返回 的签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设备的服务节点 信息。
在第四方面的第一种可能实施方式中的第一种可能实施方式中， 所述设备还包括： 第一通道创建模块，用于在所述获取模块向 HLR/HSS发起获取所述用户设备的服务 节点信息或者签约信息的请求之后， 向所述用户设备的服务节点发送第一创建会话请 求，所述第一创建会话请求中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 使所述用户设备的服务节点返回第一创建会话响应，所述第一创建会话响应中携带所述 用户设备的服务节点的地址信息和所述用户设备的服务节点的通道标识； 接收所述用户 设备的服务节点返回的第一创建会话响应， 从而与所述用户设备的服务节点建立通道。
在第四方面的第二种可能实施方式中， 所述设备还包括：
第二通道创建模块，用于在所述处理模块获取 MTC-IWF与所述用户设备的服务节点 之间的通道之前， 接收所述用户设备的服务节点发送的第二创建会话请求， 所述第二创 建会话请求中携带所述用户设备的服务节点的地址信息和所述用户设备的服务节点的 通道标识； 向所述用户设备的服务节点返回第二创建会话响应， 所述第二创建会话响应 中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 从而与所述用户设备的服 务节点建立通道。
本发明实施例提供的技术方案带来的有益效果是： MTC-IWF接收服务器发送的第一 消息， 所述第一消息中包括需要发送给用户设备的下行数据； 在本地获取所述用户设备 的服务节点信息，根据所述用户设备的服务节点信息向所述用户设备的服务节点发送第 二消息， 或获取本地与所述用户设备的服务节点之间的通道， 通过所述通道向所述用户 设备的服务节点发送第二消息， 使所述服务节点将所述下行数据发送给所述用户设备。 从而不需要向 HLR/HSS进行查询就能够将数据传输给服务节点，减少了下行数据传输中 对 HLR/HSS查询频繁的问题。 附图说明 为了更清楚地说明本发明实施例中的技术方案， 下面将对实施例描述中所需要使用 的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是本发明的一些实施例， 对 于本领域普通技术人员来讲， 在不付出创造性劳动的前提下， 还可以根据这些附图获得 其他的附图。
图 1是本发明实施例中提供的一种下行传输数据的方法流程图； 图 2是本发明实施例中提供的一种下行传输数据的方法流程图；
图 3是本发明实施例中提供的一种下行传输数据的方法流程图；
图 4是本发明实施例中提供的一种下行传输数据的方法流程图；
图 5是本发明实施例中提供的一种下行传输数据的方法流程图；
图 6是本发明实施例中提供的一种下行传输数据的方法流程图；
图 7是本发明实施例中提供的一种下行传输数据的方法流程图；
图 8是本发明实施例中提供的一种 MTC-IWF结构示意图；
图 9是本发明实施例中提供的另一种 MTC-IWF结构示意图；
图 10是本发明实施例中提供的一种 MTC-IWF结构示意图；
图 11是本发明实施例中提供的另一种 MTC-IWF结构示意图；
图 12是本发明实施例中提供的一种 MTC-IWF结构示意图；
图 13是本发明实施例中提供的另一种 MTC-IWF结构示意图。 具体实肺式 为使本发明的目的、 技术方案和优点更加清楚， 下面将结合附图对本发明实施方式 作进一步地详细描述。
参见图 1， 本实施例中提供了一种下行传输数据的方法， 所述方法包括：
101、 MTC-IWF接收服务器发送的第一消息，所述第一消息中包括需要发送给用户设 备的下行数据；
102、 所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息， 根据所述用户 设备的服务节点信息向所述用户设备的服务节点发送第二消息，所述第二消息中包括所 述需要发送给所述用户设备的下行数据，使所述服务节点将所述下行数据发送给所述用 户设备。
可选地，所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息之前，还包括: 所述 MTC-IWF向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点 信息或者签约信息的请求， 并向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户 设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能 够返回所述变化后的所述用户设备的服务节点信息；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。 可选地，所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息之前，还包括： 所述 MTC-IWF向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请 求；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
可选地，所述 MTC-IWF向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约 信息的请求之后， 还包括：
所述 MTC-IWF向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户设备的服务 节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能够返回所述 变化后的所述用户设备的服务节点信息。
可选地，所述 MTC-IWF向 HLR/HSS发起获取所述用户设备的服务节点信息或签约信 息的请求之后， 还包括：
所述 MTC-IWF 向所述用户设备的服务节点发送第一创建关联 /绑定请求， 使所述用 户设备的服务节点返回第一创建关联 /绑定响应；
所述 MTC-IWF接收所述服务节点返回的第一创建关联 /绑定响应， 从而与所述服务 节点建立关联 /绑定关系。
可选地，所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息之前，还包括： 所述 MTC-IWF接收所述用户设备的服务节点发送的第二创建关联 /绑定请求； 所述 MTC-IWF 向所述服务节点发送第二创建关联 /绑定响应， 从而与所述服务节点 建立关联 /绑定关系。
可选地， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小 数据或小数据传输的信息， 或指示所述下行数据为频繁小数据或频繁小数据传输的信 息， 或指示所述下行数据之后还有下行小数据的信息， 或指示注册 /订阅 /请求所述用户 设备和所述用户设备的服务节点的关联的信息，使所述 MTC-IWF能够根据所述指示信息 确认是否需要向 HLR/HSS注册 /订阅 /请求所述用户设备的服务节点信息， 或确认是否需 要与所述用户设备的服务节点建立关联 /绑定关系。
本实施例的有益效果是： MTC-IWF接收服务器发送的第一消息， 所述第一消息中包 括需要发送给用户设备的下行数据； 在本地获取所述用户设备的服务节点信息， 根据所 述 UE的服务节点信息向所述 UE的服务节点发送第二消息，使所述服务节点将所述下行 数据发送给所述用户设备。从而不需要向 HLR/HSS进行查询就能够将数据传输给服务节 点， 减少了下行数据传输中对 HLR/HSS查询频繁的问题。 参见图 2， 本实施例中提供了一种下行传输数据的方法， 所述方法包括：
201、 MTC-IWF接收服务器下发的第一消息，所述第一消息中包括需要发送给用户设 备的下行数据；
202、 所述 MTC-IWF获取本地与所述用户设备的服务节点之间的通道， 通过所述通 道向所述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要发送给所述 用户设备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设备。
可选地， 所述 MTC-IWF获取本地与所述用户设备的服务节点之间的通道之前， 还包 括：
所述 MTC-IWF向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点 信息或者签约信息的请求；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
可选地，所述 MTC-IWF向 HLR/HSS发起获取所述用户设备的服务节点信息或者签约 信息的请求之后， 还包括：
所述 MTC-IWF向所述用户设备的服务节点发送第一创建会话请求，所述第一创建会 话请求中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识，使所述用户设备的 服务节点返回第一创建会话响应，所述第一创建会话响应中携带所述用户设备的服务节 点的地址信息和所述用户设备的服务节点的通道标识；
所述 MTC-IWF接收所述用户设备的服务节点返回的第一创建会话响应， 从而与所述 用户设备的服务节点建立通道。
可选地， 所述 MTC-IWF获取本地与所述用户设备的服务节点之间的通道之前， 还包 括：
所述 MTC-IWF接收所述用户设备的服务节点发送的第二创建会话请求，所述第二创 建会话请求中携带所述用户设备的服务节点的地址信息和所述用户设备的服务节点的 通道标识；
所述 MTC-IWF向所述用户设备的服务节点返回第二创建会话响应，所述第二创建会 话响应中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 从而与所述用户设 备的服务节点建立通道。 可选地， 所述第一消息中还包括指示信息， 所述第一消息中还包括指示信息， 所述 指示信息： 指示所述下行数据为小数据或小数据传输的信息， 或指示所述下行数据为频 繁小数据或频繁小数据传输的信息， 或指示所述下行数据之后还有下行小数据的信息， 或指示建立通道的信息，使所述 MTC-IWF能够根据所述指示信息确认是否需要与所述用 户设备的服务节点建立通道。
本实施例的有益效果是： MTC-IWF接收服务器发送的第一消息， 所述第一消息中包 括需要发送给用户设备的下行数据； 获取本地与所述用户设备的服务节点之间的通道， 通过所述通道向所述用户设备的服务节点发送第二消息，使所述服务节点将所述下行数 据发送给所述用户设备。从而不需要向 HLR/HSS进行查询就能够将数据传输给服务节点， 减少了下行数据传输中对 HLR/HSS查询频繁的问题。 本实施例中提供了一种下行传输数据的方法， MTC-IWF在接收到服务发送的小数据 后， 向 HLR/HSS进行注册 /订阅， 注册 /订阅 UE的服务节点和 UE的关联， 这样当 HSS中 保存的 UE的服务节点发生变化时，或者 UE附着时， HLR/HSS会通知 MTC-IWF该 UE的服 务节点信息， MTC-IW保存或更新 UE服务节点信息， 这样在下行数据传输的过程中， 就 不需要再向 HLR/HSS查询 UE的服务节点信息， 从而减轻了 HLR/HSS信令负担。 本实施 例中及以下实施例中出现的符号 "/ "代表 "或" 的关系， 对此以下实施例中不再做一 一说明。 参见图 3， 具体的方法流程包括：
301、 MTC-IWF接收服务器发送的第一消息。
其中服务器包括 SCS ( Service Capability Server , 业务能力服务器） 或者 AS
(Application Server, 应用服务器）， 对此本实施例不做具体限定。
服务器下发的第一消息中包括需要发送给 UE的下行数据， 其中， 下行数据包括但 不限于： 下行小数据、 应用信息或设备触发信息等。
值得说明的是， 在第一消息中还可以携带 UE 的外部标识 external ID, 用于查询 UE的内部标识 IMSI ( International Mobile Subscriber Identification Number, 国 际移动用户识别码）， 以在 3GPP网络内部标识该 UE。
可选地， 所述第一消息中还包括指示信息， 该指示信息包括： 指示所述下行数据为 小数据或小数据传输的信息， 或指示所述下行数据为频繁小数据或频繁小数据传输的信 息， 或指示所述下行数据之后还有下行小数据的信息， 或指示注册 /订阅 /请求所述用户 设备和所述用户设备的服务节点的关联的信息，使 MTC-IWF能够根据所述指示信息确认 是否需要向 HLR/HSS注册 /订阅 UE的服务节点信息， 或确认是否需要与 UE的服务节点 建立关联 /绑定关系， 或确认是否需要与 UE的服务节点建立通道。
另外， 除了服务器向 MTC-IWF发送的第一消息中可以包括上述指示外， 在 UE附着 时， UE的服务节点也可以向 MTC-IWF发送上述指示； 或者 HLR/HSS可以向 MTC-IWF发送 上述指示； 或者 MTC-IWF收到服务器发送的小数据， 向 HLR/HSS进行查询时， HLR/HSS 可以向 MTC-IWF发送该指示。具体 MTC-IWF如何获取指示信息，本实施例不做具体限定。
302、 MTC-IWF判断本地是否有所述 UE的服务节点信息， 如果是则执行步骤 304， 否则执行步骤 303。
其中， UE的服务节点包括: SGSN ( Serving GPRS Support Node, 服务支持节点） /MME (Mobi le Management Entity, 移动管理实体）， 服务节点信息指 UE的路由信息、 或者服务节点的信息、 或者核心网服务节点信息。
303, MTC-IWF向 HLR/HSS发送获取 UE的服务节点信息或者签约信息的请求和注册 / 订阅 /请求 UE和 UE的服务节点的关联，使 HLR/HSS在获知 UE的服务节点发生变化时能 够返回变化后的 UE的服务节点信息。
本实施例中，如果 MTC-IWF未在本地找到 UE的服务节点信息，则需要先向 HLR/HSS 查询 UE的服务节点信息。具体的向 HLR/HSS查询 UE的服务节点信息方法，包括: MTC-IWF 向 HLR/HSS 发送获取所述 UE 的服务节点信息或者签约信息的请求， 接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返 回的签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设备的服务节 点信息。
进一步地， 在获取 UE的服务节点信息时， 还可以向所述 HLR/HSS注册 /订阅 /请求 所述用户设备和所述用户设备的服务节点的关联， 使所述 HLR/HSS在获知 UE的服务节 点发生变化时能够返回所述变化后的所 UE的服务节点信息。 可选地， 也可以在获取到 UE的服务节点信息之后，向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户设备 的服务节点的关联， 使所述 HLR/HSS在获知 UE的服务节点发生变化时能够返回所述变 化后的所 UE的服务节点信息。 其中， 用户设备和用户设备的服务节点的关联是指用户 设备的服务节点发生变化或用户设备由另外的服务节点服务。
本实施例中，在 MTC-IWF向 HLR/HSS进行注册 /订阅 /请求用户设备和所述用户设备 的服务节点的关联后，当 HLR/HSS中保存的 UE的服务节点发生变化时，或者 UE附着时， HLR/HSS通知 MTC-IWF该 UE的服务节点信息。 例如在 UE的位置更新 RAU ( Route Area Update, 路由区域更新） /TAU ( Tracking Area Update , 跟踪区域更新） 过程中 UE的 服务节点发生变更， 则新的服务节点从旧的服务节点获取 UE 的上下文信息， 并向 HLR/HSS发送位置更新消息， 通知该 UE当前的服务服务节点信息； 或当 UE附着时， UE 的服务节点也会向 HLR/HSS发送位置更新消息， 通知 UE的服务服务节点信息， HLR/HSS 获知服务节点的变化信息则将新的服务节点信息发送给 MTC_IWF。
本步骤中， 当第一消息中包括 UE的外部标识时， 在 MTC-IWF向 HLR/HSS获取 UE的 服务节点信息时， 也会将 UE的外部标识携带在查询请求中， HLR/HSS根据 UE的外部标 识获取 UE的 IMSI , 将 UE的 IMSI和服务节点信息返回给 MTC_IWF。
值得说明的是本步骤是在 MTC-IWF第一次接收到服务器发送给 UE的下行数据时执 行， 当 MTC-IWF已经向 HLR/HSS进行注册后， 不需要 MTC-IWF每次向 UE发送下行数据 时都执行该步骤， 所本步骤在下行数据的传输过程中不是必选的。
304、 MTC-IWF获取 UE的服务节点信息， 根据 UE的服务节点信息向所述 UE的服务 节点发送第二消息。
本步骤中， 在 MTC-IWF 已经保存了 UE 的服务节点信息， 在接收到下行数据时， MTC-IWF在本地获取 UE所在服务节点信息。 其中， MTC-IWF可以根据第一消息中携带的 UE的外部标识信息获取 UE所在服务节点信息。可选地，可以将 UE的外部标识转换为内 部标识， 将 UE的内部标识携带在第二消息中与下行数据一起发送给 UE的服务节点上。
305、 UE的服务节点将所述下行数据发送给 UE。
服务节点收到 MTC-IWF发送的下行数据， 将该下行数据发送到 UE上， 从而完成下 行数据的传输。 此步骤与现有技术类似， 对此本实施例不再赘述。
本实施例的有益效果是： MTC-IWF可以保存 /更新 UE的服务节点信息， 下次收到发 送给该 UE的下行小数据时， 就可以向 UE的服务节点发送携带小数据的消息， 而不用再 向 HLR/HSS进行查询。 本实施例中提供了一种下行传输数据的方法， 本实施例中由 UE的服务节点发起， 在服务节点和 MTC-IWF之间建立关联 /绑定关系， 通过建立的关联 /绑定关系， 服务节点 和 MTC-IWF可以获知彼此的信息， 从而在下行数据传输中无需查询 HLR/HSS。 参见图 4， 具体的方法流程包括：
401、 UE的服务节点向 MTC-IWF发送创建关联 /绑定请求。
本步骤中， UE的服务节点向 MTC-IWF发送创建关联 /绑定请求的场景包括： 服务节 点收到 UE的附着消息， 或者 UE发送的上行小数据， 或者， UE上的频繁小数据传输的应 用开启 /上线， UE向服务节点发送小数据或频繁小数据指示。 在上述几种场景下， 如果 UE的服务节点未与 MTC-IWF建立关联 /绑定关系，则 UE的服务节点向 MTC-IWF发送创建 关联 /绑定请求。
本实施例中， 针对上述发起创建关联 /绑定的场景， 在的服务节点向 MTC-IWF发起 创建关联 /绑定请求之前， 需要先找到对应的 MTC-IWF,具体获取 MTC-IWF信息的方法与 现有技术类似， 包括： UE的服务节点和 HLR/HSS交互， 获取 HLR/HSS中保存的 MTC-IWF 信息， 或 UE的服务节点从 UE的指示中获取 MTC-IWF信息， 或 UE的服务节点也可以本 地配置 MTC-IWF信息。 具体采用哪种方法获取对应的 MTC-IWF, 本实施例并不做具体限 定。
本实施例中， UE的服务节点和 HLR/HSS交互中， 还可以获取 UE的标识信息， 例如 UE的 IMSI和 /或 UE外部标识， 此处与现有技术类似， 对此本实施例不再赘述。
在 UE的服务节点发送的创建关联 /绑定的请求消息中携带服务节点信息，还可以携 带 UE的标识信息，例如， UE的 IMS I和 /或 UE外部标识， 以在 3GPP网络内部标识该 UE， 对此本实施例中并不做具体限定。
本实施例中， 另一种 UE的服务节点向 MTC-IWF发起创建关联 /绑定请求的场景是： MTC-IWF向 UE的服务节点发送下行小数据通知， UE的服务节点接收到 MTC-IWF发送的 通知后， 发起创建关联 /绑定请求。
本实施例中， 另一种 UE的服务节点向 MTC-IWF发起创建关联 /绑定请求的场景是： MTC-IWF直接请求 UE的服务节点发起创建关联 /绑定请求，以建立 MTC-IWF与 UE所在服 务节点的关联 /绑定关系。
402、 MTC-IWF向 UE的服务节点发送创建关联 /绑定响应，从而与所述服务节点建立 关联 /绑定关系。
其中， 响应消息中携带 MTC-IWF信息， 以使 UE 的服务节点根据 MTC-IWF信息与 MTC-IWF进行关联 /绑定。
本实施例中， 在 MTC-IWF与 UE的服务节点创建关联 /绑定关系后， 当 UE的服务节 点发生变化时， 例如， 在 UE的位置更新 RAU/TAU过程中服务节点可能发生变更， 则 UE 的新的服务节点从 UE的旧服务节点获取 UE的上下文信息。 UE的上下文信息中包括关联 /绑定信息， 即 MTC-IWF的信息， UE的旧的服务节点取消和 MTC-IWF的关联 /绑定， UE 的新服务节点向 MTC-IWF发送新服务节点信息， 以和 MTC-IWF建立关联 /绑定关系。
值得说明的是， 步骤 401-402是在当 MTC-IWF与 UE的服务节点还未建立关联 /绑定 关系时需要执行的步骤， 如果 MTC-IWF与 UE的服务节点已建立了关联 /绑定关系， 则在 下行数据传输时不需要再执行步骤 401-402。
403、 MTC-IW接收服务器发送的第一消息。 该步骤与上述实施例中的步骤 301类似， 对此本实施例不再赘述。
404、 MTC-IW在本地获取 UE的服务节点信息， 根据所述 UE的服务节点信息向所述 UE的服务节点发送第二消息。
由于 MTC-IWF与 UE的服务节点已建立了关联 /绑定关系，所以在下行数据的传输中， MTC-IWF只需根据 UE 的外部标识在本地获取 UE 的服务节点的信息即可， 不需要再向 HLR/HSS查询。
可选地， 可以将 UE的外部标识转换为内部标识， 将 UE的内部标识携带在第二消息 中与下行数据一起发送给 UE的服务节点上。
405、 UE的服务节点将所述下行数据发送给 UE。
此步骤与上述实施例中的步骤 305类似， 对此本实施例不再赘述。
值得说明的是， 本实施例中在 MTC-IWF与 UE的服务节点建立了关联 /绑定关系后， 对于上行数据的传输， UE的服务节点可以将上行数据直接发送给关联 /绑定的 MTC-IWF, 当然， 上行数据的传输也可以按照现有技术的方法进行传输， 对此本实施例并不做具体 限定。
本实施例的有益效果是： 由 UE的服务节点发起， 在 UE的服务节点和 MTC-IWF之间 建立关联 /绑定关系， 通过建立的关联 /绑定关系， 服务节点和 MTC-IWF可以获知彼此的 信息， 从而在下行数据传输中无需查询 HLR/HSS。 本实施例中提供了一种下行传输数据的方法， 本实施例中由 MTC-IWF发起， 在 UE 的服务节点和 MTC-IWF之间建立关联 /绑定关系， 通过建立的关联 /绑定关系， 服务节点 和 MTC-IWF可以获知彼此的信息， 从而在下行数据传输中无需查询 HLR/HSS。 参见图 5， 具体的方法流程包括：
501、 MTC-IWF接收服务器发送的第一消息。
该步骤与上述实施例中的步骤 301类似， 对此本实施例不再赘述。
502、 MTC-IWF判断本地是否有所述 UE的服务节点信息， 如果是则执行步骤 505， 否则执行步骤 503。
503、 MTC-IWF向 HLR/HSS发送获取所述 UE的服务节点信息或者签约信息的请求。 本实施例中与步骤 303—样， 如果 MTC-IWF未在本地找到 UE的服务节点信息， 则 需要先向 HLR/HSS获取 UE的服务节点信息。 具体的获取方法与步骤 303中的获取方法 类似， 对此本实施例不再赘述。
504、 MTC-IWF向 UE的服务节点发送创建关联 /绑定请求， 以与 UE的服务节点建立 关联 /绑定关系。
本实施例中， 在查询到 UE的服务节点信息之后， 向 UE的服务节点发送创建关联 / 绑定请求， 其中， 请求消息中携带 MTC-IWF信息， 还可以携带 UE标识信息； UE的服务 节点接收到 MTC-IWF发送的创建关联 /绑定请求后，向 MTC-IWF返回创建关联 /绑定响应， 其中响应消息中携带服务节点信息， MTC-IWF接收所述服务节点返回的创建关联 /绑定响 应， 从而与所述服务节点建立关联 /绑定关系。
本实施例中， 在 MTC-IWF发送下行数据时， 如果 MTC-IWF未与 UE的服务节点建立 关联 /绑定关系， 则 MTC-IWF 可以向 UE 的服务节点发起关联 /绑定请求， 但是这不是 MTC-IWF发起创建关联 /绑定请求的唯一触发条件， 在其它场景下， 也可能触发 MTC-IWF 发起创建关联 /绑定请求。例如， HLR/HSS收到新 UE的服务节点发送的位置更新消息后， HLR/HSS通知 MTC-IWF该 UE当前的服务节点信息， 使 MTC-IWF向 UE的新的服务节点发 起关联 /绑定请求； 或者， 当 UE附着时， UE的服务节点向 HLR/HSS发送位置更新消息， HLR/HSS向 MTC-IWF发送包含 UE的服务节点信息的消息， 使 MTC-IWF向 UE的新的服务 节点发起关联 /绑定请求。
值得说明的是， 步骤 503-504是 MTC-IWF与 UE的服务节点还未建立关联 /绑定关系 时需要执行的步骤， 如果 MTC-IWF与 UE的服务节点已建立了关联 /绑定关系， 则在下行 数据传输时不需要再执行步骤 503-504。
505、 MTC-IWF获取 UE的服务节点信息， 根据 UE的服务节点信息向所述 UE的服务 节点发送第二消息。
506、 UE的服务节点将所述下行数据发送给 UE。
其中，步骤 505-506与上述实施例中的步骤 404-405类似，对此本实施例不再赘述。 本实施例的有益效果是： 由 MTC-IWF发起， 在 UE的服务节点和 MTC-IWF之间建立 关联 /绑定关系，通过建立的关联 /绑定关系，服务节点和 MTC-IWF可以获知彼此的信息， 从而在下行数据传输中无需查询 HLR/HSS。 本实施例中提供了一种下行传输数据的方法， 由 UE的服务节点发起， 在 UE的服务 节点和 MTC-IWF之间建立通道， 其中该通道包括用户面连接（或称作用户面隧道）或控 制面连接 （或称作控制面隧道）， UE 的服务节点和 MTC-IWF通过建立的通道传输上行 / 下行数据。 参见图 6， 具体的方法流程包括：
601、 UE的服务节点向 MTC-IWF发送创建会话请求。
本步骤中， UE的服务节点向 MTC-IWF发送创建会话请求的场景包括：服务节点收到 UE的附着消息， 或者 UE发送的上行小数据， 或者， UE上的频繁小数据传输的应用开启 /上线， UE向服务节点发送小数据或频繁小数据指示。在上述几种场景下， 如果 UE的服 务节点未与 MTC-IWF建立通道， 则 UE的服务节点向 MTC-IWF发送创建会话请求。 针对 上述发起会话请求的场景， 在 UE的服务节点向 MTC-IWF发起创建会话请求之前， 需要 先找到对应的 MTC-IWF, 具体获取 MTC-IWF信息的方法与现有技术类似， 包括： UE的服 务节点和 HLR/HSS交互， 获取 HLR/HSS中保存的 MTC-IWF信息， 或 UE的服务节点从 UE 的指示中获取 MTC-IWF信息， 或 UE的服务节点也可以本地配置 MTC-IWF信息。 具体采 用哪种方法获取对应的 MTC-IWF, 本实施例并不做具体限定。
本实施例中， UE的服务节点和 HLR/HSS交互中， 还可以获取 UE的标识信息， 例如 UE的 IMSI和 /或 UE外部标识， 此处与现有技术类似， 对此本实施例不再赘述。
在 UE的服务节点发送的创建会话的请求消息中该服务节点的地址和通道标识， 其 中， 根据创建的连接类型， 可以是用户面通道标识， 或者控制面通道标识， 对此本实施 例不做具体限定。
可选地， 请求消息中还可以携带 UE的标识信息， 例如， UE的 IMSI和 /或 UE外部标 识， 以在 3GPP网络内部标识该 UE， 对此本实施例并不做具体限定。
值得说明的是， UE的服务节点的通道标识可以是通用的通道标识，或者是为小数据 传输预留或专门分配的通道标识， 对此本实施例不做具体限定。
本实施例中，另一种 UE的服务节点向 MTC-IWF发起创建会话请求的场景是: MTC-IWF 向 UE的服务节点发送下行小数据通知， UE的服务节点接收到 MTC-IWF发送的通知后， 发起创建会话请求。
本实施例中，另一种 UE的服务节点向 MTC-IWF发起创建会话请求的场景是: MTC-IWF 直接请求 UE的服务节点发起创建会话请求， 以建立 MTC-IWF与 UE所在服务节点的用户 面或控制面隧道。
602、 MTC-IWF向 UE的服务节点发送创建会话响应，从而与所述服务节点建立通道。 其中， 响应消息中携带 MTC-IWF的地址信息和通道标识， 根据创建的类型可以是用 户面通道标识， 或者控制面通道标识， 从而与 UE的服务节点建立通道。
值得说明的是， MTC-IWF的通道标识可以是通用的通道标识， 或者是为小数据传输 预留或专门分配的通道标识， 对此本实施例不做具体限定。
本实施例中， MTC-IWF向 UE的服务节点发送创建会话响应，与所述服务节点建立通 道的过程与现有技术类似， 对此本实施例不再赘述。
本实施例中， 在 MTC-IWF与 UE的服务节点建立通道后， 当 UE的服务节点发生变化 时， 例如， 在 UE的位置更新 RAU/TAU过程中服务节点可能发生变更， 则 UE的新的服务 节点从 UE的旧服务节点获取 UE的上下文信息。 UE的上下文信息中包括隧道信息， 即 MTC-IWF的地址信息和通道标识信息， UE的旧的服务节点去激活和 MTC-IWF之间的通道， UE的新服务节点向 MTC-IWF发送新的会话创建请求， 以和 MTC-IWF建立通道。
值得说明的是， 步骤 601-602是在当 MTC-IWF与 UE的服务节点还未建立通道时需 要执行的步骤， 如果 MTC-IWF与 UE的服务节点已建立了通道， 则在下行数据传输时不 需要再执行步骤 601-602。
603、 MTC-IW接收服务器发送的第一消息。
该步骤与上述实施例中的步骤 301类似， 对此本实施例不再赘述。
604、 MTC-IW获取本地与 UE的服务节点之间的通道， 通过所述通道向 UE的服务节 点发送第二消息。
由于 MTC-IWF与 UE的服务节点已建立了通道， 所以在下行数据的传输中， MTC-IWF 只需找到其与 UE的服务节点间的通道即可， 不需要再向 HLR/HSS查询。
可选地， 可以将 UE的外部标识转换为内部标识， 将 UE的内部标识携带在第二消息 中与下行数据一起发送给 UE的服务节点上。
605、 UE的服务节点将所述下行数据发送给 UE。
此步骤与上述实施例中的步骤 305类似， 对此本实施例不再赘述。
值得说明的是， 本实施例中在 MTC-IWF与 UE的服务节点建立了通道后， 对于上行 数据的传输， UE的服务节点可以将上行数据通过通道发送给 MTC-IWF, 当然， 上行数据 的传输也可以按照现有技术的方法进行传输， 对此本实施例并不做具体限定。
本实施例的有益效果是： 由 UE的服务节点发起， 在 UE的服务节点和 MTC-IWF之间 建立通道， 通过通道将下行数据直接发送给 UE的服务节点， 从而在下行数据传输中无 需查询 HLR/HSS。 本实施例中提供了一种下行传输数据的方法， 本实施例中由 MTC-IWF发起， 在 UE 的服务节点和 MTC-IWF之间建立通道，通过通道将下行数据直接发送给 UE的服务节点， 从而在下行数据传输中无需查询 HLR/HSS。 参见图 7， 具体的方法流程包括：
701、 MTC-IW接收服务器发送的第一消息。
该步骤与上述实施例中的步骤 301类似， 对此本实施例不再赘述。
702、 MTC-IWF判断本地是否有所述 UE的服务节点信息， 如果是则执行步骤 705， 否则执行步骤 703。 703、 MTC-IWF向 HLR/HSS发送获取所述 UE的服务节点信息或者签约信息的请求。 本实施例中与步骤 303—样， 如果 MTC-IWF未在本地找到 UE的服务节点信息， 则 需要先向 HLR/HSS获取 UE的服务节点信息。 具体的获取方法与步骤 303中的查询方法 类似， 对此本实施例不再赘述。
704、 MTC-IWF向 UE的服务节点发送创建会话请求， 以与 UE的服务节点建立通道。 本实施例中， 在查询到 UE所在服务节点信息之后， 向 UE的服务节点发送创建会话 请求， 其中， 请求消息中携带 MTC-IWF的地址信息和通道标识， 其中根据创建的类型可 以是用户面通道标识， 或者控制面通道标识。
可选地， 请求消息中还可以携带 UE的标识信息， 例如 UE的 IMSI和 /或 UE外部标 识， 以在 3GPP网络内部标识该 UE， 对此本实施例并不做具体限定。
UE的服务节点接收到 MTC-IWF发送的创建会话请求后，向 MTC-IWF返回创建会话响 应， 其中响应消息中携带服务节点的地址信息和通道标识， 其中根据创建的类型可以是 用户面通道标识， 或者控制面通道标识。
MTC-IWF接收所述服务节点返回的创建会话响应， 与所述服务节点建立通道。 具体 的 MTC-IWF接收 UE的服务节点发送创建会话响应， 与所述服务节点建立通道的过程与 现有技术类似， 对此本实施例不再赘述。
值得说明的是， MTC-IWF的通道标识可以是通用的通道标识， 或者是为小数据传输 预留或专门分配的通道标识。 UE的服务节点的通道标识可以是通用的通道标识，或者是 为小数据传输预留或专门分配的通道标识， 对此本实施例不做具体限定。
本实施例中， 在 MTC-IWF发送下行数据时， 如果 MTC-IWF未与 UE的服务节点建立 通道， 则 MTC-IWF可以向 UE的服务节点发起会话请求， 但是这不是 MTC-IWF发起创建 会话请求的唯一触发条件， 在其它场景下， 也可能触发 MTC-IWF发起创建会话请求。 例 如 HLR/HSS收到新 UE的服务节点发送的位置更新消息后， HLR/HSS通知 MTC-IWF该 UE 当前的服务节点信息， 使 MTC-IWF向 UE的新的服务节点发起会话请求； 或者， 当 UE附 着时， UE的服务节点向 HLR/HSS发送位置更新消息， HLR/HSS向 MTC-IWF发送包含 UE 的服务节点信息的消息， 使 MTC-IWF向 UE的新的服务节点发起会话请求。
值得说明的是， 步骤 703-704是 MTC-IWF与 UE的服务节点还未建立通道时需要执 行的步骤， 如果 MTC-IWF与 UE的服务节点已建立了通道， 则在下行数据传输时不需要 再执行步骤 703-704。
705、 MTC-IW获取本地与所述用户设备的服务节点之间的通道， 通过所述通道向所 述用户设备的服务节点发送第二消息。 706、 UE的服务节点将所述下行数据发送给 UE。
其中，步骤 705-706与上述实施例中的步骤 604-605类似，对此本实施例不再赘述。 本实施例的有益效果是： 由 MTC-IWF发起， 在 UE的服务节点和 MTC-IWF之间建立 通道， 通过通道将下行数据直接发送给 UE的服务节点， 从而在下行数据传输中无需查 询 HLR/HSS。 参见图 8， 本实施例中提供了一种机器类型通信的互操作设备 MTC-IWF, 包括： 接 收模块 801和处理模块 802。
接收模块 801， 用于接收服务器发送的第一消息， 所述第一消息中包括需要发送给 用户设备的下行数据；
处理模块 802， 用于获取 MTC-IWF存储的所述用户设备的服务节点信息， 根据所述 用户设备的服务节点信息向所述用户设备的服务节点发送第二消息，所述第二消息中包 括所述需要发送给所述用户设备的下行数据，使所述服务节点将所述下行数据发送给所 述用户设备。
可选地， 参见图 9， 所述设备还包括：
第一注册 /订阅模块 803，用于在所述处理模块获取 MTC-IWF存储的所述用户设备的 服务节点信息之前， 向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节 点信息或者签约信息的请求， 并向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用 户设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时 能够返回所述变化后的所述用户设备的服务节点信息； 接收并保存所述 HLR/HSS返回的 所述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返回的签约信息响应消息， 并保 存所述签约信息响应消息中携带的所述用户设备的服务节点信息。
可选地， 参见图 9， 所述设备还包括：
获取模块 804， 用于在所述处理模块获取 MTC-IWF存储的所述用户设备的服务节点 信息之前， 向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请求； 接 收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返 回的签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设备的服务节 点信息。
可选地， 参见图 9， 所述设备还包括：
第二注册 /订阅模块 805，用于在所述获取模块 804向 HLR/HSS发送获取所述用户设 备的服务节点信息或者签约信息的请求之后， 向所述 HLR/HSS注册 /订阅 /请求所述用户 设备和所述用户设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节 点发生变化时能够返回所述变化后的所述用户设备的服务节点信息。
可选地， 参见图 9， 所述设备还包括：
第一创建模块 806， 用于在所述获取模块 804向 HLR/HSS发起获取所述用户设备的 服务节点信息或签约信息的请求之后， 向所述用户设备的服务节点发送第一创建关联 / 绑定请求， 使所述用户设备的服务节点返回第一创建关联 /绑定响应； 接收所述服务节 点返回的第一创建关联 /绑定响应， 从而与所述服务节点建立关联 /绑定关系。
可选地， 参见图 9， 所述设备还包括：
第二创建模块 807， 用于在所述处理模块 802获取 MTC-IWF存储的所述用户设备的 服务节点信息之前， 接收所述用户设备的服务节点发送的第二创建关联 /绑定请求； 向 所述服务节点发送第二创建关联 /绑定响应， 从而与所述服务节点建立关联 /绑定关系。
可选地， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小 数据或小数据传输的信息， 或指示所述下行数据为频繁小数据或频繁小数据传输的信 息， 或指示所述下行数据之后还有下行小数据的信息， 或指示注册 /订阅 /请求所述用户 设备和所述用户设备的服务节点的关联的信息，使所述 MTC-IWF能够根据所述指示信息 确认是否需要向 HLR/HSS注册 /订阅 /请求所述用户设备的服务节点信息， 或确认是否需 要与所述用户设备的服务节点建立关联 /绑定关系。
本实施例的有益效果是： MTC-IWF接收服务器发送的第一消息， 所述第一消息中包 括需要发送给用户设备的下行数据； 在本地获取所述用户设备的服务节点信息， 根据所 述 UE的服务节点信息向所述 UE的服务节点发送第二消息，使所述服务节点将所述下行 数据发送给所述用户设备。从而不需要向 HLR/HSS进行查询就能够将数据传输给服务节 点， 减少了下行数据传输中对 HLR/HSS查询频繁的问题。 参见图 10， 本实施例中提供了一种机器类型通信的互操作设备 MTC-IWF, 所述设备 包括： 接收模块 901和处理模块 902。
接收模块 901， 用于接收服务器下发的第一消息， 所述第一消息中包括需要发送给 用户设备的下行数据；
处理模块 902， 用于获取 MTC-IWF与所述用户设备的服务节点之间的通道， 通过所 述通道向所述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要发送给 所述用户设备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设备。
可选地， 参见图 11， 所述设备还包括： 获取模块 903， 用于在所述处理模块 902获取 MTC-IWF与所述用户设备的服务节点 之间的通道之前， 向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请 求； 接收并保存所述 HLR/HSS 返回的所述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设 备的服务节点信息。
可选地， 参见图 11， 所述设备还包括：
第一通道创建模块 904， 用于在所述获取模块 903向 HLR/HSS发起获取所述用户设 备的服务节点信息或者签约信息的请求之后， 向所述用户设备的服务节点发送第一创建 会话请求，所述第一创建会话请求中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通 道标识， 使所述用户设备的服务节点返回第一创建会话响应， 所述第一创建会话响应中 携带所述用户设备的服务节点的地址信息和所述用户设备的服务节点的通道标识； 接收 所述用户设备的服务节点返回的第一创建会话响应， 从而与所述用户设备的服务节点建 立通道。
可选地， 参见图 11， 所述设备还包括：
第二通道创建模块 904， 用于在所述处理模块 902获取 MTC-IWF与所述用户设备的 服务节点之间的通道之前， 接收所述用户设备的服务节点发送的第二创建会话请求， 所 述第二创建会话请求中携带所述用户设备的服务节点的地址信息和所述用户设备的服 务节点的通道标识； 向所述用户设备的服务节点返回第二创建会话响应， 所述第二创建 会话响应中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 从而与所述用户 设备的服务节点建立通道。
可选地， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小 数据或小数据传输的信息， 或指示所述下行数据为频繁小数据或频繁小数据传输的信 息， 或指示所述下行数据之后还有下行小数据的信息， 或指示建立通道的信息， 使所述 MTC-IWF能够根据所述指示信息确认是否需要与所述用户设备的服务节点建立通道。
本实施例的有益效果是： MTC-IWF接收服务器发送的第一消息， 所述第一消息中包 括需要发送给用户设备的下行数据； 获取本地与所述用户设备的服务节点之间的通道， 通过所述通道向所述用户设备的服务节点发送第二消息，使所述服务节点将所述下行数 据发送给所述用户设备。从而不需要向 HLR/HSS进行查询就能够将数据传输给服务节点， 减少了下行数据传输中对 HLR/HSS查询频繁的问题。 参见图 12，本实施例中提供了一种机器类型通信的互操作设备 MTC-IWF,所述设备， 所述设备包括： 处理器 1001和存储器 1002。
存储器 1002， 用于存储用户设备的服务节点信息；
所述处理器 1001，用于接收服务器发送的第一消息，所述第一消息中包括需要发送 给用户设备的下行数据； 获取存储器 1002 中存储的所述用户设备的服务节点信息， 根 据所述用户设备的服务节点信息向所述用户设备的服务节点发送第二消息，所述第二消 息中包括所述需要发送给所述用户设备的下行数据，使所述服务节点将所述下行数据发 送给所述用户设备。
可选地，所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息之前，还包括： 所述 MTC-IWF向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点 信息或者签约信息的请求， 并向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户 设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能 够返回所述变化后的所述用户设备的服务节点信息；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
可选地，所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息之前，还包括： 所述 MTC-IWF向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请 求；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
可选地，所述 MTC-IWF向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约 信息的请求之后， 还包括：
所述 MTC-IWF向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户设备的服务 节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能够返回所述 变化后的所述用户设备的服务节点信息。
可选地，所述 MTC-IWF向 HLR/HSS发起获取所述用户设备的服务节点信息或签约信 息的请求之后， 还包括：
所述 MTC-IWF 向所述用户设备的服务节点发送第一创建关联 /绑定请求， 使所述用 户设备的服务节点返回第一创建关联 /绑定响应；
所述 MTC-IWF接收所述服务节点返回的第一创建关联 /绑定响应， 从而与所述服务 节点建立关联 /绑定关系。
可选地，所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息之前，还包括： 所述 MTC-IWF接收所述用户设备的服务节点发送的第二创建关联 /绑定请求； 所述 MTC-IWF 向所述服务节点发送第二创建关联 /绑定响应， 从而与所述服务节点 建立关联 /绑定关系。
可选地， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小 数据或小数据传输的信息， 或指示所述下行数据为频繁小数据或频繁小数据传输的信 息， 或指示所述下行数据之后还有下行小数据的信息， 或指示注册 /订阅 /请求所述用户 设备和所述用户设备的服务节点的关联的信息，使所述 MTC-IWF能够根据所述指示信息 确认是否需要向 HLR/HSS注册 /订阅 /请求所述用户设备的服务节点信息， 或确认是否需 要与所述用户设备的服务节点建立关联 /绑定关系。 参见图 13，本实施例中提供了一种机器类型通信的互操作设备 MTC-IWF,所述设备， 所述设备包括： 处理器 2001和存储器 2002。
所述存储器 2002， 用于存储用户设备的服务节点的地址信息和通道标识信息； 所述处理器 2001，用于接收服务器下发的第一消息，所述第一消息中包括需要发送 给用户设备的下行数据； 获取 MTC-IWF与所述用户设备的服务节点之间的通道， 通过所 述通道向所述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要发送给 所述用户设备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设备。
可选地， 所述 MTC-IWF获取本地与所述用户设备的服务节点之间的通道之前， 还包 括：
所述 MTC-IWF向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点 信息或者签约信息的请求；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
可选地，所述 MTC-IWF向 HLR/HSS发起获取所述用户设备的服务节点信息或者签约 信息的请求之后， 还包括：
所述 MTC-IWF向所述用户设备的服务节点发送第一创建会话请求，所述第一创建会 话请求中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识，使所述用户设备的 服务节点返回第一创建会话响应，所述第一创建会话响应中携带所述用户设备的服务节 点的地址信息和所述用户设备的服务节点的通道标识；
所述 MTC-IWF接收所述用户设备的服务节点返回的第一创建会话响应， 从而与所述 用户设备的服务节点建立通道。
可选地， 所述 MTC-IWF获取本地与所述用户设备的服务节点之间的通道之前， 还包 括：
所述 MTC-IWF接收所述用户设备的服务节点发送的第二创建会话请求，所述第二创 建会话请求中携带所述用户设备的服务节点的地址信息和所述用户设备的服务节点的 通道标识；
所述 MTC-IWF向所述用户设备的服务节点返回第二创建会话响应，所述第二创建会 话响应中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 从而与所述用户设 备的服务节点建立通道。
可选地， 所述第一消息中还包括指示信息， 所述第一消息中还包括指示信息， 所述 指示信息： 指示所述下行数据为小数据或小数据传输的信息， 或指示所述下行数据为频 繁小数据或频繁小数据传输的信息， 或指示所述下行数据之后还有下行小数据的信息， 或指示建立通道的信息，使所述 MTC-IWF能够根据所述指示信息确认是否需要与所述用 户设备的服务节点建立通道。
本实施例的有益效果是： MTC-IWF接收服务器发送的第一消息， 所述第一消息中包 括需要发送给用户设备的下行数据； 获取本地与所述用户设备的服务节点之间的通道， 通过所述通道向所述用户设备的服务节点发送第二消息，使所述服务节点将所述下行数 据发送给所述用户设备。从而不需要向 HLR/HSS进行查询就能够将数据传输给服务节点， 减少了下行数据传输中对 HLR/HSS查询频繁的问题。 需要说明的是： 上述实施例提供的机器类型通信的互操作设备中， 仅以上述各功能 模块的划分进行举例说明， 实际应用中， 可以根据需要而将上述功能分配由不同的功能 模块完成， 即将设备的内部结构划分成不同的功能模块， 以完成以上描述的全部或者部 分功能。
另外， 上述实施例提供的机器类型通信的互操作设备与下行数据传输的方法实施例 属于同一构思， 其具体实现过程详见方法实施例， 这里不再赘述。
上述本发明实施例序号仅仅为了描述， 不代表实施例的优劣。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来 完成， 也可以通过程序来指令相关的硬件完成， 所述的程序可以存储于一种计算机可读 存储介质中， 上述提到的存储介质可以是只读存储器， 磁盘或光盘等。
以上所述仅为本发明的较佳实施例， 并不用以限制本发明， 凡在本发明的精神和原 则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求
1、 一种下行传输数据的方法， 其特征在于， 所述方法包括：
机器类型通信的互操作设备 MTC-IWF接收服务器发送的第一消息，所述第一消息中 包括需要发送给用户设备的下行数据；
所述 MTC-IWF获取本地存储的所述用户设备的服务节点信息，根据所述用户设备的 服务节点信息向所述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要 发送给所述用户设备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设 备。
2、 根据权利要求 1所述的方法， 其特征在于， 所述 MTC-IWF获取本地存储的所述 用户设备的服务节点信息之前， 还包括：
所述 MTC-IWF向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点 信息或者签约信息的请求， 并向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户 设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能 够返回所述变化后的所述用户设备的服务节点信息；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
3、 根据权利要求 1所述的方法， 其特征在于， 所述 MTC-IWF获取本地存储的所述 用户设备的服务节点信息之前， 还包括：
所述 MTC-IWF向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请 求；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
4、 根据权利要求 3所述的方法， 其特征在于， 所述 MTC-IWF向 HLR/HSS发送获取 所述用户设备的服务节点信息或者签约信息的请求之后， 还包括：
所述 MTC-IWF向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户设备的服务 节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能够返回所述 变化后的所述用户设备的服务节点信息。
5、 根据权利要求 3所述的方法， 其特征在于， 所述 MTC-IWF向 HLR/HSS发起获取 所述用户设备的服务节点信息或签约信息的请求之后， 还包括：
所述 MTC-IWF 向所述用户设备的服务节点发送第一创建关联 /绑定请求， 使所述用 户设备的服务节点返回第一创建关联 /绑定响应；
所述 MTC-IWF接收所述服务节点返回的第一创建关联 /绑定响应， 从而与所述服务 节点建立关联 /绑定关系。
6、 根据权利要求 1所述的方法， 其特征在于， 所述 MTC-IWF获取本地存储的所述 用户设备的服务节点信息之前， 还包括：
所述 MTC-IWF接收所述用户设备的服务节点发送的第二创建关联 /绑定请求； 所述 MTC-IWF 向所述服务节点发送第二创建关联 /绑定响应， 从而与所述服务节点 建立关联 /绑定关系。
7、 根据权利要求 1所述的方法， 其特征在于， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小数据或小数据传输的信息， 或指示所述下行数据 为频繁小数据或频繁小数据传输的信息， 或指示所述下行数据之后还有下行小数据的信 息， 或指示注册 /订阅 /请求所述用户设备和所述用户设备的服务节点的关联的信息， 使 所述 MTC-IWF能够根据所述指示信息确认是否需要向 HLR/HSS注册 /订阅 /请求所述用户 设备的服务节点信息， 或确认是否需要与所述用户设备的服务节点建立关联 /绑定关系。
8、 一种下行传输数据的方法， 其特征在于， 所述方法包括：
机器类型通信的互操作设备 MTC-IWF接收服务器下发的第一消息，所述第一消息中 包括需要发送给用户设备的下行数据；
所述 MTC-IWF获取本地与所述用户设备的服务节点之间的通道，通过所述通道向所 述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要发送给所述用户设 备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设备。
9、 根据权利要求 8所述的方法， 其特征在于， 所述 MTC-IWF获取本地与所述用户 设备的服务节点之间的通道之前， 还包括： 所述 MTC-IWF向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点 信息或者签约信息的请求；
所述 MTC-IWF接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 所述 MTC-IWF接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响 应消息中携带的所述用户设备的服务节点信息。
10、 根据权利要求 9所述的方法， 其特征在于， 所述 MTC-IWF向 HLR/HSS发起获取 所述用户设备的服务节点信息或者签约信息的请求之后， 还包括：
所述 MTC-IWF向所述用户设备的服务节点发送第一创建会话请求，所述第一创建会 话请求中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识，使所述用户设备的 服务节点返回第一创建会话响应，所述第一创建会话响应中携带所述用户设备的服务节 点的地址信息和所述用户设备的服务节点的通道标识；
所述 MTC-IWF接收所述用户设备的服务节点返回的第一创建会话响应， 从而与所述 用户设备的服务节点建立通道。
11、 根据权利要求 8所述的方法， 其特征在于， 所述 MTC-IWF获取本地与所述用户 设备的服务节点之间的通道之前， 还包括：
所述 MTC-IWF接收所述用户设备的服务节点发送的第二创建会话请求，所述第二创 建会话请求中携带所述用户设备的服务节点的地址信息和所述用户设备的服务节点的 通道标识；
所述 MTC-IWF向所述用户设备的服务节点返回第二创建会话响应，所述第二创建会 话响应中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 从而与所述用户设 备的服务节点建立通道。
12、 根据权利要求 8所述的方法， 其特征在于， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小数据或小数据传输的信息， 或指示所述下行数据 为频繁小数据或频繁小数据传输的信息， 或指示所述下行数据之后还有下行小数据的信 息， 或指示建立通道的信息， 使所述 MTC-IWF能够根据所述指示信息确认是否需要与所 述用户设备的服务节点建立通道。
13、 一种机器类型通信的互操作设备 MTC-IWF, 其特征在于， 所述设备包括： 接收模块， 用于接收服务器发送的第一消息， 所述第一消息中包括需要发送给用户 设备的下行数据；
处理模块， 用于获取 MTC-IWF存储的所述用户设备的服务节点信息， 根据所述用户 设备的服务节点信息向所述用户设备的服务节点发送第二消息，所述第二消息中包括所 述需要发送给所述用户设备的下行数据，使所述服务节点将所述下行数据发送给所述用 户设备。
14、 根据权利要求 13所述的设备， 其特征在于， 所述设备还包括：
第一注册 /订阅模块， 用于在所述处理模块获取 MTC-IWF存储的所述用户设备的服 务节点信息之前， 向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点 信息或者签约信息的请求， 并向所述 HLR/HSS注册 /订阅 /请求所述用户设备和所述用户 设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生变化时能 够返回所述变化后的所述用户设备的服务节点信息； 接收并保存所述 HLR/HSS返回的所 述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返回的签约信息响应消息， 并保存 所述签约信息响应消息中携带的所述用户设备的服务节点信息。
15、 根据权利要求 13所述的设备， 其特征在于， 所述设备还包括：
获取模块，用于在所述处理模块获取 MTC-IWF存储的所述用户设备的服务节点信息 之前， 向 HLR/HSS发送获取所述用户设备的服务节点信息或者签约信息的请求； 接收并 保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返回的 签约信息响应消息， 并保存所述签约信息响应消息中携带的所述用户设备的服务节点信 息。
16、 根据权利要求 15所述的设备， 其特征在于， 所述设备还包括：
第二注册 /订阅模块， 用于在所述获取模块向 HLR/HSS发送查询所述用户设备的服 务节点信息或者签约信息的请求之后， 向所述 HLR/HSS注册 /订阅 /请求所述用户设备和 所述用户设备的服务节点的关联，使所述 HLR/HSS在获知所述用户设备的服务节点发生 变化时能够返回所述变化后的所述用户设备的服务节点信息。
17、 根据权利要求 15所述的设备， 其特征在于， 所述设备还包括：
第一创建模块，用于在所述获取模块向 HLR/HSS发起获取所述用户设备的服务节点 信息或签约信息的请求之后， 向所述用户设备的服务节点发送第一创建关联 /绑定请求， 使所述用户设备的服务节点返回第一创建关联 /绑定响应； 接收所述服务节点返回的第 一创建关联 /绑定响应， 从而与所述服务节点建立关联 /绑定关系。
18、 根据权利要求 13所述的设备， 其特征在于， 所述设备还包括：
第二创建模块，用于在所述处理模块获取 MTC-IWF存储的所述用户设备的服务节点 信息之前， 接收所述用户设备的服务节点发送的第二创建关联 /绑定请求； 向所述服务 节点发送第二创建关联 /绑定响应， 从而与所述服务节点建立关联 /绑定关系。
19、 根据权利要求 13所述的设备， 其特征在于， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小数据或小数据传输的信息， 或指示所述下行数据 为频繁小数据或频繁小数据传输的信息， 或指示所述下行数据之后还有下行小数据的信 息， 或指示注册 /订阅 /请求所述用户设备和所述用户设备的服务节点的关联的信息， 使 所述 MTC-IWF能够根据所述指示信息确认是否需要向 HLR/HSS注册 /订阅 /请求所述用户 设备的服务节点信息， 或确认是否需要与所述用户设备的服务节点建立关联 /绑定关系。
20、 一种机器类型通信的互操作设备 MTC-IWF, 其特征在于， 所述设备包括： 接收模块， 用于接收服务器下发的第一消息， 所述第一消息中包括需要发送给用户 设备的下行数据；
处理模块， 用于获取 MTC-IWF与所述用户设备的服务节点之间的通道， 通过所述通 道向所述用户设备的服务节点发送第二消息，所述第二消息中包括所述需要发送给所述 用户设备的下行数据， 使所述服务节点将所述下行数据发送给所述用户设备。
21、 根据权利要求 20所述的设备， 其特征在于， 所述设备还包括：
获取模块，用于在所述处理模块获取 MTC-IWF与所述用户设备的服务节点之间的通 道之前， 向归属位置 /用户寄存器 HLR/HSS发送获取所述用户设备的服务节点信息或者 签约信息的请求； 接收并保存所述 HLR/HSS返回的所述用户设备的服务节点信息； 或， 接收所述 HLR/HSS返回的签约信息响应消息， 并保存所述签约信息响应消息中携带的所 述用户设备的服务节点信息。
22、 根据权利要求 21所述的设备， 其特征在于， 所述设备还包括： 第一通道创建模块，用于在所述获取模块向 HLR/HSS发起获取所述用户设备的服务 节点信息或者签约信息的请求之后， 向所述用户设备的服务节点发送第一创建会话请 求，所述第一创建会话请求中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 使所述用户设备的服务节点返回第一创建会话响应，所述第一创建会话响应中携带所述 用户设备的服务节点的地址信息和所述用户设备的服务节点的通道标识； 接收所述用户 设备的服务节点返回的第一创建会话响应， 从而与所述用户设备的服务节点建立通道。
23、 根据权利要求 20所述的设备， 其特征在于， 所述设备还包括：
第二通道创建模块，用于在所述处理模块获取 MTC-IWF与所述用户设备的服务节点 之间的通道之前， 接收所述用户设备的服务节点发送的第二创建会话请求， 所述第二创 建会话请求中携带所述用户设备的服务节点的地址信息和所述用户设备的服务节点的 通道标识； 向所述用户设备的服务节点返回第二创建会话响应， 所述第二创建会话响应 中携带所述 MTC-IWF的地址信息和所述 MTC-IWF的通道标识， 从而与所述用户设备的服 务节点建立通道。
24、 根据权利要求 20所述的设备， 其特征在于， 所述第一消息中还包括指示信息， 所述指示信息： 指示所述下行数据为小数据或小数据传输的信息， 或指示所述下行数据 为频繁小数据或频繁小数据传输的信息， 或指示所述下行数据之后还有下行小数据的信 息， 或指示建立通道的信息， 使所述 MTC-IWF能够根据所述指示信息确认是否需要与所 述用户设备的服务节点建立通道。
PCT/CN2013/086261 2012-11-02 2013-10-30 下行传输数据的方法和设备 WO2014067466A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP13852149.7A EP2861000B1 (en) 2012-11-02 2013-10-30 Method and device for transmitting downlink data
US14/586,095 US9681257B2 (en) 2012-11-02 2014-12-30 Data downlink transmission method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210433549.0A CN103796188B (zh) 2012-11-02 2012-11-02 下行传输数据的方法和设备
CN201210433549.0 2012-11-02

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/586,095 Continuation US9681257B2 (en) 2012-11-02 2014-12-30 Data downlink transmission method and device

Publications (1)

Publication Number Publication Date
WO2014067466A1 true WO2014067466A1 (zh) 2014-05-08

Family

ID=50626505

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/086261 WO2014067466A1 (zh) 2012-11-02 2013-10-30 下行传输数据的方法和设备

Country Status (4)

Country Link
US (1) US9681257B2 (zh)
EP (1) EP2861000B1 (zh)
CN (1) CN103796188B (zh)
WO (1) WO2014067466A1 (zh)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170111929A1 (en) * 2014-03-07 2017-04-20 Telefonaktiebolaget Lm Ericsson (Publ) Handling messages
CN105338615B (zh) * 2014-08-12 2019-12-03 中兴通讯股份有限公司 用户设备的注册方法、实体及系统
US10547543B2 (en) * 2015-06-24 2020-01-28 Futurewei Technologies, Inc. Elegant temporal label switched path tunnel service controller
US10498640B2 (en) 2015-09-04 2019-12-03 Futurewei Technologies, Inc. PCE for temporal tunnel services
US10555202B1 (en) * 2019-02-20 2020-02-04 Oracle International Corporation Methods, systems, and computer readable media for monitoring internet of things (IoT) device state through service capability exposure function (SCEF)
US10945120B2 (en) 2019-02-27 2021-03-09 Oracle International Corporation Methods, systems, and computer readable media for dynamically provisioning and using public land mobile network (PLMN) location mappings in service capability exposure function (SCEF) or network exposure function (NEF)
US10791044B1 (en) 2019-03-29 2020-09-29 Oracle International Corporation Methods, system, and computer readable media for handling multiple versions of same service provided by producer network functions (NFs)
US10742744B1 (en) 2019-04-08 2020-08-11 Oracle International Corporation Methods, systems, and computer readable media for monitoring lightweight machine to machine (LWM2M) internet of things (IoT) devices through service capability exposure funtion (SCEF) T8 interface
US10972368B2 (en) 2019-05-17 2021-04-06 Oracle International Corporation Methods, systems, and computer readable media for providing reduced signaling internet of things (IoT) device monitoring
US10819636B1 (en) 2019-06-26 2020-10-27 Oracle International Corporation Methods, systems, and computer readable media for producer network function (NF) service instance wide egress rate limiting at service communication proxy (SCP)
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
US11895080B2 (en) 2021-06-23 2024-02-06 Oracle International Corporation Methods, systems, and computer readable media for resolution of inter-network domain names
CN114500635A (zh) * 2022-01-07 2022-05-13 支付宝(杭州)信息技术有限公司 服务处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238571A (zh) * 2010-04-27 2011-11-09 中兴通讯股份有限公司 物联网m2m业务处理的装置、系统以及方法
CN102333293A (zh) * 2011-09-21 2012-01-25 电信科学技术研究院 一种小数据的传输方法和设备
CN102404710A (zh) * 2010-09-10 2012-04-04 华为终端有限公司 机器类型通信设备的签约数据管理方法、设备及系统
CN102413453A (zh) * 2010-09-21 2012-04-11 中兴通讯股份有限公司 一种mtc设备用户号码的共享方法和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101746668B1 (ko) 2010-12-21 2017-06-13 한국전자통신연구원 접속해제 상태의 사물통신 디바이스를 위한 데이터 전송 방법 및 이를 이용하는 이동통신 시스템
EP2509345A1 (en) * 2011-04-05 2012-10-10 Panasonic Corporation Improved small data transmissions for machine-type-communication (MTC) devices
CN102340826B (zh) * 2011-11-17 2016-05-25 电信科学技术研究院 一种数据传输的方法和设备
CN102547658B (zh) * 2011-12-22 2015-04-15 电信科学技术研究院 一种数据传输方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238571A (zh) * 2010-04-27 2011-11-09 中兴通讯股份有限公司 物联网m2m业务处理的装置、系统以及方法
CN102404710A (zh) * 2010-09-10 2012-04-04 华为终端有限公司 机器类型通信设备的签约数据管理方法、设备及系统
CN102413453A (zh) * 2010-09-21 2012-04-11 中兴通讯股份有限公司 一种mtc设备用户号码的共享方法和系统
CN102333293A (zh) * 2011-09-21 2012-01-25 电信科学技术研究院 一种小数据的传输方法和设备

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US9681257B2 (en) 2017-06-13
US20150110000A1 (en) 2015-04-23
CN103796188B (zh) 2017-06-06
EP2861000B1 (en) 2017-08-02
EP2861000A1 (en) 2015-04-15
EP2861000A4 (en) 2015-10-07
CN103796188A (zh) 2014-05-14

Similar Documents

Publication Publication Date Title
WO2014067466A1 (zh) 下行传输数据的方法和设备
US11871295B2 (en) Registration management method for terminal accessing 5G network on non-3GPP access
EP3566509B1 (en) Registration management method for terminal accessing 5g network on non-3gpp access
EP3836581B1 (en) Information processing method and system, and mobility management network element
US9473877B2 (en) Uplink/downlink transmission method for small amount of data, and corresponding terminal and mobility management unit
WO2016145735A1 (zh) 基于终端直连通信的数据共享方法、装置和终端
US20130136032A1 (en) Method and apparatus for managing communications of a physical network entity
TW201225599A (en) A method and device for initiating one-to-many communication process by a network in a communication system
WO2013091397A1 (zh) 一种数据传输方法及装置
WO2013060225A1 (zh) 一种通过用户承载标识获取用户位置的系统和方法
WO2013163945A1 (zh) 一种机器类通信事件的上报方法及相应装置
WO2015089969A1 (zh) 一种m2m终端/终端外设的可及性管理方法及设备
WO2014079312A1 (zh) 一种确定用户设备之间邻近关系的方法、设备及通信系统
WO2014063578A1 (zh) 一种短消息信令优化方法、设备和系统
US9445441B2 (en) System and method for processing trigger messages of a terminal
KR20030055417A (ko) Ｉｐ 멀티미디어 서비스 가입자의 이동성 관리를 위한가입자 데이터 관리 장치 및 방법
WO2013067773A1 (zh) 一种终端触发消息有效时间控制方法及系统
US9282439B1 (en) Systems and methods of wireless device push-to-talk registration
WO2009015584A1 (fr) Procédé, système et dispositif servant à réaliser un enregistrement d'un équipement utilisateur dans un réseau personnel
WO2013091303A1 (zh) 终端触发消息处理方法、系统及相关网元
CN117795991A (zh) 一种用于边缘计算中的位置服务的方法
WO2011124179A2 (zh) 一种机器类型通信的方法、装置及系统
WO2012151951A1 (zh) 一种终端触发的方法及系统
WO2011035648A1 (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: 13852149

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2013852149

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE