WO2012062193A1 - Procédé, dispositif, et système pour le contrôle de congestion dans le transfert intercellulaire de circuit principal de télécommunications (mtc) - Google Patents

Procédé, dispositif, et système pour le contrôle de congestion dans le transfert intercellulaire de circuit principal de télécommunications (mtc) Download PDF

Info

Publication number
WO2012062193A1
WO2012062193A1 PCT/CN2011/081872 CN2011081872W WO2012062193A1 WO 2012062193 A1 WO2012062193 A1 WO 2012062193A1 CN 2011081872 W CN2011081872 W CN 2011081872W WO 2012062193 A1 WO2012062193 A1 WO 2012062193A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
handover
target
mme
enodeb
Prior art date
Application number
PCT/CN2011/081872
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
Priority claimed from CN201010535875.3A external-priority patent/CN102469503B/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012062193A1 publication Critical patent/WO2012062193A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present invention relates to a handover technique in the field of machine to machine (M2M), and more particularly to a congestion control method, apparatus, and system in MTC handover.
  • M2M machine to machine
  • M2M communication services have gradually begun to be applied, such as logistics systems, remote meter reading, smart homes and so on.
  • the M2M service provider uses the existing wireless network, such as the General Packet Radio Service (GPRS) network, and the Evolved Packet System (EPS) network to carry out M2M services.
  • GPRS General Packet Radio Service
  • EPS Evolved Packet System
  • 3GPP is committed to the study of System Architecture Evolution (SAE), which aims to enable EPC (Evolved Packet Core) to provide higher transmission rates. , shorter transmission delay, optimized packet, and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), UMTS Terrestrial Radio Access Network (UTRAN), Mobility management between wireless local area networks (WLANs) and other access networks other than 3GPP (Third Generation Partnership Projects).
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • UTRAN UMTS Terrestrial Radio Access Network
  • the architecture of the existing SAE is as shown in FIG. 1.
  • the network element included in the evolved radio access network is an evolved Node B (eNodeB, Evolved NodeB), which is used for the user. Access to provide wireless resources; packet data network (PDN, Packet Data Network is a network that provides services to users; EPC provides lower latency and allows more wireless access systems to access, including the following network elements:
  • the Mobility Management Entity is a control plane function entity that temporarily stores user data. It is responsible for managing and storing the context of user equipment (UE, User Equipment), such as user identification, mobility management status, and user security. The parameter, etc., allocates a temporary identifier to the user, and when the UE is camped on the tracking area or the network, it is responsible for authenticating the user.
  • UE User Equipment
  • the parameter, etc. allocates a temporary identifier to the user, and when the UE is camped on the tracking area or the network, it is responsible for authenticating the user.
  • the Serving Gateway is a user plane entity that is responsible for user plane data routing processing and terminates downlink data of UEs in idle (ECM_IDLE) state. Manage and store the SAE bearer context of the UE, such as IP bearer service parameters and network internal routing information.
  • the S-GW is the anchor point of the internal user plane of the 3GPP system. A user can only have one S-GW at a time.
  • the packet data network gateway (PGW, PDN Gateway) is the gateway responsible for the UE accessing the PDN, and assigns the user IP address. It is also the mobility anchor of the 3GPP and non-3GPP access systems.
  • the PGW functions include policy implementation and charging support. . Users can access multiple PGWs at the same time.
  • the Policy and Charging Enforcement Function (PCEF) is also located in the PGW.
  • the Policy and Charging Rules Function (PCRF) is responsible for providing policy control and charging rules to the PCEF.
  • PCF Policy and Charging Rules Function
  • SPR Subscription Database
  • SP Subscription Profile Repository
  • the Home Subscriber Server (HSS) is responsible for permanently storing user subscription data.
  • the content stored in the HSS includes the UE's International Mobile Subscriber Identification (IMSI) and the IP address of the PGW.
  • IMSI International Mobile Subscriber Identification
  • the SGW and the PGW may be unified.
  • the EPC system user plane network element includes the SGW and the PGW.
  • MTC Server Machine Type Communication Server
  • MTC Server is mainly responsible for information collection and data storage/processing of MTC equipment, and necessary management of MTC equipment.
  • MTC Machine Type Communication User Equipment
  • M2M service is a networked application and service based on intelligent interaction of machine terminals. It uses intelligent machine terminals to transmit information through wireless networks, and provides information solutions for customers to meet customer monitoring, command and dispatch. Information needs for data collection and measurement.
  • the source eNodeB moves from the source eNodeB to the target eNodeB, the source eNodeB needs to initiate the handover, and the source eNodeB can initiate the handover from the X2 interface and the S1 interface.
  • the target eNodeB or the target MME is in the network congestion state, This switch request can be rejected.
  • FIG. 2 is a process of describing an X2 handover performed by a radio side to a target eNodeB when the UE is moved to the target eNodeB by the UE, specifically including:
  • S201 The UE accesses the EPS network, and performs data interaction with the remote end by using the established EPS bearer.
  • the source eNodeB initiates a measurement control command to the UE, and configures the location restriction information and the measurement rule of the UE.
  • the UE according to the measurement rule or system information, the location information is included in the measurement report and sent to the source eNodeB;
  • the source eNodeB selects the target eNodeB according to the location information provided in the measurement report, and determines to initiate the handover.
  • the source eNodeB initiates a handover (HO, handover) request to the target eNodeB, and carries a radio bearer setup context (RRC context), a target cell identifier (Target Cell ID), a signaling context (Signling context), and a radio resource assignment context (E- RAB context ) Waiting for the HO parameter to the target eNodeB;
  • RRC context radio bearer setup context
  • Target Cell ID target cell identifier
  • Signaling context Signaling context
  • E- RAB context radio resource assignment context
  • the target eNodeB If the target eNodeB allows handover, allocate radio resources according to the QoS (Quality of Service) parameter in the E-RAB. When the eNodeB is in a congested state and there is no available radio resource, the target eNodeB rejects the handover request initiated by the source eNodeB;
  • QoS Quality of Service
  • the target eNodeB is congested, and sends a handover reject message (HO failure) to the source eNodeB, rejecting the request of the source eNodeB.
  • HO failure handover reject message
  • the source eNodeB After receiving the handover reject message, the source eNodeB selects another available target eNodeB according to the cell ID of the UE, and attempts to initiate the handover.
  • the source eNodeB needs to send an RRC reconfiguration message to the UE, and switch the wireless connection of the UE to the target eNodeB.
  • FIG. 3 is a process of the S1 handover performed by the core network side when the UE is moved to the target eNodeB by the source eNodeB in the prior art, and specifically includes:
  • the UE accesses the EPS network, and performs data interaction with the remote end by using the established EPS bearer.
  • the source eNodeB determines to initiate a handover to the target eNode through the S1 interface (HO is initiated);
  • the source eNodeB initiates a handover request (HO request;) to the source MME, and carries the transparent data of the source eNodeB to the target eNodeB, the target tracking area identifier (targer TAI), and the ID of the target eNodeB.
  • HO request a handover request
  • targer TAI target tracking area identifier
  • the source MME selects the target MME according to the Target TAI information, and sends a forward redirect request to the target MME, where the MME UE context, the target tracking area identifier Target TAI, and the source eNodeB to the target eNodeB transparent data are carried.
  • Information such as the ID of the target eNodeB, and the MME UE context includes information such as an IMSI, a terminal capability, an S-GW address, a P-GW address, and an APN.
  • the target MME determines, according to the Target TAI, whether a new S-GW needs to be selected. Selecting a new S-GW, the target MME needs to re-establish the EPS bearer between the target S-GW and the P-GW;
  • the target MME sends a handover request message (for example, a redirection request) to the target eNodeB, and carries the S-GW entry address, the EPS Bear QoS parameter, the source eNodeB to the target eNodeB transparent data, and requests to perform handover;
  • a handover request message for example, a redirection request
  • the target eNodeB is in network congestion, and if there is no radio resource allocation, the handover request is rejected.
  • the target eNodeB sends a handover failure message (for example, a redirection request rejection) to the target MME, rejects the handover request, and the target MME releases the network resource reserved for the terminal.
  • a handover failure message for example, a redirection request rejection
  • the target MME deletes the established session by sending a delete session request message.
  • the target MME sends a forward redirect redirection message to the source MME, rejecting the current handover;
  • the source MME After receiving the redirect reject message, the source MME returns a handover failure message (HO failure) to the source eNodeB.
  • HO failure handover failure
  • the number of MTC terminals may be more than 10 times the number of mobile terminals.
  • Each MTC terminal has access to the 3GPP network for data communication as long as it has a 3GPP communication module. If a large-scale deployment of MTC terminals accesses concurrent data at the same time, it will inevitably bring congestion to all levels of the wireless network, signaling network, and data transmission, causing M2M devices to access and transmit data barriers, which may seriously cause network defects. .
  • the prior art only proposes a handover method initiated by the source eNodeB for a common terminal such as a mobile phone.
  • a common terminal such as a mobile phone.
  • the MTC terminal there is no corresponding method yet. If the handover of the MTC terminal is performed according to the method of the ordinary terminal, the MTC will be used because of the MTC.
  • the number of terminals is far greater than that of ordinary terminals, which has a lot of impact on the services of the existing network, such as congestion on the existing network, which affects the normal use and user experience of the existing network services.
  • the main object of the present invention is to provide a congestion control method, apparatus, and system for MTC handover, which are to solve the problem that the handover caused by MTC terminal mobility affects the normal service of the ordinary terminal and causes network congestion.
  • the present invention provides a congestion control method in an MTC handover, where the method includes: in a process of performing an MTC handover, the target eNodeB or the target MME determines according to the acquired MTC information of the MTC terminal and the current network load state. Whether it is in a network congestion state, if yes, refuses to perform the current handover; otherwise, continues the current handover.
  • the target eNodeB determines whether the network is in a network congestion state according to the obtained MTC information of the MTC terminal and the current network load status, and is: according to the received handover request initiated by the source eNodeB.
  • the MTC information of the MTC terminal, and the current network load status the target eNodeB determines whether it is in a network congestion state; if yes, rejects the handover request of the source eNodeB, and sends a handover failure message to the source eNodeB; otherwise, accepts the Switch the request and continue the subsequent operations of the current switch.
  • the method further includes: acquiring, by the source eNodeB, the MTC information of the MTC terminal from the MTC terminal or the source MME, and The target eNodeB initiates a handover request carrying the MTC information.
  • the target MME determines whether it is in a network congestion state according to the obtained MTC information of the MTC terminal and the current network load status, and is: according to the forward forwarding redirection request sent by the source MME. MTC information of the MTC terminal carried, And the current network load status, the target MME determines whether it is in a network congestion state; if yes, rejects the forward redirect request, and sends a forward redirect request rejection message to the source MME; otherwise, accepts the source MME Forwards the redirect request and sends a redirect request to the currently switched target eNodeB.
  • the method before the target MME receives the forward redirection request that carries the MTC information, the method further includes: the source MME acquiring the MTC information of the MTC terminal, and sending the MTC information to the target MME Send a forward redirect request carrying the MTC information.
  • the source MME acquires the MTC information, when the MTC terminal is attached to the network where the source MME is located, the MTC terminal carries its own MTC information to the source MME by using an attach request; Or, when the MTC terminal is attached to the network where the source MME is located, the source MME obtains the MTC information of the MTC terminal from the quality of service (QoS) parameter of the MTC terminal.
  • QoS quality of service
  • the target MME sends a redirection request to the currently-switched target eNodeB, where: the target MME sends a redirection request carrying the MTC information of the MTC terminal to the currently-switched target eNodeB;
  • the method further includes: the target eNodeB receiving the redirect request, determining, according to the MTC information of the MTC terminal carried in the redirect request, and the current network load status, whether the network is currently in a network congestion state, and if yes, rejecting the Redirecting a request, sending a redirect request rejection message to the target MME; otherwise, continuing the subsequent operation of the current handover.
  • the method further includes: after receiving the redirect request rejection message, the target MME sends the source MME to the current handover. Returning a forward redirect request rejection message, rejecting the current forward redirect request of the source MME; afterwards, the source MME reselects the target MME, and sends a forward carrying the MTC information to the selected target MME Redirecting the request; or, the source MME returns a handover failure message to the source eNodeB of the current handover, notifying the source The eNodeB currently fails to switch.
  • the handover failure message, and the forward redirection request rejection message include a cause value and/or a waiting time, where the cause value is an indication that the target eNodeB or the target MME is currently in a network congestion state;
  • the waiting time is used to indicate the time elapsed by the source eNodeB or the source MME from the current rejection to the selection of the target eNodeB or the target MME again.
  • the MTC information includes any one or more of the following three types of information: an MTC indication (MTC Indication), a ⁇ priority indication (Low Priority), and an MTC ARP.
  • MTC Indication MTC Indication
  • ⁇ priority indication Low Priority
  • MTC ARP MTC ARP
  • the present invention also provides a congestion control apparatus in an MTC handover, where the apparatus includes: an obtaining unit, a determining unit, a rejecting unit, and an accepting unit, wherein the acquiring unit is configured to acquire the MTC during the MTC switching process.
  • a determining unit configured to determine, according to the MTC information of the MTC terminal acquired by the acquiring unit, and the current network load status, whether the target eNodeB or the target MME is in a network congestion state, and if yes, starting the rejecting unit, Otherwise, the accepting unit is activated; the rejecting unit is used to reject the current switching; and the accepting unit is used to continue the current switching.
  • the present invention also provides a congestion control system in an MTC handover, where the system includes: a source eNodeB and a target eNodeB, where the source eNodeB is configured to acquire MTC information of the MTC terminal from an MTC terminal or a source MME, and The target eNodeB initiates a handover request that carries the MTC information.
  • the target eNodeB includes: a first acquiring unit, a first determining unit, a first rejecting unit, and a first accepting unit, where the first acquiring unit is configured to receive the Determining the MTC information of the MTC terminal carried in the handover request initiated by the source eNodeB; the first determining unit, configured to: according to the MTC information of the MTC terminal carried in the handover request received by the first obtaining unit, and the current network load status, Determining whether the target eNodeB itself is in a network congestion state, if yes, starting the first rejecting unit, otherwise starting the first accepting unit; the first rejecting unit, for rejecting the switching request of the source eNodeB,
  • the source eNodeB sends a handover failure message; a first accepting unit, configured to accept a handover request of the source eNodeB, and continue a subsequent operation of the current handover.
  • the present invention also provides a congestion control system in an MTC handover, the system includes: a source MME and a target MME, where the source MME is configured to acquire MTC information of the MTC terminal, and send the carried to the target MME The forwarding request of the MTC information;
  • the target MME includes: a second acquiring unit, a second determining unit, a second rejecting unit, and a second receiving unit, where the second acquiring unit is configured to receive the carried by the target MME a request for redirection of the MTC information of the MTC terminal;
  • the first determining unit configured to determine, according to the MTC information of the MTC terminal carried in the redirection request received by the second obtaining unit, and the current network load status, the target MME itself Whether the network is in a network congestion state, if yes, the second rejection unit is started, otherwise, the second accepting unit is started;
  • the first rejecting unit is configured to reject the forward redirect request, and send a forward redirect redirect to the source MME. Requesting
  • the second receiving unit of the target MME is configured to send, to the currently switched target eNodeB, a redirection request that carries the MTC information; the system further includes: the target eNodeB, where the target eNodeB includes a third obtaining unit, a third determining unit, a third rejecting unit, and a third accepting unit, wherein the third obtaining unit is configured to receive the redirect request sent by the second accepting unit of the target MME; a determining unit, configured to determine, according to the MTC information of the MTC terminal carried in the redirection request received by the third acquiring unit, and the current network load status, whether the target eNodeB is currently in a network congestion state, and if so, the startup The third rejecting unit; otherwise, the third accepting unit is activated; the third rejecting unit is configured to reject the redirect request, and send a redirect request rejection message to the target MME; and a third accepting unit, configured to accept The redirect request continues the subsequent operations of the current handover.
  • the source MME is further configured to: receive a forward redirect request rejection message sent by the target MME; after that, reselect the target MME and send the selected target MME to the selected target MME.
  • the target MME further includes a receiving feedback unit, the receiving The feedback unit is configured to receive a redirect request rejection message returned by the target eNodeB, and send a forward redirect rejection message to the source MME.
  • the present invention proposes a congestion control scheme for a handover of an MTC terminal, and the target eNodeB or the target MME determines whether it is in a network congestion state according to the obtained MTC information of the MTC terminal; and rejects or allows the current handover according to the judgment result, in the MTC.
  • the congestion control of the target network for the MTC terminal is implemented, and the impact of the MTC handover on the live network is minimized, so that the normal service of the ordinary UE is not subject to a large number of MTC terminals.
  • the effect of frequent switching when moving thus effectively preventing network congestion, and maximizing the effective use of network resources through network optimization.
  • FIG. 1 is a schematic diagram of an architecture of an EPS network system in the prior art
  • FIG. 2 is a flowchart of performing X2 handover when a normal UE moves from a source eNodeB to a target eNodeB in the prior art
  • FIG. 3 is a flowchart of performing S1 handover when a normal UE moves from a source eNodeB to a target eNodeB in the prior art
  • FIG. 5 is a schematic flowchart of an implementation process of performing congestion control in an X2 handover process when an MTC UE moves from a source eNodeB to a target eNodeB according to the present invention
  • FIG. 6 is a schematic flowchart of an implementation process of performing congestion control in an S1 handover process when an MTC UE moves from a source eNodeB to a target eNodeB according to the present invention
  • FIG. 7 is a schematic diagram of another implementation flow of congestion control in an X2 handover process when an MTC UE moves from a source eNodeB to a target eNodeB according to the present invention
  • FIG. 8 is a flowchart of the present invention when an MTC UE moves from a source eNodeB to a target eNodeB, Another implementation flow diagram of congestion control during SI handover. detailed description
  • the basic idea of the present invention is: when the MTC terminal moves from the wireless area of the source eNodeB to the wireless area of the target eNodeB, during the handover process, the congestion control for the MTC terminal is performed, thereby preventing the handover caused by the movement of the MTC terminal from affecting the ordinary terminal. Normal business.
  • a congestion control method in MTC handover according to the present invention mainly includes the following steps:
  • Step 401 The target eNodeB or the target MME obtains the MTC information of the MTC terminal during the MTC handover.
  • Step 402 The target eNodeB or the target MME determines whether the network is in a network congestion state according to the obtained MTC information of the MTC terminal and the current network load status. If yes, the current handover is refused; otherwise, the current handover is continued.
  • the MTC information may include any one or more of the following three types of information: an MTC indication (MTC Indication), a low priority indication (Low Priority), and an MTC allocation and retention priority (ARP).
  • MTC Indication MTC Indication
  • Low Priority Low Priority
  • ARP MTC allocation and retention priority
  • the MTC Indication is used to indicate the MTC UE itself, and the Low Priority is used to indicate that the MTC UE is a low priority MTC terminal.
  • the bearer-level QoS parameters include QCI, ARP, GBR guaranteed bit rate, MBR maximum bit rate, and AMBR aggregation maximum bit rate.
  • ARP and QCI are used in GBR and Non-GBR bearers.
  • the main purpose of ARP is In the case of resource restrictions, it is decided to accept or reject the establishment or modification request of the bearer. At the same time, ARP is used for special resource restrictions, such as switching, to decide which bearer to drop. Once the bearer is successfully established, ARP does not affect the transmission of the packet.
  • ARP defines 1 to 15 levels for bearer allocation and handover control of common terminals.
  • MTC ARP of the MTC terminal it is used for the load distribution and handover control of the MTC terminal, which can be defined by the specific value of the MTC ARP to be compared with the common terminal.
  • ARP is distinguished. For example, you can define 20 to 30 levels for MTC ARP.
  • Each network element in the network can determine whether the current bearer is established, modified, or switched based on the ARP.
  • One mode is that there is an X2 interface between the source eNodeB and the target eNodeB, and the source eNodeB directly initiates the handover to the target eNodeB through the X2 interface.
  • the other way is between the source eNodeB and the target eNodeB. Without the X2 interface, the source eNodeB initiates a handover directly to the target eNodeB through the S1 interface.
  • the source eNodeB in the current MTC handover acquires the MTC information of the MTC terminal from the MTC terminal or the source MME, and initiates carrying the MTC to the target eNodeB.
  • Information switching request For the handover using the X2 interface, the specific implementation process of the present invention is as follows: The source eNodeB in the current MTC handover acquires the MTC information of the MTC terminal from the MTC terminal or the source MME, and initiates carrying the MTC to the target eNodeB. Information switching request;
  • the target eNodeB receives the handover request initiated by the source eNodeB, and determines whether it is in a network congestion state according to the MTC information of the MTC terminal carried in the handover request and the current network load status; if yes, rejects the handover of the source eNodeB. Requesting, sending a handover failure message to the source eNodeB; otherwise, accepting the handover request, continuing the subsequent operation of the current handover.
  • the handover failure message includes a cause value and/or a waiting time, where the cause value is specifically an indication that the target eNodeB is currently in a network congestion state; the waiting time is used to indicate that the source eNodeB is from the current rejection to the current selection again. The time elapsed by the target eNodeB.
  • the MTC terminal When the MTC terminal is attached to the network where the source MME is located, the MTC terminal carries its own MTC information to the source MME of the current handover by using an attach request; or, the MTC terminal is attached to the network where the source MME is located.
  • the source MME obtains the MTC information of the MTC terminal from the quality of service (QoS) parameter of the MTC terminal. Sending, by the source MME, a forward redirect request carrying the acquired MTC information to the target MME;
  • QoS quality of service
  • the target MME of the current handover receives the forward redirection request sent by the source MME, and determines whether it is in a network congestion state according to the MTC information of the MTC terminal carried in the MTC terminal and the current network load status; if yes, rejecting the forward transfer weight Orienting the request, sending a forward redirect request rejection message to the source MME; otherwise, accepting the forward redirect request of the source MME, and sending a redirect request to the currently switched target eNodeB.
  • the redirection request sent by the target MME to the currently switched target eNodeB is specifically a redirection request that carries the MTC information of the MTC terminal.
  • the method may further include: the target eNodeB receiving the redirect request sent by the target MME, and determining whether the network is currently in the network according to the MTC information of the MTC terminal carried in the redirect request and the current network load status.
  • the congestion state if yes, rejecting the redirect request, sending a redirect request rejection message to the target MME; otherwise, continuing the subsequent operation of the current handover.
  • the method further includes: after receiving the redirect request rejection message, the target MME returns a forward redirect request to the source MME that is currently handed over. Rejecting the message, rejecting the current forward redirect request of the source MME; then, the source MME reselects the target MME, and sends a forward redirect request carrying the MTC information to the selected target MME, or The source MME returns a handover failure message to the source eNodeB that is currently handed over, and notifies the source eNodeB that the current handover fails.
  • the handover failure message and the forward redirect request rejection message include a cause value and/or a waiting time, where the cause value is specifically an indication that the target MME is currently in a network congestion state; the waiting time is used to Indicates the time elapsed by the source MME from the current rejection to the selection of the target MME again.
  • the present invention further provides a congestion control apparatus in an MTC handover, where the apparatus mainly includes: an obtaining unit, a determining unit, a rejecting unit, and an accepting unit, where the acquiring unit is configured to perform the MTC switching process.
  • the determining unit configured to determine, according to the MTC information of the MTC terminal acquired by the acquiring unit, and the current network load status, whether the target eNodeB or the target MME is in a network congestion state, and if yes, start Reject the unit, otherwise, start the accepting unit; reject the unit, to reject the current switch; accept the unit, to continue the current switch.
  • the congestion control apparatus in the above MTC handover may be specifically provided on the target eNodeB or the target MME capable of MTC handover, or may be independently provided, but connected to the target eNodeB or the target MME.
  • the present invention also provides a congestion control system in two types of MTC handovers: a congestion control system in a first type of MTC handover, which is applicable to handover using an X2 interface, where the system includes: a source eNodeB and a target eNodeB, where ,
  • a source eNodeB configured to acquire MTC information of the MTC terminal from an MTC terminal or a source MME, and initiate a handover request that carries the MTC information to the target eNodeB;
  • the target eNodeB includes: a first acquiring unit, a first determining unit, a first rejecting unit, and a first accepting unit, where the first acquiring unit is configured to receive MTC information of the MTC terminal carried in the handover request initiated by the source eNodeB a first determining unit, configured to determine, according to the MTC information of the MTC terminal carried in the handover request received by the first acquiring unit, and the current network load status, whether the target eNodeB itself is in a network congestion state, and if yes, start Determining, by the first rejecting unit, the first accepting unit, the first rejecting unit, configured to reject a handover request of the source eNodeB, and send a handover failure message to the source eNodeB; Accepting the handover request of the source eNodeB, continuing the subsequent operation of the current handover.
  • the congestion control system in the second MTC handover is applicable to the S1 interface.
  • the system includes: a source MME and a target MME, where
  • the source MME is configured to obtain MTC information of the MTC terminal, and send a forward redirect request that carries the MTC information to the target MME.
  • the target MME includes: a second obtaining unit, a second determining unit, a second rejecting unit, and a second receiving unit, where the second acquiring unit is configured to receive, by the target MME, a redirection of the MTC information that carries the MTC terminal a first determining unit, configured to determine, according to the MTC information of the MTC terminal carried in the redirection request received by the second acquiring unit, and the current network load status, whether the target MME itself is in a network congestion state, and if yes, Then, the second rejecting unit is started, otherwise, the second accepting unit is started; the first rejecting unit is configured to reject the forward redirecting redirect request, and send a forward redirect request rejection message to the source MME; the first accepting unit, A forward redirect request for accepting the source MME, and sending a redirect request to the currently switched target eNodeB.
  • the second receiving unit of the target MME is specifically configured to send, to the currently switched target eNodeB, a redirection request that carries the MTC information.
  • the system further includes: the target eNodeB, the target eNodeB specifically includes: a third obtaining unit, a third determining unit, a third rejecting unit, and a third accepting unit, wherein the third obtaining unit is configured to receive the target And the third determining unit is configured to: according to the MTC information of the MTC terminal carried in the redirection request received by the third acquiring unit, and the current network load status, Determining whether the target eNodeB is currently in a network congestion state, if yes, starting the third reject unit; otherwise, starting the third accepting unit; and third rejecting unit, for rejecting the redirect request, to the target
  • the MME sends a redirect request rejection message, and the third accepting unit is configured to accept the redirect request and continue the subsequent operation of the current handover.
  • the source MME is further configured to: receive a forward redirect request rejection message sent by the target MME; after that, reselect the target MME, and send the carried to the selected target MME. Forwarding redirection request with the MTC information, or returning a handover failure message to the source eNodeB that initiates the current handover, notifying the source eNodeB that the current handover fails; the target MME further includes a receiving feedback unit, and the receiving feedback The unit is configured to receive a redirect request rejection message returned by the target eNodeB, and send a forward redirect rejection message to the source MME.
  • a congestion control method is performed in the X2 switching process when the MTC UE moves from the source eNodeB to the target eNodeB.
  • the MTC UE accesses the EPS network and performs data communication with the MTC Server.
  • the MTC UE moves from the source eNodeB radio area to the target eNodeB radio area, and the source eNodeB initiates a handover request to the target eNodeB, carries the MTC indication (MTC Indication) of the MTC UE, and/or a low priority indication (Low Priority), indicating the target eNodeB performs MTC switching.
  • MTC Indication MTC Indication
  • Low Priority Low Priority
  • the target eNodeB performs MTC handover according to the handover request: determining whether it is in a network congestion state set in the MTC setting or other congestion control, and if yes, rejecting the handover request to avoid affecting the existing network; otherwise, Continue the subsequent switching operations.
  • the MTC UE is connected to the EPS network, and performs data exchange with the remote MTC Server (not shown in FIG. 5) through the established EPS bearer to perform data transmission.
  • the source eNodeB acquires the MTC Indication of the MTC UE, and/or the MTC information such as the Low Priority from the MTC UE, and establishes a context in its own radio bearer after the RRC is successfully established.
  • the MTC information is saved in (RRC Context).
  • the source eNodeB initiates a measurement control command to the MTC UE, and configures location restriction information and measurement rules of the MTC UE.
  • the MTC UE according to the measurement rule, including its own location information in the measurement report and sent to the source eNodeB;
  • the source eNodeB selects a target eNodeB for the MTC UE according to the location information provided in the measurement report sent by the MTC UE, and determines to initiate a handover (ie, HO initiation).
  • the source eNodeB sends an HO request to the target eNodeB, and carries an HO parameter such as an RRC context, a Target Cell ID, a Signalling context, and an E-RAB context to the target eNodeB.
  • the RRC context includes the MTC Indication of the MTC UE, and/or Low
  • the target eNodeB performs MTC congestion control, and detects that the current network load has reached a pre-configured network congestion threshold, and determines that the network is in a network congestion state.
  • the target eNodeB after receiving the handover request, the target eNodeB searches for the MTC information in the RRC Context included therein, and determines whether the network congestion state is based on the found MTC information and the pre-configured network congestion threshold, and according to the judgment result, Decide whether to switch.
  • the target eNodeB after receiving the handover request including the MTC Indication, and/or Low Priority of the MTC UE, the target eNodeB detects the current network load, for example, can detect the current CPU load average value, and considers the overload if it reaches the 80% level; Or, the statistics of the interface traffic are used for judging. For example, the target eNodeB can only process 100G traffic. If the traffic has reached 80M, the network is considered overloaded. After that, the target eNodeB determines according to the MTC Indication, and/or Low Priority of the MTC UE. Whether the current network load reaches the pre-configured network congestion threshold. If yes, it determines that it is in the network congestion state and decides to reject the handover request. Otherwise, it determines that it is in the normal network state and allows MTC handover.
  • the current network load for example, can detect the current CPU load average value, and considers the overload if it reaches the 80% level; Or, the statistics of the interface
  • the network congestion threshold for the MTC handover needs to be configured in advance on the target eNodeB according to the operator policy.
  • the network congestion threshold for MTC handover can be configured as follows:
  • Manner 1 When the handover request includes MTC Indication and Low Priority, or only includes Low Priority, the network load reaches 40% for congestion control, that is, setting corresponding The first network congestion threshold is 40%; when the handover request includes only the MTC Indication, the network load reaches 50% for congestion control, that is, the corresponding second network congestion threshold is set to 50%;
  • the target eNodeB sends a handover failure message (HO failure) to the source eNodeB, and rejects the handover request of the source eNodeB.
  • HO failure handover failure message
  • the target eNodeB may carry a cause value (cause) and/or a first waiting time in the handover failure message, and notify the source eNodeB that the current network is congested.
  • the cause is the indication that the target eNodeB is currently in the network congestion state, and is used to notify the source eNodeB that the current handover request fails because the target eNodeB is currently in a network congestion state.
  • the first waiting time is used to indicate the time elapsed by the source eNodeB from the current rejection to the current target eNodeB, that is, the source eNodeB does not select the target eNodeB to attempt to switch before the waiting time overflows.
  • the first waiting time may be pre-configured in the target eNodeB, and is generally determined according to the statistical result of the network state of the target eNodeB, which is an empirical value. During the busy period of the target eNodeB, a longer first waiting time can be configured, and during the idle period of the target eNodeB, a shorter first waiting time can be configured.
  • the source eNodeB After receiving the handover failure message, the source eNodeB selects another available target eNodeB for the MTC UE according to the location information of the MTC UE provided in the measurement report, and attempts to initiate a handover request; or before the first waiting time overflows, The source eNodeB then attempts to initiate a handover request to the current target eNodeB.
  • the source eNodeB after performing the above congestion control, as long as the target eNodeB accepts the source The handover request of the eNodeB, the source eNodeB sends an RRC reconfiguration message to the MTC UE, and switches the wireless connection of the MTC UE to the target eNodeB that accepts the handover request.
  • the source eNodeB sends an RRC reconfiguration message to the MTC UE, and the MTC UE The wireless connection is switched to the target eNodeB that accepts the handover request, and the handover of the MTC UE from the source eNodeB to the target eNodeB is completed.
  • the present embodiment is a congestion control method in the process of performing an S1 handover when the MTC UE moves from the source eNodeB to the target eNodeB.
  • the MTC terminal MTC UE accesses the EPS network and performs data communication with the MTC server. .
  • the MTC UE moves from the source eNodeB radio area to the target eNodeB radio area, and the source eNodeB initiates a handover request to the source MME through the S1 interface, and the source MME initiates a forward redirection request to the target MME, and carries the MTC Indication, and/or Low of the MTC UE.
  • the target MME Priority, indicating that the target MME performs MTC handover; after receiving the forward redirect request, the target MME performs MTC handover: determining whether it is in a network congestion state set by the MTC, and if yes, rejecting the forward redirect request No, it performs a subsequent handover operation, the target MME initiates a redirection request to the target eNodeB, carries the MTC Indication of the MTC UE, and/or Low Priority, and then the target eNodeB performs an MTC handover operation according to the redirection request. That is, it is judged whether it is in the network congestion state set by the MTC, and if so, the redirection request is rejected to avoid affecting the existing network; otherwise, the subsequent switching operation is performed.
  • the MTC UE has accessed the EPS network, and performs data exchange with the remote MTC Server (not shown in FIG. 6) through the established EPS bearer to perform data transmission;
  • the MTC UE When the MTC UE attaches to the EPS network, it carries its own MTC in the attach request. After the attachment is successful, the source MME stores the identifier information of the MTC UE and the MTC information such as the MTC Indication and/or the Low Priority in the currently carried MM context.
  • the source eNodeB determines to initiate a handover to the target eNode through the S1 interface (HO is initiated);
  • the source eNodeB initiates a handover request (HO request;) to the source MME, and carries the HO parameters such as the transparent data of the source eNodeB to the target eNodeB, the Targer TAI, the ID of the target eNodeB, and the identifier information of the MTC UE, such as the IMSI of the MTC UE. .
  • HO request a handover request
  • the source MME carries the HO parameters such as the transparent data of the source eNodeB to the target eNodeB, the Targer TAI, the ID of the target eNodeB, and the identifier information of the MTC UE, such as the IMSI of the MTC UE.
  • the source MME selects a target MME according to the Target TAI in the handover request, and sends a forward redirect request to the target MME, and carries the forwarding MME in the forward redirect request.
  • Target TAI transparent data from the source eNodeB to the target eNodeB, and the ID of the target eNodeB.
  • the MME UE context includes the IMSI, the terminal capability, the S-GW address, the P-GW address, the access point name (APN, Access Point Name), and the currently hosted MM context of the MTC UE.
  • the MM context includes MTC information such as MTC Indication and/or Low Priority of the MTC UE.
  • the target MME performs MTC congestion control, and detects that the current network load has reached a pre-configured network congestion threshold, and determines that the network is in a network congestion state.
  • the target MME after receiving the forward redirect request, the target MME searches for the MTC information in the MME UE context of the forward redirect request, and determines whether the network is in the network according to the found MTC information and the pre-configured network congestion threshold. Congestion status, and based on the judgment result, decide whether to switch.
  • the target MME After receiving the forward redirection request including the MTC Indication, and/or the Low Priority, the target MME detects the current network load, and the detection method of the specific detection target eNodeB is similar, and is not described in detail; Whether the network load reaches the pre-configured The network congestion threshold, if yes, determines that it is in a network congestion state, and decides to reject the forward redirect request; otherwise, it determines that it is in a normal network state, and allows subsequent MTC handover operations.
  • the network congestion threshold for the MTC handover needs to be configured in advance in the target MME according to the operator policy.
  • the configuration may be performed in the first mode or the second mode in the step S506.
  • the specific value of the configured network congestion threshold may be different from that in the step S506, and determined according to the network operation status of the target MME.
  • the target MME sends a forward redirect redirection message to the source MME, and rejects the forward redirect request of the source MME.
  • the forward redirect redirection message may carry the cause and the second waiting time, notify the source MME that the network is congested, and the source MME does not select the target MME to attempt to perform handover before the waiting time overflows.
  • the cause is specifically an indication that the target MME is currently in a network congestion state, and the reason for the failure of the source MME to notify the current handover request is that the target MME is currently in a network congestion state.
  • the second waiting time is used to indicate the time that the source MME has to go from being currently rejected to selecting the current target MME again.
  • the second waiting time may be pre-configured in the target MME, and is generally determined according to the statistical result of the target MME network status, which is an empirical value.
  • a longer second waiting time can be configured, and during the idle period of the target MME, a shorter second waiting time can be configured.
  • the source MME After receiving the forward redirect redirection message, the source MME selects another available target MME and attempts to initiate a forward redirect request, or after the second waiting time overflows, the source MME selects the current target MME to try again. Forward the redirect request.
  • the source MME when all MMEs reject the current forward redirect request of the source MME, the source MME returns a handover failure message (HO failure) to the source eNodeB, and notifies the source eNodeB that the handover fails.
  • the handover failure message may also include a cause, and the cause may be an indication that all available target MMEs are currently in a network congestion state, and the reason for notifying the source eNodeB that the current handover request fails is that all available target MMEs are currently in the Network congestion status.
  • the target MME can accept the current forwarding request of the source MME, the target MME that accepts the current forwarding request of the source MME sends a redirect request message to the target eNodeB, and carries the S-GW entry address and the EPS Bear. – requesting to perform handover by using QoS parameters, source eNodeB to target eNodeB transparent data, and MTC Indication and/or Low Priority information of the MTC UE;
  • step 5610 which is basically the same as step 506, except that the target eNodeB finds the MTC Indication and/or Low of the MTC UE from the redirect request message sent by the target MME.
  • Priority MTC information when it is judged that the network is in a network congestion state, it decides to reject the redirect request, and determines that it is in the normal state of the network, and allows subsequent MTC handover.
  • the target eNodeB After the target eNodeB receives the redirect request message, if the target eNodeB is in the normal state of the network, the handover is allowed, the EPS Bear-QoS is implicitly transmitted to the E-RAB QoS, and the radio resource is allocated to the MTC UE according to the QoS parameter; If the target eNodeB is in a network congestion state, it decides to reject the redirect request initiated by the target MME, and then sends a redirect reject message to the target MME.
  • the target eNodeB sends a redirect reject message to the target MME, rejects the redirect request message of the target MME, and the target MME releases the network resource reserved for the MTC UE.
  • the redirection reject message may further carry a cause, and the cause is specifically an indication that the target eNodeB is currently in a network congestion state, and is used to notify the target MME that the current redirection request is rejected because the target eNodeB is currently in a network congestion state.
  • the target MME sends a forward redirect redirection message to the source MME, and rejects the current forward redirection request of the source MME.
  • the forward redirect redirection message may also carry a cause, the cause and the step
  • the reason in S61 1 is that the source eMME is notified that the current forwarding redirection request is rejected because the target eNodeB is currently in a network congestion state.
  • the source MME After receiving the forwarding redirection rejection message, the source MME returns a handover failure message to the source eNodeB, and notifies the source eNodeB that the current handover fails.
  • the handover failure message may also carry a cause, which is the same as that in step S611, and is used to notify the source eNodeB that the current handover request is rejected because the target eNodeB is currently in a network congestion state.
  • This embodiment is another congestion control method in the process of performing the X2 handover when the MTC UE moves from the source eNodeB to the target eNodeB.
  • the MTC terminal MTC UE accesses the EPS network and performs data with the MTC server. Communication.
  • the MTC UE moves from the source eNodeB radio area to the target eNodeB radio area, and the source eNodeB initiates a handover to the target eNodeB, carrying the MTC ARP of the MTC UE, instructing the target eNodeB to perform MTC handover; and after receiving the handover request, the target eNodeB performs MTC handover: Determine whether it is in the network congestion state set by the MTC. If yes, reject the handover request to avoid affecting the existing network; if not, continue to perform subsequent handover operations.
  • the MTC UE allocates an MTC ARP to the bearer during the establishment of the bearer.
  • the MTC UE When attaching to the EPS network, the MTC UE first establishes an RRC connection and initiates an attach request to the source MME.
  • the source MME establishes an EPS bearer for the MTC UE, and returns an EPS Bearer context to the source eNodeB, carrying the QoS parameter, where the QoS parameter includes the MTC ARP of the MTC UE.
  • the source eNodeB maps the QoS parameters to E-RAB QoS parameters, and establishes a radio EPS bearer, and saves the E-RAB QoS parameters of the MTC ARP including the MTC UE in the E-RAB Context.
  • the MTC UE has access to the EPS network, and the established EPS bearer and remote end MTC Server (not shown in Figure 7) performs data interaction;
  • step S505 which is basically the same as step S505.
  • the MTC Indication of the MTC UE is not included in the RRC context, and/or the Low Priority, but the MTC ARP of the MTC UE is included in the E-RAB context to indicate The destination eNodeB performs MTC handover;
  • step S506 substantially the same as step S506, the difference is: the target eNodeB does not determine whether the current network load reaches the pre-configured network congestion threshold according to the MTC Indication, and/or the Low Priority, but detects the current network according to the MTC ARP of the MTC UE. Whether the load reaches the preset network congestion threshold and determines whether it is in a network congestion state.
  • the network congestion threshold for configuring MTC handover in the target eNodeB is different in implementation.
  • the corresponding congestion control threshold may be preset in the target eNodeB according to the network running status of the target eNodeB for different levels of the MTC ARP.
  • the target eNodeB After receiving the handover request carrying the MTC ARP, the target eNodeB verifies whether the current network load reaches its corresponding network congestion threshold according to the level of the MTC ARP, and if yes, determines that the network is in a network congestion state, and determines The handover request is rejected; otherwise, it is determined that it is in the normal state of the network, and subsequent MTC handover is allowed.
  • step S708-S710 which is exactly the same as step S507-509.
  • This embodiment is another congestion control method in the process of performing the S1 handover when the MTC UE moves from the source eNodeB to the target eNodeB.
  • the MTC terminal accesses the EPS network and performs data communication with the MTC Server.
  • the MTC UE moves from the source eNodeB radio area to the target eNodeB radio area, and the source eNodeB initiates a handover request to the source MME through the S1 interface, and the source MME initiates a forward redirection request to the target MME, and carries the MTC ARP.
  • the target MME identifies that it is an MTC handover, determines whether it is in a network congestion state set by the MTC, and if so, rejects the forward redirect request; otherwise, performs a subsequent handover operation, and the target MME continues. Initiating a redirection request to the target eNodeB, the target eNodeB identifies the MTC handover, and determines whether it is in the network congestion state set by the MTC. If yes, the redirection request is rejected to avoid affecting the existing network. Otherwise, the subsequent execution is performed. Switch operations. As shown in FIG. 8, the specific process of this embodiment is as follows:
  • the MTC UE allocates MTC ARP to the bearer.
  • the network signs the HSS or SPR.
  • the MTC ARP of the MTC UE, and the MTC ARP is included in the QoS parameters allocated for the EPS bearer, and is stored in the EPS Bearer Context currently carried in the source MME.
  • step S702 which is identical to step S702;
  • the MME UE context carried by the forward redirect request includes: an IMSI of the MTC UE, a terminal capability, an S-GW address, a P-GW address, an APN, and the EPS.
  • Information such as QoS parameters in the Bearer Context.
  • the QoS parameter includes the MTC ARP of the MTC UE.
  • step S605 which is basically the same as step S605.
  • the target MME when it receives the forward redirect request, it searches for the MTC ARP in the MME UE Context, and determines whether it is in accordance with the MTC ARP and the pre-configured network congestion threshold. Network congestion status.
  • the process of configuring the network congestion threshold of the MTC handover in the target MME is the same as that in step S707.
  • the difference is that the specific value of the congestion control threshold can be set according to the network operating status of the target MME.
  • the target MME After receiving the forward redirection request carrying the MTC ARP, the target MME verifies whether the current network load reaches its corresponding network congestion threshold according to the level of the MTC ARP, and if yes, determines that it is in network congestion. The state determines to reject the forward redirect request; otherwise, it determines that it is in the normal state of the network, allowing subsequent MTC handover.
  • S807-S809 which are completely the same as steps S606 ⁇ S608; S810, which is substantially the same as step S609, except that the redirect request message sent by the target MME to the target eNodeB carries information such as an ingress address of the S-GW, an EPS Bear QoS parameter, and a transparent data of the source eNodeB to the target eNodeB, and the request is performed.
  • the MTC ARP of the MTC UE is included in the EPS Bearer QoS parameter.
  • step S811 which is substantially the same as step S610.
  • the target eNodeB finds the MTC ARP of the MTC UE from the redirect request message sent by the target MME, and determines whether the network is in the network according to the MTC ARP of the found MTC UE.
  • the congestion state, the specific process of judgment, and the process of setting the network congestion threshold in advance are the same as step S707. According to the judgment result, the subsequent operation is different from step S707.
  • the target eNodeB receives the redirect request and will redirect the requested EPS.
  • Bear Licates MTC ARP in QoS, based on the MTC ARP found.
  • the target eNodeB allows the handover, implicitly transmits the EPS Bear QoS to the E-RAB QoS, and allocates the radio resource according to the QoS parameter, and decides to reject the redirection request when determining that it is in the network congestion state. .

Landscapes

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

Abstract

La présente invention concerne un procédé pour le contrôle de congestion dans le transfert intercellulaire de circuit principal de télécommunications (MTC), le procédé comprenant les étapes suivantes: lors d'un processus de transfert intercellulaire de circuit MTC, la détermination par un nœud B évolué cible ou une entité de gestion de mobilité cible (MME) pour savoir si le nœud B évolué cible ou l'entité MME cible se trouve dans un état de congestion de réseau selon l'information de circuit MTC acquise d'un terminal de circuit MTC et un statut de charge courante de réseau; dans l'affirmative, le refus du transfert intercellulaire en cours; dans le cas contraire, la poursuite du transfert intercellulaire en cours. L'invention concerne également un dispositif et un système de contrôle de congestion dans un transfert intercellulaire de circuit MTC. L'influence du transfert intercellulaire de circuit MTC sur le réseau courant est réduite à un degré minimal, de sorte qu'un service normal d'un équipement utilisateur commun ne soit pas affecté par un transfert intercellulaire fréquent lors du déplacement d'un grand nombre de terminaux de circuit MTC, permettant ainsi d'empêcher une congestion de réseau, et une utilisation efficace des ressources de réseau à un degré maximal grâce à l'optimisation de réseau.
PCT/CN2011/081872 2010-11-08 2011-11-07 Procédé, dispositif, et système pour le contrôle de congestion dans le transfert intercellulaire de circuit principal de télécommunications (mtc) WO2012062193A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010535875.3 2010-11-08
CN201010535875.3A CN102469503B (zh) 2010-11-08 Mtc切换中的拥塞控制方法及装置、系统

Publications (1)

Publication Number Publication Date
WO2012062193A1 true WO2012062193A1 (fr) 2012-05-18

Family

ID=46050406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081872 WO2012062193A1 (fr) 2010-11-08 2011-11-07 Procédé, dispositif, et système pour le contrôle de congestion dans le transfert intercellulaire de circuit principal de télécommunications (mtc)

Country Status (1)

Country Link
WO (1) WO2012062193A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2996393A4 (fr) * 2013-07-04 2017-01-18 Nec Corporation Système, procédé et dispositif de communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007130325A2 (fr) * 2006-05-01 2007-11-15 Interdigital Technology Corporation Procédé et appareil pour faciliter le transfert sans perte dans des systèmes 3gpp à évolution à long terme
CN102045777A (zh) * 2011-01-17 2011-05-04 西安电子科技大学 用于蜂窝网的高效机器类通信接入控制方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007130325A2 (fr) * 2006-05-01 2007-11-15 Interdigital Technology Corporation Procédé et appareil pour faciliter le transfert sans perte dans des systèmes 3gpp à évolution à long terme
CN102045777A (zh) * 2011-01-17 2011-05-04 西安电子科技大学 用于蜂窝网的高效机器类通信接入控制方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP TS 22.368 V10.0.0 (2010-03): Service requirements for Machine-Type Communications (MTC); Stage 1 (Release 10)", TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS, March 2010 (2010-03-01) *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2996393A4 (fr) * 2013-07-04 2017-01-18 Nec Corporation Système, procédé et dispositif de communication
US9883440B2 (en) 2013-07-04 2018-01-30 Nec Corporation System, method, and apparatus for establishing a connection between a terminal and a network node

Also Published As

Publication number Publication date
CN102469503A (zh) 2012-05-23

Similar Documents

Publication Publication Date Title
KR102633426B1 (ko) 무선 네트워크에 의한 무선 디바이스 페이징
JP7416368B2 (ja) 時間依存ネットワーキングのための制御プレーンに基づく設定
US11012907B2 (en) Method and system for transferring user equipment in mobile communication system
KR102310309B1 (ko) 이동 통신 시스템에서 음성 호 설정 시간을 단축시키는 방법 및 장치
US9813865B2 (en) Network-initiated control method and apparatus for providing proximity service
KR101973462B1 (ko) 접속 해제를 수행하는 방법 및 그 단말
US9648653B2 (en) User equipment-initiated control method and apparatus for providing proximity service
US9504005B2 (en) Method for processing data associated with location area update in a wireless communication system
US9532202B2 (en) Access control method, access control apparatus and communication system
WO2011134329A1 (fr) Procédé et système pour transmettre des paquets de données de petite taille
KR20150014834A (ko) 특정 서비스를 지속적으로 제공하는 방법 및 장치
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
JP7283868B2 (ja) ユーザ装置、制御装置、及び通信制御方法
WO2011060673A1 (fr) Procédé d'établissement de support public, procédé de transmission de données et appareil du côté du cœur de réseau
WO2012094957A1 (fr) Procédé et système pour effecteur une gestion de mobilité sur un terminal mtc
US20160183127A1 (en) Methods, systems and devices for supporting local breakout in small cell architecture
JP7283869B2 (ja) ユーザ装置、制御装置、及び通信制御方法
WO2014048085A1 (fr) Procédé de commande pour la connexion entre un équipement utilisateur et un réseau et équipement de gestion de la mobilité
JP2014510456A (ja) 共有ネットワークのアクセス制御方法、アクセスネットワークノード及びコアネットワークノード
WO2008014684A1 (fr) Procédé permettant la mise en oeuvre de l'équilibrage des charges
WO2011135790A1 (fr) Dispositif de communication et nœud de réseau
WO2012062193A1 (fr) Procédé, dispositif, et système pour le contrôle de congestion dans le transfert intercellulaire de circuit principal de télécommunications (mtc)
KR102354644B1 (ko) 이동 통신 시스템에서 음성 호 설정 시간을 단축시키는 방법 및 장치
CN102469503B (zh) Mtc切换中的拥塞控制方法及装置、系统

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

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

Country of ref document: EP

Kind code of ref document: A1