WO2013091161A1 - Procédé et appareil d'optimisation de robustesse de mobilité - Google Patents

Procédé et appareil d'optimisation de robustesse de mobilité Download PDF

Info

Publication number
WO2013091161A1
WO2013091161A1 PCT/CN2011/084215 CN2011084215W WO2013091161A1 WO 2013091161 A1 WO2013091161 A1 WO 2013091161A1 CN 2011084215 W CN2011084215 W CN 2011084215W WO 2013091161 A1 WO2013091161 A1 WO 2013091161A1
Authority
WO
WIPO (PCT)
Prior art keywords
connection
network node
link failure
failure information
user equipment
Prior art date
Application number
PCT/CN2011/084215
Other languages
English (en)
Inventor
Yang Liu
Haitao Li
Original Assignee
Nokia Corporation
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 Nokia Corporation filed Critical Nokia Corporation
Priority to PCT/CN2011/084215 priority Critical patent/WO2013091161A1/fr
Publication of WO2013091161A1 publication Critical patent/WO2013091161A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • 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
    • 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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present invention generally relates to communication networks. More specifically, the invention relates to Mobility Robustness Optimization (MRO).
  • MRO Mobility Robustness Optimization
  • Radio Link Failure for example during a handover procedure may be caused by many reasons, such as coverage hole, handover too early, handover too late, handover to wrong cell, and etc. Except for coverage hole, if the handover failure occurred in a handover procedure is caused by improper handover (HO) parameter settings in the network side, it is desired definitely to avoid such RLF to improve the success rate of the handover procedure, which can obtain a good user performance for operators. MRO may be used to do such network optimization.
  • LTE Long Term Evolution
  • RLF Radio Link Failure
  • MRO may be used to do such network optimization.
  • the present description introduces a new MRO solution for providing link failure information for a source network node at which a link failure occurs to make a wise decision on a link failure issue.
  • a method comprising: maintaining a first connection between a first network node and a user equipment (UE), and a second connection between a second network node and the UE; and sending, through the first connection, link failure information of the second connection to the first network node for transferring the link failure information to the second network node, in response to a failure of the second connection.
  • UE user equipment
  • an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: maintaining a first connection between a first network node and the apparatus, and a second connection between a second network node and the apparatus; and sending, through the first connection, link failure information of the second connection to the first network node for transferring the link failure information to the second network node, in response to a failure of the second connection.
  • a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer, the computer program code comprising: code for maintaining a first connection between a first network node and a UE, and a second connection between a second network node and the UE; and code for sending, through the first connection, link failure information of the second connection to the first network node for transferring the link failure information to the second network node, in response to a failure of the second connection.
  • an apparatus comprising: maintaining means for maintaining a first connection between a first network node and the apparatus, and a second connection between a second network node and the apparatus; and sending means for sending, through the first connection, link failure information of the second connection to the first network node for transferring the link failure information to the second network node, in response to a failure of the second connection.
  • the link failure information may be transferred to the second network node directly. In another exemplary embodiment, the link failure information may be transferred to the second network node through a network entity. According to exemplary embodiments, one of the first connection and the second connection may be used for local network services, and the other may be used for macro network services.
  • the method according to the first aspect of the present invention may further comprise: keeping the link failure information at the UE; establishing a third connection between a third network node and the UE; and reporting, through the third connection, the link failure information to the third network node for transferring the link failure information to the second network node.
  • the apparatus may further comprise: keeping means for keeping the link failure information at the apparatus; establishing means for establishing a third connection between a third network node and the apparatus; and reporting means for reporting, through the third connection, the link failure information to the third network node for transferring the link failure information to the second network node.
  • a method comprising: maintaining a first connection between a first network node and a UE, the UE having a second connection with a second network node; receiving link failure information of the second connection from the UE through the first connection, in response to a failure of the second connection; and transferring the link failure information to the second network node.
  • an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: maintaining a first connection between the apparatus and a UE, the UE having a second connection with another apparatus; receiving link failure information of the second connection from the UE through the first connection, in response to a failure of the second connection; and transferring the link failure information to the another apparatus.
  • a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer, the computer program code comprising: code for maintaining a first connection between a first network node and a UE, the UE having a second connection with a second network node; code for receiving link failure information of the second connection from the UE through the first connection, in response to a failure of the second connection; and code for transferring the link failure information to the second network node.
  • an apparatus comprising: maintaining means for maintaining a first connection between the apparatus and a UE, the UE having a second connection with another apparatus; receiving means for receiving link failure information of the second connection from the UE through the first connection, in response to a failure of the second connection; and transferring means for transferring the link failure information to the another apparatus.
  • the apparatus in the sixth/eighth aspect of the present invention may comprise a first network node, and the another apparatus in the sixth/eighth aspect of the present invention may comprise a second network node.
  • said transferring the link failure information to the second network node may comprise one of the following s: sending the link failure information to the second network node directly, and sending the link failure information to the second network node through a network entity.
  • one of the first connection and the second connection may be used for local network services, and the other may be used for macro network services.
  • a ninth aspect of the present invention there is provided a method comprising: maintaining a second connection between a second network node and a UE, the UE having a first connection with a first network node; and obtaining, from the first network node, link failure information of the second connection which is reported by the UE to the first network node through the first connection, in response to a failure of the second connection.
  • an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: maintaining a second connection between the apparatus and a UE, the UE having a first connection with another apparatus; and obtaining, from the another apparatus, link failure information of the second connection which is reported by the UE to the another apparatus through the first connection, in response to a failure of the second connection.
  • a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer, the computer program code comprising: code for maintaining a second connection between a second network node and a UE, the UE having a first connection with a first network node; and code for obtaining, from the first network node, link failure information of the second connection which is reported by the UE to the first network node through the first connection, in response to a failure of the second connection.
  • an apparatus comprising: maintaining means for maintaining a second connection between the apparatus and a UE, the UE having a first connection with another apparatus; and obtaining means for obtaining, from the another apparatus, link failure information of the second connection which is reported by the UE to the another apparatus through the first connection, in response to a failure of the second connection.
  • the apparatus in the tenth/ twelfth aspect of the present invention may comprise a second network node, and the another apparatus in the tenth/ twelfth aspect of the present invention may comprise a first network node.
  • said obtaining the link failure information of the second connection may comprise one of the followings: receiving the link failure information from the first network node directly, and receiving the link failure information from the first network node through a network entity.
  • the method according to the ninth aspect of the present invention may further comprise: determining a reason for the failure of the second connection based at least in part on the link failure information.
  • the apparatus may further comprise: determining means for determining a reason for the failure of the second connection based at least in part on the link failure information.
  • the method according to the ninth aspect of the present invention may further comprise: receiving from a third network node the link failure information which is reported by the UE to the third network node through a third connection established in response to the failure of the second connection.
  • the provided methods, apparatus, and computer program products can enable the number of procedures of link failure judgment to be decreased significantly. Meanwhile, less time and fewer resources in radio and backhaul may be involved in the whole procedure, which makes MRO more attractive for implementation with higher efficiency.
  • Fig.l exemplarily shows handover too late counting procedures in MRO
  • Fig.2A is a flowchart illustrating a method for MRO, which may be performed at a UE in accordance with embodiments of the present invention
  • Fig.2B is a flowchart illustrating a method for MRO, which may be performed at a first network node in accordance with embodiments of the present invention
  • Fig.2C is a flowchart illustrating a method for MRO, which may be performed at a second network node in accordance with embodiments of the present invention
  • Fig.3A shows an exemplary MRO scenario where a local connection is used with a direct interface between a serving evolved Node B (eNB) and a serving Access Point (AP) in accordance with an embodiment of the present invention
  • eNB serving evolved Node B
  • AP serving Access Point
  • Fig.3B shows an exemplary MRO scenario where a local connection is used with an indirect interface between a serving eNB and a serving AP in accordance with another embodiment of the present invention
  • Fig.4 shows exemplary MRO scenarios where a macro network connection is used with a direct/indirect interface between a serving eNB and a serving AP in accordance with embodiments of the present invention
  • Fig.5 is a simplified block diagram of various apparatuses which are suitable for use in practicing exemplary embodiments of the present invention. DETAILED DESCRIPTION OF THE INVENTION
  • LAE Local Area Evolution
  • QoS Quality of Service
  • SN Support Node
  • RAN Radio Access Network
  • HeNB Home eNB
  • LTE-LAN Another architecture called as LTE-LAN is researched to compete with world-wide popular Wireless Fidelity (WiFi) technique.
  • LTE-LAN is basically assumed to be based on LTE technology but is more focused on some local area use cases and scenarios, and it has much similarity with LAE concept.
  • LTE-LAN is also expected to provide high performance services for users with low cost.
  • a BS in LAE architecture may be considered as an AP in LTE-LAN system.
  • LTE-LAN and LTE macro network are independent networks which may operate in different bands. So far, an X2-like or SI -like interface may be introduced between different APs and between an AP and an eNB, since a lot of features (for example carrier aggregation, interference management, etc.) would be developed with this interface.
  • a UE may experience a RLF for example during a communication procedure or experience a handover failure during a handover procedure.
  • MRO is one of the major features of Self-Optimized Network (SON) function introduced in Release 8 (Rel-8) in 3GPP.
  • Release 9 (Rel-9) and Release 10 (Rel-10) the implementation of MRO has involved efforts from both RAN2 and RAN3, and some complicated procedures are also defined for MRO.
  • Fig.l exemplarily shows handover too late counting procedures in MRO, which may be used for a source eNB where a RLF occurred to make a correct decision for a RLF case as in Rel-9 and Rel-10.
  • a UE has a connection with a serving eNB (which may be called as a source eNB here). If a RLF occurred on this connection, for example when a handover procedure is ongoing for this UE, the UE may initiate a Radio Resource Control (RRC) connection re-establishment procedure to a new eNB (which is shown as Re-estab eNB in Fig.l), for example according to the current specification.
  • RRC Radio Resource Control
  • the UE may report RLF relevant information (for example, Reference Signal Received Power & Reference Signal Received Quality (RSRP&RSRQ) of serving cell and neighboring cell before the RLF) to the new eNB using a dedicated signaling (for example, UE Information Request/Response). Then the RLF information may be transferred from the new eNB to the source eNB where the RLF happened to help judge potential improper settings of HO parameters of a network. For example, a first RLF indication may be counted as a handover too late case as shown in Fig.l.
  • RLF relevant information for example, Reference Signal Received Power & Reference Signal Received Quality (RSRP&RSRQ) of serving cell and neighboring cell before the RLF
  • a dedicated signaling for example, UE Information Request/Response.
  • the RLF information may be transferred from the new eNB to the source eNB where the RLF happened to help judge potential improper settings of HO parameters of a network. For example, a first RLF indication
  • the UE may return to an idle mode and the network side can never get the RLF information from the UE.
  • this has been overcome by introducing an enhanced mechanism in which the UE keeps the RLF information and uses a future potential RRC establishment procedure to indicate a new eNB that the UE has the RLF information to report, which may trigger the subsequent network retrievement and information transfer procedure among eNBs.
  • the UE may initiate a RRC connection setup procedure to a new eNB, and indicate to a network that the RLF information is available.
  • the new eNB may retrieve the RLF information from the UE with a dedicate RRC signaling. As such, the new eNB may transfer the RLF information to the source eNB to help check whether its previous judgment of RLF reasons is right, and a modification may be made accordingly if necessary.
  • a communication system such as LTE-LAN and LAE network, for example, a
  • RLF may also occur during a communication procedure or a handover failure may occur during a handover procedure as in the LTE system.
  • Rel-10 as shown in Fig.l are employed, at least seven steps or messages in air interfaces and backhaul interfaces are used to get a correct result for a RLF scenario.
  • RAN2 for example, indication bit in RRC connection request message and RRC connection re-establishment request message, UE Information Request/Response
  • RAN3 for example, RLF indication, handover report
  • RLF indication, handover report works, which is too complicated for implementation and also time consuming.
  • the network side would never get RLF information, which may cause a wrong judgment of RLF reasons and trigger a wrong adjustment of network HO parameters, leading to more issues such as frequent handover failure problems.
  • it is desirable to define a new simple MRO solution which can skip complicated information exchange procedures involved in RAN2 and RAN3.
  • Fig.2A is a flowchart illustrating a method for MRO, which may be performed at a UE in accordance with embodiments of the present invention. In this method, a
  • UE such as a mobile station, a wireless terminal, a personal digital assistant (PDA), a portable device and the like
  • PDA personal digital assistant
  • a portable device may maintain a first connection with a first network node (such as a BS, an eNB, an AP, a control center and the like) and a second connection with a second network node (such as a BS, an eNB, an AP, a control center and the like), as shown in block 212.
  • the UE may maintain two independent RRC connections, one with its serving eNB and the other with its serving AP.
  • the first network node and the second network node may be the same kind of network nodes.
  • one of the first and the second connections may be used for local network services (for example, high speed data services in a local area), and the other of the first and the second connections may be used for macro network services (for example, more stable and more carefully managed services in a macro network).
  • a failure may occur on one of the first and second connections.
  • the UE may send, through the first connection, link failure information of the second connection to the first network node for transferring the link failure information to the second network node, as shown in block 214.
  • the link failure information may be transferred to the second network node from the first network node directly.
  • the link failure information may be transferred to the second network node from the first network node through a network entity (such as a Mobility Management Entity (MME) or other suitable intermediate entity in core networks).
  • MME Mobility Management Entity
  • the UE may use any existing signaling massages (such as "MeasurementReport") or newly defined signaling messages to send the link failure information.
  • the UE may keep the link failure information, and when it could establish a third connection with a third network node (such as a BS/eNB/AP/control center, etc.) in the future, the UE may report, through the third connection, the link failure information to the third network node for transferring the link failure information to the second network node.
  • a third network node such as a BS/eNB/AP/control center, etc.
  • the third network node and the second network node may belong to the same kind of communication network.
  • the third connection may comprise a re-established connection for the services previously supported by the second connection, or a future potential connection established by the UE in a network in which the second network node is located.
  • Fig.2B is a flowchart illustrating a method for MRO, which may be performed at a first network node in accordance with embodiments of the present invention.
  • the first network node (such as a BS/eNB/AP/control center, etc.) may maintain a first connection with a UE which may have a second connection with a second network node, as shown in block
  • the first and the second network nodes may support different services in two independent networks.
  • the first network node may support services in a macro network and the second network node may support services in a local network, and vice versa.
  • the first network node may receive link failure information of the second connection from the UE through the first connection.
  • the first network node may transfer the link failure information to the second network node.
  • said transferring the link failure information to the second network node may comprise one of the folio wings: sending the link failure information to the second network node directly, and sending the link failure information to the second network node through a network entity.
  • the link failure information may be transferred to the second network node via a direct interface between the first network node and the second network node, for example with any existing massages (such as those defined in TS 36.423) or newly defined messages.
  • the direct interface may comprise an X2-like interface, or a SI -like interface defined for direct data transmission.
  • the link failure information may be transferred to the second network node via an indirect interface between the first network node and the second network node, for example with any existing massages (such as SI massages defined in TS 36.413) or newly defined messages.
  • the link failure information may be transferred to a network entity (such as MME or other intermediate network entity) via a SI -like interface between the first network node and the network entity, and then forwarded by the network entity to the second network node via a SI -like interface between the network entity and the second network node.
  • a network entity such as MME or other intermediate network entity
  • the direct interface may have higher priority over the indirect interface to be selected for transferring the link failure information.
  • Fig.2C is a flowchart illustrating a method for MRO, which may be performed at a second network node in accordance with embodiments of the present invention.
  • the second network node corresponds to the description with respect to Fig.2A.
  • a BS/eNB/AP/control center may maintain a second connection with a BS/eNB/AP/control center, etc.
  • UE which may have a first connection with a first network node, as shown in block
  • the second network node may obtain, from the first network node, link failure information of the second connection which is reported by the UE to the first network node through the first connection.
  • said obtaining the link failure information of the second connection may comprise one of the followings: receiving the link failure information from the first network node directly, and receiving the link failure information from the first network node through a network entity.
  • direct reception may have higher priority than indirect reception.
  • the second network node may receive from a third network node the link failure information which is reported by the UE to the third network node through a third connection established in response to the failure of the second connection.
  • the second network node may obtain the link failure information from the third network node via a direct interface between them, such as an X2-like interface.
  • the second network node may determine a reason for the failure of the second connection.
  • Figs.2A-2C may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function(s).
  • the schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
  • a UE may maintain two independent connections for communications, and if a link failure occurs on one connection of them, then the UE can report link failure information utilizing the other connection, so that a source network node losing connection can make correct judgment on failure reasons based at least in part on the reported link failure information.
  • a link failure occurs in the macro network side, for example when the UE loses its connection with a source serving network node (such as an eNB) in the macro network, the UE can report link failure information through its connection with a local serving network node (such as an AP), then the local serving network node can transfer corresponding information to the source serving network node of the UE, so as to assist the source serving network node to judge reasons of the failure case.
  • a source serving network node such as an eNB
  • the local serving network node can transfer corresponding information to the source serving network node of the UE, so as to assist the source serving network node to judge reasons of the failure case.
  • the UE also can report link failure information utilizing its connection with a macro serving network node, so that a local serving network node which lost its connection with the UE can obtain the link failure information from the macro serving network node.
  • the solution of the present invention may involve only two steps or messages to provide essential information for a source serving network node to make a wise decision on the RLF issue, which is much more efficient and simpler, and also timesaving.
  • the source serving network node thus can obtain RLF information using less time and less resource both in radio and backhaul.
  • Fig.3A shows an exemplary MRO scenario where a local connection is used with a direct interface between a serving eNB and a serving AP in accordance with an embodiment of the present invention
  • Fig.3B shows an exemplary MRO scenario where a local connection is used with an indirect interface between a serving eNB and a serving AP in accordance with another embodiment of the present invention.
  • a UE may maintain two RRC connections with a communication system, one is with a macro eNB (shown as the serving eNB in Figs.3A-3B) and the other is with a local AP such as LTE-LAN AP (shown as the serving AP in Figs.3A-3B).
  • a RLF may occur in the macro network side.
  • the UE may send RLF information (for example, "rlf-InfoAvailable-rlO" in current specification TS 36.331) to the serving AP using the existing RRC connection between the UE and the serving AP.
  • RLF information transmission can use any current uplink RRC messages such as "MeasurementReport", or use other new defined uplink RRC message containing RLF information such as "rlf-InfoAvailable-rlO" information.
  • the serving AP may transfer the obtained RLF information to the serving eNB of the UE, for example by utilizing direct interfaces with current message already defined in TS 36.423 "RLF INDICATION".
  • the RLF information may be transferred by the serving AP to a network entity (such as the MME in Fig.3B), then forwarded from the MME to the serving eNB.
  • these messages may comprise any existing messages (for example, SI messages such as "eNB/MME CONFIGURATION TRANSFER") or other new type of defined message containing the RLF information.
  • the UE may optionally initiate a RRC connection re-establishment procedure for a new eNB (shown as Re-estab eNB in
  • Figs.3A-3B in the macro network side, for example according to current specifications.
  • the UE may send a RLF indication to a source eNB (corresponding to the serving eNB in Figs.3A-3B) where the RLF happened to inform this issue.
  • a source eNB corresponding to the serving eNB in Figs.3A-3B
  • the source eNB of the UE can make a correct judgment on failure reasons. For example, upon determination of a handover failure reason, the source eNB may treat this failure event as coverage hole or handover too late, and then make a HO parameter adjustment accordingly to improve handover success rate and provide better user experience.
  • MRO also can be used in a scenario where a RLF occurs in a local area.
  • a UE may utilize a macro RRC connection to transfer
  • Fig.4 shows exemplary MRO scenarios where a macro network connection is used with a direct/indirect interface between a serving eNB and a serving AP in accordance with embodiments of the present invention.
  • a UE may maintain two RRC connections with a communication system, one is with a macro eNB (shown as the serving eNB in Fig.4) and the other is with a local AP such as a
  • the UE may send RLF information (for example, "rlf-InfoAvailable-rlO" in current specification TS 36.331) to the serving eNB using the existing macro RRC connection.
  • RLF information transmission can use any current uplink RRC messages such as "MeasurementReport", or use other new defined uplink RRC message containing RLF information such as "rlf-InfoAvailable-rlO" information.
  • the serving eNB may transfer the
  • RLF information to a source AP (corresponding to the serving AP in Fig.4) of the UE where the RLF happened, with a direct interface (as shown by the upper half of the block in Fig.4) utilizing current messages already defined in TS 36.423 "RLF
  • UE may optionally initiate a RRC connection re-establishment procedure for a new
  • the source AP in the local network side, for example according to current specifications.
  • the source AP may send a RLF indication to the source AP to inform this issue.
  • the source AP of the UE can make a correct judgment on failure reasons. For example, upon determination of a handover failure reason, the source AP may treat this failure event as coverage hole or handover too late, and then make a HO parameter adjustment accordingly to improve handover success rate and provide better user experience.
  • the number of procedures of handover too late judgment can be decreased from 7 steps to 2 steps, and less time as well as fewer resources in radio and backhaul may be involved in the whole procedure, which makes MRO more attractive for implementation with higher efficiency.
  • Fig.5 is a simplified block diagram of various apparatuses which are suitable for use in practicing exemplary embodiments of the present invention.
  • a UE 530 such as mobile phone, wireless terminal, portable device, PDA, multimedia tablet, and etc.
  • the first network node 510 such as a BS/eNB/AP/control center, etc.
  • the second network node 520 such as a BS/eNB/AP/control center, etc.
  • the UE 530 may comprise a data processor (DP) 530A, a memory (MEM) 530B that stores a program (PROG) 530C, and a suitable transceiver 530D for communicating with an apparatus such as another UE, a network node, a server and so on.
  • the first network node 510 may comprise a data processor (DP) 51 OA, a memory (MEM) 510B that stores a program (PROG) 5 IOC, and a suitable transceiver 510D for communicating with an apparatus such as the second network node 520, a UE 530 or a network entity (not shown in Fig.5).
  • the second network node 520 may comprise a data processor (DP) 520A, a memory (MEM) 520B that stores a program (PROG) 520C, and a suitable transceiver 520D for communicating with an apparatus such as the first network node 510, the UE 530 or a network entity (not shown in Fig.5).
  • DP data processor
  • MEM memory
  • PROG program
  • a suitable transceiver 520D for communicating with an apparatus such as the first network node 510, the UE 530 or a network entity (not shown in Fig.5).
  • at least one of the transceivers 510D, 520D, 530D may be an integrated component for transmitting and/or receiving signals and messages.
  • at least one of the transceivers 510D, 520D, 530D may comprise separate components to support transmitting and receiving signals/messages, respectively.
  • the respective DPs 510A, 520A and 530A may be used for processing these signals and
  • the UE 530, the first network node 510 and the second network node 520 may comprise various means and/or components for implementing functions of the foregoing steps and methods in Fig.2A-2C.
  • the UE 530 may comprise: maintaining means for maintaining a first connection between a first network node (such as the first network node 510) and the
  • the UE 530 may further comprise: keeping means for keeping the link failure information at the UE; establishing means for establishing a third connection between a third network node and the UE; and reporting means for reporting, through the third connection, the link failure information to the third network node for transferring the link failure information to the second network node.
  • the first network node 510 may comprise: maintaining means for maintaining a first connection between the first network node and a UE (such as the UE 530) which may have a second connection with a second network node (such as the second network node 520); receiving means for receiving link failure information of the second connection from the UE through the first connection, in response to a failure of the second connection; and transferring means for transferring the link failure information to the second network node.
  • a UE such as the UE 530
  • second network node such as the second network node 520
  • the second network node 520 may comprise: maintaining means for maintaining a second connection between the second network node 520 and a UE (such as the UE 530) which may have a first connection with a first network node (such as the first network node 510); and obtaining means for obtaining, from the first network node, link failure information of the second connection which is reported by the UE to the first network node through the first connection, in response to a failure of the second connection.
  • the second network node 520 may further comprise: determining means for determining a reason for the failure of the second connection based at least in part on the link failure information.
  • At least one of the PROGs 5 IOC, 520C, 530C is assumed to comprise program instructions that, when executed by the associated DP, enable an apparatus to operate in accordance with the exemplary embodiments, as discussed above. That is, the exemplary embodiments of the present invention may be implemented at least in part by computer software executable by the DP 51 OA of the first network node 510, by the DP 520A of the second network node 520 and by the DP 530A of the UE 530, or by hardware, or by a combination of software and hardware.
  • the MEMs 510B, 520B and 530B may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the DPs 510A, 520A and 530A may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples.
  • DSPs digital signal processors
  • the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the exemplary embodiments of this invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • exemplary embodiments of the inventions may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device.
  • the computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, random access memory (RAM), and etc.
  • the functionality of the program modules may be combined or distributed as desired in various embodiments.
  • the functionality may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA), and the like.

Landscapes

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

Abstract

L'invention concerne un procédé d'optimisation de robustesse de mobilité, lequel procédé consiste à : maintenir une première connexion entre un premier nœud de réseau et un équipement utilisateur, et une seconde connexion entre un second nœud de réseau et l'équipement utilisateur ; et envoyer, par l'intermédiaire de la première connexion, des informations d'échec de liaison de la seconde connexion au premier nœud de réseau pour transférer les informations d'échec de liaison au second nœud de réseau, en réponse à un échec de la seconde connexion.
PCT/CN2011/084215 2011-12-19 2011-12-19 Procédé et appareil d'optimisation de robustesse de mobilité WO2013091161A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/084215 WO2013091161A1 (fr) 2011-12-19 2011-12-19 Procédé et appareil d'optimisation de robustesse de mobilité

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/084215 WO2013091161A1 (fr) 2011-12-19 2011-12-19 Procédé et appareil d'optimisation de robustesse de mobilité

Publications (1)

Publication Number Publication Date
WO2013091161A1 true WO2013091161A1 (fr) 2013-06-27

Family

ID=48667624

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/084215 WO2013091161A1 (fr) 2011-12-19 2011-12-19 Procédé et appareil d'optimisation de robustesse de mobilité

Country Status (1)

Country Link
WO (1) WO2013091161A1 (fr)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104080111A (zh) * 2013-03-29 2014-10-01 宏碁股份有限公司 网络分集式错误回报方法、使用者设备及通信系统
US20140295825A1 (en) * 2013-03-29 2014-10-02 Acer Incorporated Network diversity based error reporting method and user equipment using the same
WO2015033015A1 (fr) * 2013-09-09 2015-03-12 Nokia Corporation Détection et récupération à partir d'une perte de connexion de petites cellules
CN104581984A (zh) * 2013-10-28 2015-04-29 财团法人工业技术研究院 处理上行链路传送的方法及其通信装置
GB2519975A (en) * 2013-11-01 2015-05-13 Nec Corp Communication system
US20150133122A1 (en) * 2013-11-08 2015-05-14 Industrial Technology Research Institute Method of Handling Radio Link Failure
WO2015133954A1 (fr) 2014-03-03 2015-09-11 Telefonaktiebolaget L M Ericsson (Publ) Orientation de sélection de mobilité et/ou d'accès entre des cellules
WO2015143914A1 (fr) * 2014-03-28 2015-10-01 中国移动通信集团公司 Procédé, dispositif et système de commande de communication pour un terminal mobile
TWI556663B (zh) * 2014-12-25 2016-11-01 宏達國際電子股份有限公司 處理與多個基地台間通訊的失敗的方法及其裝置
EP3048748A4 (fr) * 2013-09-18 2017-07-26 China Mobile Communications Corporation Procédé de communications entre terminaux mobiles, dispositif et équipement apparenté
US9723533B2 (en) 2013-08-12 2017-08-01 Samsung Electronics Co., Ltd Method of handling radio link failure in wireless communication system based on multi-eNB connectivity and apparatus thereof
CN108093447A (zh) * 2017-12-20 2018-05-29 中磊电子（苏州）有限公司 基站切换参数调整方法
EP3337227A4 (fr) * 2015-08-11 2018-07-18 KDDI Corporation Dispositif de station de base, dispositif de communication, procédé de commande et programme
CN108307524A (zh) * 2016-09-19 2018-07-20 华为技术有限公司 链路建立方法及设备与无线通信系统
US10334498B2 (en) * 2014-01-28 2019-06-25 Huawei Technologies Co., Ltd. Service transfer method and apparatus
US20210352752A1 (en) * 2013-02-28 2021-11-11 Nec Corporation Radio communication system, radio station, radio terminal, communication control method, and non-transitory computer readable medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1608356A (zh) * 2001-12-29 2005-04-20 联想(北京)有限公司 长短距结合的无线通信系统及其方法
CN102217353A (zh) * 2008-11-17 2011-10-12 高通股份有限公司 无线电链路故障报告
CN102273262A (zh) * 2009-01-06 2011-12-07 高通股份有限公司 切换失败消息传送方案

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1608356A (zh) * 2001-12-29 2005-04-20 联想(北京)有限公司 长短距结合的无线通信系统及其方法
CN102217353A (zh) * 2008-11-17 2011-10-12 高通股份有限公司 无线电链路故障报告
CN102273262A (zh) * 2009-01-06 2011-12-07 高通股份有限公司 切换失败消息传送方案

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210352752A1 (en) * 2013-02-28 2021-11-11 Nec Corporation Radio communication system, radio station, radio terminal, communication control method, and non-transitory computer readable medium
US11812489B2 (en) 2013-02-28 2023-11-07 Nec Corporation Radio communication system, radio station, radio terminal, communication control method, and non-transitory computer readable medium
US11723102B2 (en) * 2013-02-28 2023-08-08 Nec Corporation Radio communication system, radio station, radio terminal, communication control method, and non-transitory computer readable medium
CN104080111A (zh) * 2013-03-29 2014-10-01 宏碁股份有限公司 网络分集式错误回报方法、使用者设备及通信系统
US20140295825A1 (en) * 2013-03-29 2014-10-02 Acer Incorporated Network diversity based error reporting method and user equipment using the same
US10887812B2 (en) 2013-08-12 2021-01-05 Samsung Electronics Co., Ltd Method of handling radio link failure in wireless communication system based on multi-eNB connectivity and apparatus thereof
US10512019B2 (en) 2013-08-12 2019-12-17 Samsung Electronics Co., Ltd. Method of handling radio link failure in wireless communication system based on multi-eNB connectivity and apparatus thereof
US10225784B2 (en) 2013-08-12 2019-03-05 Samsung Electronics Co., Ltd. Method of handling radio link failure in wireless communication system based on multi-eNB connectivity and apparatus thereof
US9723533B2 (en) 2013-08-12 2017-08-01 Samsung Electronics Co., Ltd Method of handling radio link failure in wireless communication system based on multi-eNB connectivity and apparatus thereof
WO2015033015A1 (fr) * 2013-09-09 2015-03-12 Nokia Corporation Détection et récupération à partir d'une perte de connexion de petites cellules
US9930589B2 (en) 2013-09-09 2018-03-27 Nokia Technologies Oy Detection and recovery from loss of small cell connection
EP3048748A4 (fr) * 2013-09-18 2017-07-26 China Mobile Communications Corporation Procédé de communications entre terminaux mobiles, dispositif et équipement apparenté
CN104581984A (zh) * 2013-10-28 2015-04-29 财团法人工业技术研究院 处理上行链路传送的方法及其通信装置
GB2519975A (en) * 2013-11-01 2015-05-13 Nec Corp Communication system
US10952116B2 (en) 2013-11-01 2021-03-16 Nec Corporation Communication system
CN104640232A (zh) * 2013-11-08 2015-05-20 财团法人工业技术研究院 处理无线链路失败的方法
EP2884688A1 (fr) * 2013-11-08 2015-06-17 Industrial Technology Research Institute Procédé de gestion de défaillance de liaison radio
US20150133122A1 (en) * 2013-11-08 2015-05-14 Industrial Technology Research Institute Method of Handling Radio Link Failure
US10334498B2 (en) * 2014-01-28 2019-06-25 Huawei Technologies Co., Ltd. Service transfer method and apparatus
US10321382B2 (en) 2014-03-03 2019-06-11 Telefonaktiebolaget Lm Ericsson (Publ) Mobility and/or access selection between cells
WO2015133954A1 (fr) 2014-03-03 2015-09-11 Telefonaktiebolaget L M Ericsson (Publ) Orientation de sélection de mobilité et/ou d'accès entre des cellules
WO2015143914A1 (fr) * 2014-03-28 2015-10-01 中国移动通信集团公司 Procédé, dispositif et système de commande de communication pour un terminal mobile
TWI556663B (zh) * 2014-12-25 2016-11-01 宏達國際電子股份有限公司 處理與多個基地台間通訊的失敗的方法及其裝置
US10237789B2 (en) 2014-12-25 2019-03-19 Htc Corporation Device and method of handling failure in communications with multiple base stations
EP3337227A4 (fr) * 2015-08-11 2018-07-18 KDDI Corporation Dispositif de station de base, dispositif de communication, procédé de commande et programme
EP3503668A4 (fr) * 2016-09-19 2019-09-25 Huawei Technologies Co., Ltd. Procédé et dispositif d'établissement de liaison et système de communication sans fil
CN108307524B (zh) * 2016-09-19 2021-11-19 华为技术有限公司 链路建立方法及设备与无线通信系统
US11368999B2 (en) * 2016-09-19 2022-06-21 Huawei Technologies Co., Ltd. Link setup method, device, and wireless communications system
CN108307524A (zh) * 2016-09-19 2018-07-20 华为技术有限公司 链路建立方法及设备与无线通信系统
CN108093447A (zh) * 2017-12-20 2018-05-29 中磊电子（苏州）有限公司 基站切换参数调整方法

Similar Documents

Publication Publication Date Title
US9883422B2 (en) Method and apparatus for enhanced connection control
WO2013091161A1 (fr) Procédé et appareil d'optimisation de robustesse de mobilité
US10187370B2 (en) Fast-accessing method and apparatus
EP3675579B1 (fr) Procédés de programmation de données, appareils et supports lisibles par ordinateur
US9723476B2 (en) Location registration for a device-to-device (D2D) user equipment
US11363528B2 (en) Method and apparatus for reducing signaling overhead and reducing battery of terminal
US10057937B2 (en) Communications via multiple access points
CN110892743A (zh) 具有0 ms用户平面中断的切换
WO2018127215A1 (fr) Procédé et appareil permettant de rapporter des informations de position d'un terminal, et procédé et appareil permettant d'effectuer une transmission de liaison descendante
JP7413553B2 (ja) 再確立方法および通信機器
WO2017024890A1 (fr) Procédé, appareil, et système de communication dispositif-à-dispositif
US11218929B2 (en) Information transmission method and apparatus and communication system
US20210007028A1 (en) Communications method and apparatus, system, and storage medium
WO2015143914A1 (fr) Procédé, dispositif et système de commande de communication pour un terminal mobile
WO2015161575A1 (fr) Procédé, station de base, entité de gestion mobile, et système de notification d'emplacement de terminal utilisateur
JP2023158130A (ja) サイドリンク伝送におけるユーザ装置能力の標識方法及び装置
JP2021510950A (ja) 媒体アクセス制御層の制御要素の確認方法、装置及び通信システム
JP2021502756A (ja) 通信装置のランダム・アクセス方法、装置、及び記憶媒体
US8705448B2 (en) Voice and data connection control in a mobile device
WO2022082690A1 (fr) Procédé, appareil et système de commutation de groupe
CN116349293A (zh) Iab节点的移植方法及装置
WO2024026898A1 (fr) Procédé et appareil de traitement d'informations et procédé et appareil d'émission/réception d'informations
WO2024031402A1 (fr) Procédé et appareil de relaxation de mesure, et système de communication
JP2024511813A (ja) 信号の送受信方法、装置及び通信システム
WO2015042883A1 (fr) Procédé de transmission de service de liaison montante, procédé de transmission de service de liaison descendante, et dispositif

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

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

Country of ref document: EP

Kind code of ref document: A1