WO2012041198A1 - 一种拥塞处理方法及设备 - Google Patents

一种拥塞处理方法及设备 Download PDF

Info

Publication number
WO2012041198A1
WO2012041198A1 PCT/CN2011/080157 CN2011080157W WO2012041198A1 WO 2012041198 A1 WO2012041198 A1 WO 2012041198A1 CN 2011080157 W CN2011080157 W CN 2011080157W WO 2012041198 A1 WO2012041198 A1 WO 2012041198A1
Authority
WO
WIPO (PCT)
Prior art keywords
apn
message
attach
congested
mme
Prior art date
Application number
PCT/CN2011/080157
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 WO2012041198A1 publication Critical patent/WO2012041198A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • 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
    • 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 a machine type communication technology, and in particular, to a congestion processing method and apparatus. Background technique
  • NTT DoCoMo proposed a congestion control method based on Access Point Name (APN) to avoid and resolve congestion associated with a particular APN.
  • the network starts a back-off timer according to whether the APN is congested, including a Mobility Management back-off timer and a Session Management back-off timer.
  • EPS Evolved Packet System
  • ESM EPS Session Management
  • the Mobility Management Entity detects APN-based congestion according to certain criteria.
  • the standards include:
  • EPS Bearers The maximum number of active EPS bearers (EPS Bearers) for each APN (Per APN); b. Percentrate of EPS Bearer of Per APN;
  • the MME is unreachable to one or more packet data network gateways (PDN Gateway, PGW; Packet Data Network, PDN), or receives a congestion indication from these PDN GWs;
  • PDN Gateway Packet Data Network
  • PDN Packet Data Network
  • the MME When a congestion for an APN occurs, the MME stores a Mobility
  • EPS Mobility Management back-off timer for EPS Mobility Management process, 1" port l 1 attach (Take) process, Tracking Area Update (TAU) process
  • Session Management back-off timer for EPS Session Management
  • PDN Connectivity Request for EPS Session Management
  • the MME should abbreviate the process and start the Mobility Management back-off timer, and indicate that the UE cannot initiate any Mobility Management process before the timer expires.
  • the default APN (default APN) is used in the subscription data. If it is determined that the used APN is in a congested state, the MME should reject the PDN Connectivity Request message and instruct the UE to start the Session Management back-off timer. Before the J3 ⁇ 4 timer expires, the UE cannot Initiate the PDN Connectivity Request process for the J3 ⁇ 4 APN.
  • the network needs to retain the subscription information of the UE for a period of time.
  • the technical problem to be solved by the present invention is to provide a congestion processing method and device for solving In the prior art, when the UE subscribes to multiple ports, the UE is prevented from obtaining normal service during the processing based on the scheme of the congestion-based control.
  • a congestion processing method is provided in the embodiment of the present invention, including the following steps:
  • the mobility management entity After receiving the attach request Attach Request message initiated by the user equipment UE, the mobility management entity determines the subscription access point name APN of the UE;
  • the MME determines that the APN in the contracted APN is congested
  • the MME indicates, in the message returning to the UE, the APN that is congested in the subscribed APN, and indicates that the session management backoff timer is set to the APN in the congestion.
  • a congestion processing method is provided in the embodiment of the present invention, including the following steps:
  • the UE sends an Attach Request message to the MME.
  • the UE sets a Session Management back-off timer for the congested APN.
  • the embodiment of the present invention provides a mobility management entity device, including:
  • An APN determining module configured to determine a subscription APN of the UE after receiving an Attach Request message initiated by the UE;
  • a congestion determination module configured to determine a congested APN in the contracted APN
  • an indication module configured to indicate, in the message returned to the UE, a congested APN in the subscribed APN, and to indicate that a Session Management back-off timer is set for the APN that is congested.
  • a user equipment is provided in the embodiment of the present invention, including:
  • a sending module configured to send an Attach Request message to the MME
  • a receiving module configured to receive a message that the MME returns to the UE, where the message indicates a CPN that is congested in the APN of the UE, and indicates that a Session Management back-off timer is set for the APN that is in congestion;
  • Congestion processing module for setting Session Management back-off to a congested APN Timer
  • the MME determines that the APN of the subscribed APN of the UE is congested, and indicates to the UE that the APN in the subscribed APN is congested, and indicates that the pair is in congestion.
  • APN sets the Session Management back-off timer.
  • the UE can learn the APN that is congested in the contracted APN, so that the corresponding subsequent process can be retrieved.
  • the ARP is not congested and the Attach request cannot be initiated. Later, it was rejected by the network because other contracted APNs were congested. Therefore, the problem that the UE is prevented from obtaining normal service when the UE subscribes to multiple APNs is overcome.
  • the UE can obtain information about all the congested APNs in the subscribed APN, the UE can be prevented from initiating the EPS Session Management process to the APNs, thereby avoiding unnecessary signaling waste.
  • the technical solution provided by the embodiment of the present invention can improve the irrationality of the prior art, minimize the signaling resource consumption in the network, ensure the normal service operation, and improve the user experience.
  • FIG. 4 is a schematic flow chart showing an implementation process of a congestion processing method in which a UE desires to provide an APN according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of a mobility management entity device according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a user equipment according to an embodiment of the present invention.
  • DETAILED Embodiment 5 is a schematic structural diagram of a user equipment according to an embodiment of the present invention.
  • Network congestion may occur.
  • Network congestion can be divided into user plane congestion and signaling plane congestion. Once network congestion occurs, the network should reject the corresponding signaling connection request or data transmission request.
  • congestion control based on APN. It is proposed that in the Attach process, if the requested APN is congested, the Attach process is rejected and a back-off timer is started. Before the timer expires, The MTC Device cannot initiate any Mobility Management request, ie the Attach process can no longer be initiated.
  • the attach procedure In the Long Term Evolution (LTE) system, the attach procedure must establish a PDN connection. This requires the UE to initiate the Attach process and initiate the PDN Connectivity Request process. In the existing Attach process, the UE is in the Attach Request.
  • the PSN Connectivity Request message is sent in the ESM message container IE (Information Element, IE) of the message.
  • the PDN Connectivity Request message cannot carry the APN, so the network can use the default APN signed by the UE to initiate the PDN Connectivity Request process. .
  • the ESM information transfer flag (EMS information transfer flag) needs to be set in the PDN Connectivity Request message, so that the MME initiates an ESM Information Tequest process after the Security Context is established, and then The UE will provide an APN in the ESM Information Response message. If the network allows the APN, the APN is used to initiate the PDN Connectivity Request process.
  • the APN may be in a congested state when the UE initiates the Attach procedure, but for other APNs, it may be in a normal state, and the APN used by the established PDN connection is not congested.
  • other APNs that the UE subscribes to are experiencing congestion.
  • the APN-based method of congestion control cannot work well. For example, at least the following two inappropriate scenarios exist: 1. In the existing Attach process, the UE 6 can use the default APN to establish a PDN connection, or use other APNs to establish a PDN connection. If the Mobility Management backoff timer is set according to the NTT Docomo method, the UE is prevented from subsequently initiating Mobility.
  • the management process as long as the APN requested by the UE is in a congested state, the UE will not be able to access the network during the entire backoff timer. Even if the other APNs that the UE subscribes to are not congested, the UE cannot obtain the corresponding service. Therefore, this method prevents the UE from acquiring normal services.
  • the UE cannot know whether other APNs are in the process after the Attach process ends. Congested state, so the UE may soon initiate the establishment of an additional PDN connection corresponding to the APN in the congested state, and the process will be rejected by the network, wasting signaling resources.
  • one UE may subscribe to multiple APNs.
  • the APN that may be used is in a congested state, but for other APNs, it may be in a normal state, and the UE may try to respond after the Attach process is rejected.
  • the Attach process of other non-congested APNs obtains services corresponding to these APNs, which cannot be implemented in the prior art, because any Mobility Management process is rejected after the UE-initiated Attach process is rejected.
  • the APN used by the established PDN connection is not congested, and the UE may quickly initiate the establishment process of the additional PDN connection corresponding to the APN in the congestion state, which is rejected by the network.
  • the UE will re-initiate the attach process corresponding to the non-congested APN after the attach process is rejected, so that the UE can obtain the service corresponding to other non-congested APNs in time.
  • the implementation of the MME side and the UE side will be described first, and finally, the implementation of the two will be described. However, this does not mean that the two must be implemented together. In fact, when the MME is implemented separately from the UE, At the same time, the problems existing on the MME side and the UE side are also solved, but when the two are used in combination, a better technical effect is obtained.
  • FIG. 1 is a schematic flowchart of an implementation process of a congestion processing method on an MME side, as shown in FIG. The following steps: 7
  • Step 101 After receiving the Attach Request message initiated by the UE, the MME determines the signing APN of the UE.
  • Step 102 The MME determines that the APN in the contracted APN is congested
  • Step 103 The MME indicates, in the message returning to the UE, the APN that is congested in the subscribed APN, and indicates that the Session Management back-off timer is set for the APN that is in congestion.
  • the congestion processing scheme on the UE side is also provided in the embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for implementing congestion processing on a UE side, as shown in FIG. 2, which may include the following steps:
  • Step 201 The UE sends an Attach Request message to the MME.
  • Step 202 The UE receives a message that the MME returns to the UE, where the message indicates the APN that is congested in the subscribed APN of the UE, and indicates that the Session Management back-off timer is set to the APN that is in congestion.
  • Step 203 The UE sets a Session Management back-off timer to the APN that is congested. It can be seen that, in this solution, after the UE initiates the Attach Request message, the UE can learn the APN that is congested in the contracted APN, and thus can obtain the corresponding subsequent process, and cannot initiate the Attach request because one APN is congested. It will not be rejected by the network after the successful attachment, because other contracted APNs are congested.
  • the APN when a UE may subscribe to multiple APNs, the APN may be in a congested state when the UE initiates an Attach procedure, but for other APNs, it may be in a normal state, and the APN used by the established PDN connection does not occur. Congestion, but when other APNs subscribed by the UE are congested, the implementation of the solution of the present invention will be described based on the implementation of the scenario in which the APN-based congestion control method does not work well.
  • the following two implementations are used to illustrate that it is only because the APN-based method of congestion control does not work well in these two cases; however, theoretically, in other In this case, the technical solution provided in the embodiment of the present invention can also be used, as long as the UE can notify the UE of the status of the subscribed APN after the UE initiates the Attach, so that the UE can perform the subsequent process. It is used to teach those skilled in the art how to apply the invention in detail, but it does not mean that it can be used only in these two scenarios, and the corresponding process improvement can be determined in combination with practical needs in the implementation process.
  • This method is described by taking the example that the UE uses the default APN to establish a PDN connection. The following is explained first from the implementation on the MME side.
  • the MME may indicate that the APN in the subscribed APN is congested in the Attach Reject message of the returning UE, and indicate that the Session Management back-off timer is set for the APN that is in congestion.
  • the MME may indicate in the Attach Reject message of the returning UE and reject the message. UE's Attach process.
  • the UE does not carry the APN or ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message.
  • the message that the MME returns to the UE is an Attach Reject message.
  • it may further include:
  • the UE determines the APN that is congested and not congested
  • the UE selects the APN that is not congested to initiate an Attach request, or initiates an Attach request after the Session Management back-off timer of the congested APN expires.
  • the method further includes:
  • the UE does not select the APN that corresponds to the Session Management backoff timer that has not timed out.
  • the PDN Connectivity Request is initiated.
  • the UE initiates an Attach procedure, and does not provide an APN to the network, and does not carry an ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message; the network initiates the PDN Connectivity Request process by using the default APN, The network refuses Attach because the default APN is in congestion state The process, but carries the Session Management backoff timer of each APN in the congested state of the UE subscription 9 in the reject message, and does not start the Mobility Management backoff timer.
  • the UE receives the Session Management backoff timer of each APN that is in a congested state, and starts the corresponding timer, and then checks whether the contracted APN is not in a congested state. If yes, the APN is used to initiate the Attach process again. If not, the UE needs to wait until the ASN Session Management backoff timer expires before initiating the Attach process.
  • the UE initiates an attach procedure using an APN that is not in a congested state.
  • the UE After the Attach is completed, the UE cannot initiate a PDN Connectivity Request corresponding to the APN that the Session Management backoff timer has not timed out.
  • FIG. 3 is a schematic flowchart of a method for implementing a congestion processing method for a UE to establish a PDN connection by using a default APN.
  • a new MME is a new MME that initiates an attach request
  • an old MME is an MME that provides services for a previously used UE.
  • the following processes can be included in the process:
  • Step 301 The UE sends an Attach request message to the eNB.
  • Step 302 The eNB sends an Attach request message to the new MME.
  • Step 303 The new MME sends an identification request message to the old MME.
  • Step 304 The old MME sends an identification response message to the new MME.
  • Step 305 The new MME sends an identification request message to the UE.
  • Step 306 The UE sends an identification response message to the new MME.
  • Step 307 authentication, security authentication, etc.
  • Step 308-309 UE, new MME, device identification logger (Device Identification
  • ME Identity Check is a mobile device identity check
  • Step 310 The new MME sends an encryption option request message to the UE.
  • Step 311 The UE sends an encryption option response message to the new MME.
  • Step 312 The new MME sends a delete session request message to the SGW.
  • Step 313 The SGW deletes the session response message from the new MME.
  • Step 314 The new MME sends a location update request message to the home subscriber server (HSS).
  • HSS home subscriber server
  • Step 315 The HSS sends a location cancellation message to the old MME.
  • Step 316 The old MME returns a location cancellation confirmation message to the HSS.
  • Step 317 The old MME sends a delete session request message to the PGW.
  • Step 318 The PGW sends a delete session response message to the old MME.
  • Step 319 The HSS sends a location update confirmation message to the new MME.
  • Step 320 The new MME sends an Attach Reject message to the UE.
  • Step 321 The UE determines whether there is an APN that is not in congestion
  • Step 322 The UE sends an Attach request message to the new MME.
  • the behavior of the MME and the UE can be implemented as follows:
  • the UE initiates the Attach process, and the PDN connectivity in the ESM message container
  • the MME obtains the subscription information of the UE, and obtains the default APN signed by the UE. However, if the default APN is in a congested state, the acknowledgment process is rejected.
  • the MME returns the APN and the corresponding Session backoff timer that are subscribed to by the UE.
  • the message format can be bolded in the following message format:
  • This message is sent by the network to the UE to indicate that the corresponding attach request has been rejected. See table 8.2.3.1.
  • the session backoff Timer List indicates a session backoff timer list
  • List x.x represents a list of backoff timers, O means optional, TLV means type - length - value, cell length.
  • Backoff Timer List can be as follows:
  • Backoff Timer list IE (backoff timer list information element) octet 1
  • Access point name 1 (access point name 1 ) octet 4 octet i
  • Backoff Timer 1 (backoff timer 1) octet i+1
  • Access point name n (access point name n ) octet j+1 octet k
  • the Backoff Timer can use the definition of GPRS Timer in Section 10.5.7.3 of TS 24.008 (see Figure 10.5.146/3GPP TS 24.008: GPRS Timer information element for details): 8 7 6 5 12 4 3 2 1
  • Access point name can use the definition of 10.5.6.1 in TS24.008 (see Figure 10.5.152/3GPP TS 24.008: Access point name information element for details).
  • the UE receives the contracted session management backoff timer of the APN in the congested state, starts the corresponding timer, and then checks whether the subscribed APN is not in the congested state. If yes, the APN is used to initiate the Attach process again. If not, the UE needs to wait until the Session Management backoff timer of the APN expires before initiating the Attach process.
  • the UE re-initiates the attach process.
  • This method is described by taking the example that the UE wants to provide an APN and sets the ESM information transfer flag in the PDN Connectivity Request message.
  • the UE may carry the ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the initiated Attach Request message.
  • the MME may indicate that the APN in the subscribed APN is congested in the ESM information Request message of the returning UE, and indicate that the Session Management back-off timer is set for the APN that is in congestion.
  • it may further include:
  • the MME When the ASN is carried in the ESM information Response message sent by the UE to the MME, the MME returns the APN carried in the ESM information Response message of the MME by the UE.
  • the UE completes the PDN Connectivity Request process
  • the MME rejects the attach procedure of the UE.
  • the MME when the MME rejects the attach procedure of the UE, the MME may further include:
  • the MME does not start the Mobility Management backoff timer.
  • the UE may carry the ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message.
  • the message that the MME returns to the UE may be an ESM information Request message. In the implementation, it may further include:
  • the UE determines the APN that is congested and not congested
  • the UE selects an APN that is not congested, and sends the APN to the MME after the APN is carried in the ESM information Response message. If there is no APN that is not congested, the APN is not carried in the ESM information Response message.
  • the APN if the APN is not carried in the ESM information Response message, it can further include:
  • the Attach request is initiated after the session management back-off timer of the congested APN times out.
  • the method further includes:
  • the UE does not select the APN initiated by the Session Management backoff timer that has not timed out.
  • the UE initiates an attach procedure, and carries an ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message.
  • the MME After receiving the ESM information transfer flag and obtaining the subscription data of the UE, the MME checks whether the APN signed by the UE is in a congested state, and if yes, passes the Session backoff timer of each APN in the congested state to the ESM information request process. UE. 3. After receiving the Session backoff timer of each APN in a congested state, the UE starts the corresponding timer, and then checks whether the subscribed APN is not in a congested state, and if so, the ESM INFORMATION RESPONSE message. An APN that is not in a congested state is reported to the MME; if not, it is not.
  • the MME uses the APN to complete the PDN Connectivity Request process. Otherwise, the MME uses the default APN to initiate the PDN Connectivity Request process. At this time, the default APN is in a congested state, and the MME rejects the Attach process.
  • the MME may or may not start the Mobility Management backoff timer.
  • the UE does not provide the APN to the MME in the fourth point, the UE needs to wait until the Session backoff timer of the APN expires. If the Mobility Management backoff timer is started, the UE must wait for the timer to expire before re-initiating the first point. The attach process.
  • the UE After the Attach is completed, the UE cannot initiate a PDN Connectivity Request corresponding to the APN that the Session Management backoff timer has not timed out.
  • FIG. 4 is a schematic flowchart of a method for implementing a congestion processing method for a UE to provide an APN.
  • a new MME for a UE to initiate an attach request is used, and an old MME is a MME serving a previously used UE;
  • the following processes can be included:
  • Step 401 The UE sends an Attach request message to the eNB.
  • Step 402 The eNB sends an Attach request message to the new MME.
  • Step 403 The new MME sends an identification request message to the old MME.
  • Step 404 The old MME sends an identification response message to the new MME.
  • Step 405 The new MME sends an identification request message to the UE.
  • Step 406 The UE sends an identification response message to the new MME.
  • Step 407 authentication, security authentication, etc.
  • Steps 408-409 performing a recognition process between the UE, the new MME, and the EIR; Step 410: The new MME sends an ii 5 encryption option message to the UE.
  • Step 411 The UE sends an encryption option response message to the new MME.
  • Step 412 The new MME sends a delete session request message to the SGW.
  • Step 413 The SGW sends a delete session response message to the new MME.
  • Step 414 The new MME sends a location update request message to the HSS.
  • Step 415 The HSS sends a location cancellation message to the old MME.
  • Step 416 The old MME returns a location cancellation confirmation message to the HSS.
  • Step 417 The old MME sends a delete session request message to the PGW.
  • Step 418 The PGW sends a delete session response message to the old MME.
  • Step 419 The HSS sends a location update confirmation message to the new MME.
  • Step 420 The new MME sends an ESM information request message to the UE.
  • Step 421 The UE determines whether there is an APN that is not in congestion
  • Step 422 The UE sends an ESM information response message to the new MME.
  • Step 423-424 Attach accept or reject between the UE and the new MME, and a request process initiated by the UE.
  • the behavior of the MME and the UE can be implemented as follows:
  • the UE initiates an attach procedure, and carries the ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message.
  • the MME receives the ESM information transfer flag.
  • the MME obtains the subscription information of the UE from the HSS, and checks whether the APN signed by the UE is in a congested state.
  • the session backoff timer of each APN in the congested state is delivered to the UE through the ESM INFORMATION REQUEST message during the ESM information request.
  • the message format may be as follows: The part of the format with bold indications is:
  • This message is sent by the network to the UE to request the UE to provide ESM information, ie protocol configuration options or APN or both.
  • the session backoff Timer List indicates a session backoff timer list
  • the Backoff Timer List x.x indicates a backoff timer list
  • O indicates optional
  • TLV indicates type-length-value
  • X indicates cell length.
  • Backoff Timer List can be as follows:
  • Backoff Timer list IE (backoff timer list information element) octet 1
  • Access point name 1 (access point name 1 ) octet 4 octet i
  • Backoff Timer 1 (backoff timer 1) octet i+1
  • Access point name n (access point name n ) octet j+1 octet k
  • the Backoff Timer can use the definition of GPRS Timer in 10.4.7.3 of TS 24.008 (see Figure 10.5.146/3GPP TS 24.008: GPRS Timer information element for details):
  • Access point name can use the definition of 10.5.6.1 in TS24.008 (see Figure 10.5.152/3GPP TS 24.008: Access point name information element for details).
  • the UE receives the Session Management backoff timer of each APN in the congested state, and starts the corresponding timer.
  • the APN is carried in the ESM INFORMATION RESPONSE message, otherwise it is not carried. 7. If the APN is carried in the ESM INFORMATION RESPONSE message, the MME uses the APN to complete the PDN Connectivity Request procedure; otherwise, the MME may start the Mobility Management backoff timer and the Reject Attach procedure.
  • the UE may wait until the APN Session Management backoff timer expires before initiating the Attach process to complete the PDN Connectivity Request process.
  • an embodiment of the present invention provides a mobility management entity device and a user device.
  • the principle of solving the problem is similar to the congestion processing method in the embodiment of the present invention.
  • the implementation, the repetition will not be repeated.
  • FIG. 5 is a schematic structural diagram of a mobility management entity device. As shown in FIG. 5, the device may include:
  • the determining module 501 is configured to: after receiving the Attach Request message initiated by the UE, determine the subscription APN of the UE;
  • a congestion determination module 502 configured to determine a congested APN in the contracted APN
  • the indicating module 503 is configured to indicate, in the message returned to the UE, the APN that is congested in the subscribed APN, and to indicate that the Session Management back-off timer is set for the APN that is in congestion.
  • the indication module is further configured to: in the Attach Reject message of the returning UE, indicate the APN that is congested in the subscribed APN, and indicate that the Session Management back-off timer is set to the APN that is in congestion.
  • the indication module may be further configured to: when the UE initiates the attach process, the UE does not carry the APN or the ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message, and returns the message to the Attach Reject message of the UE. Give instructions.
  • the MME may further include:
  • the attach processing module 504 is configured to reject the attach process of the UE when returning the Attach Reject message.
  • the indication module is further configured to carry the ESM in the PDN Connectivity Request message of the ESM message container of the UE-initiated Attach Request message.
  • the ESN information request message returned to the UE indicates the APN that is congested in the contracted APN, and the session management back-off timer is set to the APN that is congested.
  • the MME may further include:
  • the attaching processing module 504 is configured to: when the ASN is carried in the ESM information Response message that the UE returns to the MME, complete the PDN Connectivity Request process by using the APN carried in the ESM information Response message returned by the UE; and returning the ESM of the MME in the UE When the message does not carry an APN, the UE's Attach process is rejected.
  • the attach processing module may be further configured to not start the Mobility Management backoff timer when rejecting the attach procedure of the UE.
  • FIG. 6 is a schematic structural diagram of a user equipment. As shown in the figure, the UE may include:
  • the sending module 601 is configured to send an Attach Request message to the MME.
  • the receiving module 602 is configured to receive a message that the MME returns to the UE, where the message indicates the APN that is congested in the subscribed APN of the UE, and indicates that the Session Management back-off timer is set for the APN that is in congestion;
  • the congestion processing module 603 is configured to set a Session Management back-off timer for the APN that is congested.
  • the sending module may further be used to carry the APN or ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message.
  • the receiving module is further configured to receive an Attach Reject message that the MME returns to the UE.
  • the congestion processing module may be further configured to determine an APN that is congested and not congested; select an APN that is not congested to initiate an Attach request, or initiate an Attach request after a Session Management back-off timer of the congested APN expires.
  • the congestion processing module may be further configured to: after the initiation of the Attach request, do not select the APN initiated by the Session Management backoff timer that does not time out. Connectivity Request.
  • the sending module may be further configured to carry the ESM information transfer flag in the PDN Connectivity Request message of the ESM message container of the Attach Request message.
  • the receiving module is further configured to receive an ESM information Request message that the MME returns to the UE.
  • the congestion processing module may be further configured to determine an APN that is congested and not congested; select an APN that is not congested, and report the APN to the MME after the ESN information Response message is sent; if there is no APN that is not congested, The APN is not carried in the ESM information Response message.
  • the congestion processing module may be further configured to: if the APN is not carried in the ESM information Response message, initiate an Attach request after the session management back-off timer of the APN is timed out.
  • the congestion processing module may be further configured to initiate a PDN Connectivity Request by selecting an APN corresponding to the Session Management backoff timer that does not time out after the initiation of the Attach request is completed.
  • the technical solution provided by the embodiment of the present invention can improve the unreasonableness of the prior art, can minimize the signaling resource consumption in the network, ensure the normal service operation, and improve the user experience.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of one or more computer program products embodied on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.
  • a computer-usable storage medium including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the present invention is described with reference to flowchart illustrations and/or block diagrams of a method, apparatus (system), and computer program product according to embodiment 1 of the present invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种拥塞处理方法及设备，包括：移动性管理实体在接收用户设备发起的附着请求消息后，确定用户设备的签约接入点名称；移动性管理实体确定签约接入点名称中处于拥塞的接入点名称；移动性管理实体在返回用户设备的消息中指示签约接入点名称中处于拥塞的接入点名称，以及指示对处于拥塞的接入点名称设置会话管理退避定时器，从而能够针对现有技术的不合理之处提出改进，能够尽量减少网络中的信令资源消耗，又能保证正常业务的运行。

Description

一种拥塞处理方法及设备 本申请要求在 2010年 9月 30日提交中国专利局、申请号为 201010504059.6、 发明名称为"一种机器类通信中的拥塞处理方法及设备"的中国专利申请的优 先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及机器类通信技术， 特别涉及一种拥塞处理方法及设备。 背景技术
在现有的机器类通信 ( Machine Type Communications, MTC )技术中， 由于机器类通信设备（MTC Device ) 的数量众多， 需要考虑到由此产生的大 量的信令和数据传输可能带来的网络拥塞， 因此在第 3 代合作项目 （3rd Generation partnership project, 3 GPP ) 中， 提出了 3GPP 网络的拥塞控制 ( Congestion Control )特性。
在 SA2#80此会议上， NTT DoCoMo提出了一种基于接入点名称（ Access Point Name, APN ) 的拥塞控制 （ congestion control ) 的方法， 用来避免和解 决与特定的 APN相关的拥塞。 网络根据判断某个 APN是否拥塞， 来启动退 避定时器（ back-off timer ), 包括移动性管理退避定时器（ Mobility Management back-off timer )和会话管理退避定时器 ( Session Management back-off timer ), 指示 MTC Device在 back-off timer超时之前， 不能发起任何演进分组系统移 动性管理 ( EPS Mobility Management, EMM; Evolved Packet System, EPS ) 或 EPS系统的会话管理（EPS Session Management, ESM )的请求。 具体实现 的步骤为：
1. 移动性管理实体（Mobility Management Entity, MME )根据一定的标 准来检测基于 APN的 congestion, 标准包括：
a. 每个 APN ( Per APN )的激活的 EPS承载（ EPS Bearer )的最大数目； b. Per APN的 EPS Bearer的激 速率；
c. MME到一个或多个分组数据网络网关（ PDN Gateway, PGW; Packet Data Network, PDN ) 不可达， 或者收到来自这些 PDN GW 的 congestion indication;
当针对某一个 APN 的 congestion 发生时， MME 存储一个 Mobility
Management back-off timer (针对 EPS Mobility Management过程, 1"列 ^口 l1付着 ( Attach )过程，跟踪区更新（ Traking Area Update , TAU )过程）和一个 Session Management back-off timer (针对 EPS Session Management过程 , 1"列 ^口 PDN连 接请求（ PDN Connectivity Request )过程）， 如果用户设备 ( User Equipment, UE )在这些 timer超时之前， 发起到此 APN的接入或连接请求， 网络应该拒 绝。 具体分为：
a. 当 Attach或 TAU过程中请求的 APN是处于拥塞状态 , 则 MME应该 巨绝该过程， 并启动 Mobility Management back-off timer , 同时指示 UE在该 timer超时之前， 不能发起任何 Mobility Management过程。
b. UE发起的 PDN Connectivity Request过程， 携带 APN, 如果没有携带
APN, 则使用签约数据里默认 APN ( default APN ), 如果判断使用的 APN处 于拥塞状态， MME应该拒绝 PDN Connectivity Request消息，并指示 UE启动 Session Management back-off timer, 在 J¾ timer超时之前， UE不能发起对应 J¾ APN的 PDN Connectivity Request过程。
现有技术中， 网络在拒绝 Attach过程后， 需要在一段时间内保留 UE的 签约信息。
现有技术存在的不足在于： 基于 APN的 congestion control的方案中， 当 一个 UE签约了多个 APN, 在其中一个 APN发生拥塞时， 将会妨碍 UE获得 正常的服务。 发明内容
本发明所解决的技术问题在于提供了一种拥塞处理方法及设备， 用以解 决现有技术中当 UE签约了多个 ΑΡή时， 在基于 ΑΡΝ的 congestion control 的方案进行处理过程中妨碍 UE获得正常服务的问题。
本发明实施例中提供了一种拥塞处理方法， 包括如下步骤：
移动性管理实体 MME 在接收用户设备 UE 发起的附着请求 Attach Request消息后， 确定 UE的签约接入点名称 APN;
MME确定签约 APN中处于拥塞的 APN;
MME在返回 UE的消息中指示签约 APN中处于拥塞的 APN, 以及指示 对处于拥塞的 APN设置会话管理退避定时器 Session Management back-off timer„
本发明实施例中提供了一种拥塞处理方法， 包括如下步骤：
UE向 MME发送 Attach Request消息；
UE接收 MME返回的消息，所述消息中指示了 UE的签约 APN中处于拥 塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer;
UE对处于拥塞的 APN设置 Session Management back-off timer。
本发明实施例中提供了一种移动性管理实体设备， 包括：
APN确定模块， 用于在接收 UE发起的 Attach Request消息后， 确定 UE 的签约 APN;
拥塞确定模块， 用于确定签约 APN中处于拥塞的 APN;
指示模块， 用于在返回 UE的消息中指示签约 APN中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
本发明实施例中提供了一种用户设备， 包括：
发送模块， 用于向 MME发送 Attach Request消息；
接收模块， 用于接收 MME返回 UE的消息， 所述消息中指示了 UE的签 约 APN 中处于拥塞的 APN , 以及指示对处于拥塞的 APN设置 Session Management back-off timer;
拥塞处理模块，用于对处于拥塞的 APN设置 Session Management back-off timer„
本发明有益效果如下：
在本发明实施例提供的技术方案中， MME 在接收 UE 发起的 Attach Request消息后，确定 UE的签约 APN中处于拥塞的 APN,并向 UE指示签约 APN 中处于拥塞的 APN , 以及指示对处于拥塞的 APN 设置 Session Management back-off timer。 由于 UE在发起 Attach Request消息后， 便可以获 知签约 APN中处于拥塞的 APN, 从而能够釆取相应的后续流程， 不会因一个 APN处于拥塞而导致不能发起 Attach请求， 也不会在虽然成功附着后因为别 的签约 APN拥塞而被网络拒绝。 因此克服了当 UE签约了多个 APN时妨碍 UE获得正常服务的问题。
进一步的， 在 UE正常 Attach之后， 如果 UE能够获得签约 APN中所有 处于拥塞的 APN 的信息， 便可以避免 UE 向这些 APN发起 EPS Session Management过程， 从而避免不必要的信令浪费。
可见， 本发明实施例提供的技术方案能够针对现有技术的不合理之处提 出改进， 能够尽量减少网络中的信令资源消耗， 又能保证正常业务的运行， 提高用户体验。 附图说明
图 1为本发明实施例中 ΜΜΕ侧的拥塞处理方法实施流程示意图； 图 2为本发明实施例中 UE侧的拥塞处理方法实施流程示意图； 图 3为本发明实施例中 UE使用 default ΑΡΝ来建立 PDN连接的拥塞处理 方法实施流程示意图；
图 4为本发明实施例中 UE 希望提供 APN的拥塞处理方法实施流程示意 图；
图 5为本发明实施例中移动性管理实体设备结构示意图；
图 6为本发明实施例中用户设备结构示意图。 具体实施方式 5
发明人在发明过程中注意到：
在 MTC技术中， 由于 MTC Device的数量众多，如果大量的 MTC Device 同时与网络进行信令交互或数据传输， 可能会产生网络拥塞。 网络的拥塞可 以分为用户面拥塞和信令面拥塞。 一旦网络拥塞发生， 网络应该拒绝相应的 信令连接请求或数据传输请求。 现有协议中， 存在一种基于 APN的拥塞控制 的方法， 提出在 Attach过程中， 如果请求的 APN发生了拥塞， 则拒绝 Attach 过程， 同时启动一个 back-off timer, 在此定时器超时之前， MTC Device不能 发起任何 Mobility Management请求， 即不能再发起 Attach过程。
在长期演进（Long Term Evolution, LTE ) 系统中， Attach过程必须要建 立一个 PDN连接，这就要求 UE发起 Attach过程的同时，发起 PDN Connectivity Request过程， 在现有的 Attach过程中， UE在 Attach Request消息的 ESM消 息容器信息单元 ( ESM message container IE; Information Element, IE ) 中捎 带 PDN Connectivity Request消息，此时 PDN Connectivity Request消息不能携 带 APN, 这样网络可以使用 UE签约的 default APN来发起 PDN Connectivity Request过程。
如果 UE希望提供 APN, 则需要在 PDN Connectivity Request消息中设置 ESM信息传送标志（ ESM information transfer flag ),这样 MME会在安全上下 文（ Security Context )建立之后发起 ESM信息请求（ ESM Information Tequest ) 过程， 然后 UE会在 ESM信息响应（ ESM Information Response )消息中提供 APN。 如果网络允许使用该 APN, 则使用该 APN来发起 PDN Connectivity Request过程。
然而， 当一个 UE可能签约了多个 APN , UE发起 Attach过程时， 可能 使用的 APN正处于拥塞状态， 但是对于其他 APN, 可能其处于正常状态， 以 及建立的 PDN连接所使用的 APN没有发生拥塞， 但是 UE签约的其他 APN 正在发生拥塞， 基于 APN的 congestion control的方法就不能很好的工作， 例 如至少存在以下 2个不合适的场景： 1、在现有的 Attach过程中， UE6可以使用 default APN来建立 PDN连接， 也可以使用其他 APN来建立 PDN连接， 如果按照 NTT Docomo的方法来设 置 Mobility Management backoff timer , 阻止 UE 后续发起的 Mobility Management过程， 那么只要 UE发起的 Attach过程中请求的 APN处于拥塞 状态， 那么 UE将在整个 backoff timer时间内， 都不能接入网络， 即使 UE签 约的其他 APN没有发生拥塞， UE也不能获得相应的服务。 因此该方法妨碍 了 UE获取正常的服务。
2、 如果 UE发起 Attach过程中， 建立的 PDN连接所使用的 APN没有发 生拥塞，但是 UE签约的其他 APN正在发生拥塞，在现有方法中， UE在 Attach 过程结束后并不能知道其他 APN是否处于拥塞状态， 因此 UE可能很快发起 了对应正处于拥塞状态的 APN的附加 PDN连接 ( additional PDN connection ) 的建立过程， 而该过程会被网络拒绝， 浪费信令资源。
可见， 一个 UE可能签约了多个 APN, UE发起 Attach过程时， 可能使用 的 APN正处于拥塞状态， 但是对于其他 APN, 可能其处于正常状态， 而 UE 可能在 Attach过程被拒绝之后，希望尝试对应其他非拥塞 APN的 Attach过程 以获得对应这些 APN 的服务， 而这现有技术中不能实现， 因为 UE发起的 Attach过程被拒绝后， 任何 Mobility Management过程都被拒绝。 以及建立的 PDN连接所使用的 APN没有发生拥塞， UE可能很快发起了对应正处于拥塞 状态的 APN的 additional PDN connection的建立过程的情况导致被网络拒绝。 本发明实施例中将解决 UE如何在 Attach过程被拒绝之后重新发起对应非拥 塞 APN的 Attach过程， 使得 UE可以及时获得对应其他非拥塞 APN的服务。 下面结合附图对本发明的具体实施方式进行说明。
在说明过程中， 首先分别从 MME侧与 UE侧的实施进行说明， 最后再对 二者的配合实施进行说明， 但这并不意味着二者必须配合实施， 实际上， 当 MME与 UE分开实施时， 也解决了分别在 MME侧、 UE侧所存在的问题， 只是二者结合使用时， 会获得更好的技术效果。
图 1为 MME侧的拥塞处理方法实施流程示意图，如图 1所示，可以包括 如下步骤： 7
步骤 101、 MME在接收 UE发起的 Attach Request消息后， 确定 UE的签 约 APN;
步骤 102、 MME确定签约 APN中处于拥塞的 APN;
步骤 103、 MME在返回 UE的消息中指示签约 APN中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
相应的， 本发明实施例中还提供了 UE侧的拥塞处理方案。
图 2为 UE侧的拥塞处理方法实施流程示意图，如图 2所示， 可以包括如 下步骤：
步骤 201、 UE向 MME发送 Attach Request消息；
步骤 202、 UE接收 MME返回 UE的消息，所述消息中指示了 UE的签约 APN 中处于拥塞的 APN , 以及指示对处于拥塞的 APN 设置 Session Management back-off timer;
步骤 203、UE对处于拥塞的 APN设置 Session Management back-off timer。 可见， 在本方案中， UE在发起 Attach Request消息后， 便可以获知签约 APN 中处于拥塞的 APN, 也因而能够釆取相应的后续流程， 而不会因一个 APN处于拥塞而导致不能发起 Attach请求， 也不会在虽然成功附着后因为别 的签约 APN拥塞而被网络拒绝。
下面对当一个 UE可能签约了多个 APN, UE发起 Attach过程时，可能使 用的 APN正处于拥塞状态， 但是对于其他 APN, 可能其处于正常状态， 以及 建立的 PDN连接所使用的 APN没有发生拥塞， 但是 UE签约的其他 APN正 在发生拥塞时， 基于 APN的 congestion control的方法就不能很好的工作的场 景的实施来阐述本发明方案的实施。 但是釆用下述的两种实施方式来说明仅 仅是因为在这两种情况下基于 APN的 congestion control的方法不能很好的工 作这一问题表现得较为突出； 但是， 从理论上来说， 在其他情况下也是可以 使用本发明实施例中提供的技术方案的， 只要能够在 UE发起 Attach后， 告 知 UE签约 APN的状态， 以便于 UE进行后续流程即可， 下述的两种方式仅 用于教导本领域技术人员具体如何 施本发明， 但不意味仅能在这两种场景 中使用， 实施过程中可以结合实践需要来确定相应的流程改进。
方式一：
该方式是以 UE使用 default APN来建立 PDN连接为例进行说明的。 下面先从 MME侧的实施进行说明。
实施中， MME可以在返回 UE的附着拒绝（Attach Reject ) 消息中指示 签约 APN 中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
实施中，在 UE发起 Attach过程中， UE没有在 Attach Request消息的 ESM message container 的 PDN Connectivity Request 消息中携带 APN 或 ESM information transfer flag时， MME可以在返回 UE的 Attach Reject消息中进行 指示， 并拒绝 UE的 Attach过程。
下面再从 UE侧相应的实施进行说明。
实施中， UE在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中没有携带 APN或 ESM information transfer flag。
实施中， MME返回 UE的消息是 Attach Reject消息。
实施中， 还可以进一步包括：
UE确定处于拥塞与不拥塞的 APN;
UE选择不拥塞的 APN发起 Attach请求， 或者在拥塞的 APN的 Session Management back-off timer超时后发起 Attach请求。
实施中， UE发起 Attach请求完成后， 还可以进一步包括：
UE不选择未超时的 Session Management backoff timer对应的 APN发起 PDN Connectivity Request„
在该方式中， 1、 UE发起 Attach过程， 并且不向网络提供 APN, 也不在 Attach Request消息的 ESM message container的 PDN Connectivity Request消 息中携带 ESM information transfer flag; 网络使用 default APN发起 PDN Connectivity Request过程，由于 default APN正处于拥塞^ 态，网络拒绝 Attach 过程， 但在拒绝消息中携带 UE签约 9的各个处于拥塞状态的 APN的 Session Management backoff timer, 也不启动 Mobility Management backoff timer„
2、 UE收到各个处于拥塞状态， 且签约的 APN的 Session Management backoff timer, 启动相应的 timer, 然后查看签约的 APN中是否有不处于拥塞 状态的， 如果有， 则使用此 APN再次发起 Attach过程； 如果没有， 则 UE需 要等到有 APN的 Session Management backoff timer超时再发起 Attach过程。
3、 UE使用不处于拥塞状态的 APN发起 Attach过程。
4、 Attach完成之后， UE不能发起对应 Session Management backoff timer 未超时的 APN的 PDN Connectivity Request。
下面以实例进行说明。
实施例 1 :
图 3为 UE使用 default APN来建立 PDN连接的拥塞处理方法实施流程示 意图， 图中 new MME为 UE发起附着请求的新 MME, old MME为之前为的 UE提供服务的 MME; 如图 3所示， 在该过程中可以包括如下流程：
步骤 301、 UE向 eNB发送 Attach请求消息；
步骤 302、 eNB向 new MME发送 Attach请求消息；
步骤 303、 new MME向 old MME发送识别请求消息；
步骤 304、 old MME向 new MME发送识别响应消息；
步骤 305、 new MME向 UE发送识别请求消息；
步骤 306、 UE向 new MME发送识别响应消息；
步骤 307、 鉴权、 安全性认证等；
步骤 308-309、 UE、 new MME、设备识别登录器（ Equipment Identification
Register, EIR )之间进行识别过程， 其中 ME Identity Check为移动设备标识 检查；
步骤 310、 new MME向 UE发送加密选项请求消息；
步骤 311、 UE向 new MME发送加密选项响应消息；
步骤 312、 new MME向 SGW发送删除会话请求消息； 步骤 313、 SGW向 new MME ¾1删除会话响应消息；
步骤 314、 new MME向归属用户服务器（ Home Subscriber Server, HSS ) 发送位置更新请求消息；
步骤 315、 HSS向 old MME发送位置消除消息；
步骤 316、 old MME向 HSS返回位置消除确认消息；
步骤 317、 old MME向 PGW发送删除会话请求消息；
步骤 318、 PGW向 old MME发送删除会话响应消息；
步骤 319、 HSS向 new MME发送位置更新确认消息；
步骤 320、 new MME向 UE发送 Attach拒绝消息；
步骤 321、 UE判断是否有不处于拥塞的 APN;
步骤 322、 UE向 new MME发送 Attach请求消息。
在上述过程中， MME和 UE的行为可以按如下方式实施：
1、 UE发起 Attach过程,在 ESM message container中的 PDN connectivity
Request中不带 APN, 也不带 ESM information transfer flag„
2、 MME取得 UE的签约信息， 得到 UE签约的 default APN, 但是发现 default APN正处于拥塞状态， 则拒绝 Attach过程。
3、 MME在 Attach Reject消息中返回 UE签约的处于拥塞状态的 APN和 对应的 Session backoff timer, 实施中， 其消息格式可以在如下的消息格式中 增加加粗示意的部分为：
This message is sent by the network to the UE to indicate that the corresponding attach request has been rejected. See table 8.2.3.1.
Message type： ATTACH REJECT
Significance: dual
Direction: network to UE
Table 8.2.3.1 : ATTACH REJECT message content
Figure imgf000012_0001
其中， Session backoff Timer List表示会话退避定时器列表， Backoff Timer
List x.x表示退避定时器列表， O表示可选， TLV表示类型 -长度 -值, 信元长度。
实施中， Backoff Timer List的定义可以如下：
Backoff Timer list IE (退避定时器列表信息单元） octet 1
Length of Backoff Timer List (退避定时器列表长度） octet 2-3
Access point name 1 (接入点名称 1 ) octet 4 octet i
Backoff Timer 1 (退避定时器 1 ) octet i+1
octet i+2 octet i+3 octet j
Access point name n (接入点名称 n ) octet j+1 octet k
Backoff Timer n (接入点名称 n ) octet k+1
octet k+2 实施中， Backoff Timer可以釆用 TS 24.008里 10.5.7.3节的 GPRS Timer 的定义 （具体可以参见 Figure 10.5.146/3GPP TS 24.008: GPRS Timer information element ): 8 7 6 512 4 3 2 1
GPRS Timer IEI octet 1
Unit Timer value octet 2 实施中， Access point name可以釆用 TS24.008里 10.5.6.1节的定义（具 体可以参见 Figure 10.5.152/3GPP TS 24.008: Access point name information element )
8 7 6 5 4 3 2 1
Access point name IEI octet 1
Length of access point name contents octet 2
Access point name value octet 3
I octet n*
4、 UE 收到签约的各个处于拥塞状态的 APN 的 Session Management backoff timer, 启动相应的 timer, 然后查看签约的 APN中是否有不处于拥塞 状态的， 如果有， 则使用此 APN再次发起 Attach过程； 如果没有， 则 UE需 要等到有 APN的 Session Management backoff timer超时再发起 Attach过程。
5、 根据第 4点中确定的 APN, UE重新发起 Attach过程。
方式二：
该方式是以 UE 希望提供 APN,在 PDN Connectivity Request消息中设置 ESM information transfer flag为例进行说明的。
下面先从 MME侧的实施进行说明。
实施中， UE可以在发起的 Attach Request消息的 ESM message container 的 PDN Connectivity Request消息中携带 ESM information transfer flag;
MME可以在返回 UE的 ESM information Request消息中指示签约 APN 中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
实施中， 还可以进一步包括：
在 UE返回 MME的 ESM information Response消息中携带有 APN时， MME用 UE返回 MME的 ESM information Response消息中携带的 APN为 UE完成 PDN Connectivity Request过程；
在 UE返回 MME的 ESM information Response消息中没有携带有 APN时， MME拒绝 UE的 Attach过程。
实施中 , MME拒绝 UE的 Attach过程时， 还可以进一步包括：
MME不启动 Mobility Management backoff timer。
下面再从 UE侧相应的实施进行说明。
实施中， UE可以在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中携带 ESM information transfer flag。
实施中， MME返回 UE的消息可以是 ESM information Request消息。 实施中， 还可以进一步包括：
UE确定处于拥塞与不拥塞的 APN;
UE选择一个不拥塞的 APN, 并在 ESM information Response消息中携带 该 APN后向 MME上报； 若没有不拥塞的 APN, 则不在 ESM information Response消息中携带 APN。
实施中，若 ESM information Response消息中没有携带 APN,还可以进一 步包括：
在拥塞的 APN的 Session Management back-off timer超时后发起 Attach请 求。
实施中， UE发起 Attach请求完成后， 还可以进一步包括：
UE不选择未超时的 Session Management backoff timer对应的 APN发起
PDN Connectivity Request„
在该方式中， 1、 UE发起 Attach过程， 在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中携带 ESM information transfer flag。
2、 MME收到 ESM information transfer flag并取得 UE的签约数据之后， 检查 UE签约的 APN是否有处于拥塞状态， 如果有则在 ESM information request过程中将各个处于拥塞状态的 APN的 Session backoff timer传递给 UE。 3、 UE收到 ESM information request过程中各个处于拥塞状态的 APN的 Session backoff timer之后， 启动相应的 timer, 然后查看签约的 APN中是否有 不处于拥塞状态的， 如果有， 则在 ESM INFORMATION RESPONSE消息中 将选取的一个不处于拥塞状态的 APN上报给 MME; 如果没有， 则不带。
4、 MME如果在 ESM Information Response消息中收到 APN, 则使用此 APN完成 PDN Connectivity Request过程， 否则 MME使用 default APN发起 PDN Connectivity Request过程， 此时 default APN处于拥塞状态， MME将拒 绝 Attach过程， 此时 MME可以也可以不启动 Mobility Management backoff timer„
5、如果 UE在第 4点中没有提供 APN给 MME, 则 UE需等到有 APN的 Session backoff timer超时之后 , 如果有 Mobility Management backoff timer启 动， 也要等该 timer超时之后， 重新发起第 1点中的 Attach过程。
6、 Attach完成之后， UE不能发起对应 Session Management backoff timer 未超时的 APN的 PDN Connectivity Request。
下面以实例进行说明。
实施例 2:
图 4为 UE 希望提供 APN的拥塞处理方法实施流程示意图， 如图所示， 图中 new MME为 UE发起附着请求的新 MME, old MME为之前为的 UE提 供服务的 MME; 如图 4所示， 在该过程中可以包括如下流程：
步骤 401、 UE向 eNB发送 Attach请求消息；
步骤 402、 eNB向 new MME发送 Attach请求消息；
步骤 403、 new MME向 old MME发送识别请求消息；
步骤 404、 old MME向 new MME发送识别响应消息；
步骤 405、 new MME向 UE发送识别请求消息；
步骤 406、 UE向 new MME发送识别响应消息；
步骤 407、 鉴权、 安全性认证等；
步骤 408-409、 UE、 new MME、 EIR之间进行识别过程； 步骤 410、 new MME向 UE发 ii5加密选项消息；
步骤 411、 UE向 new MME发送加密选项响应消息；
步骤 412、 new MME向 SGW发送删除会话请求消息；
步骤 413、 SGW向 new MME发送删除会话响应消息；
步骤 414、 new MME向 HSS发送位置更新请求消息；
步骤 415、 HSS向 old MME发送位置消除消息；
步骤 416、 old MME向 HSS返回位置消除确认消息；
步骤 417、 old MME向 PGW发送删除会话请求消息；
步骤 418、 PGW向 old MME发送删除会话响应消息；
步骤 419、 HSS向 new MME发送位置更新确认消息；
步骤 420、 new MME向 UE发送 ESM information request消息；
步骤 421、 UE判断是否有不处于拥塞的 APN;
步骤 422、 UE向 new MME发送 ESM information response消息； 步骤 423-424、 UE与 new MME之间的 Attach接受或者拒绝， 以及 UE 在发起的请求过程。
在上述过程中， MME和 UE的行为可以按如下方式实施：
1. UE发起 Attach过程，在 Attach Request消息的 ESM message container 的 PDN Connectivity Request消息中携带 ESM information transfer flag。
2. MME收到 ESM information transfer flag。
3. MME从 HSS取得 UE的签约信息， 检查 UE签约的 APN是否有处于 拥塞状态。
4.如果 MME发现有处于拥塞状态的 APN,则在 ESM information request 过程中将各个处于拥塞状态的 APN 的 Session backoff timer 通过 ESM INFORMATION REQUEST消息传递给 UE, 实施中， 其消息格式可以在如下 的消息格式中增加加粗示意的部分为：：
This message is sent by the network to the UE to request the UE to provide ESM information, i.e. protocol configuration options or APN or both. See table 8.3.13.1.
Message type: ESM INFORMATION REQUEST
Significance: dual
Direction: network to UE
Table 8.3.13.1 : ESM INFORMATION REQUEST message content
Figure imgf000017_0001
其中， Session backoff Timer List表示会话退避定时器列表， Backoff Timer List x.x表示退避定时器列表， O表示可选， TLV表示类型 -长度 -值， X表示 信元长度。
实施中， Backoff Timer List的定义可以如下：
8 7 6 4 3 2 1
Backoff Timer list IE (退避定时器列表信息单元） octet 1
Length of Backoff Timer List (退避定时器列表长度） octet 2-3
Access point name 1 (接入点名称 1 ) octet 4 octet i
Backoff Timer 1 (退避定时器 1 ) octet i+1
octet i+2 octet i+3 octet j
Access point name n (接入点名称 n ) octet j+1 octet k
Backoff Timer n (接入点名称 n ) octet k+1
octet k+2 实施中， Backoff Timer可以釆用 TS 24.008里 10.5.7.3节的 GPRS Timer 的定义 （具体可以参见 Figure 10.5.146/3GPP TS 24.008: GPRS Timer information element ):
8 7 6 5 4 3 2 1
GPRS Timer IEI octet 1
Unit Timer value octet 2 实施中， Access point name可以釆用 TS24.008里 10.5.6.1节的定义（具 体可以参见 Figure 10.5.152/3GPP TS 24.008: Access point name information element )
8 7 6 5 4 3 2 1
Access point name IEI octet 1
Length of access point name contents octet 2
Access point name value octet 3
I octet n*
5. UE 收到签约的各个处于拥塞状态的 APN 的 Session Management backoff timer , 启动相应的 timer。
6. 在第 5点中，如果 UE签约的 APN中有不处于拥塞状态的，则在 ESM INFORMATION RESPONSE消息中携带此 APN , 否则不带。 7.如果 ESM INFORMATION RESPONSE消息中携带 APN,则 MME使用 此 APN完成 PDN Connectivity Request过程； 否则 MME可以启动 Mobility Management backoff timer, 同时 Reject Attach过程。
8. 如果 Attach过程被拒绝， UE可以等到有 APN的 Session Management backoff timer超时后，再发起 Attach过程，使用此 APN完成 PDN Connectivity Request过程。
基于同一发明构思， 本发明实施例中还提供了一种移动性管理实体设备、 用户设备， 由于这些设备解决问题的原理与本发明实施例的拥塞处理方法相 似， 因此这些设备的实施可以参见方法的实施， 重复之处不再赘述。
图 5为移动性管理实体设备结构示意图，如 5图所示，ΜΜΕ中可以包括：
ΑΡΝ确定模块 501 , 用于在接收 UE发起的 Attach Request消息后， 确定 UE的签约 APN;
拥塞确定模块 502, 用于确定签约 APN中处于拥塞的 APN;
指示模块 503 , 用于在返回 UE 的消息中指示签约 APN 中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
实施中，指示模块还可以进一步用于在返回 UE的 Attach Reject消息中指 示签约 APN中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
实施中， 指示模块还可以进一步用于在 UE发起 Attach过程中， UE没有 在 Attach Request消息的 ESM message container的 PDN Connectivity Request 消息中携带 APN或 ESM information transfer flag时，在返回 UE的 Attach Reject 消息中进行指示。
实施中， MME中还可以进一步包括：
附着处理模块 504 , 用于在返回 Attach Reject消息时， 拒绝 UE的 Attach 过程。
实施中， 指示模块还可以进一步用于在 UE发起的 Attach Request消息的 ESM message container 的 PDN Connectivity Request 消息中携带有 ESM information transfer flag时, 在返回 UE的 ESM information Request消息中指 示签约 APN中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
实施中， MME中还可以进一步包括：
附着处理模块 504, 用于在 UE返回 MME的 ESM information Response 消息中携带有 APN时， 用 UE返回的 ESM information Response消息中携带 的 APN为 UE完成 PDN Connectivity Request过程；在 UE返回 MME的 ESM information Response消息中没有携带有 APN时， 拒绝 UE的 Attach过程。
实施中， 附着处理模块还可以进一步用于在拒绝 UE的 Attach过程时， 不启动 Mobility Management backoff timer。
图 6为用户设备结构示意图， 如图所示， UE中可以包括：
发送模块 601 , 用于向 MME发送 Attach Request消息；
接收模块 602, 用于接收 MME返回 UE的消息， 所述消息中指示了 UE 的签约 APN中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer;
拥塞处理模块 603 , 用于对处于拥塞的 APN设置 Session Management back-off timer。
实施中， 发送模块还可以进一步用于不在 Attach Request 消息的 ESM message container 的 PDN Connectivity Request 消息中携带 APN 或 ESM information transfer flag。
实施中 , 接收模块还可以进一步用于接收 MME返回 UE的 Attach Reject 消息。
实施中，拥塞处理模块还可以进一步用于确定处于拥塞与不拥塞的 APN; 选择不拥塞的 APN 发起 Attach 请求， 或者在拥塞的 APN 的 Session Management back-off timer超时后发起 Attach请求。
实施中， 拥塞处理模块还可以进一步用于在发起 Attach请求完成后， 不 选择未超时的 Session Management backoff timer 对应的 APN 发起 PDN Connectivity Request。
实施中， 发送模块还可以进一步用于在 Attach Request 消息的 ESM message container的 PDN Connectivity Request消息中携带 ESM information transfer flag。
实施中， 接收模块还可以进一步用于接收 MME 返回 UE 的 ESM information Request消息。
实施中，拥塞处理模块还可以进一步用于确定处于拥塞与不拥塞的 APN; 选择一个不拥塞的 APN, 并在 ESM information Response消息中携带该 APN 后向 MME上报； 若没有不拥塞的 APN, 则不在 ESM information Response消 息中携带 APN。
实施中， 拥塞处理模块还可以进一步用于若不在 ESM information Response消息中携带 APN, 在拥塞的 APN的 Session Management back-off timer超时后发起 Attach请求。
实施中， 拥塞处理模块还可以进一步用于在发起 Attach请求完成后， 不 选择未超时的 Session Management backoff timer 对应的 APN 发起 PDN Connectivity Request。
为了描述的方便， 以上所述装置的各部分以功能分为各种模块或单元分 别描述。 当然， 在实施本发明时可以把各模块或单元的功能在同一个或多个 软件或硬件中实现。
由上述可知， 本发明实施例提供的技术方案能够针对现有技术的不合理 之处， 提出了改进， 能够尽量减少网络中的信令资源消耗， 又能保证正常业 务的运行， 提高用户体验。
本领域内的技术人员应明白， 本发明的实施例可提供为方法、 系统、 或 计算机程序产品。 因此， 本发明可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实施例的形式。 而且， 本发明可釆用在一个或多个 其中包含有计算机可用程序代码的计算机可用存储介质 (包括但不限于磁盘 存储器、 CD-ROM、 光学存储器等）上实施的计算机程序产品的形式。 本发明是参照根据本发明实施 1的方法、 设备（系统）、 和计算机程序产 品的流程图和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图 和 /或方框图中的每一流程和 /或方框、 以及流程图和 /或方框图中的流程 和 /或方框的结合。 可提供这些计算机程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器， 使得通 过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流 程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设 备以特定方式工作的计算机可读存储器中， 使得存储在该计算机可读存储器 中的指令产生包括指令装置的制造品， 该指令装置实现在流程图一个流程或 多个流程和 /或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上， 使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的 处理， 从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图 一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的步 骤。
尽管已描述了本发明的优选实施例， 但本领域内的技术人员一旦得知了 基本创造性概念， 则可对这些实施例作出另外的变更和修改。 所以， 所附权 利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。 发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 莉 要 求
1、 一种拥塞处理方法， 其特征在于， 包括如下步骤：
移动性管理实体 MME 在接收用户设备 UE 发起的附着请求 Attach Request消息后， 确定 UE的签约接入点名称 APN;
MME确定签约 APN中处于拥塞的 APN;
MME在返回 UE的消息中指示签约 APN中处于拥塞的 APN, 以及指示 对处于拥塞的 APN设置会话管理退避定时器 Session Management back-off timer„
2、 如权利要求 1所述的方法， 其特征在于， 所述消息是附着拒绝 Attach Reject消息。
3、 如权利要求 2所述的方法， 其特征在于， 所述 MME返回消息包括： 在 UE发起 Attach过程中， UE没有在 Attach Request消息的演进分组系 统的会话管理消息容器信息单元 ESM message container的分组数据网络连接 请求 PDN Connectivity Request消息中携带 APN或演进分组系统的会话管理信 息传送标志 ESM information transfer flag时， MME在返回 UE的 Attach Reject 消息中进行指示， 并拒绝 UE的 Attach过程。
4、 如权利要求 1所述的方法， 其特征在于， 若 UE发起的 Attach Request 消息的 ESM message container的 PDN Connectivity Request消息中携带有 ESM information transfer flag , 则所述消息是演进分组系统的会话管理信息请求 ESM information Request消息。
5、 如权利要求 4所述的方法， 其特征在于， 该方法还包括：
在 UE返回 MME的演进分组系统的会话管理信息响应 ESM information Response消息中携带有 APN时， MME用 UE返回的 ESM information Response 消息中携带的 APN为 UE完成 PDN Connectivity Request过程；
在 UE返回 MME的 ESM information Response消息中没有携带有 APN时， MME拒绝 UE的 Attach过程。
6、 如权利要求 2、 3或 5所述 方法， 其特征在于， MME拒绝 UE的 Attach过程进一步包括：
MME不启动 Mobility Management backoff timer„
7、 一种拥塞处理方法， 其特征在于， 包括如下步骤：
UE向 MME发送 Attach Request消息；
UE接收 MME返回的消息，所述消息中指示了 UE的签约 APN中处于拥 塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer;
UE对处于拥塞的 APN设置 Session Management back-off timer„
8、如权利要求 Ί所述的方法 ,其特征在于 ,所述 UE向 ΜΜΕ发送 Attach
Request消息包括：
UE在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中不携带 APN或 ESM information transfer flag„
9、 如权利要求 8所述的方法， 其特征在于， 所述 MME返回 UE的消息 是 Attach Rej ect消息。
10、 如权利要求 7至 9任一所述的方法， 其特征在于， 该方法还包括： UE确定处于拥塞与不拥塞的 APN;
UE选择不拥塞的 APN发起 Attach请求， 或者在拥塞的 APN的 Session Management back-off timer超时后发起 Attach请求。
11、 如权利要求 10所述的方法， 其特征在于， UE发起 Attach请求完成 后， 还包括：
UE不选择未超时的 Session Management backoff timer对应的 APN发起 PDN Connectivity Request„
12、如权利要求 Ί所述的方法，其特征在于，所述 UE向 ΜΜΕ发送 Attach Request消息包括：
UE在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中携带有 ESM information transfer flag。
13、 如权利要求 12所述的方法 其特征在于， 所述 ΜΜΕ返回 UE的消 息是 ESM information Request消息。
14、 如权利要求 7或 12或 13所述的方法， 其特征在于， 该方法还包括： UE确定处于拥塞与不拥塞的 APN;
UE选择一个不拥塞的 APN, 并在 ESM information Response消息中携带 该 APN后向 MME上报； 若没有不拥塞的 APN, 则不在 ESM information Response消息中携带 APN。
15、 如权利要求 14所述的方法， 其特征在于， 该方法还包括：
若 ESM information Response消息中没有携带 APN, UE在拥塞的 APN 的 Session Management back-off timer超时后发起 Attach请求。
16、 如权利要求 15所述的方法， 其特征在于， 所述 UE发起 Attach请求 完成后， 还包括：
UE不选择未超时的 Session Management backoff timer对应的 APN发起 PDN Connectivity Request„
17、 一种移动性管理实体设备， 其特征在于， 包括：
APN确定模块， 用于在接收 UE发起的 Attach Request消息后， 确定 UE 的签约 APN;
拥塞确定模块， 用于确定签约 APN中处于拥塞的 APN;
指示模块， 用于在返回 UE的消息中指示签约 APN中处于拥塞的 APN, 以及指示对处于拥塞的 APN设置 Session Management back-off timer。
18、 如权利要求 17所述的设备， 其特征在于， 所述指示模块具体用于： 在返回 UE的 Attach Reject消息中指示签约 APN中处于拥塞的 APN, 以 及指示对处于拥塞的 APN设置 Session Management back-off timer。
19、 如权利要求 18所述的设备， 其特征在于， 所述指示模块具体用于： 在 UE发起 Attach过程中， UE没有在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中携带 APN或 ESM information transfer flag时， 在返回 UE的 Attach Reject消息中进行指示。
20、 如权利要求 19所述的设备 其特征在于， 所述设备还包括： 附着处理模块， 用于在返回 Attach Reject消息时， 拒绝 UE的 Attach过 程。
21、 如权利要求 17所述的设备， 其特征在于， 所述指示模块具体用于： 在 UE发起的 Attach Request 消息的 ESM message container 的 PDN
Connectivity Request消息中携带有 ESM information transfer flag时, 在返回 UE的 ESM information Request消息中指示签约 APN中处于拥塞的 APN, 以 及指示对处于拥塞的 APN设置 Session Management back-off timer。
22、 如权利要求 21所述的设备， 其特征在于， 所述设备还包括： 附着处理模块， 用于在 UE返回 MME的 ESM information Response消息 中携带有 APN时，用 UE返回的 ESM information Response消息中携带的 APN 为 UE 完成 PDN Connectivity Request 过程； 在 UE返回 MME 的 ESM information Response消息中没有携带有 APN时， 拒绝 UE的 Attach过程。
23、 如权利要求 19或 22所述的设备， 其特征在于， 所述附着处理模块 具体用于：
在巨绝 UE的 Attach过程时， 不启动 Mobility Management backoff timer„
24、 一种用户设备， 其特征在于， 包括：
发送模块， 用于向 MME发送 Attach Request消息；
接收模块， 用于接收 MME返回 UE的消息， 所述消息中指示了 UE的签 约 APN 中处于拥塞的 APN , 以及指示对处于拥塞的 APN设置 Session Management back-off timer;
拥塞处理模块，用于对处于拥塞的 APN设置 Session Management back-off timer„
25、 如权利要求 24所述的用户设备， 其特征在于， 所述发送模块具体用 于：
不在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中携带 APN或 ESM information transfer flag。
26、 如权利要求 25所述的用户 备， 其特征在于， 所述接收模块具体用 于：
接收 MME返回 UE的 Attach Reject消息。
27、 如权利要求 24至 26任一所述的用户设备， 其特征在于， 所述拥塞 处理模块具体用于：
确定处于拥塞与不拥塞的 APN; 选择不拥塞的 APN发起 Attach请求， 或者在拥塞的 APN的 Session Management back-off timer超时后发起 Attach请 求。
28、 如权利要求 27所述的用户设备， 其特征在于， 所述拥塞处理模块具 体用于：
在发起 Attach请求完成后， 不选择未超时的 Session Management backoff timer对应的 APN发起 PDN Connectivity Request。
29、 如权利要求 24所述的用户设备， 其特征在于， 所述发送模块具体用 于：
在 Attach Request消息的 ESM message container的 PDN Connectivity Request消息中携带 ESM information transfer flag。
30、 如权利要求 29所述的用户设备， 其特征在于， 所述接收模块具体用 于：
接收 MME返回 UE的 ESM information Request消息。
31、 如权利要求 24或 29或 30所述的用户设备， 其特征在于， 所述拥塞 处理模块具体用于：
确定处于拥塞与不拥塞的 APN; 选择一个不拥塞的 APN, 并在 ESM information Response消息中携带该 APN后向 MME上报； 若没有不拥塞的 APN , 则不在 ESM information Response消息中携带 APN。
32、 如权利要求 31所述的用户设备， 其特征在于， 所述拥塞处理模块具 体用于：
若不在 ESM information Response消息中携带 APN, 在拥塞的 APN的 Session Management back-off timer超时后发起 Attach请求。
33、 如权利要求 32所述的用户设备， 其特征在于， 所述拥塞处理模块具 体用于：
在发起 Attach请求完成后， 不选择未超时的 Session Management backoff timer对应的 APN发起 PDN Connectivity Request。
PCT/CN2011/080157 2010-09-30 2011-09-26 一种拥塞处理方法及设备 WO2012041198A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010504059.6A CN102448111B (zh) 2010-09-30 2010-09-30 一种机器类通信中的拥塞处理方法及设备
CN201010504059.6 2010-09-30

Publications (1)

Publication Number Publication Date
WO2012041198A1 true WO2012041198A1 (zh) 2012-04-05

Family

ID=45891943

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080157 WO2012041198A1 (zh) 2010-09-30 2011-09-26 一种拥塞处理方法及设备

Country Status (2)

Country Link
CN (1) CN102448111B (zh)
WO (1) WO2012041198A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103079184B (zh) * 2013-01-11 2015-07-08 西安工程大学 一种网络拥塞状态下发送触发消息的方法
CN104185214B (zh) * 2013-05-24 2019-01-11 华为终端有限公司 一种发送上行信令的方法和设备
EP3379890B1 (en) * 2015-11-19 2020-12-02 LG Electronics Inc. -1- Operation method for terminal operating in congested network situation in wireless communication system and apparatus therefor

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATT: "ESM back-off timers for multiple congested APNs", 3GPP TSG-CT WG1 MEETING #70, CL-111072, 14 February 2011 (2011-02-14) *
CATT: "ESM back-off timers for multiple congested APNs", 3GPP TSG-CT WG1 MEETING #70, CL-111073, 14 February 2011 (2011-02-14) *
KPN ET AL.: "NAS level reject per APN with back-off timer function", 3GPP TSG SA WG2 MEETING #80, 24 August 2010 (2010-08-24), pages 2 - 104406 *
NTT DOCOMO: "Discussion on the target procedures for the NAS Back-off Timer", 3GPP TSG SA WG2 MEETING #80, 3 September 2010 (2010-09-03) *

Also Published As

Publication number Publication date
CN102448111B (zh) 2014-09-24
CN102448111A (zh) 2012-05-09

Similar Documents

Publication Publication Date Title
US11863312B2 (en) System, methods, and apparatuses for managing data rate for control plane optimization
JP7154544B2 (ja) 無線通信システムでサービスを制御するための方法
TWI718517B (zh) 用於無線通訊中的會話釋放的方法、電子裝置及存儲器
USRE49636E1 (en) Method and apparatus of improving quality of calls in mobile communication system
EP2536178B1 (en) Methods and apparatuses for processing priority services
KR102151031B1 (ko) 저전력 단말의 통신 효과를 높이는 방법 및 장치
US20080293399A1 (en) Method for supporting MBMS service transmission in LTE system
WO2011082538A1 (zh) 机器型通信中基于组的移动性优化方法和设备
WO2013040978A1 (zh) 数据分流触发方法、网络侧设备和用户设备及网络系统
WO2015062098A1 (zh) 一种网络选择方法及核心网设备
WO2009094837A1 (en) A method for selecting a policy and charging rules function server on a non-roaming scene
WO2012041197A1 (zh) 一种移动性管理过程的处理方法及网络侧装置
US10812536B2 (en) Method and apparatus for providing quality of service for web-based real-time communication
WO2012174943A1 (zh) 一种确定终端状态的方法、装置和系统
WO2012041185A1 (zh) 一种通知能力的方法和网络拥塞控制的方法、系统及设备
WO2013166913A1 (zh) 小量数据上下行传输方法、及相应终端和移动性管理单元
US9049614B2 (en) Method and device for handling mobility management context
WO2012041184A1 (zh) 一种会话管理退避指示方法及网络侧装置、和会话管理退避方法及用户设备
KR102170503B1 (ko) 이동통신시스템에서의 호출장치 및 방법
WO2013097503A1 (zh) 拥塞控制方法和设备
KR20160001569A (ko) 웹 기반 실시간 통신을 위한 서비스품질 제공 방법 및 장치
CN113439458A (zh) 用于连接建立的方法和装置
WO2012041198A1 (zh) 一种拥塞处理方法及设备
WO2012041250A1 (zh) 一种机器类通信中的拥塞处理方法及设备
CN105323806B (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: 11828094

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

Country of ref document: EP

Kind code of ref document: A1