WO2011160504A1 - 提高业务呼通率的实现方法及无线网络控制器 - Google Patents

提高业务呼通率的实现方法及无线网络控制器 Download PDF

Info

Publication number
WO2011160504A1
WO2011160504A1 PCT/CN2011/073983 CN2011073983W WO2011160504A1 WO 2011160504 A1 WO2011160504 A1 WO 2011160504A1 CN 2011073983 W CN2011073983 W CN 2011073983W WO 2011160504 A1 WO2011160504 A1 WO 2011160504A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
message
cell update
network controller
update message
Prior art date
Application number
PCT/CN2011/073983
Other languages
English (en)
French (fr)
Inventor
柯文
黄梅青
史莉荣
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP11797535.9A priority Critical patent/EP2587847B1/en
Priority to RU2013101518/07A priority patent/RU2572089C2/ru
Priority to US13/696,352 priority patent/US8805395B2/en
Publication of WO2011160504A1 publication Critical patent/WO2011160504A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present invention relates to the field of communications, and in particular, to an implementation method for improving a service call rate and a wireless network controller. Background technique
  • the call rate is an important indicator to measure network performance and directly affects the user's call experience. If the call rate is low and the user fails to dial once, the call request will be initiated again, which not only reduces the user experience, but also wastes network resources and easily causes network congestion. Therefore, how to improve the service call rate has become An important research topic.
  • FIG. 1 is a schematic diagram of a successful service establishment process in the prior art.
  • a UE User Equipment
  • an RRC (Radio Resource Control) connection is first sent.
  • the RNC Radio Network Controller
  • the RNC allocates radio resources to the UE, and sends an RRC connection setup message to the UE to guide the establishment of the signaling radio bearer.
  • the RRC connection is established. Complete the message to the RNC.
  • the UE After the RRC signaling connection establishment process is completed, the UE performs a NAS (Non-Access Stratum) signaling interaction with the CN (Core Network) through a direct transmission message, and the CN sends a service assignment message to the RNC, RNC.
  • the assignment message is received, the service bearer is allocated to the UE, and the radio bearer setup message is sent to the UE to guide the UE to establish a service radio bearer.
  • the radio bearer setup complete message is sent to the RNC.
  • the RNC After receiving the RNC, the RNC returns a service establishment completion message.
  • the call failure problem is particularly prominent due to the quality of the wireless environment.
  • the RNC sends a radio bearer setup message to the UE and waits for the UE to return a response.
  • 2 is a schematic diagram of a prior art air interface failure process, as shown in FIG. 2,
  • the failures caused by the air interface quality problem are as follows: 1.
  • the UE cannot correctly receive the RB (Radio Bearer) setup message on the network side (210); 2.
  • the UE receives the RB setup message and returns a response, but the network The side does not receive the response (220); 3.
  • the UE receives the RB setup message, and detects that the radio link fails during the reconfiguration process, causing the reconfiguration process to terminate (230).
  • the above situation ultimately leads to the failure of business establishment (240).
  • the UE detects that the radio link of the physical layer fails, or the RLC (Radio Link Control) layer is unrecoverable, and notifies the RRC layer to initiate a "radio link failure" or The "RLC is not recoverable” cause cell update message.
  • the RNC After receiving the message, the RNC performs the radio link re-establishment process, first deleting the radio link corresponding to the UE, switching to the public state, and then preparing the new link, and A cell update acknowledge message is sent on the downlink common transport channel, and the new configuration information is sent to the UE.
  • the process is referred to as call re-establishment in the present invention.
  • call reestablishment can solve the problem of poor air quality, there are two problems in the case of call failure:
  • the RNC can save the call by performing the call re-establishment procedure, but if the UE does not report the cell update in time, it will cause the call drop, which is greatly Reduce the business call rate.
  • the main object of the present invention is to provide an implementation method for improving the call rate of a service and a radio network controller, which can improve the network call rate.
  • the present invention provides a method for improving a service call rate, including: a radio network controller sends a radio bearer setup message to a user equipment; and the radio network controller determines whether it is at a first preset.
  • the radio bearer response message from the user equipment is not received in the time, and if yes, the radio network controller triggers the user equipment to report the cell update message; the radio network controller receives the cell update message from the user equipment, and carries the message according to the cell update message.
  • the information and/or the time when the cell update message is received determines the configuration state of the user equipment; the radio network controller performs call re-establishment processing according to the configuration state of the user equipment.
  • the present invention also provides an implementation method for improving a service call rate, including: the service radio network controller sends a radio bearer setup message to the user equipment; the service radio network controller determines whether the user is not received within the first preset time.
  • the radio bearer response message of the device if yes, the serving radio network controller triggers the user equipment to report the cell update message; the serving radio network controller sends the radio link deactivation message or the radio link delete message to the drift radio network controller;
  • the network controller receives the cell update message from the user equipment, and determines the configuration state of the user equipment according to the information carried in the cell update message and/or the time when the cell update message is received; the service radio network controller is configured according to the user equipment.
  • the status is used for call re-establishment processing.
  • the present invention provides a radio network controller, including: a sending module, configured to send a radio bearer setup message to a user equipment; a first determining module, configured to determine whether the radio from the user equipment is not received within the first preset time a triggering module, configured to: when the determining result of the first determining module is YES, triggering the user equipment to report a cell update message; the receiving module is configured to receive a cell update message from the user equipment; and the second determining module is configured to: Determining a configuration state of the user equipment according to the information carried in the cell update message and/or the time when the cell update message is received.
  • the reestablishing processing module is configured to perform call re-establishment processing according to the configuration state of the user equipment determined by the second judging module.
  • the present invention further provides a radio network controller, including: a first sending module, configured to send a radio bearer setup message to a user equipment;
  • a first determining module configured to determine whether a radio bearer response message from the user equipment is not received within the first preset time
  • a triggering module configured to trigger the user equipment to report a cell update message when the determining result of the first determining module is YES
  • a second sending module configured to send a radio link deactivation message or a radio link deletion message to the drift radio network controller
  • a receiving module configured to receive a cell update message from the user equipment
  • a second determining module configured to determine a configuration state of the user equipment according to information carried by the cell update message and/or a time when the cell update message is received;
  • a reconstruction processing module configured to perform call reconstruction processing according to the configuration state of the user equipment determined by the second determining module.
  • the RNC by inserting a call re-establishment in the service establishment process, the RNC triggers a cell update message on the UE to determine the configuration state of the UE, so that the RNC and the UE are in the call re-establishment process.
  • the configuration status is consistent, which improves the network call rate, further improves the utilization of network resources, and brings a good user experience.
  • FIG. 1 is a schematic diagram of a successful business establishment process in the prior art
  • FIG. 2 is a schematic diagram of a prior art air interface failure process
  • FIG. 3 is a flowchart of a method for implementing a service call rate improvement according to an embodiment of the present invention
  • FIG. 4 to FIG. 10 are schematic flowcharts of an embodiment of a method according to the present invention
  • FIG. 11 is a block diagram of a radio network controller in accordance with an embodiment of the present invention. detailed description
  • the basic idea of the present invention is: the radio network controller sends a radio bearer setup message to the user equipment; the radio network controller determines whether the radio bearer response message from the user equipment is not received within the first preset time, and if so, the radio network The controller triggers the user equipment to report a cell update message; the radio network controller receives the cell update message from the user equipment, and Determining a configuration state of the user equipment according to the information carried in the cell update message and/or the time when the cell update message is received; the radio network controller performs call re-establishment processing according to the configuration state of the user equipment.
  • FIG. 3 is a flowchart of a method for improving service call rate according to an embodiment of the present invention. As shown in FIG. 3, the method includes the following steps:
  • Step 302 The RNC sends a radio bearer (RB) setup message to the UE.
  • RB radio bearer
  • Step 304 The RNC determines whether it does not receive the radio bearer response message from the UE within the first preset time. If yes, the RNC triggers the UE to report the cell update message.
  • Step 306 The RNC receives the cell update message from the UE, and determines the configuration state of the user equipment according to the information carried in the cell update message and/or the time when the cell update message is received.
  • Step 308 The RNC performs a call according to the configuration state of the UE. Reconstruction processing.
  • the RNC triggers the UE to report the cell update message, but is not limited to the following two modes: the RL deactivation mode and the RL deletion mode.
  • the RL deactivation mode means that the RNC sends the RL to the NodeB (base station) to which the UE belongs. Activating the message, causing the radio link to stop downlink transmission, causing the UE to lose synchronization on the downlink.
  • the UE After satisfying the radio link failure reporting condition, the UE sends a cell update message of the radio link failure reason to the RNC, so that the RNC performs a radio link re-establishment process;
  • the RL deletion mode means that the RNC sends an RL deletion message to the NodeB to which the UE belongs.
  • the radio link re-establishment process by reporting the cell update message of the radio link failure reason to the RNC.
  • the RL deactivation mode the uplink is still maintained, and the RL deletion mode is relatively complete.
  • the purpose of the two methods is to enable the UE to report the cell update message to reestablish the radio link.
  • the timer T2 second preset time
  • T313 is the radio link failure reporting timer initiated after N313 consecutive out-of-synchronization.
  • the RNC directly returns a service assignment failure to the CN. In the specific embodiment of the present invention, only the case where the RNC receives the cell update message before the T2 timeout is considered.
  • the call re-establishment process first deletes the link and then establishes a new link; In the mode, the call re-establishment process only has a new link process.
  • step 304 the reason why the RNC does not receive the radio bearer response message from the user equipment in the first preset time is divided into: (1) the air interface message (radio bearer setup message) fails to be delivered according to the time point of the air interface failure; (2) Failure in the processing of the air interface message; (3) Failure to return the air interface response message.
  • These scenarios can cover the air interface failure caused by all air interface quality. The scenario is differentiated in order for the RNC to accurately determine the state of the UE and keep the configuration synchronized with the UE.
  • the RNC sets the timer, that is, waits for the air interface response message within the first preset time. If the air interface response message is received within the first preset time, the timer is deleted. Otherwise, the timer expires and the RNC considers the air interface abnormal. No longer waiting for air interface messages.
  • the setting of the first preset time (timer T1) needs to consider the time required for the air interface response and the IU port timer time.
  • the RNC waits for the air interface response time to be shortened.
  • the setting of the second preset time (timer T2) can be determined according to the criteria that the wireless link failure meets.
  • the first preset time cannot be set too short. If the setting is too short, the UE side will not be reconfigured, and the network side will time out in advance. Therefore, the network side air interface timer duration is usually greater than the air interface response requirement.
  • Time TUE Specifically, setting the first preset time requires a comprehensive test. Consider the length of the message, the transmission of the air interface, and the processing of the UE. Therefore T1>TUE.
  • the call re-establishment is inserted in the service establishment process, so the time required for the call re-establishment needs to be considered when setting the first preset time, and the IU port (interface between the RNC and the CN) is avoided.
  • T that is, the time from the RNC receiving the service assignment request from the CN to returning the service establishment completion to the CN
  • the IU port times out, the call cannot be recovered.
  • the time of call re-establishment includes the duration T2 (i.e., the second preset time) at which the UE detects the failure of the radio link and the length of time required for the call re-establishment process. Therefore T1 ⁇ T-T2.
  • the duration of the timer T1 should not be greater than the duration of the failure of the radio link detected on the new configuration after the new configuration takes effect, that is, T1 ⁇ TUE + T2.
  • the T1 timer does not time out
  • the RNC receives the cell update of the RL failure reason
  • the sum of the durations of failures to the radio link is greater than the duration T1 of the RNC waiting for an air interface response. If the RNC receives the cell update of the RL failure cause before the T1 timeout, the UE is considered to be still in the old configuration (ie, the first configuration state).
  • the RNC may process whether the RLC RLC layer receives the ACK of the opposite end according to whether the RNC receives the RB setup message: if received, the UE is considered to receive the RB setup message; otherwise, the UE does not receive the RB setup message; There are two cases: (1) The UE does not receive the RB setup message; (2) The UE receives the RB setup message and returns an ACK, but the RNC does not receive the ACK.
  • the CELL UPDATE message includes a Reconfiguration Status Indicator (UE) message, which indicates that the UE receives the RB establishment/RB reconfiguration/RB release and other messages.
  • UE Reconfiguration Status Indicator
  • the UE is in the reconfiguration process, or has returned an RB response message, waiting for the RLC ACK of the message. If the Reconfiguration Status Indicator cell is not carried in the CELL UPDATE sent by the UE, the UE is considered not to receive the RB setup message.
  • the manner of distinguishing the foregoing three scenarios according to the embodiment of the present invention includes: if the Reconfiguration Status Indicator cell is not carried in the cell update message, the UE may not be considered as the cell update message received before or after the timeout.
  • the RB setup message is received, and is still in the first configuration state (that is, the old configuration). If the cell update message received in the timer T1 (that is, the first preset time) expires, the UE can be considered as returning.
  • the RB response message has been switched to the second configuration state (ie, the new configuration); if the cell is received in the cell update message received before the air interface timer (ie, the first preset time) expires, the UE is considered to be positive. In the reconfiguration process, it is still in the old configuration.
  • the RNC In the case that it is determined that the UE has switched to the new configuration, the RNC also needs to switch to the new configuration, because the new configuration is already valid on the UE side when the UE returns a successful RB setup response message, so the RNC presses the received air interface. The response is processed, and the call is re-established on the new configuration. Because the RNC does not correctly receive the air interface RB setup complete message, the encrypted information in the response message cannot be obtained, and the UE does not receive the ACK of the opposite RLC layer (Acknowledgement). The acknowledgement frame does not take effect on the encrypted information. Therefore, the encrypted information on the network side and the UE side does not cause inconsistency due to the loss of the air interface response message.
  • the RNC performs the following processing:
  • the UE does not receive the RB setup message of the RNC, the UE is still in the old configuration, and the RNC performs call reestablishment on the old configuration, and then re-establishes the service RB after the call is successfully reestablished.
  • the UE receives the RB setup message and returns a successful response, but the RNC does not receive the response.
  • the RNC reclaims the call by inserting a call re-establishment procedure on the new configuration.
  • the UE When the UE receives the RB setup message, but the radio link fails or the RLC does not recover during the reconfiguration process, the UE stops the reconfiguration process, maintains the old configuration, and reports the reason that the radio link fails.
  • the cell update message at this time, the RNC performs call re-establishment on the old configuration, and re-establishes the service RB after the call is successfully re-established.
  • Figure 4 is a schematic diagram of a process of receiving a UE cell update message after the RNC and other RBs establish a response timeout, and after the RL is deactivated (including the SRNC RL), as shown in Figure 4, the process includes:
  • Step 401 The RNC receives the service assignment message sent by the CN.
  • Step 402 The RNC sends a radio link reconfiguration request message to the NodeB.
  • Step 403 The RNC receives the radio link reconfiguration response message returned by the NodeB.
  • Step 405 The RNC sets an air interface timer T1 (first preset time);
  • Step 406 The RNC determines that the T1 timer expires, that is, no response is received during the T1 process.
  • Step 407 The RNC sends a radio link deactivation command message to the NodeB to deactivate the radio link to which the UE belongs.
  • Step 408 The RNC sets a timer T2 (second preset time), and waits for a cell update message of the UE;
  • Step 409 The RNC receives a cell update message from the UE before the timeout of the timer T2, where the cell update message carries the current reconfiguration status indication of the UE.
  • Step 410 The RNC sends a radio link deletion request message to the NodeB.
  • Step 411 The RNC receives the radio link deletion response message returned by the NodeB.
  • Step 412 The RNC sends a radio link setup request message to the NodeB.
  • Step 413 The RNC receives the radio link setup response message returned by the NodeB.
  • Step 414 The RNC sends a cell update confirmation message to the UE.
  • Step 415 The RNC receives the reconfiguration complete message returned by the UE.
  • Step 416 The RNC sends a service assignment response message to the CN.
  • Figure 5 shows the timeout response of the RNC and other RBs in the service establishment process. After the RL is deactivated.
  • FIG. 5 shows the addition of the radio interface deactivation message across the IUR interface (logical interface between two RNCs, the interface between the serving RNC (SRNC) and the drift RNC (DRNC)).
  • the active set includes the DRNC radio link
  • the radio link is required to be used to deactivate the message to the DRNC through the IUR port.
  • the process specifically includes:
  • Step 501 The SRNC receives the service assignment message sent by the CN.
  • Step 502 The SRNC sends a radio link reconfiguration request message to the NodeB.
  • Step 503 The SRNC sends a radio link reconfiguration request message to the DRNC.
  • Step 504 The DRNC sends a radio link reconfiguration request message to the NodeB (DRNC).
  • Step 505 The SRNC receives the radio link reconfiguration response message returned by the NodeB.
  • Step 506 The DRNC receives the radio link returned by the NodeB (DRNC). Reconfigure response message;
  • Step 507 The SRNC receives the radio link reconfiguration response message returned by the DRNC.
  • Step 509 The SRNC sets the air interface timer T1 (the first preset time);
  • Step 510 The SRNC determines that the T1 timer expires, that is, the response message from the UE is not received during the T1 process;
  • Step 511 The SRNC sends a radio link deactivation command message to the NodeB to deactivate the radio link to which the UE belongs.
  • Step 512 The SRNC sends a radio link deactivation command message to the DRNC.
  • Step 513 The DRNC sends a radio link deactivation command message to the NodeB (DRNC).
  • Step 515 The SRNC receives a cell update message from the UE before the timeout of the timer T2, where the cell update message carries the current reconfiguration status indication of the UE.
  • Step 516 The SRNC sends a radio link deletion request message to the NodeB.
  • Step 517 The SRNC sends a radio link deletion request message to the DRNC.
  • Step 518 The DRNC sends a radio link deletion request message to the NodeB (DRNC).
  • Step 520 The SRNC receives the radio link setup response message returned by the NodeB.
  • Step 522 The SRNC receives the reconfiguration complete message returned by the UE.
  • Step 523 The SRNC sends a service assignment response message to the CN.
  • Figure 6 is a schematic diagram of a process of receiving a UE cell update message after the RNC and other RBs establish a response timeout in the service establishment process, and after deleting the RL (including only the SRNC RL), as shown in Figure 6, the process specifically includes:
  • Step 601 The RNC receives the service assignment message sent by the CN.
  • Step 602 The RNC sends a radio link reconfiguration message to the NodeB.
  • Step 603 The RNC receives the radio link reconfiguration response message returned by the NodeB.
  • Step 604 The RNC sends a radio bearer setup message to the UE.
  • Step 605 The RNC sets a waiting air interface timer T1;
  • Step 606 The RNC determines that the T1 timer expires, that is, the response message of the UE is not received during the T1 process;
  • Step 607 The RNC sends a radio link deletion request message to the NodeB.
  • Step 608 The RNC receives the radio link deletion response message returned by the NodeB.
  • Step 609 The RNC sets a timer T2, and waits for a cell update message of the UE.
  • Step 610 The RNC receives the cell update message of the UE before the timer T2 times out.
  • Step 611 The RNC sends a radio link setup request message to the NodeB.
  • Step 612 The RNC receives the radio link setup response message returned by the NodeB.
  • Step 613 The RNC sends a cell update confirmation message to the UE.
  • Step 614 The RNC receives the reconfiguration complete message returned by the UE.
  • Step 615 The RNC sends a service assignment response message to the CN.
  • Figure 7 is a schematic diagram of the flow of the RNC and other air interface RB establishment response timeouts after the service establishment process, after deleting 1 1 ⁇ (including DRNC RL), and waiting for the UE cell update.
  • Figure 7 is similar to Figure 6. The difference is that after the T1 times out, the DRNC radio link is deleted. The SRNC sends the radio link to the DRNC through the IUR interface. As shown in Figure 7, the process includes:
  • Step 701 The SRNC receives the service assignment message sent by the CN.
  • Step 702 The SRNC sends a radio link reconfiguration request message to the NodeB.
  • Step 703 The SRNC sends a radio link reconfiguration request message to the DRNC.
  • Step 704 The DRNC sends a radio link reconfiguration request message to the NodeB (DRNC).
  • Step 705 The SRNC receives the radio link reconfiguration response message returned by the NodeB.
  • Step 706 The DRNC receives the radio link returned by the NodeB (DRNC).
  • Reconfiguration response cancellation step 707 The SRNC receives the radio link reconfiguration response message returned by the DRNC;
  • Step 708 The SRNC sends a radio bearer setup message to the UE;
  • Step 709 The SRNC sets an air interface timer T1 (first preset time);
  • Step 710 The SRNC determines that the T1 timer expires, that is, the response message from the UE is not received during the T1 process;
  • Step 711 The SRNC sends a radio link deletion request message to the NodeB.
  • Step 712 The SRNC sends a radio link deletion request message to the DRNC.
  • Step 713 The DRNC sends a radio link deletion request message to the NodeB (DRNC).
  • Step 715 The SRNC receives a cell update message from the UE before the timeout of the timer T2, where the cell update message carries the current reconfiguration status indication of the UE.
  • Step 716 The SRNC sends a radio link setup request message to the NodeB.
  • Step 717 The SRNC receives the radio link setup response message returned by the NodeB.
  • Step 719 The SRNC receives the reconfiguration complete message returned by the UE.
  • Step 720 The SRNC sends a service assignment response message to the CN.
  • FIG. 8 is a schematic diagram of a process in which the UE does not receive an RB setup message and the RNC deactivates the wireless link to trigger call reestablishment during the service establishment process. As shown in FIG. 8, the process specifically includes:
  • Step 801 The RNC receives the service assignment message sent by the CN.
  • Step 802 The RNC sends a radio link reconfiguration request message to the NodeB.
  • Step 803 The RNC receives the radio link reconfiguration response message returned by the NodeB.
  • Step 804 The RNC sends a radio bearer setup message to the UE, where the radio bearer setup message indicates that the message is not sent to the UE by using a dotted line.
  • Step 805 The RNC sets a waiting air interface timer T1;
  • Step 806 The RNC determines that the T1 timer expires, that is, the UE does not receive the response message during the T1 process.
  • Step 807 The RNC sends a radio link deactivation command message to the NodeB to deactivate the radio link to which the UE belongs.
  • Step 808 The RNC sets a timer T2, and waits for a cell update message of the UE.
  • Step 809 The RNC receives the cell update message reported by the UE before the timer T2 times out, and the message does not carry the reconfiguration indication cell, indicating that the UE does not perform reconfiguration processing.
  • Step 810 The RNC sends a radio link deletion request message to the NodeB.
  • Step 811 The RNC receives the radio link deletion response message returned by the NodeB.
  • Step 812 The RNC sends a radio link setup request message to the NodeB.
  • Step 813 The RNC receives the radio link setup response message returned by the NodeB.
  • Step 814 The RNC sends a cell update confirmation message to the UE.
  • Step 815 The RNC receives the reconfiguration complete message returned by the UE.
  • Step 816 After the call reestablishment is completed, the RNC sends a radio bearer setup message to the UE.
  • Step 817 The RNC receives the RB setup response message returned by the UE.
  • Step 818 The RNC sends a service assignment response message to the CN.
  • FIG. 9 is a schematic diagram of a process in which a UE does not receive an RB setup message and a RNC deletes a radio link to trigger a call reestablishment in a service establishment process, and FIG. 9 is similar to FIG. 8 .
  • the UE performs the establishment of the service radio bearer, as shown in FIG. 9, the process specifically includes:
  • Step 901 The RNC receives the service assignment message sent by the CN.
  • Step 902 The RNC sends a radio link reconfiguration message to the NodeB.
  • Step 903 The RNC receives the radio link reconfiguration response message returned by the NodeB.
  • Step 904 The RNC sends a radio bearer setup message to the UE, where the radio bearer setup message indicates that the message is not sent to the UE by using a dotted line.
  • Step 905 The RNC sets a waiting air interface timer T1;
  • Step 906 The RNC determines that the T1 timer expires, that is, the UE does not receive the response message during the T1 process;
  • Step 907 The RNC sends a radio link deletion request message to the NodeB.
  • Step 908 The RNC receives the radio link deletion response message returned by the NodeB.
  • Step 909 The RNC sets a timer T2, and waits for the cell update message of the UE.
  • Step 910 The RNC receives the cell update message reported by the UE before the timer T2 times out.
  • the message does not carry the reconfiguration indicator cell, indicating that the UE does not perform reconfiguration processing;
  • the RNC sends a radio link setup request message to the NodeB;
  • the RNC receives the radio link setup response message returned by the NodeB;
  • the RNC sends a cell update confirmation message to the UE
  • the RNC receives the reconfiguration complete message returned by the UE
  • Step 915 After the call reestablishment is completed, the RNC sends a radio bearer setup message to the UE.
  • Step 916 The RNC receives the RB setup response message returned by the UE.
  • Step 917 The RNC sends a service assignment response message to the CN.
  • FIG 10 is a schematic diagram of a process in which the RNC receives a cell update before the air interface response times out during the service establishment process. As shown in Figure 10, the process specifically includes:
  • Step 1001 The RNC receives the service assignment message sent by the CN.
  • Step 1002 The RNC sends a radio link reconfiguration message to the NodeB.
  • Step 1003 The RNC receives the radio link reconfiguration response message returned by the NodeB.
  • Step 1004 The RNC sends a radio bearer setup message to the UE.
  • Step 1005 The RNC sets a waiting air interface timer T1;
  • Step 1006 The RNC receives the cell update of the UE before the T1 timer expires.
  • Step 1007 The RNC deletes the timer T1.
  • Step 1008 The RNC sends a radio link deletion request message to the NodeB.
  • Step 1009 The RNC receives the radio link deletion response message returned by the NodeB.
  • Step 1010 The RNC sends a radio link setup request message to the NodeB.
  • Step 1011 The RNC receives the radio link setup response message returned by the NodeB.
  • Step 1012 The RNC sends a cell update confirmation message to the UE.
  • Step 1013 The RNC receives the reconfiguration complete message returned by the UE.
  • Step 1014 After the call reestablishment is completed, the RNC sends an RB setup message to the UE to perform establishment of the service radio bearer.
  • Step 1015 The RNC receives the RB setup response message returned by the UE.
  • Step 1016 The RNC sends a service assignment response message to the CN.
  • FIG. 4 to FIG. 7 show a specific embodiment of the air interface response timeout such as RNC, wherein FIG. 4 and FIG. 5 use the wireless link deactivation mode to trigger call re-establishment, FIG. 6 and FIG.
  • the call re-establishment is triggered by the radio link deletion mode
  • FIGS. 4 and 6 are processes including only the S-side link
  • FIGS. 5 and 7 are process diagrams including the D-side link
  • FIG. 8 and FIG. 9 show that the UE does not receive the RB.
  • FIG. 8 ⁇ triggers call reestablishment by means of wireless link deactivation
  • FIG. 9 triggers call reestablishment by means of radio link deletion.
  • Figure 10 shows a specific embodiment of the RNC receiving a cell update before the air interface response times out.
  • FIG. 11 is a block diagram of a radio network controller according to an embodiment of the present invention.
  • the radio network controller includes:
  • the sending module 10 is configured to send a radio bearer setup message to the user equipment, where the first determining module 20 is configured to determine whether the radio bearer response message from the user equipment is not received within the first preset time; the triggering module 30 is configured to: When the judgment result of the first judging module is yes, the user equipment is triggered to report the cell update message; the receiving module 40 is configured to receive the cell update message from the user equipment; and the second determining module 50 is configured to use the cell update message according to the cell update message. The information of the user equipment and/or the time when the cell update message is received is used to determine the configuration state of the user equipment.
  • the reconstruction processing module 60 is configured to perform call reconstruction processing according to the configuration state of the user equipment determined by the second determining module.
  • the triggering module 30 triggers the user equipment to report the cell update message by sending a radio link deactivation message or a radio link deletion message to the base station to which the user equipment belongs.
  • the second determining module 50 further includes: a first determining submodule, configured to: when the cell update message does not carry the reconfiguration information of the user equipment, determine that the user equipment is in the first configuration state; When the cell update message is received in the first preset time, and the cell update message carries the reconfiguration information of the user equipment, the user equipment is determined to be in the first configuration state; The third determining sub-module is configured to determine that the user equipment is in the second configuration state when the cell update message is received in the first preset time and the cell update message carries the reconfiguration information of the user equipment.
  • the present invention further provides a radio network controller, where the radio network controller includes: a first sending module, configured to send a radio bearer setup message to the user equipment;
  • a first determining module configured to determine whether a radio bearer response message from the user equipment is not received within the first preset time
  • a triggering module configured to trigger the user equipment to report a cell update message when the determining result of the first determining module is YES;
  • a second sending module configured to send a radio link deactivation message or a radio link deletion message to the drift radio network controller
  • a receiving module configured to receive a cell update message from the user equipment
  • a second determining module configured to determine a configuration state of the user equipment according to information carried by the cell update message and/or a time when the cell update message is received;
  • a reconstruction processing module configured to perform call reconstruction processing according to the configuration state of the user equipment determined by the second determining module.
  • the working process of the radio network controller according to the embodiment of the present invention may refer to FIG. 2 to FIG. 10, and details are not described herein.
  • the call drop caused by the failure of the air interface can be effectively recovered, and the network call rate is improved.
  • the RNC by inserting a call re-establishment in the service establishment process, the RNC triggers the UE to report the report.
  • the cell update message is used to determine the configuration state of the UE, so that the configuration state of the RNC and the UE are consistent in the call reestablishment process, thereby improving the network call rate.

Landscapes

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

Description

提高业务呼通率的实现方法及无线网络控制器 技术领域
本发明涉及通讯领域， 尤其涉及一种提高业务呼通率的实现方法及无 线网络控制器。 背景技术
呼通率是衡量网络性能的重要指标， 并直接影响用户的呼叫感受。 如 果呼通率低， 用户一次拨号不成功， 会再次发起呼叫请求， 不仅降低了用 户体验， 也会对网络资源造成浪费， 同时容易引发网络拥塞等问题， 因此， 如何提高业务呼通率已成为一项重要的研究课题。
图 1是现有技术的业务建立成功流程示意图， 如图 1所示， 根据 3GPP 技术规范， UE ( User Equipment, 用户终端）发起一次呼叫时， 首先发送 RRC ( Radio Resource Control, 无线资源控制）连接请求给 RNC ( Radio Network Controller, 无线网络控制器）， RNC为该 UE分配无线资源， 并发 送 RRC连接建立消息给 UE引导其建立信令无线承载， UE完成 RRC无线 资源配置后， 发送 RRC连接建立完成消息给 RNC。 RRC信令连接建立过 程完成后， UE通过直传消息跟 CN ( Core Network,核心网）进行 NAS ( Non Access Stratum, 非接入层）信令交互， 由 CN下发业务指派消息给 RNC, RNC收到该指派消息， 为 UE分配业务承载， 并发送无线承载建立消息给 UE引导其建立业务无线承载， UE配置完成后发送无线承载建立完成消息 给 RNC。 RNC收到后给 CN返回业务建立完成消息。
引起呼叫失败的原因有很多种， 其中由于无线环境质量导致的呼叫失 败问题尤为突出， 在呼叫建立流程中， RNC给 UE发送无线承载建立消息， 并等待 UE返回响应。图 2是现有技术的空口失败流程示意图，如图 2所示， 由于空口质量问题引发的失败有以下几种： 一、 UE无法正确收到网络侧的 RB ( Radio Bearer, 无线 载）建立消息 （210 ); 二、 UE收到 RB建立消 息并返回响应 , 但网络侧没有收到响应（ 220 ); 三、 UE收到 RB建立消息 , 在重配过程中检测到无线链路失败， 导致重配流程终止（230 )。 上述情况 最终都导致业务建立失败（240 )。
当空口质量变差时， UE会检测到物理层的无线链路失败， 或 RLC ( Radio Link Control, 无线链路控制）层的不可恢复错， 并通知 RRC层， 发起 "无线链路失败" 或 "RLC不可恢复" 原因的小区更新消息， RNC接 收到该消息后，执行无线链路的重建流程，首先删除该 UE对应的无线链路， 切换到公用态， 然后准备好新建链路， 并在下行公共传输信道上发送小区 更新确认消息， 将新配置信息发送给 UE。 为描述简便， 该过程在本发明中 称之为呼叫重建。
虽然呼叫重建可以解决空口质量变差的问题， 但对于呼叫失败的情况， 还存在两个问题：
( 1 )呼叫重建虽然可以通过无线链路的重建挽回呼叫， 但必须保证网 络侧和 UE侧配置保持同步， 由于空口质量问题的复杂性， 使得 RNC无法 准确判断 UE当前的状态。
( 2 )如果业务建立过程中， 空口质量变差并且 116上>¾了小区更新， 则 RNC可以通过执行呼叫重建流程来挽回呼叫， 但是如果 UE没有及时上 报小区更新， 则会导致掉话， 大大降低业务呼通率。 发明内容
有鉴于此， 本发明的主要目的在于提供一种提高业务呼通率的实现方 法及无线网络控制器， 能够提高网络呼通率。
本发明提供一种提高业务呼通率的实现方法， 包括： 无线网络控制器 向用户设备发送无线承载建立消息； 无线网络控制器判断是否在第一预设 时间内未接收到来自用户设备的无线承载响应消息， 若是， 则无线网络控 制器触发用户设备上报小区更新消息； 无线网络控制器接收到来自用户设 备的小区更新消息， 并根据小区更新消息所携带的信息和 /或接收到小区更 新消息的时间判断用户设备的配置状态； 无线网络控制器根据用户设备的 配置状态进行呼叫重建处理。
本发明还提供一种提高业务呼通率的实现方法， 包括： 服务无线网络 控制器向用户设备发送无线承载建立消息； 服务无线网络控制器判断是否 在第一预设时间内未接收到来自用户设备的无线承载响应消息， 若是， 则 服务无线网络控制器触发用户设备上报小区更新消息； 服务无线网络控制 器向漂移无线网络控制器发送无线链路去激活消息或无线链路删除消息； 服务无线网络控制器接收到来自用户设备的小区更新消息， 并根据小区更 新消息所携带的信息和 /或接收到小区更新消息的时间， 判断用户设备的配 置状态； 服务无线网络控制器根据用户设备的配置状态进行呼叫重建处理。
本发明提供一种无线网络控制器， 包括： 发送模块， 用于向用户设备 发送无线承载建立消息； 第一判断模块， 用于判断是否在第一预设时间内 未接收到来自用户设备的无线承载响应消息； 触发模块， 用于在第一判断 模块的判断结果为是时， 触发用户设备上报小区更新消息； 接收模块， 用 于接收来自用户设备的小区更新消息； 第二判断模块， 用于根据小区更新 消息所携带的信息和 /或接收到小区更新消息的时间， 判断用户设备的配置 状态； 重建处理模块， 用于根据第二判断模块判断的用户设备的配置状态 进行呼叫重建处理。
本发明还提供一种无线网络控制器， 包括： 第一发送模块， 用于向用 户设备发送无线承载建立消息；
第一判断模块， 用于判断是否在第一预设时间内未接收到来自用户设 备的无线承载响应消息； 触发模块， 用于在所述第一判断模块的判断结果为是时， 触发所述用 户设备上报小区更新消息；
第二发送模块， 用于向漂移无线网络控制器发送无线链路去激活消息 或无线链路删除消息；
接收模块， 用于接收来自所述用户设备的小区更新消息；
第二判断模块， 用于根据所述小区更新消息所携带的信息和 /或接收到 所述小区更新消息的时间， 判断所述用户设备的配置状态；
重建处理模块， 用于根据所述第二判断模块判断的所述用户设备的配 置状态进行呼叫重建处理。
与现有技术相比， 根据本发明的技术方案， 通过在业务建立过程中插 入呼叫重建， RNC触发 UE上 "^的小区更新消息来判断 UE的配置状态， 使得在呼叫重建处理中 RNC和 UE的配置状态一致， 从而提高了网络呼通 率， 进一步提高网络资源利用率， 给用户带来良好的使用体验。 附图说明
图 1是现有技术的业务建立成功流程示意图；
图 2是现有技术的空口失败流程示意图；
图 3是根据本发明实施例的提高业务呼通率的实现方法的流程图； 图 4至图 10是根据本发明方法实施例流程示意图；
图 11是根据本发明的实施例的无线网络控制器的框图。 具体实施方式
本发明的基本思想是：无线网络控制器向用户设备发送无线承载建立 消息； 无线网络控制器判断是否在第一预设时间内未接收到来自用户设 备的无线承载响应消息， 若是， 则无线网络控制器触发用户设备上报小 区更新消息； 无线网络控制器接收到来自用户设备的小区更新消息， 并 根据小区更新消息所携带的信息和 /或接收到小区更新消息的时间判断 用户设备的配置状态； 无线网络控制器根据用户设备的配置状态进行呼 叫重建处理。
下面通过附图及具体实施例对本发明再做进一步的详细说明。
本发明提供一种提高业务呼通率的实现方法， 图 3是根据本发明实施 例的提高业务呼通率的实现方法的流程图， 如图 3 所示， 该方法包括以下 步骤：
步骤 302, RNC向 UE发送无线承载（RB )建立消息；
步骤 304, RNC判断其是否在第一预设时间内未接收到来自 UE的无线 承载响应消息， 若是， 则 RNC触发 UE上报小区更新消息；
步骤 306, RNC接收到来自 UE的小区更新消息，并根据小区更新消息 所携带的信息和 /或接收到小区更新消息的时间判断用户设备的配置状态； 步骤 308, RNC根据 UE的配置状态进行呼叫重建处理。
在步骤 304中， RNC触发 UE上报小区更新消息包括但不限于以下两 种方式： RL去激活方式以及 RL删除方式； 其中， RL去激活方式是指 RNC 向 UE所属的 NodeB (基站 )发送 RL去激活消息， 使得无线链路停止下行 发射， 导致 UE下行失步， UE在满足无线链路失败上报条件后， 发送无线 链路失败原因的小区更新消息给 RNC, 从而 RNC进行无线链路重建过程； RL删除方式是指 RNC向 UE所属的 NodeB发送 RL删除消息， 同样是为 了让 UE下行失步， 上报无线链路失败原因的小区更新消息给 RNC, 从而 进行无线链路重建过程； 比较这两种方式， 在 RL去激活方式下， 上行链路 仍然保持， RL删除方式比较彻底， 但这两种方式的目的都是为了让 UE上 报小区更新消息进行无线链路的重建。 RNC发送 RL去激活消息或 RL删除 消息后， 需要设置定时器 T2 (第二预设时间 )等待 UE上报小区更新消息， 设置该定时器时长请参考 T313和 N313的取值， 其中， N313是物理层连续 失步的次数， T313是 N313次连续失步后启动的无线链路失败上报定时器。 如果在该定时器超时前未收到 UE上报的小区更新消息， 则认为是异常情 况， 不在本发明的讨论范围内。 若该异常情况发生， 则 RNC直接给 CN返 回业务指派失败。 在本发明具体实施例中仅考虑 RNC在 T2超时前收到小 区更新消息的情况。
在具体实施时， 釆用 RL去激活方式和釆用 RL删除方式触发呼叫重建 是有区别的， 在 RL去激活方式下， 呼叫重建过程是先删除链路， 再建立新 链路； 在 RL删除方式下， 呼叫重建过程只有新建链路过程。
步骤 304中， RNC在第一预设时间内未接收到来自用户设备的无线承 载响应消息的原因， 根据空口失败的时间点划分为： （1 ) 空口消息 （无线 承载建立消息） 下发失败； （2 ) 空口消息处理过程中失败； （3 )返回空口 响应消息失败三种情况， 这些场景能涵盖所有空口质量导致的空口失败。 区分场景是为了使 RNC准确判断 UE的状态， 并和 UE保持配置的同步。
下面具体说明区分上述三种情形的方法。
首先， 可以从 RNC等待空口响应定时器是否超时加以区分。 一般情况 下， RNC设置定时器， 即在第一预设时间内等待空口响应消息， 如果在第 一预设时间内接收到空口响应消息， 则删除定时器， 否则定时器超时， RNC 认为空口异常不再等待空口消息。
需要说明， 第一预设时间 （定时器 T1 ) 的设定需要考虑空口响应需要 的时间以及 IU口定时器时间。 在保证空口配置时间满足的情况下， 可以适 当缩短 RNC等待空口响应时间。 第二预设时间 （定时器 T2 ) 的设定， 可 依据无线链路失败满足的标准来确定。
具体来说， 首先， 第一预设时间不能设置过短， 如果设置过短， 将致 使 UE侧还没重配完成， 网络侧提前超时，所以网络侧的空口定时器时长通 常大于空口响应需要的时间 TUE。 具体地， 设置第一预设时间需要综合考 虑消息长度、 空口传输、 UE处理等因素。 因此 T1>TUE。
其次， 根据本发明实施例， 在业务建立过程中插入呼叫重建， 所以在 设置第一预设时间时还需要考虑呼叫重建所需要的时间， 避免 IU口 （RNC 与 CN之间的接口）定时器 T (即从 RNC接收到来自 CN的业务指派请求 到向 CN返回业务建立完成的时间）提前超时，否则会出现即使呼叫重建成 功， 但 IU口超时的情况， 仍然达不到挽回呼叫的目的。 呼叫重建的时间包 括 UE检测到无线链路失败的时长 T2 (即第二预设时间 )和呼叫重建流程 所需的时长。 因此 T1<T-T2。
根据无线链路失败上报准则， UE侧检测到无线链路失败的时间 （即第 二预设时间 )可以通过 T313和 N313计算得到， 即检测到无线链路失败的 时间 Τ2 (第二预设时间 ) =T313+N313*10ms+160ms+Toff, 其中 N313是物 理层连续失步的次数， T313是 N313次连续失步后启动的无线链路失败上 报定时器， Toff为系统偏移量， 160ms是同步检测的固定延迟。
另外， 定时器 T1的时长不应当大于新配置生效后， 在新配置上检测到 无线链路失败的时长， 即 T1<TUE+T2。
所以在 T1定时器未超时的情况下， 如果 RNC接收到 RL失败原因的 小区更新， 则认为 UE没有切换到新配置 （即第二配置状态）， 因为切换到 新配置的时长和新配置上检测到无线链路失败的时长之和大于 RNC等待空 口响应的时长 T1。如果在 T1超时前 RNC接收到 RL失败原因的小区更新 , 则认为 UE仍处于旧配置 （即第一配置状态）。
RNC在等待空口响应定时器 T1超时后， 可以根据 RNC发送 RB建立 消息后， RNC的 RLC层是否接收到对端的 ACK来处理： 如果接收到， 则 认为 UE接收到 RB建立消息； 否则， 没有收到存在两种情况： （1 ) UE没 有收到 RB建立消息； （ 2 ) UE收到 RB建立消息并返回 ACK, 但 RNC没 有收到 ACK。 值得注意的是， 对于 R6及以上版本， 在 CELL UPDATE (小区更新） 消息中包含有重配状态指示 （Reconfiguration Status Indicator )信元， 其表 征 UE收到 RB建立 /RB重配 /RB释放等消息， 正处于重配流程中， 或已返 回 RB响应消息， 正在等待该消息的 RLC ACK。 如果 UE发送的 CELL UPDATE中没有携带 Reconfiguration Status Indicator信元， 则认为 UE没有 收到 RB建立消息。
因此， 根据本发明实施例的区分上述三种情形的方式包括： 如果在小 区更新消息中没有携带 Reconfiguration Status Indicator信元， 无论是超时前 还是超时后收到的小区更新消息， 都可以认为 UE没有收到 RB建立消息， 仍处于第一配置状态 (即旧配置）； 如果在定时器 T1 (即第一预设时间）超 时后收到的小区更新消息中携带了此信元，可以认为 UE返回了 RB响应消 息， 已经切换到第二配置状态（即新配置）； 如果在空口定时器（即第一预 设时间）超时前收到的小区更新消息中携带了此信元，则认为 UE正处于重 配流程中， 仍处于旧配置。
在判断出 UE已经切换到新配置的情况下， RNC也需要切换到新配置 上，因为 UE在返回成功的 RB建立响应消息时，新配置已经在 UE侧生效， 所以此时 RNC按收到空口响应进行处理， 并在新配置上进行呼叫重建； 又 因为 RNC没有正确收到空口 RB建立完成消息， 所以无法获取响应消息中 的加密信息， 而 UE因为没有收到对端 RLC层的 ACK ( Acknowledgement, 确认帧 ), 也不会生效加密信息， 所以网络侧和 UE侧的加密信息不会因为 空口响应消息的丟失而产生不一致。
根据上述的空口失败的三种情形， RNC分别进行如下处理：
( 1 )在 UE没有收到 RNC的 RB建立消息的情况下 , UE仍处于旧配 置上， RNC在旧配置上进行呼叫重建， 呼叫重建成功后再重建业务 RB。
( 2 )在 UE收到 RB建立消息并返回成功响应，但 RNC没有收到该响 应消息的情况下， RNC在新配置上通过插入呼叫重建流程挽回呼叫。
( 3 )在 UE收到 RB建立消息， 但重配过程中检测到无线链路失败或 RLC不恢复的情况下， UE会停止重配流程， 保持旧配置， 并上报原因为无 线链路失败的小区更新消息， 此时， RNC在旧配置上进行呼叫重建， 呼叫 重建成功后再重建业务 RB。
下面结合图 4至图 10详细描述本发明实施例。
图 4是业务建立过程中 RNC等空口 RB建立响应超时， 去激活 RL后 (仅包含 SRNC RL ),接收到 UE小区更新消息的流程示意图，如图 4所示， 该流程具体包括：
步骤 401 : RNC接收到 CN下发的业务指派消息；
步骤 402： RNC向 NodeB发送无线链路重配请求消息；
步骤 403： RNC接收到 NodeB返回的无线链路重配响应消息； 步骤 404: RNC向 UE发送无线承载建立消息；
步骤 405: RNC设置空口定时器 T1 (第一预设时间）；
步骤 406: RNC判断 T1定时器超时， 即在 T1过程中没有接收到来自
UE的响应消息；
步骤 407: RNC向 NodeB发送无线链路去激活命令消息， 去激活 UE 所属的无线链路；
步骤 408: RNC设置定时器 T2 (第二预设时间 ), 等待 UE的小区更新 消息；
步骤 409: RNC在定时器 T2超时前接收到来自 UE的小区更新消息， 该小区更新消息中携带有 UE当前的重配状态指示；
步骤 410: RNC向 NodeB发送无线链路删除请求消息；
步骤 411 : RNC接收到 NodeB返回的无线链路删除响应消息； 步骤 412: RNC向 NodeB发送无线链路建立请求消息； 步骤 413 : RNC接收到 NodeB返回的无线链路建立响应消息； 步骤 414: RNC向 UE发送小区更新确认消息；
步骤 415: RNC接收到 UE返回的重配完成消息；
步骤 416: RNC向 CN发送业务指派响应消息。
图 5是业务建立过程中 RNC等空口 RB建立响应超时， 去激活 RL后
(包含 DRNC RL ), 接收到 UE小区更新消息的流程示意图。 图 5在图 4 所示的基础上， 增加了无线链路去激活消息的跨 IUR 口 （logical interface between two RNCs,服务 RNC ( SRNC )和漂移 RNC ( DRNC )之间的接口） 处理， 当 UE的激活集包含 DRNC无线链路时， 需要通过 IUR口传递无线 链路去激活消息到 DRNC, 如图 5所示， 该流程具体包括：
步骤 501 : SRNC接收到 CN下发的业务指派消息；
步骤 502: SRNC向 NodeB发送无线链路重配请求消息；
步骤 503： SRNC向 DRNC发送无线链路重配请求消息；
步骤 504: DRNC向 NodeB ( DRNC )发送无线链路重配请求消息； 步骤 505: SRNC接收到 NodeB返回的无线链路重配响应消息； 步骤 506: DRNC接收到 NodeB ( DRNC )返回的无线链路重配响应消 息；
步骤 507: SRNC接收到 DRNC返回的无线链路重配响应消息； 步骤 508: SRNC向 UE发送无线承载建立消息；
步骤 509: SRNC设置空口定时器 T1 (第一预设时间）；
步骤 510: SRNC判断 T1定时器超时， 即在 T1过程中没有接收到来自 UE的响应消息；
步骤 511 : SRNC向 NodeB发送无线链路去激活命令消息， 去激活 UE 所属的无线链路；
步骤 512: SRNC向 DRNC发送无线链路去激活命令消息； 步骤 513: DRNC向 NodeB ( DRNC )发送无线链路去激活命令消息； 步骤 514: SRNC设置定时器 T2 (第二预设时间 ), 等待 UE的小区更 新消息；
步骤 515: SRNC在定时器 T2超时前接收到来自 UE的小区更新消息， 该小区更新消息中携带有 UE当前的重配状态指示；
步骤 516: SRNC向 NodeB发送无线链路删除请求消息；
步骤 517: SRNC向 DRNC发送无线链路删除请求消息；
步骤 518: DRNC向 NodeB ( DRNC )发送无线链路删除请求消息； 步骤 519: SRNC向 NodeB发送无线链路建立请求消息；
步骤 520: SRNC接收到 NodeB返回的无线链路建立响应消息； 步骤 521： SRNC向 UE发送小区更新确认消息；
步骤 522: SRNC接收到 UE返回的重配完成消息；
步骤 523: SRNC向 CN发送业务指派响应消息。
图 6是业务建立过程中 RNC等空口 RB建立响应超时，删除 RL后（仅 包含 SRNC RL ), 接收到 UE小区更新消息的流程示意图， 如图 6所示， 该 流程具体包括：
步骤 601 : RNC接收到 CN下发的业务指派消息；
步骤 602: RNC向 NodeB发送无线链路重配消息；
步骤 603： RNC接收到 NodeB返回的无线链路重配响应消息； 步骤 604: RNC向 UE发送无线承载建立消息；
步骤 605: RNC设置等待空口定时器 T1 ;
步骤 606: RNC判断 T1定时器超时， 即在 T1过程中没有收到 UE的 响应消息；
步骤 607： RNC向 NodeB发送无线链路删除请求消息；
步骤 608: RNC接收到 NodeB返回的无线链路删除响应消息； 步骤 609: RNC设置定时器 T2, 等待 UE的小区更新消息；
步骤 610: RNC在定时器 T2超时前接收到 UE的小区更新消息； 步骤 611 : RNC向 NodeB发送无线链路建立请求消息；
步骤 612: RNC接收到 NodeB返回的无线链路建立响应消息； 步骤 613: RNC向 UE发送小区更新确认消息；
步骤 614: RNC接收到 UE返回的重配完成消息；
步骤 615: RNC向 CN发送业务指派响应消息。
图 7是业务建立过程中 RNC等空口 RB建立响应超时，删除 1 1^后（包 含 DRNC RL ), 等到 UE小区更新的流程示意图。 图 7与图 6类似， 差别在 于在 T1超时后， 需增加 DRNC无线链路的删除， SRNC通过 IUR口将无 线链路删除传递到 DRNC, 如图 7所示， 该流程具体包括：
步骤 701 : SRNC接收到 CN下发的业务指派消息；
步骤 702: SRNC向 NodeB发送无线链路重配请求消息；
步骤 703： SRNC向 DRNC发送无线链路重配请求消息；
步骤 704: DRNC向 NodeB ( DRNC )发送无线链路重配请求消息； 步骤 705: SRNC接收到 NodeB返回的无线链路重配响应消息； 步骤 706: DRNC接收到 NodeB ( DRNC )返回的无线链路重配响应消 步骤 707: SRNC接收到 DRNC返回的无线链路重配响应消息； 步骤 708: SRNC向 UE发送无线承载建立消息；
步骤 709: SRNC设置空口定时器 T1 (第一预设时间）；
步骤 710: SRNC判断 T1定时器超时， 即在 T1过程中没有接收到来自 UE的响应消息；
步骤 711 : SRNC向 NodeB发送无线链路删除请求消息；
步骤 712: SRNC向 DRNC发送无线链路删除请求消息； 步骤 713: DRNC向 NodeB ( DRNC )发送无线链路删除请求消息； 步骤 714: SRNC设置定时器 T2 (第二预设时间 ), 等待 UE的小区更 新消息；
步骤 715: SRNC在定时器 T2超时前接收到来自 UE的小区更新消息， 该小区更新消息中携带有 UE当前的重配状态指示；
步骤 716: SRNC向 NodeB发送无线链路建立请求消息；
步骤 717: SRNC接收到 NodeB返回的无线链路建立响应消息； 步骤 718: SRNC向 UE发送小区更新确认消息；
步骤 719: SRNC接收到 UE返回的重配完成消息；
步骤 720: SRNC向 CN发送业务指派响应消息。
图 8是业务建立过程中， UE没有接收到 RB建立消息， RNC去激活无 线链路触发呼叫重建的流程示意图， 如图 8所示， 该流程具体包括：
步骤 801 : RNC接收到 CN下发的业务指派消息；
步骤 802: RNC向 NodeB发送无线链路重配请求消息；
步骤 803： RNC接收到 NodeB返回的无线链路重配响应消息； 步骤 804: RNC向 UE发送无线承载建立消息，无线承载建立消息用虚 线表示该消息没有发送到 UE;
步骤 805: RNC设置等待空口定时器 T1 ;
步骤 806: RNC判断 T1定时器超时， 即在 T1过程中没有收到 UE的 响应消息；
步骤 807: RNC向 NodeB发送无线链路去激活命令消息， 去激活 UE 所属的无线链路；
步骤 808: RNC设置定时器 T2, 等待 UE的小区更新消息；
步骤 809: RNC在定时器 T2超时前接收到 UE上报的小区更新消息， 该消息中没有携带重配指示信元， 表示 UE没有进行重配处理； 步骤 810: RNC向 NodeB发送无线链路删除请求消息；
步骤 811 : RNC接收到 NodeB返回的无线链路删除响应消息； 步骤 812: RNC向 NodeB发送无线链路建立请求消息；
步骤 813: RNC接收到 NodeB返回的无线链路建立响应消息； 步骤 814: RNC向 UE发送小区更新确认消息；
步骤 815: RNC接收到 UE返回的重配完成消息；
步骤 816: 在呼叫重建完成后， RNC向 UE发送无线承载建立消息； 步骤 817: RNC接收到 UE返回的 RB建立响应消息；
步骤 818: RNC向 CN发送业务指派响应消息。
图 9是业务建立过程中， UE没有收到 RB建立消息， RNC删除无线链 路触发呼叫重建的流程示意图， 图 9和图 8类似， 在删除无线链路触发呼 叫重建后 ,发送 RB建立消息给 UE进行业务无线承载的建立，如图 9所示 , 该流程具体包括：
步骤 901 : RNC接收到 CN下发的业务指派消息；
步骤 902： RNC向 NodeB发送无线链路重配消息；
步骤 903： RNC接收到 NodeB返回的无线链路重配响应消息； 步骤 904: RNC向 UE发送无线承载建立消息，无线承载建立消息用虚 线表示该消息没有发送到 UE;
步骤 905: RNC设置等待空口定时器 T1 ;
步骤 906: RNC判断 T1定时器超时， 即在 T1过程中没有收到 UE的 响应消息；
步骤 907： RNC向 NodeB发送无线链路删除请求消息；
步骤 908: RNC接收到 NodeB返回的无线链路删除响应消息； 步骤 909: RNC设置定时器 T2, 等待 UE的小区更新消息；
步骤 910: RNC在定时器 T2超时前接收到 UE上报的小区更新消息， 该消息中没有携带重配指示信元， 表示 UE没有进行重配处理;
RNC向 NodeB发送无线链路建立请求消息;
RNC接收到 NodeB返回的无线链路建立响应消息；
RNC向 UE发送小区更新确认消息;
Figure imgf000017_0001
RNC接收到 UE返回的重配完成消息；
步骤 915: 在呼叫重建完成后， RNC向 UE发送无线承载建立消息； 步骤 916: RNC接收到 UE返回的 RB建立响应消息；
步骤 917: RNC向 CN发送业务指派响应消息。
图 10是业务建立过程中， RNC在空口响应超时前收到小区更新的流程 示意图， 如图 10所示， 该流程具体包括：
步骤 1001 : RNC接收到 CN下发的业务指派消息；
步骤 1002: RNC向 NodeB发送无线链路重配消息；
步骤 1003: RNC接收到 NodeB返回的无线链路重配响应消息； 步骤 1004: RNC向 UE发送无线承载建立消息；
步骤 1005: RNC设置等待空口定时器 T1 ;
步骤 1006: 在 T1定时器未超时前， RNC收到 UE的小区更新； 步骤 1007: RNC删除定时器 T1 ;
步骤 1008: RNC向 NodeB发送无线链路删除请求消息；
步骤 1009: RNC接收到 NodeB返回的无线链路删除响应消息； 步骤 1010: RNC向 NodeB发送无线链路建立请求消息；
步骤 1011 : RNC接收到 NodeB返回的无线链路建立响应消息； 步骤 1012: RNC向 UE发送小区更新确认消息；
步骤 1013: RNC接收到 UE返回的重配完成消息；
步骤 1014: 呼叫重建完成后， RNC向 UE发送 RB建立消息， 进行业 务无线承载的建立; 步骤 1015 : RNC接收到 UE返回的 RB建立响应消息；
步骤 1016: RNC向 CN发送业务指派响应消息。
在上述的流程示意图中，图 4~图 7示出 RNC等空口响应超时的具体实 施例， 其中图 4和图 5釆用的是无线链路去激活方式触发呼叫重建， 图 6 和图 7釆用无线链路删除方式触发呼叫重建， 图 4和 6是仅包括 S侧链路 的处理， 图 5和 7是包括 D侧链路的处理示意图； 图 8和图 9示出 UE没 有收到 RB建立消息的具体实施例，其中图 8釆用无线链路去激活方式触发 呼叫重建， 图 9釆用无线链路删除方式触发呼叫重建。 图 10示出了 RNC 在空口响应超时前收到小区更新的具体实施例。
为实现上述方法， 本发明还提供一种无线网络控制器， 图 11是根据本 发明的实施例的无线网络控制器的框图， 如图 11所示， 该无线网络控制器 包括：
发送模块 10, 用于向用户设备发送无线承载建立消息； 第一判断模块 20, 用于判断是否在第一预设时间内未接收到来自用户设备的无线承载响 应消息； 触发模块 30, 用于在第一判断模块的判断结果为是的情况时， 触 发用户设备上报小区更新消息； 接收模块 40, 用于接收来自用户设备的小 区更新消息； 第二判断模块 50, 用于根据小区更新消息所携带的信息和 /或 接收到小区更新消息的时间， 判断用户设备的配置状态； 重建处理模块 60, 用于根据第二判断模块判断的用户设备的配置状态进行呼叫重建处理。
其中， 触发模块 30通过向用户设备所属的基站发送无线链路去激活消 息或无线链路删除消息， 触发用户设备上报小区更新消息。
其中第二判断模块 50进一步包括： 第一判断子模块， 用于在小区更新 消息中未携带用户设备的重配信息时， 判断用户设备为第一配置状态； 第 二判断子模块， 用于在第一预设时间内接收到小区更新消息、 且小区更新 消息中携带有用户设备的重配信息时， 判断用户设备为第一配置状态； 第 三判断子模块， 用于在超过第一预设时间接收到小区更新消息、 且小区更 新消息中携带有用户设备的重配信息时， 判断用户设备为第二配置状态。
本发明还提供一种无线网络控制器， 该无线网络控制器包括： 第一发送模块， 用于向用户设备发送无线承载建立消息；
第一判断模块， 用于判断是否在第一预设时间内未接收到来自用户设 备的无线承载响应消息；
触发模块， 用于在所述第一判断模块的判断结果为是时， 触发所述用 户设备上报小区更新消息；
第二发送模块， 用于向漂移无线网络控制器发送无线链路去激活消息 或无线链路删除消息；
接收模块， 用于接收来自所述用户设备的小区更新消息；
第二判断模块， 用于根据所述小区更新消息所携带的信息和 /或接收到 所述小区更新消息的时间， 判断所述用户设备的配置状态；
重建处理模块， 用于根据所述第二判断模块判断的所述用户设备的配 置状态进行呼叫重建处理。
在具体实施中， 根据本发明实施例的无线网络控制器的工作流程可以 参考图 2至图 10, 此处不赘述。
综上所示， 根据本发明上述技术方案， 可以有效地挽回因空口失败导 致的掉话， 提高了网络呼通率。
以上所述仅为本发明的实施例而已， 并不用于限制本发明， 对于本领 域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的权 利要求范围之内。 工业实用性
本发明中通过在业务建立过程中插入呼叫重建， RNC触发 UE上报的 小区更新消息来判断 UE的配置状态， 使得在呼叫重建处理中 RNC和 UE 的配置状态一致， 从而提高了网络呼通率。

Claims

权利要求书
1、 一种提高业务呼通率的实现方法， 其特征在于， 该方法包括： 无线网络控制器向用户设备发送无线承载建立消息；
所述无线网络控制器判断是否在第一预设时间内未接收到来自用户设 备的无线承载响应消息， 若是， 则所述无线网络控制器触发所述用户设备 上报小区更新消息；
所述无线网络控制器接收到来自所述用户设备的小区更新消息， 并根 据所述小区更新消息所携带的信息和 /或接收到所述小区更新消息的时间， 判断所述用户设备的配置状态；
所述无线网络控制器根据所述用户设备的配置状态进行呼叫重建处 理。
2、 根据权利要求 1所述的方法， 其特征在于， 所述无线网络控制器触 发用户设备上报小区更新消息为：
所述无线网络控制器通过向所述用户设备所属的基站发送无线链路去 激活消息或无线链路删除消息， 触发所述用户设备上报小区更新消息。
3、 根据权利要求 1所述的方法， 其特征在于， 所述无线网络控制器根 据所述小区更新消息所携带的信息和 /或接收到所述小区更新消息的时间判 断所述用户设备的配置状态为：
若所述小区更新消息中未携带所述用户设备的重配信息， 则判断所述 用户设备为第一配置状态；
若在第一预设时间内接收到所述小区更新消息、 且所述小区更新消息 中携带有所述用户设备的重配信息， 则判断所述用户设备为第一配置状态； 若超过所述第一预设时间接收到所述小区更新消息、 且所述小区更新 消息中携带有所述用户设备的重配信息， 则判断所述用户设备为第二配置 状态。
4、 根据权利要求 3所述的方法， 其特征在于， 所述第一预设时间与第 二预设时间的和小于第三预设时间， 其中， 所述第二预设时间为所述用户 设备侧检测到无线链路失败的时间， 所述第三预设时间为从所述无线网络 控制器接收到来自核心网的业务指派请求到向所述核心网返回业务建立完 成的时间。
5、 根据权利要求 3所述的方法， 其特征在于， 所述无线网络控制器根 据所述用户设备的配置状态进行呼叫重建处理为：
若所述用户设备为第一配置状态， 则所述无线网络控制器在第一配置 状态进行呼叫重建， 呼叫重建成功后再重建业务无线承载；
若所述用户设备为第二配置状态， 则所述无线网络控制器在第二配置 状态进行呼叫重建。
6、 根据权利要求 1所述的方法， 其特征在于， 若所述无线网络控制器 在第一预定时间内接收到来自用户设备的无线承载响应消息， 该方法还包 括：
所述无线网络控制器接收来自所述用户设备主动上报的小区更新消 息；
所述无线网络控制器判断所述用户设备为第一配置状态；
所述无线网络控制器在第一配置状态进行呼叫重建处理。
7、 一种提高业务呼通率的实现方法， 其特征在于， 该方法包括： 服务无线网络控制器向用户设备发送无线承载建立消息；
所述服务无线网络控制器判断是否在第一预设时间内未接收到来自用 户设备的无线承载响应消息， 若是， 则所述服务无线网络控制器触发所述 用户设备上报小区更新消息；
所述服务无线网络控制器向漂移无线网络控制器发送无线链路去激活 消息或无线链路删除消息； 所述服务无线网络控制器接收到来自所述用户设备的小区更新消息， 并根据所述小区更新消息所携带的信息和 /或接收到所述小区更新消息的时 间， 判断所述用户设备的配置状态；
所述服务无线网络控制器根据所述用户设备的配置状态进行呼叫重建 处理。
8、 一种无线网络控制器， 其特征在于， 该无线网络控制器包括： 发送模块， 用于向用户设备发送无线承载建立消息；
第一判断模块， 用于判断是否在第一预设时间内未接收到来自用户设 备的无线承载响应消息；
触发模块， 用于在所述第一判断模块的判断结果为是时， 触发所述用 户设备上报小区更新消息；
接收模块， 用于接收来自所述用户设备的小区更新消息；
第二判断模块， 用于根据所述小区更新消息所携带的信息和 /或接收到 所述小区更新消息的时间， 判断所述用户设备的配置状态；
重建处理模块， 用于根据所述第二判断模块判断的所述用户设备的配 置状态进行呼叫重建处理。
9、 根据权利要求 8所述的无线网络控制器， 其特征在于， 所述触发模 块通过向所述用户设备所属的基站发送无线链路去激活消息或无线链路删 除消息， 触发所述用户设备上报小区更新消息。
10、 根据权利要求 8所述的无线网络控制器， 其特征在于， 所述第二 判断模块进一步包括：
第一判断子模块 , 用于在所述小区更新消息中未携带所述用户设备的 重配信息时， 判断所述用户设备为第一配置状态；
第二判断子模块， 用于在第一预设时间内接收到所述小区更新消息、 且所述小区更新消息中携带有所述用户设备的重配信息时， 判断所述用户 设备为第一配置状态；
第三判断子模块， 用于在超过所述第一预设时间接收到所述小区更新 消息、 且所述小区更新消息中携带有所述用户设备的重配信息时， 判断所 述用户设备为第二配置状态。
11、 一种无线网络控制器， 其特征在于， 该无线网络控制器包括： 第一发送模块， 用于向用户设备发送无线承载建立消息；
第一判断模块， 用于判断是否在第一预设时间内未接收到来自用户设 备的无线承载响应消息；
触发模块， 用于在所述第一判断模块的判断结果为是时， 触发所述用 户设备上报小区更新消息；
第二发送模块， 用于向漂移无线网络控制器发送无线链路去激活消息 或无线链路删除消息；
接收模块， 用于接收来自所述用户设备的小区更新消息；
第二判断模块， 用于根据所述小区更新消息所携带的信息和 /或接收到 所述小区更新消息的时间， 判断所述用户设备的配置状态；
重建处理模块， 用于根据所述第二判断模块判断的所述用户设备的配 置状态进行呼叫重建处理。
PCT/CN2011/073983 2010-06-25 2011-05-12 提高业务呼通率的实现方法及无线网络控制器 WO2011160504A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP11797535.9A EP2587847B1 (en) 2010-06-25 2011-05-12 Implementation method for improving call connection ratio of service and radio network controller
RU2013101518/07A RU2572089C2 (ru) 2010-06-25 2011-05-12 Способ увеличения коэффициента завершенных служебных вызовов и контроллер радиосети
US13/696,352 US8805395B2 (en) 2010-06-25 2011-05-12 Implementation method for improving service call completion ratio and radio network controller

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010220752.0 2010-06-25
CN201010220752.0A CN102300187B (zh) 2010-06-25 2010-06-25 提高业务呼通率的实现方法及无线网络控制器

Publications (1)

Publication Number Publication Date
WO2011160504A1 true WO2011160504A1 (zh) 2011-12-29

Family

ID=45360289

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/073983 WO2011160504A1 (zh) 2010-06-25 2011-05-12 提高业务呼通率的实现方法及无线网络控制器

Country Status (6)

Country Link
US (1) US8805395B2 (zh)
EP (1) EP2587847B1 (zh)
CN (1) CN102300187B (zh)
HK (1) HK1164614A1 (zh)
RU (1) RU2572089C2 (zh)
WO (1) WO2011160504A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102655651A (zh) * 2012-01-05 2012-09-05 电信科学技术研究院 语音业务的单通检测方法和设备
GB2505965B (en) * 2012-09-18 2015-06-10 Toshiba Res Europ Ltd Controller for coordinating wireless transmissions between a plurality of radio units and one or more user devices
US9071433B2 (en) * 2013-03-13 2015-06-30 Qualcomm Incorporated Method and apparatus for improving re-transmission of reconfiguration messages
CN104811997B (zh) * 2014-01-26 2019-07-05 中兴通讯股份有限公司 用户设备的配置状态管理方法、无线网络控制器及基站
WO2015163669A1 (en) * 2014-04-25 2015-10-29 Lg Electronics Inc. Method for a configuration error management for a sidelink radio bearer and device therefor
US9560610B2 (en) 2014-05-01 2017-01-31 Telefonaktiebolaget L M Ericsson (Publ) Monitoring of radio link synchronization in a user equipment's active set
WO2015169332A1 (en) * 2014-05-05 2015-11-12 Nokia Solutions And Networks Oy Rlc reconfiguration during cell reselection
CN104113928B (zh) * 2014-07-11 2018-04-17 大唐移动通信设备有限公司 一种无线承载控制rbc消息处理方法及装置
WO2016163825A1 (ko) * 2015-04-08 2016-10-13 엘지전자 주식회사 무선 통신 시스템에서 단말의 사이드링크 단말 정보 전송 방법 및 상기 방법을 이용하는 단말
WO2017177413A1 (zh) * 2016-04-14 2017-10-19 华为技术有限公司 链路异常信息的传输方法、装置和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1964555A (zh) * 2005-11-09 2007-05-16 大唐移动通信设备有限公司 一种无线承载业务重配置失败的处理方法
CN101646213A (zh) * 2008-08-07 2010-02-10 华为技术有限公司 小区重选优化方法和装置
CN101730162A (zh) * 2008-10-29 2010-06-09 中兴通讯股份有限公司 一种小区重选的方法
CN101730061A (zh) * 2008-10-31 2010-06-09 大唐移动通信设备有限公司 业务建立与小区更新的同步处理方法、装置及系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2571423C (en) * 2004-06-21 2014-08-05 Nokia Corporation Recovery method for lost signaling connection with high speed downlink packet access/fractional dedicated physical channel
US7801527B2 (en) * 2005-04-28 2010-09-21 Motorola Mobility, Inc. Cell update process with reconfiguration status
CN100455136C (zh) * 2006-06-01 2009-01-21 华为技术有限公司 小区更新的实现方法
EP2595337B1 (en) * 2010-07-15 2019-03-13 LG Electronics Inc. Method and apparatus for transmitting reception confirmation response of user equipment in wireless communication system
KR20130089659A (ko) * 2010-11-11 2013-08-12 퀄컴 인코포레이티드 회선 교환 폴백 성능을 개선하기 위한 시스템들 및 방법들
US20130286851A1 (en) * 2011-04-12 2013-10-31 Public Wireless, Inc. Common radio element application manager for wireless small cells

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1964555A (zh) * 2005-11-09 2007-05-16 大唐移动通信设备有限公司 一种无线承载业务重配置失败的处理方法
CN101646213A (zh) * 2008-08-07 2010-02-10 华为技术有限公司 小区重选优化方法和装置
CN101730162A (zh) * 2008-10-29 2010-06-09 中兴通讯股份有限公司 一种小区重选的方法
CN101730061A (zh) * 2008-10-31 2010-06-09 大唐移动通信设备有限公司 业务建立与小区更新的同步处理方法、装置及系统

Also Published As

Publication number Publication date
EP2587847A1 (en) 2013-05-01
CN102300187B (zh) 2014-09-10
RU2013101518A (ru) 2014-07-20
HK1164614A1 (zh) 2012-09-21
US20130053052A1 (en) 2013-02-28
RU2572089C2 (ru) 2015-12-27
US8805395B2 (en) 2014-08-12
CN102300187A (zh) 2011-12-28
EP2587847A4 (en) 2017-07-19
EP2587847B1 (en) 2019-08-28

Similar Documents

Publication Publication Date Title
US11582650B2 (en) Methods and system for performing handover in a wireless communication system
WO2011160504A1 (zh) 提高业务呼通率的实现方法及无线网络控制器
US10039086B2 (en) Communication method and apparatus in network environment where terminal may have dual connectivity to multiple base stations
JP6491675B2 (ja) Ｂｂｕプールにおける仮想基地局移行のための方法及び装置
US20080192703A1 (en) Method and system for recovering from drx timing de-synchronization in lte _active
WO2018171744A1 (zh) 无线链路监测方法和用户设备
WO2015113254A1 (zh) 一种无线链路失败的处理方法及设备
WO2010130135A1 (zh) 一种长期演进系统中跨基站切换方法及系统
CN111866965B (zh) 条件切换方法及对应的用户设备
US20220304092A1 (en) Fast failure recovery with master node
WO2017173612A1 (zh) 数据传输方法、用户设备及接入网设备
EP4094537A1 (en) Managing conditional configuration when a secondary cell is unavailable
US20210377758A1 (en) Communication control method
WO2011113378A2 (zh) 一种用户面缓冲器内存的恢复方法及装置
US20220007259A1 (en) Communication control method
WO2013079036A1 (zh) 一种资源释放控制方法及接入设备
CN115516989A (zh) 小区切换中的持续lbt失败检测和恢复的方法及装置
WO2011032319A1 (zh) 小区无线链路失败处理方法和用户设备
KR20100008232A (ko) 무선연결 설정방법
JP7426383B2 (ja) 通信制御方法
WO2013060228A1 (zh) 一种组合业务下进行信令传输的方法、设备及系统
WO2024065543A1 (zh) 失败检测及恢复方法和装置
CN118338348A (zh) 无线链路失败报告方法以及用户设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11797535

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011797535

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 13696352

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2013101518

Country of ref document: RU

Kind code of ref document: A