WO2013097337A1 - 一种网络拥塞控制方法及系统 - Google Patents

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

Info

Publication number
WO2013097337A1
WO2013097337A1 PCT/CN2012/071607 CN2012071607W WO2013097337A1 WO 2013097337 A1 WO2013097337 A1 WO 2013097337A1 CN 2012071607 W CN2012071607 W CN 2012071607W WO 2013097337 A1 WO2013097337 A1 WO 2013097337A1
Authority
WO
WIPO (PCT)
Prior art keywords
iwf
trigger message
mobility management
management unit
signaling
Prior art date
Application number
PCT/CN2012/071607
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 WO2013097337A1 publication Critical patent/WO2013097337A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/06Access restriction performed under specific conditions based on traffic conditions

Definitions

  • the present invention relates to machine type communication (MTC) in the field of mobile communications, and in particular, to a network congestion control method and system.
  • MTC machine type communication
  • FIG. 1 is a schematic structural diagram of a cellular wireless communication system.
  • a cellular wireless communication system is mainly composed of a core network (CN, Core Network), an access network (RAN, Radio Access Network), and a terminal.
  • the core network is responsible for non-access stratum transactions, such as terminal location update, radio resource management, etc., and is an anchor point of the user plane; the access network includes base stations, or base stations, and base station control, and the base stations can be based on actual conditions.
  • a user equipment UE, User Equipment refers to various devices that can communicate with a cellular wireless communication network, such as a mobile phone, a notebook computer, and the like.
  • a mobility management unit (such as a Mobility Management Entity (MME) or a Serving GPRS Support Node (SGSN)) is a unit in the core network responsible for managing terminal access control, location information update, and handover. Control of non-access stratum signaling from the core network to the terminal and registration of the terminal to the network.
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • the Home Subscriber Server (HSS) or the Home Location Register (HLR) is an entity in the core network that is responsible for storing information such as identity information, authentication information, and authorization information of the terminal.
  • the HSS or HLR can be used to store the identity information of the user and the binding information of the user and the terminal, or only the identity information of the user (the binding information of the user and the terminal is saved by the gateway), or directly save the identity information of the terminal.
  • HSS or The HLR is also responsible for the user's subscription database, as well as the user's authentication and authorization.
  • the service platform can query user or terminal information from the HSS or HLR.
  • the MTC Inter-working Function is a connected entity between the mobile communication network and the external public network. It can implement functions such as protocol conversion, address query, and information storage.
  • the interoperability function entity is connected to the application server, and the peer can be connected to the HSS/HLR, or the MME/SGSN.
  • the MTC server is required to trigger the terminal to establish a connection with the MTC server to report the required data. Then, after receiving the trigger message of the MTC server, the terminal receives the trigger message. You need to be able to respond immediately and establish a connection to the MTC server.
  • the existing solution is to send a trigger message to the HSS through the MTC server, and then query the MME or SGSN of the serving terminal through the HSS, and send a trigger message to the MME or the SGSN, and then pass the non-access.
  • the layer signaling is sent to the terminal, and the terminal establishes a connection with the MTC server according to the trigger message.
  • the network resources may be insufficient, and the network may not process the signaling or data sent by the terminal in time to form network congestion.
  • the MME or the SGSN rejects the uplink access request of the terminal, but does not restrict the downlink signaling from being sent to the terminal.
  • the terminal immediately responds to the trigger message, sends a receiving acknowledgement signaling to the network, or further requests to establish a connection with the MTC server, and triggers the message on the premise of network congestion. The response will further worsen the congestion of the current network. Summary of the invention
  • the main purpose of the present invention is to provide a network congestion control method and system, which implements effective control of a trigger message by signaling interaction between network entities, and ensures that the current network congestion state is no longer deteriorated.
  • the present invention provides a network congestion control method, including:
  • the mobility management unit When the network is congested, the mobility management unit sends load control signaling or trigger message rejection signaling to the interoperation function entity (IWF);
  • IWF interoperation function entity
  • the IWF After receiving the load control signaling or the trigger message rejection signaling, the IWF stops sending the trigger message to the mobility management unit.
  • the mobility management unit when the network is congested, the mobility management unit sends the load control signaling to the IWF:
  • the mobility management unit When network congestion occurs, the mobility management unit sends load control signaling to the IWF, which carries the load status of the current network in a congested state.
  • the stopping sending a trigger message to the mobility management unit is:
  • the IWF After receiving the load control signaling sent by the mobility management unit, the IWF reads the load status. When the current network is congested, the IWF stops sending the trigger message to the mobility management unit.
  • the mobility management unit when the network is congested, the mobility management unit sends a trigger message rejection signal to the IWF:
  • the mobility management unit sends a trigger message to the IWF after receiving the trigger message sent by the IWF, where the reason for the rejection is carried.
  • the stopping sending a trigger message to the mobility management unit is:
  • the IWF After receiving the trigger message rejection signaling sent by the mobility management unit, the IWF reads the reason for the rejection.
  • the reason for the rejection is that when the current network is congested, the sending of the trigger message to the mobility management unit is stopped.
  • the method further includes: after receiving the load control signaling or the trigger message rejection signaling, the IWF instructs the machine type communication (MTC) server to reduce the transmission of the trigger message by sending the control signaling.
  • MTC machine type communication
  • the method further includes: The IWF saves the unsent trigger message and saves the identifier or address of the mobility management unit where network congestion occurs, and the trigger message received from the MTC server after the identity or address of the mobility management unit is saved.
  • the method further includes: deleting, by the IWF, the locally saved valid time-to-time trigger message, and sending a trigger message to the MTC server to send the report signaling.
  • the method further includes:
  • the mobility management unit After the network congestion is removed, the mobility management unit sends the load control release signaling to the IWF, where the load state of the current network is not congested;
  • the IWF After receiving the load control release signaling, the IWF resumes sending a trigger message to the mobility management unit.
  • the method further includes: deleting, by the IWF, the identifier or address of the mobility management unit in the locally saved congestion mobility management unit list.
  • the method further includes: after receiving the load control solution signaling of the mobility management unit, the IWF instructs the MTC server to resume sending all the trigger messages by sending control signaling.
  • the method further includes: after the IWF stops sending the trigger message to the mobility management unit, sending the trigger message to send to the MTC server, indicating that the trigger message is sent and the reason for the failure is sent.
  • the present invention also provides a network congestion control system, including: a mobility management unit, an IWF;
  • a mobility management unit configured to send load control signaling or trigger message rejection signaling to the IWF when the network is congested
  • the IWF after receiving the load control signaling or triggering the message rejection signaling, stops sending the trigger message to the mobility management unit.
  • the IWF is further configured to save the trigger message, and the identifier or address of the mobility management unit that sends the load control signaling or the trigger message rejection signaling.
  • the IWF is further configured to: after receiving the load control signaling, instruct the MTC server to reduce the sending of the trigger message by sending control signaling.
  • the IWF is further configured to delete a locally saved valid time-out trigger message, and send a trigger message to the MTC server to send report signaling.
  • the mobility management unit is further configured to: after the network congestion is removed, send a load control release signaling to the IWF, where the current state is not congested;
  • the IWF is further configured to: after receiving the load control release signaling, resume sending a trigger message to the mobility management unit.
  • the IWF is further configured to delete the identifier or address of the mobility management unit in the locally saved congestion mobility management unit list.
  • the IWF is further configured to: after receiving the load control release signaling of the mobility management unit, instruct the MTC server to resume sending all the trigger messages by sending control signaling.
  • the IWF is further configured to stop sending a trigger message to the mobility management unit, and send a trigger message to send to the MTC server, indicating that the trigger message is sent and the reason for the failure is sent.
  • the network congestion control method and system provided by the present invention, when the network is congested, the mobility management unit sends the load control signaling or the trigger message rejection signaling to the IWF; after the IWF receives the load control signaling or the trigger message rejection signaling, The sending of the trigger message to the mobility management unit is stopped.
  • the present invention implements effective control of the trigger message by signaling interaction between the network entities, and ensures that the congestion state of the current network is no longer deteriorated.
  • FIG. 1 is a schematic structural diagram of a cellular wireless communication system
  • FIG. 2 is a schematic flow chart of a method for implementing network congestion control according to the present invention.
  • FIG. 3 is a schematic flowchart of Embodiment 1 of a method for implementing network congestion control according to the present invention
  • 4 is a schematic flowchart of Embodiment 2 of a method for implementing network congestion control according to the present invention
  • FIG. 5 is a schematic flowchart of Embodiment 3 of a method for implementing network congestion control according to the present invention
  • FIG. 6 is a fourth embodiment of a method for implementing network congestion control according to the present invention
  • FIG. 7 is a schematic structural diagram of a network congestion control system according to the present invention. detailed description
  • the basic idea of the present invention is: when the network is congested, the mobility management unit sends the load control signaling or the trigger message rejection signaling to the IWF; after receiving the load control signaling or the trigger message rejection signaling, the IWF stops sending the trigger message. Give the mobility management unit.
  • FIG. 2 is a schematic flowchart of a network congestion control method according to the present invention. As shown in FIG. 2, the method includes the following steps:
  • Step 201 When the network is congested, the mobility management unit sends load control signaling or trigger message rejection signaling to the IWF;
  • the mobility management unit is an MME or an SGSN;
  • the mobility management unit When the network is congested, the mobility management unit actively sends the load control signaling to the IWF; or, after the network is congested, the mobility management unit does not actively send the load control signaling to the IWF, but sends the trigger message sent by the IWF.
  • the trigger message rejects the signaling to the IWF and indicates in the signaling that the reason for the rejection is network congestion.
  • Step 202 After receiving the load control signaling or the trigger message rejection signaling, the IWF stops sending the trigger message to the mobility management unit.
  • Embodiment 3 is a schematic flowchart of Embodiment 1 of a method for implementing network congestion control according to the present invention.
  • the mobility management unit is an MME, and when the network is congested, the MME sends load control signaling to the IWF, as shown in FIG.
  • the method specifically includes the following steps:
  • Step 301 The network operator configures a load threshold for the MME. Specifically, the network operator configures a load threshold for the MME according to the running capability of the MME, such as how many users can handle the connection request at the same time, and the load threshold must be smaller than the maximum number of users that can be processed simultaneously.
  • Step 302 When it is determined that the network congestion occurs according to the load threshold, the MME sends the load control signaling to the IWF, where the bearer carries a load status indicating that the current network is in a congested state;
  • the MME when the number of currently processed users reaches the load threshold, the MME considers that the current network is in a congested state, and the MME sends load control signaling to the IWF, where the load control signaling carries a load status, and the value of the load status is set to 1 , indicating that the current network is in a congested state.
  • Step 303 The IWF stops sending a trigger message to the MME when determining that the network is congested according to the load status.
  • the IWF After receiving the load control signaling sent by the MME, the IWF reads the load status. If the value of the load status in the load control signaling is 1, indicating that the network is congested on the current network, the trigger message is stopped. MME.
  • Step 304 The IWF saves the unsent trigger message, and the identifier or address of the MME where the network is congested, and saves the trigger message received from the MTC server according to the identifier or address of the MME.
  • the IWF saves the local unsent trigger message, and also saves the identifier or address of the MME where the network congestion occurs to the local congestion MME list; the new trigger message is sent by the MTC server.
  • the IWF sends the identifier of the terminal to which the trigger message belongs to the HSS.
  • the HSS queries the identifier or address of the serving MME of the terminal, and sends the identifier or address of the MME to the IWF.
  • the IWF sends the identifier or address of the MME sent by the HSS to the local device.
  • the identifier or the address of the MME stored in the MME list is compared. If the identifier or address of the MME is found, the IWF saves the trigger message and does not send the trigger message to the MME.
  • step 305 and step 306 are further included: Step 305: After receiving the load control signaling, the IWF instructs the MTC server to reduce the sending of the trigger message by sending control signaling.
  • the IWF may further send control signaling to the MTC server, where the control signaling carries a control factor, and sets a control factor to a decimal between 0-1, Instructing the MTC server to reduce the trigger message sent to the IWF according to the percentage indicated by the control factor. For example, if the control factor is set to 0.5, the MTC server only sends 50% of the trigger message to the IWF, and the control factor is set to 0.3, then the MTC server only sends 30.
  • the % trigger message is sent to the IWF, that is, the MTC server can only send a trigger message indicating the percentage of the control factor.
  • Step 306 The IWF deletes the locally saved valid time-to-time trigger message, and sends a trigger message to the MTC server to send report signaling.
  • the IWF deletes the locally saved trigger message after the valid time expires. And sending a trigger message to the MTC server to send the report signaling, where the signaling carries the terminal identifier, the sending status, and the reason.
  • the terminal identifier is the terminal identifier to which the trigger message belongs, and the terminal identifier is initially sent by the MTC server in the trigger message.
  • IWF; The send status is set to 0, indicating that the trigger message failed to be sent, and the reason is set to "network congestion".
  • Step 307 After the network congestion is removed, the MME sends a load control release signaling to the IWF, where the load state indicating that the current network is not congested is carried;
  • the MME sends the load control release signaling to the IWF, where the load control release signaling carries a load status, which is used to indicate whether the current network is congested, and when set to 1, the current network is in a congested state, and is set. When 0, it indicates that the current network is not congested.
  • Step 308 after receiving the load control cancellation signaling sent by the MME, the IWF resumes sending a trigger message to the MME; Specifically, after receiving the load control cancellation signaling sent by the MME, the IWF sends the saved trigger message of the MME to the MME; if there is a new trigger message that needs to be sent to the MME, the trigger message is sent to the MME.
  • Step 309 The IWF deletes the identifier or address of the MME in the locally saved congestion MME list.
  • step 310 may be further included:
  • Step 310 After receiving the load control cancellation signaling of the MME, the IWF instructs the MTC server to resume sending all the trigger messages by sending control signaling.
  • the IWF after receiving the load control cancellation signaling of the MME, the IWF sends control signaling to the MTC server, where the control signaling carries a control factor, and the control factor is set to 1, that is, the MTC server is allowed to resume sending all the trigger messages. To the IWF.
  • the mobility management unit is an SGSN.
  • the SGSN sends load control signaling to the IWF, as shown in FIG.
  • the method specifically includes the following steps:
  • Step 401 The network operator configures a load threshold for the SGSN.
  • the network operator configures a load threshold for the SGSN according to the running capability of the SGSN, such as how many user connection requests can be processed simultaneously, and the load threshold must be smaller than the maximum number of users that can be processed simultaneously.
  • Step 402 When it is determined that the network congestion occurs according to the load threshold, the SGSN sends the load control signaling to the IWF, where the bearer carries a load status indicating that the current network is in a congested state;
  • the SGSN when the number of currently processed users reaches the load threshold, the SGSN considers that the current network is in a congested state, and the SGSN sends load control signaling to the IWF, where the load control signaling carries a load status, and the value of the load status is set to 1 , indicating that the current network is in a congested state.
  • Step 403 the IWF stops determining to send when the current network is congested according to the load status. Trigger a message to the SGSN;
  • the IWF After receiving the load control signaling sent by the SGSN, the IWF reads the load status. If the value of the load status in the load control signaling is 1, indicating that the network is congested on the current network, the trigger message is stopped. SGSN.
  • Step 404 The IWF saves the unsent trigger message, and the identifier or address of the SGSN where the network is congested, and saves the trigger message received from the MTC server according to the identifier or address of the SGSN.
  • the IWF saves the local unsent trigger message, and also saves the identifier or address of the SGSN where the network congestion occurs to the local congestion SGSN list; a new trigger message is sent by the MTC server.
  • the IWF sends the identifier of the terminal to which the trigger message belongs to the HSS.
  • the HSS queries the identifier or address of the serving SGSN of the terminal, and sends the identifier or address of the SGSN to the IWF.
  • the IWF sends the identifier or address of the SGSN sent by the HSS to the local device.
  • the identifier or address of the SGSN saved in the SGSN list is compared. If the identifier or address of the matching SGSN is found, the IWF saves the trigger message and does not send the trigger message to the SGSN.
  • step 405 and step 406 are further included:
  • Step 405 After receiving the load control signaling, the IWF instructs the MTC server to reduce the sending of the trigger message by sending control signaling.
  • the IWF may further send control signaling to the MTC server, where the control signaling carries a control factor, and sets the control factor to a decimal between 0-1, Instructing the MTC server to reduce the trigger message sent to the IWF according to the percentage indicated by the control factor. For example, if the control factor is set to 0.5, the MTC server only sends 50% of the trigger message to the IWF, and the control factor is set to 0.3, then the MTC server only sends 30. The % trigger message is sent to the IWF, that is, the MTC server can only send a trigger message indicating the percentage of the control factor. Step 406: The IWF deletes the locally saved valid time-to-time trigger message, and sends a trigger message to the MTC server to send report signaling.
  • the IWF deletes the locally saved trigger message after the valid time expires. And sending a trigger message to the MTC server to send the report signaling, where the signaling carries the terminal identifier, the sending status, and the reason.
  • the terminal identifier is the terminal identifier to which the trigger message belongs, and the terminal identifier is initially sent by the MTC server in the trigger message.
  • IWF; The send status is set to 0, indicating that the trigger message failed to be sent, and the reason is set to "network congestion".
  • Step 407 After the network congestion is removed, the SGSN sends a load control release signaling to the IWF, where the load state indicating that the current network is not congested is carried;
  • the SGSN sends the load control release signaling to the IWF, where the load control release signaling carries a load status, which is used to indicate whether the current network is congested, and when set to 1, the current network is in a congested state, and is set. When 0, it indicates that the current network is not congested.
  • Step 408 After receiving the load control cancellation signaling sent by the SGSN, the IWF resumes sending the trigger message to the SGSN.
  • the IWF after receiving the load control cancellation signaling sent by the SGSN, the IWF sends the saved trigger message of the SGSN to the SGSN; if there is a new trigger message that needs to be sent to the SGSN, the trigger message is sent to the SGSN. SGSN.
  • Step 409 The IWF deletes the identifier or address of the SGSN in the locally saved congestion SGSN list.
  • step 410 is further included:
  • Step 410 After receiving the load control cancellation signaling of the SGSN, the IWF instructs the MTC server to resume sending all the trigger messages by sending control signaling.
  • the IWF after receiving the load control cancellation signaling of the SGSN, the IWF sends the control signaling.
  • the control signaling carries a control factor, and the control factor is set to 1, that is, the MTC server is allowed to resume sending all the trigger messages to the IWF.
  • the mobility management unit is an MME or an SGSN, and the mobility management unit does not actively send load control signaling to the IWF, but After receiving the trigger message sent by the IWF, the sending trigger message rejects the signaling to the IWF, and indicates that the reason for the rejection is network congestion in the signaling.
  • the method specifically includes the following steps:
  • Step 501 The network operator configures a load threshold for the mobility management unit.
  • the network operator configures a load threshold for the mobility management unit according to the running capability of the mobility management unit, such as how many user connection requests can be processed simultaneously, and the load threshold must be smaller than the maximum that can be processed simultaneously. User number.
  • Step 502 When it is determined that the network congestion occurs according to the load threshold, the mobility management unit sends a trigger message to the IWF after receiving the trigger message sent by the IWF, where the reason for the rejection is carried;
  • the mobility management unit when the number of currently processed users reaches the load threshold, the mobility management unit considers that the current network is in a congested state, and if the mobility management unit receives the trigger message sent by the IWF, sends a trigger message reject signaling to the IWF; The reason for the rejection is carried in the signaling, and the reason for the rejection is network congestion.
  • Step 503 The IWF stops sending the trigger message to the mobility management unit when determining that the current network is congested according to the reason for the rejection;
  • the IWF After receiving the trigger message rejection signaling sent by the mobility management unit, the IWF reads the reason for the rejection. If the reason for the rejection is network congestion, that is, the current network is congested, the sending of the trigger message to the mobility management unit is stopped. .
  • Step 504 the IWF saves the trigger message that failed to be sent, and the mobility of network congestion occurs.
  • the IWF saves the local unsent trigger message, and also saves the identifier or address of the mobility management unit where the network congestion occurs to the local congestion mobility management unit list;
  • the IWF sends the identifier of the terminal to which the trigger message belongs to the HSS, and the HSS queries the identifier or address of the service mobility management unit of the terminal, and sends the identifier or address of the mobility management unit.
  • the IWF compares the identity or address of the mobility management unit sent by the HSS with the identity or address of the mobility management unit saved in the local congestion MME list, and if the identity or address of the matching mobility management unit is found, the IWF The trigger message is saved and the trigger message is not sent to the mobility management unit.
  • step 505 and step 506 are further included:
  • Step 505 After receiving the trigger message rejection signaling, the IWF instructs the MTC server to reduce the sending of the trigger message by sending control signaling.
  • the IWF may further send control signaling to the MTC server, where the control signaling carries a control factor, and the control factor is set to be between 0 and 1.
  • the decimal is used to instruct the MTC server to reduce the trigger message sent to the IWF according to the percentage indicated by the control factor. For example, if the control factor is set to 0.5, the MTC server sends only 50% of the trigger message to the IWF, and the control factor is set to 0.3. Then, the MTC server sends only 30% of the trigger message to the IWF, that is, the MTC server can only send a percentage of the trigger message indicated by the control factor.
  • Step 506 The IWF deletes the locally saved valid time-to-time trigger message, and sends a trigger message to the MTC server to send report signaling.
  • the IWF deletes the locally saved trigger message, and sends a trigger message to the MTC server to send report signaling, where the signaling carries the terminal identifier, the sending status, and the reason.
  • the terminal identifier is the terminal to which the trigger message belongs.
  • the identifier is sent by the MTC server to the IWF in the trigger message.
  • the sending status is set to 0, indicating that the triggering message is sent, and the reason is set to "network congestion".
  • Step 507 After the network congestion is removed, the mobility management unit sends the load control release signaling to the IWF, where the bearer carries a load status indicating that the current network is not congested;
  • the mobility management unit sends the load control release signaling to the IWF, where the load control release signaling carries a load status, which is used to indicate whether the current network is congested, and when set to 1, the current network is in congestion. Status, set to 0, indicates that the current network is not congested.
  • Step 508 After receiving the load control release signaling sent by the mobility management unit, the IWF resumes sending a trigger message to the mobility management unit.
  • the IWF after receiving the load control release signaling sent by the mobility management unit, the IWF sends the saved trigger message of the mobility management unit to the mobility management unit; if there is a new need to be sent to the mobility management unit The trigger message is sent to the mobility management unit.
  • Step 509 The IWF deletes the identifier or address of the mobility management unit in the locally saved congestion mobility management unit list.
  • step 510 is further included:
  • Step 510 After receiving the load control cancellation signaling of the mobility management unit, the IWF instructs the MTC server to resume sending all the trigger messages by sending control signaling.
  • the IWF after receiving the load control cancellation signaling of the mobility management unit, the IWF sends control signaling to the MTC server, where the control signaling carries a control factor, and the control factor is set to 1, that is, the MTC server is allowed to resume sending all Trigger a message to the IWF.
  • the control signaling carries a control factor
  • the control factor is set to 1
  • the MTC server is allowed to resume sending all Trigger a message to the IWF.
  • FIG. 6 is a schematic flowchart of Embodiment 4 of a method for implementing network congestion control according to the present invention.
  • the mobility management unit is an MME or an SGSN, and the mobility management unit does not actively send load control signaling to the IWF, but After receiving the trigger message sent by the IWF, the sending trigger message rejects the signaling to the IWF, and indicates that the reason for the rejection is network congestion in the signaling.
  • the method specifically includes the following steps:
  • Step 601 The network operator configures a load threshold for the mobility management unit.
  • the network operator configures a load threshold for the mobility management unit according to the running capability of the mobility management unit, such as how many user connection requests can be processed simultaneously, and the load threshold must be smaller than the maximum that can be processed simultaneously. User number.
  • Step 602 After determining that the network congestion occurs according to the load threshold, the mobility management unit sends a trigger message to the IWF after receiving the trigger message sent by the IWF, where the reason for the rejection is carried;
  • the mobility management unit when the number of currently processed users reaches the load threshold, the mobility management unit considers that the current network is in a congested state, and if the mobility management unit receives the trigger message sent by the IWF, sends a trigger message reject signaling to the IWF; The reason for the rejection is carried in the signaling, and the reason for the rejection is network congestion.
  • Step 603 The IWF stops sending the trigger message to the mobility management unit when determining that the current network is congested according to the reason for the rejection;
  • the IWF After receiving the trigger message rejection signaling sent by the mobility management unit, the IWF reads the reason for the rejection. If the reason for the rejection is network congestion, that is, the current network is congested, the sending of the trigger message to the mobility management unit is stopped. .
  • Step 604 After stopping sending the trigger message to the mobility management unit, the IWF sends a trigger message to send to the MTC server, indicating the reason why the trigger message is sent and the transmission fails.
  • the trigger message is sent.
  • Sending a report to the server the trigger message sending report carries at least the following content: The trigger message sending status and the reason, wherein the trigger message sending status is a failure, the reason is network congestion; the trigger message sending report is used to indicate that the MTC server triggers the message sending failure. And the reason for the failure to send.
  • FIG. 7 is a schematic structural diagram of a network congestion control system according to the present invention.
  • the system includes: a mobility management unit 71, an IWF 72; ,
  • the mobility management unit 71 is configured to send load control signaling or trigger message rejection signaling to the IWF 72 when the network is congested;
  • the IWF 72 is configured to stop sending a trigger message to the mobility management unit 71 after receiving the load control signaling or the trigger message rejection signaling.
  • the IWF 72 is further configured to save the trigger message, and an identifier or address of a mobility management unit that sends load control signaling or trigger message rejection signaling.
  • the IWF 72 is further configured to: after receiving the load control signaling, instruct the MTC server to reduce the sending of the trigger message by sending control signaling.
  • the IWF 72 is further configured to delete a locally saved valid time-out trigger message, and send a trigger message to the MTC server to send report signaling.
  • the mobility management unit 71 is further configured to: after the network congestion is removed, send the load control release signaling to the IWF 72, where the load state of the current network is not congested;
  • the IWF 72 is further configured to resume sending a trigger message to the mobility management unit 71 after receiving the load control release signaling.
  • the IWF 72 is further configured to delete the identifier or address of the mobility management unit in the locally saved congestion mobility management unit list.
  • the IWF 72 is further configured to: after receiving the load control release signaling of the mobility management unit, instruct the MTC server to resume sending all the trigger messages by sending control signaling.
  • the IWF 73 is further configured to: after stopping sending the trigger message to the mobility management unit, send a trigger message to send to the MTC server, indicating that the trigger message is sent and the reason for the transmission failure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开一种网络拥塞控制方法及系统,该方法包括:网络拥塞时,移动性管理单元发送负载控制信令或触发消息拒绝信令给操作功能实体(IWF);所述IWF接收到负载控制信令或触发消息拒绝信令后,停止发送触发消息给所述移动性管理单元。根据本发明的技术方案,通过网络实体间的信令交互,实现对触发消息的有效控制,保证当前网络的拥塞状态不再恶化。

Description

一种网络拥塞控制方法及系统 技术领域
本发明涉及移动通信领域的机器类型通信 ( MTC , Machine Type Communication ), 尤其涉及一种网络拥塞控制方法及系统。 背景技术
图 1是蜂窝无线通信系统的结构示意图, 如图 1所示, 蜂窝无线通信 系统主要由核心网 (CN, Core Network ), 接入网 (RAN, Radio Access Network )和终端组成。 其中, 核心网负责非接入层的事务, 如终端位置更 新、 无线资源的管理等, 并且是用户面的锚点; 接入网包括基站、 或基站 以及基站控制, 基站之间可以根据实际情况存在物理或逻辑上的连接, 如 图 1中的基站 1与基站 2或基站 1与基站 3之间的连接, 每个基站可以与 一个或多个核心网节点连接。 终端即用户设备(UE, User Equipment ), 指 的是可以与蜂窝无线通信网络进行通信的各种设备, 如移动电话、 笔记本 电脑等。
移动性管理单元(如移动管理实体( MME, Mobility Management Entity ) 或 GPRS服务节点( SGSN, Serving GPRS Support Node ) )是核心网中负责 管理终端接入控制、 位置信息更新、 以及切换的单元, 负责核心网到终端 的非接入层信令的控制和将终端注册到网络。
归属用户服务器(HSS, Home Subscriber Server )或归属用户位置寄存 器( HLR, Home Location Register )是核心网中负责保存终端的身份信息、 认证信息和授权信息等信息的实体。 根据不同情况, HSS或 HLR可用于保 存用户的身份信息及用户和终端的绑定信息,或只保存用户的身份信息(由 网关保存用户和终端的绑定信息), 或直接保存终端的身份信息。 HSS 或 HLR还负责用户的签约数据库, 以及执行用户的身份验证和授权等。 业务 平台可从 HSS或 HLR查询用户或终端信息。
MTC互操作功能实体( IWF, Inter-working Function )是在移动通信网 和外部公网之间的一个连接实体, 能够实现协议转换、 地址查询、 信息保 存等功能。 互操作功能实体对外连接应用服务器, 对内可以连接到 HSS/HLR, 或 MME/SGSN。
通常有某些业务, 如监控管理系统需要向监控终端获取监控数据, 需 要通过 MTC服务器触发终端建立与 MTC服务器的连接, 用来上报需要的 数据; 那么终端在接收到 MTC服务器的触发消息后, 就需要能立即响应, 建立与 MTC服务器的连接。目前为了满足 MTC服务器对终端的触发需求, 已有解决方案是通过 MTC服务器发送触发消息到 HSS, 然后通过 HSS查 询服务终端的 MME或 SGSN, 将触发消息发送到 MME或 SGSN, 然后通 过非接入层信令发送到终端, 终端根据触发消息建立与 MTC服务器的连 接。 这种解决方案中, 同时接入网络的终端较多时, 可能会导致网络资源 不足, 从而造成网络不能及时处理终端发送的信令或数据, 形成网络拥塞。 在现有技术中, 网络拥塞发生时, MME或 SGSN会拒绝终端的上行接入请 求, 但是不会限制下行信令发送到终端。 然而, 当网络发送触发消息到终 端后, 终端会立即响应该触发消息, 向网络发送接收确认信令, 或会更进 一步请求建立与 MTC服务器的连接, 在网络拥塞的前提下, 对触发消息的 响应会进一步恶化当前网络的拥塞情况。 发明内容
有鉴于此, 本发明的主要目的在于提供一种网络拥塞控制方法及系统, 通过网络实体间的信令交互, 实现对触发消息的有效控制, 保证当前网络 的拥塞状态不再恶化。
为达到上述目的, 本发明的技术方案是这样实现的: 本发明提供一种网络拥塞控制方法, 包括:
网络拥塞时, 移动性管理单元发送负载控制信令或触发消息拒绝信令 给互操作功能实体(IWF );
所述 IWF接收到负载控制信令或触发消息拒绝信令后 , 停止发送触发 消息给所述移动性管理单元。
上述方法中, 所述网络拥塞时, 移动性管理单元发送负载控制信令给 IWF为:
发生网络拥塞时, 移动性管理单元发送负载控制信令给 IWF, 其中携 带当前网络处于拥塞状态的负载状态。
上述方法中, 所述停止发送触发消息给所述移动性管理单元为:
IWF接收到移动性管理单元发送的负载控制信令后, 读取其中的负载 状态, 负载状态是当前网络发生网络拥塞时, 停止发送触发消息到移动性 管理单元。
上述方法中, 所述网络拥塞时, 移动性管理单元发送触发消息拒绝信 令给 IWF为:
发生网络拥塞时, 移动性管理单元接收到 IWF发送的触发消息后, 发 送触发消息拒绝信令给 IWF, 其中携带拒绝原因。
上述方法中, 所述停止发送触发消息给所述移动性管理单元为:
IWF接收到移动性管理单元发送的触发消息拒绝信令后, 读取其中的 拒绝原因, 拒绝原因是当前网络发生拥塞时, 停止发送触发消息到移动性 管理单元。
上述方法中, 该方法还包括: IWF 收到负载控制信令或触发消息拒绝 信令后, 通过发送控制信令指示机器类型通信(MTC )服务器减少触发消 息的发送。
上述方法中, 该方法还包括: IWF保存未发送的触发消息, 并保存发生网络拥塞的移动性管理单元 的标识或地址,根据该移动性管理单元的标识或地址保存之后从 MTC服务 器收到的触发消息。
上述方法中, 该方法还包括: IWF删除本地保存的有效时间到时的触 发消息, 并向 MTC服务器发送触发消息发送报告信令。
上述方法中, 该方法还包括:
网络拥塞解除后, 移动性管理单元发送负载控制解除信令给 IWF, 其 中携带当前网络不拥塞的负载状态;
所述 IWF接收到负载控制解除信令后, 恢复发送触发消息给所述移动 性管理单元。
上述方法中, 该方法还包括: IWF在本地保存的拥塞移动性管理单元 列表中删除该移动性管理单元的标识或地址。
上述方法中, 该方法还包括: IWF 收到移动性管理单元的负载控制解 除信令后, 通过发送控制信令指示 MTC服务器恢复发送所有的触发消息。
上述方法中, 该方法还包括: IWF停止发送触发消息到移动性管理单 元后, 发送触发消息发送报告给 MTC服务器, 指示触发消息发送失败和发 送失败的原因。
本发明还提供一种网络拥塞控制系统, 包括: 移动性管理单元、 IWF; 其中,
移动性管理单元, 用于网络拥塞时, 发送负载控制信令或触发消息拒 绝信令给 IWF;
IWF, 用于接收到负载控制信令或触发消息拒绝信令后,停止发送触发 消息给所述移动性管理单元。
上述系统中, 所述 IWF, 还用于保存所述触发消息、 以及发送负载控 制信令或触发消息拒绝信令的移动性管理单元的标识或地址。 上述系统中, 所述 IWF, 还用于收到负载控制信令后, 通过发送控制 信令指示 MTC服务器减少触发消息的发送。
上述系统中, 所述 IWF, 还用于删除本地保存的有效时间到时的触发 消息, 并向 MTC服务器发送触发消息发送报告信令。
上述系统中,
所述移动性管理单元, 还用于网络拥塞解除后, 发送负载控制解除信 令给 IWF, 其中携带当前网络不拥塞的负载状态;
所述 IWF, 还用于接收到负载控制解除信令后, 恢复发送触发消息给 所述移动性管理单元。
上述系统中, 所述 IWF, 还用于在本地保存的拥塞移动性管理单元列 表中删除该移动性管理单元的标识或地址。
上述系统中, 所述 IWF, 还用于收到移动性管理单元的负载控制解除 信令后 , 通过发送控制信令指示 MTC服务器恢复发送所有的触发消息。
上述系统中, 所述 IWF, 还用于停止发送触发消息到移动性管理单元 后, 发送触发消息发送报告给 MTC服务器, 指示触发消息发送失败和发送 失败的原因。
本发明提供的网络拥塞控制方法及系统, 网络拥塞时, 移动性管理单 元发送负载控制信令或触发消息拒绝信令给 IWF; 所述 IWF接收到负载控 制信令或触发消息拒绝信令后 , 停止发送触发消息给所述移动性管理单元 , 本发明通过网络实体间的信令交互, 实现对触发消息的有效控制, 保证当 前网络的拥塞状态不再恶化。 附图说明
图 1是蜂窝无线通信系统的结构示意图;
图 2是本发明实现网络拥塞控制方法的流程示意图;
图 3是本发明实现网络拥塞控制方法的实施例一的流程示意图; 图 4是本发明实现网络拥塞控制方法的实施例二的流程示意图; 图 5是本发明实现网络拥塞控制方法的实施例三的流程示意图; 图 6是本发明实现网络拥塞控制方法的实施例四的流程示意图; 图 7是本发明实现网络拥塞控制系统的结构示意图。 具体实施方式
本发明的基本思想是: 网络拥塞时, 移动性管理单元发送负载控制信 令或触发消息拒绝信令给 IWF; 所述 IWF接收到负载控制信令或触发消息 拒绝信令后, 停止发送触发消息给所述移动性管理单元。
下面通过附图及具体实施例对本发明再做进一步的详细说明。
本发明提供一种网络拥塞控制方法, 图 2是本发明实现网络拥塞控制 方法的流程示意图, 如图 2所示, 该方法包括以下步驟:
步驟 201 , 网络拥塞时, 移动性管理单元发送负载控制信令或触发消息 拒绝信令给 IWF;
具体的, 所述移动性管理单元为 MME或 SGSN;
网络拥塞时, 移动性管理单元主动发送负载控制信令给 IWF; 或, 网 络拥塞后, 移动性管理单元不主动发送负载控制信令给 IWF, 而是在接收 到 IWF发送的触发消息后, 发送触发消息拒绝信令给 IWF, 并在信令中指 示拒绝原因为网络拥塞。
步驟 202, IWF接收到负载控制信令或触发消息拒绝信令后 ,停止发送 触发消息给该移动性管理单元。
实施例一
图 3是本发明实现网络拥塞控制方法的实施例一的流程示意图, 本实 施例中, 所述移动性管理单元为 MME, 网络拥塞时, MME发送负载控制 信令给 IWF, 如图 3所示, 该方法具体包括以下步驟:
步驟 301 , 网络运营商为 MME配置负载门限值; 具体的, 网络运营商根据 MME的运行能力,如最大能同时处理多少个 用户的连接请求,为 MME配置负载门限值,该负载门限值必须小于能够同 时处理的最大用户数。
步驟 302, 根据负载门限值确定发生网络拥塞时, MME发送负载控制 信令给 IWF, 其中携带表示当前网络处于拥塞状态的负载状态;
具体的, 当前处理的用户数达到负载门限值时, MME认为当前网络处 于拥塞状态, 则 MME发送负载控制信令给 IWF, 该负载控制信令中携带 负载状态, 该负载状态的值设置为 1 , 表示当前网络处于拥塞状态。
步驟 303 , IWF根据负载状态确定当前网络发生网络拥塞时,停止发送 触发消息到 MME;
具体的, IWF接收到 MME发送的负载控制信令后, 读取其中的负载 状态, 如果负载控制信令中的负载状态的值为 1 , 即表示当前网络发生网络 拥塞, 则停止发送触发消息到 MME。
步驟 304, IWF保存未发送的触发消息, 以及发生网络拥塞的 MME的 标识或地址, 并根据该 MME的标识或地址保存之后从 MTC服务器收到的 触发消息;
具体的 , 在 IWF停止发送触发消息到 MME的期间 , IWF保存本地未 发送的触发消息,还保存发生网络拥塞的 MME的标识或地址到本地的拥塞 MME列表; 有新的触发消息由 MTC服务器发送到 IWF时, IWF向 HSS 发送触发消息所属终端的标识, HSS查询该终端的服务 MME的标识或地 址, 将该 MME的标识或地址发送给 IWF, IWF将 HSS发送的 MME的标 识或地址和本地拥塞 MME列表中保存的 MME的标识或地址进行比较,如 果找到匹配的 MME的标识或地址, 则 IWF保存该触发消息, 不将该触发 消息发送到该 MME。
可选的, 本实施例中还可以包括步驟 305和步驟 306: 步驟 305, IWF收到负载控制信令后, 通过发送控制信令指示 MTC服 务器减少触发消息的发送;
具体的, IWF在接收到 MME发送的负载控制信令后, 还可以发送控 制信令给 MTC服务器, 该控制信令中携带控制因子, 将控制因子设置为 0-1之间的小数, 用于指示 MTC服务器按照该控制因子指示的百分比减少 发送到 IWF的触发消息, 例如控制因子设置为 0.5, 则 MTC服务器只发送 50%的触发消息到 IWF, 控制因子设置为 0.3, 则 MTC服务器只发送 30% 的触发消息到 IWF,即 MTC服务器只能发送控制因子指示的百分比数量的 触发消息。
步驟 306, IWF删除本地保存的有效时间到时的触发消息, 并向 MTC 服务器发送触发消息发送报告信令;
具体的, 如果 MTC服务器发送到 IWF的触发消息中包含有效时间, 有效时间内 IWF仍没有收到 MME发送的负载控制解除信令, 则 IWF在有 效时间到时后删除本地保存的该触发消息,并向 MTC服务器发送触发消息 发送报告信令, 该信令中携带终端标识、 发送状态和原因; 其中, 终端标 识为触发消息所属的终端标识,该终端标识最初由 MTC服务器在触发消息 中发送到 IWF;发送状态设置为 0,表示触发消息发送失败,原因设置为 "网 络拥塞"。
步驟 307, 网络拥塞解除后, MME发送负载控制解除信令给 IWF, 其 中携带表示当前网络不拥塞的负载状态;
具体的, 网络拥塞解除后, MME发送负载控制解除信令给 IWF, 该负 载控制解除信令中携带负载状态, 用于指示当前网络是否拥塞, 设置为 1 时, 表示当前网络处于拥塞状态, 设置为 0时, 表示当前网络不拥塞。
步驟 308, IWF接收到 MME发送的负载控制解除信令后, 恢复发送触 发消息到该 MME; 具体的, IWF接收到 MME发送的负载控制解除信令后, 将保存的该 MME的触发消息发送到该 MME; 如果有新的需要发送到该 MME的触发 消息, 则将该触发消息发送到该 MME。
步驟 309, IWF在本地保存的拥塞 MME列表中删除该 MME的标识或 地址。
可选的, 本实施例中还可以包括步驟 310:
步驟 310, IWF收到 MME的负载控制解除信令后, 通过发送控制信令 指示 MTC服务器恢复发送所有的触发消息;
具体的, IWF在接收到 MME的负载控制解除信令后, 发送控制信令 给 MTC服务器, 该控制信令中携带控制因子, 该控制因子设置为 1 , 即允 许 MTC服务器恢复发送所有的触发消息到 IWF。
实施例二
图 4是本发明实现网络拥塞控制方法的实施例二的流程示意图, 本实 施例中, 所述移动性管理单元为 SGSN, 网络拥塞时, SGSN发送负载控制 信令给 IWF, 如图 4所示, 该方法具体包括以下步驟:
步驟 401 , 网络运营商为 SGSN配置负载门限值;
具体的, 网络运营商根据 SGSN的运行能力, 如最大能同时处理多少 个用户的连接请求, 为 SGSN配置负载门限值, 该负载门限值必须小于能 够同时处理的最大用户数。
步驟 402, 根据负载门限值确定发生网络拥塞时, SGSN发送负载控制 信令给 IWF, 其中携带表示当前网络处于拥塞状态的负载状态;
具体的, 当前处理的用户数达到负载门限值时, SGSN认为当前网络处 于拥塞状态, 则 SGSN发送负载控制信令给 IWF, 该负载控制信令中携带 负载状态, 该负载状态的值设置为 1 , 表示当前网络处于拥塞状态。
步驟 403, IWF根据负载状态确定当前网络发生网络拥塞时,停止发送 触发消息到 SGSN;
具体的, IWF接收到 SGSN发送的负载控制信令后, 读取其中的负载 状态, 如果负载控制信令中的负载状态的值为 1 , 即表示当前网络发生网络 拥塞, 则停止发送触发消息到 SGSN。
步驟 404, IWF保存未发送的触发消息, 以及发生网络拥塞的 SGSN 的标识或地址,并根据该 SGSN的标识或地址保存之后从 MTC服务器收到 的触发消息;
具体的, 在 IWF停止发送触发消息到 SGSN的期间, IWF保存本地未 发送的触发消息, 还保存发生网络拥塞的 SGSN的标识或地址到本地的拥 塞 SGSN列表;有新的触发消息由 MTC服务器发送到 IWF时, IWF向 HSS 发送触发消息所属终端的标识, HSS查询该终端的服务 SGSN的标识或地 址, 将该 SGSN的标识或地址发送给 IWF, IWF将 HSS发送的 SGSN的标 识或地址和本地拥塞 SGSN列表中保存的 SGSN的标识或地址进行比较, 如果找到匹配的 SGSN的标识或地址, 则 IWF保存该触发消息, 不将该触 发消息发送到该 SGSN。
可选的, 本实施例中还可以包括步驟 405和步驟 406:
步驟 405, IWF收到负载控制信令后, 通过发送控制信令指示 MTC服 务器减少触发消息的发送;
具体的, IWF在接收到 SGSN发送的负载控制信令后, 还可以发送控 制信令给 MTC服务器, 该控制信令中携带控制因子, 将控制因子设置为 0-1之间的小数, 用于指示 MTC服务器按照该控制因子指示的百分比减少 发送到 IWF的触发消息, 例如控制因子设置为 0.5, 则 MTC服务器只发送 50%的触发消息到 IWF, 控制因子设置为 0.3, 则 MTC服务器只发送 30% 的触发消息到 IWF,即 MTC服务器只能发送控制因子指示的百分比数量的 触发消息。 步驟 406, IWF删除本地保存的有效时间到时的触发消息, 并向 MTC 服务器发送触发消息发送报告信令;
具体的, 如果 MTC服务器发送到 IWF的触发消息中包含有效时间, 有效时间内 IWF仍没有收到 SGSN发送的负载控制解除信令,则 IWF在有 效时间到时后删除本地保存的该触发消息,并向 MTC服务器发送触发消息 发送报告信令, 该信令中携带终端标识、 发送状态和原因; 其中, 终端标 识为触发消息所属的终端标识,该终端标识最初由 MTC服务器在触发消息 中发送到 IWF;发送状态设置为 0,表示触发消息发送失败,原因设置为 "网 络拥塞"。
步驟 407, 网络拥塞解除后, SGSN发送负载控制解除信令给 IWF, 其 中携带表示当前网络不拥塞的负载状态;
具体的, 网络拥塞解除后, SGSN发送负载控制解除信令给 IWF, 该负 载控制解除信令中携带负载状态, 用于指示当前网络是否拥塞, 设置为 1 时, 表示当前网络处于拥塞状态, 设置为 0时, 表示当前网络不拥塞。
步驟 408, IWF接收到 SGSN发送的负载控制解除信令后,恢复发送触 发消息到该 SGSN;
具体的, IWF接收到 SGSN发送的负载控制解除信令后, 将保存的该 SGSN的触发消息发送到该 SGSN;如果有新的需要发送到该 SGSN的触发 消息, 则将该触发消息发送到该 SGSN。
步驟 409, IWF在本地保存的拥塞 SGSN列表中删除该 SGSN的标识 或地址。
可选的, 本实施例中还可以包括步驟 410:
步驟 410, IWF收到 SGSN的负载控制解除信令后,通过发送控制信令 指示 MTC服务器恢复发送所有的触发消息;
具体的, IWF在接收到 SGSN的负载控制解除信令后, 发送控制信令 给 MTC服务器, 该控制信令中携带控制因子, 该控制因子设置为 1 , 即允 许 MTC服务器恢复发送所有的触发消息到 IWF。
实施例三
图 5是本发明实现网络拥塞控制方法的实施例三的流程示意图, 本实 施例中, 所述移动性管理单元为 MME或 SGSN, 移动性管理单元不主动发 送负载控制信令给 IWF, 而是在接收到 IWF发送的触发消息后, 发送触发 消息拒绝信令给 IWF, 并在信令中指示拒绝原因为网络拥塞, 如图 5所示, 该方法具体包括以下步驟:
步驟 501 , 网络运营商为移动性管理单元配置负载门限值;
具体的, 网络运营商根据移动性管理单元的运行能力, 如最大能同时 处理多少个用户的连接请求, 为移动性管理单元配置负载门限值, 该负载 门限值必须小于能够同时处理的最大用户数。
步驟 502,根据负载门限值确定发生网络拥塞时,移动性管理单元接收 到 IWF发送的触发消息后, 发送触发消息拒绝信令给 IWF, 其中携带拒绝 原因;
具体的, 当前处理的用户数达到负载门限值时, 移动性管理单元认为 当前网络处于拥塞状态,如果移动性管理单元接收到 IWF发送的触发消息, 则发送触发消息拒绝信令给 IWF; 该信令中携带拒绝原因, 该拒绝原因为 网络拥塞。
步驟 503, IWF根据拒绝原因确定当前网络发生拥塞时,停止发送触发 消息到移动性管理单元;
具体的, IWF接收到移动性管理单元发送的触发消息拒绝信令后, 读 取其中的拒绝原因, 如果拒绝原因是网络拥塞, 即表示当前网络发生拥塞, 则停止发送触发消息到移动性管理单元。
步驟 504, IWF保存未能发送的触发消息, 以及发生网络拥塞的移动性 管理单元的标识或地址, 并根据该移动性管理单元的标识或地址保存之后 从 MTC服务器收到的触发消息;
具体的, 在 IWF停止发送触发消息到移动性管理单元的期间, IWF保 存本地未发送的触发消息, 还保存发生网络拥塞的移动性管理单元的标识 或地址到本地的拥塞移动性管理单元列表;有新的触发消息由 MTC服务器 发送到 IWF时, IWF向 HSS发送触发消息所属终端的标识, HSS查询该终 端的服务移动性管理单元的标识或地址, 将该移动性管理单元的标识或地 址发送给 IWF, IWF将 HSS发送的移动性管理单元的标识或地址和本地拥 塞 MME列表中保存的移动性管理单元的标识或地址进行比较,如果找到匹 配的移动性管理单元的标识或地址, 则 IWF保存该触发消息, 不将该触发 消息发送到该移动性管理单元。
可选的, 本实施例中还可以包括步驟 505和步驟 506:
步驟 505, IWF收到触发消息拒绝信令后,通过发送控制信令指示 MTC 服务器减少触发消息的发送;
具体的, IWF在接收到移动性管理单元发送的触发消息拒绝信令后, 还可以发送控制信令给 MTC服务器, 该控制信令中携带控制因子, 将控制 因子设置为 0~1之间的小数,用于指示 MTC服务器按照该控制因子指示的 百分比减少发送到 IWF的触发消息, 例如控制因子设置为 0.5, 则 MTC月良 务器只发送 50%的触发消息到 IWF, 控制因子设置为 0.3 , 则 MTC服务器 只发送 30%的触发消息到 IWF,即 MTC服务器只能发送控制因子指示的百 分比数量的触发消息。
步驟 506, IWF删除本地保存的有效时间到时的触发消息, 并向 MTC 服务器发送触发消息发送报告信令;
具体的, 如果 MTC服务器发送到 IWF的触发消息中包含有效时间, 有效时间内 IWF仍没有收到移动性管理单元发送的负载控制解除信令, 则 IWF在有效时间到时后删除本地保存的该触发消息,并向 MTC服务器发送 触发消息发送报告信令, 该信令中携带终端标识、 发送状态和原因; 其中, 终端标识为触发消息所属的终端标识,该终端标识最初由 MTC服务器在触 发消息中发送到 IWF; 发送状态设置为 0, 表示触发消息发送失败, 原因设 置为 "网络拥塞"。
步驟 507, 网络拥塞解除后, 移动性管理单元发送负载控制解除信令给 IWF, 其中携带表示当前网络不拥塞的负载状态;
具体的, 网络拥塞解除后, 移动性管理单元发送负载控制解除信令给 IWF, 该负载控制解除信令中携带负载状态, 用于指示当前网络是否拥塞, 设置为 1时, 表示当前网络处于拥塞状态, 设置为 0时, 表示当前网络不 拥塞。
步驟 508, IWF接收到移动性管理单元发送的负载控制解除信令后, 恢 复发送触发消息到该移动性管理单元;
具体的, IWF接收到移动性管理单元发送的负载控制解除信令后, 将 保存的该移动性管理单元的触发消息发送到该移动性管理单元; 如果有新 的需要发送到该移动性管理单元的触发消息, 则将该触发消息发送到该移 动性管理单元。
步驟 509, IWF在本地保存的拥塞移动性管理单元列表中删除该移动性 管理单元的标识或地址。
可选的, 本实施例中还可以包括步驟 510:
步驟 510, IWF收到移动性管理单元的负载控制解除信令后,通过发送 控制信令指示 MTC服务器恢复发送所有的触发消息;
具体的, IWF在接收到移动性管理单元的负载控制解除信令后, 发送 控制信令给 MTC服务器, 该控制信令中携带控制因子, 该控制因子设置为 1 , 即允许 MTC服务器恢复发送所有的触发消息到 IWF。 实施例四
图 6是本发明实现网络拥塞控制方法的实施例四的流程示意图, 本实 施例中, 所述移动性管理单元为 MME或 SGSN, 移动性管理单元不主动发 送负载控制信令给 IWF, 而是在接收到 IWF发送的触发消息后, 发送触发 消息拒绝信令给 IWF, 并在信令中指示拒绝原因为网络拥塞, 如图 6所示, 该方法具体包括以下步驟:
步驟 601 , 网络运营商为移动性管理单元配置负载门限值;
具体的, 网络运营商根据移动性管理单元的运行能力, 如最大能同时 处理多少个用户的连接请求, 为移动性管理单元配置负载门限值, 该负载 门限值必须小于能够同时处理的最大用户数。
步驟 602,根据负载门限值确定发生网络拥塞时,移动性管理单元接收 到 IWF发送的触发消息后, 发送触发消息拒绝信令给 IWF, 其中携带拒绝 原因;
具体的, 当前处理的用户数达到负载门限值时, 移动性管理单元认为 当前网络处于拥塞状态,如果移动性管理单元接收到 IWF发送的触发消息, 则发送触发消息拒绝信令给 IWF; 该信令中携带拒绝原因, 该拒绝原因为 网络拥塞。
步驟 603, IWF根据拒绝原因确定当前网络发生拥塞时,停止发送触发 消息到移动性管理单元;
具体的, IWF接收到移动性管理单元发送的触发消息拒绝信令后, 读 取其中的拒绝原因, 如果拒绝原因是网络拥塞, 即表示当前网络发生拥塞, 则停止发送触发消息到移动性管理单元。
步驟 604, IWF停止发送触发消息到移动性管理单元后,发送触发消息 发送报告给 MTC服务器, 指示触发消息发送失败和发送失败的原因。
具体的, IWF停止发送触发消息到移动性管理单元后, 发送触发消息 发送报告给服务器, 该触发消息发送报告至少携带以下内容: 触发消息发 送状态和原因, 其中, 触发消息发送状态为失败, 原因为网络拥塞; 该触 发消息发送报告用于指示 MTC服务器触发消息发送失败和发送失败的原 因。
为实现上述方法, 本发明还提供一种网络拥塞控制系统, 图 7是本发 明实现网络拥塞控制系统的结构示意图, 如图 7所示, 该系统包括: 移动 性管理单元 71、 IWF 72; 其中,
移动性管理单元 71 , 用于网络拥塞时, 发送负载控制信令或触发消息 拒绝信令给 IWF 72;
IWF 72, 用于接收到负载控制信令或触发消息拒绝信令后, 停止发送 触发消息给所述移动性管理单元 71。
所述 IWF 72, 还用于保存所述触发消息、 以及发送负载控制信令或触 发消息拒绝信令的移动性管理单元的标识或地址。
所述 IWF72,还用于收到负载控制信令后,通过发送控制信令指示 MTC 服务器减少触发消息的发送。
所述 IWF 72, 还用于删除本地保存的有效时间到时的触发消息, 并向 MTC服务器发送触发消息发送报告信令。
所述移动性管理单元 71 , 还用于网络拥塞解除后, 发送负载控制解除 信令给 IWF 72, 其中携带当前网络不拥塞的负载状态;
所述 IWF 72, 还用于接收到负载控制解除信令后, 恢复发送触发消息 给所述移动性管理单元 71。
所述 IWF 72, 还用于在本地保存的拥塞移动性管理单元列表中删除该 移动性管理单元的标识或地址。
所述 IWF 72, 还用于收到移动性管理单元的负载控制解除信令后, 通 过发送控制信令指示 MTC服务器恢复发送所有的触发消息。 所述 IWF 73, 还用于停止发送触发消息到移动性管理单元后, 发送触 发消息发送报告给 MTC服务器, 指示触发消息发送失败和发送失败的原 因。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围, 凡在本发明的精神和原则之内所作的任何修改、 等同替换和改进 等, 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种网络拥塞控制方法, 其特征在于, 该方法包括:
网络拥塞时, 移动性管理单元发送负载控制信令或触发消息拒绝信令 给互操作功能实体(IWF ) ;
所述 IWF接收到负载控制信令或触发消息拒绝信令后 , 停止发送触发 消息给所述移动性管理单元。
2、 根据权利要求 1所述的方法, 其特征在于, 所述网络拥塞时, 移动 性管理单元发送负载控制信令给 IWF为:
发生网络拥塞时, 移动性管理单元发送负载控制信令给 IWF, 其中携 带当前网络处于拥塞状态的负载状态。
3、 根据权利要求 2所述的方法, 其特征在于, 所述停止发送触发消息 给所述移动性管理单元为:
IWF接收到移动性管理单元发送的负载控制信令后, 读取其中的负载 状态, 负载状态是当前网络发生网络拥塞时, 停止发送触发消息到移动性 管理单元。
4、 根据权利要求 1所述的方法, 其特征在于, 所述网络拥塞时, 移动 性管理单元发送触发消息拒绝信令给 IWF为:
发生网络拥塞时, 移动性管理单元接收到 IWF发送的触发消息后, 发 送触发消息拒绝信令给 IWF, 其中携带拒绝原因。
5、 根据权利要求 4所述的方法, 其特征在于, 所述停止发送触发消息 给所述移动性管理单元为:
IWF接收到移动性管理单元发送的触发消息拒绝信令后, 读取其中的 拒绝原因, 拒绝原因是当前网络发生拥塞时, 停止发送触发消息到移动性 管理单元。
6、根据权利要求 2或 4所述的方法,其特征在于,该方法还包括: IWF 收到负载控制信令或触发消息拒绝信令后, 通过发送控制信令指示机器类 型通信(MTC )服务器减少触发消息的发送。
7、 根据权利要求 3或 5所述的方法, 其特征在于, 该方法还包括: IWF保存未发送的触发消息, 并保存发生网络拥塞的移动性管理单元 的标识或地址,根据该移动性管理单元的标识或地址保存之后从 MTC服务 器收到的触发消息。
8、 根据权利要求 7所述的方法, 其特征在于, 该方法还包括: IWF删 除本地保存的有效时间到时的触发消息,并向 MTC服务器发送触发消息发 送报告信令。
9、 根据权利要求 7所述的方法, 其特征在于, 该方法还包括: 网络拥塞解除后, 移动性管理单元发送负载控制解除信令给 IWF, 其 中携带当前网络不拥塞的负载状态;
所述 IWF接收到负载控制解除信令后, 恢复发送触发消息给所述移动 性管理单元。
10、 根据权利要求 9 所述的方法, 其特征在于, 该方法还包括: IWF 在本地保存的拥塞移动性管理单元列表中删除该移动性管理单元的标识或 地址。
11、 根据权利要求 9 所述的方法, 其特征在于, 该方法还包括: IWF 收到移动性管理单元的负载控制解除信令后, 通过发送控制信令指示 MTC 服务器恢复发送所有的触发消息。
12、 根据权利要求 5 所述的方法, 其特征在于, 该方法还包括: IWF 停止发送触发消息到移动性管理单元后,发送触发消息发送报告给 MTC服 务器, 指示触发消息发送失败和发送失败的原因。
13、 一种网络拥塞控制系统, 其特征在于, 该系统包括: 移动性管理 单元、 IWF; 其中, 移动性管理单元, 用于网络拥塞时, 发送负载控制信令或触发消息拒 绝信令给 IWF;
IWF, 用于接收到负载控制信令或触发消息拒绝信令后,停止发送触发 消息给所述移动性管理单元。
14、 根据权利要求 13所述的系统, 其特征在于, 所述 IWF, 还用于保 存所述触发消息、 以及发送负载控制信令或触发消息拒绝信令的移动性管 理单元的标识或地址。
15、 根据权利要求 13所述的系统, 其特征在于, 所述 IWF, 还用于收 到负载控制信令后 ,通过发送控制信令指示 MTC服务器减少触发消息的发 送。
16、 根据权利要求 14所述的系统, 其特征在于, 所述 IWF, 还用于删 除本地保存的有效时间到时的触发消息,并向 MTC服务器发送触发消息发 送报告信令。
17、 根据权利要求 14所述的系统, 其特征在于,
所述移动性管理单元, 还用于网络拥塞解除后, 发送负载控制解除信 令给 IWF, 其中携带当前网络不拥塞的负载状态;
所述 IWF, 还用于接收到负载控制解除信令后, 恢复发送触发消息给 所述移动性管理单元。
18、 根据权利要求 17所述的系统, 其特征在于, 所述 IWF, 还用于在 本地保存的拥塞移动性管理单元列表中删除该移动性管理单元的标识或地 址。
19、 根据权利要求 17所述的系统, 其特征在于, 所述 IWF, 还用于收 到移动性管理单元的负载控制解除信令后,通过发送控制信令指示 MTC服 务器恢复发送所有的触发消息。
20、 根据权利要求 13所述的系统, 其特征在于, 所述 IWF, 还用于停 止发送触发消息到移动性管理单元后,发送触发消息发送报告给 MTC服务 器, 指示触发消息发送失败和发送失败的原因。
PCT/CN2012/071607 2011-12-29 2012-02-24 一种网络拥塞控制方法及系统 WO2013097337A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110450214.5 2011-12-29
CN201110450214.5A CN103188728B (zh) 2011-12-29 2011-12-29 一种网络拥塞控制方法及系统

Publications (1)

Publication Number Publication Date
WO2013097337A1 true WO2013097337A1 (zh) 2013-07-04

Family

ID=48679615

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/071607 WO2013097337A1 (zh) 2011-12-29 2012-02-24 一种网络拥塞控制方法及系统

Country Status (2)

Country Link
CN (1) CN103188728B (zh)
WO (1) WO2013097337A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3462769B1 (en) 2016-06-28 2020-03-04 Huawei Technologies Co., Ltd. Load migration method, apparatus and system
EP3313114B1 (en) * 2016-10-18 2021-06-09 Nokia Solutions and Networks Oy Detection and mitigation of signalling anomalies in wireless network
WO2019218126A1 (zh) 2018-05-14 2019-11-21 Oppo广东移动通信有限公司 控制网络拥塞的方法、终端设备和网络设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137433A (zh) * 2011-04-15 2011-07-27 电信科学技术研究院 一种接入控制方法及装置
CN102238689A (zh) * 2010-04-23 2011-11-09 中兴通讯股份有限公司 一种机器类型通信终端的接入控制方法及系统
CN102238629A (zh) * 2010-05-07 2011-11-09 华为技术有限公司 机器类型通讯的接入控制方法和设备及通信系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238689A (zh) * 2010-04-23 2011-11-09 中兴通讯股份有限公司 一种机器类型通信终端的接入控制方法及系统
CN102238629A (zh) * 2010-05-07 2011-11-09 华为技术有限公司 机器类型通讯的接入控制方法和设备及通信系统
CN102137433A (zh) * 2011-04-15 2011-07-27 电信科学技术研究院 一种接入控制方法及装置

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HTC ET AL.: "Proposed conclusion on overload handling for device triggering", 3GPP SA WG2 MEETING #88, 14 November 2011 (2011-11-14), SAN FRANCISCO, USA, pages 1 - 2, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_88_San_Francisco/Docs/S2-115307> [retrieved on 20111118] *
HTC: "Load/Overload Control via MTC-IWF", 3GPP SA WG2 MEETING #87, 14 November 2011 (2011-11-14), JEJU, KOREA, pages 1 - 2, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2Arch/TSGS2_87JejuIsland/Docs/S2-114140> [retrieved on 20110914] *
HTC: "Load/Overload Control via MTC-IWF", 3GPP SA WG2 MEETING #87, 14 September 2011 (2011-09-14), JEJU, KOREA, pages 1 - 2, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_87_Jeju_Island/Docs/S2-114674> [retrieved on 20110914] *
ZTE: "Overload control for MTC device triggering", 3GPP SA WG2 MEETING #88, 14 November 2011 (2011-11-14), SAN FRANCISCO, USA, pages 1 - 2, XP050575271, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_88_San_Francisco/Docs/S2-114840> [retrieved on 20111118] *

Also Published As

Publication number Publication date
CN103188728B (zh) 2018-07-31
CN103188728A (zh) 2013-07-03

Similar Documents

Publication Publication Date Title
KR102287842B1 (ko) 무선 통신 시스템에서의 등록 해제 방법 및 이를 위한 장치
US11617072B2 (en) Reliable data delivery over non-access stratum
US9473877B2 (en) Uplink/downlink transmission method for small amount of data, and corresponding terminal and mobility management unit
US20130012204A1 (en) Method and terminal for performing detach procedure
WO2012051890A1 (zh) 终端接入限制的方法及系统
WO2012094982A1 (zh) 一种接入控制的方法及装置
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2009097772A1 (zh) 一种资源释放控制方法及通讯系统以及相关设备
JP2010521899A (ja) トラッキングエリアの更新或いは切替プロセスにおいてリソースが誤ってリリースされることを防ぐ方法
WO2011035732A1 (zh) 本地ip接入或选定的ip流量卸载的控制方法、装置与系统
KR20160060091A (ko) 페이징 방법, 네트워크 디바이스 및 통신 시스템
EP2760229B1 (en) Trigger message sending method and system
US9629179B2 (en) Method and device for processing local access connection
US20190349742A1 (en) Method and apparatus for utilizing ladn in wireless communication system
WO2012100664A1 (zh) 一种激活终端的方法和系统
WO2011147156A1 (zh) 一种限制接入特定区域的方法及系统
WO2011044816A1 (zh) 用户设备的监控方法及监控装置
CN102014452B (zh) 一种本地ip访问连接实现移动性的方法和系统
WO2012155808A1 (zh) 设备触发方法及网元设备
WO2013097337A1 (zh) 一种网络拥塞控制方法及系统
WO2012100674A1 (zh) 一种共设mtc设备的信令优化方法和系统
EP2779778B1 (en) Method and system for effective time control of terminal trigger message
WO2011127723A1 (zh) 一种处理mtc优先警报消息的方法和系统
WO2012152046A1 (zh) 终端接入方法及系统
WO2011035671A1 (zh) 一种释放本地ip访问连接的系统及方法

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

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

Country of ref document: EP

Kind code of ref document: A1