WO2013091355A1 - 链路删除方法、装置和系统 - Google Patents

链路删除方法、装置和系统 Download PDF

Info

Publication number
WO2013091355A1
WO2013091355A1 PCT/CN2012/076612 CN2012076612W WO2013091355A1 WO 2013091355 A1 WO2013091355 A1 WO 2013091355A1 CN 2012076612 W CN2012076612 W CN 2012076612W WO 2013091355 A1 WO2013091355 A1 WO 2013091355A1
Authority
WO
WIPO (PCT)
Prior art keywords
reconfiguration
message
air interface
service
rnc
Prior art date
Application number
PCT/CN2012/076612
Other languages
English (en)
French (fr)
Inventor
黄梅青
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013091355A1 publication Critical patent/WO2013091355A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]

Definitions

  • the present invention relates to the field of communications, and in particular to a link deletion method, apparatus, and system.
  • BACKGROUND In a Wideband Code Division Multiple Access (WCDMA) system a user can simultaneously communicate using multiple codewords on a certain carrier frequency, and these codewords belong to different cells.
  • WCDMA Wideband Code Division Multiple Access
  • RL radio link
  • the macro diversity technology enables the UE to obtain good radio quality from different cells when moving between different cells.
  • the entire service establishment fails due to the failure of the RL reconfiguration of a certain leg.
  • RL reconfiguration may include: code resource congestion, transmission chain scission, NODEB (base station) side channel processing unit (Channel Element, CE) resources are insufficient, power resources are congested, and so on.
  • NODEB base station
  • CE side channel processing unit
  • the first solution is to complete the service establishment process and then delete the RL that fails to be reconfigured.
  • this method can only be applied to a service cell that is not a High-Speed Packet Access (HSPA) service.
  • HSPA High-Speed Packet Access
  • the service establishment cannot be successful, and the method requires two consecutive modes.
  • the air interface process can complete the business establishment process.
  • the leg that fails the reconfiguration may cause interference to the air interface, which may easily lead to the return of the air interface message after the service establishment is completed.
  • the second solution is to roll back the service establishment process, then delete the RL that failed the reconfiguration, and finally re-establish the service.
  • the service establishment process needs to be canceled first, and then the soft-removal process is deleted to delete the RL that fails to be re-configured, and then the service establishment is re-initiated to complete the service establishment.
  • This method requires three air interface messages.
  • the embodiments of the present invention provide a method, an apparatus, and a system for deleting a link, so as to at least solve the problem that a process of deleting a reconfiguration failed RL in a related technical service process is long. According to an aspect of the present invention, a method for deleting a link is provided.
  • the method includes: in a service processing procedure, the RNC detects whether the current condition meets the following conditions: The UE is in a macro diversity state, and at least one of the RLs corresponding to the UE A reconfiguration fails, and at least one reconfiguration succeeds; if yes, the RNC instructs the UE to delete the RL that fails the reconfiguration through the air interface message in the service processing flow; after receiving the response message of the service processing flow returned by the UE, the RNC notifies the The base station corresponding to the RL that fails the reconfiguration fails to delete the RL that fails the reconfiguration.
  • the RNC indicates that the UE deletes the RL that fails the reconfiguration by using the air interface message, and the RNC sends the air interface message to the UE, where the air interface message is provided with an RL deletion indication field, where the RL deletion indication field carries the identifier of the RL with the reconfiguration failure.
  • the air interface message carries the changed serving cell as the designated RL; wherein the designated RL is the re-allocated RL; correspondingly, the RNC notification is heavy
  • the RL corresponding to the failed RL corresponding to the failed eNB includes: The RNC notifies the corresponding base station to change the serving cell of the UE to the cell where the designated RL is located.
  • the foregoing service processing flow includes at least one of the following: a service establishment process, a service release process, a service reconfiguration process, a transport channel reconfiguration process, and a physical channel reconfiguration process; for the service establishment process, the air interface message is a radio bearer setup message; The service release process, the air interface message is a radio bearer release message; for the service reconfiguration process, the air interface message is a radio bearer reconfiguration message; for the transport channel reconfiguration process, the air interface message is a transport channel reconfiguration message; In the process, the air interface message is a physical channel reconfiguration message.
  • a link deletion method includes: receiving, by a UE in a macro diversity state, an air interface message from an RNC, where the air interface message indicates that the UE deletes an RL that fails to be reconfigured; The UE initiates a corresponding service processing procedure according to the air interface message, and deletes the RL that fails the reconfiguration. After the service processing procedure is completed, the UE returns a response message to the RNC.
  • the method further includes: the UE changing the serving cell to the cell where the designated RL is located.
  • the foregoing service processing flow includes at least one of the following: a service establishment process, a service release process, a service reconfiguration process, a transport channel reconfiguration process, and a physical channel reconfiguration process; for the service establishment process, the air interface message is a radio bearer setup message; The service release process, the air interface message is a radio bearer release message; for the service reconfiguration process, the air interface message is a radio bearer reconfiguration message; for the transport channel reconfiguration process, the air interface message is a transport channel reconfiguration message; The matching process, the air interface message is a physical channel reconfiguration message.
  • a link deletion apparatus configured to detect, in a service processing flow, whether the current condition meets the following conditions: the UE is in a macro diversity state, At least one reconfiguration of the RL corresponding to the UE fails, and at least one reconfiguration succeeds.
  • the RL indication module is deleted, and if the detection result of the detection module is yes, the UE is deleted by the air interface message in the service processing flow.
  • the RL is configured to be re-configured, and the RL notification module is configured to: after receiving the response message of the service processing procedure returned by the UE, notify the base station corresponding to the RL that fails the reconfiguration to delete the RL that fails the reconfiguration.
  • the RL indicator module includes: a scenario determining unit, configured to determine that the current scenario is that the UE is in HSPA macro diversity, and the RL that fails to be reconfigured is an HSPA serving cell; and the RL indicating unit is configured to carry the changed serving cell by using an air interface message.
  • the device further includes: an air interface message selecting unit, configured to select an air interface message according to one of the following manners: the service processing procedure is a service establishment process, the air interface message is a radio bearer setup message; and the service processing flow is a service release process, the air interface The message is a radio bearer release message; the service process flow is a service reconfiguration process, the air interface message is a radio bearer reconfiguration message; and the service process flow is a transport channel reconfiguration process, the air interface message is a transport channel reconfiguration message; The processing flow is a physical channel reconfiguration process, and the air interface message is a physical channel reconfiguration message.
  • an air interface message selecting unit configured to select an air interface message according to one of the following manners: the service processing procedure is a service establishment process, the air interface message is a radio bearer setup message; and the service processing flow is a service release process, the air interface The message is a radio bearer release message; the service process flow is a service reconfiguration process, the air interface message is a radio bearer recon
  • the apparatus is configured to: the message receiving module is configured to receive an air interface message from the RNC, where the air interface message indicates that the UE deletes the reconfiguration.
  • the failed RL; the RL deleting module is configured to initiate a corresponding service processing flow according to the air interface message received by the message receiving module, and delete the RL that fails the reconfiguration; and the response returning module is set to return a response message to the RNC after the service processing flow is completed.
  • the device further includes: a cell change module, configured to change the serving cell to a cell where the designated RL is located when the UE device is in HSPA macro diversity, and the air interface message carries the changed serving cell as the designated RL.
  • a link deletion system where the system includes an RNC and a UE, where the RNC includes the first type of link deletion device, and the UE includes the second link deletion device.
  • the RNC instructs the UE to delete the RL that fails the reconfiguration through the air interface message in the flow, and reduces the number of air interface interactions.
  • the problem that the RL process that fails the reconfiguration fails is long, the service process is optimized, and the air interface resources are saved.
  • FIG. 1 is a flowchart of a method for deleting an RNC side link according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a UE side link deletion method according to an embodiment of the present invention
  • FIG. 3 is a flowchart according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for deleting an HSPA non-service RL in a service establishment process according to an embodiment of the present invention
  • FIG. 5 is a service establishment according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a link deletion method in a service establishment process according to an embodiment of the present invention
  • FIG. 7 is a plurality of lines in a service establishment process according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a method for deleting multiple links in a service establishment process according to an embodiment of the present invention
  • FIG. 9 is a structural block diagram of an apparatus for deleting an RNC side link according to an embodiment of the present invention
  • FIG. 10 is a structural block diagram of a UE side link deleting apparatus according to an embodiment of the present invention
  • FIG. 11 is a structural block diagram of a link deleting system according to an embodiment of the present invention.
  • Step S102 In the service processing procedure, the radio network controller (Radio Network Controller, RNC for short) detects whether the current condition meets the following conditions: The UE is in a macro diversity state, and the user equipment (User Equipment, UE for short) corresponds to the RL.
  • RNC Radio Network Controller
  • Step S104 if yes, the RNC indicates, by the air interface message in the service processing flow, that the UE deletes the reconfiguration failed RL;
  • Step S106 the RNC receives the UE returned After the service processing flow completes the response message, the base station corresponding to the RL that fails the reconfiguration is notified to delete the RL that fails the reconfiguration.
  • the RNC indicates that the UE deletes the RL that fails the reconfiguration through the air interface message in the process, reduces the number of air interface interactions, and resolves the correlation.
  • the problem of deleting the re-provisioning RL process in the service process is long, optimizes the service process, and saves air interface resources.
  • the RL that fails the reconfiguration may be located at the Iur port or at the Iub port.
  • the RNC indicates that the UE deletes the RL that fails the reconfiguration by using the air interface message, and the RNC sends the air interface message to the UE, where the air interface message is provided with an RL deletion indication field, where the RL deletion indication field carries the identifier of the RL with the reconfiguration failure.
  • the air interface message carries the changed serving cell as the designated RL, and the change information may be set in the cell used by the existing serving cell, and The RL may be set to be newly added.
  • the specified RL is the RL that is successfully reconfigured.
  • the RN corresponding to the RN that the RNC fails to notify the reconfiguration fails to delete the RL that fails to be reconfigured.
  • the serving cell of the UE is the cell in which the designated RL is located.
  • the foregoing service processing procedure includes at least one of the following: a service establishment process, a service release process, a service reconfiguration process, a transport channel reconfiguration process, and a physical channel reconfiguration process; for the service establishment process, the air interface message is a RADIO BEARER SETUP (radio bearer) Establish a message); for the service release process, the air interface message is RADIO BEARER RELEASE; for the service reconfiguration process, the air interface message is RADIO BEARER RECONFIGURATION; for the transport channel reconfiguration process The air interface message is TRANSPORT CHANNEL RECONFIGURATION; for the physical channel reconfiguration procedure, the air interface message is PHYSICAL CHANNEL RECONFIGURATION.
  • Step 1 The RNC detects whether the current condition meets the following conditions: The UE that initiates the service establishment is in a macro diversity state, at least one reconfiguration of the RL corresponding to the UE fails, and at least one reconfiguration succeeds; Step 2, if the foregoing detection result In the above, the RNC indicates that the UE deletes the RL that fails the reconfiguration by using the radio bearer setup message.
  • Step 3 After receiving the service establishment success response returned by the UE, the RNC notifies the reconfiguration failure.
  • the base station corresponding to the RL deletes the RL that fails the reconfiguration.
  • the RNC carries the message indicating that the UE deletes the RL of the reconfiguration failure in the radio bearer setup message sent to the UE, and reduces The number of air interface interactions is solved, which solves the problem that the RL process for deleting the reconfiguration fails in the related technology service establishment process is long, optimizes the processing flow, and saves the air interface resources.
  • the service establishment process is not subject to the HSPA service when the RL reconfiguration fails.
  • the limitation of the cell improves the success rate of service establishment.
  • the specific process of the link deletion method in the service establishment process provided by this embodiment is as follows: First, the UE establishes macro diversity, and the CN initiates a service establishment process by using the RNC; then, the CN sends a radio access bearer (Radio Access Bearer).
  • a radio access bearer Radio Access Bearer
  • RAB assigns a message to the RNC, so that the RNC initiates reconfiguration of all RLs; when one or more RL reconfigurations fail (as long as at least one RL reconfiguration is successful, service establishment can be performed), then the UE continues The service establishment process is performed, and the RNC sends a radio bearer setup message to the UE, where the message carries the information indicating that the UE deletes the RL of the reconfiguration failure, for example, the identifier of the RL carrying the reconfiguration failure, and the like, and the RNC receives the return of the UE.
  • the NODEB base station where the RL that fails the reconfiguration is notified to delete the RL of the reconfiguration failure.
  • the method for establishing a service process is the same as the method for establishing a service in the prior art except for the link deletion method, and details are not described herein again.
  • an RL deletion indication field may be set in the radio bearer setup message (the field) It may be set in the idle field of the radio bearer setup message, or may be newly added in the radio bearer setup message, and the RL delete indication field carries the identifier of the RL that fails to be reconfigured. If multiple RL reconfiguration fails, the RL deletion indication field will carry the identifiers of the multiple reconfiguration failed RLs.
  • a preferred embodiment of the foregoing RNC indicating that the UE deletes the RL that fails the reconfiguration by using the radio bearer setup message is specifically described as follows:
  • the RNC sends a radio bearer setup message to the UE, where the radio bearer setup message is set with an RL delete indication field.
  • the RL deletion indication field carries an identifier of the RL with the reconfiguration failure.
  • This implementation can complete the reconfiguration of the failed RL notification without adding a new air interface message, saving the air interface resources and deleting the reconfiguration failed RL time.
  • the service RL reconfiguration fails in the HSPA service cell in the related art.
  • This embodiment provides a preferred implementation manner.
  • the service RL reconfiguration fails (that is, as long as one service RL reconfiguration is successful, the service establishment process can be performed).
  • the radio bearer setup message sent by the RNC to the UE carries the changed RRC as the designated RL, and the RL that is successfully reconfigured in the RL reconfiguration process can be set to the designated RL, and then the RNC notifies the corresponding base station to change the serving cell of the UE.
  • the preferred embodiment provides the following method:
  • the radio bearer setup message carries the message that the serving cell is the designated RL.
  • the specified RL is an RL with a successful reconfiguration.
  • the RNC also notifies the corresponding base station to change the serving cell of the UE to the cell where the specified RL is located.
  • the link deletion method in this embodiment may be used, and the operation of changing the serving cell is not performed.
  • the present embodiment further provides a link deletion method, which is described by taking the UE side description in the macro diversity state as an example, and the flowchart of the UE side link deletion method shown in FIG. 2, the method includes the following Steps (step S202 - step S206):
  • Step S202 The UE in the macro diversity state receives the air interface message from the RNC, where the air interface message indicates that the UE deletes the RL that fails the reconfiguration;
  • Step S204 the UE initiates the corresponding message according to the air interface message.
  • the service process is performed, and the RL that fails the reconfiguration is deleted.
  • Step S206 After the service processing procedure is completed, the UE returns a response message to the RNC.
  • the RNC receives the RL that fails the reconfiguration reconfiguration indicated by the air interface message in the process, and the UR is completed.
  • the deletion of the RL reduces the number of air interface interactions and solves the problem of long RL process for deleting reconfiguration failures in the related service processing flow, optimizes the processing flow, and saves air interface resources.
  • the method further includes: the UE changes the serving cell to the cell where the designated RL is located, that is, deletes the original serving cell, and sets the serving cell. It is the cell where the RL is located.
  • the foregoing service process includes at least one of the following: a service establishment process, a service release process, a service reconfiguration process, a transport channel reconfiguration process, and a physical channel reconfiguration process; the specific air interface message corresponding to each process may be the same as above. I won't go into details here.
  • the following takes the link deletion method in the service establishment process as an example.
  • the method includes the following steps: Step 1: The UE in the macro diversity state receives a radio bearer setup message from the RNC, where the radio bearer setup message indicates the UE deletes The RL fails to be reconfigured. Step 2: The UE triggers the establishment of the service according to the radio bearer setup message, and deletes the RL that fails the reconfiguration.
  • Step 3 The UE returns a service establishment success response to the RNC.
  • the radio bearer setup message sent by the UE to the RNC carries a message indicating that the UE deletes the reconfiguration failed RL. Based on the message, the UE deletes the RL that fails to be reconfigured, reduces the number of air interface interactions, and solves the problem that the RL process for deleting the reconfiguration failure is long in the related technology service establishment process, optimizes the processing flow, and saves air interface resources;
  • the service establishment process is not restricted by the HSPA serving cell, which improves the success rate of service establishment.
  • the service RL reconfiguration fails.
  • the present embodiment provides a preferred implementation manner.
  • the UE is in the HSPA macro diversity state, if one or more RLs are reconfigured.
  • the RB re-provisioning process can be performed in the RL re-provisioning process.
  • the radio bearer setup message sent by the RNC carries the changed serving cell as the designated RL.
  • the reconfigured RL is set to the specified RL, and then the UE can change the serving cell to the cell where the designated RL is located according to the received radio bearer setup message.
  • the preferred embodiment provides the following method:
  • the UE When the UE is in HSPA macro diversity, and the radio bearer setup message carries the changed serving cell as the designated RL, the UE changes the serving cell to the cell where the designated RL is located. .
  • the link deletion method in this embodiment may be used, and the operation of changing the serving cell is not performed.
  • This embodiment is also applicable to other macro diversity states, such as service reconfiguration and channel reconfiguration. When a certain RL reconfiguration fails, the method can also be used for salvage processing.
  • the implementation process of the above embodiment will be described in detail below in conjunction with the preferred embodiments and the accompanying drawings.
  • Embodiment 1 when a service is established in a UE in a two-path macrodiversity state (that is, two RLs), the process of establishing a service by using the link deletion method when the R99 RL reconfiguration fails in the embodiment of the present invention is performed.
  • Figure 3 shows the R99 RL deletion method in the service establishment process. The method includes the following steps (step S302 - step S314): Step S302, the RNC configures the R99 co-frequency neighboring cell, so that the UE establishes the two-path R99 macro diversity, and then Initiate the business establishment process.
  • the R99 co-frequency neighboring cell may be the same-frequency neighboring cell in the RNC or the same-frequency neighboring cell in the Ran. In this embodiment, the case where the R99 co-frequency neighboring cell is the same-frequency neighboring cell in the RNC is described in detail.
  • Step S304 the CN sends an RAB ASSIGN (RAB Assignment) message to the RNC, and the RNC initiates reconfiguration of all RLs.
  • RAB ASSIGN RAB Assignment
  • one RL reconfiguration fails, and another RL reconfiguration succeeds.
  • NODEB returns a RADIO LINK RECONFIGURATION FAILURE message to the RNC.
  • Step S308 the RNC sends an RB SETUP (Radio Bearer Setup) message to the UE, where the message carries a message indicating that the UE deletes the reconfiguration failed RL.
  • Step S310 After receiving the radio bearer setup message, the UE triggers the establishment of the service according to the radio bearer setup message, and deletes the RL that fails the reconfiguration according to the indication of the RNC, and then returns an RB SETUP (Radio Bearer Setup) success response message to the RNC.
  • Step S312 After receiving the radio bearer establishment success response, the RNC notifies the corresponding NODEB to delete the RL that fails the reconfiguration.
  • Step S314 the RNC sends a RAB ASSIGN RSPONSE (Service Assignment Response) message to the CN.
  • RAB ASSIGN RSPONSE Service Assignment Response
  • the foregoing method is described in the case where the R99 co-frequency neighboring cell is the same-frequency neighboring cell in the RNC. If the R99 co-frequency neighboring cell is in the same-frequency neighboring cell across the Iur port, the specific process is similar, but only when a certain RL reconfiguration fails.
  • the RADIO LINK RECONFIGURATION FAILURE message is returned to the RNC by the Drift Radio Network Controller (DRNC), and then the RNC notifies the RNC after receiving the radio bearer establishment success response of the UE.
  • the corresponding DRNC deletes the RL that failed the above reconfiguration.
  • the process of the service establishment method provided in this embodiment is the same as the normal service establishment process, and the process time of the service establishment is similar to the regular service establishment process time.
  • the rollback service establishment process is first performed, and then the RL that fails the reconfiguration is deleted, and finally the RL is re-established.
  • the link deletion method provided in this embodiment only needs one air interface message, which reduces air interface interaction, saves air interface resources, simplifies the process of link deletion, shortens processing delay, and increases service establishment. Success rate.
  • FIG. 4 is a flowchart of a method for deleting an HSPA non-service RL in a service establishment process, where the method includes the following steps (step S402 to step S414): Step S402: The RNC configures an HSPA co-frequency neighboring cell, so that the UE establishes a second path. HSPA macro diversity, and then initiate the business establishment process.
  • the HSPA co-frequency neighboring cell may be the same-frequency neighboring cell in the RNC or the same-frequency neighboring cell in the RNC. In this embodiment, the case where the HSPA co-frequency neighboring cell is the same-frequency neighboring cell in the RNC is described in detail.
  • Step S404 the CN sends a RAB ASSIGN (RAB Assignment) message to the RNC, and the RNC initiates reconfiguration of all RLs.
  • Step S406 the non-serving cell RL reconfiguration fails, and another RL reconfiguration succeeds.
  • NODEB returns a RADIO LINK RECONFIGURATION FAILURE message to the RNC.
  • Step S408 The RNC sends an RB SETUP (Radio Bearer Setup) message to the UE, where the message carries a message indicating that the UE deletes the reconfiguration failed RL.
  • Step S410 After receiving the radio bearer setup message, the UE triggers the establishment of the service according to the radio bearer setup message, and deletes the reconfiguration failed RL according to the indication of the RNC, and then returns an RB SETUP (radio bearer setup) success response message to the RNC.
  • Step S412 After receiving the radio bearer establishment success response, the RNC notifies the corresponding NODEB to delete the RL that fails the reconfiguration.
  • the RNC sends a RAB ASSIGN RSPONSE message to the CN.
  • the foregoing method is described for the case where the HSPA co-frequency neighboring cell is the same-frequency neighboring cell in the RNC.
  • the HSPA co-frequency neighboring cell is the same-frequency neighboring cell across the Iur port.
  • the specific procedure is similar. Only when a non-serving RL reconfiguration fails, the DRNC returns RADIO LINK RECONFIGURATION FAILURE. The message is sent to the RNC, and after the RNC receives the successful response of the radio bearer setup of the UE, the RNC notifies the corresponding DRNC to delete the RL that failed the reconfiguration.
  • the RL that fails to be reconfigured in the service establishment process is an HSPA non-serving RL
  • the process of the service establishment method provided in this embodiment is the same as the normal service establishment process, and the process time of the service establishment is similar to the regular service establishment process time.
  • the method for deleting the re-allocated failed RL is not limited in the prior art.
  • the link deletion method provided in this embodiment fails when the non-serving RL reconfiguration fails in the HSPA serving cell. It can also be implemented without the limitation of the cell, which simplifies the process of link deletion, shortens the processing delay, and increases the success rate of service establishment.
  • the third embodiment describes the process of establishing a service by using the link deletion method when the HSPA service RL reconfiguration fails in the service establishment of the UE in the two-path macro-diversity state (that is, two RLs).
  • the embodiment is merely an example, and the application scenarios of the present invention include, but are not limited to, the embodiment.
  • Step S502 The RNC configures an HSPA co-frequency neighboring cell, so that the UE establishes a two-path HSPA. Macro diversity, and then initiate the business establishment process.
  • the HSPA co-frequency neighboring cell may be the same-frequency neighboring cell in the RNC or the same-frequency neighboring cell in the RNC. In this embodiment, the case where the HSPA co-frequency neighboring cell is the same-frequency neighboring cell in the RNC is described in detail.
  • Step S504 the CN sends an RAB ASSIGN (RAB Assignment) message to the RNC, and the RNC initiates reconfiguration of all RLs.
  • Step S506 the service cell RL reconfiguration fails, and another RL reconfiguration succeeds. NODEB returns a RADIO LINK RECONFIGURATION FAILURE message to the RNC.
  • Step S508 the RNC sends an RB SETUP (Radio Bearer Setup) message to the UE, where the message carries a message indicating that the UE deletes the reconfiguration failure RL.
  • the HSPA serving cell is changed to the RL with successful reconfiguration.
  • Step S510 After receiving the radio bearer setup message, the UE triggers the establishment of the service according to the radio bearer setup message, and deletes the reconfiguration failed RL according to the indication of the RNC, and changes the HSPA serving cell to be a reconfigured RL, and then returns the RB.
  • Step S512 After receiving the radio bearer establishment success response, the RNC notifies the corresponding NODEB to delete the RL that fails the reconfiguration, and notifies the NODEB to change the HSPA serving cell.
  • the above method is described in the case where the HSPA co-frequency neighboring cell is the same-frequency neighboring cell in the RNC. If the HSPA co-frequency neighboring cell is in the same-frequency neighboring cell across the Iur port, the specific process is similar, but the reconfiguration of the RL fails in a certain service.
  • the DRNC returns a RADIO LINK RECONFIGURATION FAILURE message to the RNC, and then after the RNC receives the UE's radio bearer setup success response, the RNC notifies the corresponding DRNC to delete the reconfiguration failed RL.
  • the process of the service establishment method provided by this embodiment is the same as the normal service establishment process, and the process time of the service establishment is similar to the regular service establishment process time.
  • the method of completing the service establishment process and then deleting the re-allocated failed RL is restricted by the HSPA serving cell.
  • the link deletion method provided in this embodiment may also be used when the service RL reconfiguration of the HSPA serving cell fails. Implementation, without the limitation of the cell, simplifies the process of link deletion, shortens the processing delay, and increases the success rate of service establishment.
  • Figure 6 is a schematic diagram of a link deletion method in the service establishment process.
  • the CN sends an RAB (Radio Access Bearer) to the RNC.
  • ASSIGN RAB SETUP
  • the RNC sends a RADIO LINK RECONFIGURATION (also referred to as RL RECFG) to the NODEB (wireless link reconfiguration).
  • NODEB returns RL RECFG READY (Radio Link Reconfiguration Complete message) to the RNC.
  • the RNC sends an RL RECFG message to the DRNC. If one RL reconfiguration fails (at least one RL reconfiguration succeeds, the service establishment can be completed).
  • the DRNC returns a RL RECFG FAILURE message to the RNC.
  • the RNC sends an RB SETUP (Radio Bearer Setup message) to the UE, where the message carries a message indicating that the reconfiguration failure RL is deleted.
  • the message returns the RB SETUP CMP (Radio Bearer Setup Complete message) to the RNC after the UE successfully deletes the RL that fails the reconfiguration and completes the service establishment.
  • RB SETUP Radio Bearer Setup message
  • Embodiment 4 This embodiment describes a process of establishing a service by using a link deletion method in which multiple RL reconfiguration failures of the present invention are performed when a service is established in a three-path macro-diversity state (that is, three RLs).
  • the embodiment is merely an example, and the application scenarios of the present invention include, but are not limited to, the embodiment.
  • Step S702 the RNC configures a co-frequency neighboring cell, so that the UE establishes a three-path macrodiversity, and then initiates a service establishment process.
  • the same-frequency neighboring cell may be the same-frequency neighboring cell in the RNC, or may be the same-frequency neighboring cell in the RNC. In this embodiment, the case where the same-frequency neighboring cell is the same-frequency neighboring cell in the RNC is described in detail.
  • Step S704 the CN sends an RAB ASSIGN (RAB Assignment) message to the RNC, and the RNC initiates reconfiguration of all RLs.
  • Step S706 the two serving cell RL reconfiguration fails, and another RL reconfiguration succeeds.
  • Both NODEB1 and NODEB2 return a RADIO LINK RECONFIGURATION FAILURE message to the RNC.
  • this embodiment only exemplifies the failure of two RL reconfigurations. If there are multiple RLs that fail to be reconfigured, the method of this embodiment may be adopted as long as at least one RL reconfiguration is successful.
  • Step S708 The RNC sends an RB SETUP (Radio Bearer Setup) message to the UE, where the message carries a message indicating that the UE deletes two RLs that fail to reconfigure.
  • Step S710 After receiving the radio bearer setup message, the UE triggers the establishment of the service according to the radio bearer setup message, and deletes two RLs that fail to reconfigure according to the indication of the RNC, and then returns an RB SETUP (radio bearer setup) success response message.
  • RNC After receiving the radio bearer establishment success response, the RNC notifies the corresponding NODEB1 and NODEB2 to delete the two RLs that fail to be reconfigured.
  • Step S714 the RNC sends a RAB ASSIGN RSPONSE message to the CN.
  • the above method is described for the case where the intra-frequency neighboring cell is the same-frequency neighboring cell in the RNC. If the co-frequency neighboring cell is the same-frequency neighboring cell across the Iur port, the specific process is similar, only in the two RLs (of course, this embodiment is only The two RL reconfiguration failures are illustrated. If there are multiple RLs that fail to be reconfigured, as long as at least one RL reconfiguration is successful, the method in this embodiment can be used. When the reconfiguration fails, the DRNC returns. The RADIO LINK RECONFIGURATION FAILURE message is sent to the RNC.
  • FIG. 8 is a schematic diagram of multiple link deletion methods in the service establishment process. As shown in Figure 8, the specific process of the method is as follows: First, the CN sends RAB ASSIGN (RAB SETUP) to the RNC.
  • RAB ASSIGN RAB SETUP
  • the RNC sends a RADIO LINK RECONFIGURATION (also referred to as RL RECFG) to the NODEB1 and NODEB2 (radio link reconfiguration message), assuming the RL corresponding to NODEB1 If the reconfiguration succeeds, NODEB1 returns RL RECFG READY to the RNC, assuming that the RL reconfiguration corresponding to NODEB2 fails, and NODEB2 returns RL RECFG FAILURE to the RNC.
  • a RADIO LINK RECONFIGURATION also referred to as RL RECFG
  • the RNC sends an RL RECFG message to the DRNC. If multiple RL reconfiguration fails (that is, at least one RL reconfiguration succeeds), the DRNC returns the RL to the RNC.
  • the RECFG FAILURE message after receiving the returned message, the RNC sends an RB SETUP (Radio Bearer Setup message) to the UE, where the message carries a message indicating that the reconfiguration failed RL is deleted, and the UE successfully deletes the RL that fails the reconfiguration.
  • the RB SETUP CMP Radio Bearer Setup Complete message
  • FIG. 9 is a structural block diagram of an RNC side link deletion apparatus according to an embodiment of the present invention. As shown in FIG.
  • the apparatus includes: a detection module 90, a deletion RL indication module 92, and a deletion RL notification module 94.
  • the structure will be described below.
  • the detecting module 90 is configured to detect, in the service processing flow, whether the current condition meets the following conditions: the UE is in a macro diversity state, at least one reconfiguration in the RL corresponding to the UE fails, and at least one reconfiguration succeeds; and the RL indication module 92 is deleted.
  • the detection module 90 is configured to, when the detection result of the detection module 90 is YES, instruct the UE to delete the RL that fails the reconfiguration through the air interface message in the service processing flow; delete the RL notification module 94, and connect to the delete RL indication.
  • the module 92 is configured to: after receiving the response message that the service processing procedure is completed by the UE, notify the base station corresponding to the RL that fails the reconfiguration to delete the RL that fails the reconfiguration.
  • the RL indication module 92 indicates that the UE deletes the RL that fails the reconfiguration through the air interface message in the process, and the related service is resolved.
  • the process of deleting the re-provisioning RL process is long, the processing flow is optimized, the processing delay is shortened, the air interface interaction is reduced, and the air interface resource is saved.
  • the RL indicator module 92 includes: a scenario determining unit, configured to determine that the current scenario is that the UE is in HSPA macro diversity, and the RL that fails the reconfiguration is an HSPA serving cell; and the RL indicating unit is configured to carry the change serving cell by using the air interface message The RL is instructed by the RL; the device further includes: a cell change notification module, configured to notify the corresponding base station to change the serving cell of the UE to the cell where the designated RL is located.
  • the deleting RL indication module 92 further includes: an air interface message selecting unit, configured to select an air interface message according to one of the following manners: for the service processing procedure, the service establishment process, the air interface message is a radio bearer setup message; and the service processing procedure is a service release In the process, the air interface message is a radio bearer release message; the service process flow is a service reconfiguration process, the air interface message is a radio bearer reconfiguration message; and the service process flow is a transport channel reconfiguration process, the air interface message is a transport channel reconfiguration The service process is a physical channel reconfiguration process, and the air interface message is a physical channel reconfiguration message.
  • the air interface message is a radio bearer setup message as an example.
  • this embodiment provides a preferred implementation manner, that is, an RL deletion indication field may be further set in the radio bearer setup message.
  • the RL delete indication field carries the identifier of the RL with the reconfiguration failure. If the RL reconfiguration fails, the RL deletion indication field carries multiple identifiers of the RL with the reconfiguration failure.
  • the RNC indicates, by the radio bearer setup message, that the UE deletes the RL that fails to be reconfigured, and includes: the RNC sends a radio bearer setup message to the UE, where the radio bearer setup message is set with an RL delete indication field, and the RL deletes
  • the indication field carries the identity of the RL with the reconfiguration failure.
  • the service RL reconfiguration fails in the HSPA service cell in the related art.
  • the service RL reconfiguration fails (that is, as long as a service RL reconfiguration is successful, the service establishment process can be performed).
  • the RL that fails to be reconfigured may be located at the Iur port or at the Iub port.
  • the radio bearer setup message sent by the RNC to the UE carries the changed RRC as the designated RL, and the RL that is successfully reconfigured in the RL reconfiguration process can be set to the designated RL, and then the RNC notifies the corresponding base station to change the serving cell of the UE.
  • the cell in which the specified RL is located Corresponding to the RNC side link deletion device, the embodiment further provides a link deletion device.
  • the device in this embodiment may be set in a UE in a macro diversity state, as shown in FIG.
  • a structural block diagram of the deleting device the device comprising: a message receiving module 12, an RL deleting module 14, and a response returning module 16.
  • the structure will be described below.
  • the message receiving module 12 is configured to receive an air interface message from the RNC, where the air interface message indicates that the UE deletes the RL that fails the reconfiguration;
  • the RL deleting module 14 is connected to the message receiving module 12, and is configured to initiate a corresponding service processing flow according to the air interface message received by the message receiving module 12, and delete the RL that fails the reconfiguration; the response returning module 16 is connected to the RL deleting module. 14, after setting the above business process flow,
  • the RNC returns a successful response to the establishment of the service.
  • the RL deleting module 14 deletes the RL that fails to be reconfigured, reduces the number of air interface interactions, and solves the problem of deleting the reconfiguration in the service processing process.
  • the problem of a long failed RL process optimizes the business process and saves air interface resources.
  • the device further includes: a cell change module, configured to change the serving cell to a cell where the designated RL is located when the UE device is in HSPA macro diversity, and the air interface message carries the changed serving cell as the designated RL.
  • the service flow includes at least one of the following: a service establishment process, a service release process, a service reconfiguration process, a transport channel reconfiguration process, and a physical channel reconfiguration process; and the service establishment process, the air interface message is a radio bearer setup message; For the service release process, the air interface message is a radio bearer release message; for the service reconfiguration process, the air interface message is a radio bearer reconfiguration message; for the transport channel reconfiguration process, the air interface message is a transport channel reconfiguration message; The reconfiguration process, the air interface message is a physical channel reconfiguration message.
  • the radio bearer setup message carries the message that the serving cell is the designated RL, where the specified RL is used. To re-match the successful RL. Then, the RNC also notifies the corresponding base station to change the serving cell of the UE to the cell where the specified RL is located.
  • the preferred embodiment of the present invention provides a link deletion device in a service establishment process, where the device includes: a cell change module, configured to be When the UE is in the HSPA macro diversity, and the radio bearer setup message carries the changed serving cell as the designated RL, the serving cell is changed to the cell where the designated RL is located.
  • the link deleting apparatus of this embodiment may be used, and the operation of changing the serving cell is not performed.
  • the service establishment process is not restricted by the HSPA serving cell when the RL reconfiguration fails, and the success rate of service establishment is improved.
  • the present embodiment provides a link deletion system in a service establishment process, which is used to implement the above link deletion method and apparatus, and FIG. 11 is a diagram according to the present invention. A structural block diagram of a link deletion system of an embodiment, as shown in FIG.
  • the system includes: an RNC 110 and a UE 112,
  • the RNC 110 includes the link deletion device of FIG. 9 and the UE 112 includes the link deletion device of FIG. 10, and the specific functions of the modules are not described herein.
  • the RNC 110 determines whether the user that initiates the service establishment is in the macro diversity state and fails to re-allocate the partial RL in the service establishment process. If yes, the RNC 110 performs service establishment and deletes the reconfiguration failure RL. It has been described in detail in the embodiment of the link deletion method in the foregoing service processing, and details are not described herein again.
  • the UE 112 After receiving the radio bearer setup message, the UE 112 determines whether the radio bearer setup message sent by the RNC 110 carries an indication of deleting the RL that fails to be reconfigured. If yes, the UE 112 deletes the designated RL while performing service establishment. It can be seen from the above description that, in the case that the UE is in the service processing flow of the macro diversity, if the partial RL reconfiguration fails, the embodiment of the present invention sends the RNC to the RNC while maintaining the current service processing flow unchanged. A deletion indication of the RL that fails the reconfiguration is added to the air interface message of the user, so that the user and the system delete the RL that fails the reconfiguration while establishing the service.
  • the method is applicable to various scenarios, and is no longer limited by the failure to establish a service when the RL reconfiguration in the HSPA serving cell fails, and the service can be established more quickly, the signaling process is optimized, and the service establishment success rate is increased.
  • a general-purpose computing device which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.
  • Industrial Applicability The technical solution of the present invention adds a deletion indication of the RL that fails to be reconfigured to the air interface message sent by the RNC to the user, so that the user and the system delete the reconfiguration at the same time of establishing the service. Failed RL.
  • the method is applicable to various scenarios, and is no longer limited by the failure to establish a service when the RL reconfiguration in the HSPA serving cell fails, and the service can be established more quickly, the signaling process is optimized, and the service establishment success

Landscapes

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

Abstract

本发明公开了一种链路删除方法、装置和系统。其中，该方法包括：在业务处理流程中，RNC检测当前情况是否满足以下条件：UE处于宏分集状态，该UE对应的RL中至少有一条重配失败，且至少有一条重配成功；如果是，RNC通过业务处理流程中的空口消息指示上述UE删除重配失败的RL；RNC接收到该UE返回的该业务处理流程完成的响应消息后，通知重配失败的RL对应的基站删除上述重配失败的RL。通过本发明，优化了业务处理流程，并且缩短了处理时延，减少了空口交互，节省了空口资源。

Description

链路删除方法、 装置和系统 技术领域 本发明涉及通信领域， 具体而言， 涉及一种链路删除方法、 装置和系统。 背景技术 在宽带码分多址接入（Wideband Code Division Multiple Access,简称为 WCDMA) 系统中， 一个用户可以在某个载频上使用多个码字同时进行通讯， 这些码字分属不同 的小区， 此时用户和网络之间存在多条无线链路 （Radio Link, 简称为 RL) 链接的状 态， 称之为宏分集状态。 宏分集技术使得 UE在不同小区间移动时， 可以从不同的小 区获得很好的无线质量。 当 UE处于宏分集状态， 而核心网 （Core Network, 简称为 CN) 发起业务建立流程时， 可能由于某条腿的 RL重配失败， 而导致整个业务建立失 败。 导致 RL重配失败的原因很多， 可能有： 码资源拥塞、 传输断链、 NODEB (基站） 侧信道处理单元 （Channel Element, 简称为 CE) 资源不够、 功率资源拥塞等原因。 按照目前协议提供的信令流程， 有如下两种解决方式： 第一种解决方式是先完成 业务建立流程， 然后再删除重配失败的 RL。 但是该方式只能适用于不是 HSPA (High-Speed Packet Access, 高速分组接入） 服务小区的情况， 如果是 HSPA服务小 区重配失败， 则不能成功进行业务建立， 而且该方式需要连续的两个空口流程才能完 成业务建立过程。 此外， 重配失败的那条腿可能会对空口形成干扰， 容易导致业务建 立完成之后空口消息回不来。 第二种解决方式是先回滚业务建立流程，然后删除重配失败的 RL，最后重新进行 业务建立。 在该方式中， 需要先取消业务建立过程， 然后发起软去流程删除重配失败 的 RL， 后续再重新发起业务建立才能完成业务建立。此方式需要三个空口消息， 所需 时间太长， 会降低用户的感受度， 而且空口消息过多也会降低业务建立的成功率。 针对相关技术业务处理过程中删除重配失败的 RL的流程较长的问题， 目前尚未 提出有效的解决方案。 发明内容 本发明实施例提供了一种链路删除方法、 装置和系统， 以至少解决相关技术业 务处理过程中删除重配失败的 RL的流程较长的问题。 根据本发明实施例的一个方面， 提供了一种链路删除方法， 该方法包括： 在业务 处理流程中， RNC检测当前情况是否满足以下条件： UE处于宏分集状态， UE对应 的 RL中至少有一条重配失败， 且至少有一条重配成功； 如果是， RNC通过业务处理 流程中的空口消息指示 UE删除重配失败的 RL; RNC接收到 UE返回的业务处理流程 完成的响应消息后， 通知重配失败的 RL对应的基站删除重配失败的 RL。 上述 RNC通过空口消息指示 UE删除重配失败的 RL包括： RNC向 UE发送空口 消息， 其中， 该空口消息设置有 RL删除指示字段， 该 RL删除指示字段携带有重配失 败的 RL的标识。 当 UE处于 HSPA宏分集，且重配失败的 RL为 HSPA服务小区时， 空口消息携带 有变更服务小区为指定的 RL;其中，指定的 RL为重配成功的 RL;相应的，上述 RNC 通知重配失败的 RL对应的基站删除重配失败的 RL包括： RNC通知对应的基站变更 UE的服务小区为指定的 RL所在的小区。 上述业务处理流程至少包括以下之一： 业务建立流程、 业务释放流程、 业务重配 流程、 传输信道重配流程和物理信道重配流程； 对于业务建立流程， 该空口消息为无 线承载建立消息； 对于业务释放流程， 空口消息为无线承载释放消息； 对于业务重配 流程， 该空口消息为无线承载重配消息； 对于传输信道重配流程， 该空口消息为传输 信道重配消息； 对于物理信道重配流程， 该空口消息为物理信道重配消息。 根据本发明实施例的另一方面， 提供了一种链路删除方法， 该方法包括： 处于宏 分集状态的 UE接收来自 RNC的空口消息， 其中， 该空口消息指示 UE删除重配失败 的 RL; UE根据空口消息发起对应的业务处理流程， 并删除重配失败的 RL; 业务处 理流程完成后， UE向 RNC返回响应消息。 当 UE处于 HSPA宏分集，且该空口消息携带有变更服务小区为指定的 RL时，该 方法还包括： UE变更服务小区为指定的 RL所在的小区。 上述业务处理流程至少包括以下之一： 业务建立流程、 业务释放流程、 业务重配 流程、 传输信道重配流程和物理信道重配流程； 对于业务建立流程， 该空口消息为无 线承载建立消息； 对于业务释放流程， 该空口消息为无线承载释放消息； 对于业务重 配流程， 该空口消息为无线承载重配消息； 对于传输信道重配流程， 该空口消息为传 输信道重配消息； 对于物理信道重配流程， 该空口消息为物理信道重配消息。 根据本发明实施例的再一方面， 提供了一种链路删除装置， 该装置包括： 检测模 块，设置为在业务处理流程中，检测当前情况是否满足以下条件： UE处于宏分集状态， UE对应的 RL中至少有一条重配失败， 且至少有一条重配成功； 删除 RL指示模块， 设置为在检测模块的检测结果为是的情况下，通过业务处理流程中的空口消息指示 UE 删除重配失败的 RL; 删除 RL通知模块， 设置为接收到 UE返回的上述业务处理流程 完成的响应消息后， 通知重配失败的 RL对应的基站删除重配失败的 RL。 上述删除 RL指示模块包括:场景确定单元，设置为确定当前场景为 UE处于 HSPA 宏分集， 且重配失败的 RL为 HSPA服务小区； RL指示单元， 设置为通过空口消息携 带变更服务小区为指定的 RL的指示； 其中， 指定的 RL为重配成功的 RL; 该装置还 包括： 小区变更通知模块， 设置为通知对应的基站变更 UE 的服务小区为指定的 RL 所在的小区。 该装置还包括： 空口消息选择单元， 设置为按照以下方式之一选择空口消息： 对 于业务处理流程为业务建立流程， 该空口消息为无线承载建立消息； 对于业务处理流 程为业务释放流程， 该空口消息为无线承载释放消息； 对于业务处理流程为业务重配 流程， 该空口消息为无线承载重配消息； 对于业务处理流程为传输信道重配流程， 该 空口消息为传输信道重配消息； 对于业务处理流程为物理信道重配流程， 该空口消息 为物理信道重配消息。 根据本发明实施例的又一方面， 提供了一种链路删除装置， 该装置设置 UE上， 包括： 消息接收模块， 设置为接收来自 RNC的空口消息， 其中， 该空口消息指示 UE 删除重配失败的 RL; RL删除模块， 设置为根据消息接收模块接收的空口消息发起对 应的业务处理流程， 并删除重配失败的 RL; 响应返回模块， 设置为业务处理流程完成 后， 向 RNC返回响应消息。 该装置还包括： 小区变更模块， 设置为当 UE装置处于 HSPA宏分集， 且空口消 息携带有变更服务小区为指定的 RL时， 变更服务小区为指定的 RL所在的小区。 根据本发明实施例的还一方面， 提供了一种链路删除系统， 该系统包括 RNC 和 UE, 其中该 RNC包括上述第一种链路删除装置， 该 UE包括上述第二种链路删除装 置。 通过本发明， 在业务处理流程中， 如果 UE处于宏分集状态且存在 RL重配失败 的情况， RNC通过该流程中的空口消息指示 UE删除重配失败的 RL， 减少了空口交 互次数， 解决了相关技术业务处理过程中删除重配失败的 RL流程较长的问题， 优化 了业务处理流程， 并节省了空口资源。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中： 图 1是根据本发明实施例的 RNC侧链路删除方法的流程图； 图 2是根据本发明实施例的 UE侧链路删除方法的流程图； 图 3是根据本发明实施例的业务建立过程中的 R99 RL删除方法的流程图； 图 4是根据本发明实施例的业务建立过程中的 HSPA非服务 RL删除方法的流程 图； 图 5是根据本发明实施例的业务建立过程中的 HSPA服务 RL删除方法的流程图； 图 6是根据本发明实施例的业务建立过程中的一条链路删除方法的示意图； 图 7是根据本发明实施例的业务建立过程中的多条链路删除方法的流程图； 图 8是根据本发明实施例的业务建立过程中的多条链路删除方法的示意图； 图 9是根据本发明实施例的 RNC侧链路删除装置的结构框图； 图 10是根据本发明实施例的 UE侧链路删除装置的结构框图； 图 11是根据本发明实施例的链路删除系统的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 本发明实施例针对在业务处理流程中出现某条 RL重配失败的情况， 提供了一种 链路删除方法、装置和系统， 用以简化现有的链路删除流程， 提升空口资源的利用率。 下面通过实施例进行详细说明。 本实施例提供了一种链路删除方法，该方法以在 RNC侧描述为例进行说明，如图 1所示的 RNC侧链路删除方法的流程图，该方法包括如下步骤（步骤 S102-步骤 S106): 步骤 S102， 在业务处理流程中， 无线网络控制器 （Radio Network Controller, 简 称为 RNC) 检测当前情况是否满足以下条件： UE处于宏分集状态， 用户设备 （User Equipment, 简称为 UE)对应的 RL中至少有一条重配失败， 且至少有一条重配成功； 步骤 S104, 如果是， RNC通过该业务处理流程中的空口消息指示 UE删除重配失 败的 RL; 步骤 S106， RNC接收到 UE返回的该业务处理流程完成的响应消息后， 通知重配 失败的 RL对应的基站删除重配失败的 RL。 本实施例在业务处理流程中， 如果 UE处于宏分集状态且存在 RL重配失败的情 况， RNC通过该流程中的空口消息指示 UE删除重配失败的 RL， 减少了空口交互次 数， 解决了相关业务处理流程中删除重配失败的 RL流程较长的问题， 优化了业务处 理流程， 并节省了空口资源。 其中， 上述重配失败的 RL可能位于 Iur口， 也可能位于 Iub口。 上述 RNC通过空口消息指示 UE删除重配失败的 RL包括： RNC向 UE发送空口 消息， 其中， 该空口消息设置有 RL删除指示字段， 该 RL删除指示字段携带有重配失 败的 RL的标识。 这种设置方式实现简单， 能够与现有协议兼容， 降低开发成本。 当 UE处于 HSPA宏分集，且重配失败的 RL为 HSPA服务小区时，上述空口消息 携带有变更服务小区为指定的 RL，该变更信息可以设置在现有的服务小区使用的信元 中， 也可以设置在新增的信元； 其中， 该指定的 RL为重配成功的 RL; 相应的， 上述 RNC通知重配失败的 RL对应的基站删除重配失败的 RL包括： RNC通知对应的基站 变更 UE的服务小区为指定的 RL所在的小区。 上述业务处理流程至少包括以下之一： 业务建立流程、 业务释放流程、 业务重配 流程、 传输信道重配流程和物理信道重配流程； 对于业务建立流程， 该空口消息为 RADIO BEARER SETUP (无线承载建立消息）； 对于业务释放流程， 该空口消息为 RADIO BEARER RELEASE (无线承载释放消息）； 对于业务重配流程， 该空口消息为 RADIO BEARER RECONFIGURATION (无线承载重配消息）；对于传输信道重配流程， 空口消息为 TRANSPORT CHANNEL RECONFIGURATION (传输信道重配消息）； 对 于物理信道重配流程， 空口消息为 PHYSICAL CHANNEL RECONFIGURATION (物 理信道重配消息）。下面仅以业务建立过程中的链路删除方法为例进行说明， 该方法包 括以下步骤： 步骤 1， RNC检测当前情况是否满足以下条件： 发起业务建立的 UE处于宏分集 状态， 该 UE对应的 RL中至少有一条重配失败， 且至少有一条重配成功； 步骤 2， 如果上述检测结果为是， 上述 RNC通过无线承载建立消息指示 UE删除 上述重配失败的 RL; 步骤 3， 上述 RNC接收到 UE返回的业务建立成功响应后， 通知上述重配失败的
RL对应的基站删除该重配失败的 RL。 通过上述方法， 在 UE处于宏分集时的业务建立流程且部分 RL重配失败的情况 下， RNC在发送给 UE的无线承载建立消息中， 携带了指示 UE删除重配失败的 RL 的消息， 减少了空口交互次数， 解决了相关技术业务建立过程中删除重配失败的 RL 流程较长的问题， 优化了处理流程， 并节省了空口资源； 同时使 RL重配失败时业务 建立过程不受 HSPA服务小区的限制， 提高了业务建立的成功率。 本实施例提供的业务建立过程中的链路删除方法的具体流程如下所述： 首先， UE 建立宏分集， CN通过 RNC使 UE发起业务建立流程； 然后， CN发送无线接入承载 (Radio Access Bearer,简称为 RAB)指派消息给 RNC，使 RNC发起所有 RL的重配； 当一个或多个 RL重配出现了失败 （只要保证至少一个 RL重配成功即可进行业务建 立）， 此时 UE继续进行业务建立流程， RNC向 UE发送无线承载建立消息， 在该消息 中可以携带指示 UE删除重配失败的 RL的信息，例如携带重配失败的 RL的标识号等； 在 RNC收到 UE返回的无线承载建立成功响应消息之后， 通知重配失败的 RL所在的 NODEB基站删除上述重配失败的 RL。 本实施例中除了链路删除方法之外， 业务建立 处理过程的方法与现有技术中的业务建立方法相同， 在此不再赘述。 为了方便将上述无线承载建立消息中的指示消息与重配失败的 RL相关联， 本实 施例提供了一种优选实施方式， 即在该无线承载建立消息中可以设置一个 RL删除指 示字段 （该字段可以设置在无线承载建立消息的空闲字段中， 也可以在无线承载建立 消息中新增加此字段）， 用该 RL删除指示字段携带重配失败的 RL的标识。 如果是多 个 RL重配失败， 则该 RL删除指示字段中将会携带这多个重配失败的 RL的标识。基 于此， 上述 RNC通过无线承载建立消息指示 UE删除上述重配失败的 RL的优选实施 方式具体描述为： RNC向 UE发送无线承载建立消息， 其中， 该无线承载建立消息设 置有 RL删除指示字段， 该 RL删除指示字段携带有重配失败的 RL的标识。这种实现 方式可以在不增加新的空口消息的基础上完成重配失败的 RL的通知， 节省了空口资 源和删除重配失败的 RL的时间。 为了不受相关技术中 HSPA服务小区的服务 RL重配失败就无法成功进行业务建 立的限制， 本实施例提供了一种优选实施方式， 当 UE处于 HSPA宏分集状态时， 如 果某一条或多条服务 RL重配失败（即只要保证有一条服务 RL重配成功就可以进行业 务建立过程）。 RNC发送给 UE的无线承载建立消息中携带有变更服务小区为指定的 RL, 可以将在 RL重配过程中重配成功的 RL设置为指定的 RL， 然后 RNC通知对应 的基站变更 UE的服务小区为指定的 RL所在的小区。 基于上述变更服务小区的方法，本优选实施方式提供以下方法： 当 UE处于 HSPA 宏分集， 且重配失败的 RL为 HSPA服务小区时， 无线承载建立消息携带有变更服务 小区为指定的 RL的消息， 其中该指定的 RL为重配成功的 RL。 然后 RNC还要通知 对应的基站变更 UE的服务小区为上述指定的 RL所在的小区。 当然， 对于 HSPA服务小区的非服务 RL重配失败时， 采用本实施例的链路删除 方法即可， 不用进行变更服务小区的操作。 本实施例还提供了一种链路删除方法， 该方法以在处于宏分集状态的 UE侧描述 为例进行说明，如图 2所示的 UE侧链路删除方法的流程图，该方法包括如下步骤（步 骤 S202-步骤 S206): 步骤 S202, 处于宏分集状态的 UE接收来自 RNC的空口消息， 其中， 该空口消 息指示 UE删除重配失败的 RL; 步骤 S204， UE根据该空口消息发起对应的业务处理流程，并删除重配失败的 RL; 步骤 S206, 上述业务处理流程完成后， UE向 RNC返回响应消息。 本实施例在上述业务处理流程中， 如果 UE处于宏分集状态且存在 RL重配失败 的情况， 将会接收到 RNC通过该流程中的空口消息指示的删除重配失败的 RL， 进而 该 UR完成该 RL的删除， 这种方式减少了空口交互次数， 解决了相关业务处理流程 中删除重配失败的 RL流程较长的问题， 优化了处理流程， 并节省了空口资源。 当 UE处于 HSPA宏分集，且该空口消息携带有变更服务小区为指定的 RL时，该 方法还包括： UE变更服务小区为指定的 RL所在的小区， 即删除原有服务小区， 将服 务小区设置为 RL所在的小区。 上述业务流程至少包括以下之一： 业务建立流程、业务释放流程、业务重配流程、 传输信道重配流程和物理信道重配流程； 每个流程对应的具体空口消息可以同上， 这 里不再赘述。 下面以业务建立过程中的链路删除方法为例进行说明， 该方法包括以下 步骤： 步骤 1， 处于宏分集状态的 UE接收来自 RNC的无线承载建立消息， 其中， 该无 线承载建立消息指示 UE删除上述重配失败的 RL; 步骤 2， UE根据该无线承载建立消息触发建立业务， 并删除上述重配失败的 RL; 步骤 3， UE向上述 RNC返回业务建立成功响应。 通过上述方法， 在 UE处于宏分集时的业务建立流程且部分 RL重配失败的情况 下， 在 UE接收到 RNC发送的无线承载建立消息中携带了指示 UE删除重配失败的 RL的消息， 该 UE基于此消息删除重配失败的 RL， 减少了空口交互次数， 解决了相 关技术业务建立过程中删除重配失败的 RL流程较长的问题， 优化了处理流程， 并节 省了空口资源； 同时使 RL重配失败时业务建立过程不受 HSPA服务小区的限制， 提 高了业务建立的成功率。 为了不受 HSPA服务小区的服务 RL重配失败就无法成功进行业务建立的限制， 本实施例提供了一种优选实施方式， 当 UE处于 HSPA宏分集状态时， 如果某一条或 多条 RL重配失败 （即只要保证有一条服务 RL重配成功就可以进行业务建立过程）， UE接收到的 RNC发送的无线承载建立消息中携带有变更服务小区为指定的 RL， 可 以将在 RL重配过程中重配成功的 RL设置为指定的 RL， 然后 UE根据接收到的上述 无线承载建立消息， 可以变更服务小区为指定的 RL所在的小区。 基于上述变更服务小区的方法，本优选实施方式提供以下方法： 当 UE处于 HSPA 宏分集， 并且无线承载建立消息携带有变更服务小区为指定的 RL时， UE变更服务小 区为指定的 RL所在的小区。 当然， 对于 HSPA服务小区的非服务 RL重配失败时， 采用本实施例的链路删除 方法即可， 不用进行变更服务小区的操作。 本实施例也适应于其他的宏分集状态下， 比如业务重配、 信道重配时， 某条 RL 重配失败时， 也可以采用该方法进行挽救处理。 下面结合优选实施例和附图对上述实施例的实现过程进行详细说明。 实施例一 本实施例对处于二径宏分集状态（即有两条 RL) 的 UE进行业务建立时， 采用本 发明实施例的 R99 RL重配失败时的链路删除方法进行业务建立的过程进行说明， 当 然本实施例仅仅是举例说明， 本发明的应用场景包括但不限于本实施例。 图 3所示的 是业务建立过程中的 R99 RL删除方法，该方法包括如下步骤（步骤 S302-步骤 S314): 步骤 S302， RNC配置 R99同频邻区， 使得 UE建立二径 R99宏分集， 然后发起 业务建立流程。该 R99同频邻区可以是 RNC内同频邻区，也可以是跨 Iur口同频邻区， 本实施例对 R99同频邻区是 RNC内同频邻区的情况进行详细说明。 步骤 S304， CN发送 RAB ASSIGN (RAB指派）消息给 RNC， RNC发起所有 RL 的重配。 步骤 S306,某条 RL重配失败，同时另外一条 RL重配成功。 NODEB返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失败） 消息给 RNC。 步骤 S308， RNC发送 RB SETUP (无线承载建立） 消息给 UE, 其中该消息中携 带指示 UE删除重配失败 RL的消息。 步骤 S310， UE收到上述无线承载建立消息后， 根据该无线承载建立消息触发建 立业务， 并且按照 RNC的指示删除重配失败的 RL， 然后返回 RB SETUP (无线承载 建立） 成功响应消息给 RNC。 步骤 S312， RNC收到上述无线承载建立成功响应后，通知对应的 NODEB删除上 述重配失败的 RL。 步骤 S314， RNC向 CN发送 RAB ASSIGN RSPONSE (业务指派响应） 消息。 上述方法是针对 R99同频邻区是 RNC内同频邻区的情况进行的描述， 如果 R99 同频邻区是跨 Iur口同频邻区， 具体流程类似， 只是在某一条 RL重配失败时， 由漂流 无线网络控制器 （Drift Radio Network Controller, 简称为 DRNC) 返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失败） 消息给 RNC， 然后在 RNC收 到 UE的无线承载建立成功响应后， RNC通知对应的 DRNC删除上述重配失败的 RL。 当业务建立过程中重配失败的 RL是 R99 RL时，本实施例提供的业务建立方法的 流程和常规的业务建立流程相同， 业务建立的流程时间也和常规的业务建立流程时间 类似， 相对于现有技术中的先回滚业务建立流程， 然后删除重配失败的 RL， 最后重新 进行业务建立的方式， 本实施例提供的链路删除方法仅需要一条空口消息， 减少了空 口交互， 节省了空口资源， 简化了链路删除的流程， 缩短了处理时延， 增加了业务建 立的成功率。 实施例二 本实施例对处于二径宏分集状态（即有两条 RL) 的 UE进行业务建立时， 采用本 发明的 HSPA非服务 RL重配失败时的链路删除方法进行业务建立的过程进行说明， 当然本实施例仅仅是举例说明， 本发明的应用场景包括但不限于本实施例。 图 4所示 的是业务建立过程中的 HSPA非服务 RL删除方法的流程图，该方法包括如下步骤（步 骤 S402-步骤 S414): 步骤 S402， RNC配置 HSPA同频邻区， 使得 UE建立二径 HSPA宏分集， 然后发 起业务建立流程。 该 HSPA同频邻区可以是 RNC内同频邻区， 也可以是跨 Iur口同频 邻区， 本实施例对 HSPA同频邻区是 RNC内同频邻区的情况进行详细说明。 步骤 S404， CN发送 RAB ASSIGN (RAB指派）消息给 RNC， RNC发起所有 RL 的重配。 步骤 S406, —条非服务小区 RL重配失败， 同时另外一条 RL重配成功。 NODEB 返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失败）消息给 RNC。 步骤 S408， RNC发送 RB SETUP (无线承载建立） 消息给 UE， 其中该消息中携 带指示 UE删除重配失败 RL的消息。 步骤 S410， UE收到上述无线承载建立消息后， 根据该无线承载建立消息触发建 立业务， 并且按照 RNC的指示删除重配失败的 RL， 然后返回 RB SETUP (无线承载 建立） 成功响应消息给 RNC。 步骤 S412， RNC收到上述无线承载建立成功响应后，通知对应的 NODEB删除上 述重配失败的 RL。 步骤 S414， RNC向 CN发送 RAB ASSIGN RSPONSE (指派响应） 消息。 上述方法是针对 HSPA 同频邻区是 RNC 内同频邻区的情况进行的描述， 如果
HSPA同频邻区是跨 Iur口同频邻区， 具体流程类似， 只是在某一条非服务 RL重配失 败时， 由 DRNC返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失 败） 消息给 RNC， 然后在 RNC收到 UE的无线承载建立成功响应后， RNC通知对应 的 DRNC删除上述重配失败的 RL。 当业务建立过程中重配失败的 RL是 HSPA非服务 RL时，本实施例提供的业务建 立方法的流程和常规的业务建立流程相同， 业务建立的流程时间也和常规的业务建立 流程时间类似， 相对于现有技术中先完成业务建立流程， 然后再删除重配失败的 RL 的方式受到 HSPA服务小区的限制， 本实施例提供的链路删除方法在 HSPA服务小区 的非服务 RL重配失败时也可以实现， 没有小区的限制， 简化了链路删除的流程， 缩 短了处理时延， 增加了业务建立的成功率。 实施例三 本实施例对处于二径宏分集状态（即有两条 RL) 的 UE进行业务建立时， 采用本 发明的 HSPA服务 RL重配失败时的链路删除方法进行业务建立的过程进行说明， 当 然本实施例仅仅是举例说明， 本发明的应用场景包括但不限于本实施例。 图 5所示的 是业务建立过程中的 HSPA服务 RL删除方法的流程图， 该方法包括如下步骤 （步骤 S502-步骤 S514): 步骤 S502， RNC配置 HSPA同频邻区， 使得 UE建立二径 HSPA宏分集， 然后发 起业务建立流程。 该 HSPA同频邻区可以是 RNC内同频邻区， 也可以是跨 Iur口同频 邻区， 本实施例对 HSPA同频邻区是 RNC内同频邻区的情况进行详细说明。 步骤 S504， CN发送 RAB ASSIGN (RAB指派）消息给 RNC， RNC发起所有 RL 的重配。 步骤 S506, —条服务小区 RL重配失败， 同时另外一条 RL重配成功。 NODEB 返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失败）消息给 RNC。 步骤 S508， RNC发送 RB SETUP (无线承载建立） 消息给 UE， 其中该消息中携 带指示 UE删除重配失败 RL的消息。 同时 HSPA服务小区变更为重配成功的 RL。 步骤 S510， UE收到上述无线承载建立消息后， 根据该无线承载建立消息触发建 立业务， 并且按照 RNC的指示删除重配失败的 RL， 并且变更 HSPA服务小区为重配 成功的 RL， 然后返回 RB SETUP (无线承载建立） 成功响应消息给 RNC。 步骤 S512， RNC收到上述无线承载建立成功响应后，通知对应的 NODEB删除上 述重配失败的 RL， 通知 NODEB变更 HSPA服务小区。 步骤 S514， RNC向 CN发送 RAB ASSIGN RSPONSE (指派响应） 消息。 上述方法是针对 HSPA 同频邻区是 RNC 内同频邻区的情况进行的描述， 如果 HSPA同频邻区是跨 Iur口同频邻区， 具体流程类似， 只是在某一条服务 RL重配失败 时，由 DRNC返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失败） 消息给 RNC， 然后在 RNC收到 UE 的无线承载建立成功响应后， RNC通知对应的 DRNC删除上述重配失败的 RL。 当业务建立过程中重配失败的 RL是 HSPA服务 RL时，本实施例提供的业务建立 方法的流程和常规的业务建立流程相同， 业务建立的流程时间也和常规的业务建立流 程时间类似， 相对于现有技术中先完成业务建立流程， 然后再删除重配失败的 RL的 方式受到 HSPA服务小区的限制， 本实施例提供的链路删除方法在 HSPA服务小区的 服务 RL重配失败时也可以实现， 没有小区的限制， 简化了链路删除的流程， 缩短了 处理时延， 增加了业务建立的成功率。 图 6所示的是业务建立过程中的一条链路删除方法的示意图， 如图 6所示， 该方 法的具体流程如下所述： 首先 CN向 RNC发送 RAB (Radio Access Bearer, 无线接入 承载） ASSIGN (RAB SETUP) (即 RAB指派消息）， 如果发起业务建立的用户所在的 小区是 RNC内同频邻区， RNC向 NODEB发送 RADIO LINK RECONFIGURATION (也可以简称为 RL RECFG) (无线链路重配消息）， RL全部重配成功后， NODEB向 RNC返回 RL RECFG READY (无线链路重配完成消息）。如果发起业务建立的用户所 在的小区是跨 Iur口同频邻区， RNC向 DRNC发送 RL RECFG消息， 如果有一条 RL 重配失败 （同时至少有一条 RL重配成功， 这样才能完成业务建立）， DRNC 向 RNC 返回 RL RECFG FAILURE (无线链路重配失败消息）， RNC收到返回的消息后， 发送 RB SETUP (无线承载建立消息） 给 UE， 其中该消息中携带有指示删除重配失败 RL 的消息， 在 UE成功删除上述重配失败的 RL， 并且业务建立完成后， 向 RNC返回 RB SETUP CMP (无线承载建立完成消息）。然后 RNC发送 RL DEL (无线链路删除消息） 给 NODEB，通知 NODEB删除上述重配失败的 RL。最后 RNC向 CN返回 RAB ASSIGN RSPONSE (指派回应消息）。 至此， 整个业务建立流程结束。 实施例四 本实施例对处于三径宏分集状态（即有三条 RL) 的 UE进行业务建立时， 采用本 发明的多条 RL重配失败时的链路删除方法进行业务建立的过程进行说明， 当然本实 施例仅仅是举例说明， 本发明的应用场景包括但不限于本实施例。 图 7所示的是业务 建立过程中的多条链路删除方法的流程图， 该方法包括如下步骤 （步骤 S702-步骤 S714): 步骤 S702， RNC配置同频邻区， 使得 UE建立三径宏分集， 然后发起业务建立流 程。 该同频邻区可以是 RNC内同频邻区， 也可以是跨 Iur口同频邻区， 本实施例对同 频邻区是 RNC内同频邻区的情况进行详细说明。 步骤 S704， CN发送 RAB ASSIGN (RAB指派）消息给 RNC， RNC发起所有 RL 的重配。 步骤 S706, 两条服务小区 RL重配失败， 同时另外一条 RL重配成功。 NODEB1 和 NODEB2都返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失 败） 消息给 RNC。 当然本实施例只是对两条 RL重配失败的情况进行举例说明， 如果 重配失败的 RL有多条，只要保证至少有一条 RL重配成功，便可采用本实施例的方法。 步骤 S708， RNC发送 RB SETUP (无线承载建立） 消息给 UE， 其中该消息中携 带指示 UE删除重配失败的两条 RL的消息。 步骤 S710， UE收到上述无线承载建立消息后， 根据该无线承载建立消息触发建 立业务， 并且按照 RNC的指示删除重配失败的两条 RL， 然后返回 RB SETUP (无线 承载建立） 成功响应消息给 RNC。 步骤 S712， RNC 收到上述无线承载建立成功响应后， 通知对应的 NODEB1 和 NODEB2删除上述重配失败的两条 RL。 步骤 S714， RNC向 CN发送 RAB ASSIGN RSPONSE (指派响应） 消息。 上述方法是针对同频邻区是 RNC内同频邻区的情况进行的描述，如果同频邻区是 跨 Iur口同频邻区， 具体流程类似， 只是在两条 RL (当然本实施例只是对两条 RL重 配失败的情况进行举例说明， 如果重配失败的 RL有多条， 只要保证至少有一条 RL 重配成功， 便可采用本实施例的方法） 重配失败时， 由 DRNC 返回 RADIO LINK RECONFIGURATION FAILURE (无线链路重配失败） 消息给 RNC， 然后在 RNC收 到 UE的无线承载建立成功响应后， RNC通知对应的 DRNC删除上述重配失败的 RL。 当业务建立过程中有多条 RL重配失败时， 本实施例提供的业务建立流程中的链 路删除方法在有多条 RL重配失败时， 也可以实现。 该方式简化了链路删除的流程， 缩短了处理时延， 增加了业务建立的成功率。 图 8所示的是业务建立过程中的多条链路删除方法的示意图， 如图 8所示， 该方 法的具体流程如下所述： 首先 CN向 RNC发送 RAB ASSIGN (RAB SETUP) (RAB 指派消息），如果发起业务建立的用户所在的小区是 RNC内同频邻区， RNC向 NODEBl 和 NODEB2发送 RADIO LINK RECONFIGURATION (也可以简称为 RL RECFG) (无 线链路重配消息）， 假设 NODEBl对应的 RL重配成功， NODEBl 向 RNC返回 RL RECFG READY (无线链路重配完成消息）， 假设 NODEB2 对应的 RL 重配失败， NODEB2向 RNC返回 RL RECFG FAILURE (无线链路重配失败消息）。 如果发起业 务建立的用户所在的小区是跨 Iur口同频邻区， RNC向 DRNC发送 RL RECFG消息， 如果有多条 RL重配失败（即至少有一条 RL重配成功）， DRNC向 RNC返回 RL RECFG FAILURE消息， RNC收到返回的消息后， 发送 RB SETUP (无线承载建立消息） 给 UE, 其中该消息中携带有指示删除重配失败 RL的消息， 在 UE成功删除上述重配失 败的 RL， 并且业务建立完成后， 向 RNC返回 RB SETUP CMP (无线承载建立完成消 息）。 然后 RNC发送 RL DEL (无线链路删除消息） 给 NODEBl和 NODEB2, 通知 NODEBl和 NODEB2删除上述重配失败的 RL。 最后 RNC向 CN返回 RAB ASSIGN RSPONSE (指派回应消息）。 至此， 整个业务建立流程结束。 对应于上述业务建立过程中的链路删除方法，本实施例提供了一种链路删除装置， 该装置可以在 RNC侧实现， 用于实现上述实施例。 图 9是根据本发明实施例的 RNC 侧链路删除装置的结构框图， 如图 9所示， 该装置包括： 检测模块 90、 删除 RL指示 模块 92和删除 RL通知模块 94。 下面对该结构进行说明。 检测模块 90， 设置为在业务处理流程中， 检测当前情况是否满足以下条件 UE处 于宏分集状态， UE对应的 RL中至少有一条重配失败， 且至少有一条重配成功； 删除 RL指示模块 92， 连接至检测模块 90， 设置为在检测模块 90的检测结果为 是的情况下， 通过业务处理流程中的空口消息指示 UE删除重配失败的 RL; 删除 RL通知模块 94， 连接至删除 RL指示模块 92， 设置为接收到 UE返回的上 述业务处理流程完成的响应消息后， 通知重配失败的 RL对应的基站删除该重配失败 的 RL。 通过上述装置， 在业务处理流程中， 如果 UE处于宏分集状态且存在 RL重配失 败的情况，删除 RL指示模块 92通过该流程中的空口消息指示 UE删除重配失败的 RL， 解决了相关业务处理流程中删除重配失败的 RL流程较长的问题， 优化了处理流程， 并且缩短了处理时延， 减少了空口交互， 节省了空口资源。 上述删除 RL指示模块 92包括： 场景确定单元， 设置为确定当前场景为 UE处于 HSPA宏分集， 且重配失败的 RL为 HSPA服务小区； RL指示单元， 设置为通过空口 消息携带变更服务小区为指定的 RL的指示； 其中， 该指定的 RL为重配成功的 RL; 该装置还包括： 小区变更通知模块， 设置为通知对应的基站变更 UE的服务小区为指 定的 RL所在的小区。 上述删除 RL指示模块 92还包括： 空口消息选择单元， 设置为按照以下方式之一 选择空口消息： 对于业务处理流程为业务建立流程， 该空口消息为无线承载建立消息； 对于业务处理流程为业务释放流程， 该空口消息为无线承载释放消息； 对于业务处理 流程为业务重配流程， 该空口消息为无线承载重配消息； 对于业务处理流程为传输信 道重配流程， 该空口消息为传输信道重配消息； 对于业务处理流程为物理信道重配流 程， 该空口消息为物理信道重配消息。 下面以业务处理流程为业务建立流程， 该空口 消息为无线承载建立消息为例进行说明。 为了方便将上述无线承载建立消息中的指示消息与重配失败的 RL相关联， 本实 施例提供了一种优选实施方式， 即在该无线承载建立消息中还可以设置有 RL删除指 示字段，该 RL删除指示字段携带有重配失败的 RL的标识。如果是多个 RL重配失败， 则该 RL删除指示字段中携带多个有重配失败的 RL的标识。上述优选实施方式具体描 述为： RNC通过无线承载建立消息指示 UE删除重配失败的 RL包括： RNC向 UE发 送无线承载建立消息， 其中， 该无线承载建立消息设置有 RL删除指示字段， 该 RL 删除指示字段携带有重配失败的 RL的标识。 为了不受相关技术中 HSPA服务小区的服务 RL重配失败就无法成功进行业务建 立的限制， 本实施例提供了一种优选实施方式， 当 UE处于 HSPA宏分集状态时， 如 果某一条或多条服务 RL重配失败（即只要保证有一条服务 RL重配成功就可以进行业 务建立过程）， 重配失败的 RL可能位于 Iur口， 也可能位于 Iub口。 RNC发送给 UE 的无线承载建立消息中携带有变更服务小区为指定的 RL，可以将在 RL重配过程中重 配成功的 RL设置为指定的 RL， 然后 RNC通知对应的基站变更 UE的服务小区为指 定的 RL所在的小区。 对应于上述 RNC侧链路删除装置，本实施例还提供了一种链路删除装置，本实施 例的装置可以设置在处于宏分集状态的 UE上， 如图 10所示的是 UE侧链路删除装置 的结构框图， 该装置包括： 消息接收模块 12、 RL删除模块 14和响应返回模块 16。 下 面对该结构进行说明。 消息接收模块 12， 设置为接收来自 RNC的空口消息， 其中， 该空口消息指示 UE 删除重配失败的 RL;
RL删除模块 14，连接至消息接收模块 12，设置为根据消息接收模块 12接收的空 口消息发起对应的业务处理流程， 并并删除上述重配失败的 RL; 响应返回模块 16， 连接至 RL删除模块 14， 设置为上述业务处理流程完成后， 向
RNC返回业务建立成功响应。 通过上述装置，在处于宏分集状态的 UE侧的消息接收模块 12接收到上述空口消 息之后， RL删除模块 14删除重配失败的 RL， 减少了空口交互次数， 解决了业务处理 过程中删除重配失败的 RL流程较长的问题， 优化了业务处理流程， 并节省了空口资 源。 该装置还包括： 小区变更模块， 设置为当 UE装置处于 HSPA宏分集， 且空口消 息携带有变更服务小区为指定的 RL时， 变更服务小区为指定的 RL所在的小区。 其中， 该业务流程至少包括以下之一： 业务建立流程、 业务释放流程、 业务重配 流程、 传输信道重配流程和物理信道重配流程； 对于业务建立流程， 该空口消息为无 线承载建立消息； 对于业务释放流程， 该空口消息为无线承载释放消息； 对于业务重 配流程， 该空口消息为无线承载重配消息； 对于传输信道重配流程， 该空口消息为传 输信道重配消息； 对于物理信道重配流程， 该空口消息为物理信道重配消息。 对于业务建立流程， 如果采用上述方式， 当 UE处于 HSPA宏分集， 且重配失败 的 RL为 HSPA服务小区时，无线承载建立消息携带有变更服务小区为指定的 RL的消 息， 其中该指定的 RL为重配成功的 RL。 然后 RNC还要通知对应的基站变更 UE的 服务小区为上述指定的 RL所在的小区。 针对上述服务小区变更的过程， 本实施例优 选实施方式提供了一种业务建立过程中的链路删除装置， 该装置除了包括上述装置中 的各个模块之外还包括： 小区变更模块， 设置为当 UE装置处于 HSPA宏分集， 且无 线承载建立消息携带有变更服务小区为指定的 RL时，变更服务小区为指定的 RL所在 的小区。 当然， 对于 HSPA服务小区的非服务 RL重配失败时， 采用本实施例的链路 删除装置即可， 不用进行变更服务小区的操作。 该方式还可以使 RL重配失败时业务 建立过程不受 HSPA服务小区的限制， 提高了业务建立的成功率。 对应于上述业务建立过程中的链路删除方法和装置， 本实施提供了一种业务建立 过程中的链路删除系统， 该系统用于实现上述链路删除方法和装置， 图 11是根据本发 明实施例的链路删除系统的结构框图，如图 11所示，该系统包括： RNC110和 UE112, 其中， 本实施例以 RNC110包括上述图 9的链路删除装置以及 UE112包括上述图 10 的链路删除装置为例进行说明， 这里不再赘述各个模块的具体功能。 对于业务建立过程中， 本实施例 RNC110先判断发起业务建立的用户是否处于宏 分集状态而且在业务建立过程中部分 RL重配失败，如果是， RNC110执行业务建立同 时删除重配失败 RL，该方式在上述业务处理过程中的链路删除方法的实施例中已经进 行了详细描述， 在此不再赘述。 UE112接收到无线承载建立消息后， 先判断 RNC110 发送的无线承载建立消息中是否携带有删除重配失败的 RL 的指示， 如果是， UE112 在执行业务建立的同时删除指定的 RL。 从以上的描述中可以看出， 当 UE处于宏分集时的业务处理流程中， 如果出现部 分 RL重配失败的情况，本发明实施例在保持当前业务处理流程不变的情况下，在 RNC 发送给用户的空口消息中加入重配失败的 RL的删除指示， 使得用户和系统在建立业 务的同时删除重配失败的 RL。 该方法适用于各种场景， 不再受 HSPA服务小区内的 RL重配失败时无法建立业务的限制， 并且可以更加快速的建立业务， 优化信令流程， 增加业务建立成功率。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。 工业实用性 本发明技术方案在保持当前业务处理流程不变的情况下，在 RNC发送给用户的空 口消息中加入重配失败的 RL的删除指示， 使得用户和系统在建立业务的同时删除重 配失败的 RL。 该方法适用于各种场景， 不再受 HSPA服务小区内的 RL重配失败时无 法建立业务的限制， 并且可以更加快速的建立业务， 优化了信令流程， 增加了业务建 立成功率。

Claims

权 利 要 求 书
1. 一种链路删除方法， 包括：
在业务处理流程中， 无线网络控制器 RNC检测当前情况是否满足以下条 件：用户设备 UE处于宏分集状态，所述 UE对应的无线链路 RL中至少有一条 重配失败， 且至少有一条重配成功；
如果是，所述 RNC通过所述业务处理流程中的空口消息指示所述 UE删除 重配失败的 RL;
所述 RNC接收到所述 UE返回的所述业务处理流程完成的响应消息后，通 知所述重配失败的 RL对应的基站删除所述重配失败的 RL。
2. 根据权利要求 1所述的方法， 其中， 所述 RNC通过空口消息指示所述 UE删除 重配失败的 RL包括：
所述 RNC向所述 UE发送空口消息， 其中， 所述空口消息设置有 RL删除 指示字段， 所述 RL删除指示字段携带有重配失败的 RL的标识。
3. 根据权利要求 1所述的方法， 其中， 当所述 UE处于高速分组接入 HSPA宏分 集， 且重配失败的 RL为 HSPA服务小区时， 所述空口消息携带有变更服务小 区为指定的 RL; 其中， 所述指定的 RL为重配成功的 RL;
所述 RNC通知所述重配失败的 RL对应的基站删除所述重配失败的 RL包 括： 所述 RNC通知所述对应的基站变更所述 UE的服务小区为所述指定的 RL 所在的小区。
4. 根据权利要求 1-3任一项所述的方法， 其中， 所述业务处理流程至少包括以下 之一： 业务建立流程、 业务释放流程、 业务重配流程、 传输信道重配流程和物 理信道重配流程；
对于所述业务建立流程， 所述空口消息为无线承载建立消息； 对于所述业务释放流程， 所述空口消息为无线承载释放消息； 对于所述业务重配流程， 所述空口消息为无线承载重配消息； 对于所述传输信道重配流程， 所述空口消息为传输信道重配消息； 对于所述物理信道重配流程， 所述空口消息为物理信道重配消息。
5. 一种链路删除方法， 包括：
处于宏分集状态的用户设备 UE接收来自无线网络控制器 RNC的空口消 息， 其中， 所述空口消息指示所述 UE删除重配失败的 RL;
所述 UE根据所述空口消息发起对应的业务处理流程， 并删除所述重配失 败的 RL;
所述业务处理流程完成后， 所述 UE向所述 RNC返回响应消息。
6. 根据权利要求 5所述的方法， 其中， 当所述 UE处于高速分组接入 HSPA宏分 集， 且所述空口消息携带有变更服务小区为指定的 RL时， 所述方法还包括： 所述 UE变更服务小区为所述指定的 RL所在的小区。
7. 根据权利要求 5或 6所述的方法，其中，所述业务处理流程至少包括以下之一： 业务建立流程、 业务释放流程、 业务重配流程、 传输信道重配流程和物理信道 重配流程；
对于所述业务建立流程， 所述空口消息为无线承载建立消息； 对于所述业务释放流程， 所述空口消息为无线承载释放消息； 对于所述业务重配流程， 所述空口消息为无线承载重配消息； 对于所述传输信道重配流程， 所述空口消息为传输信道重配消息； 对于所述物理信道重配流程， 所述空口消息为物理信道重配消息。
8. 一种链路删除装置， 包括：
检测模块， 设置为在业务处理流程中， 检测当前情况是否满足以下条件： 用户设备 UE处于宏分集状态，所述 UE对应的无线链路 RL中至少有一条重配 失败， 且至少有一条重配成功；
删除 RL指示模块， 设置为在所述检测模块的检测结果为是的情况下， 通 过所述业务处理流程中的空口消息指示所述 UE删除重配失败的 RL;
删除 RL通知模块， 设置为接收到所述 UE返回的所述业务处理流程完成 的响应消息后， 通知所述重配失败的 RL对应的基站删除所述重配失败的 RL。
9. 根据权利要求 8所述的装置， 其中，
所述删除 RL指示模块包括： 场景确定单元， 设置为确定当前场景为所述 UE处于高速分组接入 HSPA宏分集，且重配失败的 RL为 HSPA服务小区； RL 指示单元， 设置为通过所述空口消息携带变更服务小区为指定的 RL的指示； 其中， 所述指定的 RL为重配成功的 RL;
所述装置还包括： 小区变更通知模块， 设置为通知所述对应的基站变更所 述 UE的服务小区为所述指定的 RL所在的小区。
10. 根据权利要求 8或 9所述的装置， 其中， 所述删除 RL指示模块包括： 空口消 息选择单元， 设置为按照以下方式之一选择空口消息：
对于所述业务处理流程为业务建立流程， 所述空口消息为无线承载建立消 息；
对于所述业务处理流程为业务释放流程， 所述空口消息为无线承载释放消 息；
对于所述业务处理流程为业务重配流程， 所述空口消息为无线承载重配消 息；
对于所述业务处理流程为传输信道重配流程， 所述空口消息为传输信道重 配消息；
对于所述业务处理流程为物理信道重配流程， 所述空口消息为物理信道重 配消息。
11. 一种链路删除装置， 所述装置设置在用户设备 UE上， 包括：
消息接收模块， 设置为接收来自无线网络控制器 RNC的空口消息， 其中， 所述空口消息指示所述 UE删除重配失败的 RL;
RL 删除模块， 设置为根据所述消息接收模块接收的所述空口消息发起对 应的业务处理流程， 并删除所述重配失败的 RL;
响应返回模块， 设置为所述业务处理流程完成后， 向所述 RNC 返回响应 消息。
12. 根据权利要求 11所述的装置， 其中， 所述装置还包括：
小区变更模块， 设置为当所述 UE装置处于 HSPA宏分集， 且所述空口消 息携带有变更服务小区为指定的 RL时， 变更服务小区为所述指定的 RL所在 的小区。
3. 一种链路删除系统， 包括： 无线网络控制器 RNC和用户设备 UE， 其中， 所述 RNC包括权利要求 8至 10任一项中所述的链路删除装置， 所述 UE包括权利 要求 11或 12中所述的链路删除装置。
PCT/CN2012/076612 2011-12-22 2012-06-07 链路删除方法、装置和系统 WO2013091355A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110434627.4 2011-12-22
CN201110434627.4A CN103179687B (zh) 2011-12-22 2011-12-22 链路删除方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2013091355A1 true WO2013091355A1 (zh) 2013-06-27

Family

ID=48639237

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/076612 WO2013091355A1 (zh) 2011-12-22 2012-06-07 链路删除方法、装置和系统

Country Status (2)

Country Link
CN (1) CN103179687B (zh)
WO (1) WO2013091355A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110611620A (zh) * 2019-09-29 2019-12-24 新华三信息安全技术有限公司 一种链路更新方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108112042B (zh) * 2016-11-25 2021-05-25 中兴通讯股份有限公司 一种保持服务rl的方法、装置及系统
WO2019157741A1 (zh) * 2018-02-14 2019-08-22 华为技术有限公司 一种频域资源的分配方法及装置
KR20200049493A (ko) 2018-10-26 2020-05-08 주식회사 케이티 차량 통신을 수행하는 방법 및 그 장치
WO2021062669A1 (zh) * 2019-09-30 2021-04-08 华为技术有限公司 一种通信方法及通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1610421A (zh) * 2003-10-21 2005-04-27 华为技术有限公司 一种删除无线链路的方法
EP1631099A1 (en) * 2004-08-27 2006-03-01 Siemens Mobile Communications S.p.A. Method to decentralize the counting of abnormal call release events on a per cell base in digital cellular communication networks
WO2007023365A1 (en) * 2005-08-23 2007-03-01 Nokia Corporation Improvement of the iub/iur hsdpa/hsupa mobility procedures

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1949916B (zh) * 2005-10-14 2010-06-23 中兴通讯股份有限公司 一种第三代移动通信系统中克服软切换掉话的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1610421A (zh) * 2003-10-21 2005-04-27 华为技术有限公司 一种删除无线链路的方法
EP1631099A1 (en) * 2004-08-27 2006-03-01 Siemens Mobile Communications S.p.A. Method to decentralize the counting of abnormal call release events on a per cell base in digital cellular communication networks
WO2007023365A1 (en) * 2005-08-23 2007-03-01 Nokia Corporation Improvement of the iub/iur hsdpa/hsupa mobility procedures

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110611620A (zh) * 2019-09-29 2019-12-24 新华三信息安全技术有限公司 一种链路更新方法及装置

Also Published As

Publication number Publication date
CN103179687B (zh) 2018-05-11
CN103179687A (zh) 2013-06-26

Similar Documents

Publication Publication Date Title
TWI535326B (zh) 在雙連結中建立無線電承載的方法
CN104581810B (zh) 一种基于载波聚合的切换方法、板间聚合切换方法和装置
WO2018228480A1 (zh) 通信方法及接入网设备、核心网设备
US9906994B2 (en) Handover method, master base station and slave base station
CN112400358B (zh) Gnb-cu-up处的完整性保护处理
US11412563B2 (en) Multi-connectivity communication method and device
CN102598786B (zh) 基站间的切换方法、基站、和通讯系统
US11330489B2 (en) Apparatus, method and computer program
WO2015039449A1 (zh) 一种小小区切换方法、基站和计算机存储介质
TW201635848A (zh) 雙連結模式下無線承載傳輸的方法
JP5826245B2 (ja) ハンドオーバ時における無線リソース設定方法及び設定装置
US20160157155A1 (en) Selective Bearer Splitting in Cell System
WO2016061785A1 (zh) 无线资源控制rrc连接方法、重连接方法和装置
WO2016061789A1 (zh) 无线资源控制rrc消息处理方法、装置和系统
WO2014173184A1 (zh) 终端多连接的管理方法、装置和系统
CN111345074B (zh) 与ue非活动有关的方法、装置和系统
WO2012130046A1 (zh) 业务承载迁移方法及装置
JP2014096664A (ja) 無線通信システムおよび通信制御方法
CN105025465B (zh) 用户终端位置上报方法、基站、移动管理实体及系统
WO2022067818A1 (zh) 一种数据传输方法及装置
WO2010075717A1 (zh) 用户上下行不同步切换的方法和装置
WO2013091355A1 (zh) 链路删除方法、装置和系统
WO2012152130A1 (zh) 承载处理方法及装置
WO2016061791A1 (zh) 接口建立方法及装置
TWI695607B (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: 12860906

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

Country of ref document: EP

Kind code of ref document: A1