WO2012094957A1 - 一种对mtc终端进行移动性管理的方法和系统 - Google Patents

一种对mtc终端进行移动性管理的方法和系统 Download PDF

Info

Publication number
WO2012094957A1
WO2012094957A1 PCT/CN2012/070003 CN2012070003W WO2012094957A1 WO 2012094957 A1 WO2012094957 A1 WO 2012094957A1 CN 2012070003 W CN2012070003 W CN 2012070003W WO 2012094957 A1 WO2012094957 A1 WO 2012094957A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
mobility management
terminal
network
mtc terminal
Prior art date
Application number
PCT/CN2012/070003
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 WO2012094957A1 publication Critical patent/WO2012094957A1/zh

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/062—Pre-authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present invention relates to the field of mobile communications, and more particularly to a method and system for mobility management of MTC terminals. Background technique
  • M2M machine to machine
  • GPRS General Packet Radio Service
  • EPS Evolved Packet System
  • the GPRS network is a second-generation mobile communication network based on packet switching.
  • GPRS evolves into a universal mobile communication system packet switching (UMTS PS, Universal Mobile Telecommunication system Packet Switch or port.
  • UMTS PS Universal Mobile Telecommunication system Packet Switch
  • the network architecture of the UMTS PS which includes the following network elements:
  • RNS Radio Network System
  • RNS includes NodeB and RNC, NodeB provides air interface for terminals
  • RNC Radio Network Controller
  • RNC Radio Network Controller
  • the RNC and the NodeB are connected through the Iub port, and the terminal accesses the packet domain core network (Packet Core) of the UMTS through the RNS;
  • Packet Core Packet Core
  • SGSN Serving GPRS Support Node
  • Gateway GPRS support node used to assign the IP address of the terminal and the gateway function to the external network, and is internally connected to the SGSN through the Gn port;
  • the home location register (HLR) is used to store the user's subscription data and the current SGSN address, and is connected to the SGSN through the Gr port and to the GGSN through the Gc port.
  • a packet data network (PDN, Packet Data Network) is used to provide a packet-based service network for users, and is connected to the GGSN through a Gi port.
  • PDN Packet Data Network
  • the MTC Server is an M2M application server, which is used to provide an M2M application for users and is connected to the GGSN through an MTCi interface.
  • the Machine Type Communication (MTC) UE needs to transmit data information to the MTC Server over the GPRS network.
  • the GPRS network establishes a tunnel between the RNC and the GGSN for the transmission.
  • the tunnel is based on the tunneling protocol (GTP, GPRS Tunneling Protocol), and the data information is reliably transmitted through the GTP tunnel.
  • GTP tunneling protocol
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • Evolved Radio Access Network is an evolved Node B (eNodeB, Evolved NodeB), which belongs to the RNS system and is used for Provide wireless resources for user access; packet data network (PDN, Packet Data Network) is a network that provides services to users; EPC provides lower latency and allows more wireless access systems to access, including the following network elements:
  • the MME Mobility Management Entity
  • UE User Equipment
  • the parameter, etc. allocates a temporary identifier to the user, and is responsible for authenticating the user when the UE is camped on the tracking area or the network.
  • the Serving Gateway is a user plane entity responsible for user plane data routing processing and terminating downlink data of UEs in idle (ECM_IDLE) state. Manage and store the SAE bearer context of the UE, such as IP bearer service parameters and intranet routing information.
  • the SGW is the anchor point of the internal user plane of the 3GPP system. A user can only have one SGW at a time.
  • the packet data network gateway (PGW, PDN Gateway) is the gateway responsible for the UE accessing the PDN, and assigns the user IP address. It is also the mobility anchor of the 3GPP and non-3GPP access systems.
  • the PGW functions include policy implementation and charging support. . Users can access multiple PGWs at the same time.
  • the Policy and Charging Enforcement Function (PCEF) is also located in the PGW.
  • the Policy and Charging Rules Function (PCRF) is responsible for providing policy control and charging rules to the PCEF.
  • the Home Subscriber Server (HSS) is responsible for permanently storing user subscription data.
  • the content stored by the HSS includes the UE's International Mobile Subscriber Identification (IMSI), and the IP address of the PGW.
  • IMSI International Mobile Subscriber Identification
  • the SGW and the PGW may be unified.
  • the EPC system user plane network element includes the SGW and the PGW.
  • the MTC Server is used to provide an M2M application for the user and is connected to the PGW through the MTCi interface.
  • MTC Server is mainly responsible for information collection and data storage/processing of MTC devices, and necessary management of MTC devices (MTC UEs).
  • the MTC UE is responsible for collecting information of several collectors and accessing the core network through the RAN node and interacting with the MTC Server.
  • the MTC UE needs to transmit data information to the MTC Server over the EPS network.
  • the EPS network establishes a GTP tunnel between the SGW and the PGW for this transmission, and the data information is reliably transmitted through the GTP tunnel.
  • FIG. 3 is a mobility management process in which the MTC UE accesses the EPS network and performs network attachment and IP bearer establishment in the prior art, including the following steps:
  • Step 101 The MTC UE initiates an attach request to the RNS radio access network (including the eNodeB or the RNC) for accessing the PS network, including the GPRS network and the EPS network, and carries the network of the terminal identifier IMSI and the MTC UE of the MTC UE.
  • Information such as access capabilities, and instructions for requesting IP assignments;
  • the RNS selects an MME/SGSN (MME or SGSN) for which the MTC UE serves and forwards the attach request to the MME/SGSN.
  • MME Mobility Management Entity
  • Step 102 The MME/SGSN sends an authentication data request (including an IMSI) to the HSS.
  • the HSS first determines the subscription data corresponding to the IMSI. If no subscription is found or the IMSI is blacklisted, the HSS returns a reference to the MME/SGSN. The weight data responds with the error reason; if the contract data corresponding to the IMSI is found, the HSS returns an authentication data response (including an authentication vector) to the MME/SGSN;
  • the MME/SGSN performs an authentication procedure to verify the legitimacy of the terminal IMSI and performs a security mode flow to enable a secure connection.
  • Step 103 The MME/SGSN sends a location update request to the HSS of the home network, where the message carries the identifier of the MME and the identifier of the MTC UE to notify the MTC UE of the currently accessed area.
  • the HSS searches for the MTC UE according to the identifier of the MTC UE.
  • Signing user data sent to MME/SGSN.
  • the subscription user data mainly includes: default access point name (APN, Access Point Name), bandwidth size and other information;
  • the MME/SGSN receives the user data, checks whether the MTC UE is allowed to access the network, and returns a receiving user response to the HSS. If the MME/SGSN finds that the MTC UE has roaming restrictions or access restrictions, the MME/SGSN will disable the MTC UE. Attach and notify HSS.
  • Step 104 The MME/SGSN selects a PGW/GGSN (PGW or GGSN) for the MTC UE according to the default APN, and sends a request for establishing a bearer thereto.
  • the request carries the identifier of the MTC UE, the identifier of the MME/SGSN, the indication for assigning the IP address to the MTC UE, the default bandwidth information, and the PGW/GGSN address.
  • the PGW/GGSN requests the PCRF to allocate the configured policy and charging rule decision information for the MTC UE;
  • the PGW/GGSN establishes a PS bearer according to the policy and charging rule decision information returned by the PCRF or the statically configured PCC policy, and returns a bearer setup response to the MME/SGSN.
  • Step 105 The MME/SGSN saves the bearer context Bearer context, and then sends an initial context setup request or an attach accept response to the RNS, indicating that the MTC UE's request to attach to the network has been accepted, carrying the APN, PS Bearer ID, PGW/GGSN address and Tunnel ID (Identifier).
  • Step 106 The RNS sends an RRC connection reconfiguration request to the MTC UE, and opens the corresponding port.
  • the RRC connection reconfiguration request carries: a PS Bearer ID, a PGW/GGSN address, an APN, an IP address assigned to the MTC UE, bandwidth information, and the like;
  • the MTC UE sends a radio bearer reconfiguration response to the RNS to establish a radio bearer.
  • Step 107 The RNS sends an initial context response to the MME/SGSN, where the message includes the TEID and address information of the RNS, and is used to send downlink data to the MTC UE.
  • Step 108 The MTC UE sends an attach complete message, carries the PS Bearer ID, and notifies the MME/SGSN that the attach process is completed.
  • the PGW/GGSN sends an update 7
  • FIG. 4 is a mobility management process for performing network location update when an MTC UE has access to an EPS network in the prior art, and includes the following steps:
  • Step 201 When the MTC UE moves in the 3GPP network, the area managed by the source MME/SGSN moves to the area managed by the new MME/SGSN.
  • the MTC UE needs to perform a location update.
  • the MTC UE initiates a TAU location update request to the new MME/SGSN, and carries information such as the identifier of the MTC UE, the network capability of the MTC UE, and the PS Bearer status.
  • Step 202 The new MME/SGSN obtains the address of the source MME/SGSN according to the identifier of the MTC UE, and sends a request for acquiring the context of the MTC UE to the source MME/SGSN, where the identifier of the MTC UE, the new MME/SGSN address, and the like are included. Requesting the source MME/SGSN to send all context information of the MTC UE to the new MME/SGSN;
  • the source MME/SGSN After receiving the context request of the MTC UE, the source MME/SGSN sends the uplink information of the MTC UE to the new MME/SGSN.
  • Step 203 The new MME/SGSN initiates an update bearer request to the PGW/GGSN, requesting to update all bearers established by the MTC UE, and the PGW/GGSN needs to update the bearer context corresponding to the MTC UE, such as updating the TEID of the MME/SGSN in the bearer context. .
  • the update response is then returned to the new MME/SGSN.
  • Step 204 The new MME/SGSN initiates a location update request to the HSS, and carries information such as the location information of the MTC UE and the new MME/SGSN address, and the HSS updates and saves the information.
  • Step 205 The HSS initiates a delete user data request to the source MME/SGSN, and the source MME/SGSN deletes all the information of the saved MTC UE.
  • Step 206 The HSS returns a location update response to the new MME/SGSN, and sends the subscription user data of the MTC UE to the new MME/SGSN, where the subscription user data includes the APN of the MTC UE, and Information such as bandwidth.
  • Step 207 The new MME/SGSN sends a TAU accept message to the MTC UE, and the MTC UE successfully performs location update on the target (new) network.
  • FIG. 5 is a process in which the MTC UE has access to the EPS network in the prior art, and when the MTC UE needs to be offline, such as shutting down, performing a network offline mobility management process, including the following steps:
  • Step 301 The MTC UE initiates a process of offline from the 3GPP network.
  • the MTC UE sends an offline request to the MME/SGSN, where the message includes information such as the identifier of the MTC UE.
  • Step 302 After receiving the offline request initiated by the MTC UE, the MME/SGSN deletes the context information related to the MTC UE.
  • the MME/SGSN sends a delete bearer request to the PGW/GGSN through the SGW, carries the LBI identifier, and requests to delete the PDN connection of the MTC UE.
  • the SGW and the GGSN/PGW delete the PDN connection of the MTC UE according to the LBI, and release the allocated bearer resources.
  • the PGW/GGSN returns a 7
  • Step 303 The MME/SGSN returns an offline request accept message to the MTC UE, to notify the MTC UE that the network has performed offline operation.
  • Step 304 The MME/SGSN sends a PS connection release command to the RNS, informing the RNS to release the PS connection, and the RNS releases the radio related resource.
  • the RNS sends a PS connection release message to the MTC UE, and releases the air interface resource with the MTC UE.
  • the M2M service is a networked application and service centered on intelligent interaction of machine terminals. It uses intelligent machine terminals to transmit information over the wireless network, providing customers with information solutions to meet customer information needs for monitoring, command and dispatch, data acquisition and measurement.
  • the communication object of M2M is machine-to-machine, which can be communication between people and machines, communication between machines and servers, and communication between different intelligent terminals.
  • Different applications of MTC equipment have different characteristics, such as lift equipment such as elevators have low mobility, PS only attributes, and monitoring, In addition to low mobility, PS only, the alarm device has attributes such as low data transmission and high availability. Therefore, different system optimizations are required for MTC devices of different applications, and the MTC devices can be effectively managed, monitored, and paid.
  • Figure 6 is an Internet of Things scenario that describes the Internet of Things as three layers: the perimeter layer, the network layer, and the application layer.
  • the peripheral layer mainly refers to the sensor network.
  • the sensor nodes use short-distance interconnection technologies, such as Bluetooth, ZigBee, WLAN, and RFID technologies to interconnect local networks. The short-distance distance can be up to several hundred meters or kilometers.
  • the sensor node is used to collect sensor data and transmit the collected data to the MTC Server through network layer transmission, such as remote meter reading applications.
  • the terminal in the stub network, may be a terminal without 3GPP communication capability or 3GPP user identity, or a terminal without non-3GPP communication capability but having a 3GPP user identity (non-MTC UE), such as having a SIM.
  • the card does not have a 3GPP communication module, and may also be a terminal (MTC UE) having 3GPP communication capability.
  • MTC UE Mobility Management Entity
  • the MTC UE roams from other areas to the terminal network area managed by the MTC GW, it needs to be in the local network according to the terminal policy or network notification. Access to the 3GPP network through the MTC GW. Or some sensor nodes have 3GPP communication capabilities. When the MTC GW is abnormal, it can directly access the 3GPP network to implement transmission with the MTC Server.
  • the MTC GW proxy terminal network terminal accesses the 3GPP network
  • the prior art does not have a corresponding mobility tube for the MTC GW as a terminal access proxy gateway in the stub network.
  • the 3GPP network it is first necessary to solve the problem of how to perform access and mobility management for each MTC terminal (including MTC UE and non-MTC UE) of the MTC GW. Therefore, it is necessary to optimize the mobility management process of the existing PS network. To meet the requirements of access control and mobility management for MTC terminals through the MTC GW. Summary of the invention
  • the main purpose of the present invention is to provide a method and a system for performing mobility management on an MTC terminal, and to solve the scenario in which the MTC GW performs proxy access to the 3GPP network in the stub network, and how to solve the 3GPP network.
  • the MTC GW performs mobility management on the accessed MTC terminal.
  • the present invention provides a method for mobility management of an MTC terminal, the method comprising: a terminal access proxy gateway (MTC GW) instead of a machine type communication (MTC) terminal and a 3GPP network for mobility management signaling interaction; 3GPP network Mobility management of MTC terminals through the MTC GW.
  • MTC GW terminal access proxy gateway
  • MTC machine type communication
  • the MTC terminal includes an MTC UE having 3GPP communication capability and a non-MTC UE having no 3GPP communication capability but having a 3GPP network user identity.
  • the method further includes:
  • the mobility management network element in the 3GPP network obtains the subscription user data of the MTC GW, and then identifies the terminal access proxy capability according to the contracted user data.
  • the MTC GW has terminal access proxy capabilities.
  • the mobility management signaling interaction and the mobility management specifically include:
  • the MTC GW sends an access request of the MTC terminal to the mobility management network element of the 3GPP network; the mobility management network element performs authentication authentication on the MTC terminal, and is used by the MTC GW. Transmitting the authentication data and vector of the MTC UE and the mobility management network element;
  • the mobility management network element sends the identifier and address of the MTC GW and the address of the mobility management network element to the HSS to which the MTC terminal associated with the MTC GW belongs to save;
  • the mobility management network element saves the context information of the MTC terminal and associates with the MTC GW, and updates the MTC GW in the mobility management network element. A list of associations with MTC terminals.
  • the method further includes: the MTC GW establishing a corresponding packet data network for the default access point name (APN) subscribed by the MTC terminal ( PDN) connection.
  • APN access point name
  • PDN mobile phone number
  • the mobility management signaling interaction and the mobility management specifically include:
  • the MTC GW sends the updated wireless access point request of the MTC terminal to the mobility management network element of the 3GPP network;
  • the mobility management network element associates the context information of the MTC terminal with the MTC GW, and updates the association list of the MTC GW and the MTC terminal in the mobility management network element;
  • the mobility management network element releases bearer resources related to the MTC terminal.
  • the method further includes: the MTC GW establishing a corresponding PDN connection for the APN subscribed by the MTC terminal.
  • the mobility management signaling interaction and the mobility management specifically include :
  • the new mobility management network element acquires the context information of the MTC GW, the association list of the MTC GW and the MTC terminal, and the context information of the MTC terminal associated with the MTC GW to the source mobility management network element; and requests the 3GPP network to update the MTC GW. All bearers;
  • the new mobility management network element sends the identifier and address of the MTC GW and the address of the new mobility management network element to the HSS to which the MTC terminal associated with the MTC GW belongs to update and save; the new mobility management network element identifies the MTC GW. Has terminal access proxy capabilities.
  • the mobility management signaling interaction and the mobility management specifically include:
  • the MTC GW sends the offline request of the MTC terminal to the mobility management network element of the 3GPP network; the mobility management network element deletes the context information of the MTC terminal, and the association between the MTC terminal and the MTC GW, and sends the MTC terminal to the MTC terminal through the MTC GW. Offline notification.
  • the method further includes:
  • the MTC GW When it is determined that the APN subscribed by the MTC terminal is not associated with another MTC terminal, the MTC GW initiates a PDN connection to the 3GPP network to deactivate, and deletes the PDN connection corresponding to the APN.
  • the method for storing the MTC terminal associated with itself in the MTC GW further provides a system for mobility management of an MTC terminal, where the system includes: an MTC terminal, and a terminal access proxy gateway ( MTC GW ) and a 3GPP network; wherein: the MTC GW is configured to perform mobility management signaling interaction with the 3GPP network instead of the MTC terminal;
  • MTC GW terminal access proxy gateway
  • the 3GPP network is configured to perform mobility management on the MTC terminal by using the MTC GW.
  • the MTC terminal includes an MTC UE having 3GPP communication capability and a non-MTC UE having no 3GPP communication capability but having a 3GPP network user identity.
  • the 3GPP network includes a mobility management network element, configured to: when the MTC GW first accesses the 3GPP network, after acquiring the subscription user data of the MTC GW, according to the terminal access proxy signed in the subscription user data Capability identification that the MTC GW has terminal access proxy capabilities;
  • the mobility management network element is further configured to associate the context information of the MTC terminal with the MTC GW when the MTC terminal accesses the 3GPP network through the MTC GW, and maintain an association list of the MTC GW and the MTC terminal.
  • the MTC GW is further configured to save information related to the MTC terminal, including at least an identifier of the MTC terminal, an attachment status of the MTC terminal, and an APN subscribed by the MTC terminal.
  • the MTC terminal accesses the 3GPP through the terminal access proxy gateway (MTC GW) of the stub network, releases the resources occupied by the MTC terminal in the 3PGG network, and uses the MTC GW to carry data on the bearer resource of the 3GPP network and the MTC Server.
  • the 3GPP network can implement a series of mobility management such as access authentication, attachment, location update, wireless access point handover, and detachment to the MTC terminal through the MTC GW, which saves resources occupied by each MTC terminal in the 3GPP network, and the 3GPP network can Other process optimizations, such as terminal monitoring and offline triggering, are performed by the MTC GW, and have significant optimization effects.
  • FIG. 1 is a schematic diagram of a GPRS network system architecture in the prior art
  • FIG. 2 is a schematic structural diagram of an EPS network system in the prior art
  • FIG. 3 is a flow chart of attaching a MTC UE to a 3GPP PS network and establishing a bearer in the prior art
  • FIG. 4 is a flowchart of performing location update of a MTC UE in a 3GPP PS network in the prior art
  • FIG. 5 is a MTC UE in the prior art.
  • FIG. 6 is a scenario diagram of an M2M application
  • FIG. 7 is a flow chart of a method for performing mobility management on a terminal according to the present invention.
  • FIG. 9 is a flowchart of the MTC UE accessing the 3GPP network through the MTC GW when the offline in the 3GPP network is performed in the present invention.
  • FIG. 11 is a flowchart of performing location update of an MTC GW in a 3GPP network according to the present invention
  • FIG. 12 is a flowchart of implementing detachment of a MTC UE from a 3GPP network by using an MTC GW in the present invention.
  • the MTC GW in the stub network performs proxy access to the 3GPP network, and solves the problem of how the 3GPP network performs mobility management on the MTC terminal accessed by the MTC GW.
  • Relevant mobility management and access control such as attachment, access point handover, location update, detachment, etc., satisfy the requirement of mobility management when the MTC terminal accesses the 3GPP network through the MTC GW of the stub network.
  • the method for performing mobility management on a terminal includes:
  • Step 1 The MTC GW replaces the MTC terminal with the 3GPP network for mobility management signaling interaction.
  • Step 2 The 3GPP network performs mobility management on the MTC terminal through the MTC GW.
  • the MTC terminal includes an MTC UE having 3GPP communication capability and a non-MTC UE having no 3GPP communication capability.
  • the method further includes: when the MTC GW accesses the 3GPP network for the first time, the mobility management unit (refers to the mobility management unit serving the MTC GW) After obtaining the subscription user data of the MTC GW, the MTC GW has the terminal access proxy capability according to the terminal access proxy capability signed in the subscription user data. Specifically, it is explained by the following first embodiment.
  • the mobility management signaling interaction and the mobility management specifically include: the MTC GW sends an access request of the MTC terminal to the mobility management network of the 3GPP network.
  • Element MME or SGSN
  • mobility management network The element authenticates the MTC terminal, and the MTC GW transparently transmits the authentication data and the vector of the MTC UE and the mobility management network element; the mobility management network element identifies the identifier and address of the MTC GW, and the mobility management The address of the network element is sent to the HSS to which the MTC terminal associated with the MTC GW belongs to save; when the authentication authentication passes and the MTC terminal is allowed to access the 3GPP network, the mobility management network element saves the context information of the MTC terminal and performs with the MTC GW.
  • the MTC GW After the MTC terminal accesses the 3GPP network through the MTC GW: After determining that the PDN connection is not established for the APN contracted by the MTC terminal, the MTC GW establishes a corresponding PDN connection for the APN. Specifically, it is explained by the following second embodiment.
  • the mobility management signaling interaction and the mobility management specifically include: the MTC GW sends the updated wireless access point request of the MTC terminal to the 3GPP. a mobility management network element of the network; the mobility management network element associates the context information of the MTC terminal with the MTC GW, and updates the association list of the MTC GW and the MTC terminal in the mobility management network element; the mobility management network element releases the MTC Terminal-related bearer resources.
  • the method further includes: when determining that the PDN connection is not established for the APN that is subscribed to the MTC terminal, the MTC GW establishes a corresponding PDN connection for the APN. Specifically, it is explained by the following third embodiment.
  • the mobility management signaling interaction and the mobility management specifically include:
  • the mobility management network element obtains the context information of the MTC GW, the association list of the MTC GW and the MTC terminal, and the context information of the MTC terminal associated with the MTC GW, and requests the 3GPP network to update all the bearers established by the MTC GW.
  • the new mobility management network element sends the identifier and address of the MTC GW and the address of the new mobility management network element to the HSS to which the MTC terminal associated with the MTC GW belongs to update and save; the new mobility management network element identifies the MTC GW. Terminal access agent capabilities. Specifically through the following fourth embodiment Description.
  • the mobility management signaling interaction and the mobility management specifically include: the MTC GW takes the MTC terminal offline.
  • the request is sent to the mobility management network element of the 3GPP network; the mobility management network element deletes the context information of the MTC terminal, and the association between the MTC terminal and the MTC GW, and sends an offline notification to the MTC terminal through the MTC GW.
  • the MTC terminal is offline:
  • the MTC GW initiates a PDN connection to the 3GPP network to deactivate, and deletes the PDN connection corresponding to the APN.
  • the MTC GW also stores information about the MTC terminal associated with itself, including at least the identifier of the MTC terminal, the attachment status of the MTC terminal, and the APN contracted by the MTC terminal.
  • the MTC UE is used as an example, and the mobility management process for the non-MTC UE and the MTC UE is the same.
  • the MTC GW is both a terminal proxy gateway for the stub network and a terminal for the 3GPP network.
  • the 3GPP network needs to authenticate the MTC GW to have the terminal access proxy capability of the stub network, and establish multiple PDN connection channels according to the multiple APNs subscribed by the MTC GW, so that the MTC GW can adopt Different PDN connection channels enable the sensor nodes (MTC UEs in the picture) belonging to different MTC Servers to connect with the MTC Server. Specifically include:
  • Step 401 The MTC GW needs to initiate an attach request to the RNS radio access network (eNodeB or RNC) for accessing the 3GPP network, including the GPRS network and the EPS network, where the MTC GW identifier (ie, IMSI) and the MTC GW are carried.
  • Information such as network access capabilities, indications for requesting IP assignment, and terminal access proxy capabilities.
  • the RNS selects an MME/SGSN (MME or SGSN) for the MTC GW to serve, And forwarding the attach request to the MME/SGSN, and carrying information such as the identifier of the MTC GW (IMSI), the network access capability of the MTC GW, the indication of requesting the IP, and the capability of the terminal access proxy to the MME/ SGSN.
  • MME MME/SGSN
  • IMSI the identifier of the MTC GW
  • IMSI the network access capability of the MTC GW
  • the indication of requesting the IP the indication of requesting the IP
  • the capability of the terminal access proxy to the MME/ SGSN.
  • Step 402 The MME/SGSN sends an authentication data request (including the IMSI of the MTC GW) to the HSS of the MTC GW home network, and the HSS first determines the subscription user data corresponding to the IMSI, if no subscription is found or the IMSI is listed in the black. In the list, the HSS returns an authentication data response to the MME/SGSN and carries the error reason; if the subscription data corresponding to the IMSI is found, the HSS returns an authentication data response (including an authentication vector) to the MME/SGSN;
  • the MME/SGSN performs an authentication procedure to verify the validity of the MSI GW's IMSI and enforces a secure mode procedure to enable secure connections.
  • Step 403 The MME/SGSN sends a location update request to the HSS of the home network of the MTC GW, where the identifier of the MME/SGSN and the identifier of the MTC GW (IMSI) are carried, and the area that the MTC GW currently accesses is notified to the HSS; the HSS is based on the MTC.
  • the GW identity finds the subscriber data and sends it to the MME/SGSN.
  • the subscriber data mainly includes: APN, bandwidth and other information;
  • the contract has the capability of the terminal network node proxy (that is, the terminal access proxy capability), and optionally, the contracted stub network node (ie, the sensor node) is different from The addresses of multiple APNs and PGWs required for MTC Server connection;
  • the MME/SGSN receives the subscription user data of the MTC GW, and checks that the MTC GW is allowed to access the network, and returns an acceptance response to the HSS. If the MME/SGSN finds that the MTC GW has roaming restrictions or access restrictions, the MME/SGSN will The MTC GW is prohibited from attaching and the HSS is notified.
  • Step 404 For the MTC GW, the MME/SGSN needs to check whether the MTC GW has the terminal access proxy capability according to the subscription user data, and if yes, identify that the MTC GW has the terminal access proxy capability, and the subsequent other MTC terminals can pass the MTC. GW access to 3GPP The internet.
  • Step 405 The MME/SGSN selects a PGW/GGSN for the MTC GW according to the default APN, and sends a bearer setup request thereto.
  • the request carries an identifier of the MTC GW (IMSI), an identifier of the MME/SGSN, an indication for assigning an IP address to the MTC GW, default bandwidth information, a PGW/GGSN address, and the like.
  • IMSI an identifier of the MTC GW
  • MME/SGSN an indication for assigning an IP address to the MTC GW
  • default bandwidth information a PGW/GGSN address
  • the PGW/GGSN requests the PCRF to deliver the QoS policy and charging rules and decision information configured for the MTC GW.
  • the PGW/GGSN establishes a PS bearer according to the QoS policy and charging information returned by the PCRF or the statically configured PCC policy, and returns a bearer setup response to the MME/SGSN.
  • Step 406 The MME/SGSN saves the bearer context, and then sends an initial context setup request or an attach accept response to the RNS, indicating that the request of the MTC GW to attach to the network has been accepted, where the APN and the PS bearer ID are carried (PS Bearer). ID), PGW/GGSN address and TEID.
  • PS Bearer PS Bearer
  • Step 407 The RNS sends an RRC connection reconfiguration request to the MTC GW, and opens the corresponding port.
  • the RRC connection reconfiguration request carries: PS Bearer ID, PGW/GGSN address, APN, IP address assigned to the MTC GW, bandwidth information, etc.
  • the MTC GW saves the APN, its own IP address, bandwidth, and PS Bearer on the local end. Important information such as ID;
  • the MTC GW sends an RRC Connection Reconfiguration Response to the RNS.
  • Step 408 The RNS sends an initial context response to the MME/SGSN, where the TEID and the address information of the RNS are used to send downlink data to the MTC GW.
  • Step 409 The MTC GW sends an attach complete message, carrying the PS Bearer ID, to notify the MME/SGSN that the attach process is complete.
  • Step 410 The MME sends an update bearer request to the PGW/GGSN, and informs the PGW/GGSN of the TEID and address of the RNS served by the MTC GW, and clears the uplink channel.
  • the PGW/GGSN sends an update 7
  • Step 411 The MTC GW functions as a proxy network terminal proxy gateway, where multiple APNs are configured to connect different MTC Servers to the sensor nodes in the stub network. Therefore, the MTC GW needs to establish multiple PDN connections.
  • the MTC GW sends a PDN connection request to the MME/SGSN, carrying information such as APN, PDN type, and PCO parameters.
  • the PDN type indication is an IPv4 or IPv6 address request
  • the PCO is an information set for transmitting the transparent data between the terminal and the PGW/GGSN.
  • Step 412 The MME/SGSN checks whether the APN is legal. If it is legal, it allocates a PS Bearer ID, and then sends a bearer setup request to the PGW/GGSN, carrying the MTC GW identity (IMSI), APN, APN-AMBR maximum bit rate, PCO. Information such as parameters.
  • IMSI MTC GW identity
  • APN APN-AMBR maximum bit rate
  • PCO PCO.
  • Information such as parameters.
  • the PGW/GGSN creates a new data entry, establishes a PS bearer corresponding to the APN, and returns a bearer setup response to the MME/SGSN, carrying the corresponding PS Bearer ID, PGW/GGSN address, and the assigned control plane and TEID of the user plane. , PCO parameters and other information.
  • Step 413 The MME/SGSN saves the bearer context, and then sends a bearer setup message to the RNS, where the message includes a PDN connection accept message sent by the MME/SGSN to the MTC GW, and the PDN connection accept message carries the APN, the PCO parameter, and the PS Bearer.
  • the ID and other parameters indicate that the request for the MTC GW to establish multiple PDN connections has been accepted.
  • the Bearer QoS parameter, the TEID of the PGW/GGSN user plane entry, and the PDN connection acceptance indication are carried in the bearer setup message.
  • Step 414 the RNS sends an RRC connection reconfiguration request to the MTC GW, and opens the corresponding port, and the RRC connection reconfiguration request carries the PDN connection accept message to the MTC GW;
  • the MTC GW sends an RRC connection reconfiguration response to the RNS to establish a corresponding radio bearer.
  • Step 415 The RNS sends a bearer setup response to the MME/SGSN, where the TEID and the address information of the RNS are used to send downlink data to the MTC GW.
  • Step 416 the MTC GW sends a PDN connection complete message, carries the PS Bearer ID, and notifies the MME/SGSN that the PDN connection establishment process is completed.
  • Step 417 The MME sends an update request to the PGW/GGSN, and notifies the TEID and address of the RNS served by the MTC GW, and clears the uplink channel.
  • the PGW/GGSN sends an update bearer response to the MME/SGSN, and the bearer update is successful.
  • the MTC GW is connected to the 3GPP network as a terminal proxy gateway for the stub network.
  • the MTC UE When the MTC UE is offline in the 3GPP network, moves to the management area of the MTC GW, and establishes a local connection with the MTC GW in the stub network, the MTC UE learns that the MTC GW has the terminal access proxy capability.
  • the MTC UE needs to communicate with the MTC Server, the MTC UE accesses the 3GPP network through the MTC GW, and the 3GPP network is responsible for authenticating the MTC UE.
  • the MME/SGSN is responsible for associating the context information of the MTC GW with the context information of the MTC UE, and maintaining a relationship list corresponding to the MTC GW and the MTC UE.
  • the MTC GW decides to create a PDN connection corresponding to the APN according to the APN signed by the MTC UE. Specifically include:
  • Step 501 The offline MTC UE moves to the area managed by the MTC GW in the 3GPP network, or the offline MTC UE is originally deployed in the MTC GW area, and the 3GPP network access status maintained by the MTC UE is offline.
  • the MTC UE establishes a local connection with the MTC GW in the stub network, such as adopting a wireless connection technology such as ZigBee, Bluetooth, WLAN, and accepts management and proxy of the MTC GW in the local network, and the MTC GW notifies the MTC UE of its 3GPP terminal access proxy capability. .
  • a wireless connection technology such as ZigBee, Bluetooth, WLAN
  • the MTC UE When the MTC UE needs to establish data communication with the MTC Server, the MTC UE needs to initiate an access request to the MTC GW through the local network signaling, requesting access to the 3GPP network through the MTC GW.
  • Step 502 The MTC GW initiates a NAS request to the RNS radio access network, where the MTC UE access request includes an MTC UE request access indication, an MTC UE identifier (IMSI), and an MTC UE network access capability. );
  • the RNS forwards the access request to the MTC GW attached via the NAS request.
  • the MME/SGSN also carries information such as the MTC UE requesting the access indication, the identity of the MTC UE (IMSI), and the network access capability of the MTC UE to the MME/SGSN.
  • Step 503 The MME/SGSN learns from the NAS request that the MTC UE requests access to the network through the MTC GW, and first performs authentication authentication on the MTC UE.
  • the MME/SGSN sends an authentication data request (including the IMSI of the MTC UE) to the HSS to which the MTC UE belongs, and the HSS first determines the subscription user data corresponding to the IMSI. If no subscription is found or the IMSI is blacklisted, the HSS Returning the authentication data response to the MME/SGSN and carrying the error reason; if the subscriber data corresponding to the IMSI is found, the HSS returns an authentication data response message (including an authentication vector) to the MME/SGSN;
  • the MME/SGSN performs an authentication procedure to the MTC UE to verify the legitimacy of the terminal IMSI and performs a security mode procedure to enable the secure connection.
  • the MTC GW transparently transmits the authentication data and vector of the MTC UE and the MME/SGSN.
  • the MTC GW In the process of performing authentication authentication on the 3GPP network by the MTC UE through the MTC GW, the MTC GW only completes the signaling of the 3GPP network and the signaling protocol of the local network. Conversion.
  • the transmission security of the MTC GW and the MTC UE is provided by the local stub network, and the transmission security of the MTC GW and the MME/SGSN is handled by the 3GPP network.
  • Step 504 The MME/SGSN sends a location update request to the HSS to which the MTC UE belongs, and the message carries information such as the address of the MME/SGSN, the identifier and address of the MTC GW, and the identifier of the MTC UE to notify the MTC UE of the currently accessed area.
  • the HSS saves the information of the MME/SGSN, the identifier and the address of the MTC GW, and searches for the subscriber data of the MTC UE according to the identifier of the MTC UE, and sends the data to the MME/SGSN.
  • the subscriber data mainly includes information such as APN and bandwidth.
  • the MME/SGSN receives the subscriber data of the MTC UE, checks that the MTC UE is allowed to access the network, and returns an accepting user response to the HSS. If the MME/SGSN finds that the MTC UE has roaming restrictions or access restrictions, the MME/SGSN will Prohibit the attachment of the MTC UE and notify HSS.
  • Step 505 The MME/SGSN saves the context information of the MTC UE, and associates with the MTC GW. For example, the “Access Mode: MTC GW Proxy Access” and the identifier of the MTC GW are added to the context information of the MTC UE. Maintaining an association list between the MTC GW and the MTC UE in the MME/SGSN, for example, the association list stores the mapping relationship between the IMSI of the MTC GW and the IMSIs of the multiple associated MTC UEs, and the association list may be placed in the context information of the MTC GW. Or maintenance alone.
  • Step 506 The MME/SGSN returns a NAS response to the MTC GW, and carries the MTC UE with the acceptance information to the MTC GW, where the MTC UE accepts the MTC UE access indication, and the part of the MTC UE, such as the APN.
  • Step 507 The MTC GW needs to initiate a 3GPP network access response to the MTC UE by using local network signaling, and notify the MTC UE that the MTC GW has accessed the 3GPP network through the MTC GW.
  • Step 508 After receiving the 3GPP network access response of the MTC GW, the MTC UE changes the 3GPP network access status to the MTC GW attachment status.
  • Step 509 The MTC GW saves the APN, the terminal identifier (IMSI), the attachment status, and the like information of the MTC UE, and checks whether the PDN connection has been established for the APN signed by the MTC UE. If not, the MTC GW needs to establish a PDN connection for the APN. . If yes, since the MTC GW has established a PDN connection for the APN, the data transmission of the MTC UE can be directly on the PDN link channel corresponding to the APN, and no new PDN connection needs to be established.
  • IMSI terminal identifier
  • the attachment status and the like information of the MTC UE
  • Step 510 If the MTC GW does not establish a PDN connection to the subscribed APN of the MTC UE, the MTC GW sends a PDN connection request to the MME/SGSN by using the APN of the MTC UE, and carries information such as the APN, the PDN type, and the PCO parameter, and the PDN type indication is IPv4. Or an IPv6 address request, the PCO is a set of information that the terminal and the PDN GW/GGSN transmit transparent data.
  • Step 511 The MME/SGSN checks whether the APN is legal. If not in the subscription data of the MTC GW, the MME/SGSN searches for the APN subscription information in the MTC UE context information associated with the MTC GW. If it is legal, it allocates a PS Bearer ID, and then sends a bearer setup request to the PGW/GGSN, carrying the MTC GW identity (IMSI), APN, APN-AMBR maximum bit rate, PCO parameters and the like;
  • IMSI MTC GW identity
  • the PGW/GGSN creates a new data entry, establishes a PS bearer corresponding to the APN, and returns a bearer setup response to the MME/SGSN, carrying the corresponding PS Bearer ID, PGW/GGSN address, and the assigned control plane and TEID of the user plane. , PCO parameters and other information.
  • Step 512 The MME/SGSN saves the bearer context, and then sends a bearer setup message to the RNS, where the message includes a PDN connection accept message sent by the MME/SGSN to the MTC GW, and the PDN connection accept message carries the APN, the PCO parameter, and the PS Bearer.
  • the ID and other parameters indicate that the request for the MTC GW to establish multiple PDN connections has been accepted.
  • the Bearer QoS parameter, the TEID of the PGW/GGSN user plane entry, and the PDN connection acceptance indication are carried in the bearer setup message.
  • Step 513 The RNS sends an RRC connection reconfiguration request to the MTC GW, and opens the corresponding port.
  • the RRC connection reconfiguration request carries a PDN connection accept message to the MTC GW;
  • the MTC GW sends an RRC connection reconfiguration response to the RNS to establish a corresponding radio bearer.
  • Step 515 The MTC GW sends a PDN connection complete message, carries the PS Bearer ID, and notifies the MME/SGSN PDN connection establishment process.
  • Step 516 The MME sends an update bearer request to the PGW/GGSN, and notifies the TEID and address of the RNS served by the MTC GW, and clears the uplink channel.
  • the PGW/GGSN sends an update bearer response to the MME/SGSN, and the bearer update is successful.
  • the MTC GW has been connected to the 3GPP network as a terminal proxy gateway of the stub network.
  • the MTC UE When the MTC UE is online in the 3GPP network, moving to the management area of the MTC GW Domain, and establish a local connection with the MTC GW in the stub network.
  • the MTC UE needs to switch the wireless access point from the 3GPP network to the MTC GW according to the policy, such as preferential access through the local network proxy.
  • the MTC UE is connected to the MTC GW of the local network, and knows that the MTC GW has the terminal access proxy capability, and requests the 3GPP network to switch the wireless access point through the MTC GW, and the 3GPP network associates the MTC UE with the MTC GW, and
  • the radio bearer resources and core network bearer resources in the 3GPP network are released. Specifically include:
  • Step 601 The MTC UE that is online in the 3GPP network moves to the area managed by the MTC GW, and the 3GPP network access status maintained by the MTC UE is online.
  • the MTC UE establishes a local connection with the MTC GW in the stub network, such as ZigBee, Bluetooth, WLAN and other wireless connection technologies, and accepts the management and proxy of the MTC GW in the local network, and the MTC GW notifies the MTC UE of its terminal access proxy capability.
  • the MTC GW such as ZigBee, Bluetooth, WLAN and other wireless connection technologies
  • the MTC UE needs to switch the wireless access point from the 3GPP network to the MTC GW according to the policy, such as preferential access through the local network proxy.
  • the MTC UE needs to initiate an update of the wireless access point request to the MTC GW through local network signaling, requesting release and The connection of the 3GPP network is changed to access the 3GPP network through the MTC GW.
  • Step 602 The MTC GW initiates a NAS request to the RNS radio access network, where the MTC UE initiates an update radio access point request, and the request message carries information such as an MTC UE identifier (IMSI).
  • IMSI MTC UE identifier
  • the RNS will forward the updated wireless access point request of the MTC UE to the MME/SGSN attached to the MTC GW through the NAS request, and also carry important information such as the identifier of the MTC UE to the MME/SGSN.
  • Step 603 The MME/SGSN sends a location update request to the HSS to which the MTC UE belongs, and notifies the HSS to which the MTC UE belongs to the HSS GW's identity and address, the SGSN/MME address, and the identifier of the MTC UE.
  • the HSS saves the identifier of the MTC GW. With address information.
  • Step 604 The MME/SGSN performs the context information of the MTC UE with the MTC GW. Association, for example, adding "access mode: MTC GW proxy access" and the identifier of the MTC GW in the context information of the MTC UE.
  • the association list of the MTC GW and the MTC UE is updated in the MME/SGSN, and the MTC UE is instead proxyed to the 3GPP network by the MTC GW.
  • Step 605 The MME/SGSN releases the MTC UE-related resources, and specifically: initiates a delete bearer request to the PGW/GGSN, and requests to delete all bearers established for the MTC UE. Specifically: the SGW, and the PGW/GGSN delete the bearer context corresponding to the MTC UE, and release the allocated bearer resource. The delete bearer response is then returned to the MME/SGSN.
  • Step 606 The MME/SGSN returns a NAS signaling response to the MTC GW, and carries the MTC UE to update the wireless access point acceptance information to the MTC GW, where the information includes an update wireless access point acceptance indication, and part of the subscription information of the MTC UE, such as an APN. .
  • Step 607 The MTC GW saves related information of the MTC UE, and returns an updated wireless access point response to the MTC UE by using local network signaling, notifying the MTC UE that the wireless access point has been updated, and the MTC UE can access the 3GPP network through the MTC GW. .
  • Step 608 After the MTC UE receives the updated wireless access point response of the MTC GW, the 3GPP network actively releases the wireless resource and the wireless connection. Specifically, the MME/SGSN sends a connection release command to the RNS, and notifies the RNS to release the wireless connection of the MTC UE. The RNS releases the radio resources allocated to the MTC UE. The RNS sends an RRC connection release message to the MTC UE, and releases the air interface resource allocated to the MTC UE.
  • the MTC UE after receiving the updated wireless access point response of the MTC GW, notifies the 3GPP network to release the wireless resource and the wireless connection, specifically: the MTC UE requests the RNS to release the wireless connection, and the RNS releases the wireless connection and the wireless resource, and notifies the MME. /SGSN.
  • the MTC UE After receiving the updated wireless access point response of the MTC GW, the MTC UE changes the 3GPP network access status to access through the MTC GW while releasing the wireless connection wireless resource.
  • Step 609 Check whether the MTC GW has established a PDN connection for the APN signed by the MTC UE. If not, the MTC GW needs to establish a PDN connection for the APN. If yes, because The MTC GW has established a PDN connection for the APN. The data transmission of the MTC UE can be directly performed on the PDN link channel corresponding to the APN, and no new PDN connection needs to be established.
  • the APN that is subscribed to the MTC UE establishes a PDN connection, that is, steps 610-616, and the implementation is the same as steps 510-516, and details are not described herein again.
  • the MTC GW has been connected to the 3GPP network as a terminal proxy gateway for the stub network.
  • the MTC GW needs to initiate a TAU request.
  • the source MME/SGSN needs to send the context information of the MTC GW and the context information and association list of the MTC UE associated with it to the new MME/SGSN, and the new MME/SGSN address, MTC GW.
  • the identity and address are sent to the HSS update to which the MTC GW belongs.
  • the new MME/SGSN identifies that the MTC GW is a terminal access proxy gateway of the stub network, maintains the proxy association of the MTC GW with the MTC UE, and maintains an association list.
  • Step 701 When the MTC GW moves in the 3GPP network, the area managed by the source MME/SGSN moves to the area managed by the new MME/SGSN.
  • the MTC GW needs to be updated.
  • the MTC GW initiates a TAU location update request to the new MME/SGSN, and carries information such as the identifier of the MTC GW, the network capability of the MTC GW, and the PS Bearer status.
  • Step 702 The new MME/SGSN obtains the address of the source MME/SGSN, and sends a context request for acquiring the MTC GW to the source MME/SGSN, where the identifier of the MTC GW, the new MME/SGSN address, and the like are included, and the source MME/SGSN is requested. Sending all context information of the MTC GW to the new MME/SGSN;
  • the source MME/SGSN After receiving the Context Request for the MTC GW, the source MME/SGSN sends the context information of the MTC GW, the association list of the MTC GW and the MTC UE, and the context information of the MTC UE to the new MME/SGSN.
  • Step 703 The new MME/SGSN initiates an update bearer request to the PGW/GGSN, requesting to update all bearers established by the MTC GW, and the PGW/GGSN needs to update the corresponding corresponding to the MTC GW.
  • Bearer context such as updating the TEID of the MME/SGSN in the bearer context.
  • the update bearer response is then returned to the new MME/SGSN.
  • Step 704 The new MME/SGSN initiates a location update request to the HSS to which the MTC GW belongs, and carries information such as the location information of the MTC GW and the address of the new MME/SGSN, and the HSS updates and saves the information.
  • the new MME/SGSN initiates a location update request to the HSS to which all MTC UEs of the MTC GW proxy, and carries the information of the address of the MTC GW and the address of the new MME/SGSN, and the HSS updates and saves.
  • Step 705 The HSS to which the MTC GW belongs initiates a request to delete the user data to the source MME/SGSN, and the source MME/SGSN deletes all the information of the MTC GW and all the information of the associated MTC UE.
  • Step 706 The HSS to which the MTC GW belongs returns a location update response to the new MME/SGSN, and sends the subscription user data of the MTC GW to the new MME/SGSN.
  • the subscription user data includes information such as the terminal access proxy capability indication and the APN.
  • Step 707 The new MME/SGSN identifies that the MTC GW is the terminal access proxy gateway of the stub network according to the subscription user information of the MTC GW, and subsequently needs to maintain the association list of the MTC GW and the MTC UE.
  • Step 708 The new MME/SGSN sends a TAU accept message to the MTC GW, and the MTC GW successfully performs location update on the target network.
  • the MTC GW has access to the 3GPP network as a terminal access proxy of the stub network, and the MTC UE has accessed the 3GPP network through the MTC GW. If the MTC UE moves out of the area managed by the MTC GW, or the MTC UE needs to go offline from the 3GPP network according to the policy, the MTC GW replaces the MTC UE to initiate an offline request of the MTC UE to the 3GPP network, and the MME/SGSN deletes the context of the MTC UE, and MTC GW association, and notify HSS of the end Offline. Specifically include:
  • Step 801 In a scenario where the MTC UE has accessed the 3GPP network through the MTC GW, according to the terminal policy or configuration, if the MTC UE has sent the data, the MTC UE needs to disconnect from the 3GPP network, and the MTC UE needs to pass the local network.
  • the signaling initiates an offline request to the MTC GW, requesting to release the connection between the MTC UE and the 3GPP network;
  • step 802 the MTC UE has moved out of the area managed by the MTC GW, and the MTC GW needs to initiate an offline request instead of the MTC UE, requesting to release the connection between the MTC UE and the 3GPP network.
  • Step 803 The MTC GW sends a NAS request to the MME/SGSN, and carries an offline request of the MTC UE, where the offline request includes information such as an identifier of the MTC UE.
  • Step 804 After receiving the offline request, the MME/SGSN notifies the HSS to which the MTC UE belongs, and the MTC UE has applied for offline.
  • Step 805 The MME/SGSN deletes the context information of the MTC UE and associates with the MTC GW, and the MTC UE does not proxy through the MTC GW.
  • Step 806 The MME/SGSN returns a NAS response to the MTC GW, and carries a notification message (with an offline acceptance or an offline notification indication) that the MTC UE has been offline.
  • Step 807 The MTC GW sends an offline notification to the MTC UE by using local network signaling, and notifies that the MTC UE is offline on the 3GPP network.
  • Step 808 The MTC UE changes the 3GPP network status to offline.
  • Step 809 The MTC GW checks whether the MTC UE subscribed to the offline MTC UE is associated with another MTC UE. If other MTC UEs use the PDN connection link corresponding to the APN, the MTC GW does not initiate the PDN connection to be activated. If no other MTC UEs are connected to the 3GPP network under the APN, the MTC GW needs to initiate a PDN connection to deactivate and delete the PDN connection corresponding to the APN.
  • Step 810 The MTC GW sends the APN signed by the MTC UE to the MME/SGSN.
  • the PDN connection deactivation request carries information such as LBI (Bearing Identifier), APN, etc.
  • LBI Bearing Identifier
  • APN APN
  • Step 811 The MME/SGSN decides to release the PDN connection, and the MME/SGSN sends a PDN connection deletion request to the PGW/GGSN, where the LBI carries the LBI. Specifically, the SGW and the PGW/GGSN delete the PDN connection according to the LBI, and release the allocated bearer resources. The PGW/GGSN returns a PDN connection deletion success response to the MME/SGSN.
  • Step 812 The MME/SGSN sends a deactivation bearer request to the RNS, requesting to deactivate all the bearers in the PDN connection, and the deactivated bearer request carries the LBI or the APN for identification, and the RNS deletes all bearer resources under the PDN connection.
  • Step 813 The RNS sends an RRC connection reconfiguration request to the MTC GW, where the bearer activates the bearer context request.
  • the MTC GW deletes the context information of all bearers under the PDN connection, and then sends an RRC connection reconfiguration response to the RNS.
  • Step 814 The RNS returns a deactivation bearer corresponding to the MME/SGSN, and confirms that the deactivation bearer is completed.
  • Step 815 After the bearer is deactivated, the MTC GW sends a deactivated bearer accept message to the RNS through the NAS signaling, and the RNS sends the deactivated bearer accept message to the MME/SGSN.
  • the present invention also provides a system for mobility management of an MTC terminal, including: an MTC terminal, an MTC GW, and a 3GPP network;
  • the MTC GW is used to replace the MTC terminal with the 3GPP network for mobility management signaling interaction; the 3GPP network is used for mobility management of the MTC terminal through the MTC GW.
  • the 3GPP network includes a mobility management network element, and when the MTC GW first accesses the 3GPP network, after acquiring the subscription user data of the MTC GW, the MTC GW has the terminal according to the capability of the terminal access agent signed in the subscription user data. Access agent capability;
  • the mobility management network element is further configured to associate the context information of the MTC terminal with the MTC GW when the MTC terminal accesses the 3GPP network through the MTC GW, and maintain the MTC GW and the The associated list of MTC terminals.
  • the MTC GW is also used to save the information of the MTC terminal associated with itself, including at least the identifier of the MTC terminal, the attachment status of the MTC terminal, and the APN signed by the MTC terminal.

Landscapes

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

Description

一种对 MTC终端进行移动性管理的方法和系统 技术领域
本发明涉及移动通信领域，特别是指一种对 MTC终端进行移动性管理 的方法和系统。 背景技术
近年来机器到机器间的通信（ M2M, Machine to Machine )业务逐渐开 始得到应用， 如物流系统、 远程抄表、 智能家居等应用。 M2M服务商使用 现有的无线网络，如通用分组无线业务（ GPRS , General Packet Radio service ) 网络、 演进分组系统（EPS, Evolved Packet System ) 网络等 PS网络开展 M2M业务。 因 M2M业务与人与人之间的通信（ H2H, Human to Human ) 业务有明显的差异性， 需要对现有的网络进行必要的优化， 以获得最佳的 网络管理与网络通讯质量。
GPRS网络是一个基于包交换的第二代移动通信网络，到了第三代移动 通信系统， GPRS演进为通用移动通信系统分组交换（UMTS PS , Universal Mobile Telecommunication system Packet Switch 或。 口图 1所示为 UMTS PS 的网络架构， 该网络架构中包含如下网元：
无线网络系统（RNS , Radio Network system ), RNS中包含 NodeB与 RNC, NodeB为终端提供空口连接； RNC ( Radio Network Controller )为无 线网络控制器， 主要用于管理无线资源以及控制 NodeB。 RNC与 NodeB之 间通过 Iub 口连接， 终端通过 RNS接入 UMTS 的分组域核心网 （Packet Core );
服务 GPRS支持节点（ SGSN, Serving GPRS Support Node ), 用于保存 用户的路由区位置信息， 负责安全和接入控制； SGSN通过 Iu口与 RNS相 连；
网关 GPRS支持节点 （GGSN, Gateway GPRS support Node ), 用于负 责分配终端的 IP地址和到外部网络的网关功能，在内部通过 Gn口与 SGSN 相连；
归属位置寄存器（ HLR, Home Location Register ), 用于保存用户的签 约数据和当前所在的 SGSN地址， 通过 Gr口与 SGSN相连， 通过 Gc口与 GGSN相连；
分组数据网络（ PDN , Packet Data Network ) , 用于为用户提供基于分 组的业务网， 通过 Gi口与 GGSN相连。
MTC Server为 M2M应用服务器， 用于为用户提供 M2M应用， 通过 MTCi接口与 GGSN相连。
在图 1中， 机器类型通信（MTC, Machine Type Communication ) UE 需要通过 GPRS网络向 MTC Server传输数据信息。 GPRS网络为此次传输 建立 RNC到 GGSN之间的隧道，隧道基于隧道协议（ GTP, GPRS Tunneling Protocol ), 数据信息通过 GTP隧道实现可靠传输。
随着无线宽带技术的发展， 业务层对传输层的带宽、 时延等性能要求 越来越高。 为提高其网络性能， 降低网络建设及运营成本， 3GPP致力于系 统架构演进 ( SAE, System Architecture Evolution ) 的研究， 目的是使得演 进的分组网 （EPC, Evolved Packet Core )可提供更高的传输速率、 更短的 传输延时、优化分组，及支持演进的 UTRAN( E-UTRAN, Evolved UTRAN ), UTRAN、无线局域网（ WLAN, Wireless Local Area Network )及其他非 3GPP 的接入网络之间的移动性管理。
目前 SAE的架构如图 2所示，其中，演进的无线接入网（ E-RAN, Evolved Radio Access Network ) 中包含的网元是演进节点 B ( eNodeB , Evolved NodeB ), 属于 RNS 系统， 用于为用户的接入提供无线资源； 分组数据网 ( PDN, Packet Data Network )是为用户提供业务的网络； EPC提供了更低 的延迟， 并允许更多的无线接入系统接入， 其包括如下网元：
移动管理实体（ MME , Mobility Management Entity ) , 是控制面功能实 体， 临时存储用户数据的服务器， 负责管理和存储用户设备（UE, User Equipment )的上下文（比如用户标识、移动性管理状态、用户安全参数等）， 为用户分配临时标识， 当 UE驻扎在该跟踪区域或者该网络时， 负责对该用 户进行鉴权。
服务网关（SGW, Serving Gateway ), 是一个用户面实体， 负责用户面 数据路由处理， 终结处于空闲（ECM_IDLE )状态的 UE的下行数据。 管理 和存储 UE的 SAE承载（ bearer )上下文， 比如 IP承载业务参数和网络内 部路由信息等。 SGW是 3GPP系统内部用户面的锚点， 一个用户在一个时 刻只能有一个 SGW。
分组数据网网关（ PGW, PDN Gateway ),是负责 UE接入 PDN的网关， 分配用户 IP地址， 也是 3GPP和非 3GPP接入系统的移动性锚点， PGW的 功能还包括策略实施、 计费支持。 用户在同一时刻能够接入多个 PGW。 策 略与计费实施功能实体（ PCEF, Policy and Charging Enforcement Function ) 也位于 PGW中。
策略与计费规则功能实体（ PCRF, Policy and Charging Rules Function ), 负责向 PCEF提供策略控制与计费规则。
归属用户服务器（ HSS , Home Subscriber Server ), 负责永久存储用户 签约数据， HSS 存储的内容包括 UE 的国际移动用户识别码 （IMSI, International Mobile Subscriber Identification )、 和 PGW的 IP地址。
在物理上， SGW和 PGW可能合一， EPC系统用户面网元包括 SGW 和 PGW。
MTC Server用于为用户提供 M2M应用，通过 MTCi接口与 PGW相连。 MTC Server主要负责对 MTC设备的信息采集和数据存储 /处理等工作， 并 可对 MTC设备 ( MTC UE )进行必要的管理。
MTC UE与 UE类似， 负责收集若干采集器的信息并通过 RAN节点接 入核心网， 并与 MTC Server交互数据。
在图 2中， MTC UE需要通过 EPS网络向 MTC Server传输数据信息。 EPS网络为此次传输建立 SGW到 PGW之间的 GTP隧道， 数据信息通过 GTP隧道实现可靠传输。
图 3是现有技术中， MTC UE接入到 EPS网络， 执行网络附着、 IP承 载建立的移动性管理过程， 包括以下步驟：
步驟 101 , MTC UE为了接入到 PS网络，包括 GPRS网络与 EPS网络， 向 RNS无线接入网络（包括 eNodeB或 RNC )发起附着请求， 在其中携带 了 MTC UE的终端标识 IMSI、 MTC UE的网络接入能力、 和请求分配 IP 的指示等信息；
RNS为 MTC UE选择一个为之服务的 MME/SGSN ( MME或 SGSN ), 并将附着请求转发到该 MME/SGSN。
步驟 102, MME/SGSN向 HSS发送鉴权数据请求（含 IMSI ), HSS首 先判断 IMSI对应的签约数据， 如果查找不到任何签约或者 IMSI已被列入 黑名单， 则 HSS向 MME/SGSN返回鉴权数据响应、 并携带错误原因； 如 果找到 IMSI对应的签约数据，则 HSS向 MME/SGSN返回鉴权数据响应（含 鉴权向量）；
MME/SGSN执行鉴权流程以验证终端 IMSI的合法性， 并执行安全模 式流程以启用安全连接。
步驟 103 , MME/SGSN向归属网的 HSS发送位置更新请求， 消息中携 带 MME的标识、和 MTC UE的标识，以告知 MTC UE当前所接入的区域； HSS 根据 MTC UE 的标识查找出 MTC UE 的签约用户数据， 发送给 MME/SGSN。 签约用户数据中主要包含： 缺省接入点名称（APN, Access Point Name )、 带宽大小等信息；
MME/SGSN接收到用户数据， 检查 MTC UE是否被允许接入到网络， 向 HSS返回接收用户响应； 若 MME/SGSN发现 MTC UE有漫游限制或接 入限制等问题， MME/SGSN将禁止 MTC UE附着， 并通知 HSS。
步驟 104 , MME/SGSN根据默认 APN为 MTC UE选择一个 PGW/GGSN ( PGW或 GGSN ),并向其发送建立承载的请求。在该请求中携带 MTC UE 的标识、 MME/SGSN的标识、 为 MTC UE分配 IP地址的指示、 缺省带宽 信息、 和 PGW/GGSN地址等信息；
如有必要， PGW/GGSN向 PCRF请求为该 MTC UE分配所配置的策略 和计费规则决策信息；
PGW/GGSN根据 PCRF返回的策略和计费规则决策信息或静态配置的 PCC策略， 建立 PS承载， 并向 MME/SGSN返回承载建立响应。
步驟 105 , MME/SGSN保存承载上下文 Bearer context, 然后向 RNS发 送初始上下文设置请求或附着接受响应， 表明 MTC UE的附着到网络的请 求已被接受， 携带 APN、 PS Bearer ID, PGW/GGSN地址与隧道端口标识 ( TEID, Tunnel Endpoint Identifier )。
步驟 106, RNS向 MTC UE发送 RRC连接重配置请求， 并开放相应的 端口。 在 RRC连接重配置请求中携带了： PS Bearer ID、 PGW/GGSN地址、 APN、 分配给 MTC UE的 IP地址、 带宽信息等；
MTC UE向 RNS发送无线承载重配置响应， 建立无线承载。
步驟 107, RNS 向 MME/SGSN发送初始上下文响应， 该消息中包含 RNS的 TEID及地址信息， 用于发送下行数据给 MTC UE。
步驟 108 , MTC UE发送附着完成消息， 携带 PS Bearer ID, 通知 MME/SGSN附着过程完成。 步驟 109, MME向 PGW/GGSN发送更新 载请求， 通知为 MTC UE 服务的 RNS 的 TEID 标识及地址， 打通上行通道。 PGW/GGSN 向 MME/SGSN发送更新 7|载响应， 载更新成功。
图 4是现有技术中， MTC UE已接入到 EPS网络， 当 MTC UE发生位 置移动时， 执行网络位置更新的移动性管理过程， 包括以下步驟：
步驟 201 , 当 MTC UE在 3GPP网络发生移动时， 由源 MME/SGSN管 理的区域移动到新 MME/SGSN管理的区域。 MTC UE需要进行位置更新。 MTC UE向新 MME/SGSN发起 TAU位置更新请求 ,携带 MTC UE的标识、 MTC UE的网络能力、 PS Bearer状态等信息。
步驟 202, 新 MME/SGSN根据 MTC UE的标识得到源 MME/SGSN的 地址， 并向源 MME/SGSN发送获取 MTC UE的上下文请求， 在其中包含 MTC UE的标识、新 MME/SGSN地址等信息，请求源 MME/SGSN将 MTC UE的所有上下文信息都发给新 MME/SGSN;
源 MME/SGSN收到获取 MTC UE的上下文请求后， 将 MTC UE的上 下文信息发给新 MME/SGSN。
步驟 203 , 新 MME/SGSN向 PGW/GGSN发起更新承载请求， 请求更 新该 MTC UE建立的所有承载， PGW/GGSN需要更新该 MTC UE对应的 承载上下文， 如更新承载上下文中的 MME/SGSN 的 TEID。 然后向新 MME/SGSN返回更新 载响应。
步驟 204, 新 MME/SGSN向 HSS发起位置更新请求， 携带 MTC UE 的位置信息与新 MME/SGSN地址等信息， HSS进行更新并保存。
步驟 205 , HSS 向源 MME/SGSN 发起删除用户数据请求， 源 MME/SGSN删除保存的该 MTC UE的所有信息。
步驟 206, HSS向新 MME/SGSN返回位置更新响应，将 MTC UE的签 约用户数据发给新 MME/SGSN, 签约用户数据包含 MTC UE的 APN、 和 带宽等信息。
步驟 207, 新 MME/SGSN发送 TAU接受消息给 MTC UE, MTC UE 成功在目标（新） 网络上进行了位置更新。
图 5是现有技术中， MTC UE已接入到 EPS网络， 当 MTC UE需要离 线时， 如关机， 执行网络离线的移动性管理过程， 包括以下步驟：
步驟 301 , MTC UE 发起从 3GPP 网络离线的流程。 MTC UE 向 MME/SGSN发送离线请求， 消息中包含 MTC UE的标识等信息。
步驟 302, MME/SGSN收到 MTC UE发起的离线请求后， MME/SGSN 删除该 MTC UE相关的上下文信息；
然后， MME/SGSN通过 SGW向 PGW/GGSN发送删除承载请求， 携 带 LBI标识， 请求删除该 MTC UE的 PDN连接。 SGW以及 GGSN/PGW 根据 LBI删除该 MTC UE的 PDN连接，释放分配的承载资源。 PGW/GGSN 向 MME/SGSN返回 7|载删除成功响应。
步驟 303 , MME/SGSN向 MTC UE返回离线请求接受消息，通知 MTC UE网络已对其进行离线操作。
步驟 304, MME/SGSN向 RNS发送 PS连接释放命令， 通知 RNS释放 PS连接， RNS释放无线相关资源。 RNS向 MTC UE发送 PS连接释放消息， 释放与 MTC UE的空口资源。
M2M业务是以机器终端智能交互为核心的、 网络化的应用与服务。 它 采用智能机器终端， 通过无线网络传输信息， 为客户提供的信息化解决方 案， 用于满足客户对监控、 指挥调度、 数据采集和测量等方面的信息化需 求。
M2M的通信对象为机器对机器， 可以是人与机器之间的通信， 机器与 服务器之间的通信， 不同智能终端之间的通信。 不同应用的 MTC设备具有 不同的特性， 如电梯等升降机设备具有低移动性、 PS only属性， 而监视、 警报设备除具有低移动性、 PS only外， 还具有低数据传输和高可用性等属 性。 因此需要针对不同应用的 MTC设备进行不同的系统优化， 可有效的对 MTC设备进行管理、 监控、 付费等。
在 M2M应用对 PS网络优化的影响研究中， 提出一种新的场景， 见图 6。 图 6是一个物联网的场景， 它描述物联网分为三层： 末梢层、 网络层与 应用层。 末梢层主要是指传感器网络， 传感器节点采用短距互连技术， 如 蓝牙、 ZigBee、 WLAN、 RFID技术实现本地网络的互连， 短距距离最大可 达几百米或上千米。 传感器节点用于收集传感器的数据， 并通过网络层传 输将采集的数据传输给 MTC Server, 如远程抄表类的应用。
在图 6中，对于传感器节点来说，很多是没有 3GPP网络通信能力的终 端， 称为非 MTC终端， 因为从成本与技术实现而言， 传感器节点全部配置 3GPP通信模组不现实。 因此需要在本地末梢网络有一个 3GPP网络终端接 入代理设备， 在图中为 MTC GW, 称为终端接入代理网关。 MTC GW既有 末梢网络节点间通信能力， 也具有 3GPP 网络通信能力与终端接入代理能 力， 需要实现本地网络的信令与数据向 3GPP网络的信令与数据进行适配。
对于图 6的场景，在末梢网络里，终端既可能是没有 3GPP通信能力也 没有 3GPP用户身份的终端， 也可能是没有 3GPP通信能力但有 3GPP用户 身份的终端（非 MTC UE ), 如具有 SIM卡但没有 3GPP通信模组， 也可能 是具有 3GPP通信能力的终端 （ MTC UE ), 当 MTC UE从其它区域漫游到 该 MTC GW管理的末梢网络区域， 根据终端策略或网络通知， 需要在本地 网络通过该 MTC GW接入到 3GPP网络。 或某些传感器节点就具有 3GPP 通信能力， 当 MTC GW异常时， 可直接接入到 3GPP网络， 实现与 MTC Server的传输。
因此， 针对 MTC GW代理末梢网络终端接入 3GPP网络的场景， 现有 技术没有针对 MTC GW作为末梢网络中终端接入代理网关的相应移动性管 理流程。 对 3GPP网络而言， 首先需要解决如何对 MTC GW代理各 MTC 终端 （包括 MTC UE和非 MTC UE )进行接入与移动性管理的问题， 因此 需要对现有 PS网络的移动性管理流程进行优化， 以满足通过 MTC GW对 MTC终端进行接入控制与移动性管理的需求。 发明内容
有鉴于此，本发明的主要目的在于提供一种对 MTC终端进行移动性管 理的方法和系统， 针对末梢网络中 MTC GW对 MTC终端进行代理接入到 3GPP网络的场景， 能够解决 3GPP网络如何通过 MTC GW对接入的 MTC 终端进行移动性管理的问题。
为了达到上述目的， 本发明的技术方案是这样实现的：
本发明提供了一种对 MTC终端进行移动性管理的方法， 该方法包括： 终端接入代理网关（ MTC GW )代替机器类型通信（ MTC )终端与 3GPP 网络进行移动性管理信令交互； 3GPP网络通过 MTC GW对 MTC终端进行 移动性管理。
进一步地，所述 MTC终端包括具有 3GPP通信能力的 MTC UE和不具 有 3GPP通信能力但具有 3GPP网络用户身份的非 MTC UE。
进一步地， MTC GW代替 MTC终端与 3GPP网络进行移动性管理信令 交互之前， 该方法还包括：
所述 MTC GW首次接入到 3GPP网络时， 3GPP网络中的移动性管理 网元获取到所述 MTC GW的签约用户数据后，根据所述签约用户数据中签 约的终端接入代理能力识别所述 MTC GW具有终端接入代理能力。
进一步地， 当所述 MTC终端请求通过 MTC GW接入到 3GPP网络时， 所述移动性管理信令交互和所述移动性管理， 具体包括：
MTC GW将 MTC终端的接入请求发送给 3GPP网络的移动性管理网 元； 所述移动性管理网元对 MTC终端进行鉴权认证， 并由所述 MTC GW 透传 MTC UE与移动性管理网元的鉴权数据与向量；
所述移动性管理网元将 MTC GW的标识及地址、所述移动性管理网元 的地址发送给与 MTC GW关联的 MTC终端归属的 HSS进行保存；
所述鉴权认证通过、 且允许 MTC终端接入 3GPP网络时， 所述移动性 管理网元保存 MTC终端的上下文信息并与 MTC GW进行关联， 并在所述 移动性管理网元中更新 MTC GW与 MTC终端的关联列表。
进一步地， 当所述 MTC终端通过 MTC GW接入到 3GPP网络后， 该 方法还包括：所述 MTC GW为所述 MTC终端签约的缺省接入点名称（ APN ) 建立对应的分组数据网络（ PDN )连接。
进一步地， 当所述 MTC终端通过 MTC GW向 3GPP网络请求切换无 线接入点时， 所述移动性管理信令交互和所述移动性管理， 具体包括：
MTC GW将 MTC终端的更新无线接入点请求发送给 3GPP网络的移动 性管理网元；
所述移动性管理网元将 MTC终端的上下文信息与 MTC GW进行关联， 并在所述移动性管理网元中更新 MTC GW与 MTC终端的关联列表；
所述移动性管理网元释放所述 MTC终端相关的承载资源。
进一步地， 当所述 MTC终端通过 MTC GW切换了无线接入点后， 该 方法还包括：所述 MTC GW为所述 MTC终端签约的 APN建立对应的 PDN 连接。
进一步地， 当 MTC GW从源移动性管理网元的管理区域移动到新移动 性管理网元的管理区域， 进行位置更新时， 所述移动性管理信令交互和所 述移动性管理， 具体包括：
新移动性管理网元向源移动性管理网元获取 MTC GW的上下文信息、 MTC GW与 MTC终端的关联列表、 以及与 MTC GW关联的 MTC终端的 上下文信息； 并请求 3GPP网络更新 MTC GW建立的所有承载； 所述新移动性管理网元将 MTC GW的标识及地址与新移动性管理网元 的地址发送给与 MTC GW关联的 MTC终端归属的 HSS进行更新并保存； 新移动性管理网元识别 MTC GW具有终端接入代理能力。
进一步地， 当所述 MTC终端请求通过 MTC GW从 3GPP网络离线时、 或者所述 MTC终端移动出 MTC GW管理的区域时， 所述移动性管理信令 交互和所述移动性管理， 具体包括：
MTC GW将 MTC终端的离线请求发送给 3GPP网络的移动性管理网 元； 所述移动性管理网元删除 MTC终端的上下文信息、 以及 MTC终端与 MTC GW的关联， 并通过 MTC GW向 MTC终端发送离线通知。
进一步地， 所述 MTC终端离线后， 该方法还包括：
确定所述 MTC终端签约的 APN没有关联其它 MTC终端时， MTC GW 向 3GPP网络发起 PDN连接去激活 , 删除所述 APN对应的 PDN连接。
进一步地， 所述 MTC GW中保存了与自身关联的所述 MTC终端的信 本发明还提供了一种对 MTC 终端进行移动性管理的系统， 该系统包 括： MTC终端、 终端接入代理网关（ MTC GW )和 3GPP网络； 其中： 所述 MTC GW用于代替所述 MTC终端与 3GPP网络进行移动性管理 信令交互；
3GPP网络用于通过所述 MTC GW对所述 MTC终端进行移动性管理。 进一步地，所述 MTC终端包括具有 3GPP通信能力的 MTC UE和不具 有 3GPP通信能力但具有 3GPP网络用户身份的非 MTC UE。
进一步地， 3GPP网络包括移动性管理网元， 用于当 MTC GW首次接 入到 3GPP网络时， 获取到所述 MTC GW的签约用户数据后， 根据所述签 约用户数据中签约的终端接入代理能力识别所述 MTC GW具有终端接入代 理能力； 所述移动性管理网元， 还用于当 MTC终端通过 MTC GW接入 3GPP 网络时，将 MTC终端的上下文信息与 MTC GW进行关联，并维护 MTC GW 与 MTC终端的关联列表。
进一步地， 所述 MTC GW还用于保存与自身关联所述 MTC终端的信 息， 至少包括 MTC终端的标识、 MTC终端的附着状态、 和 MTC终端签约 的 APN。
本发明中， MTC终端通过末梢网络的终端接入代理网关（ MTC GW ) 接入到 3GPP中，释放 MTC终端在 3PGG网络占用的资源，并使用 MTC GW 在 3GPP网络的承载资源与 MTC Server进行数据通信。 3GPP网络可通过 MTC GW对 MTC终端实现接入认证、 附着、 位置更新、 无线接入点切换、 去附着等一系列移动性管理，节约了各 MTC终端在 3GPP网络占用的资源， 并且 3GPP网络能够通过所述 MTC GW进行其它流程优化， 如终端监控与 离线触发等， 具有显著的优化效果。 附图说明
图 1为现有技术中 GPRS网络系统架构示意图；
图 2为现有技术中 EPS网络系统架构示意图；
图 3为现有技术中 MTC UE附着到 3GPP PS网络并建立承载的流程图； 图 4为现有技术中 MTC UE在 3GPP PS网络进行位置更新的流程图； 图 5为现有技术中 MTC UE从 3GPP PS网络进行去附着的流程图； 图 6为一种 M2M应用的场景图；
图 7为本发明中对终端进行移动性管理的方法流程图；
图 8为本发明中 MTC GW首次接入到 3GPP网络的流程图；
图 9为本发明中在 3GPP网络中离线时，MTC UE通过 MTC GW接入、 实现附着到 3GPP网络的流程图；
图 10为本发明中在 3GPP网络中在线时， MTC UE通过 MTC GW接 入、 实现附着到 3GPP网络的流程图；
图 11为本发明中 MTC GW在 3GPP网络中进行位置更新的流程图； 图 12为本发明中 MTC UE通过 MTC GW实现从 3GPP网络去附着的 流程图。 具体实施方式
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。 本发明中，根据 M2M应用需求，针对末梢网络中的 MTC GW对 MTC 终端进行代理接入到 3GPP网络的场景， 解决了 3GPP网络如何通过 MTC GW对其接入的 MTC终端进行移动性管理的问题， 如附着、 接入点切换、 位置更新、 去附着等相关移动性管理与接入控制， 满足了 MTC终端通过末 梢网络的 MTC GW接入 3GPP网络时进行移动性管理的需求。
如图 7所示， 本发明对终端进行移动性管理的方法包括：
步驟 1 , MTC GW代替 MTC终端与 3GPP网络进行移动性管理信令交 互。
步驟 2, 3GPP网络通过 MTC GW对 MTC终端进行移动性管理。
其中， MTC终端包括具有 3GPP通信能力的 MTC UE和不具有 3GPP 通信能力的非 MTC UE。
具体的， MTC GW代替 MTC终端与 3GPP网络进行移动性管理信令交 互之前， 该方法还包括： MTC GW首次接入到 3GPP网络时， 移动性管理 单元（指为 MTC GW服务的移动性管理单元）获取到 MTC GW的签约用 户数据后， 根据签约用户数据中签约的终端接入代理能力识别该 MTC GW 具有终端接入代理能力。 具体通过后续实施例一来说明。
当 MTC终端请求通过 MTC GW接入到 3GPP网络时， 所述移动性管 理信令交互和所述移动性管理， 具体包括： MTC GW将 MTC终端的接入 请求发送给 3GPP网络的移动性管理网元（ MME或 SGSN ); 移动性管理网 元对 MTC终端进行鉴权认证， 并由 MTC GW透传 MTC UE与移动性管理 网元的鉴权数据与向量； 所述移动性管理网元将 MTC GW的标识及地址、 所述移动性管理网元的地址发送给与 MTC GW 关联的 MTC终端归属的 HSS进行保存； 鉴权认证通过、 且允许 MTC终端接入 3GPP网络时， 移动 性管理网元保存 MTC终端的上下文信息并与 MTC GW进行关联， 并在移 动性管理网元中更新 MTC GW与 MTC终端的关联列表。 当 MTC终端通 过 MTC GW接入到 3GPP网络后：确定未对 MTC终端签约的 APN建立 PDN 连接时， MTC GW为该 APN建立对应的 PDN连接。 具体通过后续实施例 二来说明。
当 MTC终端通过 MTC GW向 3GPP网络请求切换无线接入点时， 所 述移动性管理信令交互和所述移动性管理， 具体包括： MTC GW将 MTC 终端的更新无线接入点请求发送给 3GPP网络的移动性管理网元；移动性管 理网元将 MTC终端的上下文信息与 MTC GW进行关联， 并在移动性管理 网元中更新 MTC GW与 MTC终端的关联列表；移动性管理网元释放 MTC 终端相关的承载资源。 当 MTC终端通过 MTC GW切换了无线接入点后， 该方法还包括：确定未对 MTC终端签约的 APN建立 PDN连接时， MTC GW 为该 APN建立对应的 PDN连接。 具体通过后续实施例三来说明。
当 MTC GW从源移动性管理网元的管理区域移动到新移动性管理网元 的管理区域， 进行位置更新时， 所述移动性管理信令交互和所述移动性管 理， 具体包括： 新移动性管理网元向源移动性管理网元获取 MTC GW的上 下文信息、 MTC GW与 MTC终端的关联列表、 以及与 MTC GW关联的 MTC终端的上下文信息；并请求 3GPP网络更新 MTC GW建立的所有承载； 新移动性管理网元将 MTC GW的标识及地址与新移动性管理网元的地址发 送给与 MTC GW关联的 MTC终端归属的 HSS进行更新并保存； 新移动性 管理网元识别 MTC GW具有终端接入代理能力。具体通过后续实施例四来 说明。
当 MTC终端请求通过 MTC GW从 3GPP网络离线时、或者 MTC终端 移动出 MTC GW管理的区域时， 所述移动性管理信令交互和所述移动性管 理，具体包括： MTC GW将 MTC终端的离线请求发送给 3GPP网络的移动 性管理网元； 移动性管理网元删除 MTC终端的上下文信息、 以及 MTC终 端与 MTC GW的关联，并通过 MTC GW向 MTC终端发送离线通知。 MTC 终端离线后： 确定 MTC终端签约的 APN下没有关联有其它 MTC终端时， MTC GW向 3GPP网络发起 PDN连接去激活 ,删除该 APN对应的 PDN连 接。 具体通过后续实施例五来说明。
另外， MTC GW中还保存了与自身关联的 MTC终端的信息， 至少包 括 MTC终端的标识、 MTC终端的附着状态、 和 MTC终端签约的 APN。
MTC UE为例， 对非 MTC UE与对 MTC UE的移动性管理过程是相同的。
实施例一
如图 8所示， MTC GW既为末梢网络的终端代理网关， 同时也是 3GPP 网络的终端。 当 MTC GW在初始接入到 3GPP网络时， 3GPP网络需要认 证 MTC GW具有末梢网络的终端接入代理能力， 并根据 MTC GW签约的 多个 APN, 建立多条 PDN连接通道， 这样 MTC GW可以采用不同的 PDN 连接通道， 使归属不同 MTC Server的传感器节点 （图中为 MTC UE )与 MTC Server进行连接。 具体包括：
步驟 401 , MTC GW为了接入到 3GPP网络， 包括 GPRS网络与 EPS 网络， 需要向 RNS无线接入网络（eNodeB或 RNC )发起附着请求， 其中 携带了 MTC GW的标识（即 IMSI )、 MTC GW的网络接入能力、 请求分配 IP的指示和终端接入代理能力等信息。
RNS为 MTC GW选择一个为之服务的 MME/SGSN ( MME或 SGSN ), 并将附着请求转发到该 MME/SGSN, 同时将 MTC GW的标识（IMSI )、 和 MTC GW的网络接入能力、 和请求分配 IP的指示、 和终端接入代理能力等 信息也携带给 MME/SGSN。
步驟 402, MME/SGSN向 MTC GW归属网的 HSS发送鉴权数据请求 (包含 MTC GW的 IMSI ), HSS首先判断该 IMSI对应的签约用户数据， 如果查找不到任何签约或者 IMSI已被列入黑名单， 则 HSS向 MME/SGSN 返回鉴权数据响应、 并携带错误原因； 如果找到 IMSI对应的签约数据， 则 HSS向 MME/SGSN返回鉴权数据响应 （包含鉴权向量）；
MME/SGSN执行鉴权流程以验证 MTC GW的 IMSI的合法性，并执行 安全模式流程以启用安全连接。
步驟 403 , MME/SGSN向 MTC GW归属网的 HSS发送位置更新请求， 其中携带 MME/SGSN的标识、 和 MTC GW的标识（ IMSI ), 向 HSS告知 MTC GW当前所接入的区域； HSS根据 MTC GW的标识（ IMSI )查找出 签约用户数据， 发送给 MME/SGSN。 签约用户数据中主要包含： APN、 带 宽等信息；
对于 MTC GW, 因其是末梢网络的终端接入代理设备， 签约有末梢网 络节点代理能力 （即指终端接入代理能力）， 可选的， 也可签约末梢网络节 点（即传感器节点）与不同 MTC Server连接时所需的多个 APN及 PGW的 地址；
MME/SGSN接收到 MTC GW的签约用户数据，检查 MTC GW被允许 接入到网络时， 向 HSS返回接受响应； 若 MME/SGSN发现 MTC GW有漫 游限制或接入限制等问题， MME/SGSN将禁止 MTC GW附着，并通知 HSS。
步驟 404, 对于 MTC GW, MME/SGSN需要根据其签约用户数据， 检 查 MTC GW是否具有终端接入代理能力， 若有， 则识别 MTC GW具有终 端接入代理能力， 后续其它 MTC终端可以通过该 MTC GW接入到 3GPP 网络。
步驟 405 , MME/SGSN 根据默认 APN 为 MTC GW 选择一个 PGW/GGSN, 并向其发送建立承载请求。在该请求中携带 MTC GW的标识 ( IMSI ), MME/SGSN的标识、 为 MTC GW分配 IP地址的指示、 缺省带 宽信息、 PGW/GGSN地址等。
如有必要， PGW/GGSN会向 PCRF请求下发为该 MTC GW所配置的 QoS策略和计费规则、 决策信息；
PGW/GGSN根据 PCRF返回的 QoS策略和计费信息或静态配置的 PCC 策略， 建立 PS承载， 并向 MME/SGSN返回承载建立响应。
步驟 406, MME/SGSN保存承载上下文（ Bearer context ), 然后向 RNS 发送初始上下文设置请求或附着接受响应，表明 MTC GW的附着到网络的 请求已被接受， 其中携带 APN、 PS承载 ID ( PS Bearer ID ), PGW/GGSN 地址与 TEID。
步驟 407, RNS向 MTC GW发送 RRC连接重配置请求， 并开放相应 的端口。 RRC连接重配置请求中携带了： PS Bearer ID、 PGW/GGSN地址、 APN、 分配给 MTC GW的 IP地址、 带宽信息等， MTC GW在本端保存如 APN、 自身的 IP地址、 带宽、 PS Bearer ID等重要信息；
MTC GW向 RNS发送 RRC连接重配置响应。
步驟 408, RNS向 MME/SGSN发送初始上下文响应， 其中包含 RNS 的 TEID及地址信息， 用于发送下行数据给 MTC GW。
步驟 409, MTC GW发送附着完成消息， 携带 PS Bearer ID, 通知 MME/SGSN附着过程完成。
步驟 410, MME向 PGW/GGSN发送更新承载请求， 向 PGW/GGSN告 知为 MTC GW服务的 RNS的 TEID及地址， 打通上行通道。 PGW/GGSN 向 MME/SGSN发送更新 7|载响应， 载更新成功。 步驟 411 , MTC GW作为末梢网络终端代理网关， 其上配置了多个 APN,用于为末梢网络中的传感器节点连接不同的 MTC Server。因此， MTC GW需要建立多条 PDN连接。
MTC GW向 MME/SGSN发送 PDN连接请求， 携带 APN、 PDN类型、 PCO参数等信息， PDN类型指示是 IPv4或 IPv6地址请求， PCO是终端与 PGW/GGSN传输透明数据的信息集。
步驟 412, MME/SGSN检查 APN是否合法， 若合法， 则分配一个 PS Bearer ID, 然后向 PGW/GGSN发送建立承载请求， 携带 MTC GW的标识 ( IMSI )、 APN、 APN-AMBR最大比特率、 PCO参数等信息。
PGW/GGSN创建一个新的数据入口，建立与 APN对应的一个 PS承载， 并向 MME/SGSN返回承载建立响应，携带对应的 PS Bearer ID、 PGW/GGSN 地址及分配的控制面及用户面的 TEID , PCO参数等信息。
步驟 413, MME/SGSN保存承载上下文， 然后向 RNS发送承载设置消 息， 该消息中包含 MME/SGSN发送给 MTC GW的 PDN连接接受消息，在 PDN连接接受消息中携带了 APN、 PCO参数、 PS Bearer ID等参数， 表明 MTC GW建立多条 PDN连接的请求已被接受。同时在承载设置消息中携带 Bearer QoS参数、 PGW/GGSN用户面入口的 TEID、 PDN连接接受指示等 信息。
步驟 414, RNS向 MTC GW发送 RRC连接重配置请求， 并开放相应 的端口， RRC连接重配置请求中携带了 PDN连接接受消息给 MTC GW;
MTC GW向 RNS发送 RRC连接重配置响应， 建立相应的无线承载。 步驟 415, RNS向 MME/SGSN发送承载设置响应， 其中包含 RNS的 TEID及地址信息， 用于发送下行数据给 MTC GW。
步驟 416, MTC GW发送 PDN连接完成消息， 携带 PS Bearer ID , 通 知 MME/SGSN PDN连接建立过程完成。 步驟 417, MME向 PGW/GGSN发送更新 载请求， 通知为 MTC GW 服务的 RNS的 TEID及地址， 打通上行通道。 PGW/GGSN向 MME/SGSN 发送更新承载响应， 承载更新成功。
实施例二
如图 9所示， MTC GW作为末梢网络的终端代理网关已接入到 3GPP 网络。 当 MTC UE在 3GPP网络处于离线状态、 移动到 MTC GW的管理区 域， 并与 MTC GW在末梢网络建立本地连接， MTC UE获知 MTC GW具 有终端接入代理能力。 当 MTC UE需要与 MTC Server通信时， MTC UE通 过 MTC GW接入到 3GPP网络， 3GPP网络负责对 MTC UE进行鉴权认证。 MME/SGSN负责 MTC GW的上下文信息与 MTC UE的上下文信息的关联， 并维护 MTC GW与 MTC UE对应的关系列表。 MTC GW根据 MTC UE签 约的 APN决定创建与该 APN对应的 PDN连接。 具体包括：
步驟 501 , 在 3GPP网络中离线的 MTC UE移动到 MTC GW管理的区 域， 或该离线的 MTC UE原来就部署在 MTC GW的区域， 此时 MTC UE 维持的 3GPP网络接入状态为离线。 MTC UE与 MTC GW在末梢网络建立 本地连接， 如采用 ZigBee、 蓝牙、 WLAN等无线连接技术， 并在本地网络 接受 MTC GW的管理与代理， MTC GW将其 3GPP终端接入代理能力通知 给 MTC UE。
当 MTC UE需要与 MTC Server建立数据通信时， MTC UE需要通过本 地网络信令向 MTC GW发起接入请求， 请求通过 MTC GW接入到 3GPP 网络。
步驟 502, MTC GW向 RNS无线接入网络发起 NAS请求， 在其中携 带 MTC UE的接入请求 (包含 MTC UE请求接入指示、 MTC UE的标识 ( IMSI )、 MTC UE的网络接入能力等信息）；
RNS 通过 NAS 请求将该接入请求转发到 MTC GW 附着的 MME/SGSN, 同时将 MTC UE请求接入指示、 MTC UE的标识（ IMSI )、 MTC UE的网络接入能力等信息也携带给该 MME/SGSN。
步驟 503 , MME/SGSN从 NAS请求中得知是 MTC UE通过 MTC GW 请求接入到网络， 首先对 MTC UE进行鉴权认证。
MME/SGSN向该 MTC UE归属的 HSS发送鉴权数据请求（含 MTC UE 的 IMSI ), HSS首先判断 IMSI对应的签约用户数据， 如果查找不到任何签 约或者 IMSI已被列入黑名单， 则 HSS向 MME/SGSN返回鉴权数据响应、 并携带错误原因； 如果找到 IMSI 对应的签约用户数据， 则 HSS 向 MME/SGSN返回鉴权数据响应消息（含鉴权向量）；
MME/SGSN向 MTC UE执行鉴权流程以验证终端 IMSI的合法性， 并 执行安全模式流程以启用安全连接。
MTC GW透传 MTC UE与 MME/SGSN的鉴权数据与向量，在 MTC UE 通过 MTC GW在 3GPP网络进行鉴权认证过程中， MTC GW仅完成 3GPP 网络的信令与本地网络的信令协议的转换。
MTC GW与 MTC UE的传输安全性由本地末梢网络提供， MTC GW与 MME/SGSN的传输安全性由 3GPP网络负责。
步驟 504, MME/SGSN向 MTC UE归属的 HSS发送位置更新请求， 消 息中携带 MME/SGSN的地址、 MTC GW的标识与地址、 MTC UE的标识 等信息以告知 MTC UE当前所接入的区域， HSS保存 MME/SGSN的地址、 MTC GW的标识与地址等信息， 并根据 MTC UE的标识查找出 MTC UE 的签约用户数据， 发送给 MME/SGSN。 签约用户数据中主要包含 APN、 带 宽等信息；
MME/SGSN接收到 MTC UE的签约用户数据， 检查 MTC UE被允许 接入到网络， 向 HSS返回接受用户响应； 若 MME/SGSN发现 MTC UE有 漫游限制或接入限制等问题， MME/SGSN将禁止该 MTC UE附着， 并通知 HSS。
步驟 505, MME/SGSN保存 MTC UE的上下文信息， 并与 MTC GW 进行关联， 例如， 在 MTC UE的上下文信息中增加 "接入方式： MTC GW 代理接入"及 MTC GW的标识。在 MME/SGSN中维护 MTC GW与 MTC UE 的关联列表， 例如， 关联列表中保存 MTC GW的 IMSI与多个关联的 MTC UE的 IMSI的对应关系， 关联列表可放在 MTC GW的上下文信息中， 或单 独维护。
步驟 506, MME/SGSN向 MTC GW返回 NAS响应， 携带 MTC UE附 着接受信息给 MTC GW, 其中包含接受 MTC UE接入指示、 MTC UE的部 分签约用户信息， 如 APN等。
步驟 507, MTC GW需要通过本地网络信令向 MTC UE发起 3GPP网 络接入响应 , 通知 MTC UE已通过 MTC GW接入到 3GPP网络。
步驟 508, MTC UE收到 MTC GW的 3GPP网络接入响应后， 将 3GPP 网络接入状态更改为通过 MTC GW附着状态。
步驟 509, MTC GW保存 MTC UE的 APN、 终端标识（ IMSI )、 附着 状态等相关信息，并检查是否已为 MTC UE签约的 APN建立了 PDN连接， 如果不是， MTC GW需要为该 APN建立 PDN连接。 如果是， 因 MTC GW 已为该 APN建立了 PDN连接， 该 MTC UE的数据传输可以直接在该 APN 对应的 PDN链路通道上就可以了， 不需要再建立新的 PDN连接。
步驟 510, 若 MTC GW未对 MTC UE的签约 APN建立 PDN连接， MTC GW采用该 MTC UE的 APN向 MME/SGSN发送 PDN连接请求， 携 带 APN、 PDN类型、 PCO参数等信息， PDN类型指示是 IPv4或 IPv6地址 请求， PCO是终端与 PDN GW/GGSN传输透明数据的信息集。
步驟 511 , MME/SGSN检查 APN是否合法， 若不在 MTC GW的签约 数据中，就到 MTC GW关联的 MTC UE上下文信息中查找 APN签约信息， 若合法， 则分配一个 PS Bearer ID, 然后向 PGW/GGSN发送建立承载请求， 携带 MTC GW的标识（IMSI )、 APN、 APN-AMBR最大比特率、 PCO参 数等信息；
PGW/GGSN创建一个新的数据入口，建立与 APN对应的一个 PS承载， 并向 MME/SGSN返回承载建立响应，携带对应的 PS Bearer ID、 PGW/GGSN 地址及分配的控制面及用户面的 TEID , PCO参数等信息。
步驟 512, MME/SGSN保存承载上下文， 然后向 RNS发送承载设置消 息， 该消息中包含 MME/SGSN发送给 MTC GW的 PDN连接接受消息，在 PDN连接接受消息中携带了 APN、 PCO参数、 PS Bearer ID等参数， 表明 MTC GW建立多条 PDN连接的请求已被接受。同时在承载设置消息中携带 Bearer QoS参数、 PGW/GGSN用户面入口的 TEID、 PDN连接接受指示等 信息。
步驟 513 , RNS向 MTC GW发送 RRC连接重配置请求， 并开放相应 的端口。 RRC连接重配置请求中携带了 PDN连接接受消息给 MTC GW;
MTC GW向 RNS发送 RRC连接重配置响应， 建立相应的无线承载。 步驟 514, RNS向 MME/SGSN发送承载设置响应消息，其中包含 RNS 的 TEID及地址信息， 用于发送下行数据给 MTC GW。
步驟 515, MTC GW发送 PDN连接完成消息， 携带 PS Bearer ID, 通 知 MME/SGSN PDN连接建立过程完成。
步驟 516, MME向 PGW/GGSN发送更新承载请求， 通知为 MTC GW 服务的 RNS的 TEID及地址， 打通上行通道。 PGW/GGSN向 MME/SGSN 发送更新承载响应， 承载更新成功。
实施例三
如图 10所示， MTC GW作为末梢网络的终端代理网关已接入到 3GPP 网络。 当 MTC UE在 3GPP网络处于在线状态、 移动到 MTC GW的管理区 域， 并与 MTC GW在末梢网络建立本地连接。 MTC UE根据策略， 如优先 通过本地网络代理接入，需要将无线接入点从 3GPP网络切换到 MTC GW。 该 MTC UE连接到本地网络的 MTC GW, 并获知 MTC GW具有终端接入 代理能力， 就通过该 MTC GW向 3GPP网络请求切换无线接入点， 3GPP 网络将该 MTC UE与 MTC GW进行关联，并释放在 3GPP网络的无线 载 资源及核心网承载资源。 具体包括：
步驟 601 , 在 3GPP网络中在线的 MTC UE移动到 MTC GW管理的区 域，此时 MTC UE维持的 3GPP网络接入状态为在线。 MTC UE与 MTC GW 在末梢网络建立本地连接， 如采用 ZigBee、蓝牙、 WLAN等无线连接技术， 并在本地网络接受 MTC GW的管理与代理， MTC GW将其终端接入代理 能力通知给 MTC UE。
MTC UE根据策略， 如优先通过本地网络代理接入， 需要将无线接入 点从 3GPP网络切换到 MTC GW, MTC UE需要通过本地网络信令向 MTC GW发起更新无线接入点请求， 请求释放与 3GPP 网络的连接， 改为通过 MTC GW接入到 3GPP网络。
步驟 602, MTC GW向 RNS无线接入网络发起 NAS请求， 在其中包 含 MTC UE发起的更新无线接入点请求， 请求消息中携带 MTC UE的标识 ( IMSI )等信息；
RNS将通过 NAS请求将 MTC UE的更新无线接入点请求转发到 MTC GW附着的 MME/SGSN, 同时将 MTC UE的标识等重要信息也携带给该 MME/SGSN。
步驟 603, MME/SGSN向 MTC UE归属的 HSS发送位置更新请求，将 MTC GW的标识及地址、 SGSN/MME地址、 MTC UE的标识等信息通知给 MTC UE 归属的 HSS, HSS保存 MTC GW的标识与地址信息。
步驟 604, MME/SGSN将该 MTC UE的上下文信息与 MTC GW进行 关联， 例如， 在 MTC UE的上下文信息中增加 "接入方式： MTC GW代理 接入" 及 MTC GW的标识。 在 MME/SGSN中更新 MTC GW与 MTC UE 的关联列表， 该 MTC UE改为由 MTC GW进行代理接入到 3GPP网络。
步驟 605, MME/SGSN释放 MTCUE相关的 载资源， 具体的： 向 PGW/GGSN发起删除承载请求， 请求删除为该 MTC UE建立的所有承载。 具体的： SGW、 以及 PGW/GGSN删除与该 MTC UE对应的承载上下文， 并释放分配的承载资源。 然后向 MME/SGSN返回删除承载响应。
步驟 606, MME/SGSN向 MTC GW返回 NAS信令响应，携带 MTC UE 更新无线接入点接受信息给 MTC GW,其中包含更新无线接入点接受指示、 MTC UE的部分签约信息， 如 APN等信息。
步驟 607, MTC GW保存 MTC UE的相关信息， 并通过本地网络信令 向 MTC UE返回更新无线接入点响应 , 通知 MTC UE已更新无线接入点 , MTC UE可以通过 MTC GW接入到 3GPP网络。
步驟 608, MTC UE收到 MTC GW的更新无线接入点响应后， 3GPP 网络主动释放无线资源与无线连接， 具体的： MME/SGSN向 RNS发送连 接释放命令， 通知 RNS释放该 MTC UE的无线连接， RNS释放分配给该 MTC UE的无线资源。 RNS向 MTC UE发送 RRC连接释放消息， 释放分 配给该 MTC UE的空口资源。
或者， MTC UE收到 MTC GW的更新无线接入点响应后， 通知 3GPP 网络释放无线资源与无线连接， 具体的： MTC UE向 RNS请求释放无线连 接， RNS释放无线连接和无线资源， 并通知 MME/SGSN。
MTC UE收到 MTC GW的更新无线接入点响应后，在释放无线连接无 线资源的同时， 将 3GPP网络接入状态更改为通过 MTC GW接入。
步驟 609, 检查 MTC GW是否已为 MTC UE签约的 APN建立了 PDN 连接， 如果不是， MTC GW需要为该 APN建立 PDN连接。 如果是， 因 MTC GW已为该 APN建立了 PDN连接， 该 MTC UE的数据传输可以直接 在该 APN对应的 PDN链路通道上就可以了，不需要再建立新的 PDN连接。
对 MTC UE签约的 APN建立 PDN连接、 即步驟 610~616, 其实现与 步驟 510~516相同， 此处不再赘述。
实施例四
如图 11所示， MTC GW作为末梢网络的终端代理网关已接入到 3GPP 网络。 当 MTC GW发生了移动， 移动到新的 MME/SGSN区域。 MTC GW 需要发起 TAU请求，源 MME/SGSN需要将 MTC GW的上下文信息和与之 关联的 MTC UE的上下文信息、 关联列表都需要发给新 MME/SGSN, 并将 新 MME/SGSN地址、 MTC GW的标识及地址发给 MTC GW归属的 HSS 更新。 新 MME/SGSN识别该 MTC GW是末梢网络的终端接入代理网关， 维护该 MTC GW与 MTC UE的代理关联， 并维护关联列表。
步驟 701 , 当 MTC GW在 3GPP网络发生移动时， 由源 MME/SGSN 管理的区域移动到新 MME/SGSN管理的区域。 MTC GW需要进行位置更 新。 MTC GW向新 MME/SGSN发起 TAU位置更新请求， 携带 MTC GW 的标识、 MTC GW的网络能力、 PS Bearer状态等信息。
步驟 702 , 新 MME/SGSN 得到源 MME/SGSN 的地址， 并向源 MME/SGSN发送获取 MTC GW的上下文请求，在其中包含 MTC GW的标 识、 新 MME/SGSN地址等信息， 请求源 MME/SGSN将 MTC GW的所有 上下文信息都发给新 MME/SGSN;
源 MME/SGSN收到获取 MTC GW的上下文请求后，将 MTC GW的上 下文信息、 MTC GW与 MTC UE的关联列表、 MTC UE的上下文信息都发 给新 MME/SGSN。
步驟 703 , 新 MME/SGSN向 PGW/GGSN发起更新承载请求， 请求更 新该 MTC GW建立的所有承载， PGW/GGSN需要更新该 MTC GW对应的 承载上下文， 如更新承载上下文中的 MME/SGSN 的 TEID。 然后向新 MME/SGSN返回更新承载响应。
步驟 704,新 MME/SGSN向 MTC GW归属的 HSS发起位置更新请求， 携带 MTC GW的位置信息与新 MME/SGSN的地址等信息， HSS进行更新 并保存。
同时， 新 MME/SGSN向 MTC GW代理的所有 MTC UE归属的 HSS 发起位置更新请求，携带 MTC GW的地址与新 MME/SGSN的地址等信息， HSS进行更新并保存。
步驟 705 , MTC GW归属的 HSS向源 MME/SGSN发起删除用户数据 请求， 源 MME/SGSN删除该 MTC GW的所有信息及关联的 MTC UE的所 有信息。
步驟 706, MTC GW归属的 HSS向新 MME/SGSN返回位置更新响应， 将 MTC GW的签约用户数据发给新 MME/SGSN, 签约用户数据包含终端 接入代理能力指示、 APN等信息。
步驟 707,新 MME/SGSN根据 MTC GW的签约用户信息识别 MTC GW 是末梢网络的终端接入代理网关，后续需要维护 MTC GW与 MTC UE的关 联列表。
步驟 708 , 新 MME/SGSN发送 TAU接受消息给 MTC GW , MTC GW 成功在目标网络上进行了位置更新。
实施例五
如图 12所示， MTC GW作为末梢网络的终端接入代理已接入到 3GPP 网络， MTC UE通过 MTC GW已接入到 3GPP网络。 若 MTC UE移动出 MTC GW管理的区域， 或 MTC UE根据策略需要从 3GPP网络离线， MTC GW就代替 MTC UE向 3GPP网络发起 MTC UE的离线请求， MME/SGSN 删除该 MTC UE的上下文， 及与 MTC GW的关联关系， 并通知 HSS该终 端离线。 具体包括：
步驟 801 , 在 MTC UE已通过 MTC GW接入到 3GPP网络的场景中， 根据终端策略或配置，如 MTC UE已发送完数据， MTC UE需要断开与 3GPP 网络的连接， MTC UE需要通过本地网络信令向 MTC GW发起离线请求， 请求释放该 MTC UE与 3GPP网络的连接；
或者， 步驟 802, MTC UE已移动出 MTC GW管理的区域， 此时 MTC GW需要代替该 MTC UE发起离线请求， 请求释放该 MTC UE与 3GPP网 络的连接。
步驟 803 , MTC GW向 MME/SGSN发送 NAS请求， 携带 MTC UE的 离线请求， 离线请求中包含 MTC UE的标识等信息。
步驟 804, MME/SGSN收到离线请求后，通知该 MTC UE归属的 HSS, MTC UE已申请离线。
步驟 805 , MME/SGSN删除该 MTC UE的上下文信息，及与 MTC GW 的关联， MTC UE不再通过该 MTC GW进行代理。
步驟 806, MME/SGSN向 MTC GW返回 NAS响应， 携带 MTC UE已 离线的通知消息（携带离线接受或离线通知指示）。
步驟 807, MTC GW通过本地网络信令向 MTC UE发送离线通知， 通 知 MTC UE已在 3GPP网络离线。
步驟 808 , MTC UE更改 3GPP网络状态为离线。
步驟 809 , MTC GW检查申请离线的 MTC UE签约的 APN下是否关联 有其它 MTC UE, 如果还有其它 MTC UE使用该 APN对应的 PDN连接链 路， MTC GW就不发起 PDN连接去激活。如果该 APN下没有其它 MTC UE 连接到 3GPP网络， 则 MTC GW需要发起 PDN连接去激活， 删除该 APN 对应的 PDN连接。
步驟 810, MTC GW根据该 MTC UE签约的 APN向 MME/SGSN发送 PDN连接去激活请求， 携带 LBI (承载标识）、 APN等信息， LBI用于标识 该 PDN连接的默认承载， APN用于识别该 PDN连接。
步驟 811 , MME/SGSN 决定释放该 PDN 连接， MME/SGSN 向 PGW/GGSN发送 PDN 连接删除请求， 其中携带 LBI, 具体的： SGW、 PGW/GGSN根据 LBI删除该 PDN连接，释放分配的承载资源。 PGW/GGSN 向 MME/SGSN返回 PDN连接删除成功响应。
步驟 812, MME/SGSN向 RNS发送去激活承载请求， 请求去激活该 PDN连接下的所有承载， 去激活承载请求中携带 LBI或 APN进行标识， RNS删除该 PDN连接下的所有承载资源。
步驟 813, RNS向 MTC GW发送 RRC连接重配置请求， 其中携带去 激活承载上下文请求。 MTC GW删除该 PDN连接下的所有承载的上下文信 息， 然后发送 RRC连接重配置响应给 RNS。
步驟 814, RNS向 MME/SGSN返回去激活承载相应， 确认去激活承载 完成。
步驟 815 , 去激活承载后， MTC GW通过 NAS信令向 RNS发送去激 活承载接受消息， RNS将该去激活承载接受消息发给 MME/SGSN。
为了实现上述方法，本发明还提供了一种对 MTC终端进行移动性管理 的系统， 包括： MTC终端、 MTC GW和 3GPP网络； 其中：
MTC GW用于代替 MTC终端与 3GPP网络进行移动性管理信令交互； 3GPP网络用于通过 MTC GW对 MTC终端进行移动性管理。
3GPP网络中包括移动性管理网元，用于当 MTC GW首次接入到 3GPP 网络时， 获取到 MTC GW的签约用户数据后， 根据签约用户数据中签约的 终端接入代理能力识别 MTC GW具有终端接入代理能力；
移动性管理网元， 还用于当 MTC终端通过 MTC GW接入 3GPP网络 时，将 MTC终端的上下文信息与 MTC GW进行关联， 并维护 MTC GW与 MTC终端的关联列表。
MTC GW还用于保存与自身关联的 MTC终端的信息， 至少包括 MTC 终端的标识、 MTC终端的附着状态、 和 MTC终端签约的 APN。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种对 MTC终端进行移动性管理的方法， 其特征在于， 该方法包 括：
终端接入代理网关（ MTC GW )代替机器类型通信（ MTC )终端与 3GPP 网络进行移动性管理信令交互； 3GPP网络通过 MTC GW对 MTC终端进行 移动性管理。
2、 根据权利要求 1所述对 MTC终端进行移动性管理的方法， 其特征 在于， 所述 MTC终端包括具有 3GPP通信能力的 MTC UE和不具有 3GPP 通信能力但具有 3GPP网络用户身份的非 MTC UE。
3、 根据权利要求 1所述对 MTC终端进行移动性管理的方法， 其特征 在于， MTC GW代替 MTC终端与 3GPP网络进行移动性管理信令交互之前， 该方法还包括：
所述 MTC GW首次接入到 3GPP网络时， 3GPP网络中的移动性管理 网元获取到所述 MTC GW的签约用户数据后，根据所述签约用户数据中签 约的终端接入代理能力识别所述 MTC GW具有终端接入代理能力。
4、 根据权利要求 3所述对 MTC终端进行移动性管理的方法， 其特征 在于， 当所述 MTC终端请求通过 MTC GW接入到 3GPP网络时， 所述移 动性管理信令交互和所述移动性管理， 具体包括：
MTC GW将 MTC终端的接入请求发送给 3GPP网络的移动性管理网 元； 所述移动性管理网元对 MTC终端进行鉴权认证， 并由所述 MTC GW 透传 MTC UE与移动性管理网元的鉴权数据与向量；
所述移动性管理网元将 MTC GW的标识及地址、所述移动性管理网元 的地址发送给与 MTC GW关联的 MTC终端归属的 HSS进行保存；
所述鉴权认证通过、 且允许 MTC终端接入 3GPP网络时， 所述移动性 管理网元保存 MTC终端的上下文信息并与 MTC GW进行关联， 并在所述 移动性管理网元中更新 MTC GW与 MTC终端的关联列表。
5、 根据权利要求 4所述对 MTC终端进行移动性管理的方法， 其特征 在于， 当所述 MTC终端通过 MTC GW接入到 3GPP网络后， 该方法还包 括： 所述 MTC GW为所述 MTC终端签约的缺省接入点名称（ APN )建立 对应的分组数据网络（ PDN )连接。
6、 根据权利要求 3所述对 MTC终端进行移动性管理的方法， 其特征 在于， 当所述 MTC终端通过 MTC GW向 3GPP网络请求切换无线接入点 时， 所述移动性管理信令交互和所述移动性管理， 具体包括：
MTC GW将 MTC终端的更新无线接入点请求发送给 3GPP网络的移动 性管理网元；
所述移动性管理网元将 MTC终端的上下文信息与 MTC GW进行关联， 并在所述移动性管理网元中更新 MTC GW与 MTC终端的关联列表；
所述移动性管理网元释放所述 MTC终端相关的承载资源。
7、 根据权利要求 6所述对 MTC终端进行移动性管理的方法， 其特征 在于， 当所述 MTC终端通过 MTC GW切换了无线接入点后， 该方法还包 括： 所述 MTC GW为所述 MTC终端签约的 APN建立对应的 PDN连接。
8、 根据权利要求 3所述对 MTC终端进行移动性管理的方法， 其特征 在于， 当 MTC GW从源移动性管理网元的管理区域移动到新移动性管理网 元的管理区域， 进行位置更新时， 所述移动性管理信令交互和所述移动性 管理， 具体包括：
新移动性管理网元向源移动性管理网元获取 MTC GW的上下文信息、 MTC GW与 MTC终端的关联列表、 以及与 MTC GW关联的 MTC终端的 上下文信息； 并请求 3GPP网络更新 MTC GW建立的所有承载；
所述新移动性管理网元将 MTC GW的标识及地址与新移动性管理网元 的地址发送给与 MTC GW关联的 MTC终端归属的 HSS进行更新并保存； 新移动性管理网元识别 MTC GW具有终端接入代理能力。
9、 根据权利要求 3所述对 MTC终端进行移动性管理的方法， 其特征 在于， 当所述 MTC终端请求通过 MTC GW从 3GPP网络离线时、 或者所 述 MTC终端移动出 MTC GW管理的区域时， 所述移动性管理信令交互和 所述移动性管理， 具体包括：
MTC GW将 MTC终端的离线请求发送给 3GPP网络的移动性管理网 元； 所述移动性管理网元删除 MTC终端的上下文信息、 以及 MTC终端与 MTC GW的关联， 并通过 MTC GW向 MTC终端发送离线通知。
10、 根据权利要求 9所述对 MTC终端进行移动性管理的方法， 其特征 在于， 所述 MTC终端离线后， 该方法还包括：
确定所述 MTC终端签约的 APN没有关联其它 MTC终端时， MTC GW 向 3GPP网络发起 PDN连接去激活 , 删除所述 APN对应的 PDN连接。
11、 根据权利要求 1至 10中任一所述对 MTC终端进行移动性管理的 方法， 其特征在于：
所述 MTC GW中保存了与自身关联的所述 MTC终端的信息。
12、 一种对 MTC终端进行移动性管理的系统， 其特征在于， 该系统包 括： MTC终端、 终端接入代理网关 （ MTC GW )和 3GPP网络； 其中： 所述 MTC GW用于代替所述 MTC终端与 3GPP网络进行移动性管理 信令交互；
3GPP网络用于通过所述 MTC GW对所述 MTC终端进行移动性管理。
13、 根据权利要求 12所述 MTC终端进行移动性管理的系统， 其特征 在于， 所述 MTC终端包括具有 3GPP通信能力的 MTC UE和不具有 3GPP 通信能力但具有 3GPP网络用户身份的非 MTC UE。
14、 根据权利要求 13所述 MTC终端进行移动性管理的系统， 其特征 在于， 3GPP网络包括移动性管理网元， 用于当 MTC GW首次接入到 3GPP 网络时， 获取到所述 MTC GW的签约用户数据后， 根据所述签约用户数据 中签约的终端接入代理能力识别所述 MTC GW具有终端接入代理能力； 所述移动性管理网元， 还用于当 MTC终端通过 MTC GW接入 3GPP 网络时，将 MTC终端的上下文信息与 MTC GW进行关联，并维护 MTC GW 与 MTC终端的关联列表。
15、根据权利要求 12至 14中任一所述 MTC终端进行移动性管理的系 统， 其特征在于， 所述 MTC GW还用于保存与自身关联所述 MTC终端的 信息， 至少包括 MTC终端的标识、 MTC终端的附着状态、 和 MTC终端签 约的 APN。
PCT/CN2012/070003 2011-01-14 2012-01-04 一种对mtc终端进行移动性管理的方法和系统 WO2012094957A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110008309.1A CN102595373B (zh) 2011-01-14 2011-01-14 一种对mtc终端进行移动性管理的方法和系统
CN201110008309.1 2011-01-14

Publications (1)

Publication Number Publication Date
WO2012094957A1 true WO2012094957A1 (zh) 2012-07-19

Family

ID=46483488

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/070003 WO2012094957A1 (zh) 2011-01-14 2012-01-04 一种对mtc终端进行移动性管理的方法和系统

Country Status (2)

Country Link
CN (1) CN102595373B (zh)
WO (1) WO2012094957A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104012035A (zh) * 2012-12-13 2014-08-27 华为技术有限公司 近距离服务的认证与授权的方法及设备

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104769991B (zh) * 2012-11-01 2018-04-10 Lg 电子株式会社 Mtc监控方法
CN103856928A (zh) * 2012-11-29 2014-06-11 中兴通讯股份有限公司 一种在m2m网络中移动性管理方法和系统
WO2014082311A1 (zh) * 2012-11-30 2014-06-05 华为技术有限公司 认证方法和装置
WO2014089778A1 (zh) * 2012-12-12 2014-06-19 华为技术有限公司 一种在线状态信息交互方法、机器人及系统
CN109327917B (zh) * 2013-03-22 2022-01-11 华为技术有限公司 建立连接的方法及设备
CN104717600B (zh) 2013-12-16 2019-12-10 中兴通讯股份有限公司 一种m2m终端/终端外设的可及性管理方法及设备
CN105430766A (zh) * 2014-09-23 2016-03-23 中兴通讯股份有限公司 一种mtc业务处理方法、系统及mtc设备
CN105704760B (zh) * 2014-11-26 2019-09-17 电信科学技术研究院 一种进行数据包传输的方法、设备和系统
CN105704753B (zh) * 2014-11-26 2018-09-07 电信科学技术研究院 一种进行数据传输的方法、系统和设备
US9693178B2 (en) * 2015-03-18 2017-06-27 Intel IP Corporation Procedures to provision and attach a cellular internet of things device to a cloud service provider
US9681473B2 (en) 2015-05-29 2017-06-13 Huawei Technologies Co., Ltd. MTC service management using NFV
CN107231672B (zh) * 2016-03-25 2020-10-30 中国移动通信有限公司研究院 核心网系统、接入控制方法及核心网网元
US10568012B2 (en) 2016-04-08 2020-02-18 Htc Corporation Device and method of handling mobility management
CN109150807B (zh) * 2017-06-19 2022-06-17 中兴通讯股份有限公司 凭证分发方法、用户终端、用户签约认证管理单元及介质
CN111343675A (zh) * 2018-12-19 2020-06-26 中兴通讯股份有限公司 一种终端同步移动性管理的方法、系统、设备以及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984162A (zh) * 2006-04-30 2007-06-20 华为技术有限公司 演进网络中终端在非3gpp接入系统注册方法及系统
US20070169107A1 (en) * 2003-06-25 2007-07-19 Sampo Huttunen Method of configuring parameters of machine-to-machine module and machine-to-machine module
CN101895858A (zh) * 2009-05-20 2010-11-24 华为技术有限公司 获取位置更新策略、拒绝位置更新和寻呼的方法和设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101511076A (zh) * 2008-07-29 2009-08-19 华为技术有限公司 一种用户接入网络的管理方法、装置和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070169107A1 (en) * 2003-06-25 2007-07-19 Sampo Huttunen Method of configuring parameters of machine-to-machine module and machine-to-machine module
CN1984162A (zh) * 2006-04-30 2007-06-20 华为技术有限公司 演进网络中终端在非3gpp接入系统注册方法及系统
CN101895858A (zh) * 2009-05-20 2010-11-24 华为技术有限公司 获取位置更新策略、拒绝位置更新和寻呼的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Service requirements for Machine-Type Communications (MTC); Stage 1", 3GPP TS 22.368 VLL.0.0, December 2010 (2010-12-01) *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104012035A (zh) * 2012-12-13 2014-08-27 华为技术有限公司 近距离服务的认证与授权的方法及设备

Also Published As

Publication number Publication date
CN102595373A (zh) 2012-07-18
CN102595373B (zh) 2017-11-28

Similar Documents

Publication Publication Date Title
CA3132854C (en) Wireless device paging by a wireless network
US20220256440A1 (en) Service gap control for a wireless device
US20230354447A1 (en) Establishing a Session or Cellular Internet of Things Packet Transmission
EP2566199B1 (en) Method and system for transmitting small data packets
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
US10455489B2 (en) Method for supporting PDN GW selection
US9374699B2 (en) Proximity-based service registration method and related apparatus
US8855045B2 (en) Method and system for controlling establishment of local IP access
CN114946268A (zh) 对网络切片的控制
US20120076047A1 (en) Maintaining current cell location information in a cellular access network
EP2884783A1 (en) Terminal control method, device, and system
WO2012051890A1 (zh) 终端接入限制的方法及系统
WO2011060673A1 (zh) 公用承载建立的方法、数据传输方法和核心网络侧设备
EP2259657B1 (en) Method for indicating the bearer management of a serving gateway
WO2011050678A1 (zh) 一种基于控制面与媒体面分离的网络架构实现的通信网络
CN101860910B (zh) 本地网络的承载建立方法、系统及装置
US8743752B2 (en) Method and apparatus for status transition
WO2011054320A1 (zh) 一种转移核心网ip业务的方法、设备及系统
WO2011026392A1 (zh) 一种路由策略的获取方法及系统
WO2014166089A1 (zh) 拥塞控制方法和装置
WO2010133107A1 (zh) 家用基站网关转发消息至家用基站的方法及系统
CN115735371A (zh) 网络切片特定认证和授权
WO2012100664A1 (zh) 一种激活终端的方法和系统
WO2015054847A1 (zh) 通信方法、本地网关、基站、mme和系统
WO2012129997A1 (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: 12734008

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

Country of ref document: EP

Kind code of ref document: A1