WO2012041197A1 - Procédé et dispositif côté réseau pour le processus de gestion de mobilité - Google Patents

Procédé et dispositif côté réseau pour le processus de gestion de mobilité Download PDF

Info

Publication number
WO2012041197A1
WO2012041197A1 PCT/CN2011/080154 CN2011080154W WO2012041197A1 WO 2012041197 A1 WO2012041197 A1 WO 2012041197A1 CN 2011080154 W CN2011080154 W CN 2011080154W WO 2012041197 A1 WO2012041197 A1 WO 2012041197A1
Authority
WO
WIPO (PCT)
Prior art keywords
apn
mobility management
message
timer
location update
Prior art date
Application number
PCT/CN2011/080154
Other languages
English (en)
Chinese (zh)
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 WO2012041197A1 publication Critical patent/WO2012041197A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/375—Access point names [APN]

Definitions

  • the invention relates to a method for processing a mobility management process and a network side device.
  • the application is submitted to the Chinese Patent Office on September 30, 2010, and the application number is 201010503865.1, and the invention name is "a method for rejecting the mobility management process and a network side device.
  • the priority of the Chinese Patent Application the entire contents of which is incorporated herein by reference.
  • the present invention relates to the field of wireless communication technologies, and in particular, to a method for processing a mobility management process and a network side device. Background technique
  • APN Access Point Name
  • PDN Packet Date Network
  • the network entity is an MME (Mobility Management Entity) or an SGSN (Serving GPRS Support Node), and the gateway node is a PGW (Packet Data Network Gateway) or a GGSN. (Gateway GPRS Support Node, Gateway GPRS Support Node).
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • PGW Packet Data Network Gateway
  • GGSN Gateway GPRS Support Node
  • EPS Evolved Packet System
  • the MME determines whether each APN is congested according to a specific rule. If the APN is congested and congestion control is required, the existing standard defines the APN as the APN for enabling the congestion control mechanism, and the MME determines whether the congestion occurs in each APN, which may be from the PGW.
  • the instructions are known, and can also be judged according to their own rules.
  • the attaching ATTACH process or the TA 2 J process of the UE if the APN that the UE subscribes to activates the congestion control mechanism, the ATTACH request and the TAU (Tracking Area Update procedures) request message are rejected, and the mobility management backoff is carried. The duration information of the timer.
  • the MME After rejecting the ATTACH or TAU request, the MME should retain the subscription data of the UE for a period of time.
  • the main purpose is to refuse to interact with the HSS (Home Subscriber Server, the home subscriber server), and reject the UE from the UE when the APN is still congested.
  • HSS Home Subscriber Server, the home subscriber server
  • the MME receives the PDN connection request sent by the UE, and the PDN connection request may or may not carry the APN. If the APN is not carried, the MME needs to obtain the subscription data of the UE from the HSS. At this time, the MME will learn which APNs the UE has subscribed to, and obtain the default APN of the UE from the subscription data of the UE as the APN requested by the UE. When the APN requested by the UE turns on the congestion control mechanism, the MME rejects the PDW connection request corresponding to the APN requested by the UE. For the PDW that is congested, the MME may also carry the session backoff timer to the UE by rejecting the PDN connection request message. When the MME rejects the connection request of the priority service/emergency call service, the MME shall not instruct the UE to start the session backoff timer.
  • the UE After receiving the mobility management backoff timer information sent by the MME, the UE starts the mobility management backoff timer, and the UE should not initiate any mobility management process before the mobility management backoff timer expires. .
  • the UE After receiving the session management backoff timer sent by the MME, the UE starts the session management backoff timer of the APN, before the session management backoff timer expires:
  • the UE cannot initiate any session management process of the APN, and the UE may initiate a session management process to other APNs that it subscribes to;
  • the UE cannot initiate a session management process that does not include any APN, and the UE may initiate a session management process corresponding to the specific APN, and the specific APN refers to the UE signing the APN except the default APN;
  • the present invention provides a processing method and apparatus for a mobility management process for optimizing a processing method of an existing mobility management process.
  • a method of processing a mobility management process including:
  • the network side sends a mobility management accept message to the UE according to whether the access point name APN enables the congestion control mechanism;
  • a mobility management process backoff method includes:
  • the user equipment UE receives the mobility management acceptance carried by the network side and carries the mobility management backoff timer in the mobility management process; %, package,;
  • the UE starts a mobility management backoff timer, and only initiates a mobility management process related to the priority service or the emergency call service before the mobility management timer expires;
  • the UE determines that the duration of the mobility management backoff timer is greater than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than The periodic tracking timer is started.
  • a processing network side device for a mobility management process comprising:
  • a message sending unit configured to send, in a mobility management process of the user equipment UE, a mobility management accept message to the UE according to whether a different access point name APN enables a congestion control mechanism
  • a timer carrying unit configured to carry a mobility management backoff timer in the sent mobility management accept message.
  • a user equipment UE that implements a mobility management process backoff includes:
  • Receiving a message receiving unit configured to receive, in the mobility management process, a mobility management accept message that is sent by the network side and carries a mobility management backoff timer; a first timer starting unit, configured to start a dynamic management backoff timer, and only initiate a mobility management process related to a priority service or an emergency call service before the mobility management timer expires; a second timer starting unit
  • the duration of the mobility management backoff timer is greater than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than The periodic tracking timer is started.
  • the processing method of the mobility management process and the network side device, the mobility management process backoff method and the user equipment provided by the present invention have the following beneficial effects: the mobility transmitted to the UE by whether the APN is enabled with the information of the congestion control mechanism.
  • the management acceptance message carries the mobility management backoff timer, which can further save resources of the UE and the network side, and has better effect on network congestion control.
  • FIG. 1 is a flowchart of a method for processing a mobility management process according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a mobility management backoff method according to an embodiment of the present invention
  • FIG. 3 is a structural diagram of a network side device for processing a mobility management process according to an embodiment of the present invention
  • FIG. 4 is a structural diagram of a user equipment UE for implementing a mobility management process backoff according to an embodiment of the present invention.
  • the inventors of the present invention have found that the existing mobility management processing method has the following technical drawbacks: For each APN that the UE may activate, the UE should support an independent session backoff management timer. If the UE establishes a connection to the APN, the APN is considered to be activated.
  • the network entity MME can send the mobility management backoff timer duration information to the UE, it is limited to carrying the mobility management in the reject attachment request message and the reject TAU request message.
  • the duration information of the backoff timer has certain limitations.
  • the embodiment of the present invention proposes to move Processing method and a network-side device mobility management, and mobility management during 5 move back-off method and a user equipment.
  • the method for processing the mobility management process, the network side device, the mobility management process backoff method, and the user equipment provided by the present invention will be described in more detail below with reference to the accompanying drawings and embodiments.
  • the APN-based congestion control mechanism In the 3GPP (3rd Generation Partnership Project) machine-to-machine communication specification development process, the APN-based congestion control mechanism is discussed, and it is decided that this mechanism can also be used for APN congestion caused by common UEs.
  • this mechanism can also be used for APN congestion caused by common UEs.
  • rejection scenarios and methods there is currently no complete, accurate, and specific representation of the behavior of the network and the UE, and there are some unresolved issues.
  • the present invention provides a method for processing a mobility management process.
  • the method includes: Step S10: In the mobility management process of the UE, the network side sends a mobility to the UE according to whether a different APN starts a congestion control mechanism. Sex management acceptance message;
  • Step S20 When the network side sends a mobility management accept message to the UE, the mobility management accept message sent by the network carries a mobility management backoff timer.
  • the method proposed by the present invention makes the refusal mobility management process not only limited to the implementation of rejecting the attach or location update process, but also rejects the mobility management process by receiving the message through the mobility management according to whether the APN is enabled to open the congestion control mechanism, thereby avoiding serious Network congestion, saving network resources and better congestion control.
  • the present invention provides a mobility management process backoff method, as shown in FIG. 2, including:
  • Step SOI the UE receives the mobility management acceptance of the mobility management backoff timer sent by the network side in the mobility management process; %, packet,;
  • Step S02 The UE starts a mobility management backoff timer, and only initiates a mobility management process related to a priority service or an emergency call service before the mobility management timer expires;
  • Step S03 The UE determines that the mobility management backoff timer is longer than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the duration of the mobility management backoff timer is not less than The value is used to start the periodic tracking timer.
  • the above method proposed by the present invention can be applied to a GPRS (General Packet Radio Service) system or an EPS system.
  • GPRS General Packet Radio Service
  • EPS General Packet Radio Service
  • the preferred embodiment of the technical solution of the present invention is given below by taking an application to the EPS system as an example and combining with a specific mobility management process.
  • the mobility management process of the UE is an attach procedure ATTACH
  • the mobility management accept message is an attach accept message.
  • the network side sends the mobility management accept message to the UE according to whether the different APNs enable the congestion control mechanism, and the method includes: the first network entity determines an APN that the UE requests to connect in the attaching process; and the first network entity connects according to the request. Whether the APN turns on the congestion control mechanism and sends an attach accept message to the UE.
  • the first network entity is an MME.
  • the MME determines the APN that the UE requests to connect in the attaching process, and the method includes: determining that the APN is the APN requesting the connection when the message sent by the UE in the attaching process, and determining that the UE is attached.
  • the default APN in the subscription data is determined to be the APN to be connected according to the subscription data of the UE obtained from the HSS.
  • the MME when the MME determines that the APN requesting the connection to open the congestion control mechanism, the MME sends an attach accept message carrying the mobility management backoff timer, and also sends a connection reject message to the UE, and carries the connection reject message in the connection reject message.
  • the session management backoff timer of the APN requesting the connection when the MME determines that the APN requesting the connection to open the congestion control mechanism, the MME sends an attach accept message carrying the mobility management backoff timer, and also sends a connection reject message to the UE, and carries the connection reject message in the connection reject message.
  • the session management backoff timer of the APN requesting the connection when the MME determines that the APN requesting the connection to open the congestion control mechanism, the MME sends an attach accept message carrying the mobility management backoff timer, and also sends a connection reject message to the UE, and carries the connection reject message in the connection reject message.
  • the session management backoff timer of the APN requesting the connection when the
  • the MME determines that the APN requesting the connection starts the congestion control mechanism, and attempts to establish an attach accept message carrying the mobility management backoff timer to the UE after the connection to the APN is successfully established, and also sends an activation to the UE.
  • the EPS bears the context request message, and carries the session management backoff timer of the APN in the activated EPS bearer context request message.
  • Step S101 The UE sends an attach request ATTACH REQUEST message.
  • the UE is also requested to request a PDN CONNECTIVITY REQEUST message to the APN connection, and the message may not include any APN.
  • the network performs the attach process according to the existing process. Identity request request procedure, authentication/security authentication AUTHENTICAITON/SECURITY procedure, password selection request/response CIPERE OPTION REQUEST/RESPONESE procedure.
  • the UE may indicate an APN to the MME; Step S103, if the current MME does not have a valid context, then the subscription data of the UE needs to be obtained from the HSS. At this point, you will know which defects the UE has signed. If the UE indicates the APN in the foregoing step, it indicates that the UE will establish a connection to the APN. If the APN is not indicated, the MME obtains the default APN of the UE from the subscription data of the UE as the target APN to be established in the ATTACH process. Thereby determining that the UE requests to establish a connected APN.
  • Step S104 The MME checks whether there is an APN-enabled congestion control mechanism in the APN requested by the UE.
  • the open congestion control mechanism referred to in this document is the same as the standard definition mentioned in the background technology. If no APN is enabled to enable congestion control, the current normal process is performed. If there is an APN to enable congestion control, perform S105 or S106;
  • Step S105 According to the existing ATTACH procedure, the MME still attempts to establish a connection to the requested APN. If the connection is successful, step S109 is performed. If not successful, performing S107 or S108, preferably, if the MME knows that the UE supports the mobility management backoff timer and/or the session management backoff timer function, step S108 is performed;
  • Step S106 directly performing step S107 or S108 without attempting to connect with the requested APN.
  • the MME knows that the UE supports the mobility management backoff timer and/or the session management backoff timer function, executing S108;
  • Step S107 The MME directly sends an attach reject ATTACH REJECT message to the UE, where the mobility management backoff timer is carried in the ATTACH REJECT message.
  • the ATTACH REJECT message and the request PDN reject message REQUEST PDN REJECT MESSAGE are simultaneously sent to the UE, and the MME also needs to carry the session management timer in the REQUEST PDN REJECT message;
  • Step S107-UE for the UE, the UE considers that it does not have an ATTACH to the network. If the UE cannot understand the received mobility management backoff timer and session management timer, then the behavior of the UE will cause the behavior described in the prior art. If the UE can receive the understanding of the mobility management backoff timer and the session management timer, the UE cannot initiate an ATTACH request until the mobility management backoff timer expires. After the mobility management backoff timer expires, the ATTACH request is re-initiated. Before the session management timer expires, the connection request process to the previously determined APN cannot be initiated, but can be initiated. Attach request to other APNs. 8
  • Step S108 The ATTACH ACCEPT message is directly sent to the UE, and the mobility management backoff timer is carried in the ATTACH ACCEPT message.
  • the ATTACH ACCEPT message and the REQUEST PDN REJECT message are simultaneously sent to the UE, and the MME also needs to carry the session management timer in the REQUEST PDN REJECT message;
  • Step S108 The UE returns an ATTACH COMPLETE message to the MME after receiving the ATTACH ACCEPT message.
  • the UE learns through the received REQUEST PDN REJECT message that the network has not established an APN connection to the UE for the request.
  • the UE After receiving the mobility management backoff timer and the session management timer, the UE cannot initiate a mobility management process such as TAU before the mobility management backoff timer expires. Before the session management timer expires, the UE cannot initiate the determination request.
  • APN connection process After both timers have timed out, if the UE has not established any APN connection, it needs to initiate the process of establishing a connection with the APN immediately.
  • Step S109 The ATTACH ACCEPT message is directly sent to the UE, and the mobility management backoff timer is carried in the ATTACH ACCEPT message.
  • the network sends the ATTACH ACCEPT message and the active default EPS context request ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to the UE at the same time.
  • the MME also needs to carry the session management timer in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.
  • Step S109-UE after receiving the ATTACH ACCEPT message, the UE returns an ATTACH COMPLETE message to the network. If the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message can be accepted, the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is returned to the network, which indicates that the APN is established. Connection. At this time, before the mobility management backoff timer expires, the UE cannot initiate a mobility management process such as TAU. Before the session management timer expires, the ESM process related to the connection of the APN that determines the request cannot be initiated, such as dedicated bearer activation. , carrying resource modification, etc. If it is unacceptable, it returns to activate the default EPS bearer context to reject the ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message to the network, and thereafter the UE behavior is performed according to step S108-UE.
  • Example 2 The embodiment according to the present embodiment the mobility management message is accepted 9 elimination location updating accept message, a location update procedure may involve the SGW (Serving Gateway, Serving Gateway) changes or does not change the scene, the present embodiment will not change SGW, When the network entity (MME/SGSN) that the network side communicates with the UE changes or does not change, a specific implementation manner is given.
  • SGW Serving Gateway
  • MME/SGSN Mobility Management Entity
  • the network side sends a mobility management accept message to the UE according to whether the APN has enabled the congestion control mechanism, and the method includes: the first network entity determines that the SGW does not occur during the location update process of the UE.
  • the APN that has established a connection with the UE before the location update is determined; when the first network entity determines that the APN with the UE has established a connection has an APN-enabled congestion control mechanism, the location update accept message is sent to the UE.
  • the network side sends the mobility management accept message to the UE according to whether the APN is enabled with the congestion control mechanism
  • the method includes: before the location update process, determining, by the second network entity, the location update
  • the UE is configured to acquire the bearer information of the UE from the first network entity when the UE is connected to the first network entity, and the second network entity determines, according to the acquired bearer information of the UE, The UE has established a connected APN; the second network entity determines that the APN has a congestion control mechanism in the APN that has established a connection with the UE, and sends a location update accept message to the UE.
  • the second network entity determines that there is an APN-enabled congestion control mechanism in the APN in which the UE has established a connection, and sends a location update accept message to the UE, where: the second network entity determines that the APN that has established the connection with the UE is enabled to be congested. Controlling the APN of the mechanism, and indicating that the determined APN is congested by the SGW; the SGW does not need to send a modify bearer request message to the indicated APN that is congested according to the APN that is congested by the second network entity.
  • a first modified bearer response message and returning a second modified bearer response message to the second network entity, where the second modified bearer response message is sent to the second network entity.
  • the response message carries a reject reason code indicating that the APN is sent to the congestion-generating message; the second network entity deletes the bearer of the rejected APN and the rejected APN according to the received second modified bearer response message.
  • the second network entity determines to delete all the connections in the connection between the UE and the APN, and sends the location to the UE.
  • Rejection message and the message carries the rejected cell mobility
  • the backoff timer is managed. Otherwise, the location update accept message carrying the mobility management backoff timer is sent to the UE.
  • the reason that the location update update message is carried in the location update reject message is that the allocating of the activated APN is congested.
  • the network side sends the location update accept message to the UE by deleting the connection between the UE and the APN
  • the network side implements the APN by the network side and the UE side by using the evolved packet system EPS bearer status in the location update accept message.
  • the synchronization of the bearer The network side specifically deletes the bearer of the APN and the connection to the APN through an actively initiated request de-connection process.
  • the network side further includes: the network side actively initiating a detach process to the UE.
  • the network side maintains the mobile reachable timer of the UE.
  • the Mobile Reachable timer is started when the UE enters the IDLE state (ie, the idle state).
  • the UE and the network side establish a NAS (Non-Access Stratum, non-access stratum)
  • the network side stops the Mobile Reachable timer.
  • the periodic location update timer is started after the UE enters the idle state, and stops when the UE and the network establish a signaling connection.
  • the location update process is specifically a routing area update process
  • the network entity is an SGSN
  • the periodic location update timer is an RAU timer.
  • the location update process is tracking.
  • the periodic location update timer is a TAU timer
  • the network entity is the MME.
  • the following takes the EPS system as an example to describe the process of rejecting the mobility management process in the embodiment of the present invention.
  • the embodiment is applied to the scenario where the SGW is unchanged, and specifically includes:
  • Step S201 The UE sends a tracking area update request TAU REQUEST message to the MME.
  • the MME activates all the established connection with the APN of the possible UE.
  • the MME that receives the TAU request may be the MME that the UE is connected to before, or may be the new MME. If it is a new MME, step S205 is performed, if the MME does not change, the MME Determining that the SGW is not relocated (ie, the SGW does not need to be changed to 1 ), the MME determines whether there is an APN in the APN that establishes a connection with the UE before the cell update, and the MME needs to perform step S203. If not, the current MME needs to perform the step S203. There is process processing;
  • Step S203 The MME sends a tracking area update accepting a TAU ACCEPT message to the UE, and carries a mobility management backoff timer to the UE in the TAU ACCEPT message.
  • the MME carries the mobility management backoff timer in the TAU ACCEPT message, specifically the mobility management backoff timer identifier and the duration thereof. In this step, the MME determines the mobility management backoff timer carried in the mobility management accept message. When the duration is greater than the duration of the mobile reachable timer of the UE maintained by the network side, the mobility reachable timer of the UE is restarted according to a value that is not less than the duration of the mobility management backoff timer.
  • the MME further carries a periodic TAU timer and a duration thereof in the TAUACCEPT message, and the duration of the periodic TAU timer is not less than the duration of the mobility management backoff timer; the MME is not less than the period.
  • the value of the duration of the sexual location update timer is restarted, and the mobility reachability timer of the UE is restarted.
  • Step S204 After receiving the TAU ACCEPT message carrying the mobility management backoff timer, the UE needs to start the mobility management backoff timer, and cannot initiate any mobility management process before the mobility management backoff timer expires. Only initiate mobility management processes related to priority services or emergency call services.
  • the UE determines that the duration of the mobility management backoff timer is greater than the duration of the periodic tracking area update timer, and when the periodic tracking timer needs to be started, the value of the mobility management backoff timer is not less than The periodic tracking timer is started.
  • the periodic tracking area update timer duration in the tracking area update accept message is used to initiate periodic tracking. Zone update timer.
  • Step S205 The MME needs to acquire the bearer information of the UE from the old MME, and interacts with the SGW according to the EPS bearer related information of the UE from the old MME. At this time, the new MME needs to establish a connection with the UE before the tracking area update according to the bearer information of the UE.
  • the APN and determine which of these APNs APN 12 has enabled congestion control mechanisms.
  • the APA, the APNB, and the APNC are connected to the UE before the tracking area is updated.
  • the MME determines that the congestion control mechanism is enabled on the APNB.
  • the MME needs to perform the following processing: for the connection with the APNA and the APNC, according to the existing process. That is, the MME sends a modify bearer request Modify Bearer Request message to the SGW for the APNA and the APNC respectively.
  • the MME needs to add a congestion indication to the Modify Bearer Request Modify Bearer Request message sent to the SGW, and the APN indication of the congestion control is turned on to the SGW.
  • Step S206 After receiving the Modify Bearer Request message, the SGW continues the subsequent process if there is no congestion indication. If there is a congestion indication, the APN (PGW corresponding to the APN) is subsequently processed according to whether to send the modified bearer Modify Bearer Request. If the Modify Bearer Request is required to be sent to the APN, the SGW directly sends a Modify Bearer Reponse (with Reject CAUSE CODE, or new source code) message carrying the reject reason code to the MME. If the Modify Bearer Request is not sent to the PGW, the SGW sends the Modify Bearer Reponse directly to the MME, indicating success.
  • a Modify Bearer Reponse with Reject CAUSE CODE, or new source code
  • Step S207 The new MME needs to perform different processing according to the content in the Modify Bearer Reponse message:
  • the new MME needs to delete the bearer of the rejected APN and the connection to the rejected APN.
  • the specific deletion method can be processed according to the existing method. For example, it is performed by initiating a delete session request Delete Session Request message. At this time, although the PGW is already in a congested state, if a request such as deleting a bearer, deleting a session, or deleting a PDN connection is received, these deletion requests should not be rejected and should be handled according to the normal procedure.
  • step S208 is performed, and if at least one connection is not deleted, the TAU request may be accepted. , execute S209.
  • Step S208 The MME sends a TAU REJECT message to the UE, and the specific processing procedure is as follows:
  • the MME sends a TAU REJECT message to the UE, and carries a mobility management backoff timer to the UE in the TAU REJECT message. And use a new reason value to illustrate the network because of all the UE's Live PDN connection congestion occurs, can not establish a connection to carry all PDN ⁇ 3.
  • the UE After receiving the TAU REJECT message carrying the mobility management backoff timer, the UE needs to start the mobility management backoff timer, which cannot initiate any mobility management procedure before the mobility management backoff timer expires. According to the new cause value, before the mobility management backoff timer expires, the UE can perform a connection establishment procedure to the APNs other than the APNA, the APNB, and the APNC, for example, the UE initiates a request to the APND connection.
  • the UE After the mobility management backoff timer expires, if the UE has not established any APN connection, the UE needs to perform an attach ATTACH procedure, or a UE REQUEST CONNECTIVITY procedure to establish a default APN bearer. At this point, you can establish a connection to APNA, APNB, and APNC.
  • the step is 209, the MME sends a TAU ACCEPT message to the UE.
  • the specific treatment is as follows:
  • the MME sends a TAU ACCEPT message to the UE, and carries a mobility management backoff timer to the UE in the TAU ACCEPT message.
  • the MME carries the mobility management backoff timer in the TAU ACCEPT message, specifically the mobility management backoff timer identifier and the duration thereof. In this step, the MME determines the mobility management backoff timer carried in the mobility management accept message. When the duration is greater than the duration of the mobile reachable timer of the UE maintained by the network side, the mobility reachable timer of the UE is restarted according to a value that is not less than the duration of the mobility management backoff timer.
  • the MME further carries a periodic TAU timer and a duration thereof in the TAUACCEPT message, and the duration of the periodic TAU timer is not less than the duration of the mobility management backoff timer; the MME is not less than the period.
  • the value of the duration of the sexual location update timer is restarted, and the mobility reachability timer of the UE is restarted.
  • Step S210 After receiving the TAU ACCEPT message carrying the mobility management backoff timer, the UE needs to start the mobility management backoff timer, and cannot initiate any mobility management process before the mobility management backoff timer expires. Only initiate mobility management processes related to priority services or emergency call services.
  • the duration is such that when the periodic tracking timing needs to be started, the periodic tracking timer is started according to a value that is not less than the duration of the mobility management backoff timer.
  • the periodic tracking area update timer duration in the tracking area update accept message is used to initiate periodic tracking. Zone update timer.
  • the location update process may involve a scenario in which the SGW changes or does not change.
  • the SGW changes, and the network side communicates with the UE.
  • a specific implementation is given when the network entity (MME/SGSN) changes or does not change.
  • the network side sends a mobility management accept message to the UE according to whether the APN is enabled to perform the congestion control mechanism
  • the method includes: determining, by the network side, that the serving gateway SGW changes in the location update process of the UE, before the location update and the UE Whether the APN has opened the congestion control mechanism in the connected APN, and sends a location update accept message to the UE.
  • the network entity that receives the cell update request sent by the UE may also not change, that is, the first network entity is connected before the UE cell update, and the network side that performs the location update process of the UE is the first network entity or the first
  • the network entity that performs the foregoing denial mobility management process is the first network entity
  • the scenario where the network entity changes that is, the network side that performs the location update process of the UE is the second
  • the network entity further includes: the second network entity acquiring the bearer information of the UE from the first network entity, so as to be able to determine that the UE has established a connected APN.
  • the network side sends a location update accept message to the UE according to whether the APN is enabled in the APN that has been connected to the UE before the location update, and the network side includes: the network side establishes a connection with the UE before determining the location update.
  • the APN when the APN has enabled the congestion control mechanism, the bearer of the APN and the connection to the APN are deleted; when the network side determines that all the connections in the connection between the UE and the APN are deleted, the location update rejection message is sent to the UE, and Carrying a mobility management backoff timer in the location update reject message, otherwise, sending a mobility management backoff timer to the UE
  • the location update accepts the message.
  • the reason that the location update update message is carried in the location update reject message is that the allocating of the activated APN is congested.
  • the network side deletes the connection between the UE and the APN to send the location update accept message to the UE, the network side also synchronizes the APN bearer between the network side and the UE side by using the EPS bearer status in the location update accept message.
  • the network side deletes the bearer of the APN and the connection to the APN by using an actively initiated request de-connection process.
  • the network side further includes: the network side actively initiating a detach process to the UE.
  • the location update process is specifically a routing area update process
  • the network entity is an SGSN
  • the periodic location update timer is an RAU timer
  • the location update process is performed.
  • the periodic location update timer is a TAU timer and the network entity is the MME.
  • the following is an example of the process of processing the mobility management process in the embodiment of the present invention.
  • the embodiment is applied to the scenario in which the SGW changes.
  • Step S301 the UE sends a tracking area update request TAU REQUEST message to the MME.
  • the MME activates all the established connection between the UE and the APN.
  • Step S302 If the MME of the TAU request sent by the UE is changed, the context is requested by the context request/response CONTEXT REQUEST/RESPONSE process between the new and old MMEs, so that the new MME obtains the bearer information of the UE from the old MME.
  • the MME receiving the TAU request because it is determined that the SAW has changed, the MME needs to initiate a connection to the new SGW and the update process of the bearer.
  • the MME needs to check whether there is an APN open congestion control mechanism in the APN that establishes a connection with the UE before the location update. If yes, the MME needs to perform step S303, otherwise it processes according to the existing process.
  • Step S303 this step illustrates how the MME reestablishes the connection and bearer update procedure to the SGW according to the APN-based congestion control when the SGW changes, and assumes that the UE has established three APN connections before initiating the current TAU: to the APNA, the APNB, and APNC connection.
  • the AP3 is currently connected to the UE.
  • At least one APN does not have congestion control enabled.
  • the MME determines that the APNB has enabled the congestion control mechanism, and the congestion control mechanism is not enabled for the APNA and the APNC.
  • the MME performs the process of reestablishing the connection to the new SGW and the bearer update process for the APNA and the APNC that have not enabled the congestion control mechanism, that is, the MME sends a Create Session Request to the new SGW.
  • the MME is configured to prevent the APNB that is determined to be congested from being further congested by the APNB that has started the congestion control mechanism.
  • the MME cannot perform the connection reestablishment and the bearer update process to the new SGW according to the existing procedure.
  • the MME needs to delete the connection to the APNB.
  • the MME uses the existing procedure "UE or MME requested PDN disconnection", that is, the MME actively initiates a request PDN connection process to delete the connection to the APNB.
  • the MME uses the EPS STATUS IE in the existing TAU ACCEPT message to implement synchronization of the bearer information between the network side and the UE side, that is, in the EPS STATUS IE, does not include any bearer information connected to the APNB. Subsequent steps 304 and S305 are performed.
  • Case 2 that is, in the APN that previously established a connection with the UE, all APNs have a congestion control mechanism enabled.
  • the MME has started an APN-based congestion control mechanism for APNA, APNB, and APNC.
  • the MME uses the existing procedure "UE or MME requested PDN disconnection", that is, the actively initiated request PDN de-connection process to delete the connection with the APNA, the APNB, and the APNC. Further, the MME may also initiate a de-attach DETACH procedure to detach the UE from the network. Subsequent steps S306 and S307 are performed.
  • Step S304 The MME sends a tracking area update accepting a TAU ACCEPT message to the UE, and carries a mobility management backoff timer in the TAU ACCEPT message.
  • the MME carries the mobility management backoff timer in the TAU ACCEPT message, specifically carrying the mobility management backoff timer identifier and the duration thereof. In this step, the MME determines that the mobility management accepts the cancellation. If the rf 7 length of the mobility management backoff timer carried in the information is greater than the duration of the mobility reachable timer of the UE maintained by the network side, the value of the duration of the mobility management backoff timer is not less than Restarting the mobility reachable timer of the UE
  • the MME further carries a periodic TAU timer and a duration thereof in the TAUACCEPT message, and the duration of the periodic TAU timer is not less than the duration of the mobility management backoff timer; the MME is not less than the period.
  • the value of the duration of the sexual location update timer is restarted, and the mobility reachability timer of the UE is restarted.
  • Step S305 the same step S210.
  • Step S305B The UE returns a TAU COMPLETE message to the network according to the existing procedure.
  • Step S306 the MME sends a tracking area update reject TAU REJECT message to the UE, and carries a mobility management backoff timer to the UE in the TAU REJECT message. And a new cause value indicates that the network is unable to establish a bearer for all PDN connections for the UE because of congestion of all activated PDN connections of the UE.
  • Step S307 After receiving the TAU REJECT message carrying the mobility management backoff timer, the UE needs to start the timer, and cannot initiate any mobility management process before the timer expires. According to the new cause value, before the timer expires, the UE can perform a connection establishment procedure to the APN outside the APNA, APNB, and APNC connections, for example, initiating a UE requesting a connection request to the APN, requesting to establish a connection to the APND.
  • the UE After the mobility management backoff timer expires, if the UE has not established a connection to any APN, the UE needs to perform an attach ATTACH procedure, or the UE requests to connect to the UE REQUEST CONNECTIVITY process to establish a connection to the default APN, which can be established to the APNA, APNB, APNC connection.
  • the method of rejecting mobility management and the method of retreating the mobility management process are the same as the above process.
  • the mobility management process of the UE is a detachment process initiated by the UE, and the mobility management accept message is a detachment accept message, and the network side starts the congestion control mechanism according to different APNs.
  • the mobility management accept message if the network side determines that the APN that is currently connected to the UE has an APN-enabled congestion control mechanism, and sends a detachment accept message carrying the mobility management evasion timer to the UE.
  • the UE For the APN subscribed by the UE, if the UE establishes a connection to the APN through the gateway node corresponding to the APN, it is determined that the APN is an activated APN.
  • Step S401 the UE sends a detach request DETACH REQUEST message to the MME;
  • Step S402 the MME determines that the APN-enabled congestion control mechanism is established in the APN that is currently connected to the UE, and the MME carries the mobility management backoff timer in the detachment-receiving DETACH ACCEPT message sent to the UE.
  • Step S403 After discovering the mobility management backoff timer in the received DETACH ACCEPT message, the UE starts the mobility management backoff timer, and does not initiate an attach request message to the following APN before the mobility management backoff timer expires. : The APN activated in the APN that the UE subscribes to when the UE sends the detach request message.
  • the method for handling mobility management and the method for backoff of the mobility management process are the same as the above process, and the network entities on different network sides are SGSNs.
  • the method for rejecting the mobility management process is specifically: the network side decides to detach the UE from the network, and determines that the APN currently connected to the UE has an APN enabled.
  • the network side actively initiates a detach request to the UE, and carries a mobility management backoff timer in the detach request.
  • the UE receives the detach request message initiated by the network side to initiate the mobility management backoff timer; the UE starts the mobility management backoff timer, and stops before the mobility management backoff timer expires.
  • Step S501 The MME determines to send the UE from the network to the DETACH. Before sending the DETACH REQUEST message to the UE, the MME determines that the APN that is currently connected with the UE has the APN enabled to be congested. The MME carries the mobility management backoff timer in the DE'iACH REQUEST message sent to the UE.
  • Step S502 After receiving the DETACH REQUEST, the UE sends a DETACH ACCPET message to the network according to a normal process. After the UE current DETACH REQUEST message includes the mobility management backoff timer, the mobility management backoff timer is started, and any APN activated on the UE when the DOTACH request message is received is not initiated before the mobility management backoff timer expires. ATTACH request message.
  • the mobility management entity in the network also needs to perform the modification and update process of the bearer connection established by the UE to the APN.
  • Step S601 The UE sends a SERVICE REQUEST request message to the network.
  • Step S602 after the MME receives the message, the interaction between the mobility management node, the SGW, and the PGW may be updated by referring to the methods in steps S205 to S207 in Embodiment 2 to connect the PDN connection and the bearer at the MME. The specific process will not be described again.
  • step S603 is performed, and if at least one connection is not deleted, the MME can accept the connection.
  • SERVICE REQUEST request execute
  • Step 603 The network sends a SERVICE REJECT message to the UE, and carries a corresponding reason code. And carry the label and duration of the mobility management backoff timer.
  • Step 604 the process ends normally.
  • the network can establish a bearer
  • the corresponding response message is not sent to the UE, and the UE determines that the SERIVCE request process is successful according to the bearer establishment result.
  • the mobility management entity referred to herein refers to the MME and GPRS systems in the EPS system.
  • the timer is started.
  • the mechanism is as follows: when the UE receives the attachment acceptance cancellation, the duration of the mobility management backoff timer is determined to be greater than the duration of the periodic location update timer, and when the periodic tracking timer needs to be started, the mobility is not less than The duration of the grace management backoff timer is used to start the periodic tracking timer.
  • a network side device that rejects the mobility management process.
  • the method includes: a message sending unit 10, configured to use different APNs in the mobility management process of the UE. Whether the congestion control mechanism is enabled, and the mobility management accept message is sent to the UE; the timer carrying unit 20 is configured to carry the mobility management backoff timer in the sent mobility management accept message.
  • the message sending unit 10 specifically includes any one or more of the following units: a first message sending unit, configured to send, in the attaching process of the UE, to the UE according to whether a different APN starts a congestion control mechanism And a second message sending unit, configured to: in the location update process of the UE, send a location update accept message to the UE according to whether a different APN starts a congestion control mechanism; and a third message sending unit, configured to De-attaching the process initiated by the UE, and sending a detach accept message to the UE according to whether the APN is enabled with a congestion control mechanism;
  • the timer carrying unit 20 includes any one or more of the following units: a first timer carrying unit, configured to carry a mobility management backoff timer in the attach accept message sent by the first message sending unit; a second timer carrying unit, configured to carry a mobility management backoff timer in the location update accept message sent by the second message sending unit, and a third timer carrying unit, configured to remove the detachment sent by the third message sending unit
  • the acceptance message carries a mobility management backoff timer.
  • the message sending unit 10 includes a first message sending unit, the timer carrying unit includes a first timer carrying unit, and the first message sending unit specifically includes: a first APN determining unit, configured to determine a UE The APN is requested to be connected in the attaching process.
  • the first triggering unit is configured to send an attach accept message to the UE according to whether the APN that is requested to be connected is enabled, and trigger the first timer carrying unit to carry in the attach accept message. Mobility management backoff timer.
  • the first APN determining unit is configured to send an attach accept message to the UE when the APN of the request connection is determined to be in a congestion control mechanism
  • the network side device further includes: a fourth timer
  • the bearer unit is configured to send a connection rejection message to the UE, and carry the session management backoff timer of the APN in the connection reject message.
  • the first APN determining unit is specifically configured to determine the APN-enabled congestion control mechanism, and after attempting to establish a connection to the APN, send an attach accept message to the UE, where the network side device further includes: And a timer carrying unit, configured to send an activated evolved packet system EPS bearer context request message to the UE, and carry the session management backoff timer of the APN in the activated EPS bearer context request message.
  • a timer carrying unit configured to send an activated evolved packet system EPS bearer context request message to the UE, and carry the session management backoff timer of the APN in the activated EPS bearer context request message.
  • the message sending unit includes a second message sending unit
  • the timer carrying unit includes a second timer carrying unit
  • the second message sending unit specifically includes: a second APN determining unit, configured to determine a location update The network-side device that is connected to the UE is not changed, and when the serving gateway SGW does not change during the location update process of the UE, the APN that has established a connection with the UE before the location update is determined; the second triggering unit is configured to determine When the APN has established a connection control mechanism with the APN, the UE sends a location update accept message to the UE, and triggers the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.
  • the message sending unit includes a second message sending unit
  • the timer carrying unit includes a second timer carrying unit
  • the second message sending unit specifically includes: a bearer information acquiring unit, configured to determine a location update The network side device connected to the UE is changed, and the bearer information of the UE is obtained from the previous network side device when the SGW is not changed in the location update process of the UE; the third APN determining unit is configured to be configured according to the obtained The bearer information of the UE is used to determine an APN that has established a connection with the UE before the location update.
  • the third triggering unit is configured to: when the APN with the UE that has established a connection with the APN has a congestion control mechanism, send a location update to the UE. Receiving the message, and triggering the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.
  • the third triggering unit specifically includes: a congestion indication unit, configured to determine an APN in which the congestion control mechanism is enabled in the APN in which the UE has established a connection, and instruct the SGW that the determined APN is congested, and the SGW is configured according to the SGW.
  • the APN that is congested by the second network entity returns to the second network entity when the modified bearer request message is not sent to the indicated APN that is congested.
  • Modify Bearer Response message back to the first the need to refer to 2 fe when congestion occurs in transmission APN bearer modification request message, the second return modify bearer response message to the second network entity, the second modified bearer response message carries represents Rejecting the rejection reason code of the APN sending message to the congestion;
  • the first APN deleting unit is configured to delete the bearer of the rejected APN and the connection to the rejected APN according to the received second modified bearer response message;
  • a message form determining unit configured to send a location update reject message to the UE when the connection between the UE and the APN is deleted, and carry a mobility management backoff timer in the cell reject message, otherwise, to the UE And sending a location update accept message and triggering the second timer carrying unit to carry the mobility management backoff timer in the location update accept message.
  • the message sending unit includes a second message sending unit
  • the timer carrying unit includes a second timer carrying unit
  • the second message sending unit specifically includes: a fourth APN determining unit, configured to determine When the serving gateway SGW changes during the location update process of the UE, the APN that has established a connection with the UE before the location update is determined; and the fourth triggering unit is configured to send a location update to the UE according to whether the APN has enabled the congestion control mechanism before the location update. Accept the message.
  • the fourth trigger determining unit specifically includes: a second APN deleting unit, configured to delete the bearer of the APN and the APN when the APN is enabled to connect to the APN before the location update is established. a second message form determining unit, configured to send a location update reject message to the UE when the connection between the UE and the APN connection is deleted, and carry the mobility management backoff timer in the location update reject message Otherwise, the location update accept message is sent to the UE and the second timer carrying unit is triggered to carry the mobility management backoff timer in the location update accept message.
  • a second APN deleting unit configured to delete the bearer of the APN and the APN when the APN is enabled to connect to the APN before the location update is established.
  • a second message form determining unit configured to send a location update reject message to the UE when the connection between the UE and the APN connection is deleted, and carry the mobility management backoff timer in the location update reject message.
  • the reason that the location update update reject message carries the indication that the UE location update is rejected is that all activated APNs are congested. .
  • the first message form determining or the second message form determining unit is specifically configured to: when the connection of the part of the connection between the UE and the APN is deleted, send the location update accept message to the UE, and further pass the evolution in the location update accept message.
  • the packet system EPS bearer status implements the APN on the network side and the UE side. The synchronization of the bearer. twenty three
  • the first APN deleting unit or the second APN deleting unit is specifically configured to delete the bearer of the APN and the connection to the APN by using an actively initiated request de-connection process.
  • the timer carries the mobility management back-off timer in the mobility management accept message, which is specifically carrying the mobility management back-off timer identifier and the duration thereof
  • the network-side device further includes: a first mobile reachable timer a startup unit, configured to determine, when the mobility management backoff timer carried in the mobility management accept message is longer than the mobile reachable timer duration of the UE maintained by the network side, according to not less than the mobility The value of the duration of the backoff timer is managed, and the mobility reachable timer of the UE is restarted.
  • the message sending unit includes a second message sending unit
  • the timer carrying unit includes a second timer carrying unit, and further includes: a sixth timer carrying unit, configured to carry the periodic position in the location update accept message Updating a timer and a duration thereof, the duration of the periodic location update timer being greater than a duration of the mobility management backoff timer; and a second mobile reachable timer starting unit, configured to update according to not less than the periodic location The value of the duration of the timer restarts the mobility reachable timer of the UE.
  • the message sending unit includes a third message sending unit
  • the timer carrying unit includes a third timer carrying unit
  • the third message sending unit is specifically configured to determine that the APN currently establishing a connection with the UE has an APN.
  • the congestion control mechanism is enabled, the detachment accept message is sent to the UE, and the third timer carrying unit is triggered to carry the mobility management backoff timer in the sent detachment accept message.
  • the network side device further includes: an active detaching unit 30, configured to determine to detach the UE from the network, and determine that an APN open congestion control mechanism is currently established in the APN that establishes a connection with the UE, and initiates The detach request is sent to the UE, and the mobility management backoff timer is carried in the detach request.
  • an active detaching unit 30 configured to determine to detach the UE from the network, and determine that an APN open congestion control mechanism is currently established in the APN that establishes a connection with the UE, and initiates The detach request is sent to the UE, and the mobility management backoff timer is carried in the detach request.
  • the network side device further includes: a third APN deleting unit, configured to perform, during a service request process of the UE, when performing a modification and update process of the bearer that the UE has established the connection to the APN, determining that the UE has already Establish an APN in the connected APN to enable the congestion control mechanism, and delete the The bearer of the APN and the connection to the APN; the seventh-party: the bearer carrying unit, configured to send a service reject message to the UE when deleting all the connections in the connection between the UE and the APN, and in the service reject message Carry the mobility management backoff timer.
  • a third APN deleting unit configured to perform, during a service request process of the UE, when performing a modification and update process of the bearer that the UE has established the connection to the APN, determining that the UE has already Establish an APN in the connected APN to enable the congestion control mechanism, and delete the The bearer of the APN and the connection to the APN
  • the seventh-party the bear
  • the network side device is an MME in an SGSN or an EPS system in a GPRS system.
  • a mobility management backoff timer configured to start a mobility management backoff timer, and only initiate a mobility management process related to a priority service or an emergency call service before the mobility management timer expires;
  • the duration of the mobility management backoff timer is greater than the duration of the periodic location update timer.
  • the value of the mobility management backoff timer is not less than , to start the periodic tracking timer.
  • the mobility management process is a location update process
  • the mobility management accept message is a location update accept message
  • the second timer initiating unit 403 is specifically configured to determine that the location update accept message further carries
  • the periodic location update timer is started according to the duration of the periodic location update timer in the location update accept message.
  • the mobility management process is a detachment process initiated by the UE, and the mobility management accept message is a detach accept message, and the first timer starting unit 402 is specifically configured to time out the timeout in the mobility management backoff timer.
  • the attach request of the APN activated by the UE when the detach request is sent is stopped.
  • the method further includes: a request message receiving unit 404, configured to receive a detach request message carrying a mobility management backoff timer that is actively sent by the network side, where the first timer starting unit 402 is specifically configured to start the mobile The sex management backoff timer stops, before the timeout of the mobility management backoff timer, the attach request of the APN activated by the UE when the detach request message is received.
  • a request message receiving unit 404 configured to receive a detach request message carrying a mobility management backoff timer that is actively sent by the network side, where the first timer starting unit 402 is specifically configured to start the mobile The sex management backoff timer stops, before the timeout of the mobility management backoff timer, the attach request of the APN activated by the UE when the detach request message is received.
  • 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 applied to one or more of the packages Computer/storage media (including but not limited to disk storage, containing computer usable program code,
  • a form of a computer program product implemented on a CD-ROM Compact Disc Read-Only Memory, optical storage, etc.
  • 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)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un dispositif côté réseau pour le processus de gestion de mobilité. Le procédé comprend les étapes suivantes: lors d'un processus de gestion de mobilité d'un équipement utilisateur, et dépendant de la présence ou non de mécanisme de contrôle de congestion activé dans les différents noms de points d'accès, la transmission par le côté réseau à l'équipement utilisateur d'un message d'acceptation de gestion de mobilité; l'annexion par le côté réseau d'un message de de temporisateur de réduction de puissance de gestion de mobilité au message d'acceptation de gestion de mobilité. La présente invention réduit la consommation de ressources de l'équipement utilisateur et de côté réseau, permettant ainsi un contrôle amélioré sur la congestion de réseau.
PCT/CN2011/080154 2010-09-30 2011-09-26 Procédé et dispositif côté réseau pour le processus de gestion de mobilité WO2012041197A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010503865.1A CN102448042B (zh) 2010-09-30 2010-09-30 一种拒绝移动性管理过程的方法及网络侧装置
CN201010503865.1 2010-09-30

Publications (1)

Publication Number Publication Date
WO2012041197A1 true WO2012041197A1 (fr) 2012-04-05

Family

ID=45891942

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080154 WO2012041197A1 (fr) 2010-09-30 2011-09-26 Procédé et dispositif côté réseau pour le processus de gestion de mobilité

Country Status (2)

Country Link
CN (1) CN102448042B (fr)
WO (1) WO2012041197A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103379659A (zh) * 2012-04-17 2013-10-30 电信科学技术研究院 一种多优先级场景下接入请求实现方法及装置
WO2017147735A1 (fr) * 2016-02-29 2017-09-08 华为技术有限公司 Procédé et appareil permettant de régler une longueur de temps d'un temporisateur de mise à jour de localisation périodique et dispositif de réseau
CN107623599A (zh) * 2017-09-26 2018-01-23 杭州东方通信软件技术有限公司 一种数据配置的方法和系统

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102802217B (zh) * 2012-07-30 2015-01-07 电信科学技术研究院 一种网络拥塞控制方法及设备
CN104919829B (zh) * 2012-11-02 2019-06-11 Lg电子株式会社 用于发送mtc设备的数据的方法
CN103813383A (zh) * 2012-11-09 2014-05-21 中兴通讯股份有限公司 请求的发送方法、装置及用户设备
WO2014107381A1 (fr) 2013-01-04 2014-07-10 Ingterdigital Patent Holdings, Inc. Procédé et appareil de traitement de commandes de détachement d'une couche de service et de notifications de rattachement
KR102179105B1 (ko) * 2013-07-08 2020-11-16 삼성전자 주식회사 무선 랜에서 제어 혼잡을 방지하는 방법 및 장치
CN105407539A (zh) * 2014-09-12 2016-03-16 电信科学技术研究院 一种pdn连接建立的方法及装置
CN107529194A (zh) * 2016-06-22 2017-12-29 中兴通讯股份有限公司 业务恢复方法及系统、分组数据网关及移动性管理实体
CN108924950B (zh) * 2017-04-21 2021-11-30 中兴通讯股份有限公司 一种建立承载的方法及装置
WO2019141212A1 (fr) * 2018-01-17 2019-07-25 Mediatek Singapore Pte. Ltd. Application de valeurs de temporisateur de contrôle de congestion au niveau nas au niveau d'un changement intersystème
CN112738848B (zh) * 2019-10-14 2022-12-06 中国移动通信集团安徽有限公司 核心网负荷调整方法、装置、设备及计算机可读存储介质
CN112911623B (zh) * 2019-12-04 2023-03-14 大唐移动通信设备有限公司 一种流程超时监控方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1674544A (zh) * 2004-03-26 2005-09-28 华为技术有限公司 一种控制接入的实现方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1674544A (zh) * 2004-03-26 2005-09-28 华为技术有限公司 一种控制接入的实现方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 9)", 3GPP TS 23.401 V9.5.0, 30 June 2010 (2010-06-30) *
"Medium Access Control (MAC) Protocol specification (Release 9)", 3GPP TS 36.321 V9.3.0, 30 June 2010 (2010-06-30) *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103379659A (zh) * 2012-04-17 2013-10-30 电信科学技术研究院 一种多优先级场景下接入请求实现方法及装置
WO2017147735A1 (fr) * 2016-02-29 2017-09-08 华为技术有限公司 Procédé et appareil permettant de régler une longueur de temps d'un temporisateur de mise à jour de localisation périodique et dispositif de réseau
CN107623599A (zh) * 2017-09-26 2018-01-23 杭州东方通信软件技术有限公司 一种数据配置的方法和系统
CN107623599B (zh) * 2017-09-26 2020-12-25 杭州东方通信软件技术有限公司 一种数据配置的方法和系统

Also Published As

Publication number Publication date
CN102448042A (zh) 2012-05-09
CN102448042B (zh) 2014-07-09

Similar Documents

Publication Publication Date Title
WO2012041197A1 (fr) Procédé et dispositif côté réseau pour le processus de gestion de mobilité
EP3764671B1 (fr) Procédé et appareil de communication
US11924679B2 (en) Distinguishing between general NAS level congestion and S-NSSAI related congestion control
KR101339044B1 (ko) 서빙 코어 네트워크 노드가 변경될 때의 모바일 장치의 접근성의 처리
TWI419592B (zh) 無線通訊系統改善無線資源控制連結建立的方法及相關裝置
WO2012094982A1 (fr) Procédé et dispositif de contrôle d'accès
TW201129216A (en) Method and apparatus for processing emergency calls
WO2008113235A1 (fr) Procédé pour éviter la libération erronée de ressources pendant une mise à jour de zone de suivi ou un transfert intercellulaire
WO2012174943A1 (fr) Procédé, appareil et système pour déterminer l'état d'un terminal
WO2010012176A1 (fr) Procédé, dispositif et système d'obtention dune information relative à la capacité de transfert intercellulaire entre systèmes et d'accès à un système
JP5928478B2 (ja) 移動無線通信ネットワークデバイス、移動無線通信デバイス、方法、コンピュータプログラム、コンピュータ可読媒体及び移動通信システム
US8885608B2 (en) Mobile communication method
WO2012041185A1 (fr) Procédé de notification de capacité et procédé, système et dispositif de régulation de la congestion d'un réseau
US8948754B2 (en) Method and apparatus for establishing a communication connection
WO2012109823A1 (fr) Procédé de contrôle de congestion et système d'équipements de communication de type machine
WO2012041184A1 (fr) Procédé et dispositif côté réseau d'instruction de réduction de puissance de gestion de session, et procédé et équipement utilisateur de réduction de puissance de gestion de session
WO2011127652A1 (fr) Procédé, appareil et système pour traiter un service de priorité multimédia amélioré dans un mécanisme de substitution à commutation de circuits
RU2662397C1 (ru) Способ обработки данных, устройство, терминал, объект управления мобильностью и система
WO2012041238A1 (fr) Procédé et dispositif permettant de traiter un contexte de gestion de mobilité
WO2013097503A1 (fr) Procédé et dispositif de régulation d'encombrement
WO2018045928A1 (fr) Procédé et dispositif de commande d'encombrement de réseau
WO2019061433A1 (fr) Procédé et dispositif de détection de résultat de repli par commutation de circuits (csfb), et support de stockage
WO2019214606A1 (fr) Procédé de commande exécuté dans un équipement utilisateur, et équipement utilisateur
WO2012041250A1 (fr) Procédé et dispositif de gestion de congestion dans des communications du type machine
WO2013063785A1 (fr) Procédé et dispositif d'établissement d'association gs

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

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

Country of ref document: EP

Kind code of ref document: A1