WO2012130098A1 - 一种获取机器类型通信设备ip地址的方法及系统 - Google Patents

一种获取机器类型通信设备ip地址的方法及系统 Download PDF

Info

Publication number
WO2012130098A1
WO2012130098A1 PCT/CN2012/072906 CN2012072906W WO2012130098A1 WO 2012130098 A1 WO2012130098 A1 WO 2012130098A1 CN 2012072906 W CN2012072906 W CN 2012072906W WO 2012130098 A1 WO2012130098 A1 WO 2012130098A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
mtc device
address
identity
server
Prior art date
Application number
PCT/CN2012/072906
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 中兴通讯股份有限公司
Publication of WO2012130098A1 publication Critical patent/WO2012130098A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • 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 relates to the field of mobile communications, and in particular, to a method and system for triggering an MTC device to initiate communication and acquire an IP address of an MTC device by a server type communication (MTC) server.
  • MTC server type communication
  • WiMax Worldwide Interoperability for Microwave Access
  • PS Core Packet Switched Core
  • UTRAN The evolution of the Universal Mobile Telecommunication System Radio Access Network
  • EPC evolved PS Core
  • UTRAN Global System for Mobile Communications Enhanced Data Rate for GSM Evolution radio access network (UTRAN).
  • UTRAN Wireless Local Area Network (WLAN) Mobility management between Network and other non-3GPP access networks.
  • This evolved mobile communication system is called the Evolved Packet System (EPS).
  • EPS Evolved Packet System
  • Fig. 1 is a schematic structural view of the above EPS system, and only some of the entities related to the embodiment of the present invention are shown in Fig. 1. The entities in Figure 1 are described as follows:
  • the mobile station (MS, Mobile Station) / User Equipment (UE, User Equipment) 101 has the ability to access the wireless network.
  • the MS may also be referred to as a mobile terminal.
  • GERAN/UTRAN 102 a wireless access network for traditional GSM/UMTS networks.
  • a Serving GPRS Support Node (SGSN) 103 is a control network element of a General Packet Radio Service (GPRS) network. The main function is to record the location information of the UE 101, and at the UE 101. The transmission and reception of mobile packet data is completed between the GPRS Gateway Support Node (GGSN) 106 and the GPRS Gateway Supporting Node (GGSN).
  • GGSN GPRS Gateway Support Node
  • GGSN GPRS Gateway Supporting Node
  • the Serving Gateway (S-GW) 104 is a user plane entity responsible for user plane data routing processing and terminating downlink data of the UE 101 in an idle (ECMJDLE) state.
  • the SAE bearer context of the UE 101 is managed and stored, such as IP bearer service parameters and network internal routing information.
  • the S-GW 104 is an anchor point for the internal user plane of the 3GPP system, and a user can only have one S-GW 104 at a time.
  • Packet Data Network Gateway (P-GW or PDN GW, Packet Data Network Gateway) 105, is responsible for The UE 101 accesses the gateway of the PDN, and allocates a user IP address, which is also a mobility anchor of the 3GPP and the non-3GPP access system.
  • the functions of the P-GW 105 further include policy implementation and charging support.
  • the user can access multiple P-GWs 105 at the same time.
  • the Policy and Charging Enforcement Function (PCEF) is also located in the P-GW.
  • PCEF Policy and Charging Enforcement Function
  • P-GW 105 and S-GW 104 may be located in one physical entity or in different physical entities, as shown in FIG.
  • the GGSN 106 supports the edge routing function of the GPRS network, that is, the GGSN 106 is responsible for routing and forwarding data of the GPRS network, and protecting the integrity of the GPRS network data through a firewall and a filtering function.
  • the GGSN also has a billing function.
  • the P-GW 105 includes all of the functions of the GGSN 106, i.e., the GGSN 106 is considered to be a sub-function of the P-GW 105, embedded in the P-GW 105. Therefore, the SGSN 103 can be directly connected to the P-GW 105, using the Gn/Gp interface.
  • the Home Subscriber Server (HSS) / Home Location Register (HLR) 107 is the primary user database that supports invocation/session.
  • the network When the UE establishes communication with the network to use the service, the network needs to assign an IP address to the network.
  • the network may allocate an IPv4 address to the UE, or may allocate an IPv6 prefix to the UE.
  • IPv4 address For R8 and subsequent EPS networks, a Packet Data Protocol (PDP) context or an EPS bearer supports both IPv4 and IPv6 addresses, so for UEs that support dual stacks, they can apply for IPv4 allocation to the network. Address, IPv6 prefix or IPv4 address and IPv6 prefix.
  • PDP Packet Data Protocol
  • the IP address allocation of the UE may be performed through the attach procedure or the default bearer activation of the PDN connection procedure requested by the UE:
  • the home public land mobile communication network (HPLMN) may allocate static to the UE.
  • the server is based on the user and APN granularity (per-user per-APN) configuration, or the HPLMN can assign a dynamic IP address to the UE, such as allocation on the P-GW; the visited public land mobile communication network (VPLMN) can allocate the UE Dynamic IP address, such as P-GW configuration in VPLMN; PDN operator or administrator can also assign dynamic or static IP address to UE through other address servers such as external DHCP Server or AAA Server. If the UE is not assigned an IP address after the process is complete, the subsequent UE may perform address allocation by using an IP address allocation mechanism defined by the Internet Engineering Task Force (IETF).
  • IETF Internet Engineering Task Force
  • the IP address allocation mechanism of the UE is similar to that of the EPS network, and will not be described here.
  • M2M machine-to-machine communication
  • a networked application and service centered on intelligent interaction of machine terminals. It is used in intelligent machine terminals to provide access information and information solutions for customers in a variety of communication modes. It is used to satisfy customers' monitoring, command and dispatch, data collection and measurement. Information needs.
  • M2M wireless technology
  • M2M can be applied to industrial applications, home applications, personal applications, and the like.
  • Industry applications such as: traffic monitoring, warning systems, marine rescue, vending machines, car payment, etc.
  • Home applications such as: automatic meter reading, temperature control, etc.
  • Personal applications such as: life detection, remote diagnosis, etc.
  • the communication objects of M2M are machine-to-machine and person-to-machine.
  • Data communication between one or more machines is defined as MTC, in which case less human interaction is required.
  • MTC participating machines defined as MTC device (MTC Device) 0 MTC MTC user equipment is a terminal
  • MTC server can communicate via a network PLMN MTC device.
  • the MTC Server manages and monitors MTC devices.
  • 2 is a schematic diagram of an MTC UE accessing an EPS system through E-UTRAN in the prior art
  • FIG. 3 is a schematic diagram of an MTC UE accessing a 3G system through UTRAN/GERAN in the prior art.
  • the following two network architectures may also be considered.
  • an operator can provide MTC services as a service provider. Therefore, the MTC server can be deployed and managed by the operator, or the third party providing the MTC service is trusted by the operator. In this case, you can consider establishing an interface between the MTC Server and the HLR.
  • Another architecture is shown in Figure 5.
  • the MTC Server may not be a network entity managed by the operator, and may be deployed outside the core network. Therefore, it involves MTC.
  • MTC gateway MTC gateway
  • MTC gateway MTC gateway
  • the MTC gateway can be hidden through the internal network topology.
  • the means for authenticating the access to the MTC Server to implement the security guarantee for the MTC Server to access the core network MTC gateway
  • the interface between the MTC Server or the newly added MTC gateway and the mobility management network element SGSN is added, and the service layer (the MTC server or the newly added MTC gateway) passes the mobility management network element.
  • the SGSN obtains information about the underlying access layer of the MTC terminal, and then controls access to the MTC terminal according to the obtained information of the MTC terminal.
  • the MTC Server is required to trigger the MTC device to initiate communication with the MTC Server for data transmission.
  • the MTC Server In addition to setting the MTC device to report the monitoring report to the MTC Server periodically, the MTC Server The MTC device is also requested to report the measurement data from time to time. In this case, the MTC Server needs to send an indication to the MTC device to trigger the MTC device to connect to the network or establish a data connection to communicate with the MTC Server.
  • the MTC device can be offline or online for the network, including: idle state and connection state.
  • the user plane channel of the UE is established and the UE is assigned an IP address, and the IP data packet of the UE can be transmitted in the user plane channel;
  • the idle state in the EPS network In the idle state, the UE is assigned an IP address.
  • an idle UE is not assigned an IP address.
  • the MTC device is online, if the MTC Server knows the IP address of the MTC device, the trigger data packet can be sent to the network, and the network uses the corresponding mechanism to find and trigger the MTC device.
  • the default bearer is established when the UE initially attaches to the network and is assigned to the IP address in the process, and is used by the UE before the UE is detached.
  • the MTC server is required to trigger the MTC device, the dynamic IP address assigned to the MTC device can be sent to the MTC server.
  • the specific method may be: after the MTC device obtains the IP address, the application layer interaction The IP address is notified to the MTC Server.
  • the UE When the UE accesses the 3G network through the GERAN/UTRAN, the UE does not assign an IP address when attaching, but obtains an IP address through a subsequent PDP context activation process.
  • the network needs to find a UE attached to the network but does not have a PDP context, the network needs to initiate a PDP context activation procedure for the network request.
  • the PDP context activation procedure of the network request only supports the static IP address of the UE, that is, the IP address of the UE is statically configured in advance, and the GGSN needs to know the international mobile subscriber identity of the UE (IMSI, International Mobile Subscriber). Identification Number) Pairing relationship with a static IP address.
  • IMSI international mobile subscriber identity of the UE
  • Step 601 The GGSN receives the PDP PDU data packet and determines the PDP context activation process that needs to initiate the network request.
  • Step 602 The GGSN queries the UE's IMSI according to the static IP address of the UE carried in the PDP PDU, and sends a "Send GPRS Routing Information" message to the HLR, which carries the IMSI of the UE.
  • Step 603 The HLR queries the IP address of the SGSN registered by the UE according to the IMSI of the UE, and returns a message “Send GPRS Routing Information Response”, which carries the IMSI of the UE and the IP address of the SGSN registered by the UE.
  • Step 604 The GGSN sends a "Packet Data Unit Notification Request" message to the SGSN, carrying the IMSI of the UE and the Access Point Name (APN, Access Point Name), requesting the SGSN to initiate a PDP context activation process of the network request.
  • APN Access Point Name
  • Step 605 The SGSN returns a "Packet Data Unit Notification Response" message to the GGSN.
  • Step 606 The SGSN sends a PDP Context Activation Request message to the UE, where the APN is required, and the UE is required to initiate a PDP context activation process according to the specified APN.
  • Step 607 The UE initiates a PDP context procedure and the network allocates an IP address for the UE.
  • the MTC server triggers the scenario in which the MTC device initiates communication with the MTC server, provided that the IP address of the MTC device is known to be feasible, and the MTC device that accesses the 3G network through the GERAN/UTRAN is followed by
  • the PDP context activation process obtains an IP address, and according to the current prior art, The PDP context activation process only supports the static IP address of the UE. Since IPv4 address resources are very limited and IPv6 addresses are not widely used, considering the effective use of address resources, dynamically assigning IP addresses will have a greater advantage than statically configured IP addresses in practical applications. The static IP address requires additional configuration for the network, which is more restrictive and not much in practical applications.
  • the MTC server triggers the MTC device to initiate communication with the MTC Server, it is not feasible to obtain a dynamically allocated IP address. That is, in the prior art, when the MTC device accesses the 3G network through GERAN/UTRAN, When a dynamic IP address is assigned, the MTC server cannot know the IP address of the MTC device. Therefore, the MTC device cannot be found through the network. Therefore, the MTC server cannot trigger the MTC device to initiate communication with the MTC Server.
  • the MTC device considering that the Mobile Subscriber International ISDN/PSTN Number is mainly used for voice communication and short message communication, for an MTC device that is in an online state, if the MTC device is assigned an MSISDN, The MTC device is triggered to initiate communication with the MTC Server by means of a short message.
  • MSISDN is allocated for each MTC device, it will inevitably lead to a shortage of MSISDN resources.
  • MSISDN may not be assigned, so it is impossible to trigger the MTC device to initiate communication with the MTC Server by means of short messages.
  • the main purpose of the embodiments of the present invention is to provide a method and system for acquiring an IP address of an MTC device, for an MTC device that accesses a 3G network through GERAN/UTRAN, but has no PDP context and thus is not assigned a dynamic IP address.
  • the MTC Server can trigger the MTC device to initiate communication with the MTC Server and obtain the IP address of the MTC device.
  • a method for obtaining an IP address of a machine type communication device comprising:
  • MTC machine type communication
  • the MTC server or the MTC gateway sends a trigger packet including an identity identifier and/or a trigger request of the MTC device; the network entity triggers the information corresponding to the identity identifier of the MTC device according to the identity identifier of the MTC device, and triggers
  • the Generic Wireless Packet Service Support Node SGSN
  • PDP Packet Request Protocol
  • the network entity specifically includes: a home location register (HLR) or a general wireless packet service gateway support node (GGSN); the identity of the MTC device specifically includes: a mobile subscriber international number (MSISDN) or an application layer identifier of the MTC device.
  • HLR home location register
  • GGSN general wireless packet service gateway support node
  • MSISDN mobile subscriber international number
  • the information corresponding to the identity of the MTC device includes:
  • the identity of the MTC device and the International Mobile Subscriber Identity (IMSI) are carried to the HLR through the interaction message between the SGSN and the HLR when the MTC device performs the attach procedure, the identity of the MTC device,
  • the correspondence between the access point names (APNs) corresponding to the IMSI and the MTC server is stored in the HLR; or the correspondence between the identity of the MTC device, the IMSI, and the APN corresponding to the MTC server is statically configured in the GGSN; or,
  • the PDP context activation process that triggers the SGSN to initiate a network request to allocate a dynamic IP address to the MTC device includes:
  • the MTC server or the MTC gateway sends the trigger packet to the GGSN, and the GGSN sends a GPRS routing information message to the HLR, where the GPRS routing information message carries the identity of the MTC device.
  • the HLR queries the IMSI of the MTC device, the IP address of the SGSN registered by the MTC device, and the APN corresponding to the MTC server corresponding to the MTC device according to the identity of the MTC device, and sends a GPRS routing information acknowledgement message to the GGSN, and sends the acknowledgement message to the GGSN.
  • the GPRS routing information acknowledgement message carries the IMSI of the MTC device, the IP address of the SGSN registered by the MTC device, and the APN corresponding to the MTC server corresponding to the MTC device; the GGSN is based on the IMSI of the MTC device and the IP of the SGSN registered by the MTC device.
  • the APN of the MTC server corresponding to the address and the MTC device triggers the PDP context activation process of the SGSN to initiate the network request, and allocates a dynamic IP address to the MTC device.
  • the PDP context activation process that triggers the SGSN to initiate a network request to allocate a dynamic IP address to the MTC device includes:
  • the MTC server or the MTC gateway sends the trigger packet to the GGSN, and the GGSN sends a GPRS routing information message to the HLR, where the GPRS routing information message carries the identity of the MTC device.
  • the HLR queries the IMSI of the MTC device and the IP address of the SGSN registered by the MTC device according to the identity of the MTC device, and sends a GPRS routing information confirmation message to the GGSN, and sends the IMS routing information confirmation message carrying the IMSI of the MTC device. , the IP address of the SGSN registered by the MTC device;
  • the GGSN queries the APN corresponding to the MTC server corresponding to the MTC device that is statically configured by the GGSN according to the identity of the MTC device, and the GGSN is based on the IMSI of the MTC device, the IP address of the SGSN registered by the MTC device, and the corresponding MTC device.
  • the APN corresponding to the MTC server triggers the PDP context activation process of the SGSN to initiate a network request to allocate a dynamic IP address to the MTC device.
  • the PDP context activation process that triggers the SGSN to initiate a network request to allocate a dynamic IP address to the MTC device includes:
  • the MTC server or the MTC gateway sends the trigger packet to the HLR, and the HLR is based on the body of the MTC device.
  • the identifier is queried to the IMSI of the MTC device, the IP address of the SGSN registered by the MTC device, and the APN corresponding to the MTC server corresponding to the MTC device, and returned to the MTC server or the MTC gateway;
  • the MTC server or the MTC gateway allocates a dynamic IP address to the MTC device according to the IMSI of the MTC device, the IP address of the SGSN registered by the MTC device, and the APN of the MTC server corresponding to the MTC device triggering the PDP context activation process of the SGSN to initiate the network request. .
  • the PDP context activation process that triggers the SGSN to initiate a network request to allocate a dynamic IP address to the MTC device includes:
  • the MTC server or the MTC gateway sends the trigger packet to the HLR, and the HLR queries the IMSI of the MTC device, the IP address of the SGSN registered by the MTC device, and the MTC server corresponding to the MTC device according to the identity identifier of the MTC device.
  • APN APN
  • the HLR sends a user equipment reachability notification request message to the SGSN, where the user equipment reachability notification request message carries an APN and a trigger request corresponding to the MTC server corresponding to the MTC device; the SGSN is according to the MTC device.
  • the PDP context activation process of the APN initiated by the MTC server corresponding to the MTC server corresponding to the IMSI and the MTC device allocates a dynamic IP address to the MTC device.
  • the transmitting the assigned IP address to the MTC server specifically includes: the GGSN notifying the MTC server of the assigned IP address after assigning the IP address to the MTC device; or
  • the MTC server After the MTC device obtains the assigned IP address, the MTC server is notified of the assigned IP address through application layer interaction.
  • a system for obtaining an IP address of a machine type communication device comprising: an information establishing unit and a dynamic IP address obtaining unit; wherein
  • An information establishing unit configured to establish, in the network entity, information corresponding to the identity of the MTC device; the dynamic IP address obtaining unit, configured to send, by the MTC server or the MTC gateway, a trigger packet that includes an identity identifier of the MTC device and/or a trigger request Transmitting, by the network entity, the information corresponding to the identity of the MTC device according to the identity of the MTC device, triggering the PDP context activation process initiated by the SGSN to request the network, assigning a dynamic IP address to the MTC device, and assigning the The IP address is passed to the MTC server to establish communication between the MTC device and the MTC server.
  • the network entity specifically includes: an HLR or a GGSN; the identity of the MTC device specifically includes: an application layer identifier of the MSISDN or the MTC device.
  • the information establishing unit is further configured to: when the information corresponding to the identity of the MTC device is used to be carried, to the HLR by using an interaction message between the SGSN and the HLR when the identity of the MTC device and the IMSI are attached to the MTC device.
  • the relationship between the identity of the MTC device, the IMSI, and the APN corresponding to the MTC server is stored in the HLR; or the correspondence between the identity of the MTC device, the IMSI, and the APN corresponding to the MTC server is statically configured.
  • the static relationship between the identity of the MTC device and the APN corresponding to the MTC server is statically configured in the GGSN;
  • the identity of the MTC device, the corresponding relationship between the IMSI and the APN corresponding to the MTC server are all stored in the HLR as subscription data of the MTC device.
  • the embodiment of the present invention establishes information corresponding to the identity of the MTC device in the network entity; the MTC server or the MTC gateway sends the trigger packet including the identity identifier of the MTC device and/or the trigger request; the network entity queries according to the identity identifier of the MTC device.
  • the information corresponding to the identity of the MTC device triggers the PDP context activation process initiated by the SGSN to initiate the network request, allocates a dynamic IP address to the MTC device, and transmits the assigned IP address to the MTC server, and establishes the MTC device and the MTC server. Communication between.
  • the PDP context activation process that triggers the SGSN to initiate the network request can allocate a dynamic IP address to the MTC device based on the information of the MTC device identity identification, so that the MTC server can trigger the MTC device to initiate communication with the MTC server. Obtain the IP address of the MTC device.
  • FIG. 1 is a schematic diagram of a 3G system and a GERAN/UTRAN access network architecture in the prior art
  • FIG. 2 is a schematic diagram of an MTC UE accessing an EPC system through an E-UTRAN in the prior art
  • FIG. 3 is a schematic diagram of an architecture of an MTC UE accessing a 3G system through GERAN/UTRAN in the prior art
  • FIG. 4 is another schematic diagram of an architecture of an MTC UE accessing a 3G system through GERAN/UTRAN in the prior art
  • FIG. 6 is a schematic flowchart of the PDP context activation of the network request in the prior art
  • FIG. 7 is a schematic flowchart of an MTC UE carrying an identity identifier to an HLR in an attach procedure according to Embodiment 1 of the present invention
  • FIG. 8 is a schematic diagram of a process in which an MTC Server or an MTC gateway sends a trigger packet to an MTC UE to initiate communication with an MTC UE according to Embodiment 2 of the present invention
  • FIG. 9 is a schematic diagram of a process in which an MTC Server or an MTC gateway sends a trigger packet trigger to an MTC UE to initiate communication with an MTC UE according to Embodiment 3 of the present invention
  • FIG. 10 is a schematic flowchart of a method in which an MTC Server sends a trigger packet to an MTC UE to trigger an MTC UE to initiate communication with the MTC server according to Embodiment 4 of the present invention
  • FIG. 11 is a schematic flowchart of a method in which an MTC Server sends a trigger packet to an MTC UE to trigger an MTC UE to initiate communication with the MTC server according to Embodiment 5 of the present invention
  • FIG. 12 is a schematic diagram of a process in which an MTC Server or an MTC gateway sends a trigger packet trigger to an MTC UE to initiate communication with an MTC UE according to Embodiment 6 of the present invention.
  • the basic idea of the embodiment of the present invention is: establishing information corresponding to the identity of the MTC device in the network entity; the MTC Server or the MTC gateway sending the trigger packet including the identity identifier of the MTC device and/or the trigger request; the network entity according to the MTC A letter corresponding to the identity of the MTC device queried by the identity identifier of the device.
  • the PDP context activation process that triggers the SGSN to initiate a network request, allocates a dynamic IP address to the MTC device, and transmits the assigned IP address to the MTC Server to establish communication between the MTC device and the MTC Server.
  • the embodiment of the present invention is a scheme for the MTC Server to trigger the MTC device to initiate communication and obtain the IP address of the MTC device.
  • the solution is for accessing the MTC device in the 3G network through the GERAN/UTRAN, but there is no PDP context and therefore no dynamic IP address is allocated.
  • the MTC device with a relatively fixed location or a relatively fixed motion area solves the problem that the MTC server in the network triggers the MTC device attached to the network but is not assigned a dynamic IP address to initiate communication with the MTC Server, thereby achieving the IP address.
  • the effective use of resources avoids the complexity and limitation of using static IP addresses to the network, and can also alleviate the problem of insufficient MSISDN resources caused by deploying a large number of MTC devices.
  • a method for obtaining an IP address of an MTC device which mainly includes the following contents:
  • the network entity A establishes a correspondence between the identity of the MTC device, the IMSI, and the APN corresponding to the MTC server, and the MTC Server or the MTC gateway sends a communication trigger packet including the trigger information to the network to trigger the PDP context activation process of the SGSN to initiate the network request.
  • a dynamic IP address is assigned to the MTC device, and the IP address is delivered to the MTC Server to establish communication between the MTC device and the MTC Server. This document refers to the MTC Server when the above relationship is established: The MTC Server corresponding to the identity of the MTC device is not described here.
  • the network entity A includes: an HLR or a GGSN.
  • the identity identifier of the MTC device includes: an application layer identifier of the MSISDN or the MTC device. Further, the identity of the MTC device, the corresponding relationship between the IMSI and the APN corresponding to the MTC server may be: the subscription data that is used as the MTC device is stored in the HLR;
  • establishing the identity of the MTC device the corresponding relationship between the IMSI and the APN corresponding to the MTC server, including: the identity of the MTC device and the IMSI, when the MTC device performs an attach procedure, passes the SGSN. After the interaction message with the HLR is carried to the HLR, the established relationship is implemented by the HLR.
  • the corresponding relationship established in this document refers to: the identity of the established MTC device, the corresponding relationship between the IMSI and the APN corresponding to the MTC Server, and will not be described.
  • the HLR may associate and save the identity of the MTC device with the APN corresponding to the MTC server; if the MTC device communicates with multiple MTC servers, the HLR will use the IMSI, the identity identifier of the MTC device, and The relationship of the APN corresponding to the MTC Server is associated and saved.
  • interaction message between the SGSN and the HLR includes: a location update message, or an insertion subscription data response message.
  • the corresponding relationship between the IMSI and the APN corresponding to the MTC server includes: statically configuring the established correspondences in the GGSN.
  • the correspondence between the IMSI and the APN corresponding to the MTC server including: the correspondence between the identity of the MTC device and the APN corresponding to the MTC server Statically configured in the GGSN.
  • the MTC Server or the MTC gateway saves the identity of the MTC device.
  • the communication trigger packet containing the trigger information sent by the MTC Server or the MTC gateway to the network carries the identity identifier and/or the trigger request of the MTC device.
  • the MTC Server or the MTC gateway sends a communication trigger packet to the network to trigger the SGSN to initiate a network request, and the PDP context activation process allocates a dynamic IP address to the MTC device, including: the MTC Server or the MTC gateway sends a communication trigger packet to the GGSN, and the GGSN sends
  • the HLR sends a "Send GPRS Routing Information" message, which carries the identity of the MTC device.
  • the HLR queries the IMSI of the MTC device, the address of the registered SGSN, and the APN corresponding to the MTC server corresponding to the identity of the MTC device according to the identity of the MTC device, and sends a “send GPRS route” to the GGSN.
  • the information acknowledgement message carries the IMSI of the MTC device, the address of the registered SGSN, and the APN corresponding to the MTC Server corresponding to the identity of the MTC device.
  • the GGSN triggers the PDP context activation process of the SGSN to initiate a network request according to the foregoing information to allocate a dynamic IP address to the MTC device.
  • the above information includes: an IMSI of the MTC device queried according to the identity of the MTC device, and an IP address of the SGSN registered by the MTC device according to the identity of the MTC device, according to the MTC device
  • the identity of the APN corresponding to the MTC Server is not described here.
  • the MTC Server or the MTC gateway sends a communication trigger packet to the network to trigger the SGSN to initiate a network request, and the PDP context activation process allocates a dynamic IP address to the MTC device, and further includes: the MTC Server or the MTC gateway sends a communication trigger packet to the GGSN, the GGSN Sending a "Send GPRS Routing Information" message to the HLR, which carries the identity of the MTC device.
  • the HLR queries the IMSI of the MTC device and the address of the registered SGSN according to the identity of the MTC device, and sends a "send GPRS routing information confirmation" message to the GGSN, where the IMSI carrying the MTC device and The address of the registered SGSN.
  • the GGSN further queries the APN corresponding to the MTC Server that is statically configured locally by the GGSN according to the identity of the MTC device.
  • the GGSN triggers the PDP context activation process initiated by the SGSN to initiate a network request according to the foregoing information, and allocates a dynamic IP address to the MTC device.
  • the MTC Server or the MTC gateway sends a communication trigger packet to the network to trigger the SGSN to initiate a network request, and the PDP context activation process allocates a dynamic IP address to the MTC device, and the method further includes: the MTC Server or the MTC gateway sends a communication trigger packet to the HLR.
  • the HLR that is queried by the HLR according to the content of the communication triggering packet and returned to the MTC server or the MTC device, the IMSI of the MTC device, the address of the registered SGSN, and the APN corresponding to the MTC server corresponding to the identity of the MTC device.
  • the MTC Server or the MTC gateway requests the SGSN to initiate a network request PDP context activation process according to the foregoing information, and allocates a dynamic IP address to the MTC device.
  • the MTC Server or the MTC gateway sends a communication trigger packet to the network to trigger the SGSN to initiate a network request
  • the PDP context activation process allocates a dynamic IP address to the MTC device
  • the MTC gateway sends a communication trigger packet to the HLR, and the HLR queries the IMSI of the MTC device, the address of the registered SGSN, and the APN corresponding to the MTC Server corresponding to the identity of the MTC device according to the content of the communication trigger packet.
  • the HLR sends a UE reachability notification request message to the SGSN, where the trigger request and the APN are carried.
  • the SGSN allocates a dynamic IP address to the MTC device according to the PDP context activation procedure of the information initiation network request.
  • the IP address is forwarded to the MTC Server, and the GGSN may notify the MTC Server of the IP address after assigning an IP address to the MTC device.
  • the IP address is transmitted to the MTC server, and the IP address is notified to the MTC server by the application layer interaction after the MTC device obtains the IP address.
  • the MTC device may specifically be an MTC UE.
  • Method Embodiment 1 The MTC UE carries its identity to the HLR in the attach procedure and saves it in the HLR local. As shown in FIG. 7, the process of this embodiment includes the following steps:
  • Step 701 The MTC UE sends an attach request (Attach Request) message to the SGSN via the access network GERAN/UTRAN, where the MTC UE carries the identity of the MTC UE, and the identity identifier may be the MSISDN of the MTC UE, or may be the application layer identifier of the MTC UE.
  • the application layer identifier can correspond to the MTC Server.
  • Step 702 Perform an authentication process between the MTC UE, the SGSN, and the HLR.
  • Step 703 The SGSN sends a location update message to the HLR, where the MTC UE carries the identity identifier, and the MTC device of the single application, that is, the MTC UE only communicates with one MTC Server, the HLR can correspond to the MTC UE identity identifier and the MTC Server.
  • the APN is associated and saved. If the MTC UE is a multi-application MTC device, that is, the MTC UE communicates with multiple MTC servers, the HLR can resolve the APN of the MTC Server corresponding to the identity identifier from the received identity identifier.
  • the HLR saves the relationship between the IMSI of the MTC UE, the identity, and the APN corresponding to the MTC Server.
  • Step 704 The HLR locally saves the identity identifier, and sends an insertion subscription data message to the SGSN.
  • Step 705 The SGSN returns an insertion subscription data response message to the HLR. At this time, if the SGSN does not carry the identity of the MTC UE in step 704, it is carried to the HLR in this step.
  • Step 706 The MTC UE continues to complete the subsequent attach procedure.
  • the MTC UE is attached to the 3G network, but the PDP context activation process or the PDP context activation process is performed but the PDP context deactivation process is performed, so the MTC UE is not assigned an IP address. .
  • the MTC UE is in this state, and details are not described herein.
  • Method Embodiment 2 The MTC Server or the MTC gateway sends a trigger packet to the MTC UE to trigger the MTC UE to initiate communication with it. As shown in FIG. 8, the process of this embodiment includes the following steps:
  • Step 801 The MTC Server sends a communication trigger packet to the GGSN. If there is an architecture of the MTC gateway, the MTC Server sends the communication trigger packet to the MTC gateway, and then the MTC gateway sends the communication trigger packet to the MTC gateway. GGSN. In this case, if the MTC UE deployment location in the MTC application is relatively fixed or the mobile range of the MTC UE is relatively fixed, the corresponding fixed GGSN address may be specifically configured for the application on the MTC Server or the MTC gateway. A tunnel is established between the MTC Server or the MTC gateway and the GGSN, and the trigger packet or the trigger information is directly encapsulated in a data packet whose IP address is the destination address of the GGSN and sent to the GGSN.
  • Step 802 The GGSN sends a "send GPRS routing information" message to the HLR, where the identity of the MTC UE is carried.
  • "send GPRS routing information” can be expressed as Send Routeing Info for GPRS.
  • Step 803 the relationship between the IMSI of the MTC UE, the identity identifier, and the APN corresponding to the MTC Server is stored in the HLR.
  • the HLR queries the IMSI corresponding to the MTC UE, the IP address of the registered SGSN, and the APN of the MTC Server corresponding to the identity identifier according to the received identity of the MTC UE, and returns the message to the GGSN through a "send GPRS routing information response" message.
  • "send GPRS routing information response" can be expressed as Send Routeing Info for GPRS Ack.
  • Step 804 The GGSN sends a "Packet Data Unit Notification Request" message to the SGSN, where the IMSI of the MTC UE and the requested APN are carried, and the PDP context activation procedure of the SGSN to initiate the network request is triggered.
  • "the packet data unit notification request can be expressed as a PDU Notification Request.
  • Step 805 The SGSN returns a "Packet Data Unit Notification Response" message to the GGSN.
  • "packet data unit notification response can be expressed as PDU Notification Response.
  • Step 806 The SGSN sends a "PDP Context Activation Request" message to the MTC UE, requesting the MTC UE to initiate a PDP context activation process.
  • PDP Context Activation Request can be expressed as Request PDP Context Activation
  • Step 807 The MTC UE initiates a PDP context activation process and the network allocates an IP address to the MTC UE.
  • Step 809 The IP address of the MTC UE may also notify the MTC Server of the IP address through the application layer interaction after the MTC UE obtains the IP address.
  • the MTC UE can communicate with multiple MTC Servers, and the MTC Server identity corresponds to the MTC Server, the HLR needs to separately store the MTC UE identity and the MTC Server. Correspondence of APN.
  • Method Embodiment 3 The MTC Server or the MTC gateway sends a trigger packet to the MTC UE to trigger the MTC UE to initiate communication with it. As shown in FIG. 9, the process of this embodiment includes the following steps:
  • Step 901 The MTC Server sends a communication trigger packet to the GGSN. If there is an architecture of the MTC gateway, the MTC Server sends the communication trigger packet to the MTC gateway, and then the MTC gateway sends the communication trigger packet to the GGSN. At this time, if the MTC device deployment location in the MTC application is relatively fixed or the mobile range of the MTC device is relatively fixed, the corresponding fixed GGSN address may be specifically configured for the application on the MTC Server or the MTC gateway. A tunnel is established between the MTC Server or the MTC gateway and the GGSN, and the trigger packet or the trigger information is directly encapsulated in the data packet whose destination address is the IP address of the GGSN, and sent to the GGSN.
  • Step 902 If the relationship between the APN of the MTC Server corresponding to the IMSI, the identity identifier, and the identity identifier of the MTC UE is statically configured in the GGSN, the GGSN sends a "Send GPRS Routing Information" message to the HLR, where The identity of the MTC UE queries the IP address of the SGSN to which the MTC UE is registered, and performs step 903a. If the identity of the MTC UE and the APN of the MTC Server corresponding to the identity identifier are statically configured in the GGSN, the GGSN sends the GGSN to the HLR.
  • Sending a "send GPRS routing information" message in which the identity of the MTC UE is carried, the IP address of the SGSN to which the MTC UE is registered and the IMSI of the MTC UE are queried, and step 903b is performed.
  • "send GPRS routing information" can be expressed as Send Routeing Info for GPRS.
  • Step 903a The HLR queries the IP address of the SGSN to which the MTC UE is registered according to the received identity of the MTC UE, and returns a message to the GGSN by using a "send GPRS routing information response" message, and performs step 904a.
  • Step 903b The HLR queries the IP address of the SGSN to which the MTC UE is registered and the IMSI of the MTC UE according to the received identity of the MTC UE, and returns a message to the GGSN by using a "send GPRS routing information response" message, and performs step 904b.
  • Step 904a The GGSN queries the IMSI of the MTC UE and the APN of the MTC Server corresponding to the identity identifier according to the identity of the MTC UE, and performs step 905.
  • Step 904b The GGSN queries the APN of the MTC Server corresponding to the identity identifier according to the identity of the MTC UE, and performs step 905.
  • Step 905 The GGSN sends a "Packet Data Unit Notification Request" message to the SGSN, where the IMSI of the MTC UE and the requested APN are carried, and the PDP context activation procedure of the SGSN to initiate the network request is triggered.
  • "the packet data unit notification request can be expressed as a PDU Notification Request.
  • Step 906 The SGSN returns a "Packet Data Unit Notification Response" message to the GGSN.
  • "packet data unit notification response can be expressed as PDU Notification Response.
  • Step 907 The SGSN sends a "PDP Context Activation Request" message to the MTC UE, requesting the MTC UE to initiate a PDP context activation procedure.
  • PDP Context Activation Request can be expressed as Request PDP Context Activation
  • Step 908 The MTC UE initiates a PDP context activation process and the network assigns an IP address to the MTC UE.
  • Step 910 The IP address of the MTC UE may also notify the MTC Server of the IP address through the application layer interaction after the MTC UE obtains the IP address.
  • the MTC UE can communicate with multiple MTC Servers, and the MTC Server identity corresponds to the MTC Server, the HLR needs to separately store the MTC UE identity and the MTC Server. Correspondence of APN.
  • a multi-application MTC UE that is, an MTC UE can communicate with multiple MTC Servers, and the MTC Server identity corresponds to the MTC Server, the HLR or GGSN needs to be separately saved. Correspondence between the identity of the MTC UE and the APN of the MTC Server.
  • Method Embodiment 4 The MTC Server sends a trigger packet to the MTC UE to trigger the MTC UE to initiate communication with it. As shown in FIG. 10, the process of this embodiment includes the following steps:
  • Step 1001 If the MTC Server is configured to manage or provide the MTC Server for the operator to be trusted by the operator, the MTC Server sends a trigger packet to the HLR through the interface with the HLR, and carries the identity of the MTC UE to the HLR.
  • Step 1002 The HLR queries according to the obtained identity of the MTC UE and returns the IMSI of the MTC Server MTC UE, the IP address of the registered SGSN, and the APN of the MTC Server corresponding to the identity identifier.
  • Step 1003 The MTC Server sends a trigger packet to the SGSN through the interface with the SGSN, and requests the SGSN to initiate a PDP context activation process of the network request, where the IMSI of the MTC UE and the requested APN are carried.
  • Step 1004 The SGSN sends a PDP Context Activation Request message to the MTC UE, requesting the MTC UE to initiate a PDP context activation process.
  • Step 1005 The MTC UE initiates a PDP context activation process and the network allocates an IP address for the MTC UE.
  • Step 1007 The IP address of the MTC UE may also notify the MTC Server of the IP address through the application layer interaction after the MTC UE obtains the IP address.
  • the MTC UE can communicate with multiple MTC Servers, and the MTC Server identity corresponds to the MTC Server, the HLR needs to separately store the MTC UE identity and the MTC Server. Correspondence of APN.
  • Method Embodiment 5 The MTC Server sends a trigger packet to the MTC UE to trigger the MTC UE to initiate communication with it. As shown in FIG. 11, the process of this embodiment includes the following steps:
  • Step 1101 If the MTC Server is provided for the third party or not for the operator, the operator can deploy the MTC gateway to ensure the security of the communication, and the MTC gateway has an interface connection with the HLR and the SGSN respectively.
  • the MTC Server sends a trigger packet to the MTC gateway, which carries the identity and trigger request of the MTC UE.
  • Step 1102 The MTC gateway sends a trigger packet to the HLR through the interface with the HLR, and carries the identity of the MTC UE to query the HLR of the MSI of the MTC UE, the IP address of the SGSN to which it is registered, and the APN of the MTC Server corresponding to the identity identifier. .
  • Step 1103 The HLR queries according to the obtained identity of the MTC UE and returns the IMSI of the MTC UE to the MTC UE, the IP address of the SGSN to which it is registered, and the APN of the MTC Server corresponding to the identity identifier.
  • Step 1104 The MTC gateway sends a trigger packet to the SGSN through the interface with the SGSN, and requests the SGSN to initiate a PDP context activation process of the network request, where the IMSI of the MTC UE and the requested APN are carried.
  • Step 1105 The SGSN sends a "PDP Context Activation Request" message to the MTC UE, requesting the MTC UE to initiate a PDP context activation procedure.
  • Step 1106 The MTC UE initiates a PDP context activation procedure and the network assigns an IP address to the MTC UE.
  • Step 1107 The GGSN may notify the MTC Server of the IP address of the MTC UE in reverse.
  • Step 1108 The IP address of the MTC UE may also notify the MTC Server of the IP address through the application layer interaction after the MTC UE obtains the IP address.
  • the MTC UE can communicate with multiple MTC Servers, and the MTC Server identity corresponds to the MTC Server, the HLR needs to separately store the MTC UE identity and the MTC Server. Correspondence of APN.
  • Method Embodiment 6 The MTC Server or the MTC gateway sends a trigger packet to the MTC UE to trigger the MTC UE to initiate communication with it. As shown in FIG. 12, the process of this embodiment includes the following steps:
  • Step 1201 If the MTC server is configured to manage the carrier or the third party that provides the MTC server is trusted by the operator, the MTC server sends a trigger packet to the HLR through the interface with the HLR, where the triggered trigger packet carries the MTC UE. Identity and trigger request.
  • Step 1202 If the MTC Server is provided for a third party or not for the operator, the operator can deploy
  • the MTC gateway guarantees the security of communication.
  • the MTC Server sends a trigger packet to the MTC gateway, and the MTC gateway sends a trigger packet to the HLR through the interface with the HLR, where the triggered trigger packet carries the identity identifier and the trigger request of the MTC UE.
  • Step 1203 The HLR queries the IMSI of the MTC UE and the IP address of the registered SGSN and the APN of the MTC Server corresponding to the identity identifier according to the obtained identity identifier, and the HLR sends a UE reachability notification request message to the SGSN, where the bearer is triggered.
  • the request and the requested APN trigger a PDP context activation procedure in which the SGSN initiates a network request.
  • Step 1204 The SGSN sends a PDP Context Activation Request message to the MTC UE, requesting the MTC UE to initiate a PDP context activation process.
  • Step 1205 The MTC UE initiates a PDP context activation process and the network assigns an IP address to the MTC UE.
  • Step 1206 The GGSN may notify the MTC Server of the IP address of the MTC UE in reverse.
  • Step 1207 The IP address of the MTC UE may also notify the MTC Server of the IP address through the application layer interaction after the MTC UE obtains the IP address.
  • a system for obtaining an IP address of an MTC device comprising: an information establishing unit and a dynamic IP address acquiring unit.
  • the information establishing unit is configured to establish, in the network entity, information corresponding to the identity of the MTC device.
  • the dynamic IP address obtaining unit is configured to send, by the MTC server or the MTC gateway, a trigger packet that includes an identity identifier and/or a trigger request of the MTC device, and the network entity queries the identity identifier of the MTC device according to the identity identifier of the MTC device.
  • a trigger packet that includes an identity identifier and/or a trigger request of the MTC device
  • the network entity queries the identity identifier of the MTC device according to the identity identifier of the MTC device.
  • triggering the PDP context activation process initiated by the SGSN to request the network
  • assigning a dynamic IP address to the MTC device assigning a dynamic IP address to the MTC device, and transmitting the assigned IP address to the MTC Server to establish communication between the MTC device and the MTC server.
  • the network entity specifically includes: an HLR or a GGSN; the identity of the MTC device specifically includes: an application layer identifier of the MSISDN or the MTC device.
  • the information establishing unit is further configured to: when the information corresponding to the identity of the MTC device is used, when the identity of the MTC device and the IMSI are carried to the HLR through the interaction message between the SGSN and the HLR when the MTC device performs the attaching process,
  • the correspondence between the identity of the MTC device, the IMSI, and the APN corresponding to the MTC server is stored in the HLR; or the correspondence between the identity of the MTC device, the IMSI, and the APN corresponding to the MTC Server is statically configured in the GGSN.
  • the mapping between the identity of the MTC device and the APN corresponding to the MTC server is statically configured in the GGSN; or the correspondence between the identity of the MTC device, the IMSI, and the APN corresponding to the MTC server is used as the MTC device.
  • the subscription data is saved in the HLR.

Description

一种获取机器类型通信设备 IP地址的方法及系统 技术领域
本发明涉及移动通信领域， 尤其涉及一种机器类型通信 （MTC , Machine Type Communication；)服务器触发 MTC设备发起通信并获取 MTC设备 IP地址的方法及系统。 背景技术
随着全球微波接入互通 ( WiMax, World Interoperability for Microwave Access )技术 的异军突起， 第三代移动通信系统要保持其在移动通信领域的竟争力， 必须提高其网络 性能， 并降低网络建设及运营成本。 因此目前， 第三代合作伙伴计划 （3GPP , 3rd Generation Partnership Project ) 的标准化工作组正致力于研究对分组交换核心网 （ PS Core , Packet Switched Core )和全球移动通信系统无线接入网（ UTRAN , Universal Mobile Telecommunication System Radio Access Network )的演进,目的在于使得演进的 PS Core、 也可称为 EPC 可以提供更高的传输速率、 更短的传输延时， 并支持演进的 UTRAN ( E-UTRAN, Evolved UTRAN )> 全球移动通信系统增强型数据速率全球移动通信系统 演进技术无线接入网（ GERAN, Global System for Mobile communications Enhanced Data Rate for GSM Evolution radio access network ). UTRAN > 无线局域网 ( WLAN, Wireless Local Area Network )及其它非 3GPP的接入网络之间的移动性管理。 这个演进的移动通 信系统， 就被称为演进的分组域系统（EPS, Evolved Packet System )。 图 1为上述 EPS 系统的构架示意图， 图 1中只示出了与本发明实施例有关的部分实体。 对图 1中各实体 说明如下：
移动台 （ MS , Mobile Station ) /用户设备 ( UE , User Equipment ) 101 , 具有能接入 无线网络的能力。 其中， MS也可以称为移动终端。
GERAN/UTRAN 102, 传统 GSM/UMTS网络的无线接入网。
通用无线分组业务服务支持节点 （SGSN, Serving GPRS Support Node ) 103 , 是通 用无线分组业务（GPRS, General Packet Radio Service ) 网络的控制网元， 主要作用是 记录 UE 101的位置信息，并且在 UE 101和 GPRS网关支持节点（ GGSN, Gateway GPRS Supporting Node ) 106之间完成移动分组数据的发送和接收。
服务网关（S-GW, Serving Gateway ) 104, 是一个用户面实体， 负责用户面数据路 由处理， 终结处于空闲 （ECMJDLE )状态的 UE 101的下行数据。 管理和存储 UE 101 的 SAE承载（bearer )上下文， 比如 IP承载业务参数和网络内部路由信息等。 S-GW 104 是 3GPP系统内部用户面的锚点， 一个用户在一个时刻只能有一个 S-GW 104。
分组数据网网关（ P-GW或 PDN GW, Packet Data Network Gateway ) 105 , 是负责 UE 101接入 PDN的网关， 分配用户 IP地址， 也是 3GPP和非 3GPP接入系统的移动性 锚点，P-GW 105的功能还包括策略实施、计费支持。用户在同一时刻能够接入多个 P-GW 105。 策略与计费实施功能实体（PCEF, Policy and Charging Enforcement Function )也 位于 P-GW中。
P-GW 105和 S-GW 104可以设在一个物理实体中， 也可以分别在不同的物理实体 中， 如图 1中所示。
GGSN 106, 支持 GPRS网络的边缘路由功能， 即 GGSN 106负责将 GPRS网络的 数据进行路由转发， 并通过防火墙和过滤功能来保护 GPRS网络数据的完整性。 GGSN 还具有计费功能。
P-GW 105包含了 GGSN 106的全部功能，即可认为 GGSN 106作为 P-GW 105的一 个子功能，内嵌在 P-GW 105内。因此 SGSN 103可以直接和 P-GW 105连接，使用 Gn/Gp 接口。 归属用户服务器（HSS ) /归属位置寄存器（HLR ) 107, 是支持调用 /会话的主要 用户数据库。
UE在与网络建立通信使用业务时需要网络为其分配 IP地址， 网络可以为 UE分配 IPv4地址， 也可以为 UE分配 IPv6前缀。对于 R8及后续版本的 EPS网络， 一个分组数 据协议（ PDP )上下文或一个 EPS承载同时支持使用 IPv4地址和 IPv6地址， 因此对于 支持双栈（ dual stack ) 的 UE来说， 可以向网络申请分配 IPv4地址、 IPv6前缀或 IPv4 地址及 IPv6前缀。
在 UE通过 E-UTRAN接入 EPC网络时， UE的 IP地址分配可以通过附着流程或 UE请求的 PDN连接流程的默认承载激活时进行： 归属公用陆地移动通信网（ HPLMN ) 可以为 UE 分配静态的 IP 地址， 如在 HSS 上配置或在基于外部动态主机设置协议 ( Dynamic Host Configuration Protocol ) /远端筌权拨入用户服务 （RADIUS , Remote Authentication Dial In User Service ) /Radius协议的升级版本（Diameter )服务器上基于 用户和 APN粒度（ per-user per-APN )配置， 或 HPLMN可以为 UE分配动态的 IP地址， 如在 P-GW上分配； 受访公用陆地移动通信网 （ VPLMN )可以为 UE分配动态的 IP地 址， 如在 VPLMN的 P-GW配置； PDN operator或 administrator还可以通过外部 DHCP Server或 AAA Server等其他地址服务器为 UE分配动态或静态的 IP地址。 若上述流程 结束后， UE未分配到 IP地址， 则后续 UE可以通过互联网工程任务组（IETF, Internet Engineering Task Force )定义的 IP地址分配机制进行地址分配。
在 UE通过 GERAN/UTRAN接入 3G网络时， UE的 IP地址分配机制与 EPS网络 类似， 这里就不再赘述。
M2M 狭义上的定义是机器到机器的通信。 广义上的定义是以机器终端智能交互为 核心的、 网络化的应用与服务。 它^ &于智能机器终端， 以多种通信方式为接入手段、 为客户提供的信息化解决方案， 用于满足客户对监控、 指挥调度、 数据釆集和测量等方 面的信息化需求。
无线技术的发展是 M2M市场发展的重要因素， 它突破了传统通信方式的时空限制 和地域障碍， 使企业和公众摆脱了线缆束縛， 让客户更有效地控制成本、 降低安装费用 并且使用筒单方便。 另外， 日益增长的需求推动着 M2M不断向前发展： 与信息处理能 力及网络带宽不断增长相矛盾的是， 信息获取的手段远远落后。 而 M2M很好满足了人 们的这一需求， 通过它人们可以实时监测外部环境， 实现大范围、 自动化的信息釆集。 因此， M2M 可以应用于行业应用、 家庭应用、 个人应用等。 行业应用如： 交通监控、 告警系统、 海上救援、 自动售货机、 开车付费等。 家庭应用如： 自动抄表、 温度控制等。 个人应用如： 生命检测、 远端诊断等。
M2M 的通信对象为机器对机器， 人对机器。 一个或多个机器之间的数据通信定义 为 MTC, 这种情况下较少需要人机互动。 参与 MTC的机器， 定义为 MTC设备（MTC Device )0 MTC设备是 MTC用户的终端， 可通过 PLMN网络与 MTC设备、 MTC服务 器进行通信。 MTC服务器（ MTC Server )对 MTC设备进行管理和监控。 图 2为现有技 术中 MTC UE通过 E-UTRAN接入 EPS系统的示意图， 图 3为现有技术中 MTC UE通 过 UTRAN/GERAN接入 3G系统的示意图。
另外， 为了满足对 MTC终端接入到网络时的灵活的接入控制要求， 同时尽量降低 为支持这类接入限制业务时所引起的对核心网的复杂改造，还可以考虑如下两种网络架 构： 一个架构如图 4所示， 运营商可以作为业务提供商提供 MTC业务， 因此 MTC服 务器（MTC Server )可以是运营商部署并管理的， 或者提供 MTC业务的第三方为运营 商可信的， 这种情况下， 可以考虑 MTC Server与 HLR之间建立接口； 另一个架构如图 5所示， MTC Server可能不是运营商管理的网络实体， 并且有可能部署在核心网外， 因 此， 涉及到 MTC Server接入到核心网时的接入安全，可以考虑在核心网侧增加 MTC网 关 （ MTC GW ), 使得所有 MTC Server的接入均通过该 MTC网关， 该 MTC网关可以 通过内部网络拓朴结构隐藏、对 MTC Server接入进行认证等手段实现 MTC Server接入 到核心网的安全保证。 并且， 在上述两种架构中， 均增加 MTC Server或新增的 MTC网 关与移动性管理网元 SGSN之间的接口， 由业务层（ MTC Server或新增的 MTC网关） 通过移动性管理网元 SGSN获得该 MTC 终端的底层接入层的信息， 进而根据获取的 MTC终端的信息对该 MTC终端的接入进行控制。
在 MTC应用中， 有一些场景需要 MTC Server触发 MTC设备发起与 MTC Server 的通信进行数据的传输， 如： 在一些监控上报类应用中， 除了设置 MTC设备定期向 MTC Server上报监控报告外， MTC Server也会不定期地请求 MTC设备进行测量数据的 上报， 这种情况下， 就需要 MTC Server向 MTC设备发送指示触发 MTC设备连接到网 络或建立数据连接与 MTC Server进行通信。 在这些应用中， MTC设备对于网络来说可 以处于离线状态， 也可以处于在线状态， 包括： 空闲状态和连接状态。 其中， 对于连接 状态， 不论是在 EPS网络还是在 3G网络中， UE的用户面通道是建立好的且 UE被分 配了 IP地址， UE的 IP数据包可以在用户面通道中传输； 对于空闲状态， 在 EPS网络 中， 空闲态的 UE是被分配了 IP地址的。 而在 3G网络中， 空闲态的 UE是没有被分配 IP地址的。对于 MTC设备处于在线状态的情况， 如果 MTC Server知道 MTC设备的 IP 地址， 则可以将触发数据包发送给网络， 由网络釆用相应的机制找到并触发起 MTC设 备。
在 UE通过 E-UTRAN接入 EPC网络时， 当 UE初始附着到网络时就会建立默认承 载并在此过程中被分配到 IP地址， 在 UE去附着之前都供该 UE使用。 在这种情况下， 若要求 MTC Server能够触发 MTC设备，则可以把为 MTC设备分配的动态 IP地址告诉 给 MTC Server, 具体方法可以是： 在 MTC设备获得 IP地址后， 通过应用层交互将该 IP地址通知给 MTC Server。
而在 UE通过 GERAN/UTRAN接入 3G网络时， UE在附着时并不会被分配 IP地址， 而是通过后续的 PDP上下文激活流程获得 IP地址。 而当网络需要寻找附着到网络但没 有 PDP上下文的 UE时， 网络需要发起网络请求的 PDP上下文激活流程。 根据现有技 术， 网络请求的 PDP上下文激活流程只支持 UE的静态 IP地址情况， 即： UE的 IP地 址是预先静态配置的，且 GGSN需要知道 UE的国际移动用户识别码（ IMSI, International Mobile Subscriber Identification Number )和静态 IP地址的配对关系。 如图 6所示， 包括 以下步驟：
步驟 601 : GGSN收到 PDP PDU数据包并确定需要发起网络请求的 PDP上下文激 活流程。
步驟 602: GGSN根据 PDP PDU中携带的 UE的静态 IP地址查询其与该 UE的 IMSI 的配对关系， 向 HLR发送 "发送 GPRS路由信息" 消息， 其中携带 UE的 IMSI。
步驟 603: HLR根据 UE的 IMSI查询到 UE所注册的 SGSN的 IP地址，并返回 "发 送 GPRS路由信息响应"消息，其中携带 UE的 IMSI及 UE所注册的 SGSN的 IP地址。
步驟 604: GGSN向 SGSN发送 "分组数据单元通知请求" 消息， 携带 UE的 IMSI 和接入点名称（ APN, Access Point Name ), 请求 SGSN发起网络请求的 PDP上下文激 活流程。
步驟 605: SGSN向 GGSN返回 "分组数据单元通知响应" 消息。
步驟 606: SGSN向 UE发送 "PDP上下文激活请求" 消息， 其中携带 APN, 要求 UE根据指定的 APN发起 PDP上下文激活流程。
步驟 607: UE发起 PDP上下文过程并由网络为 UE分配 IP地址。
综上所述， MTC Server触发 MTC设备发起与 MTC Server通信的场景， 前提是需 要知道 MTC设备的 IP地址才可行， 而针对通过 GERAN/UTRAN接入 3G网络的 MTC 设备而言， 是通过后续的 PDP上下文激活流程获得 IP地址， 而依据目前的现有技术， PDP上下文激活流程只支持 UE的静态 IP地址。由于 IPv4地址资源非常有限而 IPv6地 址并未广泛使用， 因此考虑到对地址资源的有效利用， 动态分配 IP地址会比静态配置 IP地址在实际应用中优势更大。 且静态 IP地址对于网络需要有额外的配置， 限制性较 大，在实际应用中也不多。然而，在上述 MTC Server触发 MTC设备发起与 MTC Server 通信的场景釆取动态分配 IP地址目前并不可行， 也就是说， 现有技术中， 当 MTC设备 通过 GERAN/UTRAN接入 3G网络而未被分配动态 IP地址时， MTC Server是无法知道 MTC设备的 IP地址的， 因此也无法通过网络找到 MTC设备， 从而 MTC Server无法触 发 MTC设备发起与 MTC Server的通信。
另外， 考虑到移动用户国际号码 （ MSISDN , Mobile Subscriber International ISDN/PSTN Number )主要用于语音通信及短消息通信，因此，对于处于在线状态的 MTC 设备， 若 MTC设备被分配了 MSISDN, 则还可以通过短消息的方式触发 MTC设备发 起与 MTC Server的通信。 但是由于 MTC设备的数量庞大， 若为每个 MTC设备分配 MSISDN, 势必导致 MSISDN资源的短缺。 并且， 今后大部分的 MTC应用应该是数据 应用而非语音业务， 因此可能不会被分配 MSISDN, 因此也无法使用通过短消息的方式 触发 MTC设备发起与 MTC Server的通信。 发明内容
有鉴于此，本发明实施例的主要目的在于提供一种获取 MTC设备 IP地址的方法及 系统， 针对通过 GERAN/UTRAN接入 3G网络的 MTC设备， 但没有 PDP上下文因此 没有被分配动态 IP地址的情况， 使 MTC Server能触发 MTC设备发起与 MTC Server 通信并获取 MTC设备的 IP地址。
为达到上述目的， 本发明实施例的技术方案是这样实现的：
一种获取机器类型通信设备 IP地址的方法， 包括：
在网络实体中建立与机器类型通信 ( MTC )设备的身份标识相对应的信息；
MTC服务器或 MTC网关发送包含 MTC设备的身份标识和 /或触发请求的触发包； 所述网络实体根据所述 MTC设备的身份标识查询到的与所述 MTC设备的身份标 识相对应的信息， 触发通用无线分组业务服务支持节点 （SGSN )发起网络请求的分组 数据协议（ PDP )上下文激活流程， 为 MTC设备分配动态 IP地址， 并将分配的 IP地址 传递给 MTC服务器， 建立 MTC设备与 MTC服务器之间的通信。
所述网络实体具体包括： 归属位置寄存器（HLR )或通用无线分组业务网关支持节 点 （GGSN ); 所述 MTC设备的身份标识具体包括： 移动用户国际号码（ MSISDN )或 MTC设备的应用层标识。
所述建立与 MTC设备的身份标识相对应的信息具体包括：
在将 MTC设备的身份标识和国际移动用户识别码（IMSI )在 MTC设备进行附着 流程时通过 SGSN与 HLR的交互消息携带给 HLR的情况下，将 MTC设备的身份标识、 IMSI及 MTC服务器对应的接入点名称（ APN ) 间的对应关系保存在 HLR中； 或者， 将 MTC设备的身份标识、 IMSI及 MTC服务器对应的 APN间的对应关系均静态地 配置在 GGSN中； 或者，
将 MTC设备的身份标识及 MTC服务器对应的 APN间的对应关系静态地配置在
GGSN中； 或者，
将所述 MTC设备的身份标识、 所述 IMSI及所述 MTC服务器对应的 APN的对应
Figure imgf000008_0001
所述触发 SGSN发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地 址具体包括：
MTC服务器或 MTC网关向 GGSN发送所述触发包， GGSN将发送 GPRS路由信息 消息发送给 HLR, 所述发送 GPRS路由信息消息中携带 MTC设备的身份标识；
所述 HLR根据 MTC设备的身份标识查询到 MTC设备的 IMSI、 MTC设备所注册 的 SGSN的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN,并将发送 GPRS路 由信息确认消息发送给 GGSN,发送 GPRS路由信息确认消息中携带 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN; 所述 GGSN根据 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC 设备对应的 MTC服务器所对应的 APN触发 SGSN发起网络请求的 PDP上下文激活流 程为 MTC设备分配动态 IP地址。
所述触发 SGSN发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地 址具体包括：
MTC服务器或 MTC网关向 GGSN发送所述触发包， GGSN将发送 GPRS路由信息 消息发送给 HLR, 所述发送 GPRS路由信息消息中携带 MTC设备的身份标识；
所述 HLR根据 MTC设备的身份标识查询到 MTC设备的 IMSI、 MTC设备所注册 的 SGSN的 IP地址， 并将发送 GPRS路由信息确认消息发送给 GGSN, 发送 GPRS路 由信息确认消息中携带 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址；
所述 GGSN根据 MTC设备的身份标识查询 GGSN本地静态配置的与 MTC设备对 应的 MTC服务器所对应的 APN, 所述 GGSN根据 MTC设备的 IMSI、 MTC设备所注 册的 SGSN的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN触发所述 SGSN 发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址。
所述触发 SGSN发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地 址具体包括：
MTC服务器或 MTC网关向 HLR发送所述触发包， 所述 HLR根据 MTC设备的身 份标识查询到 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC设备对 应的 MTC服务器所对应的 APN, 并返回给 MTC服务器或 MTC网关；
所述 MTC服务器或 MTC网关根据 MTC设备的 IMSI、 MTC设备所注册的 SGSN 的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN触发 SGSN发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址。
所述触发 SGSN发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地 址具体包括：
MTC服务器或 MTC网关向 HLR发送所述触发包， 所述 HLR根据 MTC设备的身 份标识查询到 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC设备对 应的 MTC月艮务器所对应的 APN;
所述 HLR向所述 SGSN发送用户设备可达性通知请求消息， 所述用户设备可达性 通知请求消息中携带 MTC设备对应的 MTC服务器所对应的 APN和触发请求； 所述 SGSN根据 MTC设备的 IMSI、 MTC设备对应的 MTC服务器所对应的 APN发起网络 请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址。
所述将分配的 IP地址传递给 MTC服务器具体包括： GGSN在为 MTC设备分配 IP 地址后将分配的 IP地址通知 MTC服务器； 或者，
在 MTC设备获得分配的 IP地址后，通过应用层交互将分配的 IP地址通知 MTC服 务器。
一种获取机器类型通信设备 IP地址的系统， 包括： 信息建立单元、 动态 IP地址获 取单元； 其中，
信息建立单元， 用于在网络实体中建立与 MTC设备的身份标识相对应的信息； 动态 IP地址获取单元， 用于 MTC服务器或 MTC网关发送包含 MTC设备的身份 标识和 /或触发请求的触发包； 网络实体根据所述 MTC设备的身份标识查询到的与所述 MTC设备的身份标识相对应的信息，触发 SGSN发起网络请求的 PDP上下文激活流程， 为 MTC设备分配动态 IP地址， 并将分配的 IP地址传递给 MTC服务器， 建立 MTC设 备与 MTC 服务器之间的通信。
所述网络实体具体包括： HLR或 GGSN; 所述 MTC设备的身份标识具体包括： MSISDN或 MTC设备的应用层标识。
所述信息建立单元， 进一步用于建立与 MTC设备的身份标识相对应的信息时， 在 将 MTC设备的身份标识和 IMSI在 MTC设备进行附着流程时通过 SGSN与 HLR的交 互消息携带给 HLR的情况下， 将 MTC设备的身份标识、 IMSI及 MTC服务器对应的 APN间的对应关系保存在 HLR中； 或者， 将 MTC设备的身份标识、 IMSI及 MTC服 务器对应的 APN间的对应关系均静态地配置在 GGSN中； 或者， 将 MTC设备的身份 标识及 MTC服务器对应的 APN间的对应关系静态地配置在 GGSN中； 或者， 将所述 MTC设备的身份标识、 所述 IMSI及所述 MTC服务器对应的 APN的对应关系均作为 MTC设备的签约数据保存在 HLR中。
本发明实施例在网络实体中建立与 MTC设备的身份标识相对应的信息； MTC服务 器或 MTC网关发送包含 MTC设备的身份标识和 /或触发请求的触发包； 网络实体根据 MTC设备的身份标识查询到的与 MTC设备的身份标识相对应的信息，触发 SGSN发起 网络请求的 PDP上下文激活流程， 为 MTC设备分配动态 IP地址， 并将分配的 IP地址 传递给 MTC服务器， 建立 MTC设备与 MTC 服务器之间的通信。 釆用本发明实施例， 基于 MTC设备的身份标识查询到的信息，触发 SGSN发起网络请求的 PDP上下文激活 流程能为 MTC设备分配动态 IP地址，使 MTC服务器能触发 MTC设备发起与 MTC服 务器通信并获取 MTC设备的 IP地址。 附图说明
图 1为现有技术中 3G系统及 GERAN/UTRAN接入网架构示意图；
图 2为现有技术中 MTC UE通过 E-UTRAN接入 EPC系统的示意图；
图 3为现有技术中 MTC UE通过 GERAN/UTRAN接入 3G系统的一架构示意图； 图 4为现有技术中 MTC UE通过 GERAN/UTRAN接入 3G系统的另一架构示意图； 图 5为现有技术中 MTC UE通过 GERAN/UTRAN接入 3G系统的又一架构示意图； 图 6为现有技术中网络请求的 PDP上下文激活的流程示意图；
图 7为本发明方法实施例一的 MTC UE在附着流程中将身份标识携带给 HLR并保 存的流程示意图；
图 8为本发明方法实施例二的 MTC Server或 MTC网关向 MTC UE发送触发包触 发 MTC UE发起与其通信的流程示意图；
图 9为本发明方法实施例三的 MTC Server或 MTC网关向 MTC UE发送触发包触 发 MTC UE发起与其通信的流程示意图；
图 10为本发明方法实施例四的 MTC Server向 MTC UE发送触发包触发 MTC UE 发起与其通信的流程示意图；
图 11为本发明方法实施例五的 MTC Server向 MTC UE发送触发包触发 MTC UE 发起与其通信的流程示意图；
图 12为本发明方法实施例六的 MTC Server或 MTC网关向 MTC UE发送触发包触 发 MTC UE发起与其通信的流程示意图。 具体实施方式
本发明实施例的基本思想是： 在网络实体中建立与 MTC设备的身份标识相对应的 信息； MTC Server或 MTC网关发送包含 MTC设备的身份标识和 /或触发请求的触发包； 网络实体根据 MTC设备的身份标识查询到的与所述 MTC设备的身份标识相对应的信 息， 触发 SGSN发起网络请求的 PDP上下文激活流程， 为 MTC设备分配动态 IP地址， 并将分配的 IP地址传递给 MTC Server, 建立 MTC设备与 MTC Server之间的通信。
下面结合附图对技术方案的实施作进一步的详细描述。
本发明实施例是 MTC Server触发 MTC设备发起通信并获取 MTC设备的 IP地址的 方案， 该方案针对通过 GERAN/UTRAN接入 3G网络中的 MTC设备， 但没有 PDP上 下文因此没有被分配动态 IP地址， 且位置相对固定或运动区域相对固定的 MTC设备， 解决在该网络中 MTC Server触发附着到网络但未被分配动态 IP地址的 MTC设备使其 发起与 MTC Server通信的问题， 进而达到了对 IP地址资源的有效利用且避免了使用静 态 IP地址对网络造成的复杂度和限制性， 同时也可以緩解部署大量的 MTC设备所带来 的 MSISDN资源不足的问题。
一种获取 MTC设备 IP地址的方法， 主要包括以下内容：
在网络实体 A中建立 MTC设备的身份标识、 IMSI及 MTC Server对应的 APN之间 的对应关系， MTC Server或 MTC网关向网络发送包含触发信息的通信触发包触发 SGSN 发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址， 并将该 IP地址传 递给 MTC Server, 以建立 MTC设备与 MTC Server之间的通信。 本文涉及到建立上述 关系时的 MTC Server为： 与 MTC设备的身份标识对应的 MTC Server, 不作赘述。
进一步地， 网络实体 A包括： HLR或 GGSN。
进一步地， 所述 MTC设备的身份标识包括： MSISDN或 MTC设备的应用层标识。 进一步地， 所述 MTC设备的身份标识、 IMSI及 MTC Server对应的 APN的对应关 系， 可以为： 均作为 MTC设备的签约数据保存在 HLR中；
进一步地， 建立所述 MTC设备的身份标识、 所述 IMSI及所述 MTC Server对应的 APN的对应关系包括： 将所述 MTC设备的身份标识和所述 IMSI, 在 MTC设备进行附 着流程时通过 SGSN与 HLR的交互消息携带给 HLR后， 将建立的对应关系实现 HLR 的本地保存。 其中， 本文所述建立的对应关系指： 建立的 MTC设备的身份标识、 IMSI 及 MTC Server对应的 APN的对应关系， 不做赘述。
如果 MTC设备只与一个 MTC Server通信， 则 HLR可以将 MTC设备的身份标识 与 MTC Server对应的 APN关联并保存； 如果 MTC设备与多个 MTC Server通信， 则 HLR将 MTC设备的 IMSI、 身份标识及 MTC Server对应的 APN的关系关联并保存。
进一步地， 所述 SGSN与 HLR的交互消息包括： 位置更新消息、 或插入签约数据 响应消息。
进一步地， 建立所述 MTC设备的身份标识、 所述 IMSI及所述 MTC Server对应的 APN的对应关系包括： 将建立的对应关系均静态地配置在 GGSN中。
进一步地， 建立所述 MTC设备的身份标识、 所述 IMSI及所述 MTC Server对应的 APN的对应关系包括： 将 MTC设备的身份标识及 MTC Server对应的 APN的对应关系 静态地配置在 GGSN中。
进一步地， 所述 MTC Server或 MTC网关保存有 MTC设备的身份标识。
进一步地，所述 MTC Server或 MTC网关向网络发送的包含触发信息的通信触发包 中携带 MTC设备的身份标识和 /或触发请求。
进一步地，所述 MTC Server或 MTC网关向网络发送通信触发包触发 SGSN发起网 络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址， 包括： MTC Server或 MTC网关向 GGSN发送通信触发包， GGSN向 HLR发送 "发送 GPRS路由信息"消息， 其中携带 MTC设备的身份标识。 所述 HLR根据所述 MTC设备的身份标识查询到所述 MTC设备的 IMSI、 其注册的 SGSN的地址及所述 MTC设备的身份标识对应的 MTC Server对应的 APN, 并向 GGSN发送 "发送 GPRS路由信息确认" 消息， 其中携带所 述 MTC设备的 IMSI、其注册的 SGSN的地址及所述 MTC设备的身份标识对应的 MTC Server对应的 APN。 所述 GGSN根据上述信息触发所述 SGSN发起网络请求的 PDP上 下文激活流程为 MTC设备分配动态 IP地址。 其中， 本文的 "上述信息" 包括： 根据 MTC设备的身份标识查询到的所述 MTC设备的 IMSI,根据 MTC设备的身份标识查询 到的 MTC设备所注册的 SGSN的 IP地址， 根据所述 MTC设备的身份标识查询到的 MTC Server所对应的 APN, 不 赘述。
进一步地，所述 MTC Server或 MTC网关向网络发送通信触发包触发 SGSN发起网 络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址， 还包括： MTC Server或 MTC网关向 GGSN发送通信触发包， GGSN向 HLR发送 "发送 GPRS路由信息"消息， 其中携带 MTC设备的身份标识。 所述 HLR根据所述 MTC设备的身份标识查询到所述 MTC设备的 IMSI及其注册的 SGSN的地址， 并向 GGSN发送 "发送 GPRS路由信息 确认" 消息， 其中携带所述 MTC设备的 IMSI及其注册的 SGSN的地址。 所述 GGSN 还根据所述 MTC设备的身份标识查询 GGSN本地静态配置的与其对应的 MTC Server 对应的 APN。 所述 GGSN根据上述信息触发所述 SGSN发起网络请求的 PDP上下文激 活流程为 MTC设备分配动态 IP地址。
进一步地，所述 MTC Server或 MTC网关向网络发送通信触发包触发 SGSN发起网 络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址， 还包括： MTC Server或 MTC网关向 HLR发送通信触发包， 所述 HLR根据所述通信触发包的内容查询到并返 回给 MTC Server或 MTC网关所述 MTC设备的 IMSI、 其注册的 SGSN的地址及所述 MTC设备的身份标识对应的 MTC Server对应的 APN。 所述 MTC Server或 MTC网关 根据上述信息请求所述 SGSN发起网络请求的 PDP上下文激活流程为 MTC设备分配动 态 IP地址。
进一步地，所述 MTC Server或 MTC网关向网络发送通信触发包触发 SGSN发起网 络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址， 还包括： MTC Server或 MTC网关向 HLR发送通信触发包， 所述 HLR根据所述通信触发包的内容查询到所述 MTC设备的 IMSI、 其注册的 SGSN的地址及所述 MTC设备的身份标识对应的 MTC Server对应的 APN。 所述 HLR向所述 SGSN发送 UE可达性通知请求消息， 其中携带 触发请求及所述 APN。 所述 SGSN根据上述信息发起网络请求的 PDP上下文激活流程 为 MTC设备分配动态 IP地址。
进一步地， 所述将 IP地址传递给 MTC Server, 可以是 GGSN在为 MTC设备分配 IP地址后将所述 IP地址通知 MTC Server。
进一步地， 所述将 IP地址传递给 MTC Server, 还可以是在 MTC设备获得 IP地址 后， 通过应用层交互将该 IP地址通知给 MTC Server。
以下对本发明进行举例阐述， MTC设备具体可以为 MTC UE。
方法实施例一： MTC UE在附着流程中将其身份标识携带给 HLR并保存在 HLR本 地。 如图 7所示， 本实施例的流程包括如下步驟：
步驟 701 : MTC UE经由接入网 GERAN/UTRAN向 SGSN发起附着请求（Attach Request )消息，其中携带 MTC UE的身份标识，该身份标识可以是 MTC UE的 MSISDN , 也可以是 MTC UE的应用层标识， 该应用层标识可以与 MTC Server对应。
步驟 702: MTC UE、 SGSN及 HLR之间进行鉴权认证过程。
步驟 703 : SGSN向 HLR发送位置更新消息， 其中携带 MTC UE的身份标识， 该 单应用的 MTC设备，即： MTC UE只与一个 MTC Server通信，则 HLR可以将 MTC UE 的身份标识与 MTC Server对应的 APN关联并保存；若 MTC UE为多应用的 MTC设备 , 即： MTC UE与多个 MTC Server通信， 则 HLR可以从收到的身份标识中解析出该身份 标识对应的 MTC Server的 APN。 HLR将 MTC UE的 IMSI、 身份标识及 MTC Server 对应的 APN的关系保存。
步驟 704: HLR本地保存该身份标识， 向 SGSN发送插入签约数据消息。
步驟 705 : SGSN向 HLR返回插入签约数据响应消息， 此时， 若 SGSN在步驟 704 中未携带 MTC UE的身份标识， 则在该步驟中携带给 HLR。
步驟 706： MTC UE继续完成后续附着流程。
需要注意的是， 附着流程结束后， MTC UE附着到 3G网络中， 但未进行 PDP上下 文激活流程或进行了 PDP上下文激活流程但又执行了 PDP上下文去活流程， 因此 MTC UE没有被分配 IP地址。 在下列的实施例中， MTC UE均为该状态， 后续不再赘述。
方法实施例二： MTC Server或 MTC网关向 MTC UE发送触发包触发 MTC UE发 起与其通信。 如图 8所示， 本实施例的流程包括如下步驟：
步驟 801 : MTC Server向 GGSN发送通信触发包， 如果是有 MTC网关的架构， 则 MTC Server将通信触发包发送给 MTC 网关， 再由 MTC 网关将通信触发包发送给 GGSN。 此时， 该 MTC应用中的 MTC UE部署位置相对固定或 MTC UE的移动范围相 对固定， 则可以在 MTC Server或 MTC网关上为该应用专门配置相应的固定的 GGSN 的地址。 在 MTC Server或 MTC网关与 GGSN之间建立隧道， 直接将触发包或触发信 息封装在目的地址为 GGSN的 IP地址的数据包中并发送到 GGSN。
步驟 802: GGSN向 HLR发送 "发送 GPRS路由信息" 消息， 其中携带 MTC UE 的身份标识。 其中， "发送 GPRS路由信息 " 可以表示为 Send Routeing Info for GPRS。
步驟 803: 该实施例中， MTC UE的 IMSI、 身份标识及 MTC Server对应的 APN的 关系保存在 HLR中。 HLR根据接收到的 MTC UE的身份标识查询 MTC UE对应的 IMSI、 其注册到的 SGSN的 IP地址及该身份标识对应的 MTC Server的 APN, 并通过 "发送 GPRS路由信息响应"消息返回给 GGSN。 其中， "发送 GPRS路由信息响应"可以表示 为 Send Routeing Info for GPRS Ack。
步驟 804: GGSN向 SGSN发送 "分组数据单元通知请求"消息，其中携带 MTC UE 的 IMSI及所请求的 APN,触发 SGSN发起网络请求的 PDP上下文激活流程。其中， "分 组数据单元通知请求，， 可以表示为 PDU Notification Request。
步驟 805: SGSN向 GGSN返回 "分组数据单元通知响应" 消息。 其中， "分组数据 单元通知响应，， 可以表示为 PDU Notification Response。
步驟 806: SGSN向 MTC UE发送 "PDP上下文激活请求" 消息， 要求 MTC UE发 起 PDP上下文激活流程。其中， "PDP上下文激活请求"可以表示为 Request PDP Context Activation„
步驟 807: MTC UE发起 PDP上下文激活流程并由网络为 MTC UE分配 IP地址。 步驟 808: GGSN可以将 MTC UE的 IP地址反向通知给 MTC Server。
步驟 809: MTC UE的 IP地址也可以在 MTC UE获得 IP地址后， 通过应用层交互 将该 IP地址通知给 MTC Server。
需要注意的是， 对于多应用的 MTC UE, 即： MTC UE可以与多个 MTC Server通 信， 且 MTC Server的身份标识与 MTC Server相对应， 则 HLR需要分别保存 MTC UE 的身份标识与 MTC Server的 APN的对应关系。
方法实施例三： MTC Server或 MTC网关向 MTC UE发送触发包触发 MTC UE发 起与其通信。 如图 9所示， 本实施例的流程包括如下步驟：
步驟 901 : MTC Server向 GGSN发送通信触发包， 如果是有 MTC网关的架构， 则 MTC Server向将通信触发包发送给 MTC 网关， 再由 MTC 网关将通信触发包发送给 GGSN。 此时， 该 MTC应用中的 MTC设备部署位置相对固定或 MTC设备的移动范围 相对固定，则可以在 MTC Server或 MTC网关上为该应用专门配置相应的固定的 GGSN 的地址。 在 MTC Server或 MTC网关与 GGSN之间建立隧道， 直接将触发包或触发信 息封装在目的地址为 GGSN的 IP地址的数据包中发送到 GGSN。 步驟 902: 若该实施例中， 若 MTC UE的 IMSI、 身份标识及身份标识对应的 MTC Server的 APN的关系静态地配置在 GGSN中， 则 GGSN向 HLR发送 "发送 GPRS路 由信息"消息，其中携带 MTC UE的身份标识查询 MTC UE注册到的 SGSN的 IP地址， 并执行步驟 903a; 若 MTC UE的身份标识及该身份标识对应的 MTC Server的 APN的 关系静态地配置在 GGSN中， 则 GGSN向 HLR发送 "发送 GPRS路由信息" 消息， 其 中携带 MTC UE的身份标识查询 MTC UE注册到的 SGSN的 IP地址及 MTC UE的 IMSI , 并执行步驟 903b。 其中， "发送 GPRS路由信息" 可以表示为 Send Routeing Info for GPRS。
步驟 903a: HLR根据接收到的 MTC UE的身份标识查询 MTC UE注册到的 SGSN 的 IP地址， 并通过 "发送 GPRS路由信息响应" 消息返回给 GGSN, 并执行步驟 904a。
步驟 903b: HLR根据接收到的 MTC UE的身份标识查询 MTC UE注册到的 SGSN 的 IP地址及 MTC UE的 IMSI, 并通过 "发送 GPRS路由信息响应"消息返回给 GGSN, 并执行步驟 904b。
步驟 904a: GGSN根据 MTC UE的身份标识查询 MTC UE的 IMSI及该身份标识对 应的 MTC Server的 APN, 执行步驟 905。
步驟 904b: GGSN根据 MTC UE的身份标识查询该身份标识对应的 MTC Server的 APN, 执行步驟 905。
步驟 905: GGSN向 SGSN发送 "分组数据单元通知请求"消息，其中携带 MTC UE 的 IMSI及所请求的 APN,触发 SGSN发起网络请求的 PDP上下文激活流程。其中， "分 组数据单元通知请求，， 可以表示为 PDU Notification Request。
步驟 906: SGSN向 GGSN返回 "分组数据单元通知响应" 消息。 其中， "分组数据 单元通知响应，， 可以表示为 PDU Notification Response。
步驟 907: SGSN向 MTC UE发送 "PDP上下文激活请求" 消息， 要求 MTC UE发 起 PDP上下文激活流程。其中， "PDP上下文激活请求"可以表示为 Request PDP Context Activation„
步驟 908: MTC UE发起 PDP上下文激活流程并由网络为 MTC UE分配 IP地址。 步驟 909: GGSN可以将 MTC UE的 IP地址反向通知给 MTC Server。
步驟 910: MTC UE的 IP地址也可以在 MTC UE获得 IP地址后， 通过应用层交互 将该 IP地址通知给 MTC Server。
需要注意的是， 对于多应用的 MTC UE, 即： MTC UE可以与多个 MTC Server通 信， 且 MTC Server的身份标识与 MTC Server相对应， 则 HLR需要分别保存 MTC UE 的身份标识与 MTC Server的 APN的对应关系。
需要注意的是， 对于多应用的 MTC UE, 即： MTC UE可以与多个 MTC Server通 信， 且 MTC Server的身份标识与 MTC Server相对应， 则 HLR或 GGSN需要分别保存 MTC UE的身份标识与 MTC Server的 APN的对应关系。
方法实施例四： MTC Server向 MTC UE发送触发包触发 MTC UE发起与其通信。 如图 10所示， 本实施例的流程包括如下步驟：
步驟 1001 : 若 MTC Server为运营商部署管理或提供 MTC Server的第三方为运营 商可信的， 则 MTC Server通过与 HLR之间的接口向 HLR发送触发包， 携带 MTC UE 的身份标识向 HLR查询 MTC UE的 IMSI、 其注册到的 SGSN的 IP地址及该身份标识 对应的 MTC Server的 APN。
步驟 1002: HLR根据获得的 MTC UE的身份标识进行查询并返回给 MTC Server MTC UE的 IMSI、其注册到的 SGSN的 IP地址及该身份标识对应的 MTC Server的 APN。
步驟 1003: MTC Server通过与 SGSN之间的接口向 SGSN发送触发包，请求 SGSN 发起网络请求的 PDP上下文激活流程， 其中携带 MTC UE的 IMSI及所请求的 APN。
步驟 1004: SGSN向 MTC UE发送 "PDP上下文激活请求" 消息， 要求 MTC UE 发起 PDP上下文激活流程。
步驟 1005 : MTC UE发起 PDP上下文激活流程并由网络为 MTC UE分配 IP地址。 步驟 1006: GGSN可以将 MTC UE的 IP地址反向通知给 MTC Server。
步驟 1007: MTC UE的 IP地址也可以在 MTC UE获得 IP地址后，通过应用层交互 将该 IP地址通知给 MTC Server。
需要注意的是， 对于多应用的 MTC UE, 即： MTC UE可以与多个 MTC Server通 信， 且 MTC Server的身份标识与 MTC Server相对应， 则 HLR需要分别保存 MTC UE 的身份标识与 MTC Server的 APN的对应关系。
方法实施例五： MTC Server向 MTC UE发送触发包触发 MTC UE发起与其通信。 如图 11所示， 本实施例的流程包括如下步驟：
步驟 1101 : 若 MTC Server为第三方提供或不为运营商管理， 则运营商可以部署 MTC网关保证通信的安全性，而 MTC网关与 HLR及 SGSN之间分别有接口连接。 MTC Server向 MTC网关发送触发包， 其中携带 MTC UE的身份标识和触发请求。
步驟 1102: MTC网关通过与 HLR之间的接口向 HLR发送触发包， 携带 MTC UE 的身份标识向 HLR查询 MTC UE的 IMSI、 其注册到的 SGSN的 IP地址及该身份标识 对应的 MTC Server的 APN。
步驟 1103: HLR根据获得的 MTC UE的身份标识进行查询并返回给 MTC网关 MTC UE的 IMSI、 其注册到的 SGSN的 IP地址及该身份标识对应的 MTC Server的 APN。
步驟 1104: MTC网关通过与 SGSN之间的接口向 SGSN发送触发包， 请求 SGSN 发起网络请求的 PDP上下文激活流程， 其中携带 MTC UE的 IMSI及所请求的 APN。
步驟 1105: SGSN向 MTC UE发送 "PDP上下文激活请求" 消息， 要求 MTC UE 发起 PDP上下文激活流程。 步驟 1106: MTC UE发起 PDP上下文激活流程并由网络为 MTC UE分配 IP地址。 步驟 1107: GGSN可以将 MTC UE的 IP地址反向通知给 MTC Server。
步驟 1108: MTC UE的 IP地址也可以在 MTC UE获得 IP地址后，通过应用层交互 将该 IP地址通知给 MTC Server。
需要注意的是， 对于多应用的 MTC UE, 即： MTC UE可以与多个 MTC Server通 信， 且 MTC Server的身份标识与 MTC Server相对应， 则 HLR需要分别保存 MTC UE 的身份标识与 MTC Server的 APN的对应关系。
方法实施例六： MTC Server或 MTC网关向 MTC UE发送触发包触发 MTC UE发 起与其通信。 如图 12所示， 本实施例的流程包括如下步驟：
步驟 1201 : 若 MTC Server为运营商部署管理或提供 MTC Server的第三方为运营 商可信的， 则 MTC Server通过与 HLR之间的接口向 HLR发送触发包， 其中所发送的 触发包携带 MTC UE的身份标识和触发请求。
步驟 1202: 若 MTC Server 为第三方提供或不为运营商管理， 则运营商可以部署
MTC网关保证通信的安全性。 此时， MTC Server向 MTC网关发送触发包， MTC网关 通过与 HLR之间的接口向 HLR发送触发包，其中所发送的触发包携带 MTC UE的身份 标识和触发请求。
步驟 1203 : HLR根据获得的身份标识查询到 MTC UE的 IMSI及其注册到的 SGSN 的 IP地址及该身份标识对应的 MTC Server的 APN, HLR向 SGSN发送 UE可达性通 知请求消息， 其中携带触发请求及所请求的 APN , 触发 SGSN发起网络请求的 PDP上 下文激活流程。
步驟 1204: SGSN向 MTC UE发送 "PDP上下文激活请求" 消息， 要求 MTC UE 发起 PDP上下文激活流程。
步驟 1205 : MTC UE发起 PDP上下文激活流程并由网络为 MTC UE分配 IP地址。 步驟 1206: GGSN可以将 MTC UE的 IP地址反向通知给 MTC Server。
步驟 1207: MTC UE的 IP地址也可以在 MTC UE获得 IP地址后，通过应用层交互 将该 IP地址通知给 MTC Server。
需要指出的是： 除图 12所示的本方法实施例以外， 其他方法实施例都是用专用消 息携带， 因此仅携带 MTC设备的身份标识即可， 而不需要携带 "触发请求"， 但是图 12所示的本方法实施例是对现有消息的扩展，不是专用消息， 因此，必须除了携带 MTC 设备的身份标识， 还必须携带 "触发请求"， 否则， 无法触发请求。 因为， 现有消息不 是用于该触发请求操作的， 如果不携带这个 "触发请求"， 网元不知道是要做何种操作。
需要注意的是， 对于多应用的 MTC UE , 即： MTC UE可以与多个 MTC Server通 信， 且 MTC UE的身份标识与 MTC Server相对应， 则 HLR需要分别保存 MTC UE的 身份标识与 MTC Server的 APN的对应关系。 一种获取 MTC设备 IP地址的系统， 该系统包括： 信息建立单元、 动态 IP地址获 取单元。 其中， 信息建立单元用于在网络实体中建立与 MTC设备的身份标识相对应的 信息。动态 IP地址获取单元用于 MTC Server或 MTC网关发送包含 MTC设备的身份标 识和 /或触发请求的触发包； 网络实体根据所述 MTC设备的身份标识查询到的与所述 MTC设备的身份标识相对应的信息，触发 SGSN发起网络请求的 PDP上下文激活流程， 为 MTC设备分配动态 IP地址， 并将分配的 IP地址传递给 MTC Server, 建立 MTC设 备与 MTC 服务器之间的通信。
这里，网络实体具体包括： HLR或 GGSN; MTC设备的身份标识具体包括： MSISDN 或 MTC设备的应用层标识。
这里， 信息建立单元进一步用于建立与 MTC设备的身份标识相对应的信息时， 在 将 MTC设备的身份标识和 IMSI在 MTC设备进行附着流程时通过 SGSN与 HLR的交 互消息携带给 HLR的情况下， 将 MTC设备的身份标识、 IMSI及 MTC Server对应的 APN间的对应关系保存在 HLR中；或者，将 MTC设备的身份标识、 IMSI及 MTC Server 对应的 APN间的对应关系均静态地配置在 GGSN中； 或者， 将 MTC设备的身份标识 及 MTC Server对应的 APN间的对应关系静态地配置在 GGSN中； 或者， 将 MTC设备 的身份标识、 IMSI及 MTC Server对应的 APN的对应关系均作为 MTC设备的签约数据 保存在 HLR中。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保护范围。

Claims

权利要求书
1、 一种获取机器类型通信设备 IP地址的方法， 其特征在于， 该方法包括： 在网络实体中建立与机器类型通信 ( MTC )设备的身份标识相对应的信息； MTC服务器或 MTC网关发送包含 MTC设备的身份标识和 /或触发请求的触发包； 所述网络实体根据所述 MTC设备的身份标识查询到的与所述 MTC设备的身份标 识相对应的信息， 触发通用无线分组业务服务支持节点 （SGSN )发起网络请求的分组 数据协议（ PDP )上下文激活流程， 为 MTC设备分配动态 IP地址， 并将分配的 IP地址 传递给 MTC服务器， 建立 MTC设备与 MTC服务器之间的通信。
2、 根据权利要求 1 所述的方法， 其特征在于， 所述网络实体具体包括： 归属位置 寄存器（HLR )或通用无线分组业务网关支持节点 （GGSN );
所述 MTC设备的身份标识具体包括： 移动用户国际号码（ MSISDN )或 MTC设备 的应用层标识。
3、根据权利要求 1所述的方法， 其特征在于， 所述建立与 MTC设备的身份标识相 对应的信息具体包括：
在将 MTC设备的身份标识和国际移动用户识别码（ IMSI )在 MTC设备进行附着 流程时通过 SGSN与 HLR的交互消息携带给 HLR的情况下，将 MTC设备的身份标识、 IMSI及 MTC服务器对应的接入点名称（ APN ) 间的对应关系保存在 HLR中； 或者， 将 MTC设备的身份标识、 IMSI及 MTC服务器对应的 APN间的对应关系均静态地 配置在 GGSN中； 或者，
将 MTC设备的身份标识及 MTC服务器对应的 APN间的对应关系静态地配置在
GGSN中； 或者，
将所述 MTC设备的身份标识、 所述 IMSI及所述 MTC服务器对应的 APN的对应 关系均作为 MTC设备的签约数据保存在 HLR中。
4、 根据权利要求 1所述的方法， 其特征在于， 该方法还包括： 所述 MTC服务器或 所述 MTC网关保存有所述 MTC设备的身份标识。
5、 根据权利要求 1或 2所述的方法， 其特征在于， 所述触发 SGSN发起网络请求 的 PDP上下文激活流程为 MTC设备分配动态 IP地址具体包括：
MTC服务器或 MTC网关向 GGSN发送所述触发包， GGSN将发送 GPRS路由信息 消息发送给 HLR, 所述发送 GPRS路由信息消息中携带 MTC设备的身份标识；
所述 HLR根据 MTC设备的身份标识查询到 MTC设备的 IMSI、 MTC设备所注册 的 SGSN的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN, 并将发送 GPRS路 由信息确认消息发送给 GGSN,发送 GPRS路由信息确认消息中携带 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN; 所述 GGSN根据 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC 设备对应的 MTC服务器所对应的 APN触发 SGSN发起网络请求的 PDP上下文激活流 程为 MTC设备分配动态 IP地址。
6、 根据权利要求 1或 2所述的方法， 其特征在于， 所述触发 SGSN发起网络请求 的 PDP上下文激活流程为 MTC设备分配动态 IP地址具体包括：
MTC服务器或 MTC网关向 GGSN发送所述触发包， GGSN将发送 GPRS路由信息 消息发送给 HLR, 所述发送 GPRS路由信息消息中携带 MTC设备的身份标识；
所述 HLR根据 MTC设备的身份标识查询到 MTC设备的 IMSI、 MTC设备所注册 的 SGSN的 IP地址， 并将发送 GPRS路由信息确认消息发送给 GGSN, 发送 GPRS路 由信息确认消息中携带 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址； 所述 GGSN根据 MTC设备的身份标识查询 GGSN本地静态配置的与 MTC设备对 应的 MTC服务器所对应的 APN, 所述 GGSN根据 MTC设备的 IMSI、 MTC设备所注 册的 SGSN的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN触发所述 SGSN 发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址。
7、 根据权利要求 1或 2所述的方法， 其特征在于， 所述触发 SGSN发起网络请求 的 PDP上下文激活流程为 MTC设备分配动态 IP地址具体包括：
MTC服务器或 MTC网关向 HLR发送所述触发包， 所述 HLR根据 MTC设备的身 份标识查询到 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC设备对 应的 MTC服务器所对应的 APN, 并返回给 MTC服务器或 MTC网关；
所述 MTC服务器或 MTC网关根据 MTC设备的 IMSI、 MTC设备所注册的 SGSN 的 IP地址及 MTC设备对应的 MTC服务器所对应的 APN触发 SGSN发起网络请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址。
8、 根据权利要求 1或 2所述的方法， 其特征在于， 所述触发 SGSN发起网络请求 的 PDP上下文激活流程为 MTC设备分配动态 IP地址具体包括：
MTC服务器或 MTC网关向 HLR发送所述触发包， 所述 HLR根据 MTC设备的身 份标识查询到 MTC设备的 IMSI、 MTC设备所注册的 SGSN的 IP地址及 MTC设备对 应的 MTC 艮务器所对应的 APN;
所述 HLR向所述 SGSN发送用户设备可达性通知请求消息， 所述用户设备可达性 通知请求消息中携带 MTC设备对应的 MTC服务器所对应的 APN和触发请求； 所述 SGSN根据 MTC设备的 IMSI、 MTC设备对应的 MTC服务器所对应的 APN发起网络 请求的 PDP上下文激活流程为 MTC设备分配动态 IP地址。
9、 根据权利要求 1所述的方法， 其特征在于， 所述将分配的 IP地址传递给 MTC 服务器具体包括： GGSN在为 MTC设备分配 IP地址后将分配的 IP地址通知 MTC服务
II； 或者 , 在 MTC设备获得分配的 IP地址后，通过应用层交互将分配的 IP地址通知 MTC服 务器。
10、 一种获取机器类型通信设备 IP地址的系统， 其特征在于， 该系统包括： 信息 建立单元、 动态 IP地址获取单元； 其中，
信息建立单元， 用于在网络实体中建立与 MTC设备的身份标识相对应的信息； 动态 IP地址获取单元， 用于 MTC服务器或 MTC网关发送包含 MTC设备的身份 标识和 /或触发请求的触发包； 网络实体根据所述 MTC设备的身份标识查询到的与所述 MTC设备的身份标识相对应的信息，触发 SGSN发起网络请求的 PDP上下文激活流程， 为 MTC设备分配动态 IP地址， 并将分配的 IP地址传递给 MTC服务器， 建立 MTC设 备与 MTC 服务器之间的通信。
11、 根据权利要求 10所述的系统， 其特征在于， 所述网络实体具体包括： HLR或 GGSN;
所述 MTC设备的身份标识具体包括： MSISDN或 MTC设备的应用层标识。
12、 根据权利要求 10所述的系统， 其特征在于， 所述信息建立单元， 进一步用于 建立与 MTC设备的身份标识相对应的信息时， 在将 MTC设备的身份标识和 IMSI在
MTC设备进行附着流程时通过 SGSN与 HLR的交互消息携带给 HLR的情况下，将 MTC 设备的身份标识、 IMSI及 MTC服务器对应的 APN间的对应关系保存在 HLR中；或者， 将 MTC设备的身份标识、 IMSI及 MTC服务器对应的 APN间的对应关系均静态地配置 在 GGSN中； 或者， 将 MTC设备的身份标识及 MTC服务器对应的 APN间的对应关系 静态地配置在 GGSN中； 或者， 将所述 MTC设备的身份标识、 所述 IMSI及所述 MTC 服务器对应的 APN的对应关系均作为 MTC设备的签约数据保存在 HLR中。
PCT/CN2012/072906 2011-03-30 2012-03-23 一种获取机器类型通信设备ip地址的方法及系统 WO2012130098A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110078874.5A CN102724661B (zh) 2011-03-30 2011-03-30 一种获取机器类型通信设备ip地址的方法及系统
CN201110078874.5 2011-03-30

Publications (1)

Publication Number Publication Date
WO2012130098A1 true WO2012130098A1 (zh) 2012-10-04

Family

ID=46929452

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/072906 WO2012130098A1 (zh) 2011-03-30 2012-03-23 一种获取机器类型通信设备ip地址的方法及系统

Country Status (2)

Country Link
CN (1) CN102724661B (zh)
WO (1) WO2012130098A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104937957B (zh) * 2012-11-19 2019-05-14 Iot控股公司 设备发起的触发
CN103188822B (zh) * 2013-03-18 2015-08-19 华为技术有限公司 一种机器通信方法及设备
CN111556468B (zh) * 2013-05-06 2023-02-17 康维达无线有限责任公司 装置触发
CN105227525B (zh) * 2014-06-17 2018-07-13 阿尔卡特朗讯 用于基于信令的物联网设备的ip通信方法与设备
CN105791226B (zh) * 2014-12-23 2019-03-15 中国电信股份有限公司 基于IPv6地址识别用户身份的方法、装置和系统
CN107517182B (zh) * 2016-06-16 2020-11-17 华为技术有限公司 一种垂直行业用户系统、设备以及分发身份识别号的方法
CN108462962B (zh) * 2017-02-20 2021-02-05 中国移动通信集团公司 一种连接接入点的方法和装置
CN111465000B (zh) * 2020-04-01 2022-07-22 中国联合网络通信集团有限公司 一种呼叫寻址方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101388901A (zh) * 2007-09-14 2009-03-18 大唐移动通信设备有限公司 长期演进系统中支持用户静态ip地址寻址的方法及系统
CN101860807A (zh) * 2010-05-05 2010-10-13 工业和信息化部电信传输研究所 一种m2m终端设备组的管理、建立通信方法及装置
WO2011020435A1 (zh) * 2009-08-19 2011-02-24 华为技术有限公司 M2m应用服务器下发数据包的方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101388901A (zh) * 2007-09-14 2009-03-18 大唐移动通信设备有限公司 长期演进系统中支持用户静态ip地址寻址的方法及系统
WO2011020435A1 (zh) * 2009-08-19 2011-02-24 华为技术有限公司 M2m应用服务器下发数据包的方法及系统
CN101860807A (zh) * 2010-05-05 2010-10-13 工业和信息化部电信传输研究所 一种m2m终端设备组的管理、建立通信方法及装置

Also Published As

Publication number Publication date
CN102724661A (zh) 2012-10-10
CN102724661B (zh) 2016-12-28

Similar Documents

Publication Publication Date Title
US11910292B2 (en) Support of user plane transactions over a mobile network
JP5793812B2 (ja) データオフロードをトリガするための方法、ネットワーク側デバイス、ユーザ機器、およびネットワークシステム
EP2566199B1 (en) Method and system for transmitting small data packets
WO2012130098A1 (zh) 一种获取机器类型通信设备ip地址的方法及系统
US9179443B2 (en) Method and apparatus for providing services at terminal of mobile communication system
WO2011054299A1 (zh) 机器类通讯终端信息的获取方法和系统
KR20160003807A (ko) 모바일 통신 시스템에서 서비스 품질 제어의 지원
WO2011060673A1 (zh) 公用承载建立的方法、数据传输方法和核心网络侧设备
US9131485B2 (en) Method for revocable deletion of PDN connection
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2011140884A1 (zh) Mtc组选择分组数据网网关的方法及移动性管理网元
WO2012068728A1 (zh) 获取用户的ip地址的方法和网络实体
WO2013166913A1 (zh) 小量数据上下行传输方法、及相应终端和移动性管理单元
CN103228004A (zh) 在没有移动站国际用户目录号的情况下的合法监听
US20150296445A1 (en) Method, device and system for managing packet data network type
JP2016536861A (ja) 移動無線通信装置からのデータ転送
WO2012152221A1 (zh) 业务通信方法、装置以及系统
WO2013067744A1 (zh) 一种终端组的服务网关选择方法及系统
AU2017352905B2 (en) Service differentiation for devices connected to a UE as a router
WO2011110022A1 (zh) 数据的传输方法、装置及系统
CN102238532A (zh) 一种获取mtc服务器地址的方法及系统
WO2012065298A1 (zh) 获取用户ip地址的方法和网络实体
KR20150038902A (ko) 이동 통신 시스템에서의 단말 자원 할당 관리 방법 및 그 장치
WO2011082524A1 (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: 12764454

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12764454

Country of ref document: EP

Kind code of ref document: A1