WO2013064067A1 - 一种网络拥塞控制的方法和系统 - Google Patents

一种网络拥塞控制的方法和系统 Download PDF

Info

Publication number
WO2013064067A1
WO2013064067A1 PCT/CN2012/083825 CN2012083825W WO2013064067A1 WO 2013064067 A1 WO2013064067 A1 WO 2013064067A1 CN 2012083825 W CN2012083825 W CN 2012083825W WO 2013064067 A1 WO2013064067 A1 WO 2013064067A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
congestion
iwf
mtc iwf
message
Prior art date
Application number
PCT/CN2012/083825
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 WO2013064067A1 publication Critical patent/WO2013064067A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for network congestion control. Background technique
  • M2M machine to machine
  • GPRS General Packet Radio Service
  • EPS Packet Switching
  • H2H Human to Human
  • the GPRS network is a second-generation mobile communication network based on packet switching.
  • GPRS evolves into the Universal Mobile Telecommunication System Packet Switch (UMTS PS) domain.
  • UMTS PS Universal Mobile Telecommunication System Packet Switch
  • the GPRS network architecture includes the following network elements:
  • the RNS includes a Node B (NodeB) and a Radio Network Controller (RNC).
  • NodeB provides air interface connections for the terminal.
  • the RNC is mainly used to manage radio resources and control the NodeB.
  • 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 domain core network
  • SGSN Serving GPRS Support Node
  • GGSN Gateway GPRS Support Node
  • 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;
  • the machine type communication server is an M2M application server, which is used to provide an M2M application for the user, and is connected to the GGSN through the MTCi interface.
  • 3GPP 3rd Generation Partnership Project
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • E-UTRAN Evolved UTRAN
  • WLAN Wireless Local Area Network
  • the SAE architecture includes the radio access network eNodeB, the core network control plane network element MME, and the core network user plane network element Serving GW/PDN GW and other network elements.
  • the network element included in the Evolved Radio Access Network (E-RAN) is an evolved Node B.
  • the Mobility Management Entity is a control plane function entity that temporarily stores user data. It is responsible for managing and storing the context of user equipment (UE, User Equipment) (such as user ID, mobility management status, and user security). a parameter, etc., assigns a temporary identifier to the user, and when the UE is camped on the tracking area or the network, is responsible for authenticating the user;
  • the service gateway (S-GW, Serving Gateway) is a user plane entity responsible for user plane data routing processing, terminating the downlink data of the UE in the idle (ECM_IDLE) state; managing and storing the SAE bearer context of the UE, for example IP bearer service parameters and network internal routing information;
  • S-GW is the anchor point of the internal user plane of the 3GPP system, and a user can only have one S-GW at a time;
  • the packet data network gateway (P-GW, PDN Gateway) is the gateway responsible for the UE accessing the PDN, assigns the user IP address, and is also the mobility anchor of the 3GPP and non-3GPP access systems.
  • the function of the P-GW also includes the policy implementation. And charging support; the user can access multiple P-GWs at the same time; the Policy and Charging Enforcement Function (PCEF) is also located in the P-GW;
  • PCEF Policy and Charging Enforcement Function
  • the Home Subscriber Server (HSS) is responsible for permanently storing user subscription data.
  • the content stored in the HSS includes the UE's International Mobile Subscriber Identification (IMSI) and the IP address of the P-GW.
  • IMSI International Mobile Subscriber Identification
  • the S-GW and the P-GW can be combined, and the EPC system user plane network element includes the S-GW and the P-GW.
  • M2M service is a networked application and service based on intelligent interaction of machine terminals. It uses intelligent machine terminals to transmit information through wireless networks, and provides information solutions for customers to meet customer monitoring, command and dispatch. Information needs for data collection and measurement.
  • M2M communication object is machine-to-machine, it can be communication between person and machine, machine and Communication between servers, communication between different intelligent terminals.
  • Different applications of MTC devices have different characteristics, such as elevators and other elevator devices have low mobility, PS only attributes, while monitoring and alarm devices have low mobility and high availability in addition to low mobility, PS only. Therefore, different system optimizations are required for MTC devices of different applications, and the MTC devices can be effectively managed, monitored, and paid.
  • the 3GPP network needs to be optimized so that the network has the ability to activate the terminal, so that when the MTC server needs the MTC device to report data or control it, the MTC can be triggered at any time.
  • the device establishes data communication with the MTC Server.
  • the MTC enhancement architecture of the PS network is shown in Figure 1, and introduced in the PS network architecture.
  • the MTC Server is used to provide M2M application control for users.
  • the MTC Server is mainly responsible for information collection and data storage/processing of the MTC device (MTC UE), and can perform necessary management on the MTC device;
  • the MTCi interface is connected to the P-GW.
  • the MTC IWF network element is responsible for network topology hiding and application layer and bearer layer protocol conversion.
  • the MTCsp interface uses the MTCsp interface to connect with the MTC Server, and uses the S6m interface to connect with the HSS/HLR.
  • the T5a/d is connected to the SGSN/MME.
  • the function of the existing MTC IWF is to receive the activation message of the MTC server and send the activation message to the MTC UE through the relevant network element of the 3GPP network.
  • MTC network enhancement mainly considers the process of activation using MTC IWF. As shown in Figure 2, the following steps are included:
  • Step 201 The MTC UE in the 3GPP packet domain, including the GPRS network and the EPS network, needs to initiate an attach request to the radio access network RNS (eNodeB or RNC) (hereinafter referred to as RNS, the same below), where the identifier of the MTC UE is carried (ie, the IMSI) ), the network access capability of the MTC UE, Request information such as an indication of the assigned IP and the capabilities of the terminal access agent. If the location changes when the terminal is online, a location update (TAU) process is initiated.
  • RNS radio access network
  • the RNS selects an MME/SGSN (MME or SGSN) for the MTC UE, and forwards the attach request to the MME/SGSN, and also carries the related information carried in the attached message to the MME/SGSN.
  • MME Mobility Management Entity
  • the MME/SGSN sends a location update request to the HSS of the home network of the MTC UE, which carries the address information of the MME/SGSN and the identifier of the MTC UE (IMSI), and informs the HSS of the currently accessed area of the MTC UE.
  • the HSS is identified according to the identifier of the MTC UE. (IMSI) finds the subscriber data and sends it to the MME/SGSN.
  • the SGSN/MME sends an attached access to the terminal, and the terminal is connected to the 3GPP network.
  • Step 202 The MTC Server needs to activate the MTC UE according to the application requirement.
  • the activation request of the MTC UE is sent to the home MTC IWF through the MTCsp interface, and the activation request message carries information such as trigger information and MTC UE identifier.
  • Step 203 The MTC IWF obtains an IP address of the SGSN/MME to which the MTC UE is attached and an IMSI identifier of the MTC UE from the HSS/HLR according to the MTC UE identifier in the activation request message.
  • Step 204 The MTC IWF sends a request for activating the terminal to the SGSN/MME, where the information such as the trigger information and the IMSI identifier is carried.
  • Step 205 The MME/SGSN saves the activation request locally according to the operator policy, and waits for the MTC UE to initiate a TAU process.
  • Step 206 The MTC UE initiates a periodic TAU request or a TAU request initiated by the location change to the MME/SGSN.
  • Step 207 After receiving the TAU request, the SGSN/MME performs a process of performing a location update process such as bearer modification.
  • Step 208 The MME/SGSN carries the non-access stratum (NAS) signaling in the TAU response.
  • the activation request of the terminal sends an activation request message to the MTC UE.
  • NAS non-access stratum
  • Step 209 The MTC UE sends a TAU complete message to the SGSN/MME, where the message carries the activation request accepted information.
  • Step 210 The MME/SGSN returns an activation request sending success message to the MTC IWF.
  • the process of how the trigger message is sent and how to respond in the MTC IWF congestion scenario is not considered, and the small data in the MTC IWF congestion scenario is transmitted through the MTC IWF. And how to monitor how messages are transmitted through the MTC IWF.
  • the MTC IWF needs to handle a large amount of signaling from the 3GPP network and the MTC Server, and there is a possibility of congestion. If a large amount of signaling is still received, the signaling interface of the MTC IWF and the network and the MTC Server will be blocked for a long time, and the MTC related signaling cannot be processed. The heavy degree may cause the MTC. The IWF network element crashed, causing network failure.
  • the main purpose of the embodiments of the present invention is to provide a method and system for network congestion control, so as to avoid receiving and processing a large amount of signaling from an interface when the MTC IWF is congested, and the MTC IWF may not work normally due to severe congestion.
  • the problem is to provide a method and system for network congestion control, so as to avoid receiving and processing a large amount of signaling from an interface when the MTC IWF is congested, and the MTC IWF may not work normally due to severe congestion.
  • the embodiment of the invention provides a method for network congestion control, the method includes: when the machine type communication interconnection function entity MTC IWF is congested, the MTC IWF notifies the third generation partner plan 3GPP network control plane The network element or the MTC server; the 3GPP network control plane network element or the MTC server no longer sends a non-emergency signaling message to the MTC IWF during the MTC IWF congestion.
  • the method also includes:
  • the 3GPP network control plane network element or the MTC server sends an emergency signaling message carrying the emergency identifier to the MTC IWF.
  • the non-emergency signaling message includes a signaling message that does not carry an emergency identifier associated with a low priority MTC UE or a normal MTC UE.
  • the method also includes:
  • the 3GPP network control plane network element or the MTC server After the congestion of the MTC IWF is released, the 3GPP network control plane network element or the MTC server sends a non-emergency signaling message to the MTC IWF.
  • the method also includes:
  • the 3GPP network control plane network element After receiving the congestion notification from the MTC IWF, the 3GPP network control plane network element sends an activation message from the MTC UE that has been received before the MTC IWF is congested, when the activation validity time expires, A response message indicating that the activation or failure of the activation of the MTC UE is sent to the MTC IWF; and the MTC IWF processes according to the local policy.
  • the MTC IWF notifies the 3GPP network control plane network element or the MTC server of the congestion status by using the inter-device system message.
  • the inter-device system message includes a congestion start message and a congestion end message.
  • the MTC IWF notifies the 3GPP network control plane network element or the MTC server by carrying the MTC IWF congestion indication and the delay time in the terminal signaling message associated with the MTC UE.
  • the method also includes: After the delay time expires, the 3GPP network control plane network element or the MTC server attempts to send a non-emergency signaling message to the MTC IWF, and if the MTC IWF congestion is released, the received non-emergency signaling is received. The message is processed normally; if the MTC IWF congestion is still not released, the MTC IWF rejects the received non-emergency signaling message, and re-notifies the congestion indication and delay time to the 3GPP network control plane network. Meta or MTC server.
  • the embodiment of the present invention further provides a network congestion control system, the system includes: a machine type communication interconnection function entity MTC IWF, and further includes: a third generation partnership plan 3GPP network control plane network element or an MTC server, where
  • the MTC IWF is configured to notify the 3GPP network control plane network element or the MTC server of congestion when the congestion occurs by itself;
  • the 3GPP network control plane network element or the MTC server is configured to not send non-emergency signaling messages to the MTC IWF during MTC IWF congestion.
  • the 3GPP network control plane network element or the MTC server is further configured to send an emergency signaling message carrying the emergency identifier to the MTC IWF during the MTC IWF congestion.
  • the non-emergency signaling message includes a signaling message that does not carry an emergency identifier associated with a low priority MTC UE or a normal MTC UE.
  • the 3GPP network control plane network element or the MTC server is further configured to: after the congestion of the MTC IWF is released, send a non-emergency signaling message to the MTC IWF.
  • the 3GPP network control plane network element is further configured to: after receiving the congestion notification from the MTC IWF, the activation message from the MTC UE that has been received before the MTC IWF is congested, And sending, to the MTC IWF, a response message that the activation or failure of the activation of the MTC UE is performed; and the MTC IWF processes according to the local policy.
  • the MTC IWF is further configured to notify the 3GPP network control plane network element or the MTC server by using the inter-device system message to notify the 3GPP network control plane network element or the MTC server.
  • the inter-device system message includes a congestion start message and a congestion end message.
  • the MTC IWF is further configured to notify the 3GPP network control plane network element or the MTC server by carrying the MTC IWF congestion indication and the delay time in the terminal signaling message related to the MTC UE.
  • the 3GPP network control plane network element or the MTC server is further configured to: after the delay time ends, attempt to send a non-emergency signaling message to the MTC IWF;
  • the MTC IWF performs normal processing on the received non-emergency signaling message; if the MTC IWF congestion is still not released, the MTC IWF receives the non-emergency The signaling message performs a rejection process and re-notifies the congestion indication and delay time to the 3GPP network control plane network element or the MTC server.
  • a method and system for network congestion control when a signaling congestion occurs in an MTC IWF, timely notifying a 3GPP network and an MTC Server according to a congestion mechanism, and the 3GPP network and the MTC Server suspend or reject the low priority MTC UE.
  • non-emergency signaling of the normal MTC UE which not only ensures that the emergency signaling can be processed in time, but also avoids that the MTC IWF still receives and processes a large amount of signaling during congestion to increase congestion; so that the MTC enhanced architecture can effectively cope with a large number of
  • the scenario of concurrent signaling flows ensures that the MTC UE communicates with the MTC Server in time to meet the requirements of the Internet of Things.
  • FIG. 1 is a schematic diagram of an MTC enhanced architecture of a PS network in the prior art
  • FIG. 3 is a flowchart of a method for network congestion control according to an embodiment of the present invention.
  • FIG. 4 is a flowchart 1 of notifying an SGSN/MME network element in a 3GPP network when an MTC IWF is congested in an activation process according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a MTC IWF congestion notification in a small data packet transmission process according to an embodiment of the present invention
  • Flowchart 1 of the SGSN/MME network element in the 3GPP network is a flowchart 2 of notifying an SGSN/MME network element in a 3GPP network when an MTC IWF is congested in an activation procedure according to an embodiment of the present invention
  • FIG. 7 is a flowchart 2 of notifying an SGSN/MME network element in a 3GPP network when an MTC IWF is congested in a small data packet transmission process according to an embodiment of the present invention
  • FIG. 8 is a flowchart 1 of notifying an MTC Server when an MTC IWF is congested in an activation process according to an embodiment of the present invention
  • FIG. 9 is a flowchart 2 of notifying an MTC Server when an MTC IWF is congested during an activation process according to an embodiment of the present invention.
  • the MTC IWF when the MTC IWF is congested, the MTC IWF actively informs the related entities that have signaling interactions when the MTC IWF is congested.
  • the control plane network element SGSN/MME in the 3GPP network the MTC Server responsible for MTC service control and terminal management. After the SGSN/MME or the MTC Server knows that the MTC IWF has been signaling congestion, it will not send the non-emergency signaling message to the MTC IWF for processing, and only sends the emergency signaling message, which greatly reduces the signaling processing pressure of the MTC IWF. , enabling the MTC IWF to quickly return to normal.
  • the MTC IWF congestion notification is flexible. It can be notified by system messages between devices, such as the congestion start message and the congestion end message. This requires the T5 interface for the interaction between the MTC IWF and the SGSN/MME, and the MTC IWF and MTC Server.
  • the interactive MTCsp interface is enhanced to support the system message. In order to avoid the increase of the interface caused by the increase of the system message, the system is too complicated.
  • the MTC IWF congestion identifier may be transmitted in the terminal related terminal signaling message to notify the MTC Server or the SGSN/MME, and carry a delay.
  • a method for network congestion control according to an embodiment of the present invention mainly includes the following steps:
  • Step 301 When the MTC IWF is congested, the MTC IWF notifies the 3GPP network control plane network element or the MTC Server of congestion.
  • Step 302 The 3GPP network control plane network element or the MTC Server no longer sends a non-emergency signaling message to the MTC IWF during the MTC IWF congestion.
  • the 3GPP network control plane network element or the MTC Server may send an emergency signaling message carrying the emergency identifier to the MTC IWF.
  • the non-emergency signaling message includes a signaling message that does not carry an emergency identifier associated with a low priority MTC UE or a normal MTC UE.
  • the attributes of the low priority or normal MTC UE of the MTC UE may be defined and configured by the network operator according to the actual application requirements of the MTC UE.
  • the 3GPP network control plane network element After receiving the congestion notification from the MTC IWF, the 3GPP network control plane network element sends an activation message from the MTC UE that has been received before the MTC IWF is congested, and when the activation validity time expires, the MTC UE is The response message of activation success or failure is sent to the MTC IWF; the MTC IWF processes according to the local policy.
  • the 3GPP network control plane network element or the MTC Server After the congestion of the MTC IWF is released, the 3GPP network control plane network element or the MTC Server sends a non-emergency signaling message to the MTC IWF.
  • the MTC IWF may notify the 3GPP network control plane network element or the MTC Server of the congestion condition by using the inter-device system message, where the inter-device system message includes a congestion start message and a congestion end message.
  • the MTC IWF may also notify the 3GPP network control plane network element by carrying the MTC IWF congestion indication and the delay time in the terminal signaling message related to the MTC UE.
  • MTC Server may also notify the 3GPP network control plane network element by carrying the MTC IWF congestion indication and the delay time in the terminal signaling message related to the MTC UE.
  • the 3GPP network control plane network element or the MTC Server attempts to send a non-emergency signaling message to the MTC IWF. If the MTC IWF is congested, the received non-received The emergency signaling message is processed normally; if the MTC IWF congestion is still not released, the MTC IWF rejects the received non-emergency signaling message, and re-notifies the congestion indication and delay time to the 3GPP network control plane network element or MTC. Server.
  • FIG. 4 shows a flow of notifying the SGSN/MME network element in the 3GPP network when the MTC IWF is congested during the activation process.
  • the MTC IWF when the MTC IWF is congested, the MTC IWF sends a congestion start notification message to the SGSN/MME of the 3GPP network, and the SGSN/MME performs non-emergency for the low priority terminal or the ordinary terminal in the MTC UE activation process according to the operator policy.
  • the activation response signaling is no longer sent to the MTC IWF; the emergency activation response signaling can still be sent to the MTC IWF for processing during the MTC IWF congestion.
  • the MTC IWF After the congestion of the MTC IWF is released, the MTC IWF sends a congestion end notification message to the SGSN/MME of the 3GPP network. After the SGSN/MME knows that the MTC IWF has been de-congested, the congestion control restriction is not performed, and all activation response signaling can be performed. Send it to the MTC IWF for processing.
  • the process shown in Figure 4 mainly includes the following steps:
  • Step 401 The MTC UE initiates an attach request to the 3GPP packet network. After receiving the attach request, the SGSN/MME downloads the subscription data of the user from the HSS/HLR, saves the terminal context, and allows the terminal to access the 3GPP network, and the MTC UE successfully attaches to the 3GPP.
  • the internet The internet.
  • Step 402 The MTC Server needs to activate the MTC UE according to the application requirement.
  • the MTC Server sends an activation request to the MTC UE to the MTC IWF through the MTCs interface, and the MTC IWF obtains the IP address of the SGSN/MME attached to the MTC UE and the IMSI identifier of the MTC UE from the HSS/HLR, and sends the activation request to the SGSN.
  • the activation request may include activation activation time, activation information, and the like.
  • Step 403 After receiving the activation request, the SGSN/MME may temporarily save the activation timer, and start the activation timer according to the activation effective time.
  • the activation information is sent to the MTC UE. If the activation is successful, the activation success response is reported to the MTC IWF. If the timer is activated If the MTC UE is still not successfully activated, the activation failure message is reported to the MTC IWF, and the MTC IWF sends an activation response message to the MTC Server.
  • Step 404 the MTC IWF has signaling congestion.
  • Signaling congestion can be pre-set.
  • the MTC IWF processing resources are less than 30%, which can be defined as signaling congestion.
  • Step 405 The MTC IWF sends a congestion start message to the SGSN/MME, and notifies the SGSN/MME about the congestion status of the MTC IWF.
  • Step 406 After receiving the congestion start message, the SGSN/MME performs the restriction control of the congestion control, and according to the operator policy, the non-emergency MTC activation response signaling for the low priority terminal or the common terminal does not carry the emergency identifier, Then, it is sent to the MTC IWF for processing, and the signaling message that cannot be sent can be temporarily stored or rejected in the SGSN/MME.
  • the response message may be a message that the emergency activation succeeds or the emergency activation fails.
  • the message carries the emergency identifier, and the SGSN/MME can directly send the MTC IWF for processing, which is not restricted by the congestion control.
  • the MTC IWF sends the emergency activation response to the MTC Server.
  • Step 407 before the MTC IWF is not congested, the activation message of some terminals has been sent to the SGSN/MME.
  • the SGSN/MME may The response message of the activation or failure of the activation of the terminal is sent to the MTC IWF, and the MTC IWF determines whether to send the activation response message to the MTC Server according to the policy.
  • Step 408 When the congestion is released, the MTC IWF sends a congestion end message to the SGSN/MME, and notifies the SGSN/MME that the congestion has been released.
  • Step 409 the SGSN/MME learns that the MTC IWF congestion has been canceled, and performs normal signaling interaction with the MTC IWF, and sends the non-emergency activation response message to be sent, including the low priority terminal and the activation response message related to the common terminal to the MTC.
  • the MTC IWF processes the activation response message to the MTC Server.
  • FIG. 5 shows the notification of the 3GPP network when the MTC IWF is congested in the small packet transmission procedure.
  • the MTC IWF when the MTC IWF is congested, the MTC IWF sends a congestion start notification message to the SGSN/MME of the 3GPP network, and the SGSN/MME, according to the operator policy, includes a low priority terminal or a normal terminal in the small packet transmission process.
  • the 'J the non-emergency signaling message of the data packet is no longer sent to the MTC IWF; for the emergency 'j, the signaling of the data packet can still be sent to the MTC IWF during the MTC IWF congestion.
  • the MTC IWF After the congestion of the MTC IWF is released, the MTC IWF sends a congestion end notification message to the SGSN/MME of the 3GPP network. After the SGSN/MME learns that the MTC IWF has been de-congested, the congestion control restriction is not performed, and all the small data packets are included. Signaling messages are sent to the MTC IWF for processing.
  • the process shown in Figure 5 mainly includes the following steps:
  • Step 501 The MTC UE initiates an attach request to the 3GPP packet network. After receiving the attach request, the SGSN/MME downloads the subscription data of the user from the HSS/HLR, saves the terminal context, and allows the terminal to access the 3GPP network, and the MTC UE successfully attaches to the 3GPP network.
  • the internet The internet.
  • step 502 signaling congestion occurs in the MTC IWF.
  • Signaling congestion can be pre-set.
  • the MTC IWF processing resources are less than 30%, which can be defined as signaling congestion.
  • Step 503 The MTC IWF sends a congestion start message to the SGSN/MME to notify the SGSN/MME about the congestion status of the MTC IWF.
  • the SGSN/MME After receiving the congestion start message, the SGSN/MME performs the restriction control of the congestion control. According to the operator policy, the non-emergency signaling message including the small data packet that does not carry the emergency identifier associated with the low priority terminal or the ordinary terminal is not Then, it is sent to the MTC IWF for processing, and the signaling containing the small data packet that cannot be sent can be rejected in the SGSN/MME.
  • Step 504 The MTC UE sends the NAS signaling carrying the small data packet to the SGSN/MME.
  • the signaling message may carry the emergency identifier, and the SGSN/MME may directly send the signaling to the MTC IWF for processing, without being restricted by the congestion control.
  • the MTC IWF sends the d and the data packet to the MTC Server.
  • Step 506 For the low-priority terminal-related or common terminal-related non-emergency NAS signaling including small data packets, according to the operator policy, when the SGSN/MME learns that the MTC IWF is congested, it responds to the NAS signaling rejection message. The delay message and the cause value of the MTC IWF congestion are carried in the reject message to the MTC UE. After the MTC UE learns that the MTC IWF is congested, the NAS signaling related to the MTC IWF is not initiated within the delay access time period, and then attempts to initiate the NAS signaling including the small data packet after the delay access time expires. .
  • Steps 505 and 506 are performed in no particular order, and step 505 or 506 is determined according to the judgment result of the NAS signaling carrying the small data packet sent by the MTC UE.
  • Step 507 When the congestion is released, the MTC IWF sends a congestion end message to the SGSN/MME, and notifies the SGSN/MME that the congestion has been released.
  • Step 508 When the MTC UE has a small data packet to send, the MTC UE sends the NAS signaling carrying the small data packet to the SGSN/MME; or when the delayed access time expires, the previous MTC UE tries again. Initiate NAS signaling with small packets.
  • Step 509 the SGSN/MME learns that the MTC IWF congestion has been canceled, and performs signaling interaction with the MTC IWF normally, and the signaling message containing the small data packet to be sent, whether it is a low priority terminal or an ordinary terminal related signaling.
  • the messages are sent to the MTC IWF, and the MTC IWF processes the small packets to the MTC Server.
  • Figure 6 shows another flow of notifying the SGSN/MME network element in the 3GPP network when the MTC IWF is congested during the activation process.
  • the MTC IWF rejects the activation response message sent by the SGSN/MME of the 3GPP network, and carries the MTC IWF congestion indication and the delay time in the rejection message.
  • the SGSN/MME does not send the activation response signaling for the low priority terminal or the normal terminal to the MTC IWF in the MTC UE activation process according to the operator policy; the emergency activation response signaling can still be sent to the MTC during the MTC IWF congestion. IWF processing.
  • the SGSN/MME attempts to re-initiate the non-emergency activation response signaling of the low priority terminal or the ordinary terminal to the MTC IWF. If the MTC IWF has returned to normal, the signaling can be processed normally, if the SGSN/MME does not Receiving the rejection message carrying the MTC IWF congestion indication again, the default MTC IWF is restored to normal, and the restriction of congestion control is no longer performed, and all activation response signaling may be sent to the MTC IWF for processing; if the MTC IWF is still congested, The MTC IWF congestion indication and the delay time are carried in the reject message again, and the SGSN/MME waits for the next delay time to end, and then attempts to send the activation response message until the MTC IWF returns to normal.
  • the process shown in Figure 6 mainly includes the following steps:
  • Step 601 The MTC UE initiates an attach request to the 3GPP packet network. After receiving the attach request, the SGSN/MME downloads the subscription data of the user from the HSS/HLR, saves the terminal context, and allows the terminal to access the 3GPP network, and the MTC UE successfully attaches to the 3GPP network.
  • the internet The internet.
  • Step 602 The MTC Server needs to activate the MTC UE according to the application requirement.
  • the MTC Server sends an activation request to the MTC UE to the MTC IWF through the MTCs interface, and the MTC IWF obtains the IP address of the SGSN/MME attached to the MTC UE and the IMSI identifier of the MTC UE from the HSS/HLR, and sends the activation request to the SGSN.
  • the activation request may include activation activation time, activation information, and the like.
  • Step 603 After receiving the activation request, the SGSN/MME may temporarily save the activation timer, and start the activation timer according to the activation effective time.
  • the activation information is sent to the MTC UE. If the activation is successful, the activation success response is reported to the MTC IWF. If the MTC UE cannot be successfully activated when the activation timer overflows, the activation failure message is reported to the MTC IWF, and the MTC IWF sends an activation response message to the MTC Server.
  • Step 604 the MTC IWF has signaling congestion.
  • Signaling congestion can be pre-set.
  • the MTC IWF processing resources are less than 30%, which can be defined as signaling congestion.
  • Step 605 After receiving the activation response message of the MTC UE, the SGSN/MME may not activate the MTC UE after the activation timer overflows, and the SGSN/MME sends the low priority end to the MTC IWF.
  • a non-emergency activation response message that does not carry an emergency identifier associated with the terminal or the ordinary terminal.
  • Step 606 The MTC IWF determines that the signaling is congested, and does not process the signaling message, and directly sends a reject response to the SGSN/MME, where the response message carries the MTC IWF congestion indication and the delay time.
  • the SGSN/MME After receiving the rejection response carrying the MTC IWF congestion indication, the SGSN/MME performs the congestion control restriction, and according to the operator policy, the relevant non-emergency MTC activation response signaling for the low priority terminal or the ordinary terminal is no longer It is sent to the MTC IWF for processing, and the signaling message that cannot be sent can be temporarily stored or rejected in the SGSN/MME.
  • the delay time timer is started, and an attempt to send an activation response is performed when the timer overflows.
  • the response message may be a message that the emergency activation succeeds or the emergency activation fails.
  • the message may carry the emergency identifier, and the SGSN/MME may directly send the processing to the MTC IWF without being restricted by the congestion control.
  • the MTC IWF sends the emergency activation response to the MTC Server.
  • Step 608 before the MTC IWF is not congested, the activation message of some MTC UEs has been sent to the SGSN/MME.
  • the SGSN/MME may The activation success or failure message of the MTC UE is sent to the MTC IWF, and the MTC IWF determines whether to send the activation response message to the MTC Server according to the policy.
  • Step 609 when the delay time timer overflows, the SGSN/MME attempts to initiate an activation response message related to the low priority terminal or the ordinary terminal to the MTC IWF.
  • Step 610 (including 610a, 610b), if the MTC IWF is still in the signaling congestion, the MTC IWF will initiate the reject response again, and carry the MTC IWF congestion indication and the delay time in the response message, corresponding to step 610a.
  • the SGSN/MME waits for the next delay time to expire before attempting until the MTC IWF is normal.
  • the MTC IWF If the MTC IWF has returned to normal, the MTC IWF no longer rejects the activation response message. Instead, the activation response message is sent to the MTC Server after processing, corresponding to step 610b.
  • the SGSN/MME After the SGSN/MME sends the activation response message, it does not receive the rejection response carrying the MTC IWF congestion again. The default MTC IWF congestion is released, and the signaling interaction with the MTC IWF is performed normally.
  • the SGSN/MME sends the pending activation response message.
  • the activation response message including the low priority terminal and the common terminal is sent to the MTC IWF, and the MTC IWF processes the activation response message to the MTC Server.
  • Figure 7 shows another flow of notifying the SGSN/MME network element in the 3GPP network when the MTC IWF is congested in the small packet transmission procedure.
  • the MTC IWF rejects the non-emergency signaling message transmitted by the small packet of the SGSN/MME of the 3GPP network, and carries the MTC IWF congestion indication and the delay time in the reject message.
  • the non-emergency signaling message for the small data packet including the low priority terminal or the ordinary terminal is not sent to the MTC IWF; the signaling for the emergency small data packet Messages can still be sent to the MTC IWF for processing during MTC IWF congestion.
  • the SGSN/MME After the delay time expires, the SGSN/MME attempts to re-initiate the non-emergency signaling message containing the small data packet of the low priority terminal or the ordinary terminal to the MTC IWF. If the MTC IWF has returned to normal, the signaling message can be processed normally.
  • the SGSN/MME does not receive the reject message carrying the MTC IWF congestion indication again, the default MTC IWF is restored to normal, and the restriction of congestion control is not performed, and all small packet transmission signaling can be sent to the MTC IWF for processing; If the MTC IWF is still congested, the MTC IWF congestion indication and the delay time are carried in the reject message again, and the SGSN/MME waits for the next delay time to try to send the small data packet transmission message until the MTC IWF returns to normal.
  • the process shown in Figure 7 mainly includes the following steps:
  • Step 701 The MTC UE initiates an attach request to the 3GPP packet network. After receiving the attach request, the SGSN/MME downloads the subscription data of the user from the HSS/HLR, saves the terminal context, and allows the terminal to access the 3GPP network, and the MTC UE successfully attaches to the 3GPP.
  • the internet The internet.
  • signaling congestion occurs in the MTC IWF. Signaling congestion can be pre-set. For example, the MTC IWF processing resources are less than 30%, which can be defined as signaling congestion.
  • Step 703 The MTC UE sends the NAS signaling carrying the small data packet to the SGSN/MME. If it is an emergency small data packet, it carries an emergency identifier in the NAS signaling.
  • Step 704 The SGSN/MME sends the small data packet transmission message to the MTC IWF, and carries information such as the MTC UE identifier and the emergency identifier.
  • Step 705 The MTC IWF determines that the UE has been signaling congestion, and does not process the non-emergency small packet transmission signaling message, directly initiates a reject response, and carries the MTC IWF congestion indication and the delay time in the response message.
  • the SGSN/MME After receiving the rejection response carrying the MTC IWF congestion indication, the SGSN/MME performs the restriction control of the congestion control, and according to the operator policy, the non-emergency signaling message including the small data packet related to the low priority terminal or the ordinary terminal, It is no longer sent to the MTC IWF for processing, and the signaling containing the small data packet that cannot be sent can be rejected in the SGSN/MME.
  • the delay time timer is started, and an attempt to send an activation response is performed when the timer overflows.
  • Step 706 If it is an emergency small data packet, the emergency signaling notification SGSN/MME may be carried in the NAS signaling.
  • the signaling message may carry the emergency identifier, and the SGSN/MME may directly send the signaling to the MTC IWF for processing, which is not restricted by the congestion control.
  • the MTC IWF sends the ', data packet to the MTC Server.
  • Step 707 For the low-priority terminal-related or common terminal-related non-emergency NAS signaling including small data packets, according to the operator policy, when the SGSN/MME learns that the MTC IWF is congested, it responds to the NAS signaling rejection message. The delay message and the cause value of the MTC IWF congestion are carried in the reject message to the MTC UE. After the MTC UE learns that the MTC IWF is congested, the NAS signaling related to the MTC IWF is no longer initiated within the delay access time period, and then attempts to initiate the NAS signaling including the small data packet after the delay access time expires. .
  • Step 708 When the MTC UE has a small data packet to send, the MTC UE sends the NAS signaling carrying the small data packet to the SGSN/MME; or when the delayed access time expires, the previous MTC UE tries again. Initiate NAS signaling with small packets.
  • Step 709 after the delay time timer of the SGSN/MME side overflows, the SGSN/MME attempts to initiate a small data packet transmission message related to the low priority terminal or the ordinary terminal to the MTC IWF.
  • Step 710 (including 710a, 710b), if the MTC IWF is still in the signaling congestion, the MTC IWF will initiate the reject response again, and carry the MTC IWF congestion indication and the delay time in the response message, corresponding to step 710a.
  • the SGSN/MME waits for the next delay time to expire before attempting until the MTC IWF is normal.
  • the MTC IWF no longer rejects the small packet transmission message, but sends a small packet transmission message to the MTC Server after processing, corresponding to step 710b.
  • the SGSN/MME After the SGSN/MME sends a small packet transmission signaling message, it does not receive the rejection response carrying the MTC IWF congestion again.
  • the default MTC IWF congestion is removed, the signaling interaction with the MTC IWF is performed normally, and the SGSN/MME will follow the small data.
  • the packet transmission message including the low priority terminal and the small terminal related small packet transmission message, is sent to the MTC IWF, and the MTC IWF processes the 'J, the packet message to the MTC Server.
  • Figure 8 shows a flow of notifying the MTC Server when the MTC IWF is congested during the activation process.
  • the MTC IWF when the MTC IWF is congested, the MTC IWF sends a congestion start notification message to the MTC Server.
  • the MTC Server does not send the non-emergency activation request signaling to the low priority terminal or the ordinary terminal to the MTC.
  • the IWF; emergency activation request signaling can still be sent to the MTC IWF for processing during the MTC IWF congestion.
  • the MTC IWF sends a congestion end notification message to the MTC Server.
  • the process shown in Figure 8 mainly includes the following steps:
  • Step 801 The MTC UE initiates an attach request to the 3GPP packet network. After receiving the attach request, the SGSN/MME downloads the subscription data of the user from the HSS/HLR, saves the terminal context, and allows the terminal to access the 3GPP network, and the MTC UE successfully attaches to the 3GPP.
  • the internet The internet.
  • step 802 signaling congestion occurs in the MTC IWF.
  • Signaling congestion can be pre-set.
  • the MTC IWF processing resources are less than 30%, which can be defined as signaling congestion.
  • Step 803 The MTC IWF sends a congestion start message to the MTC Server, and notifies the MTC Server about the congestion status of the MTC IWF.
  • Step 804 After receiving the congestion start message, the MTC Server performs the congestion control restriction, and the non-emergency activation request signaling for the low priority terminal or the ordinary terminal is not sent to the MTC IWF for processing.
  • the MTC Server needs to activate the MTC UE according to the application requirements.
  • the MTC Server sends an activation request to the MTC UE to the MTC IWF through the MTCsp interface.
  • the activation request message carries the emergency identifier, and the MTC Server directly sends the MTC IWF for processing, which is not restricted by the congestion control.
  • the MTC IWF sends an emergency activation request to the SGSN/MME.
  • Step 805 If the MTC UE is in an idle state, the SGSN/MME initiates a paging request to the MTC UE, and notifies the MTC UE to establish a wireless connection.
  • Step 806 The MTC UE sends a service request (service request) to the SGSN/MME, and the SGSN/MME establishes a wireless connection with the MTC UE.
  • service request service request
  • Step 807 The SGSN/MME sends an emergency activation request to the MTC UE in the service request response message.
  • Step 808 After the SGSN/MME activates the terminal successfully, the emergency activation response is sent to the MTC IWF, and the MTC IWF processes the emergency activation response to the MTC Server.
  • Step 809 After the emergency activation of the MTC UE is successful, an emergency bearer is established, and an emergency data communication service is performed with the MTC Server.
  • Step 810 After the MTC IWF returns to normal, send a congestion end message to the MTC Server to notify the MTC Server that the congestion has been released.
  • Steps 811 to 814 the MTC Server learns that the MTC IWF congestion has been canceled, and performs signaling interaction with the MTC IWF.
  • the activation request message to be sent including the low-priority terminal and the non-emergency activation request message related to the ordinary terminal, is sent to the MTC server.
  • the MTC IWF processes the activation request message to the SGSN/MME, which is delivered by the SGSN/MME to the MTC UE in the TAU response message.
  • Step 815 After the MTC UE is successfully activated, the normal bearer is established, and the normal data communication service is performed with the MTC Server.
  • Figure 9 shows another process for notifying the MTC Server when the MTC IWF is congested during the activation process.
  • the MTC IWF rejects the non-emergency activation request message sent by the MTC Server, and carries the MTC IWF congestion indication and the delay time notification to the MTC Server in the rejection message.
  • the MTC Server does not send the non-emergency activation request signaling to the low priority terminal or the normal terminal to the MTC IWF; the emergency activation response signal can still be sent to the MTC IWF during the MTC IWF congestion.
  • the MTC Server After the delay time expires, the MTC Server attempts to re-initiate the non-emergency activation response signaling of the low priority terminal or the ordinary terminal to the MTC IWF. If the MTC IWF has returned to normal, the signaling can be processed normally, if the MTC Server does not receive the signal again. To the reject message carrying the MTC IWF congestion indication, the default MTC IWF is restored to normal, and the restriction of congestion control is no longer performed.
  • All activation request signaling can be sent to the MTC IWF for processing; if the MTC IWF is still congested, then again The MTC IWF congestion indication and delay time are carried in the reject message, and the MTC Server waits for the next delay time to end and then attempts to send the activation request message until the MTC IWF returns to normal.
  • the process shown in Figure 9 mainly includes the following steps:
  • Step 901 The MTC UE initiates an attach request to the 3GPP packet network, and after receiving the attach request, the SGSN/MME downloads the subscription data of the user from the HSS/HLR, saves the terminal context, and allows the terminal.
  • the terminal accesses to the 3GPP network, and the MTC UE successfully attaches to the 3GPP network.
  • step 902 signaling congestion occurs in the MTC IWF.
  • Signaling congestion can be pre-set.
  • the MTC IWF processing resources are less than 30%, which can be defined as signaling congestion.
  • Step 903 The MTC Server needs to activate the MTC UE according to the application requirement.
  • the MTC Server sends an activation request to the MTC UE to the MTC IWF through the MTCsp interface.
  • Step 904 The MTC IWF determines that the UE has been signaling congestion, and no longer processes the activation request signaling message, and directly initiates a rejection response.
  • the response message carries the MTC IWF congestion indication and the delay time to the MTC Server.
  • the MTC Server After receiving the rejection response carrying the MTC IWF congestion indication, the MTC Server performs the congestion control restriction, and the non-emergency MTC activation request signaling for the low priority terminal or the ordinary terminal is not sent to the MTC IWF for processing.
  • the delay time timer is started, and an attempt to send a non-emergency activation request is executed when the timer overflows.
  • Step 905 For the emergency activation request, the activation request message carries the emergency identifier, and the MTC Server directly sends the MTC IWF for processing, which is not restricted by the congestion control.
  • the MTC IWF sends an emergency activation request to the SGSN/MME.
  • Step 906 If the terminal is in the idle state, the SGSN/MME initiates a paging request to the MTC UE, and notifies the MTC UE to establish a wireless connection.
  • Step 907 The MTC UE sends a service request to the SGSN/MME, and the SGSN/MME establishes a wireless connection with the MTC UE.
  • Step 908 The SGSN/MME sends an emergency activation request to the MTC UE in the service request response message.
  • Step 909 After the SGSN/MME activates the terminal successfully, the emergency activation response is sent to the MTC IWF, and the MTC IWF processes the emergency activation response to the MTC Server.
  • Step 910 After the emergency activation of the MTC UE is successful, an emergency bearer is established, and an emergency data communication service is performed with the MTC Server.
  • Step 911 when the delay time timer overflows, the MTC Server tries to initiate the low priority again.
  • the non-emergency activation request message related to the priority terminal or the ordinary terminal is sent to the MTC IWF.
  • Steps 912 ⁇ 916 If the MTC IWF is still in the signaling congestion, the MTC IWF will initiate a reject response again, and carry the MTC IWF congestion indication and delay time in the response message. The MTC Server waits for the next delay time to expire before attempting until the MTC IWF is normal.
  • the MTC IWF If the MTC IWF has returned to the normal state, the MTC IWF no longer rejects the activation request message, but sends the activation request message to the SGSN/MME after the processing, and the SGSN/MME carries the TAU response message in the TAU response message when the MTC UE performs the TAU process. MTC UE. And send the activation response to the MTC Server after the activation is successful.
  • the MTC Server After the MTC Server sends a non-emergency activation request message, if the MTC IWF congestion indication is not received again, the default MTC IWF congestion is removed, and the MTC IWF performs normal signaling interaction.
  • the MTC Server can send emergency or non-sense normally. Urgent terminal activation request message.
  • Step 917 After the MTC UE is successfully activated, the normal bearer is established, and the normal data communication service is performed with the MTC Server.
  • the present invention further provides a system embodiment of network congestion control, including: an MTC IWF, further comprising: a 3GPP network control plane network element or an MTC Server B, wherein the MTC IWF is used in itself When congestion occurs, the congestion is notified to the 3GPP network control plane network element or the MTC Server;
  • the 3GPP network control plane network element or the MTC server is configured to no longer send non-emergency signaling messages to the MTC IWF during MTC IWF congestion.
  • the non-emergency signaling message includes a signaling message that does not carry an emergency identifier associated with a low priority MTC UE or a normal MTC UE.
  • the 3GPP network control plane network element or the MTC server is further configured to send an emergency signaling message carrying the emergency identifier to the MTC IWF during the MTC IWF congestion.
  • the 3GPP network control plane network element or the MTC Server can also be used in the MTC IWF. After the congestion is released, a non-emergency signaling message is sent to the MTC IWF.
  • the 3GPP network control plane network element is further configured to: after receiving the congestion notification from the MTC IWF, the activation message from the MTC UE that has been received before the MTC IWF is congested, when the activation validity time expires Sending a response message of successful or failed activation of the MTC UE to the MTC IWF; the MTC IWF processes according to the local policy.
  • the MTC IWF is further configured to notify the 3GPP network control plane network element or the MTC Server of the congestion status by using the inter-device system message.
  • the inter-device system message includes a congestion start message and a congestion end message.
  • the MTC IWF is also used to notify the 3GPP network control plane network element or the MTC Server by carrying the MTC IWF congestion indication and the delay time in the signaling message related to the MTC UE.
  • the 3GPP network control plane network element or the MTC Server may be further configured to: after the end of the delay time, attempt to send a non-emergency signaling message to the MTC IWF;
  • the MTC IWF performs normal processing on the received non-emergency signaling message; if the congestion of the MTC IWF is still not cancelled, the MTC IWF rejects the received non-emergency signaling message, and Re-notifying the congestion indication and delay time to the 3GPP network control plane network element or the MTC server;
  • the MTC IWF congestion control mechanism can be implemented.
  • the MTC IWF When the MTC IWF is congested, the signaling from the 3GPP network and the MTC Server is processed as little as possible, so that the MTC IWF recovers from the congestion state to the normal state as soon as possible, and the network and the M2M service are guaranteed.
  • the robustness of the process avoids affecting the implementation of M2M services and improves the user experience as much as possible.

Landscapes

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

Abstract

本发明公开了一种网络拥塞控制的方法和系统，在机器类型通信互连功能实体（MTC IWF）出现信令拥塞时，根据拥塞机制及时通知第三代合作伙伴计划（3GPP）网络及MTC服务器，3GPP网络及MTC服务器悬挂或拒绝低优先级MTC UE或普通MTC UE的非紧急信令消息，这样既保证了紧急信令能得到及时处理，也避免了MTC IWF在拥塞期间仍接收及处理大量的信令使拥塞加剧；使MTC增强架构能有效应对大量信令流并发的场景，保障了MTC UE及时与MTC服务器进行数据通信，满足了物联网业务需求。

Description

一种网络拥塞控制的方法和系统 技术领域
本发明涉及通信技术领域， 尤其涉及一种网络拥塞控制的方法和系统。 背景技术
近年来机器到机器间的通信（ M2M, Machine to Machine )业务逐渐开 始得到应用， 如物流系统、 远程抄表、 智能家居等应用。 M2M服务商使用 现有的无线网络， 如通用分组无线业务 （GPRS , General Packet Radio Service ) 网络、 演进分组系统（EPS, Evolved Packet System ) 网络等分组 交换 ( PS , Packet Switching ) 网络开展 M2M业务。 由于 M2M业务相比人 与人之间的通信（H2H, Human to Human ) 业务有明显的差异性， 因此需 要对现有的网络进行必要的优化， 以获得最佳的网络管理与网络通讯质量。
GPRS网络是一个基于包交换的第二代移动通信网络，到了第三代移动 通信系统， GPRS演进为通用移动通信系统分组交换（UMTS PS , Universal Mobile Telecommunication System Packet Switch )域。 GPRS网络架构中包 含如下网元：
无线网络系统 （RNS , Radio Network System ), RNS 中包含节点 B ( NodeB ) 与无线网络控制器（RNC, Radio Network Controller ), NodeB 为终端提供空口连接， RNC主要用于管理无线资源以及控制 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, Machine Type Communication Server ) 为 M2M应用服务器， 用于为用户提供 M2M应用， 通过 MTCi接 口与 GGSN相连。
随着无线宽带技术的发展， 业务层对传输层的带宽、 时延等性能要求 越来越高。 为提高其网络性能， 降低网络建设及运营成本， 第三代合作伙 伴计划（ 3GPP )致力于系统架构演进 ( SAE, System Architecture Evolution ) 的研究， 目的是使得演进的分组网 （EPC, Evolved Packet Core )可提供更 高的传输速率、 更短的传输延时、 优化分组， 及支持演进的 UTRAN
( E-UTRAN, Evolved UTRAN ), UTRAN、 无线局域网 （WLAN, Wireless Local Area Network )及其他非 3GPP的接入网络之间的移动性管理。
SAE的架构中包含了无线接入网络 eNodeB,核心网控制面网元 MME、 核心网用户面网元 Serving GW/PDN GW等各类网元。 其中， 演进的无线接 入网（ E-RAN, Evolved Radio Access Network )中包含的网元是演进节点 B
( eNodeB, Evolved NodeB ), 属于 RNS系统， 用于为用户的接入提供无线 资源； 分组数据网（ PDN, Packet Data Network )是为用户提供业务的网络； EPC核心网提供了更低的延迟， 并允许更多的无线接入系统接入， 其包括 口下网元： 移动管理实体（ MME, Mobility Management Entity ), 是控制面功能实 体， 临时存储用户数据的服务器， 负责管理和存储用户设备（UE, User Equipment )的上下文（比如用户标识、移动性管理状态、用户安全参数等）， 为用户分配临时标识， 当 UE驻扎在该跟踪区域或者该网络时， 负责对该用 户进行鉴权；
服务网关 （S-GW, Serving Gateway ), 是一个用户面实体， 负责用户 面数据路由处理， 终结处于空闲（ECM_IDLE )状态的 UE的下行数据； 管 理和存储 UE的 SAE承载（ bearer )上下文， 比如 IP承载业务参数和网络 内部路由信息等； S-GW是 3GPP系统内部用户面的锚点， 一个用户在一个 时刻只能有一个 S-GW;
分组数据网网关（ P-GW, PDN Gateway ), 是负责 UE接入 PDN的网 关，分配用户 IP地址，也是 3GPP和非 3GPP接入系统的移动性锚点，P-GW 的功能还包括策略实施、 计费支持； 用户在同一时刻能够接入多个 P-GW; 策略与计费实施功能实体（ PCEF, Policy and Charging Enforcement Function ) 也位于 P-GW中；
归属用户服务器（HSS, Home Subscriber Server ), 负责永久存储用户 签约数据， HSS 存储的内容包括 UE 的国际移动用户识别码 （IMSI , International Mobile Subscriber Identification )和 P-GW的 IP地址。
在物理上， S-GW和 P-GW可以合设， EPC系统用户面网元包括 S-GW 和 P-GW。
M2M业务是以机器终端智能交互为核心的、 网络化的应用与服务， 它 采用智能机器终端， 通过无线网络传输信息， 为客户提供的信息化解决方 案， 用于满足客户对监控、 指挥调度、 数据采集和测量等方面的信息化需 求。
M2M的通信对象为机器对机器， 可以是人与机器之间的通信， 机器与 服务器之间的通信， 不同智能终端之间的通信。 不同应用的 MTC设备具有 不同的特性， 如电梯等升降机设备具有低移动性、 PS only属性， 而监视、 警报设备除具有低移动性、 PS only外， 还具有低数据传输和高可用性等属 性。 因此， 需要针对不同应用的 MTC设备进行不同的系统优化， 可有效的 对 MTC设备进行管理、 监控、 付费等。
同时， 由于 MTC设备具有无人值守的特征， 因此， 需要对 3GPP网络 进行优化，使网络具有可以激活终端的能力，这样当 MTC Server需要 MTC 设备上报数据或对其进行控制， 就可以随时触发 MTC设备与 MTC Server 建立数据通信。
根据 M2M业务需求， 需要网络实现对终端进行激活、 小数据量传输的 各类需求， 因此对 PS分组网络架构进行了增强， PS网络的 MTC增强架构 如图 1 所示， 在 PS 网络架构中引入了 MTC 互连功能实体 （IWF, Inter-Working Function )及相关接口。 图 1中， MTC Server用于为用户提供 M2M应用控制， MTC Server主要负责对 MTC设备 ( MTC UE ) 的信息采 集和数据存储 /处理等工作，并可对 MTC设备进行必要的管理； MTC Server 通过 MTCi接口与 P-GW相连。 MTC IWF网元负责进行网络拓朴隐藏及应 用层、 承载层协议转换， 采用 MTCsp接口与 MTC Server连接， 采用 S6m 接口与 HSS/HLR连接， 采用 T5a/d与 SGSN/MME连接。 现有 MTC IWF 的功能主要是接收 MTC Server的激活消息， 并通过 3GPP网络相关网元将 激活消息下发给 MTC UE。
现有 MTC网络增强的技术实现， 主要考虑采用 MTC IWF进行激活的 流程， 如图 2所示， 包括以下步驟：
步驟 201 , MTC UE在 3GPP分组域， 包括 GPRS网络与 EPS网络， 需 要向无线接入网络 RNS ( eNodeB或 RNC ) (简称 RNS, 下同）发起附着请 求， 其中携带了 MTC UE的标识（即 IMSI )、 MTC UE的网络接入能力、 请求分配 IP的指示和终端接入代理能力等信息。 若终端在线时位置改变， 发起的是位置更新 ( TAU ) 流程。
RNS为 MTC UE选择一个为之服务的 MME/SGSN ( MME或 SGSN ), 并将附着请求转发到该 MME/SGSN, 同时将附着消息中携带的相关信息也 携带给 MME/SGSN。
MME/SGSN向 MTC UE归属网的 HSS发送位置更新请求， 其中携带 MME/SGSN的地址信息和 MTC UE的标识（ IMSI ), 向 HSS告知 MTC UE 当前所接入的区域； HSS根据 MTC UE的标识（IMSI )查找出签约用户数 据， 发送给 MME/SGSN。
若终端允许接入， SGSN/MME就向该终端发送附着接入， 将该终端接 入到 3GPP网络。
步驟 202, MTC Server根据应用需求，需要对 MTC UE进行激活。 MTC Server将对 MTC UE的激活请求通过 MTCsp接口发给归属 MTC IWF, 激 活请求消息中携带激活（trigger )信息、 MTC UE标识等信息。
步驟 203, MTC IWF根据激活请求消息中的 MTC UE标识，从 HSS/HLR 中获取 MTC UE附着的 SGSN/MME的 IP地址及 MTC UE的 IMSI标识。
步驟 204, MTC IWF向 SGSN/MME发送激活终端的请求， 其中携带 trigger信息及 IMSI标识等信息。
步驟 205 , MME/SGSN根据运营商策略， 在本地先保存该激活请求， 等待 MTC UE发起 TAU流程。
步驟 206 , MTC UE向 MME/SGSN发起周期性 TAU请求或因位置改 变发起的 TAU请求。
步驟 207, SGSN/MME收到 TAU请求后， 进行承载修改等相关的位置 更新过程的处理。
步驟 208, MME/SGSN在 TAU响应的非接入层（ NAS )信令中携带该 终端的激活请求， 将激活请求消息发送给 MTC UE。
步驟 209, MTC UE将 TAU完成消息发给 SGSN/MME, 消息中携带激 活请求已接受信息。
步驟 210, MME/SGSN向 MTC IWF返回激活请求发送成功消息。 步驟 211 , MTC UE收到 MTC Server的激活请求后， 在 3GPP网络建 立用户面承载， 然后与 MTC Server通过 3GPP网络的用户面承载建立起应 用层连接， 实现业务数据的交互。
在现有的 MTC增强架构与具体的流程中， 没有考虑 MTC IWF拥塞场 景下 trigger消息如何发送、 如何响应等处理流程， 也没有考虑 MTC IWF 拥塞场景下小数据如何通过 MTC IWF进行传输、紧急消息及监控消息如何 通过 MTC IWF进行传输等问题。
MTC IWF是需要处理来自 3GPP网络与 MTC Server的大量信令，有信 令拥塞的可能。 当发生信令拥塞时， 如果仍然收到大量的信令， 程度轻的 会造成 MTC IWF与网络及 MTC Server的信令接口长时间堵塞， MTC相关 信令无法得到处理；程度重的可能造成 MTC IWF网元崩溃，造成网络故障。
因此， 针对 MTC增强架构， 需要解决 MTC IWF拥塞时， MTC IWF 如何与网络及 MTC Server进行交互、 及建立 MTC IWF的拥塞处理机制， 使得 MTC IWF在拥塞期间能尽可能少的接收与处理信令，尽快恢复正常状 态； 避免 MTC IWF长时间拥塞或系统崩溃， 使 M2M业务无法得到正常的 处理及实现， 影响 M2M用户体验。 发明内容
有鉴于此， 本发明实施例的主要目的在于提供一种网络拥塞控制的方 法和系统， 以避免 MTC IWF拥塞时仍然接收和处理大量来自接口的信令， 造成 MTC IWF最终因严重拥塞无法正常工作的问题。
为达到上述目的， 本发明实施例的技术方案是这样实现的： 本发明实施例提供了一种网络拥塞控制的方法， 该方法包括： 当机器类型通信互连功能实体 MTC IWF拥塞时， 所述 MTC IWF将拥 塞情况通知给第三代合作伙伴计划 3GPP网络控制面网元或 MTC服务器； 所述 3GPP网络控制面网元或 MTC服务器在 MTC IWF拥塞期间不再 发送非紧急信令消息给所述 MTC IWF。
该方法还包括：
在所述 MTC IWF拥塞期间， 所述 3GPP网络控制面网元或 MTC服务 器将携带紧急标识的紧急信令消息发送给所述 MTC IWF。
所述非紧急信令消息包括与低优先级 MTC UE或普通 MTC UE相关的 不携带紧急标识的信令消息。
该方法还包括：
当所述 MTC IWF的拥塞解除后， 所述 3GPP网络控制面网元或 MTC 服务器将非紧急信令消息发送给所述 MTC IWF。
该方法还包括：
所述 3GPP网络控制面网元收到来自所述 MTC IWF的拥塞情况通知 后， 对于在所述 MTC IWF拥塞前已收到的来自 MTC UE的激活消息， 在 激活有效时间到期时， 将所述 MTC UE的激活成功或失败的响应消息发送 给所述 MTC IWF; 所述 MTC IWF根据本地策略进行处理。
所述 MTC IWF 通过设备间系统消息将自身的拥塞情况通知给所述 3GPP网络控制面网元或 MTC服务器，
所述设备间系统消息包括拥塞开始消息和拥塞结束消息。
所述 MTC IWF通过在与所述 MTC UE相关的终端信令消息中携带 MTC IWF拥塞指示及延时时间， 将自身的拥塞情况通知给所述 3GPP网络 控制面网元或 MTC服务器。
该方法还包括： 所述 3GPP网络控制面网元或 MTC服务器在所述延时时间结束后， 尝 试向所述 MTC IWF发送非紧急信令消息， 若所述 MTC IWF拥塞解除， 则 对所接收的非紧急信令消息进行正常处理； 若所述 MTC IWF拥塞仍未解 除， 则所述 MTC IWF对所接收的非紧急信令消息进行拒绝处理， 并重新通 知拥塞指示和延时时间给所述 3GPP网络控制面网元或 MTC服务器。
本发明实施例还提供了一种网络拥塞控制的系统， 该系统包括： 机器 类型通信互连功能实体 MTC IWF, 还包括： 第三代合作伙伴计划 3GPP网 络控制面网元或 MTC服务器， 其中，
所述 MTC IWF,用于在自身发生拥塞时，将拥塞情况通知给所述 3GPP 网络控制面网元或 MTC服务器；
所述 3GPP网络控制面网元或 MTC服务器， 用于在 MTC IWF拥塞期 间不再发送非紧急信令消息给所述 MTC IWF。
所述 3GPP网络控制面网元或 MTC服务器还用于， 在所述 MTC IWF 拥塞期间， 将携带紧急标识的紧急信令消息发送给所述 MTC IWF。
所述非紧急信令消息包括与低优先级 MTC UE或普通 MTC UE相关的 不携带紧急标识的信令消息。
所述 3GPP网络控制面网元或 MTC服务器还用于， 在所述 MTC IWF 的拥塞解除后， 将非紧急信令消息发送给所述 MTC IWF。
所述 3GPP网络控制面网元还用于，在收到来自所述 MTC IWF的拥塞 情况通知后， 对于在所述 MTC IWF拥塞前已收到的来自 MTC UE的激活 消息， 在激活有效时间到期时， 将所述 MTC UE的激活成功或失败的响应 消息发送给所述 MTC IWF; 所述 MTC IWF根据本地策略进行处理。
所述 MTC IWF还用于，通过设备间系统消息将自身的拥塞情况通知给 所述 3GPP网络控制面网元或 MTC服务器，
所述设备间系统消息包括拥塞开始消息和拥塞结束消息。 所述 MTC IWF还用于， 通过在与 MTC UE相关的终端信令消息中携 带 MTC IWF拥塞指示及延时时间， 将自身的拥塞情况通知给所述 3GPP网 络控制面网元或 MTC服务器。
所述 3GPP网络控制面网元或 MTC服务器还用于， 在所述延时时间结 束后， 尝试向所述 MTC IWF发送非紧急信令消息；
相应的， 若所述 MTC IWF拥塞解除， 则所述 MTC IWF对所接收的非 紧急信令消息进行正常处理；若所述 MTC IWF拥塞仍未解除，则所述 MTC IWF对所接收的非紧急信令消息进行拒绝处理， 并重新通知拥塞指示和延 时时间给所述 3GPP网络控制面网元或 MTC服务器。
本发明实施例所提供的一种网络拥塞控制的方法和系统， 在 MTC IWF 出现信令拥塞时， 根据拥塞机制及时通知 3GPP网络及 MTC Server, 3GPP 网络及 MTC Server悬挂或拒绝低优先级 MTC UE或普通 MTC UE的非紧 急信令， 这样既保证了紧急信令能得到及时处理， 也避免了 MTC IWF在拥 塞期间仍接收及处理大量的信令使拥塞加剧；使 MTC增强架构能有效应对 大量信令流并发的场景，保障了 MTC UE及时与 MTC Server进行数据通信， 满足了物联网业务需求。 附图说明
图 1为现有技术中 PS网络的 MTC增强架构的示意图； 流程图；
图 3为本发明实施例一种网络拥塞控制的方法流程图；
图 4为本发明实施例在激活流程中， MTC IWF拥塞时通知 3GPP网络 中 SGSN/MME网元的流程图一；
图 5 为本发明实施例在小数据包传输流程中， MTC IWF拥塞时通知
3GPP网络中 SGSN/MME网元的流程图一； 图 6为本发明实施例在激活流程中， MTC IWF拥塞时通知 3GPP网络 中 SGSN/MME网元的流程图二；
图 7 为本发明实施例在小数据包传输流程中， MTC IWF拥塞时通知 3GPP网络中 SGSN/MME网元的流程图二；
图 8为本发明实施例在激活流程中， MTC IWF拥塞时通知 MTC Server 的流程图一；
图 9为本发明实施例在激活过程中， MTC IWF拥塞时通知 MTC Server 的流程图二。 具体实施方式
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。 本发明实施例为避免 MTC IWF拥塞时仍接收并处理大量的 MTC相关 信令造成拥塞加剧的问题， 当 MTC IWF拥塞时， MTC IWF主动将拥塞情 况通知给与之有信令交互的各相关实体， 如 3GPP 网络中的控制面网元 SGSN/MME, 负责 MTC业务控制及终端管理的 MTC Server。 SGSN/MME 或 MTC Server得知 MTC IWF已经信令拥塞， 就不再将非紧急信令消息发 送给 MTC IWF进行处理， 只发送紧急信令消息， 这样就大大减少了 MTC IWF的信令处理压力， 使 MTC IWF能够快速恢复到正常状态。
MTC IWF拥塞情况通知是比较灵活的，可采用设备间的系统消息通知， 如拥塞开始消息、 拥塞结束消息进行通知， 这需要对 MTC IWF 与 SGSN/MME交互的 T5接口、 及 MTC IWF与 MTC Server交互的 MTCsp 接口进行增强， 以支持该系统消息。 为避免增加系统消息造成接口的增强， 使系统过于复杂， 另一种方式可采用在终端相关的终端信令消息中来传递 MTC IWF拥塞标识以通知 MTC Server或 SGSN/MME , 并携带一个延时时 间， 在该延时时段内， MTC Server或 SGSN/MME需要避免将非紧急的信 令发给 MTC IWF处理。 本发明实施例所提供的一种网络拥塞控制的方法， 如图 3 所示， 主要 包括以下步驟：
步驟 301 , 当 MTC IWF拥塞时， MTC IWF将拥塞情况通知给 3GPP 网络控制面网元或 MTC Server。
步驟 302, 3GPP网络控制面网元或 MTC Server在 MTC IWF拥塞期间 不再发送非紧急信令消息给所述 MTC IWF。
在 MTC IWF拥塞期间， 3GPP网络控制面网元或 MTC Server可以将携 带紧急标识的紧急信令消息发送给 MTC IWF。
所述非紧急信令消息包括与低优先级 MTC UE或普通 MTC UE相关的 不携带紧急标识的信令消息。 所述 MTC UE的低优先级或普通 MTC UE的 属性可根据 MTC UE的实际应用需求由网络运营商进行定义和配置。
较佳的， 3GPP网络控制面网元收到来自 MTC IWF的拥塞情况通知后， 对于在 MTC IWF拥塞前已收到的来自 MTC UE的激活消息， 在激活有效 时间到期时， 将 MTC UE的激活成功或失败的响应消息发送给 MTC IWF; MTC IWF根据本地策略进行处理。
当 MTC IWF的拥塞解除后， 3GPP网络控制面网元或 MTC Server将非 紧急信令消息发送给 MTC IWF。
作为本发明的一种实现方式， MTC IWF可以通过设备间系统消息将自 身的拥塞情况通知给 3GPP网络控制面网元或 MTC Server, 所述设备间系 统消息包括拥塞开始消息和拥塞结束消息。
作为本发明的另一种实现方式， MTC IWF也可以通过在与 MTC UE相 关的终端信令消息中携带 MTC IWF拥塞指示及延时时间，将自身的拥塞情 况通知给 3GPP网络控制面网元或 MTC Server。
3GPP网络控制面网元或 MTC Server在所述延时时间结束后， 尝试向 MTC IWF发送非紧急信令消息， 若 MTC IWF拥塞解除， 则对所接收的非 紧急信令消息进行正常处理； 若 MTC IWF拥塞仍未解除， 则 MTC IWF对 所接收的非紧急信令消息进行拒绝处理， 并重新通知拥塞指示和延时时间 给 3GPP网络控制面网元或 MTC Server。
下面结合具体实施例对本发明的网络拥塞控制方法和系统进一步详细 阐述。
图 4 示出了在激活流程中， MTC IWF 拥塞时通知 3GPP 网络中 SGSN/MME网元的一种流程。图 4中， MTC IWF拥塞时， MTC IWF向 3GPP 网络的 SGSN/MME发送拥塞开始通知消息， SGSN/MME根据运营商策略， 在 MTC UE激活流程中， 对于低优先级终端或普通终端的非紧急激活响应 信令不再发送给 MTC IWF; 紧急激活响应信令在 MTC IWF拥塞期间仍可 以发送给 MTC IWF处理。 当 MTC IWF拥塞解除后， MTC IWF向 3GPP 网络的 SGSN/MME发送拥塞结束通知消息， SGSN/MME得知 MTC IWF 已解除拥塞， 就不再执行拥塞控制的限制， 可将所有激活响应信令都发给 MTC IWF进行处理。 图 4所示流程主要包括以下步驟：
步驟 401 , MTC UE向 3GPP分组网络发起附着请求， SGSN/MME收 到附着请求后从 HSS/HLR下载用户的签约数据，保存终端上下文并允许终 端进行接入到 3GPP网络， MTC UE成功附着到 3GPP网络。
步驟 402, MTC Server根据应用需求，需要对 MTC UE进行激活。 MTC Server将对 MTC UE的激活请求通过 MTCs 接口发给 MTC IWF , MTC IWF 从 HSS/HLR中获取 MTC UE附着的 SGSN/MME的 IP地址及 MTC UE的 IMSI标识， 并将该激活请求发给 SGSN/MME,激活请求中可包含激活有效 时间、 激活信息等内容。
步驟 403 , SGSN/MME收到激活请求后， 可临时进行保存， 并根据激 活有效时间启动激活定时器， 当 MTC UE发起 TAU时将激活信息下发给 MTC UE。 若激活成功就向 MTC IWF上报激活成功响应。 若当激活定时器 溢出时仍不能成功激活 MTC UE, 就上报激活失败消息给 MTC IWF, 由 MTC IWF将激活响应消息发给 MTC Server。
步驟 404, MTC IWF出现了信令拥塞。 信令拥塞是可以进行预先设定 的， 如 MTC IWF处理资源不足 30%, 可定义为信令拥塞。
步驟 405 , MTC IWF 向 SGSN/MME 发送拥塞开始消息， 通知 SGSN/MME有关 MTC IWF的拥塞状况。
步驟 406, SGSN/MME收到拥塞开始消息后， 就执行拥塞控制的限制 措施， 根据运营商策略， 对于低优先级终端或普通终端的相关不携带紧急 标识的非紧急 MTC激活响应信令， 不再发送给 MTC IWF进行处理， 可以 将未能发送的信令消息在 SGSN/MME进行暂存或拒绝。
对于紧急激活的响应， 响应消息可以是紧急激活成功或紧急激活失败 的消息， 该消息携带紧急标识， SGSN/MME可直接发给 MTC IWF进行处 理， 不受拥塞控制的限制。 MTC IWF将该紧急激活响应发给 MTC Server。
步驟 407 (包括 407a、 407b ), 对于 MTC IWF未拥塞前， 某些终端的 激活消息已经发给 SGSN/MME的情况， 当激活有效时间到期时，根据运营 商策略， SGSN/MME 可以将该终端的激活成功或失败的响应消息发送给 MTC IWF, 由 MTC IWF根据策略决定是否将激活响应消息发给 MTC Server
步驟 408, 拥塞解除时， MTC IWF向 SGSN/MME发送拥塞结束消息， 通知 SGSN/MME拥塞已解除。
步驟 409, SGSN/MME得知 MTC IWF拥塞已解除，就正常与 MTC IWF 进行信令交互， 将待发的非紧急激活响应消息， 包括低优先级终端及普通 终端相关的激活响应消息发给 MTC IWF, MTC IWF处理后将激活响应消 息发给 MTC Server。
图 5示出了在小数据包传输流程中， MTC IWF拥塞时通知 3GPP网络 中 SGSN/MME网元的一种流程。 在图 5中， MTC IWF拥塞时， MTC IWF 向 3GPP网络的 SGSN/MME发送拥塞开始通知消息， SGSN/MME根据运 营商策略， 在小数据包发送流程中， 对于包含低优先级终端或普通终端的 'J、数据包的非紧急信令消息不再发送给 MTC IWF; 对于紧急 ' j、数据包的信 令在 MTC IWF拥塞期间仍可以发送给 MTC IWF处理。 当 MTC IWF拥塞 解除后， MTC IWF向 3GPP网络的 SGSN/MME发送拥塞结束通知消息， SGSN/MME得知 MTC IWF已解除拥塞， 就不再执行拥塞控制的限制， 可 将所有包含小数据包的信令消息都发给 MTC IWF进行处理。图 5所示的流 程主要包括以下步驟：
步驟 501 , MTC UE向 3GPP分组网络发起附着请求， SGSN/MME收 到附着请求后从 HSS/HLR下载用户的签约数据，保存终端上下文并允许终 端进行接入到 3GPP网络， MTC UE成功附着到 3GPP网络。
步驟 502, MTC IWF出现了信令拥塞。 信令拥塞是可以进行预先设定 的， 如 MTC IWF处理资源不足 30%, 可定义为信令拥塞。
步驟 503 , MTC IWF 向 SGSN/MME 发送拥塞开始消息， 通知 SGSN/MME有关 MTC IWF的拥塞状况。
SGSN/MME收到拥塞开始消息后， 就执行拥塞控制的限制措施， 根据 运营商策略， 对于低优先级终端或普通终端相关的不携带紧急标识的包含 小数据包的非紧急信令消息， 不再发送给 MTC IWF进行处理， 可以将未能 发送的包含小数据包的信令在 SGSN/MME进行拒绝处理。
步驟 504, MTC UE将携带小数据包的 NAS信令发给 SGSN/MME。 步驟 505 , 如果是紧急小数据包， 在 NAS 信令中携带紧急标识通知 SGSN/MME。
对于包含紧急小数据包的信令消息， 该信令消息可携带紧急标识， SGSN/MME可直接将该信令发给 MTC IWF进行处理， 不受拥塞控制的限 制。 MTC IWF将该 d、数据包发给 MTC Server。
步驟 506,对于低优先级终端相关或普通终端相关的包含小数据包的非 紧急 NAS信令， 根据运营商策略， 当 SGSN/MME得知 MTC IWF拥塞后， 就会响应 NAS信令拒绝消息，在拒绝消息中携带延时接入时间及 MTC IWF 拥塞的原因值给 MTC UE。 MTC UE得知 MTC IWF拥塞后 , 与 MTC IWF 相关的 NAS信令在延时接入时间周期内不再发起， 等延时接入时间到期后 再尝试进行发起包含小数据包的 NAS信令。
步驟 505和 506的执行不分先后， 根据对 MTC UE发送的携带小数据 包的 NAS信令的判断结果决定执行步驟 505或 506。
步驟 507 , 拥塞解除时， MTC IWF向 SGSN/MME发送拥塞结束消息， 通知 SGSN/MME拥塞已解除。
步驟 508, 当 MTC UE有小数据包要发送时， MTC UE将携带小数据 包的 NAS信令发给 SGSN/MME;或是当延时接入时间到期后，先前的 MTC UE又一次尝试发起包含小数据包的 NAS信令。
步驟 509, SGSN/MME得知 MTC IWF拥塞已解除，就正常与 MTC IWF 进行信令交互， 将待发的包含小数据包的信令消息， 无论是低优先级终端 还是普通终端相关的信令消息都发给 MTC IWF, MTC IWF处理后将小数 据包发给 MTC Server。
图 6 示出了在激活流程中， MTC IWF 拥塞时通知 3GPP 网络中 SGSN/MME网元的另一种流程。 在图 6中， MTC IWF拥塞时， MTC IWF 拒绝 3GPP 网络的 SGSN/MME发送的激活响应消息， 在拒绝消息中携带 MTC IWF拥塞指示及延时时间。 SGSN/MME根据运营商策略，在 MTC UE 激活流程中， 对于低优先级终端或普通终端的激活响应信令不再发送给 MTC IWF; 紧急激活响应信令在 MTC IWF拥塞期间仍可以发送给 MTC IWF处理。 当延时时间结束后 , SGSN/MME尝试向 MTC IWF再次发起低优先级 终端或普通终端的非紧急激活响应信令，如果 MTC IWF已恢复正常， 就可 以正常处理信令， 若 SGSN/MME未再次收到携带 MTC IWF拥塞指示的拒 绝消息， 就默认 MTC IWF恢复正常， 不再执行拥塞控制的限制， 可将所有 激活响应信令都发给 MTC IWF进行处理； 如果 MTC IWF仍处于拥塞， 则 再次在拒绝消息中携带 MTC IWF拥塞指示及延时时间， SGSN/MME等下 一次延时时间结束后再尝试发送激活响应消息， 直至 MTC IWF恢复正常。
图 6所示的流程主要包括以下步驟：
步驟 601 , MTC UE向 3GPP分组网络发起附着请求， SGSN/MME收 到附着请求后从 HSS/HLR下载用户的签约数据，保存终端上下文并允许终 端进行接入到 3GPP网络， MTC UE成功附着到 3GPP网络。
步驟 602, MTC Server根据应用需求，需要对 MTC UE进行激活。 MTC Server将对 MTC UE的激活请求通过 MTCs 接口发给 MTC IWF , MTC IWF 从 HSS/HLR中获取 MTC UE附着的 SGSN/MME的 IP地址及 MTC UE的 IMSI标识， 并将该激活请求发给 SGSN/MME,激活请求中可包含激活有效 时间、 激活信息等内容。
步驟 603 , SGSN/MME收到激活请求后， 可临时进行保存， 并根据激 活有效时间启动激活定时器， 当 MTC UE发起 TAU时将激活信息下发给 MTC UE。 若激活成功就向 MTC IWF上报激活成功响应。 若当激活定时器 溢出时仍不能成功激活 MTC UE, 就上报激活失败消息给 MTC IWF, 由 MTC IWF将激活响应消息发给 MTC Server。
步驟 604, MTC IWF出现了信令拥塞。 信令拥塞是可以进行预先设定 的， 如 MTC IWF处理资源不足 30%, 可定义为信令拥塞。
步驟 605, SGSN/MME收到 MTC UE的激活响应消息后， 或是激活定 时器溢出还未能激活 MTC UE, SGSN/MME向 MTC IWF发送低优先级终 端或普通终端相关的不携带紧急标识的非紧急激活响应消息。
步驟 606, MTC IWF判断自身已信令拥塞， 就不再处理该信令消息， 直接发起拒绝响应给 SGSN/MME, 在响应消息中携带 MTC IWF拥塞指示 及延时时间。
SGSN/MME收到携带有 MTC IWF拥塞指示的拒绝响应后， 就执行拥 塞控制的限制措施， 根据运营商策略， 对于低优先级终端或普通终端的相 关的非紧急 MTC激活响应信令， 不再发送给 MTC IWF进行处理， 可以将 未能发送的信令消息在 SGSN/MME进行暂存或拒绝。并启动延时时间定时 器， 当定时器溢出时再执行发送激活响应的尝试。
步驟 607,对于紧急激活的响应， 响应消息可以是紧急激活成功或紧急 激活失败的消息， 该消息可携带紧急标识， SGSN/MME可直接发给 MTC IWF进行处理， 不受拥塞控制的限制。 MTC IWF将该紧急激活响应发给 MTC Server。
步驟 608 (包括 608a、 608b ),对于 MTC IWF未拥塞前， 某些 MTC UE 的激活消息已经发给 SGSN/MME的情况， 当激活定时器溢出时时， 根据运 营商策略， SGSN/MME可以将该 MTC UE的激活成功或失败消息发送给 MTC IWF, 由 MTC IWF根据策略决定是否将激活响应消息发给 MTC Server
步驟 609 (包括 609a、 609b ), 当延时时间定时器溢出后， SGSN/MME 再次尝试发起低优先级终端或普通终端相关的激活响应消息给 MTC IWF。
步驟 610 (包括 610a、 610b ),若 MTC IWF还处于信令拥塞， MTC IWF 会再次发起拒绝响应， 并在响应消息中携带 MTC IWF拥塞指示及延时时 间， 对应步驟 610a。 SGSN/MME等待下一次延时时间到期后再进行尝试， 直至 MTC IWF正常。
若 MTC IWF已恢复正常状态， MTC IWF不再拒绝该激活响应消息， 而是处理后将激活响应消息发给 MTC Server, 对应步驟 610b。
SGSN/MME发出激活响应消息后， 没有再次收到携带 MTC IWF拥塞 的拒绝响应， 就默认 MTC IWF拥塞已解除， 就正常与 MTC IWF进行信令 交互， SGSN/MME将待发的激活响应消息， 包括低优先级终端及普通终端 相关的激活响应消息发给 MTC IWF, MTC IWF处理后将激活响应消息发 给 MTC Server。
图 7示出了在小数据包传输流程中， MTC IWF拥塞时通知 3GPP网络 中 SGSN/MME网元的另一种流程。在图 7中， MTC IWF拥塞时， MTC IWF 拒绝 3GPP网络的 SGSN/MME发送的小数据包传输的非紧急信令消息， 在 拒绝消息中携带 MTC IWF拥塞指示及延时时间。 SGSN/MME根据运营商 策略， 在小数据包发送流程中， 对于包含低优先级终端或普通终端的小数 据包的非紧急信令消息不再发送给 MTC IWF; 对于紧急小数据包的信令消 息在 MTC IWF拥塞期间仍可以发送给 MTC IWF处理。
当延时时间结束后， SGSN/MME尝试向 MTC IWF再次发起包含低优 先级终端或普通终端的小数据包的非紧急信令消息，如果 MTC IWF已恢复 正常， 就可以正常处理该信令消息， 若 SGSN/MME未再次收到携带 MTC IWF拥塞指示的拒绝消息，就默认 MTC IWF恢复正常， 不再执行拥塞控制 的限制，可将所有小数据包传输信令都发给 MTC IWF进行处理；如果 MTC IWF仍处于拥塞， 则再次在拒绝消息中携带 MTC IWF拥塞指示及延时时 间， SGSN/MME等下一次延时时间结束后再尝试发送小数据包传输消息， 直至 MTC IWF恢复正常。
图 7所示的流程主要包括以下步驟：
步驟 701 , MTC UE向 3GPP分组网络发起附着请求， SGSN/MME收 到附着请求后从 HSS/HLR下载用户的签约数据，保存终端上下文并允许终 端进行接入到 3GPP网络， MTC UE成功附着到 3GPP网络。 步驟 702, MTC IWF出现了信令拥塞。 信令拥塞是可以进行预先设定 的， 如 MTC IWF处理资源不足 30%, 可定义为信令拥塞。
步驟 703 , MTC UE将携带小数据包的 NAS信令发给 SGSN/MME。 若 是紧急小数据包， 在 NAS信令中携带紧急标识。
步驟 704, SGSN/MME将小数据包传输消息发给 MTC IWF,携带 MTC UE标识及紧急标识等信息。
步驟 705, MTC IWF判断自身已信令拥塞， 就不再处理该非紧急的小 数据包传输信令消息， 直接发起拒绝响应， 在响应消息中携带 MTC IWF拥 塞指示及延时时间。
SGSN/MME收到携带有 MTC IWF拥塞指示的拒绝响应后， 就执行拥 塞控制的限制措施， 根据运营商策略， 对于低优先级终端或普通终端相关 的包含小数据包的非紧急信令消息， 不再发送给 MTC IWF进行处理， 可以 将未能发送的包含小数据包的信令在 SGSN/MME进行拒绝处理。并启动延 时时间定时器， 当定时器溢出时再执行发送激活响应的尝试。
步驟 706, 如果是紧急小数据包， 可以在 NAS信令中携带紧急标识通 知 SGSN/MME。
对于包含紧急小数据包的信令消息， 该信令消息可携带紧急标识， SGSN/MME可直接将该信令发给 MTC IWF进行处理， 不受拥塞控制的限 制。 MTC IWF将该 '〗、数据包发给 MTC Server。
步驟 707,对于低优先级终端相关或普通终端相关的包含小数据包的非 紧急 NAS信令， 根据运营商策略， 当 SGSN/MME得知 MTC IWF拥塞后， 就会响应 NAS信令拒绝消息， 在拒绝消息中携带延时时间及 MTC IWF拥 塞的原因值给 MTC UE。 MTC UE得知 MTC IWF拥塞后 , 与 MTC IWF相 关的 NAS信令在延时接入时间周期内不再发起， 等延时接入时间到期后再 尝试进行发起包含小数据包的 NAS信令。 步驟 708, 当 MTC UE有小数据包要发送时， MTC UE将携带小数据 包的 NAS信令发给 SGSN/MME;或是当延时接入时间到期后，先前的 MTC UE又一次尝试发起包含小数据包的 NAS信令。
步驟 709 (包括 709a、 709b ), 当 SGSN/MME侧的延时时间定时器溢 出后， SGSN/MME再次尝试发起低优先级终端或普通终端相关的小数据包 传输消息给 MTC IWF。
步驟 710 (包括 710a、 710b ),若 MTC IWF还处于信令拥塞， MTC IWF 会再次发起拒绝响应， 并在响应消息中携带 MTC IWF拥塞指示及延时时 间， 对应步驟 710a。 SGSN/MME等待下一次延时时间到期后再进行尝试， 直至 MTC IWF正常。
若 MTC IWF已恢复正常状态， MTC IWF不再拒绝该小数据包传输消 息， 而是处理后将小数据包传输消息发给 MTC Server, 对应步驟 710b。
SGSN/MME发出小数据包传输信令消息后， 没有再次收到携带 MTC IWF拥塞的拒绝响应， 就默认 MTC IWF拥塞已解除， 正常与 MTC IWF进 行信令交互， SGSN/MME将后续的小数据包传输消息， 包括低优先级终端 及普通终端相关的小数据包传输消息发给 MTC IWF, MTC IWF处理后将 'J、数据包消息发给 MTC Server。
图 8示出了在激活流程中， MTC IWF拥塞时通知 MTC Server的一种 流程。 在图 8中， MTC IWF拥塞时， MTC IWF向 MTC Server发送拥塞开 始通知消息 , 在 MTC UE激活流程中 , MTC Server对于低优先级终端或普 通终端的非紧急激活请求信令不再发送给 MTC IWF; 紧急激活请求信令在 MTC IWF拥塞期间仍可以发送给 MTC IWF处理。 当 MTC IWF拥塞解除 后， MTC IWF向 MTC Server发送拥塞结束通知消息， MTC Server得知 MTC IWF已解除拥塞， 就不再执行拥塞控制的限制， 可将所有激活请求信 令都发给 MTC IWF进行处理。 图 8所示的流程主要包括以下步驟：
步驟 801 , MTC UE向 3GPP分组网络发起附着请求， SGSN/MME收 到附着请求后从 HSS/HLR下载用户的签约数据，保存终端上下文并允许终 端进行接入到 3GPP网络， MTC UE成功附着到 3GPP网络。
步驟 802, MTC IWF出现了信令拥塞。 信令拥塞是可以进行预先设定 的， 如 MTC IWF处理资源不足 30%, 可定义为信令拥塞。
步驟 803 , MTC IWF向 MTC Server发送拥塞开始消息， 通知 MTC Server有关 MTC IWF的拥塞状况。
步驟 804, MTC Server收到拥塞开始消息后， 就执行拥塞控制的限制 措施， 对于低优先级终端或普通终端的非紧急激活请求信令， 就不再发送 给 MTC IWF进行处理。
MTC Server根据应用需求， 需要对 MTC UE进行激活。 MTC Server 将对 MTC UE的激活请求通过 MTCsp接口发给 MTC IWF。 对于紧急激活 请求， 该激活请求消息携带紧急标识， MTC Server直接发给 MTC IWF进 行处理，不受拥塞控制的限制。 MTC IWF将紧急激活请求发给 SGSN/MME。
步驟 805 , 若 MTC UE处于空闲（ idle )状态， SGSN/MME向 MTC UE 发起寻呼 （ paging )请求， 通知 MTC UE建立无线连接。
步驟 806, MTC UE向 SGSN/MME发送业务请求（ service request ), SGSN/MME与 MTC UE建立起无线连接。
步驟 807, SGSN/MME在业务请求响应消息中， 将紧急激活请求发给 MTC UE。
步驟 808, SGSN/MME激活终端成功后， 将紧急激活响应发给 MTC IWF , MTC IWF处理后将紧急激活响应发给 MTC Server。
步驟 809, MTC UE紧急激活成功后， 建立紧急承载， 与 MTC Server 进行紧急数据通信业务。 步驟 810, MTC IWF恢复正常后， 向 MTC Server发送拥塞结束消息， 通知 MTC Server拥塞已解除。
步驟 811~814, MTC Server得知 MTC IWF拥塞已解除，就正常与 MTC IWF进行信令交互， 将待发的激活请求消息， 包括低优先级终端及普通终 端相关的非紧急激活请求消息发给 MTC IWF, MTC IWF处理后将激活请 求消息发给 SGSN/MME, 由 SGSN/MME在 TAU响应消息中交付给 MTC UE。
步驟 815, MTC UE正常激活成功后， 建立普通承载， 与 MTC Server 进行正常数据通信业务。
图 9示出了在激活流程中， MTC IWF拥塞时通知 MTC Server的另一 种流程。 在图 9中， MTC IWF拥塞时， MTC IWF拒绝 MTC Server发送的 非紧急激活请求消息，在拒绝消息中携带 MTC IWF拥塞指示及延时时间通 知给 MTC Server。在 MTC UE激活流程中， MTC Server对于低优先级终端 或普通终端的非紧急激活请求信令不再发送给 MTC IWF; 紧急激活响应信 令在 MTC IWF拥塞期间仍可以发送给 MTC IWF处理。
当延时时间结束后， MTC Server尝试向 MTC IWF再次发起低优先级 终端或普通终端的非紧急激活响应信令，如果 MTC IWF已恢复正常， 就可 以正常处理信令， 若 MTC Server未再次收到携带 MTC IWF拥塞指示的拒 绝消息， 就默认 MTC IWF恢复正常， 不再执行拥塞控制的限制， 可将所有 激活请求信令都发给 MTC IWF进行处理； 如果 MTC IWF仍处于拥塞， 则 再次在拒绝消息中携带 MTC IWF拥塞指示及延时时间， MTC Server等下 一次延时时间结束后再尝试发送激活请求消息， 直至 MTC IWF恢复正常。
图 9所示的流程主要包括以下步驟：
步驟 901 , MTC UE向 3GPP分组网络发起附着请求， SGSN/MME收 到附着请求后从 HSS/HLR下载用户的签约数据，保存终端上下文并允许终 端进行接入到 3GPP网络， MTC UE成功附着到 3GPP网络。
步驟 902, MTC IWF出现了信令拥塞。 信令拥塞是可以进行预先设定 的， 如 MTC IWF处理资源不足 30%, 可定义为信令拥塞。
步驟 903 , MTC Server根据应用需求，需要对 MTC UE进行激活。 MTC Server将对 MTC UE的激活请求通过 MTCsp接口发给 MTC IWF。
步驟 904, MTC IWF判断自身已信令拥塞， 就不再处理该激活请求信 令消息， 直接发起拒绝响应，在响应消息中携带 MTC IWF拥塞指示及延时 时间给 MTC Server。 MTC Server收到携带有 MTC IWF拥塞指示的拒绝响 应后， 就执行拥塞控制的限制措施， 对于低优先级终端或普通终端的非紧 急 MTC激活请求信令， 就不再发送给 MTC IWF进行处理。 并启动延时时 间定时器， 当定时器溢出时再执行发送非紧急激活请求的尝试。
步驟 905 , 对于紧急激活请求， 该激活请求消息携带紧急标识， MTC Server直接发给 MTC IWF进行处理， 不受拥塞控制的限制。 MTC IWF将 紧急激活请求发给 SGSN/MME。
步驟 906, 若终端处于 idle状态， SGSN/MME向 MTC UE发起 paging 请求， 通知 MTC UE建立无线连接。
步驟 907, MTC UE向 SGSN/MME发送 service request, SGSN/MME 与 MTC UE建立起无线连接。
步驟 908, SGSN/MME在业务请求响应消息中， 将紧急激活请求发给 MTC UE。
步驟 909, SGSN/MME激活终端成功后， 将紧急激活响应发给 MTC IWF, MTC IWF处理后将紧急激活响应发给 MTC Server。
步驟 910, MTC UE紧急激活成功后， 建立紧急承载， 与 MTC Server 进行紧急数据通信业务。
步驟 911 , 当延时时间定时器溢出后， MTC Server再次尝试发起低优 先级终端或普通终端相关的非紧急激活请求消息给 MTC IWF。
步驟 912~916, 若 MTC IWF还处于信令拥塞， MTC IWF会再次发起 拒绝响应， 并在响应消息中携带 MTC IWF拥塞指示及延时时间。 MTC Server等待下一次延时时间到期后再进行尝试， 直至 MTC IWF正常。
若 MTC IWF已恢复正常状态， MTC IWF不再拒绝该激活请求消息， 而是处理后将激活请求消息发给 SGSN/MME, 由 SGSN/MME在 MTC UE 进行 TAU过程时在 TAU响应消息中携带给 MTC UE。 并在激活成功后将 激活响应发给 MTC Server。
MTC Server发出非紧急激活请求消息后， 若没有再次收到携带 MTC IWF拥塞指示的拒绝响应，就默认 MTC IWF拥塞已解除，正常与 MTC IWF 进行信令交互， MTC Server后续可正常发送紧急或非紧急的终端激活请求 消息。
步驟 917, MTC UE正常激活成功后， 建立普通承载， 与 MTC Server 进行正常数据通信业务。
对应上述网络拥塞控制的方法， 本发明还提供了一种网络拥塞控制的 系统实施例 ,包括： MTC IWF,还包括： 3GPP网络控制面网元或 MTC ServerB 其中， MTC IWF, 用于在自身发生拥塞时， 将拥塞情况通知给 3GPP 网络控制面网元或 MTC Server;
3GPP网络控制面网元或 MTC Server, 用于在 MTC IWF拥塞期间不再 发送非紧急信令消息给 MTC IWF。
所述非紧急信令消息包括与低优先级 MTC UE或普通 MTC UE相关的 不携带紧急标识的信令消息。
较佳的 , 3GPP网络控制面网元或 MTC Server还可用于 , 在 MTC IWF 拥塞期间， 将携带紧急标识的紧急信令消息发送给所述 MTC IWF。
较佳的， 3GPP网络控制面网元或 MTC Server还可用于， 在 MTC IWF 的拥塞解除后， 将非紧急信令消息发送给 MTC IWF。
较佳的， 3GPP网络控制面网元还可用于， 在收到来自 MTC IWF的拥 塞情况通知后， 对于在 MTC IWF拥塞前已收到的来自 MTC UE的激活消 息， 在激活有效时间到期时， 将 MTC UE的激活成功或失败的响应消息发 送给 MTC IWF; MTC IWF根据本地策略进行处理。
较佳的， MTC IWF还可用于， 通过设备间系统消息将自身的拥塞情况 通知给 3GPP网络控制面网元或 MTC Server,
所述设备间系统消息包括拥塞开始消息和拥塞结束消息。
MTC IWF还用于 ,通过在与 MTC UE相关的信令消息中携带 MTC IWF 拥塞指示及延时时间， 将自身的拥塞情况通知给 3GPP 网络控制面网元或 MTC Server。
3GPP网络控制面网元或 MTC Server还可用于， 在所述延时时间结束 后， 尝试向 MTC IWF发送非紧急信令消息；
相应的， 若 MTC IWF拥塞解除， 则 MTC IWF对所接收的非紧急信令 消息进行正常处理； 若 MTC IWF拥塞仍未解除， 则 MTC IWF对所接收的 非紧急信令消息进行拒绝处理， 并重新通知拥塞指示和延时时间给 3GPP 网络控制面网元或 MTC服务器；
上述操作循环进行， 直至 MTC IWF解除拥塞。
根据上述实施例， 可以实现 MTC IWF拥塞控制机制， 当 MTC IWF拥 塞时， 尽量少的处理来自 3GPP网络及 MTC Server的信令， 使 MTC IWF 尽快从拥塞状态恢复到正常状态，保障网络及 M2M业务流程的健壮性，避 免影响 M2M业务实现， 尽可能提高用户体验。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种网络拥塞控制的方法， 该方法包括：
当机器类型通信互连功能实体 MTC IWF拥塞时， 所述 MTC IWF将 拥塞情况通知给第三代合作伙伴计划 3GPP网络控制面网元或 MTC服务 器；
所述 3GPP网络控制面网元或 MTC服务器在 MTC IWF拥塞期间不 再发送非紧急信令消息给所述 MTC IWF。
2、根据权利要求 1所述网络拥塞控制的方法， 其中， 该方法还包括： 在所述 MTC IWF拥塞期间， 所述 3GPP网络控制面网元或 MTC服 务器将携带紧急标识的紧急信令消息发送给所述 MTC IWF。
3、 根据权利要求 1所述网络拥塞控制的方法， 其中， 所述非紧急信 令消息包括与低优先级 MTC UE或普通 MTC UE相关的不携带紧急标识 的信令消息。
4、根据权利要求 1所述网络拥塞控制的方法， 其中， 该方法还包括： 当所述 MTC IWF的拥塞解除后，所述 3GPP网络控制面网元或 MTC 服务器将非紧急信令消息发送给所述 MTC IWF。
5、根据权利要求 1所述网络拥塞控制的方法， 其中， 该方法还包括： 所述 3GPP网络控制面网元收到来自所述 MTC IWF的拥塞情况通知 后， 对于在所述 MTC IWF拥塞前已收到的来自 MTC UE的激活消息， 在激活有效时间到期时， 将所述 MTC UE的激活成功或失败的响应消息 发送给所述 MTC IWF; 所述 MTC IWF根据本地策略进行处理。
6、 根据权利要求 1至 5任一项所述网络拥塞控制的方法， 其中， 所 述 MTC IWF通过设备间系统消息将自身的拥塞情况通知给所述 3GPP网 络控制面网元或 MTC服务器，
所述设备间系统消息包括拥塞开始消息和拥塞结束消息。
7、 根据权利要求 1至 5任一项所述网络拥塞控制的方法， 其中， 所 述 MTC IWF通过在与所述 MTC UE相关的终端信令消息中携带 MTC IWF拥塞指示及延时时间， 将自身的拥塞情况通知给所述 3GPP 网络控 制面网元或 MTC服务器。
8、根据权利要求 7所述网络拥塞控制的方法， 其中， 该方法还包括： 所述 3GPP网络控制面网元或 MTC服务器在所述延时时间结束后， 尝试向所述 MTC IWF发送非紧急信令消息，若所述 MTC IWF拥塞解除， 则对所接收的非紧急信令消息进行正常处理；若所述 MTC IWF拥塞仍未 解除， 则所述 MTC IWF对所接收的非紧急信令消息进行拒绝处理， 并重 新通知拥塞指示和延时时间给所述 3GPP 网络控制面网元或 MTC服务 器。
9、 一种网络拥塞控制的系统， 该系统包括： 机器类型通信互连功能 实体 MTC IWF, 还包括： 第三代合作伙伴计划 3GPP网络控制面网元或 MTC服务器， 其中，
所述 MTC IWF, 用于在自身发生拥塞时， 将拥塞情况通知给所述 3GPP网络控制面网元或 MTC服务器；
所述 3GPP网络控制面网元或 MTC服务器， 用于在 MTC IWF拥塞 期间不再发送非紧急信令消息给所述 MTC IWF。
10、 根据权利要求 9所述网络拥塞控制的系统， 其中， 所述 3GPP网 络控制面网元或 MTC服务器还用于， 在所述 MTC IWF拥塞期间， 将携 带紧急标识的紧急信令消息发送给所述 MTC IWF。
11、根据权利要求 9所述网络拥塞控制的系统， 其中， 所述非紧急信 令消息包括与低优先级 MTC UE或普通 MTC UE相关的不携带紧急标识 的信令消息。
12、 根据权利要求 9所述网络拥塞控制的系统， 其中， 所述 3GPP网 络控制面网元或 MTC服务器还用于， 在所述 MTC IWF的拥塞解除后， 将非紧急信令消息发送给所述 MTC IWF。
13、 根据权利要求 9所述网络拥塞控制的系统， 其中， 所述 3GPP网 络控制面网元还用于，在收到来自所述 MTC IWF的拥塞情况通知后，对 于在所述 MTC IWF拥塞前已收到的来自 MTC UE的激活消息， 在激活 有效时间到期时， 将所述 MTC UE的激活成功或失败的响应消息发送给 所述 MTC IWF; 所述 MTC IWF根据本地策略进行处理。
14、 根据权利要求 9至 13任一项所述网络拥塞控制的系统， 其中， 所述 MTC IWF还用于，通过设备间系统消息将自身的拥塞情况通知给所 述 3GPP网络控制面网元或 MTC服务器，
所述设备间系统消息包括拥塞开始消息和拥塞结束消息。
15、 根据权利要求 9至 13任一项所述网络拥塞控制的系统， 其中， 所述 MTC IWF还用于， 通过在与 MTC UE相关的终端信令消息中携带 MTC IWF拥塞指示及延时时间， 将自身的拥塞情况通知给所述 3GPP网 络控制面网元或 MTC服务器。
16、 根据权利要求 15所述网络拥塞控制的系统， 其中，
所述 3GPP网络控制面网元或 MTC服务器还用于， 在所述延时时间 结束后， 尝试向所述 MTC IWF发送非紧急信令消息；
相应的， 若所述 MTC IWF拥塞解除， 则所述 MTC IWF对所接收的 非紧急信令消息进行正常处理； 若所述 MTC IWF拥塞仍未解除， 则所述 MTC IWF对所接收的非紧急信令消息进行拒绝处理， 并重新通知拥塞指 示和延时时间给所述 3GPP网络控制面网元或 MTC服务器。
PCT/CN2012/083825 2011-11-04 2012-10-31 一种网络拥塞控制的方法和系统 WO2013064067A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110344949.X 2011-11-04
CN201110344949XA CN103096376A (zh) 2011-11-04 2011-11-04 一种网络拥塞控制的方法和系统

Publications (1)

Publication Number Publication Date
WO2013064067A1 true WO2013064067A1 (zh) 2013-05-10

Family

ID=48191335

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/083825 WO2013064067A1 (zh) 2011-11-04 2012-10-31 一种网络拥塞控制的方法和系统

Country Status (2)

Country Link
CN (1) CN103096376A (zh)
WO (1) WO2013064067A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104185214B (zh) * 2013-05-24 2019-01-11 华为终端有限公司 一种发送上行信令的方法和设备
CN104684021B (zh) * 2013-11-29 2020-01-14 中兴通讯股份有限公司 一种建立nas连接的方法、系统及无线接入网节点
CN108809550A (zh) * 2017-04-26 2018-11-13 华为技术有限公司 异常数据传输方法、装置和系统
CN107819823A (zh) * 2017-09-26 2018-03-20 深圳市诚壹科技有限公司 一种信息处理方法、服务器及计算机可读存储介质
CN110351828B (zh) * 2018-04-04 2021-02-09 华为技术有限公司 一种定位方法及装置
KR20220033012A (ko) * 2020-09-08 2022-03-15 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 rrc 연결 재개 절차를 위한 타이머 제어를 위한 방법 및 장치

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101977416A (zh) * 2010-05-19 2011-02-16 中兴通讯股份有限公司 一种mtc设备的过载控制方法和系统
CN102170662A (zh) * 2011-05-28 2011-08-31 西安电子科技大学 物联网过载控制方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101977416A (zh) * 2010-05-19 2011-02-16 中兴通讯股份有限公司 一种mtc设备的过载控制方法和系统
CN102170662A (zh) * 2011-05-28 2011-08-31 西安电子科技大学 物联网过载控制方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HTC. LOAD/OVERLOAD CONTROL VIA MTC-IWF, 3GPP SA WG2 MEETING #87, 10 September 2011 (2011-09-10), pages 2 - 114523 *

Also Published As

Publication number Publication date
CN103096376A (zh) 2013-05-08

Similar Documents

Publication Publication Date Title
US8879413B2 (en) Method and system for controlling access of machine type communications devices
US9077723B2 (en) Method, mobile management unit and gateway for restricting MTC device to access and communicate
WO2011054299A1 (zh) 机器类通讯终端信息的获取方法和系统
EP4002954A1 (en) Reliable data delivery over non-access stratum
US9942088B2 (en) Fault detection method, gateway, user equipment, and communications system
WO2013064067A1 (zh) 一种网络拥塞控制的方法和系统
WO2011134329A1 (zh) 一种小数据包传输的方法和系统
WO2011054300A1 (zh) Mtc终端的接入控制方法和系统
JP2015511409A5 (zh)
WO2011050689A1 (zh) 机器类通讯终端的接入控制方法和系统
KR20130031265A (ko) 혼잡/과부하 제어 방법 및 장치
WO2011127710A1 (zh) 控制机器类型通信设备接入网络的方法及系统
WO2012110002A1 (zh) 一种接入控制的方法及装置
WO2012083789A1 (zh) 资源分配处理方法、装置和网络服务系统
WO2014101228A1 (zh) 无线网络的能力开放系统、网关、代理和方法
WO2012174943A1 (zh) 一种确定终端状态的方法、装置和系统
WO2012109951A1 (zh) 一种共享网络的接入控制方法和系统
WO2011160308A1 (zh) 网络拥塞处理方法、网络设备和网络系统
WO2012159283A1 (zh) 重复接入检测和限制的方法、装置、用户设备和系统
KR102387582B1 (ko) 무선 통신 시스템에서 pdn 연결 관리 방법 및 장치
WO2011050688A1 (zh) 机器类通讯终端信息的获取方法和系统
WO2010051696A1 (zh) 一种无线资源释放的方法和系统
WO2012100664A1 (zh) 一种激活终端的方法和系统
WO2013097503A1 (zh) 拥塞控制方法和设备
WO2016101285A1 (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: 12845464

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

Country of ref document: EP

Kind code of ref document: A1