WO2013102374A1 - 用户设备在无线网络控制器之间迁移的方法、装置及系统 - Google Patents

用户设备在无线网络控制器之间迁移的方法、装置及系统 Download PDF

Info

Publication number
WO2013102374A1
WO2013102374A1 PCT/CN2012/084637 CN2012084637W WO2013102374A1 WO 2013102374 A1 WO2013102374 A1 WO 2013102374A1 CN 2012084637 W CN2012084637 W CN 2012084637W WO 2013102374 A1 WO2013102374 A1 WO 2013102374A1
Authority
WO
WIPO (PCT)
Prior art keywords
rnc
coding type
source
migration
target
Prior art date
Application number
PCT/CN2012/084637
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 EP12864468.9A priority Critical patent/EP2793509A4/en
Publication of WO2013102374A1 publication Critical patent/WO2013102374A1/zh
Priority to US14/324,946 priority patent/US9167490B2/en
Priority to US14/853,637 priority patent/US9392507B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, device, and system for migrating user equipment between wireless network controllers. Background technique
  • a User Equipment In a Universal Mobile Telecommunications System (UMTS), a User Equipment (UE) establishes a Radio Bearer (RB), RNC through an access node and a Radio Network Controller (RNC).
  • RNC Radio Network Controller
  • a radio access bearer (RAB) is established with the core network (Core Network) to establish a radio link between the UE and the CN to implement the circuit domain service of the UE.
  • the RNC After establishing the radio link of the UE to the CN via the RNC, the RNC will migrate the UEs that are performing circuit domain services to other RNCs according to the power load conditions of the access network and/or the core network.
  • the source and the RNC support the type of the voice coding that is supported by the source RNC and the source RNC.
  • the UE needs to synchronize the coding type between the UE and the target RNC in the process of migrating from the source RNC to the target RNC, even if the coding type of the UE and the target RNC are consistent.
  • the technology of the existing UEs to migrate between the RNCs is that the source RNC informs the target RNCs of the coding types configured by the UE and the source RNC through the CN, and the CN selects the UE according to the coding type configured by the UE and the coding type supported by the target RNC.
  • the coding type supported by the target RNC is used as the coding type used when the UE establishes an RB with the target RNC.
  • the target RNC reconfigures the coding type configured by the UE as The coding type is consistent with the coding type indicated by the CN for the target RNC, and then the RNC migration is performed on the UE.
  • the target RNC directly rejects the migration of the UE.
  • An embodiment of the present application provides a method, an apparatus, and a system for a user equipment to migrate between radio network controllers, which can ensure that when the coding type configured by the UE is inconsistent with the coding type configured by the CN, the UE can be successfully migrated to the target RNC. .
  • the present application provides a method for a user equipment to migrate between radio network controllers, including: receiving a radio network controller RNC migration request message that the user equipment UE does not participate in, where the request message carries an active RNC transmission.
  • the source RNC to the transparent container of the target RNC and the coding type indicated by the core network CN, the transparent container includes the coding type configured by the UE; if the coding type configured by the UE is inconsistent with the coding type indicated by the CN,
  • the source RNC sends a transparent container of the target RNC to the source RNC, the transparent container carrying the UE for modifying the UE Encoding type reconfiguration message, such that the source RNC sends a reconfiguration message to the UE.
  • the present application provides another method for migrating between user equipments in a radio network controller, including: transmitting, to a core network CN, a radio network controller RNC migration request message that the user equipment UE does not participate, so that the CN Sending a migration request message to the target RNC; receiving a migration command message sent by the CN, where the migration command message includes a transparent container of the target RNC to the source RNC sent by the target RNC, where the transparent container includes the UE code a type of reconfiguration message; sending a reconfiguration message to the UE, such that the UE changes the coding type according to the reconfiguration message.
  • the present application provides another method for migrating between user equipments in a radio network controller, including: when initiating a migration, if the radio link of the user equipment UE is under the control of the target radio network controller RNC, determining The source RNC does not know the coding type supported by the target RNC or determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC or determines that the UE has a broadband adaptive multi-rate bearer; initiates an RNC migration process in which the UE participates.
  • the present application provides another method for migrating between user equipments in a radio network controller, including: receiving an RNC migration request message that the user equipment UE does not participate in the source radio network controller RNC;
  • the configured coding type is inconsistent with the coding type supported by the target RNC, and sends a migration failure message to the source RNC, so that the source RNC initiates an RNC migration process in which the UE participates according to the migration failure message.
  • the present application provides another method for migrating between user equipments in a radio network controller, including: receiving a request message sent by a source radio network controller RNC; and transmitting, to the source RNC, a user equipment UE coding type The message is reconfigured so that the source RNC reconfigures the coding type of the UE; and receives an RNC migration request message that the UE does not participate in the RNC, so as to complete the RNC migration process that the UE does not participate in.
  • the present application provides another method for migrating between user equipments in a radio network controller, including: sending a request message to a core network CN; receiving a reconfiguration message sent by the CN; according to the reconfiguration message Re-allocating the coding type of the user equipment UE; Line network controller RNC migration process.
  • the present application provides a radio network controller RNC, including: a receiver, configured to receive an RNC migration request message that the user equipment UE does not participate in, where the request message carries the source RNC sent by the active RNC to the target.
  • a transparent container of the RNC and a coding type indicated by the core network CN the transparent container includes an encoding type configured by the UE, and a transmitter, configured to send a transparent container of the target RNC to the source RNC to the source RNC, the transparent container And carrying a reconfiguration message for modifying the UE coding type, so that the source RNC sends a reconfiguration message to the UE.
  • the present application further provides a radio network controller RNC, including: a transmitter, configured to send, to the core network CN, an RNC migration request message that the user equipment UE does not participate, so that the CN sends the target to the target RNC.
  • a migration request message the receiver, configured to receive a migration command message sent by the CN, where the migration command message includes a transparent container of the target RNC to the source RNC sent by the target RNC, where the transparent container includes a UE coding type Retransmitting message;
  • the transmitter is further configured to send a reconfiguration message to the UE, so that the UE changes an encoding type according to the reconfiguration message.
  • the application further provides a radio network controller RNC, including: a determiner, configured to determine that a source RNC does not know an encoding type supported by a target RNC or determine an encoding type of the UE configuration and the target RNC support The coding type is inconsistent or it is determined that the UE has a broadband adaptive multi-rate bearer; and the processor is configured to initiate an RNC migration process in which the UE participates.
  • a radio network controller RNC including: a determiner, configured to determine that a source RNC does not know an encoding type supported by a target RNC or determine an encoding type of the UE configuration and the target RNC support The coding type is inconsistent or it is determined that the UE has a broadband adaptive multi-rate bearer; and the processor is configured to initiate an RNC migration process in which the UE participates.
  • the present application further provides a core network CN, including: a receiver, configured to receive an RNC migration request message that is not used by the user equipment UE sent by the source radio network controller RNC, and a transmitter, configured to The source RNC sends a migration failure message, so that the source RNC initiates an RNC migration process in which the UE participates according to the migration failure message.
  • a core network CN including: a receiver, configured to receive an RNC migration request message that is not used by the user equipment UE sent by the source radio network controller RNC, and a transmitter, configured to The source RNC sends a migration failure message, so that the source RNC initiates an RNC migration process in which the UE participates according to the migration failure message.
  • the present application further provides a core network CN, including: a receiver, configured to receive a request message sent by a source radio network controller RNC; and a transmitter, configured to send a user equipment UE coding type to the source RNC The re-allocation message, so that the source RNC re-allocates the coding type of the UE; the receiver is further configured to receive the RNC migration that the UE sent by the source RNC does not participate in. The message is sought to complete the RNC migration process in which the UE does not participate.
  • a core network CN including: a receiver, configured to receive a request message sent by a source radio network controller RNC; and a transmitter, configured to send a user equipment UE coding type to the source RNC The re-allocation message, so that the source RNC re-allocates the coding type of the UE; the receiver is further configured to receive the RNC migration that the UE sent by the source RNC does not participate in. The message is sought to complete the RNC migration process in
  • the present application further provides a radio network controller RNC, including: a transmitter, configured to send a request message to a core network CN, a receiver, configured to receive a reconfiguration message sent by the CN, and a processor, And a method for re-provisioning the UE according to the reconfiguration message; the processor is further configured to initiate an RNC migration process in which the user equipment UE does not participate.
  • RNC radio network controller
  • the present application provides a system for migrating user equipment between radio network controllers, including: a target radio network controller RNC, configured to receive an RNC migration request message that the user equipment UE does not participate in, the request message And carrying the source RNC sent by the active RNC to the transparent container of the target RNC and the coding type indicated by the core network CN, where the transparent container includes the coding type configured by the UE, if the coding type configured by the UE and the CN indication Inconsistent coding type, sending a transparent container of the target RNC to the source RNC to the source RNC, the transparent container carrying a reconfiguration message for modifying the UE coding type, so that the source RNC sends a reconfiguration message to the a source RNC, configured to send, to the CN, an RNC migration request message that the UE does not participate, so that the CN sends a migration request message to the target RNC, and receives a migration command message sent by the CN, where the migration command message is sent Include
  • the present application further provides a system for migrating user equipment between radio network controllers, including: a source radio network controller RNC, when initiating a migration, if a radio link of the user equipment UE is at a target Under the control of the RNC, it is determined that the source RNC does not know the coding type supported by the target RNC or determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC or determines that the UE has a broadband adaptive multi-rate bearer, and initiates UE participation.
  • a source radio network controller RNC when initiating a migration, if a radio link of the user equipment UE is at a target Under the control of the RNC, it is determined that the source RNC does not know the coding type supported by the target RNC or determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC or determines that the UE has a broadband adaptive multi-rate bearer, and initiates UE participation.
  • the RNC migration process the core network CN is configured to receive an RNC migration request message that the UE does not participate in the source RNC, and if the coding type configured by the UE is different from the coding type supported by the target RNC, the migration fails to be sent to the source RNC. a message, so that the source RNC initiates an RNC migration process in which the UE participates according to the migration failure message.
  • the present application further provides a system for migrating user equipment between radio network controllers, including: a core network CN, receiving a request message sent by a source radio network controller RNC, and sending a user equipment to the source RNC.
  • a recoding message of the UE coding type so that the source RNC re-allocates the coding type of the UE, and receives an RNC migration request message that the UE does not participate in the RNC, so as to complete the RNC migration process that the UE does not participate in; And sending a request message to the CN, receiving a reconfiguration message sent by the CN, reconfiguring the coding type of the UE according to the reconfiguration message, and initiating an RNC migration process in which the UE does not participate.
  • the method, device, and system for migrating user equipment between the radio network controllers can be used to configure the coding type of the UE when the coding type configured by the UE is inconsistent with the coding type indicated by the CN and the target RNC.
  • the reconfiguration is an encoding type consistent with the coding type indicated by the CN for the UE and the target RNC, and then initiates an RNC migration procedure in which the UE does not participate.
  • the RNC migration process in which the UE participates is directly initiated, and the coding type configured by the UE is reconfigured to be the CN
  • the coding type of the coding type indicated by the UE and the target RNC when the radio link of the UE circuit domain service has been controlled by the target RNC, the RNC migration process in which the UE does not participate cannot reconfigure the UE coding type, and the coding type configured by the UE and the CN configuration can be ensured.
  • the coding types are inconsistent, the UE can migrate to the target RNC smoothly.
  • 1 is a flowchart of a method for migrating user equipments between radio network controllers in an embodiment of the present application
  • 2 is a flowchart of a method for migrating user equipments between radio network controllers according to another embodiment of the present application
  • FIG. 3 is a flowchart of a method for migrating user equipment between radio network controllers according to another embodiment of the present application
  • FIG. 4 is a schematic structural diagram of an RNC according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an RNC according to an embodiment of the present application.
  • FIG. 6 is a flowchart of a method for migrating user equipment between radio network controllers according to another embodiment of the present application.
  • FIG. 7 is a flowchart of a method for migrating user equipment between radio network controllers according to another embodiment of the present application.
  • FIG. 8 is a network interaction diagram of a RNC migration process in which a UE initiated by a source RNC in the embodiment of the present application;
  • FIG. 9 is a flowchart of a method for migrating user equipment between radio network controllers according to another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of an RNC according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an RNC according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of an MSC according to an embodiment of the present application.
  • FIG. 13 is a flowchart of a method for migrating user equipment between radio network controllers according to another embodiment of the present application.
  • 15 is a flowchart of a method for migrating user equipment between radio network controllers according to another embodiment of the present application.
  • 16 is a schematic structural diagram of an MSC according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of an RNC according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of an RNC according to an embodiment of the present application. detailed description
  • the Mobile Switching Center (MSC) in the CN is used as the executive body in the CN to describe the embodiment of the present application.
  • the CN may be used as the execution entity of the embodiment of the present application.
  • the element device is not limited to the MSC, and the embodiment of the present application does not limit the embodiment.
  • the embodiment of the present application provides a method for migrating user equipments between radio network controllers, as shown in FIG. 1.
  • the target RNC receives an RNC migration request message that the UE does not participate in.
  • the request message carries the source RNC sent by the active RNC to the transparent container of the target RNC and the coding type indicated by the MSC, and the transparent container includes the coding type configured by the UE.
  • the target RNC sends the target RNC to the transparent container of the source RNC to the source RNC.
  • the target RNC carries a reconfiguration message for changing the UE coding type in the transparent container of the source RNC, so that the source RNC sends a reconfiguration message to the UE.
  • the target RNC receives the reconfiguration complete message.
  • the reconfiguration complete message is sent by the UE to the target RNC or sent by the UE to the source RNC. If the UE sends a reconfiguration complete message to the source RNC, the source RNC notifies the target RNC to complete the reconfiguration.
  • the target RNC receives the reconfiguration complete message, completes reconfiguration of the UE coding type, and migrates to the UE.
  • the method for migrating user equipment between wireless network controllers can When the coding type configured by the UE is inconsistent with the coding type indicated by the MSC, the coding type configured by the UE is reconfigured to be indicated by the MSC by carrying the coding type re-allocated for the UE in the transparent container of the target RNC to the source RNC.
  • the encoding type with the same encoding type.
  • the UE migration failure caused by the RNC migration process in which the UE participates cannot be initiated, and the UE is successfully migrated to the target RNC.
  • the embodiment of the present application provides another method for migrating user equipments between radio network controllers. As shown in FIG. 2, the method is a further extension of the embodiment shown in FIG. 1.
  • the target RNC receives the RNC migration request message that the UE sent by the RNC does not participate in.
  • the migration request message carries a transparent RNC to the transparent container of the target RNC, and the non-access stratum synchronization indication in the transparent container of the source RNC to the target RNC carries the coding type configured by the UE.
  • the target RNC sends the target RNC to the transparent container of the source RNC to the source RNC.
  • the non-access stratum synchronization indication in the transparent container of the target RNC to the source RNC carries the coding type indicated by the MSC, and the source RNC reconfigures the coding type configured by the UE according to the coding type.
  • the coding type configured by the UE is a Wideband Adaptive Multi-Rate (WB AMR), and the coding type indicated by the MSC for the UE and the target RNC is a narrowband adaptive multi-rate ( Narrow Adaptive Multi-Rate, ⁇ AMR ), you need to reconfigure the encoding type configured by the UE.
  • the target RNC carries the coding type (NB AMR) indicated by the MSC to the UE and the target RNC in the transparent container of the target RNC to the source RNC, indicating that the source RNC reconfigures the coding type configured by the UE as the NB AMR.
  • the target RNC sends a migration detection message to the MSC.
  • the target RNC After receiving the migration execution trigger, the target RNC sends a migration detection message to the MSC, the target RNC starts the SRNC operation, and the MSC switches the user plane from the source RNC to the target RNC.
  • the migration execution touch The transmission may be an receipt of a reconfiguration complete message from the air interface or an indication received from an interface between the source RNC and the target RNC.
  • the target RNC receives the reconfiguration complete message.
  • the reconfiguration complete message is sent by the UE to the target RNC or sent by the UE to the source RNC. If the UE sends a reconfiguration complete message to the source RNC, the source RNC notifies the target RNC to complete the reconfiguration.
  • the target RNC sends a migration message to the MSC.
  • the method for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can be carried as a UE in a transparent container of the target RNC to the source RNC when the coding type configured by the UE is inconsistent with the coding type indicated by the MSC.
  • the coding type of the UE reconfigures the coding type configured by the UE to the coding type consistent with the coding type indicated by the MSC.
  • the UE migration failure caused by the RNC migration process in which the UE participates cannot be initiated, and the UE is successfully migrated to the target RNC.
  • the method for migrating the user equipment between the radio network controllers in the embodiment of the present application can also directly migrate the UE to the target RNC after re-allocating the coding type for the UE, thereby saving the prior art in reconfiguring the UE.
  • the source RNC After the coding type, the source RNC also needs to initiate the RNC migration process that the UE does not participate in, which saves the signaling overhead of the network.
  • the embodiment of the present application provides a method for migrating user equipments between radio network controllers, as shown in FIG. 3.
  • the source RNC sends an RNC migration request message that the UE does not participate to the MSC, so that the MSC sends a migration request message to the target RNC.
  • the migration request message is used to migrate the UE from the source RNC to the target RNC.
  • step 302 is performed to reconfigure the coding type configured by the UE.
  • the source RNC receives the migration command message sent by the MSC.
  • the migration command message includes a transparent container of the target RNC sent by the target RNC to the source RNC, where the transparent container includes a reconfiguration message of the UE coding type.
  • the transparent container includes a reconfiguration message of the UE coding type.
  • the reconfiguration message carries the NB AMR, and the source RNC adds the coding type of the UE according to the reconfiguration message. It is equipped with NB AMR.
  • the source RNC sends a reconfiguration message to the UE, so that the UE changes the coding type according to the reconfiguration message and sends a reconfiguration complete message to the target RNC or the source RNC.
  • the UE After the UE changes the WB AMR to the NB AMR according to the reconfiguration message sent by the source RNC, the UE sends a reconfiguration complete message to the target RNC or the source RNC, indicating that the coding type reconfiguration of the UE configuration is completed. If the source RNC receives the reconfiguration complete message, the source RNC notifies the target RNC to complete the reconfiguration.
  • the method for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can be carried as a UE in a transparent container of the target RNC to the source RNC when the coding type configured by the UE is inconsistent with the coding type indicated by the MSC.
  • the coding type of the UE reconfigures the coding type configured by the UE to the coding type consistent with the coding type indicated by the MSC.
  • the UE migration failure caused by the RNC migration process in which the UE participates cannot be initiated, and the UE is successfully migrated to the target RNC.
  • an embodiment of the present application provides an RNC, as shown in FIG. 4, to implement the method embodiment shown in FIG. 2.
  • the RNC includes: a receiver 41 and a transmitter 42.
  • the receiver 41 is configured to receive an RNC migration request message that the UE does not participate in, where the request message carries a source RNC sent by the active RNC to a transparent container of the target RNC and an encoding type indicated by the MSC, where the transparent container includes a code configured by the UE. Types of.
  • the migration request message carries the transparent RNC of the active RNC to the target RNC, and the non-access stratum synchronization indication in the transparent container of the source RNC to the target RNC carries the coding type configured by the UE.
  • the transmitter 42 is configured to send, to the source RNC, a transparent container of the target RNC to the source RNC, where the transparent container carries a reconfiguration message for changing the UE coding type, so that the source RNC sends a reconfiguration message to the UE.
  • the non-access stratum synchronization indication in the transparent container of the target RNC to the source RNC carries the coding type indicated by the MSC, and the source RNC reconfigures the coding type configured by the UE according to the coding type.
  • the coding type configured by the UE is WB AMR
  • the MSC indicates that the coding type indicated by the UE and the target RNC is NB AMR.
  • the coding type configured by the UE needs to be reconfigured.
  • the target RNC carries the coding type (NB AMR) indicated by the MSC to the UE and the target RNC in the transparent container of the target RNC to the source RNC, indicating that the source RNC reconfigures the coding type configured by the UE to the NB AMR.
  • the receiver 41 is further configured to receive a reconfiguration complete message sent by the UE.
  • the receiver 41 After the coding type configured by the UE is reconfigured as the NB AMR, the receiver 41 receives the reconfiguration complete message sent by the UE, indicating that the reconfiguration of the UE coding type is completed.
  • the RNC provided by the embodiment of the present application can encode the UE by carrying the coding type re-allocated for the UE in the transparent container of the target RNC to the source RNC when the coding type configured by the UE is different from the coding type indicated by the MSC.
  • the type reconfiguration is an encoding type that is consistent with the encoding type indicated by the MSC.
  • the RNC provided by the embodiment of the present application can also directly migrate the UE to the target RNC after re-allocating the coding type for the UE, which saves the prior art that the UE needs to be initiated by the source RNC after reconfiguring the UE coding type.
  • the steps of the participating RNC migration process save the signaling overhead of the network.
  • an embodiment of the present application provides an RNC, as shown in FIG. 5, to implement the method embodiment shown in FIG.
  • the RNC includes: a transmitter 51 And receiver 52.
  • the transmitter 51 is configured to send, to the MSC, an RNC migration request message that the UE does not participate, so that the CN sends a migration request message to the target RNC.
  • the migration request message is used to migrate the UE from the source RNC to the target RNC.
  • the coding type configured by the UE is inconsistent with the coding type indicated by the MSC, the coding type configured by the UE is reconfigured.
  • the receiver 52 is configured to receive a migration command message sent by the MSC.
  • the migration command message includes a transparent container that is sent by the target RNC to the source RNC, and the transparent container includes a re-matching message of the UE coding type.
  • the transparent container includes a re-matching message of the UE coding type.
  • the coding type of the UE is WB AMR
  • the coding type indicated by the MSC for the UE and the target RNC is NB AMR
  • the reconfiguration message carries the NB AMR
  • the source RNC adds the coding type of the UE according to the reconfiguration message. It is equipped with NB AMR.
  • the transmitter 51 is further configured to send a reconfiguration message to the UE, so that the UE changes the coding type according to the reconfiguration message.
  • the UE After the UE changes the WB AMR to the NB AMR according to the reconfiguration message sent by the source RNC, the UE sends a reconfiguration complete message to the target RNC, indicating that the coding type reconfiguration of the UE configuration is completed.
  • the RNC provided by the embodiment of the present application can encode the UE by carrying the coding type re-allocated for the UE in the transparent container of the target RNC to the source RNC when the coding type configured by the UE is different from the coding type indicated by the MSC.
  • the type reconfiguration is an encoding type that is consistent with the encoding type indicated by the MSC.
  • the embodiment of the present application provides a system for migrating user equipment between radio network controllers, and the system covers implementations of the method and apparatus embodiments shown in FIG. 1 to FIG.
  • the system includes: a target RNC and a source RNC.
  • a target RNC configured to receive an RNC migration request message that the UE does not participate in, in the request message And carrying the source RNC sent by the active RNC to the transparent container of the target RNC and the coding type indicated by the MSC, where the transparent container includes the coding type configured by the UE, and if the coding type configured by the UE is inconsistent with the coding type indicated by the MSC, the target is sent to the source RNC.
  • a transparent container of the RNC to the source RNC the transparent container carrying a reconfiguration message for changing the UE coding type, so that the source RNC sends a reconfiguration message to the UE.
  • the source RNC is configured to send, to the MSC, an RNC migration request message that the UE does not participate in, so that the MSC sends a migration request message to the target RNC, and receives a migration command message sent by the MSC, where the migration command message includes the target RNC sent by the target RNC to the source RNC.
  • a transparent container containing a re-matching message of the UE coding type, and sending a reconfiguration message to the UE, so that the UE changes the coding type according to the reconfiguration message.
  • the system for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can be carried as a UE in a transparent container of the target RNC to the source RNC when the coding type configured by the UE is inconsistent with the coding type indicated by the MSC.
  • the coding type of the UE reconfigures the coding type configured by the UE to the coding type consistent with the coding type indicated by the MSC.
  • the UE migration failure caused by the RNC migration process in which the UE participates cannot be initiated, and the UE is successfully migrated to the target RNC.
  • the system for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can also directly migrate the UE to the target RNC after reconfiguring the coding type for the UE, saving the prior art in reconfiguring the UE.
  • the source RNC After the coding type, the source RNC also needs to initiate the RNC migration process that the UE does not participate in, which saves the signaling overhead of the network.
  • the embodiment of the present application provides a method for migrating user equipment between radio network controllers, as shown in FIG. 6.
  • the source RNC determines that the source RNC does not know the coding type supported by the target RNC or determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC or determines the location. Broadband adaptive multi-rate Hosted.
  • the source RNC initiates an RNC migration process in which the UE participates.
  • the source RNC reconfigures the coding type of the UE into an encoding type consistent with the encoding type supported by the target RNC in the RNC migration process in which the UE participates.
  • the source RNC when the radio link of the UE is under the control of the target RNC, the source RNC cannot initiate the RNC migration process in which the UE participates. If the coding type configured by the UE is inconsistent with the coding type supported by the target RNC, the source RNC cannot reconfigure the coding type configured by the UE during the RNC migration process in which the UE participates, and can only reject the migration of the UE.
  • the method for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can initiate the RNC migration process in which the UE participates when the radio link of the UE is under the control of the target RNC, in the RNC migration process in which the UE participates.
  • Recoding the coding type configured by the UE to the coding type consistent with the coding type supported by the target RNC ensures that the UE successfully migrates to the target RNC.
  • the embodiment of the present application provides another method for migrating user equipments between radio network controllers. As shown in FIG. 7, the method is a further extension to the embodiment shown in FIG. 6.
  • the source RNC determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC.
  • the implementation manner of determining that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC includes the following two methods.
  • the source RNC determines that the coding type configured by the UE does not match the coding type supported by the target RNC.
  • the source RNC receives the migration failure message sent by the MSC, and after receiving the migration failure message, the source RNC learns that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC.
  • the source RNC determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC, the source RNC also receives the coding type supported by the target RNC sent by the network management system or the target RNC, so that the source is used.
  • the RNC can compare the coding type configured by the UE with the coding type supported by the target RNC, and determine the coding type and destination of the UE configuration.
  • the encoding types supported by the standard RNC are inconsistent.
  • the source RNC may determine, by one of the foregoing two determining manners, that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC, and the source RNC determines the coding type configured by the UE and the target RNC.
  • step 703 is performed.
  • the source RNC determines that the coding type configured by the UE is an adaptive coding type, and does not know the coding type supported by the target RNC.
  • step 703 is performed.
  • WB AMR Wideband Adaptive Multi-Rate
  • the MSC indicates the coding type for the UE and the target RNC according to the coding type supported by the UE and the coding type supported by the target RNC.
  • the MSC will normally indicate the type of encoding supported by the target RNC.
  • the coding type configured by the UE is WB AMR and the target RNC only supports Narrow Adaptive Multi-Rate (NB AMR)
  • NB AMR Narrow Adaptive Multi-Rate
  • step 203 is performed to reconfigure the coding type configured by the UE from the WB AMR to the NB AMR, so that the coding type configured by the UE is consistent with the coding type of the target RNC.
  • the source RNC initiates an RNC migration process in which the UE participates.
  • the coding type configured by the UE is reconfigured in the RNC migration process in which the UE participates, and the migration process of the UE is completed.
  • the RNC migration process in which the source RNC initiates UE participation mainly includes the following steps.
  • the source RNC sends a Relocation Required message to the MSC.
  • the Relocation Type is set to UE involved in relocation of SRNS (the UE participates in the RNC migration process;). Indicates that the migration process initiated by the source RNC is the RNC migration process in which the UE participates.
  • Non-access stratum synchronization indication of the source RNC in the transparent container from the source RNC to the target RNC Indicates the encoding type of the UE configuration.
  • the MSC sends a Relocation Request message to the target RNC.
  • the MSC indicates the coding type for the UE and the target RNC according to the coding type supported by the target RNC and the coding type supported by the UE, and notifies the target RNC of the indicated coding type in the non-access stratum synchronization indication.
  • the target RNC checks whether the coding type configured by the UE and the coding type indicated by the MSC are consistent.
  • the target RNC does not support this encoding type, place the encoding type supported by itself in the target RNC to the source RNC transparent container.
  • the target RNC sends the target RNC to the source RNC transparent container to the MSC through a Relocation Request Ack message.
  • the MSC sends a Relocation Command message to the source RNC. This command carries the target RNC to the source RNC transparent container.
  • the source RNC sends a reconfiguration message to the UE according to the configuration in the target RNC to the source RNC transparent container, indicating that the UE reconfigures the coding type.
  • the target RNC sends a Relocation Detect message to the MSC.
  • the MSC switches the user plane from the source RNC to the target RNC.
  • the target RNC After receiving the reconfiguration complete message, the target RNC sends a Relocation Complete message to the MSC to complete the coding type reconfiguration and migration configured by the UE.
  • the source RNC After receiving the reconfiguration complete message, the source RNC notifies the target RNC to complete the coding type reconfiguration, and the target RNC sends a Relocation Complete message to the MSC to complete the coding type reconfiguration and migration configured for the UE.
  • the source RNC reconfigures the coding type configured by the UE to the coding type supported by the target RNC.
  • the method for migrating user equipment between radio network controllers can initiate the RNC migration of the UE when the radio link of the UE is under the control of the target RNC.
  • the coding type configured by the UE is reconfigured to be the coding type of the coding type supported by the target RNC.
  • the source RNC cannot initiate the UE migration failure caused by the RNC migration process in which the UE participates, and the UE is successfully migrated to the target RNC.
  • the method for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can also perform UE participation when the UE uses the WB AMR, regardless of whether the coding type configured by the UE is consistent with the coding type supported by the target RNC.
  • the RNC migration process reconfigures the coding type configured by the UE to the coding type supported by the target RNC, and saves the step of determining whether the UE and the target RNC coding type are consistent.
  • the embodiment of the present application provides a method for migrating user equipment between radio network controllers, as shown in FIG. 9.
  • the MSC receives an RNC migration request message that the UE sent by the source RNC does not participate in. Move to the target RNC.
  • the MSC sends a migration failure message to the source RNC.
  • the migration failure message carries an indication information, such as an RNC migration process indicating that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC or indicating that the source RNC initiates UE participation.
  • the source RNC initiates the RNC migration process in which the UE participates according to the migration failure message.
  • the migration of the step 401 fails.
  • the source RNC needs to initiate the RNC migration process in which the UE participates according to the migration failure message sent by the MSC, and configure the coding of the UE in the migration process.
  • Type reconfiguration is the type of encoding supported by the target RNC.
  • the method for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can initiate the RNC migration process in which the UE participates when the radio link of the UE is under the control of the target RNC, in the RNC migration process in which the UE participates.
  • Reconfigure the coding type configured by the UE as the target RNC The supported coding types of the coding type ensure the smooth migration of the UE to the target RNC.
  • the embodiment of the present application provides an RNC, as shown in FIG. 10, to implement the method embodiment shown in FIG.
  • the RNC includes a determiner 1001 and a processor 1002.
  • the determiner 1001 is configured to determine that the source RNC does not know the coding type supported by the target RNC or determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC.
  • the processor 1002 is configured to initiate an RNC migration process in which the UE participates.
  • the RNC may include: a transmitter 1101, configured to send an RNC handover request message that the UE does not participate to the MSC, and a receiver 1102, configured to receive a migration failure message sent by the MSC.
  • the migration failure message is used to indicate that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC.
  • the receiver 1102 is further configured to receive a coding type supported by the target RNC sent by the network management node or the target RNC.
  • the receiver 1102 further receives the coding type supported by the target RNC sent by the node such as the network management or the target RNC.
  • the determiner 1001 may compare the coding type configured by the UE with the coding type supported by the target RNC, and determine that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC.
  • the RNC provided by the embodiment of the present application can initiate the RNC migration process in which the UE participates when the radio link of the UE is under the control of the target RNC, and reconfigure the coding type configured by the UE as the target RNC in the RNC migration process in which the UE participates. Supported encoding types with consistent encoding types.
  • the UE migration failure caused by the RNC migration process in which the UE participates cannot be initiated, and the UE is successfully migrated to the target RNC.
  • the RNC provided by the embodiment of the present application can also be used when the UE uses the WB AMR. Whether the coding type of the UE is consistent with the coding type supported by the target RNC, the RNC migration process in which the UE participates is performed, and the coding type configured by the UE is reconfigured to the coding type supported by the target RNC, which saves the judgment of the UE and the target RNC coding type. Whether the steps are consistent.
  • the embodiment of the present application provides an MSC, as shown in FIG. 12, to implement the method embodiment shown in FIG.
  • the MSC includes a receiver 1201 and a transmitter 1202.
  • the receiver 1201 is configured to receive an RNC migration request message that the UE sent by the source RNC does not participate in. Move to the target RNC.
  • the sender 1202 is configured to send a migration failure message to the source RNC.
  • the source RNC initiates the RNC migration process in which the UE participates according to the migration failure message.
  • the source RNC needs to initiate the RNC migration process in which the UE participates according to the migration failure message sent by the MSC, and reconfigure the coding type configured by the UE as the target in the migration process.
  • the type of encoding supported by RNC is inconsistent with the coding type supported by the target RNC.
  • the MSC provided by the embodiment of the present application can initiate the RNC migration process in which the UE participates when the radio link of the UE is under the control of the target RNC, and reconfigure the coding type configured by the UE as the target RNC in the RNC migration process in which the UE participates.
  • the supported coding types of the coding type ensure the smooth migration of the UE to the target RNC.
  • the embodiment of the present application provides a system for migrating user equipment between radio network controllers, and the system covers implementations of the method and apparatus embodiments described in FIG. 6 to FIG.
  • the system includes: a source RNC and an MSC.
  • the source RNC is used to initiate the migration, if the radio link of the UE is under the control of the target RNC, determine that the source RNC does not know the coding type supported by the target RNC or determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC, and initiates The RNC migration process in which the UE participates.
  • the MSC is configured to receive, by the source RNC, an RNC migration request message that the UE does not participate in, if The coding type configured by the UE is inconsistent with the coding type supported by the target RNC, and the migration failure message is sent to the source RNC, so that the source RNC initiates the RNC migration process in which the UE participates according to the migration failure message.
  • the system for the user equipment UE to be migrated between the radio network controllers RNC can initiate the RNC migration process in which the UE participates when the radio link of the UE is under the control of the target RNC, and the RNC migration involved in the UE
  • the coding type configured by the UE is reconfigured to the coding type of the coding type supported by the target RNC.
  • the UE migration failure caused by the RNC migration process in which the UE participates cannot be initiated, and the UE is successfully migrated to the target RNC.
  • the system for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can also perform UE participation when the UE uses the WB AMR, regardless of whether the coding type configured by the UE is consistent with the coding type supported by the target RNC.
  • the RNC migration process reconfigures the coding type configured by the UE to the coding type supported by the target RNC, and saves the step of determining whether the UE and the target RNC coding type are consistent.
  • the embodiment of the present application provides a method for migrating user equipments between radio network controllers, as shown in FIG.
  • the MSC receives the request message sent by the source RNC.
  • the MSC sends a re-matching message of the UE coding type to the source RNC.
  • the MSC sends a reconfiguration message of the UE coding type to the source RNC, and is used to reconfigure the coding type configured by the UE.
  • the MSC receives an RNC migration request message that is not used by the UE sent by the source RNC, so as to complete the RNC migration process that the UE does not participate in.
  • the UE changes the coding type according to the reconfiguration message.
  • the source RNC completes the coding type change, the source RNC initiates an RNC migration process in which the UE does not participate, thereby completing the migration to the UE.
  • the method for migrating between user equipments of the radio network controller can be performed to the source RNC when the coding type configured by the UE is different from the coding type supported by the target RNC.
  • the reconfiguration message is sent, and the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message, and then initiates an RNC migration process in which the UE does not participate to migrate the UE from the source RNC to the target RNC.
  • the problem that the UE migration fails due to the inconsistency between the coding type of the UE configuration and the coding type indicated by the MSC in the prior art is solved, and the UE can be smoothly migrated to the target RNC.
  • the embodiment of the present application provides another method for migrating user equipments between radio network controllers. As shown in FIG. 14, the method is a further extension of the embodiment shown in FIG.
  • the MSC receives an encoding type change request message sent by the source RNC.
  • the source RNC determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC, the source RNC sends an encoding type change request message to the MSC for reconfiguring the coding type configured by the UE. .
  • the coding type change request message carries the coding type to be configured by the designated UE.
  • the network management or the target RNC needs to send the coding type supported by the target RNC to the source RNC, so that the source RNC can determine the coding type configured by the UE and the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC. Is the encoding type consistent?
  • the source RNC when the coding type of the UE is WB AMR and the coding type supported by the target RNC is NB AMR, the source RNC sends an encoding type change request message to the MSC, where the message carries the specific indication UE. After receiving the coding type change request message sent by the source RNC, the MSC performs step 1403 to notify the source RNC to reconfigure the coding type configured by the UE as NB AMR according to the coding type change request message. .
  • the MSC receives an RNC migration request message that the UE sent by the source RNC does not participate in. If the coding type configured by the UE is different from the coding type supported by the target RNC, step 1403 is performed to reconfigure the coding type configured by the UE.
  • the MSC sends a reconfiguration message of the UE coding type to the source RNC.
  • the UE changes the coding type according to the reconfiguration message, and the source RNC completes the coding type at the UE. After the change, the RNC migration process in which the UE does not participate is initiated, and the migration process to the UE is completed.
  • the MSC may first send a migration failure message to the source RNC, indicating that the source RNC waits to receive the recoding message of the UE coding type or the coding type configured by the UE and the coding type supported by the target RNC.
  • the reconfiguration message is sent from the source type RNC in step 1401, and the code type change request message carries the specified UE.
  • the encoding type (such as NB AMR in step 1401).
  • the MSC carries the coding type used by the specified UE in the reconfiguration message and sends it to the source RNC.
  • the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message.
  • the MSC determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC, and then carries the coding type used by the specified UE (such as NB AMR) in the reconfiguration message. Sent to the source RNC.
  • the MSC receives an RNC migration request message that is not used by the UE that is sent by the source RNC, so as to complete the RNC migration process that the UE does not participate in.
  • the source RNC After receiving the reconfiguration message sent by the MSC, the source RNC reconfigures the coding type configured by the UE, and then initiates an RNC migration process in which the UE does not participate.
  • the recombination process of the UE is consistent with the coding type supported by the target RNC. Therefore, the RNC migration process initiated by the source RNC cannot migrate the UE to the target RNC.
  • the method for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can send a reconfiguration message to the source RNC when the coding type configured by the UE is different from the coding type supported by the target RNC, and the source RNC according to the reconfiguration
  • the message reconfigures the coding type configured by the UE, and then initiates an RNC migration process in which the UE does not participate to migrate the UE from the source RNC to the target RNC.
  • the problem that the UE migration fails due to the inconsistency between the coding type configured by the UE and the coding type supported by the target RNC in the prior art is solved, and the UE can be smoothly migrated to the target RNC.
  • the embodiment of the present application provides a method for migrating user equipments between radio network controllers, as shown in FIG. 1501.
  • the source RNC sends a request message to the MSC.
  • the request message includes an encoding type change request message or an RNC migration request message that the UE does not participate in.
  • the source RNC determines that the coding type configured by the UE does not match the coding type supported by the target RNC, it sends an encoding type change request message to the MSC, where the coding type change request message carries the coding type used by the UE.
  • the source RNC needs to receive the coding type supported by the target RNC sent by the node RNC such as the network management system or the target RNC, and the source RNC determines the coding type and target configured by the UE according to the coding type configured by the UE and the coding type supported by the target RNC. Whether the encoding types supported by RNC are consistent.
  • the source RNC receives the reconfiguration message sent by the MSC.
  • the reconfiguration message is used to change the coding type configured by the UE.
  • the re-matching message has two triggering sources: 1) The re-matching message is sent from the encoding type change request message sent by the source RNC in step 1501, where the encoding type change request message carries the encoding type used by the specified UE.
  • the MSC sends the code type used by the UE to the source RNC, and the source RNC reconfigures the code type configured by the UE according to the reconfiguration message.
  • the MSC determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC, and then carries the coding type used by the specified UE to the source RNC in the reconfiguration message.
  • the source RNC may first receive a migration failure message indicating that the source RNC is waiting to receive the UE coding type reconfiguration message or the UE configured coding type is inconsistent with the target RNC supported coding type.
  • the source RNC re-allocates the coding type of the UE according to the reconfiguration message.
  • the source RNC initiates an RNC migration process in which the UE does not participate.
  • the source RNC After the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message sent by the MSC, the source RNC initiates an RNC migration process in which the UE does not participate, and completes the RNC migration to the UE. Since the source RNC reconfigures the coding type of the UE configuration according to the reconfiguration message to the coding class supported by the target RNC. The type of the coding is consistent. Therefore, in the RNC migration process in which the original NRC initiates the UE does not participate, the UE fails to migrate due to the coding type of the UE and the coding type supported by the target RNC. The UE can be successfully migrated to the target RNC. .
  • the method for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can send a reconfiguration message to the source RNC when the coding type configured by the UE is different from the coding type supported by the target RNC, and the source RNC according to the reconfiguration
  • the message reconfigures the coding type configured by the UE, and then initiates an RNC migration process in which the UE does not participate to migrate the UE from the source RNC to the target RNC.
  • the problem that the UE migration fails due to the inconsistency between the coding type configured by the UE and the coding type supported by the target RNC in the prior art is solved, and the UE can be smoothly migrated to the target RNC.
  • an embodiment of the present application provides an MSC, as shown in FIG. 16, to implement the method embodiment shown in FIG.
  • the MSC includes: a receiver 1601, configured to receive a request message sent by the source RNC, and a sender 1602, configured to send, to the source RNC, a reconfiguration message of a UE coding type.
  • the UE changes the coding type according to the reconfiguration message, and after the UE completes the coding type change, the source RNC initiates an RNC migration process that the UE does not participate in, and completes the migration process to the UE.
  • the re-configuration message described in this step has two trigger sources: 1) The re-configuration message is sent from the source type RNC, and the code type change request message carries the code used by the specified UE. Types of.
  • the transmitter 1602 carries the coding type used by the designated UE in the reconfiguration message and sends the code to the source RNC.
  • the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message.
  • the MSC determines that the coding type configured by the UE does not match the coding type supported by the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC, and then carries the coding type used by the specified UE to the source RNC in the reconfiguration message.
  • the receiver 1601 is further configured to receive an RNC migration request message that the UE sent by the source RNC does not participate in, so as to complete the RNC migration process that the UE does not participate in.
  • the receiver 1601 is specifically configured to receive an encoding type change request message sent by the source RNC, where the encoding type change request message carries a coding class to be used by the specified UE. Type.
  • the source RNC determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC, the source RNC sends an encoding type change request message to the MSC for reconfiguring the coding type configured by the UE. .
  • the coding type change request message carries the coding type to be used by the designated UE.
  • the source RNC determines whether the coding type configured by the UE is consistent with the coding type supported by the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC.
  • the MSC provided by the embodiment of the present application can send a reconfiguration message to the source RNC when the coding type configured by the UE is different from the coding type supported by the target RNC, and the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message. Then, the RNC migration process in which the UE does not participate is initiated to migrate the UE from the source RNC to the target RNC.
  • the problem that the UE migration fails due to the inconsistency between the coding type configured by the UE and the coding type indicated by the MSC in the prior art is solved, and the UE can be smoothly migrated to the target RNC.
  • an embodiment of the present application provides an RNC, as shown in FIG. 17, for implementing the method embodiment shown in FIG.
  • the RNC includes: a transmitter 1701, configured to send a request message to the MSC, and a receiver 1702, configured to receive a reconfiguration message sent by the MSC, where the reconfiguration message is used to change a coding type configured by the UE.
  • the reconfiguration message is used to change the coding type of the UE configuration.
  • the re-matching message has two triggering sources: 1) The re-matching message is sent from the source type RNC, and the encoding type change request message carries the encoding type used by the specified UE.
  • the MSC carries the coding type used by the UE in the reconfiguration message and sends it to the source RNC.
  • the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message.
  • the MSC determines that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC according to the coding type configured by the UE and the coding type supported by the target RNC, and then sends the coding type used by the specified UE to the source RNC in the reconfiguration message.
  • the processor 1703 is configured to reconfigure an encoding type of the UE according to the reconfiguration message.
  • the processor 1703 is further configured to: after reconfiguring the coding type configured by the UE according to the reconfiguration message sent by the MSC, initiate an RNC migration process that the UE does not participate in, and complete the RNC migration to the UE. Since the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message to an encoding type consistent with the encoding type supported by the target RNC, the processor 1703 does not appear during the RNC migration process in which the UE does not participate due to the UE configuration. The UE migration failure caused by the inconsistent coding type supported by the target RNC can successfully migrate the UE to the target RNC.
  • the transmitter 1701 is specifically configured to send an encoding type change request message to the MSC, where the message carries the encoding type to be used by the specified UE, or sends an RNC migration request message that the UE does not participate in to the MSC.
  • the request message includes an encoding type change request message and an RNC migration request message that the UE does not participate in.
  • the source RNC determines that the coding type configured by the UE does not match the coding type supported by the target RNC, it sends an encoding type change request message to the MSC, where the coding type change request message carries the coding type used by the UE.
  • the transmitter 1701 is further configured to: when determining that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC, send an encoding type change request message to the MSC.
  • the receiver 1702 is further configured to receive a coding type supported by a target RNC sent by a node such as a network management or a target RNC.
  • the RNC further includes: a determiner 1801, configured to determine, according to the coding type supported by the target RNC and the coding type configured by the UE, that the coding type configured by the UE is inconsistent with the coding type supported by the target RNC.
  • the RNC provided by the embodiment of the present application can send a reconfiguration message to the source RNC when the coding type configured by the UE is different from the coding type supported by the target RNC, and the source RNC reconfigures the coding type configured by the UE according to the reconfiguration message. Then, the RNC migration process in which the UE does not participate is initiated to migrate the UE from the source RNC to the target RNC.
  • the coding class of the UE configuration in the prior art is solved. The problem that the UE migration fails due to the inconsistent coding type supported by the target RNC can successfully migrate the UE to the target RNC.
  • the embodiment of the present application provides a system for migrating user equipment between radio network controllers, and the system covers implementations of the method and apparatus embodiments shown in FIG. 13 to FIG.
  • the system includes: an MSC and a source RNC.
  • the MSC receives the request message sent by the source RNC, and sends a re-configuration message of the UE coding type to the source RNC, so that the source RNC re-allocates the coding type of the UE, and receives the RNC migration request message that the UE does not participate in the RNC, so as to complete the UE. Participate in the RNC migration process.
  • the source RNC is configured to send a request message to the MSC, receive a reconfiguration message sent by the MSC, reconfigure the coding type of the UE according to the reconfiguration message, and initiate an RNC migration process that the UE does not participate in.
  • the system for the user equipment to be migrated between the radio network controllers in the embodiment of the present application can send a reconfiguration message to the source RNC when the coding type configured by the UE is inconsistent with the coding type supported by the target RNC, and the source RNC according to the reconfiguration
  • the message reconfigures the coding type configured by the UE, and then initiates an RNC migration process in which the UE does not participate to migrate the UE from the source RNC to the target RNC.
  • the problem that the UE migration fails due to the inconsistency between the coding type configured by the UE and the coding type supported by the target RNC in the prior art is solved, and the UE can be smoothly migrated to the target RNC.
  • the CN indicates that the coding type is indicated by the target RNC based on the coding type supported by the target RNC
  • the "target RNC supported coding type” and all the embodiments in this application are described.
  • the "CN (or MSC) is a different expression of the same meaning of the coding type indicated by the UE and the target RNC, and the meaning thereof is the coding type supported by the target RNC.
  • the present application can be implemented by means of software plus necessary general hardware, and of course, by hardware, but in many cases, the former is a better implementation. .
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
  • Hard A disk or optical disk, etc. includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

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

Abstract

本申请公开了一种用户设备在无线网络控制器之间迁移的方法、装置及系统，涉及通信技术领域，为将用户设备（UE）配置的编码类型配置成与目标无线网络控制器（RNC）支持的编码类型一致的编码类型，以便将UE迁移到目标RNC上而发明。所述方法包括：目标RNC接收UE不参与的RNC迁移请求消息（101），该请求消息中携带有源RNC发送的源RNC到目标RNC的透明容器和CN指示的编码类型，该透明容器包含所述UE配置的编码类型，若UE配置的编码类型与CN指示的编码类型不一致，则目标RNC向源RNC发送目标RNC到源RNC的透明容器，该透明容器携带用于更改UE编码类型的重配消息，以便源RNC发送重配消息给所述UE。本发明主要应用于跨RNC的切换。

Description

用户设备在无线网络控制器之间迁移的方法、 装置及系统 本申请要求于 2012 年 01 月 05 日提交中国专利局、 申请号为 201210002252.9、发明名称为"用户设备在无线网络控制器之间迁移的方法、 装置及系统"和 2012 年 04 月 27 日提交中国专利局、 申请号为 201210128354.5、发明名称为"用户设备在无线网络控制器之间迁移的方法、 装置及系统"的中国专利申请的优先权， 其全部内容通过引用结合在本申请 中。
技术领域
本申请涉及通信技术领域， 尤其涉及一种用户设备在无线网络控制器 之间迁移的方法、 装置及系统。 背景技术
在通用移动通信系统 ( Universal Mobile Telecommunications System, UMTS ) 中， 用户设备（ User Equipment , UE )通过接入节点与无线网络控 制器（ Radio Network Controller, RNC )建立无线 载（ Radio Bearer, RB ), RNC与核心网（ Core Network, CN )建立无线接入承载（ Radio Access Bearer, RAB ) , 由此建立 UE到 CN的无线链路， 实现 UE的电路域业务。
当建立好 UE经由 RNC连接到 CN的无线链路后， RNC会根据接入网 和 /或核心网的功率负载状况将正在进行电路域业务的 UE迁移到其他 RNC 上。 由于源 RNC与目标 RNC所支持的语音编码类型有可能不一致， 而 UE 配置的编码类型与源 RNC所支持的编码类型相一致， 所以当源 RNC与目 标 RNC支持的语音编码类型不一致时，在将 UE从源 RNC迁移到目标 RNC 的过程中需要同步 UE与目标 RNC之间的编码类型， 即使 UE与目标 RNC 的编码类型保持一致。 现有的 UE在 RNC之间迁移的技术， 是由源 RNC将 UE与源 RNC配 置的编码类型通过 CN告知给目标 RNC, CN根据 UE配置的编码类型和目 标 RNC支持的编码类型， 选择 UE与目标 RNC都支持的编码类型作为 UE 与目标 RNC建立 RB时使用的编码类型。在 UE参与的 RNC迁移过程（ UE Involved in Relocation of SRNS ) 中， 如果 CN为目标 RNC指示的编码类型 与 UE与源 RNC使用的编码类型不一致，则目标 RNC会将 UE配置的编码 类型重配为与 CN为目标 RNC指示的编码类型一致的编码类型， 然后对 UE进行 RNC迁移。 在 UE不参与的 RNC迁移过程 ( UE not Involved in Relocation of SRNS ) 中， 如果 CN为目标 RNC指示的编码类型与 UE与源 RNC使用的编码类型不一致， 则目标 RNC直接拒绝 UE的迁移。
在实现上述 UE在不同编码类型 RNC之间迁移的过程中， 发明人发现现 有技术中至少存在如下问题： 当 UE电路域业务的无线链路已经被目标 RNC 控制时， 只能执行 UE不参与的 RNC迁移过程 ( UE not Involved in Relocation of SRNS ) , 此种情况下， 如果 UE配置的编码类型与 CN为目标 RNC指示的 编码类型不一致， 则无法将 UE迁移到目标 RNC上。 发明内容
本申请的实施例提供一种用户设备在无线网络控制器之间迁移的方 法、 装置及系统， 能够保证当 UE配置的编码类型与 CN配置的编码类型不 一致时， UE可以顺利迁移到目标 RNC上。
一方面， 本申请提供了一种用户设备在无线网络控制器之间迁移的方 法， 包括：接收用户设备 UE不参与的无线网络控制器 RNC迁移请求消息， 所述请求消息中携带有源 RNC发送的源 RNC到目标 RNC的透明容器和核 心网 CN指示的编码类型， 所述透明容器包含所述 UE配置的编码类型； 若 所述 UE配置的编码类型与所述 CN指示的编码类型不一致 ,向所述源 RNC 发送目标 RNC到源 RNC的透明容器，所述透明容器携带用于更改所述 UE 编码类型的重配消息， 以便所述源 RNC发送重配消息给所述 UE。
另一方面， 本申请提供了另一种用户设备在无线网络控制器之间迁移 的方法， 包括： 向核心网 CN发送用户设备 UE不参与的无线网络控制器 RNC迁移请求消息， 以便所述 CN向所述目标 RNC发送迁移请求消息； 接 收所述 CN发送的迁移命令消息， 所述迁移命令消息中包含所述目标 RNC 发送的目标 RNC到源 RNC的透明容器， 所述透明容器中包含 UE编码类 型的重配消息； 向所述 UE发送重配消息， 以便所述 UE根据所述重配消息 更改编码类型。
另一方面， 本申请提供了另一种用户设备在无线网络控制器之间迁移 的方法， 包括： 在发起迁移时， 若用户设备 UE的无线链路在目标无线网络 控制器 RNC控制下，确定源 RNC不知道目标 RNC支持的编码类型或确定 所述 UE配置的编码类型与所述目标 RNC支持的编码类型不一致或确定所 述 UE存在宽带自适应多速率承载； 发起 UE参与的 RNC迁移过程。
另一方面， 本申请提供了另一种用户设备在无线网络控制器之间迁移 的方法， 包括： 接收源无线网络控制器 RNC发送的用户设备 UE不参与的 RNC迁移请求消息；若所述 UE配置的编码类型与目标 RNC支持的编码类 型不一致， 向所述源 RNC发送迁移失败消息， 以便所述源 RNC根据所述 迁移失败消息发起 UE参与的 RNC迁移过程。
另一方面， 本申请提供了另一种用户设备在无线网络控制器之间迁移 的方法， 包括： 接收源无线网络控制器 RNC发送的请求消息； 向所述源 RNC发送用户设备 UE编码类型的重配消息， 以便所述源 RNC重配所述 UE的编码类型； 接收源 RNC发送的 UE不参与的 RNC迁移请求消息， 以 便完成 UE不参与的 RNC迁移过程。
另一方面， 本申请提供了另一种用户设备在无线网络控制器之间迁移 的方法， 包括：向核心网 CN发送请求消息；接收所述 CN发送的重配消息； 根据所述重配消息重配所述用户设备 UE的编码类型；发起 UE不参与的无 线网络控制器 RNC迁移过程。
另一方面， 本申请提供了一种无线网络控制器 RNC, 包括： 接收器， 用于接收用户设备 UE不参与的 RNC迁移请求消息， 所述请求消息中携带 有源 RNC发送的源 RNC到目标 RNC的透明容器和核心网 CN指示的编码 类型， 所述透明容器包含所述 UE配置的编码类型； 发送器， 用于向所述源 RNC发送目标 RNC到源 RNC的透明容器， 所述透明容器携带用于更改所 述 UE编码类型的重配消息， 以便所述源 RNC发送重配消息给所述 UE。
另一方面， 本申请还提供了一种无线网络控制器 RNC, 包括： 发送器， 用于向核心网 CN发送用户设备 UE不参与的 RNC迁移请求消息， 以便所 述 CN向所述目标 RNC发送迁移请求消息； 接收器， 用于接收所述 CN发 送的迁移命令消息， 所述迁移命令消息中包含所述目标 RNC发送的目标 RNC到源 RNC的透明容器，所述透明容器中包含 UE编码类型的重配消息； 所述发送器还用于向所述 UE发送重配消息，以便所述 UE根据所述重配消 息更改编码类型。
另一方面， 本申请还提供了一种无线网络控制器 RNC, 包括： 判断器， 用于确定源 RNC不知道目标 RNC支持的编码类型或确定所述 UE配置的 编码类型与所述目标 RNC支持的编码类型不一致或确定所述 UE存在宽带 自适应多速率承载； 处理器， 用于发起 UE参与的 RNC迁移过程。
另一方面， 本申请还提供了一种核心网 CN, 包括： 接收器， 用于接收 源无线网络控制器 RNC发送的用户设备 UE不参与的 RNC迁移请求消息； 发送器， 用于向所述源 RNC发送迁移失败消息， 以便所述源 RNC根据所 述迁移失败消息发起 UE参与的 RNC迁移过程。
另一方面， 本申请还提供了一种核心网 CN, 包括： 接收器， 用于接收 源无线网络控制器 RNC发送的请求消息； 发送器， 用于向所述源 RNC发 送用户设备 UE编码类型的重配消息， 以便所述源 RNC重配所述 UE的编 码类型； 所述接收器还用于接收源 RNC发送的 UE不参与的 RNC迁移请 求消息， 以便完成 UE不参与的 RNC迁移过程。
另一方面， 本申请还提供了一种无线网络控制器 RNC, 包括： 发送器， 用于向核心网 CN发送请求消息； 接收器， 用于接收所述 CN发送的重配消 息； 处理器， 用于才艮据所述重配消息重配所述 UE的编码类型； 所述处理器 还用于发起用户设备 UE不参与的 RNC迁移过程。
另一方面， 本申请提供了一种用户设备在无线网络控制器之间迁移的 系统， 包括： 目标无线网络控制器 RNC, 用于接收用户设备 UE不参与的 RNC迁移请求消息， 所述请求消息中携带有源 RNC发送的源 RNC到目标 RNC的透明容器和核心网 CN指示的编码类型，所述透明容器包含所述 UE 配置的编码类型，若所述 UE配置的编码类型与所述 CN指示的编码类型不 一致， 向所述源 RNC发送目标 RNC到源 RNC的透明容器， 所述透明容器 携带用于更改所述 UE编码类型的重配消息， 以便所述源 RNC发送重配消 息给所述 UE; 源 RNC, 用于向所述 CN发送 UE不参与的 RNC迁移请求 消息， 以便所述 CN向所述目标 RNC发送迁移请求消息， 接收所述 CN发 送的迁移命令消息， 所述迁移命令消息中包含所述目标 RNC发送的目标 RNC到源 RNC的透明容器，所述透明容器中包含 UE编码类型的重配消息， 向所述 UE发送重配消息， 以便所述 UE根据所述重配消息更改编码类型。
另一方面， 本申请还提供了一种用户设备在无线网络控制器之间迁移 的系统， 包括： 源无线网络控制器 RNC, 用于在发起迁移时， 若用户设备 UE的无线链路在目标 RNC控制下， 确定源 RNC不知道目标 RNC支持的 编码类型或确定所述 UE配置的编码类型与所述目标 RNC支持的编码类型 不一致或确定所述 UE存在宽带自适应多速率承载， 发起 UE参与的 RNC 迁移过程； 核心网 CN, 用于接收源 RNC发送的 UE不参与的 RNC迁移请 求消息， 若所述 UE配置的编码类型与目标 RNC支持的编码类型不一致， 向所述源 RNC发送迁移失败消息， 以便所述源 RNC根据所述迁移失败消 息发起 UE参与的 RNC迁移过程。 另一方面， 本申请还提供了一种用户设备在无线网络控制器之间迁移 的系统， 包括： 核心网 CN, 接收源无线网络控制器 RNC发送的请求消息， 向所述源 RNC发送用户设备 UE编码类型的重配消息， 以便所述源 RNC 重配所述 UE的编码类型，接收源 RNC发送的 UE不参与的 RNC迁移请求 消息， 以便完成 UE不参与的 RNC迁移过程； 源 RNC, 用于向 CN发送请 求消息，接收所述 CN发送的重配消息， 根据所述重配消息重配所述 UE的 编码类型， 发起 UE不参与的 RNC迁移过程。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法、 装 置及系统， 能够当 UE配置的编码类型与 CN为 UE和目标 RNC指示的编码类 型不一致时， 将 UE配置的编码类型重配为与 CN为 UE和目标 RNC指示的编 码类型一致的编码类型， 然后发起 UE不参与的 RNC迁移过程。 或者， 当 UE 配置的编码类型与 CN为 UE和目标 RNC指示的编码类型不一致时，直接发起 UE参与的 RNC迁移过程， 通过 UE参与的 RNC迁移过程将 UE配置的编码类 型重配为与 CN为 UE和目标 RNC指示的编码类型一致的编码类型。解决了现 有技术中当 UE电路域业务的无线链路已经被目标 RNC控制时， UE不参与的 RNC迁移过程无法重配 UE编码类型的问题，能够保证当 UE配置的编码类型 与 CN配置的编码类型不一致时， UE可以顺利迁移到目标 RNC上。 附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案， 下面将对 实施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是本申请的一些实施例， 对于本领域普通技术人员 来讲， 在不付出创造性劳动的前提下， 还可以根据这些附图获得其他的附 图。
图 1 为本申请实施例中用户设备在无线网络控制器之间迁移的方法的 流程图； 图 2为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 3 为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 4为本申请实施例中 RNC的结构示意图；
图 5为本申请实施例中 RNC的结构示意图；
图 6为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 7 为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 8为本申请实施例中源 RNC发起的 UE参与的 RNC迁移过程的网 络交互图；
图 9为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 10为本申请实施例中 RNC的结构示意图；
图 11为本申请实施例中 RNC的结构示意图；
图 12为本申请实施例中 MSC的结构示意图；
图 13为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 14为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 15为本申请另一个实施例中用户设备在无线网络控制器之间迁移的 方法的流程图；
图 16为本申请实施例中 MSC的结构示意图；
图 17为本申请实施例中 RNC的结构示意图；
图 18为本申请实施例中 RNC的结构示意图。 具体实施方式
下面将结合本申请实施例中的附图， 对本申请实施例中的技术方案进 行清楚、 完整地描述， 显然， 所描述的实施例仅仅是本申请一部分实施例， 而不是全部的实施例。 基于本申请中的实施例， 本领域普通技术人员在没 有作出创造性劳动前提下所获得的所有其他实施例， 都属于本申请保护的 范围。
本申请实施例中以 CN中的移动交换中心 （Mobile Switching Center, MSC )作为 CN中的执行主体代表 CN描述本申请的实施例， 实际应用中可 以代表 CN作为本申请实施例的执行主体的网元设备并不限定于 MSC , 对 此本申请实施例不作限制。
本申请实施例提供了一种用户设备在无线网络控制器之间迁移的方 法， 如图 1所示。
101、 目标 RNC接收 UE不参与的 RNC迁移请求消息。
所述请求消息中携带有源 RNC发送的源 RNC到目标 RNC的透明容器 和 MSC指示的编码类型， 所述透明容器包含 UE配置的编码类型。
102、 当 UE配置的编码类型与 MSC指示的编码类型不一致时， 目标 RNC向源 RNC发送目标 RNC到源 RNC的透明容器。
目标 RNC到源 RNC的透明容器中携带用于更改 UE编码类型的重配 消息， 以便源 RNC发送重配消息给 UE。
103、 目标 RNC接收重配完成消息。
所述重配完成消息 UE发送给目标 RNC或由 UE发送给源 RNC。 若 UE将重配完成消息发送给源 RNC, 则源 RNC通知目标 RNC完成重配。
目标 RNC接收重配完成消息 , 完成对 UE编码类型的重配和对 UE的 迁移。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够在当 UE 配置的编码类型与 MSC指示的编码类型不一致时通过在目标 RNC到源 RNC的透明容器中携带为 UE重配的编码类型的方式将 UE配置 的编码类型重配为与 MSC指示的编码类型相一致的编码类型。解决了现有 技术中， 当 UE的无线链路都在目标 RNC控制下时， 无法发起 UE参与的 RNC迁移过程导致的 UE迁移失败的问题，保证了 UE顺利迁移到目标 RNC 上。
本申请实施例提供了另一种用户设备在无线网络控制器之间迁移的方 法， 如图 2所示， 所述方法是对图 1所示实施例的进一步扩展。
201、 目标 RNC接收源 RNC发送的 UE不参与的 RNC迁移请求消息。 该迁移请求消息中携带有源 RNC到目标 RNC的透明容器，所述源 RNC 到目标 RNC的透明容器中的非接入层同步指示中携带有 UE配置的编码类 型。
202、若 UE配置的编码类型与 MSC指示的编码类型不一致，目标 RNC 向源 RNC发送目标 RNC到源 RNC的透明容器。
该目标 RNC 到源 RNC 的透明容器中的非接入层同步指示中携带有 MSC指示的编码类型，源 RNC根据该编码类型对 UE配置的编码类型进行 重配。
在本申请实施例的一个应用场景中， UE配置的编码类型为宽带自适应 多速率（ Wideband Adaptive Multi-Rate, WB AMR ), MSC为 UE和目标 RNC 指示的编码类型为窄带自适应多速率 （ Narrow Adaptive Multi-Rate , ΝΒ AMR ), 此时需要对 UE配置的编码类型进行重配。 目标 RNC在目标 RNC 到源 RNC的透明容器中携带 MSC为 UE和目标 RNC指示的编码类型（NB AMR ), 指示源 RNC将 UE配置的编码类型重配为 NB AMR。
203、 目标 RNC向 MSC发送迁移检测消息。
目标 RNC收到迁移执行触发后，向 MSC发送迁移检测消息，目标 RNC 开始 SRNC操作， MSC切换用户面从源 RNC到目标 RNC。 该迁移执行触 发可能是从空口收到重配完成消息或者是从源 RNC和目标 RNC之间的接 口收到的指示。
204、 目标 RNC接收重配完成消息。
所述重配完成消息 UE发送给目标 RNC或由 UE发送给源 RNC。 若 UE将重配完成消息发送给源 RNC, 则源 RNC通知目标 RNC完成重配。
205、 目标 RNC向 MSC发送迁移消息。
完成对 UE的迁移。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够在当 UE 配置的编码类型与 MSC指示的编码类型不一致时通过在目标 RNC到源 RNC的透明容器中携带为 UE重配的编码类型的方式将 UE配置 的编码类型重配为与 MSC指示的编码类型相一致的编码类型。解决了现有 技术中， 当 UE的无线链路都在目标 RNC控制下时， 无法发起 UE参与的 RNC迁移过程导致的 UE迁移失败的问题，保证了 UE顺利迁移到目标 RNC 上。
此外， 本申请实施例提供的用户设备在无线网络控制器之间迁移的方 法， 还能够在为 UE重配编码类型后， 直接将 UE迁移到目标 RNC上， 节 省了现有技术在重配 UE编码类型后还需由源 RNC发起 UE不参与的 RNC 迁移过程的步骤， 节省了网络的信令开销。
本申请实施例提供一种用户设备在无线网络控制器之间迁移的方法， 如图 3所示。
301、源 RNC向 MSC发送 UE不参与的 RNC迁移请求消息，以便 MSC 向目标 RNC发送迁移请求消息。
所述迁移请求消息用于将 UE从源 RNC迁移到目标 RNC上。当 UE配 置的编码类型与 MSC指示的编码类型不一致时， 执行步骤 302, 对 UE配 置的编码类型进行重配。
302、 源 RNC接收 MSC发送的迁移命令消息。 该迁移命令消息中包含目标 RNC发送的目标 RNC到源 RNC的透明容 器， 该透明容器中包含 UE编码类型的重配消息。 例如， 当 UE配置的编码 类型为 WB AMR, MSC为 UE和目标 RNC指示的编码类型为 NB AMR时 , 所述重配消息中携带 NB AMR, 源 RNC根据重配消息将 UE配置的编码类 型重配为 NB AMR。
303、 源 RNC向 UE发送重配消息， 以便 UE根据重配消息更改编码类 型并发送重配完成消息到目标 RNC或源 RNC。
UE在根据源 RNC发送的重配消息将 WB AMR更改为 NB AMR后 , 向目标 RNC或源 RNC发送重配完成消息， 表示完成 UE配置的编码类型 重配。 若是源 RNC收到重配完成消息， 源 RNC通知目标 RNC完成重配。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够在当 UE 配置的编码类型与 MSC指示的编码类型不一致时通过在目标 RNC到源 RNC的透明容器中携带为 UE重配的编码类型的方式将 UE配置 的编码类型重配为与 MSC指示的编码类型相一致的编码类型。解决了现有 技术中， 当 UE的无线链路都在目标 RNC控制下时， 无法发起 UE参与的 RNC迁移过程导致的 UE迁移失败的问题，保证了 UE顺利迁移到目标 RNC 上。
参考图 2所示方法实施例的实现， 本申请实施例提供了一种 RNC, 如 图 4所示， 用以实现图 2所示的方法实施例。 所述 RNC包括： 接收器 41 和发送器 42。
接收器 41 , 用于接收 UE不参与的 RNC迁移请求消息， 该请求消息中 携带有源 RNC发送的源 RNC到目标 RNC的透明容器和 MSC指示的编码 类型， 所述透明容器包含 UE配置的编码类型。
该迁移请求消息中携带有源 RNC到目标 RNC的透明容器，所述源 RNC 到目标 RNC的透明容器中的非接入层同步指示中携带有 UE配置的编码类 型。 发送器 42, 用于向源 RNC发送目标 RNC到源 RNC的透明容器， 该 透明容器携带用于更改 UE编码类型的重配消息， 以便源 RNC发送重配消 息给 UE。
该目标 RNC 到源 RNC 的透明容器中的非接入层同步指示中携带有 MSC指示的编码类型，源 RNC根据该编码类型对 UE配置的编码类型进行 重配。
在本申请实施例的一个应用场景中， UE配置的编码类型为 WB AMR, MSC为 UE和目标 RNC指示的编码类型为 NB AMR,此时需要对 UE配置 的编码类型进行重配。 目标 RNC在目标 RNC到源 RNC的透明容器中携带 MSC为 UE和目标 RNC指示的编码类型 （ NB AMR ), 指示源 RNC将 UE 配置的编码类型重配为 NB AMR。
所述接收器 41还用于接收 UE发送的重配完成消息。
当 UE配置的编码类型重配为 NB AMR后， 所述接收器 41接收 UE发 送的重配完成消息， 表明完成对 UE编码类型的重配。
本申请实施例提供的 RNC,能够在当 UE配置的编码类型与 MSC指示 的编码类型不一致时通过在目标 RNC到源 RNC的透明容器中携带为 UE 重配的编码类型的方式将 UE配置的编码类型重配为与 MSC指示的编码类 型相一致的编码类型。解决了现有技术中，当 UE的无线链路都在目标 RNC 控制下时，无法发起 UE参与的 RNC迁移过程导致的 UE迁移失败的问题， 保证了 UE顺利迁移到目标 RNC上。
此外， 本申请实施例提供的 RNC, 还能够在为 UE重配编码类型后， 直接将 UE迁移到目标 RNC上， 节省了现有技术在重配 UE编码类型后还 需由源 RNC发起 UE不参与的 RNC迁移过程的步骤， 节省了网络的信令 开销。
参考图 3所示方法实施例的实现， 本申请实施例提供了一种 RNC, 如 图 5所示， 用以实现图 3所示的方法实施例。 所述 RNC包括： 发送器 51 和接收器 52。
发送器 51 , 用于向 MSC发送 UE不参与的 RNC迁移请求消息， 以便 CN向目标 RNC发送迁移请求消息。
所述迁移请求消息用于将 UE从源 RNC迁移到目标 RNC上。当 UE配 置的编码类型与 MSC指示的编码类型不一致时， 对 UE配置的编码类型进 行重配。
接收器 52, 用于接收 MSC发送的迁移命令消息。
该迁移命令消息中包含目标 RNC发送的目标 RNC到源 RNC的透明容 器， 该透明容器中包含 UE编码类型的重配消息。 例如， 当 UE配置的编码 类型为 WB AMR, MSC为 UE和目标 RNC指示的编码类型为 NB AMR时 , 所述重配消息中携带 NB AMR, 源 RNC根据重配消息将 UE配置的编码类 型重配为 NB AMR。
所述发送器 51还用于向 UE发送重配消息， 以便 UE根据重配消息更 改编码类型。
UE在根据源 RNC发送的重配消息将 WB AMR更改为 NB AMR后 , 向目标 RNC发送重配完成消息， 表示完成 UE配置的编码类型重配。
本申请实施例提供的 RNC,能够在当 UE配置的编码类型与 MSC指示 的编码类型不一致时通过在目标 RNC到源 RNC的透明容器中携带为 UE 重配的编码类型的方式将 UE配置的编码类型重配为与 MSC指示的编码类 型相一致的编码类型。解决了现有技术中，当 UE的无线链路都在目标 RNC 控制下时，无法发起 UE参与的 RNC迁移过程导致的 UE迁移失败的问题， 保证了 UE顺利迁移到目标 RNC上。
进一步的， 本申请实施例提供了一种用户设备在无线网络控制器之间 迁移的系统， 所述系统涵盖了图 1至图 5所示的方法和装置实施例的实现。 所述系统包括： 目标 RNC和源 RNC。
目标 RNC , 用于接收 UE不参与的 RNC迁移请求消息， 该请求消息中 携带有源 RNC发送的源 RNC到目标 RNC的透明容器和 MSC指示的编码 类型，该透明容器包含 UE配置的编码类型，若 UE配置的编码类型与 MSC 指示的编码类型不一致， 向源 RNC发送目标 RNC到源 RNC的透明容器， 该透明容器携带用于更改 UE编码类型的重配消息， 以便源 RNC发送重配 消息给 UE。
源 RNC, 用于向 MSC发送 UE不参与的 RNC迁移请求消息， 以便 MSC向目标 RNC发送迁移请求消息， 接收 MSC发送的迁移命令消息， 该 迁移命令消息中包含目标 RNC发送的目标 RNC到源 RNC的透明容器，该 透明容器中包含 UE编码类型的重配消息， 向 UE发送重配消息， 以便 UE 才艮据重配消息更改编码类型。
本申请实施例提供的用户设备在无线网络控制器之间迁移的系统， 能 够在当 UE 配置的编码类型与 MSC指示的编码类型不一致时通过在目标 RNC到源 RNC的透明容器中携带为 UE重配的编码类型的方式将 UE配置 的编码类型重配为与 MSC指示的编码类型相一致的编码类型。解决了现有 技术中， 当 UE的无线链路都在目标 RNC控制下时， 无法发起 UE参与的 RNC迁移过程导致的 UE迁移失败的问题，保证了 UE顺利迁移到目标 RNC 上。
此外， 本申请实施例提供的用户设备在无线网络控制器之间迁移的系 统， 还能够在为 UE重配编码类型后， 直接将 UE迁移到目标 RNC上， 节 省了现有技术在重配 UE编码类型后还需由源 RNC发起 UE不参与的 RNC 迁移过程的步骤， 节省了网络的信令开销。
本申请实施例提供了一种用户设备在无线网络控制器之间迁移的方 法， 如图 6所示。
601、 在发起迁移时， 若 UE的无线链路在目标 RNC控制下， 源 RNC 确定源 RNC不知道目标 RNC支持的编码类型或确定 UE配置的编码类型 与目标 RNC支持的编码类型不一致或确定所述 UE存在宽带自适应多速率 承载。
602、 源 RNC发起 UE参与的 RNC迁移过程。
源 RNC在 UE参与的 RNC迁移过程中将 UE的编码类型重配为与目标 RNC支持的编码类型一致的编码类型。
现有技术中， 当 UE的无线链路都在目标 RNC控制下时， 源 RNC无 法发起 UE参与的 RNC迁移过程。如果 UE配置的编码类型与目标 RNC支 持的编码类型不一致时， 源 RNC无法在 UE参与的 RNC迁移过程中重配 UE配置的编码类型， 只能拒绝 UE的迁移。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够当 UE的无线链路都在目标 RNC控制下时，发起 UE参与的 RNC迁移过 程，在 UE参与的 RNC迁移过程中将 UE配置的编码类型重配为与目标 RNC 支持的编码类型一致的编码类型， 保证了 UE顺利迁移到目标 RNC上。
本申请实施例提供了另一种用户设备在无线网络控制器之间迁移的方 法， 如图 7所示， 所述方法是对图 6所示实施例的进一步扩展。
701、 在发起迁移时， 若 UE的无线链路在目标 RNC控制下， 源 RNC 确定 UE配置的编码类型与目标 RNC支持的编码类型不一致。
确定 UE配置的编码类型与目标 RNC支持的编码类型不一致的实现方 式包括如下两种方式。
1 )源 RNC判断 UE配置的编码类型与目标 RNC支持的编码类型不一 致。
2 ) 源 RNC接收 MSC发送的迁移失败消息， 源 RNC接收到该迁移失 败消息后获知 UE配置的编码类型与目标 RNC支持的编码类型不一致。
需要说明的是， 1 ) 中在源 RNC判断 UE配置的编码类型与目标 RNC 支持的编码类型不一致之前， 源 RNC还要接收网管系统或目标 RNC等节 点发送的目标 RNC支持的编码类型， 以便源 RNC可以对 UE配置的编码 类型和目标 RNC支持的编码类型进行比较， 确定 UE配置的编码类型与目 标 RNC支持的编码类型不一致。
本申请实施例中源 RNC可通过但不局限于通过上述 2种确定方式之 一，确定 UE配置的编码类型与目标 RNC支持的编码类型不一致，当源 RNC 确定 UE配置的编码类型与目标 RNC支持的编码类型不一致时， 执行步骤 703。
702、 在发起迁移时， 若 UE的无线链路在目标 RNC控制下， 源 RNC 确定 UE配置的编码类型为自适应编码类型,不知道目标 RNC所支持的编码 类型。
比如， 当 UE配置的编码类型为宽带自适应多速率（ Wideband Adaptive Multi-Rate , WB AMR )类型时， 执行步骤 703。
在本申请实施例的一个应用场景中， MSC根据 UE支持的编码类型和 目标 RNC支持的编码类型为 UE和目标 RNC指示编码类型。 MSC—般会 以目标 RNC 支持的编码类型为准进行配指示。 当 UE 配置的编码类型为 WB AMR , 而目标 RNC 只支持窄带自适应多速率 （ Narrow Adaptive Multi-Rate, NB AMR )时 , 如果 MSC指示目标 RNC釆用 NB AMR, 则目 标 RNC无法与使用 WB AMR的 UE进行数据交互， 此种情况下需要执行 步骤 203 , 将 UE配置的编码类型由 WB AMR重配为 NB AMR, 以便 UE 配置的编码类型与目标 RNC的编码类型保持一致。
703、 源 RNC发起 UE参与的 RNC迁移过程。
在 UE参与的 RNC迁移过程中对 UE配置的编码类型进行重配并完成 UE的迁移过程。 具体的， 如图 8所示， 源 RNC发起 UE参与的 RNC迁移 过程主要包括如下步骤。
801、 源 RNC向 MSC发送 Relocation Required (迁移请求） 消息。 其中 Relocation Type设置为 UE involved in relocation of SRNS ( UE参 与的 RNC迁移过程；)。 表示源 RNC发起的迁移过程为 UE参与的 RNC迁 移过程。源 RNC在源 RNC到目标 RNC的透明容器中的非接入层同步指示 中指示 UE配置的编码类型。
802、 MSC向目标 RNC发送 Relocation Request (迁移要求） 消息。 MSC根据目标 RNC支持的编码类型和 UE支持的编码类型为 UE和目 标 RNC指示编码类型， 并在非接入层同步指示中向目标 RNC告知指示的 编码类型。
803、 目标 RNC检查 UE配置的编码类型和 MSC指示的编码类型是否 一致。
若目标 RNC不支持该编码类型时， 将自身支持的编码类型放置在目标 RNC到源 RNC透明容器中。
804、目标 RNC将目标 RNC到源 RNC透明容器通过 Relocation Request Ack (迁移请求确认） 消息发送给 MSC。
805、 MSC向源 RNC发送 Relocation Command (迁移命令） 消息。 该命令中携带目标 RNC到源 RNC透明容器。
806、 源 RNC根据目标 RNC到源 RNC透明容器中的配置向 UE发送 重配消息， 指示 UE重配编码类型。
807、 目标 RNC向 MSC发送 Relocation Detect (迁移检查 ) 消息。 MSC切换用户面从源 RNC到目标 RNC。
808、当目标 RNC收到 UE发送重配完成消息后，向 MSC发送 Relocation Complete (迁移完成） 消息， 完成对 UE配置的编码类型重配和迁移。
当源 RNC收到 UE发送重配完成消息后通知目标 RNC完成编码类 型重配， 目标 RNC向 MSC发送 Relocation Complete (迁移完成）消息， 完 成对 UE配置的编码类型重配和迁移。
在图 8所示的 UE参与的 RNC迁移过程中，源 RNC将 UE配置的编码 类型重配为目标 RNC支持的编码类型。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够当 UE的无线链路都在目标 RNC控制下时，发起 UE参与的 RNC迁移过 程， 在 UE参与的 RNC迁移过程中将 UE配置的编码类型重配为目标 RNC 支持的编码类型一致的编码类型。解决了现有技术中， 当 UE的无线链路都 在目标 RNC控制下时， 源 RNC无法发起 UE参与的 RNC迁移过程导致的 UE迁移失败的问题， 保证了 UE顺利迁移到目标 RNC上。
此外， 本申请实施例提供的用户设备在无线网络控制器之间迁移的方 法， 还能够在 UE使用 WB AMR时， 无论 UE配置的编码类型与目标 RNC 支持的编码类型是否一致， 都执行 UE参与的 RNC迁移过程， 将 UE配置 的编码类型重配为目标 RNC支持的编码类型，节省了判断 UE与目标 RNC 编码类型是否一致的步骤。
本申请实施例提供了一种用户设备在无线网络控制器之间迁移的方 法， 如图 9所示。
901、 MSC接收源 RNC发送的 UE不参与的 RNC迁移请求消息。 移到目标 RNC上。
902、若 UE配置的编码类型与目标 RNC支持的编码类型不一致， MSC 向源 RNC发送迁移失败消息。
所述迁移失败消息携带一个指示信息，比如指示 UE配置的编码类型与 目标 RNC支持的编码类型不一致或指示源 RNC发起 UE参与的 RNC迁移 过程。 源 RNC根据迁移失败消息发起 UE参与的 RNC迁移过程。
当 UE配置的编码类型与目标 RNC支持的编码类型不一致时，步骤 401 迁移失败，需要源 RNC根据 MSC发送的迁移失败消息发起 UE参与的 RNC 迁移过程， 并在该迁移过程中将 UE配置的编码类型重配为目标 RNC支持 的编码类型。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够当 UE的无线链路都在目标 RNC控制下时，发起 UE参与的 RNC迁移过 程， 在 UE参与的 RNC迁移过程中将 UE配置的编码类型重配为目标 RNC 支持的编码类型一致的编码类型， 保证了 UE顺利迁移到目标 RNC上。 参考图 7所示方法实施例的实现， 本申请实施例提供了一种 RNC, 如 图 10所示，用以实现图 7所示的方法实施例。所述 RNC包括：判断器 1001 和处理器 1002。
判断器 1001 , 用于确定源 RNC不知道目标 RNC支持的编码类型或确 定 UE配置的编码类型与所述目标 RNC支持的编码类型不一致。
处理器 1002, 用于发起 UE参与的 RNC迁移过程。
进一步的， 如图 11所示， 所述 RNC可以包括： 发送器 1101 , 用于发 送 UE不参与的 RNC切换请求消息到 MSC; 接收器 1102, 用于接收 MSC 发送的迁移失败消息。
所述迁移失败消息用于指示 UE配置的编码类型与目标 RNC支持的编 码类型不一致。
进一步的， 所述接收器 1102还用于接收网管节点或目标 RNC发送的 目标 RNC支持的编码类型。
进一步的， 在所述判断器 1001确定 UE配置的编码类型与目标 RNC 支持的编码类型不一致之前， 所述接收器 1102还要接收网管或目标 RNC 等节点发送的目标 RNC支持的编码类型， 以便所述判断器 1001可以对 UE 配置的编码类型和目标 RNC支持的编码类型进行比较， 确定 UE配置的编 码类型与目标 RNC支持的编码类型不一致。
本申请实施例提供的 RNC,能够当 UE的无线链路都在目标 RNC控制 下时， 发起 UE参与的 RNC迁移过程， 在 UE参与的 RNC迁移过程中将 UE配置的编码类型重配为目标 RNC支持的编码类型一致的编码类型。 解 决了现有技术中， 当 UE的无线链路都在目标 RNC控制下时，无法发起 UE 参与的 RNC迁移过程导致的 UE迁移失败的问题， 保证了 UE顺利迁移到 目标 RNC上。
此外， 本申请实施例提供的 RNC, 还能够在 UE使用 WB AMR时， 无 论 UE配置的编码类型与目标 RNC支持的编码类型是否一致， 都执行 UE 参与的 RNC迁移过程， 将 UE配置的编码类型重配为目标 RNC支持的编 码类型， 节省了判断 UE与目标 RNC编码类型是否一致的步骤。
参考图 10所示方法实施例的实现，本申请实施例提供了一种 MSC,如 图 12所示，用以实现图 10所示的方法实施例。所述 MSC包括：接收器 1201 和发送器 1202。
接收器 1201 , 用于接收源 RNC发送的 UE不参与的 RNC迁移请求消 息。 移到目标 RNC上。
发送器 1202, 用于向源 RNC发送迁移失败消息。
源 RNC根据迁移失败消息发起 UE参与的 RNC迁移过程。当 UE配置 的编码类型与目标 RNC支持的编码类型不一致时， 需要源 RNC根据 MSC 发送的迁移失败消息发起 UE参与的 RNC迁移过程， 并在该迁移过程中将 UE配置的编码类型重配为目标 RNC支持的编码类型。
本申请实施例提供的 MSC,能够当 UE的无线链路都在目标 RNC控制 下时， 发起 UE参与的 RNC迁移过程， 在 UE参与的 RNC迁移过程中将 UE配置的编码类型重配为目标 RNC支持的编码类型一致的编码类型， 保 证了 UE顺利迁移到目标 RNC上。
进一步的， 本申请实施例提供了一种用户设备在无线网络控制器之间 迁移的系统， 所述系统涵盖了图 6至图 12所述方法和装置实施例的实现。 所述系统包括： 源 RNC和 MSC。
源 RNC, 用于在发起迁移时， 若 UE的无线链路在目标 RNC控制下， 确定源 RNC不知道目标 RNC支持的编码类型或确定 UE配置的编码类型 与目标 RNC支持的编码类型不一致， 发起 UE参与的 RNC迁移过程。
MSC, 用于接收源 RNC发送的 UE不参与的 RNC迁移请求消息， 若 UE配置的编码类型与目标 RNC支持的编码类型不一致，向源 RNC发送迁 移失败消息， 以便源 RNC根据迁移失败消息发起 UE参与的 RNC迁移过 程。
本申请实施例提供的用户设备 UE在无线网络控制器 RNC之间迁移的 系统，能够当 UE的无线链路都在目标 RNC控制下时，发起 UE参与的 RNC 迁移过程， 在 UE参与的 RNC迁移过程中将 UE配置的编码类型重配为目 标 RNC支持的编码类型一致的编码类型。 解决了现有技术中， 当 UE的无 线链路都在目标 RNC控制下时， 无法发起 UE参与的 RNC迁移过程导致 的 UE迁移失败的问题， 保证了 UE顺利迁移到目标 RNC上。
此外， 本申请实施例提供的用户设备在无线网络控制器之间迁移的系 统， 还能够在 UE使用 WB AMR时， 无论 UE配置的编码类型与目标 RNC 支持的编码类型是否一致， 都执行 UE参与的 RNC迁移过程， 将 UE配置 的编码类型重配为目标 RNC支持的编码类型，节省了判断 UE与目标 RNC 编码类型是否一致的步骤。
本申请实施例提供了一种用户设备在无线网络控制器之间迁移的方 法， 如图 13所示。
1301、 MSC接收源 RNC发送的请求消息。
1302, MSC向源 RNC发送 UE编码类型的重配消息。
若 UE配置的编码类型与目标 RNC支持的编码类型不一致， MSC向源 RNC发送 UE编码类型的重配消息， 用于对 UE配置的编码类型进行重配。
1303、 MSC接收源 RNC发送的 UE不参与的 RNC迁移请求消息， 以 便完成 UE不参与的 RNC迁移过程。
UE根据该重配消息更改编码类型。 源 RNC在 UE完成编码类型更改 后， 发起 UE不参与的 RNC迁移过程， 由此完成对 UE的迁移。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够当 UE配置的编码类型与目标 RNC支持的编码类型不一致时向源 RNC 发送重配消息，由源 RNC根据该重配消息对 UE配置的编码类型进行重配， 然后发起 UE不参与的 RNC迁移过程将 UE从源 RNC迁移到目标 RNC上。 解决了现有技术中 UE配置的编码类型与 MSC指示的编码类型不一致导致 的 UE迁移失败的问题， 能够将 UE顺利迁移到目标 RNC上。
本申请实施例提供了另一种用户设备在无线网络控制器之间迁移的方 法， 如图 14所示， 所述方法是对图 13所示实施例的进一步扩展。
1401、 MSC接收源 RNC发送的编码类型变更请求消息。
若源 RNC根据 UE配置的编码类型以及目标 RNC支持的编码类型确 定 UE配置的编码类型与目标 RNC支持的编码类型不一致时， 向 MSC发 送编码类型变更请求消息，用于重配 UE配置的编码类型。所述编码类型变 更请求消息中携带有指定 UE要配置的编码类型。
需要说明的是， 网管或目标 RNC等节点需要向源 RNC发送目标 RNC 支持的编码类型，以便源 RNC能够根据 UE配置的编码类型以及目标 RNC 支持的编码类型判断 UE配置的编码类型与目标 RNC支持的编码类型是否 一致。
在本申请实施例的一个应用场景中， 当 UE 配置的编码类型为 WB AMR, 目标 RNC支持的编码类型为 NB AMR时 , 源 RNC向 MSC发送编 码类型变更请求消息， 该消息中携带具体指示 UE 重配的编码类型 （NB AMR ), MSC在接收到源 RNC发送的编码类型变更请求消息后， 执行步骤 1403 , 根据该编码类型变更请求消息通知源 RNC将 UE配置的编码类型重 配为 NB AMR。
1402、 MSC接收源 RNC发送的 UE不参与的 RNC迁移请求消息。 如果 UE配置的编码类型与目标 RNC支持的编码类型不一致时， 执行 步骤 1403 , 对 UE配置的编码类型进行重配。
1403、 MSC向源 RNC发送 UE编码类型的重配消息。
以便 UE根据该重配消息更改编码类型， 源 RNC在 UE完成编码类型 更改后， 发起 UE不参与的 RNC迁移过程， 完成对 UE的迁移过程。
另外， 在 1403步骤之前， MSC可先向源 RNC发送迁移失败消息， 指 示源 RNC等待接收 UE编码类型的重配消息或 UE配置的编码类型与目标 RNC支持的编码类型。
需要说明的是， 本步骤中所述的重配触发来源有二： 1 )该重配消息来 自步骤 1401 中源 RNC发送的编码类型变更请求消息， 该编码类型变更请 求消息中携带指定 UE使用的编码类型 (如步骤 1401中的 NB AMR )。 MSC 将指定 UE使用的编码类型携带于该重配消息中发送给源 RNC, 由源 RNC 根据该重配消息对 UE配置的编码类型进行重配。 2 ) MSC根据 UE配置的 编码类型以及目标 RNC支持的编码类型判断出 UE配置的编码类型与目标 RNC支持的编码类型不一致， 然后在重配消息中携带指定 UE使用的编码 类型 （如 NB AMR )发送给源 RNC。
1404、 MSC接收源 RNC发送的 UE不参与的 RNC迁移请求消息， 以 便完成 UE不参与的 RNC迁移过程。
源 RNC接收到 MSC发送的重配消息后对 UE配置的编码类型进行重 配， 然后发起 UE不参与的 RNC迁移过程。 由于重配后 UE配置的编码类 型与目标 RNC支持的编码类型一致了， 所以源 RNC发起的 UE不参与的 RNC迁移过程可以将 UE迁移到目标 RNC上。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够当 UE配置的编码类型与目标 RNC支持的编码类型不一致时向源 RNC 发送重配消息，由源 RNC根据该重配消息对 UE配置的编码类型进行重配， 然后发起 UE不参与的 RNC迁移过程将 UE从源 RNC迁移到目标 RNC上。 解决了现有技术中 UE配置的编码类型与目标 RNC支持的编码类型不一致 导致的 UE迁移失败的问题， 能够将 UE顺利迁移到目标 RNC上。
本申请实施例提供了一种用户设备在无线网络控制器之间迁移的方 法， 如图 15所示。 1501、 源 RNC向 MSC发送请求消息。
该请求消息包括编码类型变更请求消息或 UE不参与的 RNC迁移请求 消息。 当源 RNC确定 UE配置的编码类型与目标 RNC支持的编码类型不 一致时， 向 MSC发送编码类型变更请求消息， 该编码类型变更请求消息中 携带有指示 UE使用的编码类型。
需要说明的是， 源 RNC需要接收网管或或目标 RNC等节点目标 RNC 发送的目标 RNC支持的编码类型， 源 RNC根据 UE配置的编码类型以及 目标 RNC支持的编码类型判断 UE配置的编码类型与目标 RNC支持的编 码类型是否一致。
1502、 源 RNC接收 MSC发送的重配消息。
所述重配消息用于更改 UE配置的编码类型。所述重配消息的触发来源 有二： 1 )该重配消息来自步骤 1501中源 RNC发送的编码类型变更请求消 息， 该编码类型变更请求消息中携带指定 UE使用的编码类型。 MSC将指 定 UE使用的编码类型携带于该重配消息中发送给源 RNC ,由源 RNC根据 该重配消息对 UE配置的编码类型进行重配。 2 ) MSC根据 UE配置的编码 类型以及目标 RNC支持的编码类型判断出 UE配置的编码类型与目标 RNC 支持的编码类型不一致，然后在重配消息中携带指定 UE使用的编码类型发 送给源 RNC。
另外， 在 1502步骤之前， 源 RNC可先接收迁移失败消息， 该失败消 息指示源 RNC等待接收 UE编码类型的重配消息或 UE配置的编码类型与 目标 RNC支持的编码类型不一致。
1503、 源 RNC根据重配消息重配 UE的编码类型。
1504、 源 RNC发起 UE不参与的 RNC迁移过程。
源 RNC在根据 MSC发送的重配消息对 UE配置的编码类型进行重配 后， 发起 UE不参与的 RNC迁移过程， 完成对 UE的 RNC迁移。 由于源 RNC根据重配消息将 UE配置的编码类型重配为与目标 RNC支持的编码类 型一致的编码类型， 所以在原 NRC发起 UE不参与的 RNC迁移过程中不 会出现由于 UE配置的编码类型与目标 RNC支持的编码类型不一致造成的 UE迁移失败， 能够将 UE顺利迁移到目标 RNC上。
本申请实施例提供的用户设备在无线网络控制器之间迁移的方法， 能 够当 UE配置的编码类型与目标 RNC支持的编码类型不一致时向源 RNC 发送重配消息，由源 RNC根据该重配消息对 UE配置的编码类型进行重配， 然后发起 UE不参与的 RNC迁移过程将 UE从源 RNC迁移到目标 RNC上。 解决了现有技术中 UE配置的编码类型与目标 RNC支持的编码类型不一致 导致的 UE迁移失败的问题， 能够将 UE顺利迁移到目标 RNC上。
参考图 14所示方法实施例的实现， 本申请实施例提供了一种 MSC, 如图 16所示，用以实现图 14所示的方法实施例。所述 MSC包括：接收器 1601 , 用于接收源 RNC发送的请求消息； 发送器 1602, 用于向源 RNC发送 UE 编码类型的重配消息。
以便 UE根据该重配消息更改编码类型， 源 RNC在 UE完成编码类型 更改后， 发起 UE不参与的 RNC迁移过程， 完成对 UE的迁移过程。
需要说明的是， 本步骤中所述的重配消息的触发来源有二： 1 )该重配 消息来自源 RNC发送的编码类型变更请求消息， 该编码类型变更请求消息 中携带指定 UE使用的编码类型。 所述发送器 1602将指定 UE使用的编码 类型携带于该重配消息中发送给源 RNC, 由源 RNC根据该重配消息对 UE 配置的编码类型进行重配。 2 )MSC根据 UE配置的编码类型以及目标 RNC 支持的编码类型判断出 UE配置的编码类型与目标 RNC支持的编码类型不 一致， 然后在重配消息中携带指定 UE使用的编码类型发送给源 RNC。
进一步的， 所述接收器 1601还用于接收源 RNC发送的 UE不参与的 RNC迁移请求消息， 以便完成 UE不参与的 RNC迁移过程。
进一步的， 所述接收器 1601具体用于接收源 RNC发送的编码类型变 更请求消息， 该编码类型变更请求消息中携带有指定 UE要使用的编码类 型。
当源 RNC根据 UE配置的编码类型以及目标 RNC支持的编码类型确 定 UE配置的编码类型与目标 RNC支持的编码类型不一致时， 向 MSC发 送编码类型变更请求消息，用于重配 UE配置的编码类型。所述编码类型变 更请求消息中携带有指定 UE要使用的编码类型。 便源 RNC根据 UE配置的编码类型以及目标 RNC支持的编码类型判断 UE 配置的编码类型与目标 RNC支持的编码类型是否一致。
本申请实施例提供的 MSC,能够当 UE配置的编码类型与目标 RNC支 持的编码类型不一致时向源 RNC发送重配消息， 由源 RNC根据该重配消 息对 UE配置的编码类型进行重配， 然后发起 UE不参与的 RNC迁移过程 将 UE从源 RNC迁移到目标 RNC上。解决了现有技术中 UE配置的编码类 型与 MSC指示的编码类型不一致导致的 UE迁移失败的问题， 能够将 UE 顺利迁移到目标 RNC上。
参考图 15所示方法实施例的实现，本申请实施例提供了一种 RNC,如 图 17所示，用以实现图 15所示的方法实施例。所述 RNC包括：发送器 1701 , 用于向 MSC发送请求消息；接收器 1702,用于接收 MSC发送的重配消息， 该重配消息用于更改 UE配置的编码类型。
所述重配消息用于更改 UE配置的编码类型。所述重配消息的触发来源 有二： 1 )该重配消息来自源 RNC发送的编码类型变更请求消息， 该编码 类型变更请求消息中携带指定 UE使用的编码类型。 MSC将指定 UE使用 的编码类型携带于该重配消息中发送给源 RNC,由源 RNC根据该重配消息 对 UE配置的编码类型进行重配。 2 ) MSC根据 UE配置的编码类型以及目 标 RNC支持的编码类型判断出 UE配置的编码类型与目标 RNC支持的编 码类型不一致， 然后在重配消息中携带指定 UE使用的编码类型发送给源 RNC。 处理器 1703 , 用于根据所述重配消息重配所述 UE的编码类型。
进一步的，所述处理器 1703还用于在根据 MSC发送的重配消息对 UE 配置的编码类型进行重配后，发起 UE不参与的 RNC迁移过程，完成对 UE 的 RNC迁移。 由于源 RNC根据重配消息将 UE配置的编码类型重配为与 目标 RNC支持的编码类型一致的编码类型， 所以在所述处理器 1703发起 UE 不参与的 RNC 迁移过程中不会出现由于 UE 配置的编码类型与目标 RNC支持的编码类型不一致造成的 UE迁移失败， 能够将 UE顺利迁移到 目标 RNC上。
进一步的， 所述发送器 1701具体用于向 MSC发送编码类型变更请求 消息， 该消息中携带有指定 UE要使用的编码类型， 或者向 MSC发送 UE 不参与的 RNC迁移请求消息。
该请求消息包括编码类型变更请求消息和 UE不参与的 RNC迁移请求 消息。 当源 RNC确定 UE配置的编码类型与目标 RNC支持的编码类型不 一致时， 向 MSC发送编码类型变更请求消息， 该编码类型变更请求消息中 携带有指示 UE使用的编码类型。
进一步的， 所述发送器 1701还用于当确定 UE配置的编码类型与目标 RNC支持的编码类型不一致时， 向 MSC发送编码类型变更请求消息。
进一步的， 所述接收器 1702还用于接收网管或目标 RNC等节点发送 的目标 RNC支持的编码类型。
进一步的， 如图 18所示， 所述 RNC还包括： 判断器 1801 , 用于根据 目标 RNC支持的编码类型和 UE配置的编码类型确定 UE配置的编码类型 与目标 RNC支持的编码类型不一致。
本申请实施例提供的 RNC,能够当 UE配置的编码类型与目标 RNC支 持的编码类型不一致时向源 RNC发送重配消息， 由源 RNC根据该重配消 息对 UE配置的编码类型进行重配， 然后发起 UE不参与的 RNC迁移过程 将 UE从源 RNC迁移到目标 RNC上。解决了现有技术中 UE配置的编码类 型与目标 RNC支持的编码类型不一致导致的 UE迁移失败的问题， 能够将 UE顺利迁移到目标 RNC上。
进一步的， 本申请实施例提供了一种用户设备在无线网络控制器之间 迁移的系统， 所述系统涵盖了图 13至图 18所示方法和装置实施例的实现。 所述系统包括： MSC和源 RNC。
MSC, 接收源 RNC发送的请求消息， 向源 RNC发送 UE编码类型的 重配消息， 以便源 RNC重配 UE的编码类型 ,接收源 RNC发送的 UE不参 与的 RNC迁移请求消息， 以便完成 UE不参与的 RNC迁移过程。
源 RNC, 用于向 MSC发送请求消息， 接收 MSC发送的重配消息， 根 据重配消息重配所述 UE的编码类型， 发起 UE不参与的 RNC迁移过程。
本申请实施例提供的用户设备在无线网络控制器之间迁移的系统， 能 够当 UE配置的编码类型与目标 RNC支持的编码类型不一致时向源 RNC 发送重配消息，由源 RNC根据该重配消息对 UE配置的编码类型进行重配， 然后发起 UE不参与的 RNC迁移过程将 UE从源 RNC迁移到目标 RNC上。 解决了现有技术中 UE配置的编码类型与目标 RNC支持的编码类型不一致 导致的 UE迁移失败的问题， 能够将 UE顺利迁移到目标 RNC上。
需要说明的是， 由于 CN (或 MSC )为 UE和目标 RNC指示编码类型 是基于目标 RNC支持的编码类型而指示的， 所以本申请所有实施例中所述 的"目标 RNC支持的编码类型"和所述的" CN (或 MSC )为 UE和目标 RNC 指示的编码类型"为同一含义的不同表述方式， 其含义都为目标 RNC 支持 的编码类型。
通过以上的实施方式的描述， 所属领域的技术人员可以清楚地了解到 本申请可借助软件加必需的通用硬件的方式来实现， 当然也可以通过硬件， 但很多情况下前者是更佳的实施方式。 基于这样的理解， 本申请的技术方 案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出 来， 该计算机软件产品存储在可读取的存储介质中， 如计算机的软盘， 硬 盘或光盘等， 包括若干指令用以使得一台计算机设备（可以是个人计算机， 服务器， 或者网络设备等）执行本申请各个实施例所述的方法。
以上所述， 仅为本申请的具体实施方式， 但本申请的保护范围并不局 限于此， 任何熟悉本技术领域的技术人员在本申请揭露的技术范围内， 可 轻易想到变化或替换， 都应涵盖在本申请的保护范围之内。 因此， 本申请 的保护范围应所述以权利要求的保护范围为准。

Claims

权利要求
1、 一种用户设备在无线网络控制器之间迁移的方法， 其特征在于， 包 括：
接收用户设备 UE不参与的无线网络控制器 RNC迁移请求消息， 所述 请求消息中携带有源 RNC发送的源 RNC到目标 RNC的透明容器和核心网 CN指示的编码类型， 所述透明容器包含所述 UE配置的编码类型；
若所述 UE配置的编码类型与所述 CN指示的编码类型不一致 ,向所述 源 RNC发送目标 RNC到源 RNC的透明容器，所述透明容器携带用于更改 所述 UE编码类型的重配消息， 以便所述源 RNC发送重配消息给所述 UE。
2、 一种用户设备在无线网络控制器之间迁移的方法， 其特征在于， 包 括：
向核心网 CN发送用户设备 UE不参与的无线网络控制器 RNC迁移请 求消息， 以便所述 CN向所述目标 RNC发送迁移请求消息；
接收所述 CN发送的迁移命令消息，所述迁移命令消息中包含所述目标 RNC发送的目标 RNC到源 RNC的透明容器， 所述透明容器中包含 UE编 码类型的重配消息；
向所述 UE发送重配消息，以便所述 UE根据所述重配消息更改编码类 型。
3、 一种用户设备在无线网络控制器之间迁移的方法， 其特征在于， 包 括：
在发起迁移时，若用户设备 UE的无线链路在目标无线网络控制器 RNC 控制下， 确定源 RNC不知道目标 RNC支持的编码类型或确定所述 UE配 置的编码类型与所述目标 RNC支持的编码类型不一致或确定所述 UE存在 宽带自适应多速率承载；
发起 UE参与的 RNC迁移过程。
4、根据权利要求 3所述的用户设备在无线网络控制器之间迁移的方法， 其特征在于， 所述确定所述 UE配置的编码类型与所述目标 RNC支持的编 码类型不一致， 包括：
发送 UE不参与的 RNC切换请求消息到核心网 CN;
接收所述 CN发送的迁移失败消息， 所述迁移失败消息用于指示所述 UE配置的编码类型与所述目标 RNC支持的编码类型不一致。
5、根据权利要求 3所述的用户设备在无线网络控制器之间迁移的方法， 其特征在于， 若所述 UE的无线链路在目标 RNC控制下， 还包括： 所述确定所述 UE配置的编码类型与所述目标 RNC支持的编码类型不 一致为： 确定所述 UE配置的编码类型与所述网管节点或所述目标 RNC发 送的所述目标 RNC支持的编码类型不一致。
6、 一种用户设备在无线网络控制器之间迁移的方法， 其特征在于， 包 括：
接收源无线网络控制器 RNC发送的用户设备 UE不参与的 RNC迁移 请求消息；
若所述 UE配置的编码类型与目标 RNC支持的编码类型不一致， 向所 述源 RNC发送迁移失败消息， 以便所述源 RNC根据所述迁移失败消息发 起 UE参与的 RNC迁移过程。
7、 一种用户设备在无线网络控制器之间迁移的方法， 其特征在于， 包 括：
接收源无线网络控制器 RNC发送的请求消息；
向所述源 RNC发送用户设备 UE编码类型的重配消息， 以便所述源 RNC重配所述 UE的编码类型；
接收源 RNC发送的 UE不参与的 RNC迁移请求消息，以便完成 UE不 参与的 RNC迁移过程。
8、根据权利要求 7所述的用户设备在无线网络控制器之间迁移的方法， 其特征在于， 所述接收源 RNC发送的请求消息， 包括：
接收所述源 RNC发送的编码类型变更请求消息， 所述编码类型变更请 求消息中携带有指定所述 UE要配置的编码类型； 或者 ,
接收所述源 RNC发送的 UE不参与的 RNC迁移请求消息。
9、根据权利要求 8所述的用户设备在无线网络控制器之间迁移的方法， 其特征在于， 在所述接收所述源 RNC发送的 UE不参与的 RNC迁移请求 消息之后， 还包括：
若所述 UE配置的编码类型与所述目标 RNC支持的编码类型不一致， 向所述源 RNC发送重配消息。
10、 一种用户设备在无线网络控制器之间迁移的方法， 其特征在于， 包括：
向核心网 CN发送请求消息；
接收所述 CN发送的重配消息；
根据所述重配消息重配用户设备 UE的编码类型；
发起 UE不参与的无线网络控制器 RNC迁移过程。
11、 根据权利要求 10所述的用户设备在无线网络控制器之间迁移的方 法， 其特征在于， 所述向核心网 CN发送请求消息， 包括：
向所述 CN发送编码类型变更请求消息， 所述消息中携带有指定所述 UE要配置的编码类型； 或者，
向所述 CN发送 UE不参与的 RNC迁移请求消息。
12、 根据权利要求 11所述的用户设备在无线网络控制器之间迁移的方 法， 其特征在于， 在所述向所述 CN发送编码类型变更请求消息之前，还包 括：
接收网管节点或目标 RNC发送的所述目标 RNC支持的编码类型； 确定所述 UE配置的编码类型与所述目标 RNC支持的编码类型不一致。
13、 一种无线网络控制器 RNC, 其特征在于， 包括： 接收器， 用于接收用户设备 UE不参与的 RNC迁移请求消息， 所述请 求消息中携带有源 RNC发送的源 RNC到目标 RNC的透明容器和核心网 CN指示的编码类型， 所述透明容器包含所述 UE配置的编码类型；
发送器， 用于向所述源 RNC发送目标 RNC到源 RNC的透明容器， 所 述透明容器携带用于更改所述 UE编码类型的重配消息， 以便所述源 RNC 发送重配消息给所述 UE。
14、 一种无线网络控制器 RNC, 其特征在于， 包括：
发送器， 用于向核心网 CN发送用户设备 UE不参与的 RNC迁移请求 消息， 以便所述 CN向所述目标 RNC发送迁移请求消息；
接收器，用于接收所述 CN发送的迁移命令消息，所述迁移命令消息中 包含所述目标 RNC发送的目标 RNC到源 RNC的透明容器，所述透明容器 中包含 UE编码类型的重配消息；
所述发送器还用于向所述 UE发送重配消息，以便所述 UE根据所述重 配消息更改编码类型。
15、 一种无线网络控制器 RNC, 其特征在于， 包括：
判断器，用于确定源 RNC不知道目标 RNC支持的编码类型或确定所述 UE配置的编码类型与所述目标 RNC支持的编码类型不一致或确定所述 UE 存在宽带自适应多速率承载；
处理器， 用于发起 UE参与的 RNC迁移过程。
16、 根据权利要求 15所述的 RNC, 其特征在于， 还包括：
发送器， 用于发送 UE不参与的 RNC切换请求消息到核心网 CN; 接收器，用于接收所述 CN发送的迁移失败消息，所述迁移失败消息用 于指示所述 UE配置的编码类型与所述目标 RNC支持的编码类型不一致。
17、根据权利要求 15所述的 RNC, 其特征在于， 所述接收器还用于接 所述判断器还用于确定所述 UE 配置的编码类型与所述网管节点或所 述目标 RNC发送的所述目标 RNC支持的编码类型不一致。
18、 一种核心网 CN, 其特征在于， 包括：
接收器， 用于接收源无线网络控制器 RNC发送的用户设备 UE不参与 的 RNC迁移请求消息；
发送器， 用于向所述源 RNC发送迁移失败消息， 以便所述源 RNC根 据所述迁移失败消息发起 UE参与的 RNC迁移过程。
19、 一种核心网 CN, 其特征在于， 包括：
接收器， 用于接收源无线网络控制器 RNC发送的请求消息； 发送器， 用于向所述源 RNC发送用户设备 UE编码类型的重配消息， 以便所述源 RNC重配所述 UE的编码类型；
所述接收器还用于接收源 RNC发送的 UE不参与的 RNC迁移请求消 息， 以便完成 UE不参与的 RNC迁移过程。
20、 根据权利要求 19所述的 CN, 其特征在于， 所述接收器具体用于 接收所述源 RNC发送的编码类型变更请求消息， 所述编码类型变更请求消 息中携带有指定所述 UE要配置的编码类型；
所述接收器还具体用于接收所述源 RNC发送的 UE不参与的 RNC迁 移请求消息。
21、 根据权利要求 20所述的 CN, 其特征在于， 所述发送器还用于向 所述源 RNC发送重配消息。
22、 一种无线网络控制器 RNC, 其特征在于， 包括：
发送器， 用于向核心网 CN发送请求消息；
接收器， 用于接收所述 CN发送的重配消息；
处理器， 用于根据所述重配消息重配所述 UE的编码类型；
所述处理器还用于发起用户设备 UE不参与的 RNC迁移过程。
23、根据权利要求 22所述的 RNC, 其特征在于， 所述发送器具体用于 向所述 CN发送编码类型变更请求消息，所述消息中携带有指定所述 UE要 配置的编码类型；
所述发送器还具体用于向所述 CN发送 UE不参与的 RNC迁移请求消 息。
24、根据权利要求 23所述的 RNC, 其特征在于， 所述接收器还用于接 收网管节点或目标 RNC发送的所述目标 RNC支持的编码类型；
所述 RNC还包括判断器， 用于确定所述 UE配置的编码类型与所述目 标 RNC支持的编码类型不一致。
25、 一种用户设备在无线网络控制器之间迁移的系统， 其特征在于， 包括：
目标无线网络控制器 RNC,用于接收用户设备 UE不参与的 RNC迁移 请求消息，所述请求消息中携带有源 RNC发送的源 RNC到目标 RNC的透 明容器和核心网 CN指示的编码类型，所述透明容器包含所述 UE配置的编 码类型， 若所述 UE配置的编码类型与所述 CN指示的编码类型不一致， 向 所述源 RNC发送目标 RNC到源 RNC的透明容器，所述透明容器携带用于 更改所述 UE编码类型的重配消息， 以便所述源 RNC发送重配消息给所述 UE;
源 RNC, 用于向所述 CN发送 UE不参与的 RNC迁移请求消息， 以便 所述 CN向所述目标 RNC发送迁移请求消息， 接收所述 CN发送的迁移命 令消息，所述迁移命令消息中包含所述目标 RNC发送的目标 RNC到源 RNC 的透明容器， 所述透明容器中包含 UE编码类型的重配消息， 向所述 UE发 送重配消息， 以便所述 UE根据所述重配消息更改编码类型。
26、 一种用户设备在无线网络控制器之间迁移的系统， 其特征在于， 包括：
源无线网络控制器 RNC, 用于在发起迁移时， 若用户设备 UE的无线链 路在目标 RNC控制下，确定源 RNC不知道目标 RNC支持的编码类型或确 定所述 UE配置的编码类型与所述目标 RNC支持的编码类型不一致或确定 所述 UE存在宽带自适应多速率承载， 发起 UE参与的 RNC迁移过程； 核心网 CN, 用于接收源 RNC发送的 UE不参与的 RNC迁移请求消息， 若所述 UE配置的编码类型与目标 RNC支持的编码类型不一致， 向所述源 RNC发送迁移失败消息， 以便所述源 RNC根据所述迁移失败消息发起 UE 参与的 RNC迁移过程。
27、 一种用户设备在无线网络控制器之间迁移的系统， 其特征在于， 包 括：
核心网 CN, 接收源无线网络控制器 RNC发送的请求消息， 向所述源 RNC发送用户设备 UE编码类型的重配消息， 以便所述源 RNC重配所述 UE的编码类型， 接收源 RNC发送的 UE不参与的 RNC迁移请求消息， 以 便完成 UE不参与的 RNC迁移过程；
源 RNC, 用于向 CN发送请求消息，接收所述 CN发送的重配消息， 根据 所述重配消息重配所述 UE的编码类型， 发起 UE不参与的 RNC迁移过程。
PCT/CN2012/084637 2012-01-05 2012-11-15 用户设备在无线网络控制器之间迁移的方法、装置及系统 WO2013102374A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP12864468.9A EP2793509A4 (en) 2012-01-05 2012-11-15 METHOD, APPARATUS AND SYSTEM FOR RELOCATING RADIO EQUIPMENT BETWEEN RADIO NETWORK CONTROLLERS
US14/324,946 US9167490B2 (en) 2012-01-05 2014-07-07 Method, apparatus and system for relocating user equipment between radio network controllers
US14/853,637 US9392507B2 (en) 2012-01-05 2015-09-14 Method, apparatus and system for relocating user equipment between radio network controllers

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201210002252.9 2012-01-05
CN201210002252 2012-01-05
CN201210128354.5A CN103200635B (zh) 2012-01-05 2012-04-27 用户设备在无线网络控制器之间迁移的方法、装置及系统
CN201210128354.5 2012-04-27

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/324,946 Continuation US9167490B2 (en) 2012-01-05 2014-07-07 Method, apparatus and system for relocating user equipment between radio network controllers

Publications (1)

Publication Number Publication Date
WO2013102374A1 true WO2013102374A1 (zh) 2013-07-11

Family

ID=48722954

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/084637 WO2013102374A1 (zh) 2012-01-05 2012-11-15 用户设备在无线网络控制器之间迁移的方法、装置及系统

Country Status (4)

Country Link
US (2) US9167490B2 (zh)
EP (1) EP2793509A4 (zh)
CN (1) CN103200635B (zh)
WO (1) WO2013102374A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111901391A (zh) * 2017-08-30 2020-11-06 王梅 在不同数据域内的设备间进行数据交换的方法及系统
US11570672B2 (en) * 2018-02-09 2023-01-31 Beijing Xiaomi Mobile Software Co., Ltd. Handover method between base stations, device, system and storage medium
EP3797543B1 (en) * 2018-05-23 2022-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Methods for indication of radio access technology
US11601858B2 (en) 2018-09-03 2023-03-07 Telefonaktiebolaget Lm Ericsson (Publ) Relocation of a user equipment connection from a source radio network controller RNC to a target RNC initiated via a core network
CN109714750B (zh) * 2018-12-18 2020-12-22 Oppo广东移动通信有限公司 通话方法、装置、电子终端及介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101262639A (zh) * 2007-03-06 2008-09-10 华为技术有限公司 服务无线网络控制器迁移方法及无线网络控制器
CN101365165A (zh) * 2007-08-10 2009-02-11 中兴通讯股份有限公司 传递用于减小高速下行共享控制信道负荷参数的方法

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6618589B1 (en) * 1999-10-27 2003-09-09 Telefonaktiebolaget Lm Ericsson (Publ) Method for performing cell and URA updates in a radio access network
SE0100475D0 (sv) * 2001-02-09 2001-02-09 Ericsson Telefon Ab L M Method and system of retransmission
US6845095B2 (en) * 2001-04-27 2005-01-18 Telefonaktiebolaget Lm Ericsson (Publ) Efficient header handling involving GSM/EDGE radio access networks
US20030003919A1 (en) * 2001-06-29 2003-01-02 Per Beming Relocation of serving network radio network controller ( SRNC) which has used direct transport bearers between SRNC and base station
CN1703736A (zh) 2002-10-11 2005-11-30 诺基亚有限公司 用于源控制可变比特率宽带语音编码的方法和装置
CN1499760A (zh) * 2002-11-05 2004-05-26 ��������ͨ�ż����о����޹�˾ 多媒体广播与组播业务在Iu接口的信令承载连接方法
US7596380B2 (en) * 2004-07-26 2009-09-29 Lg Electronics Inc. Changing serving radio network controller for mobile terminal supporting multimedia broadcast services
GB0422836D0 (en) * 2004-10-13 2004-11-17 Nokia Corp Communications network
ATE538554T1 (de) * 2005-08-16 2012-01-15 Panasonic Corp Verfahren und vorrichtungen für das zurücksetzen einer sendesequenznummer (tsn)
CA2667611C (en) * 2006-11-07 2013-01-08 Qualcomm Incorporated Method and apparatus for serving radio network subsystem relocation in wireless communication systems
CN101938801B (zh) * 2009-06-30 2013-08-07 中兴通讯股份有限公司 一种实现网络间重定位的方法及系统
GB2496959B (en) * 2012-11-02 2014-05-21 Broadcom Corp Method and apparatus for obtaining reliable e-dch reception for transmission of scheduling information

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101262639A (zh) * 2007-03-06 2008-09-10 华为技术有限公司 服务无线网络控制器迁移方法及无线网络控制器
CN101365165A (zh) * 2007-08-10 2009-02-11 中兴通讯股份有限公司 传递用于减小高速下行共享控制信道负荷参数的方法

Also Published As

Publication number Publication date
EP2793509A4 (en) 2015-08-05
US9167490B2 (en) 2015-10-20
US20140323132A1 (en) 2014-10-30
US9392507B2 (en) 2016-07-12
CN103200635B (zh) 2016-06-29
EP2793509A1 (en) 2014-10-22
CN103200635A (zh) 2013-07-10
US20160007246A1 (en) 2016-01-07

Similar Documents

Publication Publication Date Title
JP6890687B2 (ja) マスタ基地局始動のセカンダリ基地局解放とセカンダリ基地局始動のセカンダリ基地局変更手続きとの間の競合状態の回避
WO2019166032A1 (zh) 通信方法及装置
CN116326174A (zh) 用于主节点发起的条件主辅助小区添加的系统和方法
RU2741051C1 (ru) Обработка pdcp во время повторного установления соединения
EP4154591A1 (en) Preserving cell group addition/change configuration on handover
WO2014198133A1 (zh) 一种数据无线承载drb的资源分配方法及装置
CN111727628B (zh) 用于无线电接入技术间切换的方法
CN115997413A (zh) Cu间迁移中的iab节点切换
CN113950806B (zh) 4g系统中的用户平面完整性保护
BR112013027871B1 (pt) Método para sincronização de um estado de camada física, controlador de rede de rádio de serviço (srnc), estação base e sistema para sincronização de um estado de camada física
WO2013102374A1 (zh) 用户设备在无线网络控制器之间迁移的方法、装置及系统
JP2016529811A (ja) サービス移行方法、関連装置およびコンピュータ記憶媒体
US20230269647A1 (en) Control Plane Aspects of Dual Active Protocol Stack Handover Report
WO2022078112A1 (zh) 连接建立方法、装置、设备及存储介质
CN116326170A (zh) Scg挂起/休眠/停用-信令、配置和行为
EP4218293A1 (en) Canceling of conditional pscell addition
RU2763449C1 (ru) Индикатор базовой сети и обработка обеспечения безопасности для передачи обслуживания
WO2020168913A1 (zh) 切换方法、装置及通信设备
TW201824936A (zh) 上下文釋放方法、設備及系統
CN114467361A (zh) 在多无线电双连接中恢复无线电连接
WO2019119236A1 (zh) 网络重定向方法及终端、接入网设备、移动管理设备
JP2024509905A (ja) デュアルアクティブプロトコルスタックフォールバックの後の無線リンク障害のための自己組織化ネットワーク報告に対する拡張
CN111903155B (zh) 具有核心网络改变的rat内切换
JP2018174597A (ja) ベアラ管理装置、方法及び通信システム
US20240187929A1 (en) Methods for revoking inter-donor topology adaptation in integrated access and backhaul networks

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012864468

Country of ref document: EP