WO2018024128A1 - 一种小区配置方法及装置 - Google Patents

一种小区配置方法及装置 Download PDF

Info

Publication number
WO2018024128A1
WO2018024128A1 PCT/CN2017/094108 CN2017094108W WO2018024128A1 WO 2018024128 A1 WO2018024128 A1 WO 2018024128A1 CN 2017094108 W CN2017094108 W CN 2017094108W WO 2018024128 A1 WO2018024128 A1 WO 2018024128A1
Authority
WO
WIPO (PCT)
Prior art keywords
scg
scg configuration
configuration information
information
senb
Prior art date
Application number
PCT/CN2017/094108
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 KR1020197006344A priority Critical patent/KR102180383B1/ko
Priority to EP17836310.7A priority patent/EP3496448A1/en
Priority to JP2019506437A priority patent/JP2019525625A/ja
Priority to US16/323,229 priority patent/US20190182883A1/en
Publication of WO2018024128A1 publication Critical patent/WO2018024128A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/32—Hierarchical cell structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • 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/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present application relates to the field of mobile communications technologies, and in particular, to a cell configuration method and apparatus.
  • LTE-A Long Term Evolution-Advanced
  • New RAT new radio access
  • the dual connectivity technology means that the user equipment (UE) can simultaneously transmit uplink and downlink traffic using the wireless spectrum resources of the two base stations, and the two base stations distribute and manage their respective cells, and manage
  • the base station of the master cell group (MCG) is a macro base station (MeNB), that is, the primary base station, and the base station that manages the secondary cell group (SCG) is a small base station (SeNB), that is, a secondary base station, and the macro base station is mainly responsible for coverage and mobility, the small base station is responsible for the offloading of uplink and downlink data services to improve the peak throughput of users.
  • MCG master cell group
  • SCG secondary cell group
  • SCG small base station
  • the small base station is responsible for the offloading of uplink and downlink data services to improve the peak throughput of users.
  • RRC radio resource control
  • the RRC connection fails in the base station switching configuration, whether the MCG configuration fails or the SCG configuration fails, the RRC re-establishment is required through the MCG.
  • This method occupies the wireless resources of the MCG and seriously affects the relationship between the user and the MCG. Normal data communication.
  • a user equipment of the LTE-A dual connectivity technology is taken as an example.
  • the user equipment needs one MeNB and at least one SeNB, and the user equipment can communicate with the base station only after the RRC connection is successfully established.
  • only the MeNB can generate the last RRC message and deliver the RRC message to the user equipment and establish an RRC connection.
  • the specific steps are as follows:
  • the MeNB provides the user equipment configuration to the SeNB. Parameters (such as the capabilities of the user equipment, the radio resource configuration of the user equipment, etc.); after receiving the user equipment configuration parameters sent by the MeNB, the SeNB generates corresponding SCG configuration information [eg, physical uplink control channel (Physical Uplink Control Channel).
  • SCG configuration information eg, physical uplink control channel (Physical Uplink Control Channel).
  • the PUCCH configuration information is fed back to the MeNB.
  • the MeNB generates a final RRC message based on the locally configured MCG configuration information and the SCG configuration information provided by the SeNB, and sends the RRC message to the user equipment to establish an RRC connection.
  • CA carrier aggregation
  • the MeNB saves radio resource management (RRM) measurement configuration information of the user equipment, and determines whether the SeNB needs to provide an additional serving cell for the user equipment by using the received measurement report (such as service status, bearer type, and the like).
  • the resource such as the SCells of the SCG, etc.
  • the SeNB determines whether to increase the configuration of the serving cell for the user equipment according to the request information received from the MeNB.
  • the MeNB and the SeNB perform information exchange through the X2 interface (eg, the MeNB sends the UE configuration parameter to the SeNB, the SeNB sends the SCG configuration information to the MeNB, etc.); accordingly, the MeNB also generates a part of the SCG configuration locally.
  • the MeNB generates the final RRC message and sends the final RRC message to the user equipment, in combination with the SCG configuration information generated by the SeNB and the SCG configuration information sent by the SeNB, and the MCG information generated by the MCG.
  • the MeNB does not change the SCG configuration information uploaded by the SeNB.
  • the MCG configuration and the SCG configuration are performed. If the MCG configuration is successful, once the SCG configuration fails, the user terminal considers that the RRC connection fails, and notifies the MeNB to initiate the RRC reestablishment. However, after the MCG is successfully configured, the user equipment can communicate normally. Therefore, once the MeNB initiates RRC reestablishment based on the SCG configuration failure, severe data interruption will occur, which seriously affects the normal communication of the user equipment.
  • LTE and NR tightinterworking in a 5G system are taken as an example.
  • the RRC message can be generated by the MCG and can be generated by the SCG.
  • the RRC message is transmitted through the primary signaling radio bearer (Signaling Radio Bearer, SRB, referred to as the primary bearer).
  • SRB1 is sent to the user equipment.
  • the RRC message is generated by the SCG, the RRC message is sent to the user equipment through a secondary bearer (SRB on the secondary), such as SRB3.
  • the configuration information of the SCG can be delivered in the following two manners:
  • Manner 1 The SCG configuration information and the MCG configuration information are sent by the MCG to the user equipment. In this mode, if the RRC connection fails, the configuration information of the MCG fails or the configuration information of the SCG fails. The agreement is determined to be initiated by the MCG for RRC re-establishment.
  • the SCG configuration information is sent by the SCG to the user equipment.
  • the MCG configuration information is sent by the MCG to the user equipment, that is, the corresponding configuration information is delivered. In this mode, if the SCG configuration information fails, the MCG configuration fails. If the information is successful, the agreement will also determine that the RRC re-establishment is initiated by the MCG.
  • the embodiment of the present application provides a cell configuration method and apparatus, to avoid serious data interruption, and to ensure normal communication of user equipment.
  • a cell configuration method is applied to a scenario in which a primary base station MeNB and a secondary base station SeNB work together, including:
  • the first base station triggers setting the secondary cell group SCG configuration information
  • the first base station triggers sending the SCG configuration information to the user equipment UE, and triggers the UE to perform SCG configuration;
  • the first base station When the first base station receives the SCG reconfiguration failure information, it is determined that the UE fails to perform the SCG configuration, and when it is determined that the primary cell group MCG configuration is successful, the triggering maintains the original SCG configuration information that is not previously sent, or triggers the SCG release. .
  • the first base station triggers setting the SCG configuration information, including:
  • the first base station triggers the SeNB to set corresponding SCG configuration information for the UE.
  • the first base station If the first base station is the SeNB, the first base station directly triggers local setting of corresponding SCG configuration information for the UE.
  • the first base station triggers sending the SCG configuration information to the UE, including:
  • the first base station sends the locally set MCG configuration information and the SCG configuration information set by the SeNB to the UE by using the first message; or the first base station uses the first message to configure the SCG configured by the SeNB.
  • Information is sent to the UE;
  • the first base station sends the locally set SCG configuration information to the UE by using the first message.
  • determining that the UE fails to perform SCG configuration including:
  • the first base station If the first base station is the MeNB, the first base station directly receives the SCG reconfiguration failure information sent by the UE, and determines that the UE fails to perform the SCG configuration.
  • the first base station determines, when the SCG reconfiguration failure information sent by the MeNB is received, The UE performs the SCG configuration failure.
  • the SCG reconfiguration failure information sent by the MeNB is sent by the MeNB to the first base station after receiving the SCG reconfiguration failure information sent by the UE.
  • the first base station determines that the UE fails to perform the SCG configuration, and when determining that the MCG configuration is successful, triggering to maintain the original SCG configuration information that is sent last time, including:
  • the first base station determines that the UE performs the SCG configuration failure, and if it determines that the MCG configuration is successful, uses the successfully configured MCG configuration information, and sends the SCG reconfiguration failure information to the SeNB, triggering the SeNB to maintain the last time.
  • the original SCG configuration information is unchanged; or the first base station determines that the UE fails to perform the SCG configuration, maintains the original MCG configuration information, and sends the SCG reconfiguration failure information to the SeNB, triggering the SeNB to maintain the original SCG that was previously delivered.
  • the configuration information remains unchanged; or,
  • the first base station determines that the UE fails to perform the SCG configuration, and determines that the original SCG configuration information that was previously delivered is unchanged after the MCG configuration is successful.
  • the first base station determines that the UE performs the SCG configuration failure, and when determining that the MCG configuration is successful, triggering the execution of the SCG release, including:
  • the first base station determines that the UE performs the SCG configuration failure, and if it determines that the MCG configuration is successful, uses the successfully configured MCG configuration information, and sends the SCG reconfiguration failure information to the SeNB, triggering the SeNB to perform the SCG release; Or, after the first base station determines that the UE fails to perform the SCG configuration, the original MCG configuration information is maintained, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or
  • the first base station determines that the UE fails to perform SCG configuration, and after determining that the MCG configuration is successful, performs SCG release.
  • the first base station acquires a corresponding SCG configuration failure reason based on the received SCG reconfiguration failure information, and triggers resetting and resending the corresponding new SCG configuration information based on the SCG configuration failure reason.
  • the first base station triggers the re-setting and re-issuing the corresponding new SCG configuration information, according to the reason for the failure of the SCG configuration, including:
  • the first base station sends the SCG configuration failure reason to the SeNB, and triggers the SeNB to reset the new SCG configuration information and send the new SCG configuration information to the first base station based on the SCG configuration failure reason. And sending, by the first base station, to the UE, or triggering the SeNB to reset the new SCG configuration information and send the new SCG configuration information to the UE according to the SCG configuration failure reason;
  • the first base station receives the SCG configuration failure reason sent by the MeNB, and directly triggers the local SCG configuration information to be newly set based on the SCG configuration failure reason, and sends the new SCG configuration information to the MeNB. And being sent by the MeNB to the UE, or the first base station directly sends the new SCG configuration information to the UE.
  • the first base station triggers to reset the new SCG configuration information based on the cause of the failure of the SCG configuration.
  • the first base station triggers the SeNB to perform any of the following operations:
  • the new SCG configuration information is reset according to a preset manner.
  • the MeNB re-negotiates, and after the UE capability is re-evaluated, the new SCG configuration information is reset according to the evaluation result;
  • the SCG configuration information that fails to be configured is adjusted accordingly, and the new SCG configuration information is reset according to the adjustment result.
  • a cell configuration method is applied to a scenario in which a primary base station MeNB and a secondary base station SeNB work together, including:
  • the user equipment UE performs SCG configuration according to the secondary cell group SCG configuration information delivered by the network side;
  • the SCG reconfiguration failure information is sent to the network side;
  • the UE determines that the primary cell group MCG configuration is successful, the original SCG configuration information that is sent by the network side is maintained unchanged, or the SCG release is performed.
  • the original SCG configuration information that is sent by the network side is maintained unchanged, or the SCG release is performed, including:
  • the UE If the UE also receives the MCG configuration information that is sent by the network, and determines that the MCG configuration is successful, the UE uses the configured MCG configuration information, and maintains the original SCG configuration information that was delivered last time, or performs SCG release.
  • the UE If the UE does not receive the MCG configuration information sent by the network, the UE maintains the original MCG configuration information that was delivered last time, and maintains the original SCG configuration information that was delivered last time or performs SCG release.
  • the method before the sending, by the UE, the SCG reconfiguration failure information to the network side, the method further includes:
  • the UE determines a cause of the SCG configuration failure, and generates a corresponding SCG reconfiguration failure information based on the SCG configuration failure reason.
  • the reason for the failure of the SCG configuration determined by the UE includes any one of the following reasons:
  • a cell configuration apparatus is applied to a scenario in which a primary base station MeNB and a secondary base station SeNB work together, including:
  • a first triggering unit configured to trigger setting a secondary cell group SCG configuration information
  • a second triggering unit configured to trigger sending the SCG configuration information to the user equipment UE, and triggering the UE to perform SCG configuration
  • a processing unit configured to determine, when receiving the SCG reconfiguration failure information, that the UE fails to perform SCG configuration, and When it is determined that the primary cell group MCG configuration is successful, the triggering maintains the original SCG configuration information that was previously delivered unchanged, or triggers the execution of the SCG release.
  • the first trigger unit when triggering setting SCG configuration information, is configured to:
  • the SeNB is triggered to set corresponding SCG configuration information for the UE.
  • the device is an SeNB, the corresponding SCG configuration information is set for the UE directly.
  • the second triggering unit is configured to trigger sending the SCG configuration information to the UE by:
  • the first message is used to send the locally set MCG configuration information and the SCG configuration information set by the SeNB to the UE; or the first message is used to send the SCG configuration information set by the SeNB to the UE;
  • the first message is used to directly send the locally set SCG configuration information to the UE.
  • the processing unit is configured to: when receiving the SCG reconfiguration failure information, determine that the UE performs the SCG configuration failure:
  • the device is a MeNB, if the SCG reconfiguration failure information sent by the UE is directly received, it is determined that the UE fails to perform SCG configuration;
  • the SeNB is the SeNB
  • the UE determines that the UE performs the SCG configuration failure.
  • the SCG reconfiguration failure information sent by the MeNB is after the MeNB receives the SCG reconfiguration failure information sent by the UE. , sent to the device.
  • the processing unit is configured to determine that the UE performs the SCG configuration failure in the following manner, and when determining that the MCG configuration is successful, triggering to maintain the original SCG configuration information that is last delivered:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original delivery.
  • the SCG configuration information is unchanged; or, after determining that the UE fails to perform the SCG configuration, the original MCG configuration information is maintained unchanged, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original SCG configuration information that is delivered last time; ,
  • the device is the SeNB, it is determined that the UE fails to perform the SCG configuration, and after determining that the MCG configuration is successful, the original SCG configuration information that was previously delivered is maintained.
  • the processing unit is configured to determine that the UE performs SCG configuration failure in the following manner, and triggers execution of SCG release when determining that the MCG configuration is successful:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or, After the UE performs the SCG configuration, the original MCG configuration information is maintained, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or
  • the device is a SeNB, it is determined that the UE fails to perform SCG configuration, and after determining that the MCG configuration is successful, performing SCG release.
  • processing unit is further configured to:
  • the reason for the failure of the corresponding SCG configuration is obtained based on the received SCG reconfiguration failure information, and the corresponding new SCG configuration information is triggered and re-issued based on the failure reason of the SCG configuration.
  • the processing unit is configured to trigger re-setting and re-issue the corresponding new SCG configuration information according to the SCG configuration failure reason in the following manner:
  • the SCG configuration failure reason is sent to the SeNB, and the SeNB is triggered to reset the new SCG configuration information and send the new SCG configuration information to the device according to the SCG configuration failure reason.
  • the device is sent to the UE, or the SeNB is triggered to reset the new SCG configuration information and send the new SCG configuration information to the UE according to the SCG configuration failure reason;
  • the device is a SeNB, after receiving the SCG configuration failure reason sent by the MeNB, directly triggering to newly reset the new SCG configuration information based on the SCG configuration failure reason, and sending the new SCG configuration information to the MeNB, by the MeNB The information is sent to the UE, or the new SCG configuration information is directly sent to the UE.
  • the processing unit is configured to trigger the SeNB to perform any one of the following operations when the new SCG configuration information is triggered to be reset based on the SCG configuration failure reason:
  • the new SCG configuration information is reset according to a preset manner.
  • the MeNB re-negotiates, and after the UE capability is re-evaluated, the new SCG configuration information is reset according to the evaluation result;
  • the SCG configuration information that fails to be configured is adjusted accordingly, and the new SCG configuration information is reset according to the adjustment result.
  • a cell configuration apparatus is applied to a scenario in which a primary base station MeNB and a secondary base station SeNB work together, including:
  • a configuration unit configured to perform SCG configuration according to the secondary cell group SCG configuration information delivered by the network side;
  • a communication unit configured to send, when the SCG configuration fails, send the SCG reconfiguration failure information to the network side;
  • the processing unit is configured to: when the primary cell group MCG configuration is successful, maintain the original SCG configuration information that is sent last time on the network side, or perform SCG release.
  • the processing unit is configured to: when the MCG configuration is successful, when the original SCG configuration information sent by the network side is unchanged, or the SCG release is performed:
  • the MCG configuration information is sent to the network, and the MCG configuration is successful, the MCG configuration information is successfully configured, and the original SCG configuration information that is delivered last time is maintained, or the SCG release is performed.
  • the original MCG configuration information that was delivered last time is maintained, and the original SCG configuration information that was delivered last time is maintained, or SCG release is performed.
  • the communications unit is configured to send the SCG reconfiguration failure information to the network side in the following manner:
  • Determining the cause of the failure of the SCG configuration, and generating a corresponding SCG reconfiguration failure based on the reason for the failure of the SCG configuration The information is sent to the network side for the SCG reconfiguration failure information.
  • the communications unit when determining the cause of the SCG configuration failure, is configured to determine that the SCG configuration failure reason is any one of the following reasons:
  • a cell configuration device includes a processor, a transceiver, and a memory, wherein
  • the processor is configured to read a program in the memory and perform the following process:
  • the SCG reconfiguration failure information When the SCG reconfiguration failure information is received, it is determined that the UE performs SCG configuration failure, and when it is determined that the primary cell group MCG configuration is successful, triggering to maintain the previous original SCG configuration information unchanged, or triggering execution of SCG release.
  • the transceiver is configured to receive and transmit data under the control of a processor.
  • the processor is configured to trigger setting SCG configuration information by:
  • the SeNB is triggered to set corresponding SCG configuration information for the UE.
  • the device is an SeNB, the corresponding SCG configuration information is set for the UE directly.
  • the processor is configured to trigger sending the SCG configuration information to the UE by:
  • the first message is used to send the locally configured primary cell group MCG configuration information and the SCG configuration information set by the SeNB to the UE; or the first message is used to send the SCG configuration information set by the SeNB to the UE.
  • the first message is used to directly send the locally set SCG configuration information to the UE.
  • the processor is configured to: when receiving the SCG reconfiguration failure information, determine that the UE performs the SCG configuration failure:
  • the device is a MeNB, if the SCG reconfiguration failure information sent by the UE is directly received, it is determined that the UE fails to perform SCG configuration;
  • the SeNB is the SeNB
  • the UE determines that the UE performs the SCG configuration failure.
  • the SCG reconfiguration failure information sent by the MeNB is after the MeNB receives the SCG reconfiguration failure information sent by the UE. , sent to the device.
  • the processor is configured to determine that the UE performs the SCG configuration failure in the following manner, and when determining that the MCG configuration is successful, triggering to maintain the original SCG configuration information that is last delivered:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original delivery.
  • the SCG configuration information is unchanged; or, after determining that the UE fails to perform the SCG configuration, the original MCG configuration information is maintained unchanged, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original SCG configuration information that is delivered last time; ,
  • the device is the SeNB, it is determined that the UE fails to perform the SCG configuration, and after determining that the MCG configuration is successful, the original SCG configuration information that was previously delivered is maintained.
  • the processor is configured to determine that the UE fails to perform SCG configuration, and triggers execution of SCG release when determining that the MCG configuration is successful:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or, After the UE performs the SCG configuration, the original MCG configuration information is maintained, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or
  • the device is a SeNB, it is determined that the UE fails to perform SCG configuration, and after determining that the MCG configuration is successful, performing SCG release.
  • the processor is further configured to:
  • the reason for the failure of the corresponding SCG configuration is obtained based on the received SCG reconfiguration failure information, and the corresponding new SCG configuration information is triggered and re-issued based on the failure reason of the SCG configuration.
  • the processor is configured to trigger re-setting and re-issue the corresponding new SCG configuration information according to the reason for the failure of the SCG configuration in the following manner:
  • the SCG configuration failure reason is sent to the SeNB, and the SeNB is triggered to reset the new SCG configuration information and send the new SCG configuration information to the device according to the SCG configuration failure reason.
  • the device is sent to the UE, or the SeNB is triggered to reset the new SCG configuration information and send the new SCG configuration information to the UE according to the SCG configuration failure reason;
  • the device is a SeNB, after receiving the SCG configuration failure reason sent by the MeNB, directly triggering to newly reset the new SCG configuration information based on the SCG configuration failure reason, and sending the new SCG configuration information to the MeNB, by the MeNB The information is sent to the UE, or the new SCG configuration information is directly sent to the UE.
  • the processor is configured to trigger the SeNB to perform any one of the following operations when the new SCG configuration information is triggered to be reset based on the SCG configuration failure reason:
  • the new SCG configuration information is reset according to a preset manner.
  • the MeNB re-negotiates, and after the UE capability is re-evaluated, the new SCG configuration information is reset according to the evaluation result;
  • the SCG configuration information that fails to be configured is adjusted accordingly, and the new SCG configuration information is reset according to the adjustment result.
  • a cell configuration device includes a processor, a transceiver, a memory, and a user interface, where
  • the processor is configured to read a program in the memory and perform the following process:
  • the SCG reconfiguration failure information is sent to the network side;
  • the original SCG configuration information that is sent by the network side is maintained unchanged, or the SCG release is performed.
  • the transceiver is configured to receive and transmit data under the control of the processor.
  • the processor is configured to: when the MCG configuration is successful, when the original SCG configuration information sent by the network side is unchanged, or the SCG release is performed:
  • the MCG configuration information is sent to the network, and the MCG configuration is successful, the MCG configuration information is successfully configured, and the original SCG configuration information that is delivered last time is maintained, or the SCG release is performed.
  • the original MCG configuration information that was delivered last time is maintained, and the original SCG configuration information that was delivered last time is maintained, or SCG release is performed.
  • the processor is configured to send, by using the transceiver, the SCG reconfiguration failure information to the network side by:
  • the SCG configuration failure reason is determined, and the corresponding SCG reconfiguration failure information is generated based on the SCG configuration failure reason, and the SCG reconfiguration failure information is sent to the network side by the transceiver.
  • the processor when determining the cause of the failure of the SCG configuration, is configured to determine that the reason for the failure of the SCG configuration is any one of the following reasons:
  • the first base station sends the SCG configuration information to the UE for SCG configuration.
  • the SCG reconfiguration failure information is sent to the network side.
  • the UE and the network side When it is determined that the MCG configuration is successful, the original SCG configuration information that is delivered last time is maintained, or the SCG release is triggered. That is, in the case that only the SCG configuration fails, the RRC re-establishment is not frequently initiated, but the original The SCG configuration information, in this way, effectively avoids serious data interruption, ensures normal communication of the user equipment, thereby improving data transmission efficiency, ensuring system performance, and improving the user experience.
  • FIG. 1 is a schematic diagram of a dual connectivity technology of an LTE-A system in the prior art
  • FIGS. 2a and 2b are schematic diagrams of LTE and NR tightinterworking in a 5G system in the prior art
  • FIG. 3 is a structural diagram of an LTE and NR tightinterworking protocol in a 5G system in the prior art
  • FIG. 5 is a flowchart of a process in which the MeNB sends the SCG configuration information and the UE fails to perform the SCG configuration failure in the embodiment of the present application;
  • FIG. 6 is a flowchart of a process in which the MeNB sends the SCG configuration information and the UE generates a “parsing error” in the embodiment of the present application;
  • FIG. 7 is a flowchart of a process in which a SeNB sends SCG configuration information and a “parameter error” occurs in a UE according to an embodiment of the present disclosure
  • FIG. 8 is a flowchart of a process in which the SeNB sends the SCG configuration information and the UE exceeds the UE capability in the embodiment of the present application;
  • FIG. 9 is a flowchart of a process for the SeNB to perform SCG release in a case where the MeNB sends the SCG configuration information and the UE fails to perform the SCG configuration in the embodiment of the present application;
  • FIG. 10 is a schematic diagram of a first functional structure of a first base station according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a first function of a UE according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a second functional structure of a first base station according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a second functional structure of a UE in an embodiment of the present application.
  • a cell configuration scheme is designed, which is: when the UE determines that the SCG configuration fails, in the scenario where the MeNB and the SeNB are jointly applied.
  • the SCG reconfiguration failure information is sent to the network side. At this time, both the UE and the network side maintain the original SCG configuration information that was delivered last time.
  • the scenario of LTE and NR tightinterworking in a 5G system is taken as an example in the embodiment of the present application.
  • the base station which may be MeNB or SeNB
  • the base station which may be MeNB or SeNB
  • Step 400 The first base station obtains UE status information, where the UE status information may include multiple types of parameters, such as capability information of the UE, UE radio resource configuration information, and the like.
  • the first base station may be a macro base station, such as an LTE eNB, a 5G NR NB, or the like; or a small base station, such as a low power node (LPN), a pico base station (pico), or a home base station ( Femto), etc., an access point (AP); or a network node composed of a central unit (CU) and a plurality of transmission reception points (TRPs) managed and controlled by the central unit (CU). There are one or more cells (different frequency points or sector splits) under one base station. Both the macro base station and the small base station can be used as the primary base station, that is, the MeNB, or can also be used as the secondary base station, that is, the SeNB.
  • LPN low power node
  • pico pico
  • Femto home base station
  • AP access point
  • CU central unit
  • TRPs transmission reception points
  • the first base station when performing step 400, may adopt, but is not limited to, the following manner:
  • the UE status information may be determined according to the reporting of the UE (eg, the reported measurement report, the service status, the bearer type, and the like).
  • Mode B1 If the first base station is the SeNB, the UE status information may be obtained according to the notification of the MeNB, or the first base station may directly report the report according to the UE (eg, the reported measurement report, service status, bearer type, etc.) ) to determine UE status information.
  • the UE e.g. the reported measurement report, service status, bearer type, etc.
  • Step 410 The first base station triggers setting SCG configuration information.
  • the first base station when performing step 410, may adopt, but is not limited to, the following manner:
  • Mode A2 If the first base station is the MeNB, the first base station sends the UE status information to the SeNB, and triggers the SeNB to set corresponding SCG configuration information based on the UE status information.
  • Mode B2 If the first base station is the SeNB, the first base station directly triggers setting the corresponding SCG configuration information locally based on the obtained UE status information.
  • Step 420 The first base station triggers sending the SCG configuration information to the UE.
  • the first base station may be triggered by using the first message (the first message may be RRC, which is the same in the following, and is not described again).
  • the first base station may adopt but not be limited to The following way
  • Mode A3 If the first base station is the MeNB, the first base station may send the locally set MCG configuration information and the obtained SCG configuration information to the UE together by using an RRC message; or, the RRC message may be used, and only the obtained SCG is used.
  • the configuration information is sent to the UE. At this time, the UE will reconfigure the SCG and maintain the original MCG configuration information.
  • the new RRC message generated by the MeNB (eg, RRC Connection Reconfiguration message, etc.), where the RRC message includes SCG configuration information generated by the SeNB (eg, ASN.1 of SCG configuration information) And the locally set MCG configuration information, and the MeNB sends the foregoing RRC message to the UE by using a primary bearer (for example, SRB1); or, the MCG may also add a field in a container manner in the original RRC message, such as An information element (IE) is added to the information transfer (DL informationTransfer) message for transmitting the SCG configuration information.
  • IE information element
  • Mode B3 If the first base station is a SeNB, the first base station may directly generate the locally generated RRC message. The SCG configuration information is sent to the UE.
  • the SeNB sends the RRC message to the UE by using a secondary bearer (SRB on the secondary).
  • SRB secondary bearer
  • the MeNB may also send the MCG configuration information set by itself to the UE. If the UE obtains the MCG configuration information and the SCG configuration information, the MCG and the SCG may be reconfigured separately, if the UE only obtains the SCG. If the configuration information is used, the UE will reconfigure the SCG and maintain the original MCG configuration information.
  • Step 430 After obtaining the foregoing SCG configuration information, the UE performs SCG configuration locally.
  • the UE obtains the MCG configuration information and the SCG configuration information from the RRC message sent by the MeNB, or if the UE obtains the MCG configuration information from the RRC message sent by the MeNB, the UE obtains the RRC message sent by the SeNB. After the SCG configuration information, the UE reconfigures the MCG and the SCG respectively.
  • the UE If the UE obtains the SCG configuration information only from the RRC message sent by the SeNB, the UE reconfigures the SCG and maintains the original MCG configuration information unchanged.
  • Step 440 The UE determines that the SCG configuration fails, and then maintains the original SCG configuration information unchanged, or performs SCG release.
  • the original SCG configuration information is the SCG configuration information obtained by the UE last time, and is also the SCG configuration information that the UE is currently using. After the UE determines that the SCG configuration fails, it is determined that when the MCG configuration is successful, the UE will Instead of starting the RRC re-establishment process, the original SCG configuration information of the last configuration or the SCG release is performed.
  • the MCG configuration succeeds in two cases. One is that the UE obtains the MCG configuration information, and the MCG configuration is successfully performed. The MeNB and the UE both use the successfully configured MCG configuration. The second is that the MeNB does not deliver the information to the UE.
  • the MCG configuration information in which the MeNB and the UE maintain the original MCG configuration information, but in either case, the UE maintains the original SCG configuration information or performs SCG release as long as the SCG configuration fails.
  • step 440 when step 440 is performed, it is divided into the following three cases:
  • the UE obtains the MCG configuration information and the SCG configuration information from the RRC message sent by the MeNB. Since the RRC message includes two configuration information, the UE processes the MCG configuration information according to the default processing priority. , then process the SCG configuration information.
  • the UE If the MCG configuration fails, the UE notifies the MCG to directly perform RRC re-establishment. This is not considered in the embodiment of the present application, and therefore is not described again.
  • the UE adopts the new MCG configuration information and maintains the original SCG.
  • the configuration information is unchanged or the SCG is released.
  • the second case is that the UE obtains the SCG configuration information from the RRC message sent by the MeNB, where the RRC message only includes the SCG configuration information, that is, the UE maintains the original MCG configuration information unchanged regardless of whether the SCG configuration is successful. Then, when the SCG configuration fails, the UE not only maintains the original MCG configuration information, but also maintains the original SCG configuration information or performs SCG release.
  • the third case is that the UE obtains the SCG configuration information from the RRC message sent by the SeNB.
  • the UE does not adopt the new SCG configuration information, but maintains the original SCG configuration information or performs SCG release.
  • Step 450 The UE determines a reason for the SCG configuration failure.
  • the reasons for the failure of the SCG configuration include but are not limited to the following four types:
  • the first reason: “more than UE capability” is specifically described. "Over-the-UE capability” can be understood as the fact that some parameters in the SCG configuration information received by the UE exceed the capability of the UE to access, for example, the maximum context identifier in the Packet Data Convergence Protocol (PDCP) configuration.
  • the Max Context Identifier (maxCID) exceeds the maximum number of robust header compression contexts indicated by the capability information of the UE.
  • parsing error can be understood as that the UE cannot correctly parse some content in the received SCG configuration information, for example, the ASN.1 included in the SCG configuration information cannot be recognized by the UE, or, in the information delivery message (DL informationTransfer) The content of the added IE cannot be recognized by the UE.
  • the third reason the "parameter error” of the specific description.
  • the “parameter error” can be understood as the configuration parameter that is included in the SCG configuration information received by the UE, for example, assuming that a certain configuration parameter of the SCG in the UE is in the range of 0 to 100, and the SCG configuration information received by the UE is The value of this parameter is 200.
  • SCG configuration failure is outlined.
  • SCG configuration failure can be understood as not specifically distinguishing which type of SCG configuration failure reason, but generally describing the cause of the SCG configuration failure as the "SCG configuration failure" described in the general description.
  • Step 460 The UE sends the SCG configuration failure reason in the SCG reconfiguration failure information to the first base station, and notifies the first base station that the SCG configuration fails.
  • the UE may generate the corresponding SCG reconfiguration failure information based on the determined SCG configuration failure reason, and then send the SCG reconfiguration failure information to the first base station.
  • the UE may adopt but Not limited to the following ways:
  • Mode A4 If the first base station is the MeNB, the UE may directly send the SCG reconfiguration failure information carrying the SCG configuration failure reason to the first base station;
  • Mode B4 If the first base station is the SeNB, the UE may firstly carry the SCG carrying the cause of the failure of the SCG configuration.
  • the configuration failure information is sent to the MeNB, and then the SeNB receives the SCG reconfiguration information that is sent by the MeNB and carries the SCG configuration failure reason.
  • the SCG reconfiguration failure information sent by the MeNB is the SCG reconfiguration failure information sent by the MeNB.
  • the post-transmitted information is information generated independently by the MeNB based on the SCG reconfiguration failure information sent by the UE according to the communication protocol with the SeNB.
  • the UE sends the SCG reconfiguration failure information to the MeNB through the primary bearer (for example, SRB1).
  • the SCG reconfiguration failure information sent on the air interface may be an independent RRC message, or may be The IE in the original RRC message, regardless of the form of SCG reconfiguration failure information, includes the reason for the SCG configuration failure.
  • the UE may adopt the following two methods:
  • the reason why the UE fails to configure the SCG configuration is uniformly described in the SCG configuration failure information as the SCG reconfiguration failure (scg-reconfiguration failure).
  • the reason why the UE fails to configure the SCG configuration is classified in the SCG configuration failure information according to the specific failure reason, such as: UE Capability-Exceed, Parse Error, and Parameter Error.
  • Step 470 The first base station triggers to maintain the original SCG configuration information unchanged, and according to the obtained SCG configuration failure reason, triggers resetting and resending the corresponding new SCG configuration information, or triggers execution of SCG release.
  • the first base station learns that the sent SCG configuration information is not successfully set, it also automatically triggers the use of the original SCG configuration information (ie, the last configured SCG configuration information) or triggers the execution of the SCG release instead of triggering the RRC reestablishment process.
  • Example 1 When the first base station is the MeNB, the first base station determines that the MCG configuration is successful and the SCG configuration fails, and the first base station uses the successfully configured MCG configuration information. And sending the SCG reconfiguration failure information to the SeNB, triggering the SeNB to maintain the original SCG configuration information or triggering the SeNB to perform the SCG release; or the first base station may receive the SCG reconfiguration failure information sent by the UE (may not be The MCG configuration information is sent, the MCG configuration is not performed, and the SCG configuration fails. At this time, the first base station maintains the original MCG configuration information, and sends the SCG reconfiguration failure information to the SeNB, triggering the SeNB to maintain the original SCG configuration information. The SeNB is changed or triggered to perform SCG release.
  • the first base station determines that the SCG configuration fails after receiving the SCG reconfiguration failure information sent by the MeNB, and determines that the original SCG configuration information that was previously delivered is not after the MCG configuration is successful.
  • Changing or performing the SCG release where the SCG reconfiguration failure information sent by the MeNB received by the first base station is sent by the MeNB to the first base station after receiving the SCG reconfiguration failure information sent by the UE;
  • the base station determines that the MCG configuration is successful, that is, the MeNB does not instruct the first base station to trigger the RRC re-establishment process. In this case, whether the MeNB uses the new MCG configuration information or maintains the original MCG configuration information, the first base station does not receive the trigger.
  • the indication of the RRC reestablishment process is that the MCG configuration is successful at this time.
  • the first base station when triggering resetting and resending the corresponding new SCG configuration information, may adopt, but is not limited to, the following manner:
  • Mode A5 If the first base station is the MeNB, the first base station sends the obtained SCG configuration failure reason to the SeNB, and the SeNB resets the new SCG configuration information based on the SCG configuration failure reason. After the setting is completed, the SeNB will be new.
  • the SCG configuration information is sent to the MeNB, and then sent by the MeNB to the UE. Alternatively, the SeNB may directly send the new SCG configuration information to the UE.
  • Mode B5 If the first base station is the SeNB, after receiving the SCG configuration failure reason sent by the MeNB, the first base station locally resets the new SCG configuration information based on the SCG configuration failure reason. After the setting is completed, the first base station is new.
  • the SCG configuration information is sent to the MeNB, and is sent by the MeNB to the UE. Alternatively, the first base station may directly send the new SCG configuration information to the UE.
  • the MeNB sends a new SCG using the successfully configured MCG configuration information according to the method described in the first or the second embodiment. If the MCG is not changed, the new MCG configuration information is sent using the original MCG configuration information.
  • the SeNB uses the original SCG configuration information and sends the original SCG configuration information when determining the SCG configuration failure according to the method described in the first or the second embodiment.
  • New SCG configuration information if the new SCG configuration information is sent by the SeNB, the SeNB uses the original SCG configuration information and sends the original SCG configuration information when determining the SCG configuration failure according to the method described in the first or the second embodiment.
  • New SCG configuration information if the new SCG configuration information is sent by the SeNB, uses the original SCG configuration information and sends the original SCG configuration information when determining the SCG configuration failure according to the method described in the first or the second embodiment.
  • the reason for the failure of the parsing is “SCG reconfiguration failure”, and the SeNB resets the new SCG configuration information according to a preset manner.
  • the new SCG configuration information is reconfigured.
  • the SeNB adjusts the SCG configuration information that was previously delivered, and generates new SCG configuration information.
  • the second case is as follows: The reason for the failure of the parsing is specifically described as: “over UE capability”, “parsing error” or “parameter error”, and corresponding processing is performed according to specific reasons.
  • the first type if the reason for the failure is that the original SCG configuration information exceeds the capability of the UE, the UE needs to initiate a UE capability negotiation session with the MeNB to perform UE capability negotiation again. After the UE capability is re-determined, the first base station re-determines the UE capability. Set the corresponding new SCG configuration information;
  • the second type If the failure of the parsing is that the UE cannot parse the original SCG configuration information or there is a parameter error in the original SCG configuration information, the original SCG configuration information is adjusted accordingly (for example, the SCG configuration information is re-encoded and reset. New parameters, etc.) can generate new SCG configuration information.
  • Step 480 The UE performs SCG configuration according to the received new SCG configuration information.
  • the UE can obtain the new SCG configuration information, and perform SCG configuration based on the new SCG configuration information. After the configuration is completed, the UE can start to use the new SCG configuration information to perform data transmission with the network side.
  • the first scenario is as follows: the SCG configuration information is sent by the MeNB, and the UE fails to perform the SCG configuration failure.
  • Step 500 The SeNB sends SCG configuration information to the MeNB.
  • the SeNB may first obtain the UE state information, and then set corresponding SCG configuration information based on the UE state information, for example, compile with an abstract syntax representation (ASN), generate an ASN.1 of the SCG configuration information, and generate the SCG.
  • the configuration information is sent to the MeNB.
  • Step 510 The MeNB sends MCG configuration information and SCG configuration information to the UE.
  • the MeNB receives the SCG configuration information from the SeNB, generates the RRC message by combining the SCG configuration information with the locally set MCG configuration information, and sends the RRC message to the UE by using the primary bearer (for example, SRB1).
  • the primary bearer for example, SRB1.
  • Step 520 The UE determines that the SCG configuration fails.
  • the UE obtains the MCG configuration information and the SCG configuration information from the RRC message sent by the MeNB. Since the RRC message includes two configuration information, the UE processes the MCG configuration information and processes the SCG configuration information according to the default processing priority. . At this time, if the MCG configuration is successful and the SCG configuration fails, the UE adopts the successfully configured MCG configuration information, maintains the original SCG configuration information unchanged, and determines the cause of the SCG configuration failure.
  • the SCG configuration failure there are four reasons for the failure of the SCG configuration, that is, the "SCG configuration failure” generally described, and the "over-the-UE capability", “parsing error”, and “parameter error” described in detail.
  • the reason for the failure of the SCG configuration is described as an example of the failure of the SCG configuration. Therefore, the UE determines the cause of the failure of the SCG configuration as the "SCG configuration failure" generally described.
  • Step 530 The UE sends an SCG reconfiguration failure message to the MeNB, and notifies the SCG of the configuration failure reason.
  • the SCG reconfiguration failure information is sent to the MeNB by using a separate RRC message through the primary bearer (for example, SRB1), where the SCG configuration failure reason is included, that is, the SCG reconfiguration failure is generally described. ".
  • Step 540 The MeNB sends an SCG reconfiguration failure message to the SeNB, and notifies the SCG of the reconfiguration failure reason.
  • the MeNB receives the SCG reconfiguration failure information sent by the UE, and sends an SCG reconfiguration failure message to the SeNB.
  • Information which includes the reason for the failure of the SCG configuration, that is, the "SCG reconfiguration failure" outlined.
  • Step 550 The SeNB sends new SCG configuration information to the MeNB.
  • the SeNB After receiving the SCG reconfiguration failure information sent by the MeNB, the SeNB re-evaluates the capability of the UE after re-evaluating the capability of the UE according to the failure reason "SCG reconfiguration failure", and generates a corresponding new SCG configuration information, and the new The SCG configuration information is sent to the MeNB.
  • Step 560 The MeNB sends new SCG configuration information to the UE.
  • the MeNB After receiving the new SCG configuration information, the MeNB generates an RRC connection reconfiguration message, where the RRC connection reconfiguration message includes new SCG configuration information, and in step 520, the UE has successfully configured the MCG configuration information, and thus, the MeNB
  • the RRC connection reconfiguration message is sent, the MCG configuration information that is successfully configured is used, and the MeNB sends the RRC connection reconfiguration message to the UE through the primary bearer (for example, SRB1).
  • the primary bearer for example, SRB1
  • the UE can obtain the new SCG configuration information, and perform SCG configuration based on the new SCG configuration information. After the configuration is completed, the UE can start to use the new SCG configuration information to perform data transmission with the network side.
  • the SeNB can also directly send the new SCG configuration information to the UE.
  • the foregoing process is only an example.
  • the SeNB directly sends the new SCG configuration information, in step 520, if the UE maintains the original SCG configuration information, Then, the SeNB needs to use the original SCG configuration information, and sends an RRC message carrying the new SCG configuration information to the UE through the SRB on the secondary, for example, SRB3.
  • the second scenario is as follows: the SCeNB sends the SCG configuration information, and the UE generates a “parsing error”.
  • Step 600 The SeNB sends SCG configuration information to the MeNB.
  • the SeNB may first obtain the UE status information, and then set the corresponding SCG configuration information based on the UE status information, for example, compiling with the ASN, generating the ASN.1 of the SCG configuration information, and transmitting the generated SCG configuration information to the MeNB.
  • Step 610 The MeNB sends the SCG configuration information to the UE.
  • the MeNB receives the SCG configuration information from the SeNB, and sends the SCG configuration to the UE through the primary bearer (for example, SRB1) by using the RRC message.
  • the MeNB does not send the MCG configuration information to the UE, therefore, the UE Maintain the original MCG configuration information unchanged.
  • Step 620 The UE determines that the SCG configuration fails.
  • the UE obtains the SCG configuration information from the MeNB. If the SCG configuration fails, the UE does not adopt the new SCG configuration information, but maintains the original SCG configuration information unchanged, and determines the SCG configuration failure reason.
  • the SCG configuration failure there are four reasons for the failure of the SCG configuration, that is, the "SCG configuration failure” generally described, and the “over-the-UE capability”, “parsing error”, and “parameter error” described in detail.
  • the UE uses “parse error” as SCG
  • the reason for the configuration failure is described as an example. Therefore, the UE determines the cause of the failure of the SCG configuration as the "parsing error" of the specific description.
  • Step 630 The UE sends an SCG reconfiguration failure message to the MeNB, and notifies the SCG of the configuration failure reason.
  • the SCG reconfiguration failure information is sent to the MeNB by using a separate RRC message through the primary bearer (for example, SRB1), where the SCG configuration failure reason, that is, the “parsing error” of the specific description is included.
  • the primary bearer for example, SRB1
  • Step 640 The MeNB sends an SCG reconfiguration failure message to the SeNB, and notifies the SCG of the reconfiguration failure reason.
  • the MeNB receives the SCG reconfiguration failure information sent by the UE, and sends the SCG reconfiguration failure information to the SeNB, where the SCG configuration failure reason, that is, the “analysis error” specifically described, is included.
  • Step 650 The SeNB sends new SCG configuration information to the UE.
  • the SeNB After receiving the SCG reconfiguration failure information sent by the MeNB, the SeNB performs the corresponding adjustment on the original SCG configuration information according to the failure reason "analysis error" (for example, re-encoding the SCG configuration information, etc.), and generates a corresponding new SCG. Configure the information and send the new SCG configuration information to the UE.
  • the failure reason "analysis error” for example, re-encoding the SCG configuration information, etc.
  • the SeNB When the SeNB directly sends new SCG configuration information to the UE, if the UE maintains the original SCG configuration information unchanged in step 620, the SeNB needs to use the original SCG configuration information, and the secondary carrier (SRB on the secondary) to the UE. An RRC message carrying the new SCG configuration information is sent.
  • the UE can obtain the new SCG configuration information, and perform SCG configuration based on the new SCG configuration information. After the configuration is completed, the UE can start to use the new SCG configuration information to perform data transmission with the network side.
  • the SeNB can also send new SCG configuration information to the UE through the MeNB.
  • the foregoing process is only an example.
  • the SeNB sends new SCG configuration information to the UE through the MeNB
  • the MeNB generates RRC after receiving the new SCG configuration information.
  • the RRC connection reconfiguration message includes the new SCG configuration information, and in step 610, if the UE maintains the original MCG configuration information, the MeNB sends the RRC connection reconfiguration message this time.
  • the MCG configuration information is continuously used, and the MeNB sends the RRC connection reconfiguration message to the UE through the primary bearer (for example, SRB1).
  • the primary bearer for example, SRB1
  • the third scenario is as follows: the SeNB sends the SCG configuration information, and the UE generates a “parameter error”.
  • Step 700 The SeNB sends SCG configuration information to the UE.
  • the SeNB may first obtain the UE state information, and then set the corresponding SCG configuration information based on the UE state information, and send the generated SCG configuration information to the UE.
  • Step 710 The UE determines that the SCG configuration fails.
  • the UE obtains the SCG configuration information directly from the SeNB, and if the SCG configuration fails, determines that the SCG configuration fails. because.
  • the MeNB does not send the MCG configuration information to the UE, and therefore, the UE maintains the original MCG configuration information.
  • the SCG configuration failure there are four reasons for the failure of the SCG configuration, that is, the "SCG configuration failure” generally described, and the “over-the-UE capability”, “parsing error”, and “parameter error” described in detail.
  • the reason for the failure of the SCG configuration is described as an example of the "parameter error”. Therefore, the UE determines the cause of the failure of the SCG configuration as the "parameter error" of the specific description.
  • Step 720 The UE sends an SCG reconfiguration failure information to the MeNB, and notifies the SCG of the configuration failure reason.
  • the SCG reconfiguration failure information is sent to the MeNB by using a separate RRC message through the primary bearer (for example, SRB1), where the SCG configuration failure reason, that is, the “parameter error” is specifically described.
  • SRB1 the primary bearer
  • Step 730 The MeNB sends an SCG reconfiguration failure information to the SeNB, and notifies the SCG of the reconfiguration failure reason.
  • the MeNB receives the SCG reconfiguration failure information sent by the UE, and sends the SCG reconfiguration failure information to the SeNB, where the SCG configuration failure reason, that is, the “parameter error” specifically described is included.
  • Step 740 The SeNB sends new SCG configuration information to the MeNB.
  • the SeNB After receiving the SCG reconfiguration failure information sent by the MeNB, the SeNB performs corresponding adjustment on the original SCG configuration information according to the failure reason "parameter error” (such as resetting new parameters, etc.), and generates corresponding new SCG configuration information.
  • the new SCG configuration information is sent to the MeNB.
  • Step 750 The MeNB sends new SCG configuration information to the UE.
  • the MeNB After receiving the new SCG configuration information, the MeNB generates an RRC connection reconfiguration message, where the RRC connection reconfiguration message includes new SCG configuration information, and in step 710, if the UE maintains the original MCG configuration information unchanged, When the MeNB sends the RRC connection reconfiguration message, the MeNB will continue to use the MCG configuration information, and the MeNB will send the RRC connection reconfiguration message to the UE through the primary bearer (for example, SRB1).
  • the primary bearer for example, SRB1
  • the UE can obtain the new SCG configuration information, and perform SCG configuration based on the new SCG configuration information. After the configuration is completed, the UE can start to use the new SCG configuration information to perform data transmission with the network side.
  • the SeNB can also directly send new SCG configuration information to the UE.
  • the foregoing process is only an example.
  • the SeNB directly sends new SCG configuration information to the UE if the UE maintains the original SCG configuration information, the SeNB needs to Using the original SCG configuration information, the RRC message carrying the new SCG configuration information is sent to the UE through the SRB on the secondary, for example, SRB3.
  • the fourth scenario is as follows: the SCG sends the SCG configuration information by the SeNB, and the UE generates the “over-UE capability”.
  • Step 800 The SeNB sends the SCG configuration information to the UE.
  • the SeNB may first obtain the UE state information, and then set the corresponding SCG configuration information based on the UE state information, and send the generated SCG configuration information to the UE.
  • Step 810 The UE determines that the SCG configuration fails.
  • the UE obtains the SCG configuration information directly from the SeNB. If the SCG configuration fails, the SCG configuration failure reason is determined.
  • the UE since the MeNB does not send the MCG configuration information to the UE, the UE maintains the original MCG configuration information unchanged.
  • the UE determines the cause of the failure of the SCG configuration as the "over-the-UE capability" of the specific description.
  • Step 820 The UE sends an SCG reconfiguration failure information to the MeNB, and notifies the SCG of the configuration failure reason.
  • the SCG reconfiguration failure information is sent to the MeNB by using a separate RRC message through the primary bearer (for example, SRB1), where the SCG configuration failure reason is included, that is, the “over-UE capability” is specifically described. .
  • the primary bearer for example, SRB1
  • Step 830 The MeNB sends an SCG reconfiguration failure message to the SeNB, and notifies the SCG of the reconfiguration failure reason.
  • the MeNB receives the SCG reconfiguration failure information sent by the UE, and sends the SCG reconfiguration failure information to the SeNB, where the SCG configuration failure reason, that is, the “exceeded UE capability” is specifically described.
  • Step 840 The SeNB performs UE capability negotiation with the MeNB.
  • the SeNB After receiving the SCG reconfiguration failure information sent by the MeNB, the SeNB re-evaluates the capability of the UE after re-evaluating the capability of the UE according to the reason for the failure to exceed the UE capability, and generates a corresponding new SCG configuration information, and the new SCG is generated.
  • the configuration information is directly sent to the UE.
  • Step 850 The SeNB sends new SCG configuration information to the UE.
  • the SeNB generates new SCG configuration information and directly sends the information to the UE. If the UE maintains the original SCG configuration information, the SeNB needs to use the original SCG configuration information and deliver the information to the UE through the SRB on the secondary, for example, SRB3. An RRC message carrying new SCG configuration information.
  • the UE can obtain the new SCG configuration information, and perform SCG configuration based on the new SCG configuration information. After the configuration is completed, the UE can start to use the new SCG configuration information to perform data transmission with the network side.
  • the SeNB can also send new SCG configuration information to the UE through the MeNB.
  • the foregoing process is only an example.
  • the MeNB After receiving the new SCG configuration information, the MeNB generates an RRC connection reconfiguration message, where the RRC connection is generated.
  • the reconfiguration message contains the new SCG configuration information, and in step 810, if the UE maintains the original MCG configuration information, the MeNB continues to use the MCG configuration information when the RRC connection reconfiguration message is sent.
  • the MeNB sends the RRC Connection Reconfiguration message to the UE through the primary bearer (eg, SRB1).
  • the primary bearer eg, SRB1
  • the above four embodiments are all that when the UE determines that the SCG configuration fails, the SCG reconfiguration failure information is sent to the network side, and the UE and the network side maintain the original SCG configuration information that was previously delivered unchanged when the MCG configuration is successful.
  • the SCG reconfiguration failure information is sent to the network side, and the UE and the network side may also trigger the execution of the SCG release when determining that the MCG configuration is successful. No new SCG configuration information will be sent or sent.
  • the fifth scenario is as follows: In the case that the SCG configuration information is sent by the MeNB, and the UE fails to perform the SCG configuration, the UE sends the SCG reconfiguration failure information to the network side, and the UE and the network side Determines that the SCG release is triggered when the MCG configuration is successful.
  • Step 900 The SeNB sends SCG configuration information to the MeNB.
  • the SeNB may first obtain the UE state information, and then set corresponding SCG configuration information based on the UE state information, for example, compile with an abstract syntax representation (ASN), generate an ASN.1 of the SCG configuration information, and generate the SCG.
  • the configuration information is sent to the MeNB.
  • Step 910 The MeNB sends MCG configuration information and SCG configuration information to the UE.
  • the MeNB receives the SCG configuration information from the SeNB, generates the RRC message by combining the SCG configuration information with the locally set MCG configuration information, and sends the RRC message to the UE by using the primary bearer (for example, SRB1).
  • the primary bearer for example, SRB1.
  • Step 920 The UE determines that the SCG configuration fails.
  • the UE obtains the MCG configuration information and the SCG configuration information from the RRC message sent by the MeNB. Since the RRC message includes two configuration information, the UE processes the MCG configuration information and processes the SCG configuration information according to the default processing priority. . At this time, if the MCG configuration is successful and the SCG configuration fails, the UE adopts the successfully configured MCG configuration information, determines the cause of the SCG configuration failure, and performs SCG release.
  • the SCG configuration failure there are four reasons for the failure of the SCG configuration, that is, the "SCG configuration failure” generally described, and the "over-the-UE capability", “parsing error”, and “parameter error” described in detail.
  • the reason for the failure of the SCG configuration is described as an example of the failure of the SCG configuration. Therefore, the UE determines the cause of the failure of the SCG configuration as the "SCG configuration failure" generally described.
  • Step 930 The UE sends an SCG reconfiguration failure message to the MeNB, and notifies the SCG of the configuration failure reason.
  • the SCG reconfiguration failure information is sent to the MeNB by using a separate RRC message through the primary bearer (for example, SRB1), where the SCG configuration failure reason, that is, the generally described "SCG" is included. Reconfiguration failed.”
  • the primary bearer for example, SRB1
  • Step 940 The MeNB sends an SCG reconfiguration failure message to the SeNB, and notifies the SCG of the reconfiguration failure reason.
  • the MeNB receives the SCG reconfiguration failure information sent by the UE, and sends the SCG reconfiguration failure information to the SeNB, where the SCG configuration failure reason, that is, the "SCG reconfiguration failure" generally described is included.
  • Step 950 The SeNB performs SCG release.
  • the SeNB After receiving the SCG reconfiguration failure information sent by the MeNB, the SeNB determines that the UE fails to perform SCG configuration according to the failure reason "SCG reconfiguration failure", and then performs SCG release.
  • scenario 2 scenario 3, and scenario 4, after the SeNB receives the SCG reconfiguration failure information sent by the MeNB, the SeNB determines that the UE performs SCG configuration failure after performing the SCG configuration failure according to the failure reason, and does not send or
  • the new SCG configuration information is the same as that in the fifth embodiment, and therefore will not be described again.
  • the interaction between the SeNB and the MeNB is performed through the X2 interface.
  • the interaction between the SeNB and the MeNB is not limited to the X2 interface, and may also be through the X1. Or X3, ..., Xn are completed, so I won't go into details.
  • a cell configuration device for example, a first base station
  • a cell configuration device includes at least a first trigger unit 100, a second trigger unit 101, and a processing unit 102, where
  • the first triggering unit 100 is configured to trigger setting the secondary cell group SCG configuration information
  • the second triggering unit 101 is configured to trigger sending the SCG configuration information to the user equipment UE, and trigger the UE to perform SCG configuration;
  • the processing unit 102 is configured to: when the SCG reconfiguration failure information is received, determine that the UE fails to perform the SCG configuration, and if it is determined that the primary cell group MCG configuration is successful, trigger to maintain the original SCG configuration information that is last delivered, or trigger Perform SCG release.
  • the first triggering unit 100 when triggering setting SCG configuration information, is configured to:
  • the SeNB is triggered to set corresponding SCG configuration information for the UE.
  • the device is an SeNB, the corresponding SCG configuration information is set for the UE directly.
  • the second triggering unit 101 when triggering sending the SCG configuration information to the UE for SCG configuration, is configured to:
  • the first message is used to send the locally set MCG configuration information and the SCG configuration information set by the SeNB to the UE; or, using the first message, only the SCG configuration information set by the SeNB is sent to the UE;
  • the first message is used to directly send the locally set SCG configuration information to the UE.
  • Unit 102 is used to:
  • the device is a MeNB, if the SCG reconfiguration failure information sent by the UE is directly received, it is determined that the UE fails to perform SCG configuration;
  • the device is an SeNB, if the SCG reconfiguration failure information sent by the MeNB is received, determining that the UE performs SCG configuration failure; wherein the received SCG reconfiguration failure information sent by the MeNB is that the MeNB receives the SCG reconfiguration sent by the UE. After the failure message, it is sent to the device.
  • the processing unit 102 is configured to:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original delivery.
  • the SCG configuration information is unchanged; or, after determining that the UE fails to perform the SCG configuration, the original MCG configuration information is maintained unchanged, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original SCG configuration information that is delivered last time; ,
  • the device is the SeNB, it is determined that the UE fails to perform the SCG configuration, and after determining that the MCG configuration is successful, the original SCG configuration information that was previously delivered is maintained.
  • the processing unit 102 is configured to:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or, After the UE performs the SCG configuration, the original MCG configuration information is maintained, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or
  • the device is a SeNB, it is determined that the UE fails to perform SCG configuration, and after determining that the MCG configuration is successful, performing SCG release.
  • processing unit 102 is further configured to:
  • the device acquires a corresponding SCG configuration failure reason based on the received SCG reconfiguration failure information, and triggers resetting and resending the corresponding new SCG configuration information based on the SCG configuration failure reason.
  • the processing unit 102 is configured to:
  • the SCG configuration failure reason is sent to the SeNB, and the SeNB is triggered to reset the new SCG configuration information and send the new SCG configuration information to the device according to the SCG configuration failure reason.
  • the device is sent to the UE, or the SeNB is triggered to reset the new SCG based on the reason for the failure of the SCG configuration. Configuration information and sending new SCG configuration information to the UE;
  • the device is a SeNB, after receiving the SCG configuration failure reason sent by the MeNB, directly triggering to newly reset the new SCG configuration information based on the SCG configuration failure reason, and sending the new SCG configuration information to the MeNB, by the MeNB The information is sent to the UE, or the new SCG configuration information is directly sent to the UE.
  • the processing unit 102 is configured to:
  • the new SCG configuration information is reset according to a preset manner.
  • the MeNB re-negotiates, and after the UE capability is re-evaluated, the new SCG configuration information is reset according to the evaluation result;
  • the SCG configuration information that fails to be configured is adjusted accordingly, and the new SCG configuration information is reset according to the adjustment result.
  • a cell configuration device for example, a user equipment
  • a configuration unit 110 for example, a communication unit 111
  • a processing unit 112 for example, a processor
  • the configuration unit 110 is configured to perform SCG configuration according to the secondary cell group SCG configuration information delivered by the network side;
  • the communication unit 111 is configured to: when it is determined that the SCG configuration fails, send the SCG reconfiguration failure information to the network side;
  • the processing unit 112 is configured to: when the configuration of the primary cell group MCG is successful, maintain the original SCG configuration information that is sent last time on the network side, or perform SCG release.
  • the processing unit 112 when it is determined that the MCG configuration is successful, when the original SCG configuration information that is sent by the network side is not changed, or the SCG release is performed, the processing unit 112 is configured to:
  • the MCG configuration information is sent to the network, and the MCG configuration is successful, the MCG configuration information is successfully configured, and the original SCG configuration information that is delivered last time is maintained, or the SCG release is performed.
  • the original MCG configuration information that was delivered last time is maintained, and the original SCG configuration information that was delivered last time is maintained, or SCG release is performed.
  • the communication unit 111 is configured to:
  • the communication unit 111 when determining a cause of failure of the SCG configuration, is configured to:
  • a cell configuration apparatus for example, a first base station
  • a processor 120 for example, a first base station
  • a transceiver 121 for example, a transceiver 121
  • a memory 122 for example, a processor 120, a transceiver 121, and a memory 122
  • the processor 120 is configured to read a program in the memory 122 and perform the following process:
  • the SCG reconfiguration failure information When the SCG reconfiguration failure information is received, it is determined that the UE performs SCG configuration failure, and when it is determined that the primary cell group MCG configuration is successful, triggering to maintain the previous original SCG configuration information unchanged, or triggering execution of SCG release.
  • the transceiver 121 is configured to receive and transmit data under the control of the processor 120.
  • the processor 120 when the SCG configuration information is triggered, the processor 120 is specifically configured to:
  • the SeNB is triggered to set corresponding SCG configuration information for the UE.
  • the device is an SeNB, the corresponding SCG configuration information is set for the UE directly.
  • the processor 120 when the SCG configuration information is sent to the UE for SCG configuration, the processor 120 is specifically configured to:
  • the first message is used to send the locally set MCG configuration information and the SCG configuration information set by the SeNB to the UE; or, using the first message, only the SCG configuration information set by the SeNB is sent to the UE;
  • the first message is used to directly send the locally set SCG configuration information to the UE.
  • the processor 120 when receiving the SCG reconfiguration failure information, determining that the UE fails to perform the SCG configuration, the processor 120 is specifically configured to:
  • the device is a MeNB, if the SCG reconfiguration failure information sent by the UE is directly received, it is determined that the UE fails to perform SCG configuration;
  • the device is an SeNB, if the SCG reconfiguration failure information sent by the MeNB is received, determining that the UE performs SCG configuration failure; wherein the received SCG reconfiguration failure information sent by the MeNB is that the MeNB receives the SCG reconfiguration sent by the UE. After the failure message, it is sent to the device.
  • the processor 120 is specifically configured to:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original delivery.
  • the SCG configuration information is unchanged; or, after determining that the UE fails to perform the SCG configuration, the original MCG configuration information is maintained unchanged, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to maintain the original SCG configuration information that is delivered last time; ,
  • the device is the SeNB, it is determined that the UE fails to perform the SCG configuration, and after determining that the MCG configuration is successful, the original SCG configuration information that was previously delivered is maintained.
  • the processor 120 is specifically configured to:
  • the device is a MeNB
  • the MCG configuration is determined to be successful
  • the MCG configuration information is successfully configured
  • the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or, After the UE performs the SCG configuration, the original MCG configuration information is maintained, and the SCG reconfiguration failure information is sent to the SeNB, and the SeNB is triggered to perform the SCG release; or
  • the device is a SeNB, it is determined that the UE fails to perform SCG configuration, and after determining that the MCG configuration is successful, performing SCG release.
  • the processor 120 is further specifically configured to:
  • the reason for the failure of the corresponding SCG configuration is obtained based on the received SCG reconfiguration failure information, and the corresponding new SCG configuration information is triggered and re-issued based on the failure reason of the SCG configuration.
  • the processor 120 is specifically configured to:
  • the SCG configuration failure reason is sent to the SeNB, and the SeNB is triggered to reset the new SCG configuration information and send the new SCG configuration information to the device according to the SCG configuration failure reason.
  • the device is sent to the UE, or the SeNB is triggered to reset the new SCG configuration information and send the new SCG configuration information to the UE according to the SCG configuration failure reason;
  • the device is a SeNB, after receiving the SCG configuration failure reason sent by the MeNB, directly triggering to newly reset the new SCG configuration information based on the SCG configuration failure reason, and sending the new SCG configuration information to the MeNB, by the MeNB The information is sent to the UE, or the new SCG configuration information is directly sent to the UE.
  • the processor 120 is specifically configured to: when the new SCG configuration information is triggered to be reset based on the reason for the failure of the SCG configuration:
  • the new SCG configuration information is reset according to a preset manner.
  • the MeNB re-negotiates, and after the UE capability is re-evaluated, the new SCG configuration information is reset according to the evaluation result;
  • the SCG configuration information that fails to be configured is adjusted accordingly, and the new SCG configuration information is reset according to the adjustment result.
  • the processor 120, the transceiver 121, and the memory 122 can be connected by a bus.
  • the bus architecture can include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 120 and various circuits of memory represented by memory 122.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 121 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 120 is responsible for managing the bus architecture and general processing, and the memory 122 can store data used by the processor 120 when performing operations.
  • a cell configuration device eg, user equipment
  • a processor 130 includes a processor 130, a transceiver 131, a memory 132, and a user interface 133, where
  • the processor 130 is configured to read a program in the memory 132 and perform the following process:
  • the SCG reconfiguration failure information is sent to the network side;
  • the transceiver 131 is configured to receive and transmit data under the control of the processor 130.
  • the processor 130 when it is determined that the MCG configuration is successful, when the original SCG configuration information sent by the network side is unchanged, or the SCG release is performed, the processor 130 is specifically configured to:
  • the MCG configuration information is sent to the network, and the MCG configuration is successful, the MCG configuration information is successfully configured, and the original SCG configuration information that is delivered last time is maintained, or the SCG release is performed.
  • the original MCG configuration information that was delivered last time is maintained, and the original SCG configuration information that was delivered last time is maintained, or SCG release is performed.
  • the processor 130 is specifically configured to:
  • the processor 130 when determining the cause of the failure of the SCG configuration, is specifically configured to:
  • the processor 130, the transceiver 131, the memory 132, and the user interface 133 can be connected by a bus.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 130 and various circuits of memory represented by memory 132.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • Transceiver 131 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 133 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 130 is responsible for managing the bus architecture and general processing, and the memory 132 can store data used by the processor 130 when performing operations.
  • the first base station sends the SCG configuration information to the UE for SCG configuration.
  • the SCG is sent to the network side. If the configuration fails, the UE and the network will maintain the original SCG configuration information that was delivered last time, or trigger the SCG release, that is, if only the SCG configuration fails.
  • the RRC re-establishment will not be initiated frequently, but the original SCG configuration information is used, thus effectively avoiding serious data interruption and ensuring normal communication of the user equipment, thereby improving data transmission efficiency, ensuring system performance, and improving users.
  • Experience will be used, thus effectively avoiding serious data interruption and ensuring normal communication of the user equipment, thereby improving data transmission efficiency, ensuring system performance, and improving users.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the present application is a flowchart of a method, device (system), and computer program product according to an embodiment of the present application. And / or block diagram to describe. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本申请涉及涉及移动通信技术领域，尤其涉及一种小区配置方法及装置，用以避免严重的数据中断，保证用户设备的正常通信。该方法为：在MeNB和SeNB联合应用的场景下，第一基站将SCG配置信息发送给UE进行SCG配置，当UE确定SCG配置失败时，会向网络侧发送SCG重配置失败信息，此时，UE和网络侧会在确定MCG配置成功时，维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放，即在仅有SCG配置失败的情况下，不会频繁发起RRC重建，而是使用原来的SCG配置信息，这样，有效避免了严重的数据中断，保证了用户设备的正常通信，从而提高了数据传输效率，保证了系统性能，也提高了用户体验。

Description

一种小区配置方法及装置
本申请要求在2016年8月5日提交中国专利局、申请号为201610635900.2、发明名称为“一种小区配置方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种小区配置方法及装置。
背景技术
随着网络科技的发展，人们对移动网络的需求量越来越大，提升用户吞吐量是未来移动通信技术发展的一大趋势，而节点间无线资源聚合是提升用户吞吐量的潜在技术方案，目前长期演进升级(Long Term Evolution-Advanced，LTE-A)双连接技术和5G系统中LTE和新无线接入(New RAT，NR)紧密互通技术(tight interworking)中均采用了节点间无线资源聚合技术。
以LTE-A系统的双连接技术为例，双连接技术是指用户终端(User Equipment，UE)可以同时利用两个基站的无线频谱资源传输上下行业务，两个基站分布管理各自的小区，管理主小区组(Master Cell Group，MCG)的基站是宏基站(MeNB)，即主基站，管理辅小区组(Secondary Cell Group，SCG)的基站是小基站(SeNB)，即辅基站，宏基站主要负责覆盖范围和移动性，小基站则负责上下行数据业务的分流以提高用户的峰值吞吐量。
用户设备与基站进行通信时，需要先建立无线资源控制(Radio Resource Control，RRC)连接，只有当RRC连接成功，基站与用户之间才能实现通信，但是，若出现RRC连接失败，即基站切换配置出现问题，需要重新建立RRC连接，才能够保证UE与基站之间顺利通信。
现有技术中，若出现RRC连接失败，则需要对主辅基站建立RRC重连接，
而基站切换配置中一旦出现RRC连接失败时，无论是MCG配置失败，还是SCG配置失败，均需要通过MCG发起RRC重建，这种做法占用了MCG的无线资源，严重影响了用户与MCG之间的正常数据通信。
参阅图1所示，以LTE-A的双连接技术的用户设备为例。用户设备需要一个MeNB和至少一个SeNB，而用户设备只有在成功建立RRC连接之后才能实现与基站的通信。在双连接技术的控制面协议中规定，只有MeNB能产生最后的RRC消息，且将此RRC消息传递给用户设备并以此建立RRC连接。具体步骤如下：MeNB向SeNB提供用户设备配置 参数(如用户设备的能力、用户设备的无线资源配置等等)；SeNB接收到MeNB发送的用户设备配置参数后，生成相应的SCG配置信息[如，物理上行链路控制信道(Physical Uplink Control Channel，PUCCH)配置信息]反馈给MeNB，MeNB基于本地配置的MCG配置信息和SeNB提供的SCG配置信息生成最终的RRC消息，并将此RRC消息发送给用户设备以建立RRC连接。
具体的，当MeNB和SeNB上同时配置了载波聚合(Carrier Aggregation，CA)，即MeNB下管理的小区数不止一个时，MeNB管理的小区组即组成了MCG，同样的，SeNB下管理的小区数不止一个时，SeNB管理的小区组即组成了SCG。
具体的，MeNB保存用户设备的无线资源管理(Radio Resource Management，RRM)测量配置信息，以接收到的测量报告(如业务情况、承载类型等等)决定是否需要SeNB为用户设备提供额外的服务小区资源(如SCG的SCells等等)，若需要SeNB为用户设备提供额外的服务小区资源，则向SeNB发送请求信息；SeNB会根据从MeNB接收到的请求信息决定是否为用户设备增加服务小区的配置信息，即生成SCG配置信息；MeNB和SeNB通过X2接口进行信息交互(如，MeNB向SeNB发送UE配置参数、SeNB向MeNB发送SCG配置信息等等)；相应的，MeNB本地也会生成一部分SCG配置信息，MeNB会将MeNB本地生成SCG配置信息结合由SeNB发送来的SCG配置信息组合成新的SCG配置信息，并且再结合MCG本地生成的MCG信息，生成最终的RRC消息发送给用户设备，其中，MeNB不会改变SeNB上传的SCG配置信息。
进一步地，如果用户设备接收到RRC后，会进行MCG配置和SCG配置，在MCG配置成功的情况下，一旦SCG配置失败，用户终端则会认为RRC连接失败，会通知MeNB发起RRC重建。然而，MCG配置成功后，用户设备是是可以正常通信的，因此，一旦MeNB基于SCG配置失败发起RRC重建，将会产生严重的数据中断，从而严重影响了用户设备的正常通信。
参阅图2a和图2b所示，以5G系统中LTE和NR tightinterworking为例。
其中，5G系统中LTE和NR tightinterworking的协议架构参阅图3所示，
在此协议架构下，RRC消息既能由MCG产生，又能由SCG产生，当RRC消息由MCG产生时，该RRC消息通过主信令无线承载(Signaling Radio Bearer，SRB，简称主承载)，如SRB1，发送给用户设备。当RRC消息由SCG产生时，该RRC消息通过辅承载(SRB on the secondary)，如SRB3，发送给用户设备。
因此，基于上述协议，无论是以LTE为MeNB，NR为SeNB(如图2a)，还是以NR为MeNB，LTE为SeNB(如图2b)，SCG的配置信息可以通过如下两种方式下发：
方式一：SCG配置信息和MCG配置信息均由MCG下发给用户设备，在此方式中，一旦出现RRC连接失败，则不论是MCG的配置信息失败，还是SCG的配置信息失败， 协议均认定由MCG发起RRC重建。
方式二：SCG配置信息由SCG下发给用户设备，MCG配置信息由MCG下发给用户设备，即各自下发对应的配置信息，在此方式中，若SCG的配置信息失败，而MCG的配置信息成功，则协议也会认定由MCG发起RRC重建。
显然，在5G系统LTE和NR tightinterworking联合工作的场景下，一旦SCG配置信息配置失败，即使MCG配置信息配置成功，也会由MCG发起RRC重建，这样，会产生严重的数据中断，从而严重影响了用户设备的正常通信。
有鉴于此，需要设计一种新的基站配置方法克服上述缺陷。
发明内容
本申请实施例提供一种小区配置方法及装置，用以避免严重的数据中断，保证用户设备的正常通信。
本申请实施例提供的具体技术方案如下：
一种小区配置方法，应用于主基站MeNB和辅基站SeNB联合工作的场景，包括：
第一基站触发设置辅小区组SCG配置信息；
第一基站触发将所述SCG配置信息发往用户设备UE，并触发所述UE进行SCG配置；
第一基站接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
可选的，第一基站触发设置SCG配置信息，包括：
若第一基站是MeNB，则第一基站触发SeNB针对UE设置相应的SCG配置信息。
若第一基站是SeNB，则第一基站在本地直接触发针对UE设置相应的SCG配置信息。
可选的，第一基站触发将所述SCG配置信息发往UE，包括：
若第一基站是MeNB，则第一基站采用第一消息，将本地设置的MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，第一基站采用第一消息，将SeNB设置的SCG配置信息发往UE；
若第一基站是SeNB，则第一基站采用第一消息，直接将本地设置的SCG配置信息发往UE。
可选的，第一基站接收到SCG重配置失败信息时，确定UE执行SCG配置失败，包括：
若第一基站是MeNB，则第一基站直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
若第一基站是SeNB，则第一基站接收MeNB发送的SCG重配置失败信息时，确定 UE执行SCG配置失败；其中，MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向第一基站发送的。
可选的，第一基站确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，包括：
若第一基站为MeNB，则第一基站确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，第一基站确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
若第一基站为SeNB，则第一基站确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
可选的，第一基站确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放，包括：
若第一基站为MeNB，则第一基站确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，第一基站确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
若第一基站为SeNB，则第一基站确定UE执行SCG配置失败，以及确定MCG配置成功后，执行SCG释放。
可选的，进一步包括：
第一基站基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
可选的，第一基站基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息，包括：
若第一基站是MeNB，则第一基站将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往第一基站，再由第一基站发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往UE；
若第一基站是SeNB，则第一基站接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，第一基站直接将所述新的SCG配置信息下发给UE。
可选的，第一基站基于所述SCG配置失败原因，触发重新设置新的SCG配置信息， 包括：
第一基站触发SeNB执行以下操作中的任意一种：
若确定SCG配置失败原因为SCG配置失败，则按照预设方式重新设置新的SCG配置信息；
若确定SCG配置失败原因为超过UE能力，则与MeNB重新进行协商，并在对UE能力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
若确定SCG配置失败原因为解析错误或参数错误，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
一种小区配置方法，应用于主基站MeNB和辅基站SeNB联合工作的场景，包括：
用户设备UE根据网络侧下发的辅小区组SCG配置信息进行SCG配置；
UE确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
UE确定主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，UE确定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放，包括：
若UE还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则UE使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
若UE未接收到网络侧下发的MCG配置信息，则UE维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，UE向网络侧发送SCG重配置失败信息之前，还包括：
UE确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败信息。
可选的，UE确定的SCG配置失败原因，包括以下原因中的任意一种：
SCG配置失败；
超过UE能力；
解析错误；
参数错误。
一种小区配置装置，应用于主基站MeNB和辅基站SeNB联合工作的场景，包括：
第一触发单元，用于触发设置辅小区组SCG配置信息；
第二触发单元，用于触发将所述SCG配置信息发往用户设备UE，并触发所述UE进行SCG配置；
处理单元，用于接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且 在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
可选的，触发设置SCG配置信息时，所述第一触发单元用于：
若所述装置是MeNB，则触发SeNB针对UE设置相应的SCG配置信息。
若所述装置是SeNB，则在本地直接触发针对UE设置相应的SCG配置信息。
可选的，所述第二触发单元用于采用如下方式触发将所述SCG配置信息发往UE：
若所述装置是MeNB，则采用第一消息，将本地设置的MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，采用第一消息，将SeNB设置的SCG配置信息发往UE；
若所述装置是SeNB，则采用第一消息，直接将本地设置的SCG配置信息发往UE。
可选的，所述处理单元用于采用如下方式，在接收到SCG重配置失败信息时，确定UE执行SCG配置失败：
若所述装置是MeNB，则直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
若所述装置是SeNB，则接收MeNB发送的SCG重配置失败信息时，确定UE执行SCG配置失败；其中，MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向所述装置发送的。
可选的，所述处理单元用于采用如下方式确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一次下发的原SCG配置信息不变：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
可选的，所述处理单元用于采用如下方式确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，执行SCG释放。
可选的，所述处理单元进一步用于：
基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
可选的，所述处理单元用于采用如下方式基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息：
若所述装置是MeNB，则将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往所述装置，再由所述装置发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往UE；
若所述装置是SeNB，则接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，直接将所述新的SCG配置信息下发给UE。
可选的，基于所述SCG配置失败原因，触发重新设置新的SCG配置信息时，所述处理单元用于触发SeNB执行以下操作中的任意一种：
若确定SCG配置失败原因为SCG配置失败，则按照预设方式重新设置新的SCG配置信息；
若确定SCG配置失败原因为超过UE能力，则与MeNB重新进行协商，并在对UE能力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
若确定SCG配置失败原因为解析错误或参数错误，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
一种小区配置装置，应用于主基站MeNB和辅基站SeNB联合工作的场景，包括：
配置单元，用于根据网络侧下发的辅小区组SCG配置信息并进行SCG配置；
通信单元，用于确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
处理单元，用于确定在主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，所述处理单元用于采用如下方式，在确定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变时，或者，执行SCG释放：
若还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
若未接收到网络侧下发的MCG配置信息，则维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，所述通信单元用于采用如下方式向网络侧发送SCG重配置失败信息：
确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败 信息，向网络侧发送所述SCG重配置失败信息。
可选的，确定SCG配置失败原因时，所述通信单元用于确定SCG配置失败原因为以下原因中的任意一种：
SCG配置失败；
超过UE能力；
解析错误；
参数错误。
一种小区配置装置，包括处理器、收发机和存储器，其中，
所述处理器，用于读取所述存储器中的程序，执行下列过程：
通过所述收发机发送SCG配置信息，或接收SCG重配置失败信息；
触发设置辅小区组SCG配置信息；
触发将所述SCG配置信息发往用户设备UE进行SCG配置；
接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
所述收发机，用于在处理器的控制下接收和发送数据。
可选的，所述处理器用于采用如下方式触发设置SCG配置信息：
若所述装置是MeNB，则触发SeNB针对UE设置相应的SCG配置信息。
若所述装置是SeNB，则在本地直接触发针对UE设置相应的SCG配置信息。
可选的，所述处理器用于采用如下方式触发将所述SCG配置信息发往UE：
若所述装置是MeNB，则采用第一消息，将本地设置的主小区组MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，采用第一消息，将SeNB设置的SCG配置信息发往UE；
若所述装置是SeNB，则采用第一消息，直接将本地设置的SCG配置信息发往UE。
可选的，所述处理器用于采用如下方式，在接收到SCG重配置失败信息时，确定UE执行SCG配置失败：
若所述装置是MeNB，则直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
若所述装置是SeNB，则接收MeNB发送的SCG重配置失败信息时，确定UE执行SCG配置失败；其中，MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向所述装置发送的。
可选的，所述处理器用于采用如下方式确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一次下发的原SCG配置信息不变：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
可选的，所述处理器用于采用如下方式，确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，执行SCG释放。
可选的，所述处理器进一步用于：
基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
可选的，所述处理器用于采用如下方式基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息：
若所述装置是MeNB，则将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往所述装置，再由所述装置发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往UE；
若所述装置是SeNB，则接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，直接将所述新的SCG配置信息下发给UE。
可选的，基于所述SCG配置失败原因，触发重新设置新的SCG配置信息时，所述处理器用于触发SeNB执行以下操作中的任意一种：
若确定SCG配置失败原因为SCG配置失败，则按照预设方式重新设置新的SCG配置信息；
若确定SCG配置失败原因为超过UE能力，则与MeNB重新进行协商，并在对UE能力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
若确定SCG配置失败原因为解析错误或参数错误，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
一种小区配置装置，包括处理器、收发机、存储器和用户接口，其中，
所述处理器，用于读取所述存储器中的程序，执行下列过程：
通过所述收发机发送SCG重配置失败信息，或接收SCG配置信息；
根据网络侧下发的辅小区组SCG配置信息并进行SCG配置；
确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
确定在主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放；
所述收发机，用于在所述处理器的控制下接收和发送数据。
可选的，所述处理器用于采用如下方式，在确定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变时，或者，执行SCG释放：
若还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
若未接收到网络侧下发的MCG配置信息，则维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，所述处理器用于采用如下方式通过所述收发机向网络侧发送SCG重配置失败信息：
确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败信息，通过所述收发机向网络侧发送所述SCG重配置失败信息。
可选的，确定SCG配置失败原因时，所述处理器用于确定SCG配置失败原因为以下原因中的任意一种：
SCG配置失败；
超过UE能力；
解析错误；
参数错误。
本申请有益效果如下：
在MeNB和SeNB联合应用的场景下，第一基站将SCG配置信息发送给UE进行SCG配置，当UE确定SCG配置失败时，会向网络侧发送SCG重配置失败信息，此时，UE和网络侧会在确定MCG配置成功时，维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放，即在仅有SCG配置失败的情况下，不会频繁发起RRC重建，而是使用原来的SCG配置信息，这样，有效避免了严重的数据中断，保证了用户设备的正常通信，从而提高了数据传输效率，保证了系统性能，也提高了用户体验。
附图说明
图1为现有技术下LTE-A系统的双连接技术示意图；
图2a和图2b为现有技术下5G系统中LTE和NR tightinterworking示意图；
图3为现有技术下5G系统中LTE和NR tightinterworking协议架构图；
图4为本申请实施例中小区配置流程图；
图5为本申请实施例中MeNB下发SCG配置信息且UE发生“SCG配置失败”情况的处理流程图；
图6为本申请实施例中MeNB下发SCG配置信息且UE发生“解析错误”情况的处理流程图；
图7为本申请实施例中SeNB下发SCG配置信息且UE发生“参数错误”情况的处理流程图；
图8为本申请实施例中SeNB下发SCG配置信息且UE发生“超过UE能力”情况的处理流程图；
图9为本申请实施例中MeNB下发SCG配置信息且UE发生“SCG配置失败”情况下SeNB执行SCG释放的处理流程图；
图10为本申请实施例中第一基站第一种功能结构示意图；
图11为本申请实施例中UE第一种功能结构示意图；
图12为本申请实施例中第一基站第二种功能结构示意图；
图13为本申请实施例中UE第二种功能结构示意图。
具体实施方式
用以避免严重的数据中断，保证用户设备的正常通信，本申请实施例中，设计了一种小区配置方案，该方案为：在MeNB和SeNB联合应用的场景下，当UE确定SCG配置失败时，会向网络侧发送SCG重配置失败信息，此时，UE和网络侧均会在确定MCG配置成功时，维持上一次下发的原SCG配置信息不变。
下面结合附图对本申请优选的实施方式进行详细说明。
参阅图2a和图2b所示，本申请实施例中以5G系统中LTE和NR tightinterworking的场景为例。
在上述场景中，参阅图4所示，基站(可以是MeNB，也可以是SeNB)指示UE进行小区配置的详细流程如下：
步骤400：第一基站获得UE状态信息，其中，UE状态信息可以包括多种类型的参数，如，UE的能力信息，UE无线资源配置信息等等。
本申请实施例中，第一基站可以是宏基站，如LTE eNB、5G NR NB等；也可以是小基站，如低功率节点(Low Power Node，LPN)、微微基站(pico)、家庭基站(femto)等，接入点(Access Point，AP)；也可以是中央单元(Central Unit，CU)与其管理和控制的多个传输接收点(Transmission Reception Point，TRP)共同组成的网络节点。一个基站下有一个或多个小区(不同的频点或扇区分裂)。无论是宏基站，还是小基站均可以做为主基站，即MeNB，或者，也可以做为辅基站，即SeNB。
本申请实施例中，在执行步骤400时，第一基站可以采用但不限于以下方式：
方式A1：若第一基站是MeNB，则可以直接根据UE的上报(如，上报的测量报告、业务情况、承载类型等等)，来确定UE状态信息。
方式B1：若第一基站是SeNB，则可以根据MeNB的通知，来获得UE状态信息，或者，第一基站也可以直接根据UE的上报(如，上报的测量报告、业务情况、承载类型等等)来确定UE状态信息。
步骤410：第一基站触发设置SCG配置信息。
本申请实施例中，在执行步骤410时，第一基站可以采用但不限于以下方式：
方式A2：若第一基站是MeNB，则第一基站将UE状态信息发往SeNB，触发SeNB基于该UE状态信息设置相应的SCG配置信息。
方式B2：若第一基站是SeNB，则第一基站基于获得的UE状态信息，在本地直接触发设置相应的SCG配置信息。
步骤420：第一基站触发将上述SCG配置信息发往UE。
本申请实施例中，第一基站通常会采用第一消息进行触发(第一消息可以为RRC，以下相同，不再赘述)，相应的，在执行步骤420时，第一基站可以采用但不限于以下方式
方式A3：若第一基站是MeNB，则第一基站可以采用RRC消息，将本地设置的MCG配置信息和获得的SCG配置信息一同发往UE；或者，也可以采用RRC消息，仅将获得的SCG配置信息发往UE，此时，UE将会重新配置SCG，而维持原MCG配置信息不变。
具体的，由MeNB产生的新的RRC消息〔如，RRC连接重配置(Connection Reconfiguration)消息等等〕，其中，上述RRC消息包含由SeNB产生的SCG配置信息(如，SCG配置信息的ASN.1)和本地设置的MCG配置信息，以及，MeNB将上述RRC消息通过主承载(例如，SRB1)发送给UE；或者，MCG也可以在原有的RRC消息中采用容器(container)方式增加一个字段，如在信息传递(DL informationTransfer)消息中增加信息单元(information element，IE)，用于传输SCG配置信息。
方式B3：若第一基站是SeNB，则第一基站可以采用RRC消息，直接将本地生成的 SCG配置信息发往UE。
具体的，由SeNB产生的RRC消息，其中，上述RRC信息包含由SCG产生的SCG配置信息，以及，由SeNB并将上述RRC消息通过辅承载(SRB on the secondary)发送给UE。
在SeNB发送SCG配置信息的过程中，MeNB也有可能将自身设置的MCG配置信息发往UE，如果UE同时获得MCG配置信息和SCG配置信息，则可以分别重新配置MCG和SCG，若UE仅获得SCG配置信息，则UE将会重新配置SCG，而维持原MCG配置信息不变。
步骤430：UE获得上述SCG配置信息后，在本地进行SCG配置。
由前述内容可知，若UE从MeNB发送的RRC消息中同时获得了MCG配置信息和SCG配置信息，或者，若UE从MeNB发送的RRC消息中获得了MCG配置信息，从SeNB发送的RRC消息中获得了SCG配置信息，则UE会分别重新配置MCG和SCG；
而若UE仅从SeNB发送的RRC消息中获得SCG配置信息，则UE会重新配置SCG，同时，将维持原MCG配置信息不变。
步骤440：UE确定SCG配置失败，则维持原SCG配置信息不变，或者，执行SCG释放。
本申请实施例中，所谓的原SCG配置信息即是UE上一次获得的SCG配置信息，也是UE当前正在使用的SCG配置信息，在UE确定SCG配置失败后，确定在MCG配置成功时，UE会沿用上一次配置的原SCG配置信息或者执行SCG释放，而不是开始执行RRC重建流程。
而MCG配置成功是分两种情况，一种是UE获得MCG配置信息，并成功执行了MCG配置，此时MeNB和UE均会使用配置成功的MCG配置；第二种是MeNB未向UE下发MCG配置信息，此时MeNB和UE均会维持原MCG配置信息不变，但无论是哪一种情况，只要SCG配置失败，UE均会维持原SCG配置信息不变，或者，执行SCG释放。
具体的，执行步骤440时，会分为以下三种情况：
第一种情况为：UE从MeNB发送的RRC消息中获得了MCG配置信息和SCG配置信息，由于该RRC消息同时包含了两条配置信息，按照默认的处理优先级，UE会先处理MCG配置信息，再处理SCG配置信息。
若MCG配置失败，那么，UE会通知MCG直接进行RRC重建，本申请实施例中不考虑这种情况，因此不再赘述。
若MCG配置成功，而SCG配置失败，则UE采用新的MCG配置信息，而维持原SCG 配置信息不变或者执行SCG释放。
第二种情况为：UE从MeNB发送的RRC消息中获得了SCG配置信息，其中，该RRC消息仅包含SCG配置信息，即，无论SCG配置是否成功，UE均会维持原MCG配置信息不变，那么，当SCG配置失败时，则UE不仅会维持原MCG配置信息不变，且维持原SCG配置信息不变或者执行SCG释放。
第三种情况为：UE从SeNB发送的RRC消息中获得了SCG配置信息，
那么当SCG配置失败时，则UE不采用新的SCG配置信息，而是维持原SCG配置信息不变或者执行SCG释放。
步骤450：UE确定SCG配置失败原因。
本申请实施例中，SCG配置失败的原因包含但不限于以下四种：
第一种原因：具体描述的“超过UE能力”。“超过UE能力”可以理解为是UE接收到的SCG配置信息中的某些参数超出了UE接入的能力，如，分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)配置中的上下文标识的最大数(Max Context Identifier，maxCID)超过了UE的能力信息指示的鲁棒性头压缩上下文的最大数。
第二种原因：具体描述的“解析错误”。“解析错误”可以理解为是UE不能正确解析接收到的SCG配置信息中的某些内容，如，SCG配置信息中包含的ASN.1不能被UE识别，或，在信息传递消息(DL informationTransfer)中增加的IE的内容不能被UE识别。
第三种原因：具体描述的“参数错误”。“参数错误”可以理解为是UE接收到的SCG配置信息中包含错误的配置参数，如，假设UE中SCG的某个配置参数的范围在0～100之内，而UE接收到的SCG配置信息中该参数的值为200。
第四种原因：概括描述的“SCG配置失败”。“SCG配置失败”可以理解为是不具体区分究竟是哪一种SCG配置失败原因，而是笼统的将SCG配置失败原因记载为概括描述的“SCG配置失败”。
步骤460：UE将SCG配置失败原因携带在SCG重配置失败信息中发送至第一基站，通知第一基站SCG配置失败。
本申请实施例中，UE可以基于确定的SCG配置失败原因生成相应的SCG重配置失败信息，再将SCG重配置失败信息发往第一基站，具体的，在执行步骤460时，UE可以采用但不限于以下方式:
方式A4：若第一基站为MeNB，则UE可以将携带有SCG配置失败原因的SCG重配置失败信息直接发送至第一基站；
方式B4：若第一基站为SeNB，则UE可以先将携带有SCG配置失败原因的SCG重 配置失败信息发送至MeNB，然后，SeNB再接收MeNB发送的携带有SCG配置失败原因的SCG重配置信息；其中，MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后发送的，是MeNB基于UE发送的SCG重配置失败信息，按照与SeNB之间的通信协议独立生成的信息。
无论采用哪一种方式，UE均会通过主承载(例如，SRB1)将SCG重配置失败信息发送至MeNB，其中，空口上发送的SCG重配置失败信息可以是一条独立的RRC消息，也可以是原有的RRC消息中的IE，不论是哪一种形式的SCG重配置失败信息，均包含了SCG配置失败原因。
具体的，本申请实施例中，UE在SCG配置失败信息中记载SCG配置失败原因时，可以采用但不限于以下两种方法：
方法一：概括描述。
其中，UE将SCG配置失败原因在SCG配置失败信息中统一记载为SCG重配置失败(scg-ReconfigurationFailure)。
方法二：具体描述。
其中，UE将SCG配置失败原因在SCG配置失败信息中按具体失败原因分类记载，如：超过UE能力(UECapability-Exceed)、解析错误(ParseError)和参数错误(ParameterError)。
步骤470：第一基站触发维持原SCG配置信息不变，并基于获得的SCG配置失败原因，触发重新设置以及重新发送相应的新的SCG配置信息，或者，触发执行SCG释放。
第一基站获知发送的SCG配置信息未设置成功时，也会自动触发沿用原SCG配置信息(即上次一配置的SCG配置信息)或者触发执行SCG释放，而不是触发RRC重建流程。
例一：第一基站是MeNB时，第一基站会在接收到UE发送的SCG重配置失败信息时，确定MCG配置成功，SCG配置失败，此时，第一基站会使用配置成功的MCG配置信息，以及向SeNB发送SCG重配置失败信息，触发SeNB维持原SCG配置信息不变或者触发SeNB执行SCG释放；或者，第一基站会在接收到UE发送的SCG重配置失败信息时(此时可能未下发MCG配置信息)，确定未进行MCG配置，SCG配置失败，此时，第一基站会维持原MCG配置信息不变，以及向SeNB发送SCG重配置失败信息，触发SeNB维持原SCG配置信息不变或者触发SeNB执行SCG释放。
例二，第一基站是SeNB时，第一基站会在接收到MeNB发送的SCG重配置失败信息时，确定SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变或者执行SCG释放，其中，第一基站接收到的MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后向第一基站发送的；其中，第一 基站确定MCG配置成功，即表示MeNB并未指示第一基站触发RRC重建流程，此时，无论MeNB使用新的MCG配置信息还是维持原MCG配置信息不变，只要第一基站未收到用于触发RRC重建流程的指示，即认为此时MCG配置成功。
具体的，本申请实施例中，在触发重新设置以及重新发送相应的新的SCG配置信息时，第一基站可以采用但不限于以下方式:
方式A5：若第一基站是MeNB，则第一基站将获得的SCG配置失败原因通过发送给SeNB，由SeNB基于SCG配置失败原因重新设置新的SCG配置信息，设置完成后，由SeNB将新的SCG配置信息发往MeNB，再由MeNB发往UE，或者，SeNB也可以直接将新的SCG配置信息发往UE。
方式B5：若第一基站是SeNB，则第一基站接收到MeNB发送的SCG配置失败原因后，基于该SCG配置失败原因在本地重新设置新的SCG配置信息，设置完成后，第一基站将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，第一基站也可以直接将新的SCG配置信息下发给UE。
在上述方式A5和B5中，若新的SCG配置信息由MeNB发送，则MeNB会依据例一或例二中记载的方式，若MCG配置成功，则使用配置成功的MCG配置信息下发新的SCG配置信息，若MCG未发生改变，则使用原MCG配置信息下发新的SCG配置信息。
同理，在上述方式A5和B5中，若新的SCG配置信息由SeNB发送，则SeNB会依据例一或例二中记载的方式，在确定SCG配置失败时，使用原SCG配置信息，下发新的SCG配置信息。
另一方面，在进行SCG配置信息的重新设置时，包含但不限于以下两种情况：
第一种情况为：解析出的失败原因为概括描述的“SCG重配置失败”，则SeNB会按照预设方式重新设置新的SCG配置信息。
例如，SeNB与MeNB重新协商后，重新配置新的SCG配置信息。
又例如，SeNB对上一次下发的SCG配置信息进行调整后，生成新的SCG配置信息。
具体采用哪一种方式视应用环境而定。
第二种情况为：解析出的失败原因为具体描述的：“超过UE能力”、“解析错误”或“参数错误”，则根据具体原因进行相应处理。
其中，具体描述的失败原因又可按具体原因分为两类进行相应处理。
第一类：若解析出的失败原因为原SCG配置信息超过UE能力，则需要在SeNB会与MeNB之间发起UE能力协商对话重新进行UE能力协商，待重新确定UE能力后，第一基站再设置相应的新的SCG配置信息；
第二类：若解析出的失败原因为UE不能解析出原SCG配置信息或者原SCG配置信息中存在参数错误，则在原SCG配置信息进行相应调整(如，对SCG配置信息进行重新编码、重新设置新的参数等等)即可生成新的SCG配置信息。
步骤480：UE根据接收到的新的SCG配置信息，进行SCG配置。
至此，UE可以获得的新的SCG配置信息，并基于新的SCG配置信息进行SCG配置，在配置完成后，UE便可以开始使用新的SCG配置信息与网络侧进行数据传输。
基于上述实施例，下面采用具体的应用场景对上述实施例作出进一步详细说明。
第一种场景为：由MeNB下发SCG配置信息，且UE发生“SCG配置失败”的情况。
参阅图5所示，第一种场景的具体流程如下：
步骤500：SeNB向MeNB发送SCG配置信息。
具体的，SeNB可以先获得UE状态信息，再基于UE状态信息设置相应的SCG配置信息，如，采用抽象语法表示法(ASN)进行编译，产生SCG配置信息的ASN.1，并将生成的SCG配置信息发送给MeNB。
步骤510：MeNB向UE下发MCG配置信息和SCG配置信息。
MeNB从SeNB接收到SCG配置信息，将该SCG配置信息结合本地设置的MCG配置信息产生RRC消息，并将此RRC消息通过主承载(例如，SRB1)发送给UE。
步骤520：UE确定SCG配置失败。
UE从MeNB发送的RRC消息中获得了MCG配置信息和SCG配置信息，由于该RRC消息同时包含了两条配置信息，按照默认的处理优先级，UE会先处理MCG配置信息，再处理SCG配置信息。此时，若MCG配置成功，而SCG配置失败，则UE采用配置成功的MCG配置信息，而维持原SCG配置信息不变，并确定SCG配置失败原因。
具体的，SCG配置失败原因有四种，即概括描述的“SCG配置失败”，以及具体描述的“超过UE能力”、“解析错误”和“参数错误”。在本场景中，以“SCG配置失败”为SCG配置失败原因为例进行说明，因此，UE将SCG配置失败原因确定为概括描述的“SCG配置失败”。
步骤530：UE向MeNB发送SCG重配置失败信息，通知SCG配置失败原因。
UE确认SCG配置失败后，会以一条独立的RRC消息通过主承载(例如，SRB1)向MeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，概括描述的“SCG重配置失败”。
步骤540：MeNB向SeNB发送SCG重配置失败信息，通知SCG重配置失败原因。
MeNB接收到UE发送的SCG重配置失败信息，并向SeNB发送SCG重配置失败信 息，其中，包含了SCG配置失败原因，即，概括描述的“SCG重配置失败”。
步骤550：SeNB向MeNB发送新的SCG配置信息。
SeNB收到MeNB发送的SCG重配置失败信息后，SeNB会根据失败原因“SCG重配置失败”，重新与MeNB协商，重新评估UE的能力后，产生相应的新的SCG配置信息，并将新的SCG配置信息发送给MeNB。
步骤560：MeNB向UE下发新的SCG配置信息。
MeNB接收到新的SCG配置信息后会产生RRC连接重配置消息，其中，RRC连接重配置消息包含了新的SCG配置信息，而在步骤520中，UE已成功配置了MCG配置信息，因而，MeNB本次发送RRC连接重配置消息时，会使用上述配置成功的MCG配置信息，且MeNB会将该RRC连接重配置消息通过主承载(例如，SRB1)发送给UE。
至此，UE可以获得的新的SCG配置信息，并基于新的SCG配置信息进行SCG配置，在配置完成后，UE便可以开始使用新的SCG配置信息与网络侧进行数据传输。
当然，SeNB也可以直接向UE下发新的SCG配置信息，上述过程仅为举例，当SeNB直接下发新的SCG配置信息时，由于在步骤520中，如果UE维持原SCG配置信息不变，那么SeNB需要使用原SCG配置信息，通过辅承载(SRB on the secondary)，例如，SRB3，向UE发送携带有新的SCG配置信息的RRC消息。
第二种场景为：由MeNB下发SCG配置信息，且UE发生“解析错误”的情况。
参阅图6所示，第二种场景的具体流程如下：
步骤600：SeNB向MeNB发送SCG配置信息。
具体的，SeNB可以先获得UE状态信息，再基于UE状态信息设置相应的SCG配置信息，如，采用ASN进行编译，产生SCG配置信息的ASN.1，并将生成的SCG配置信息发送给MeNB。
步骤610：MeNB向UE下发SCG配置信息。
MeNB从SeNB接收到SCG配置信息，并采用RRC消息将该SCG配置通过主承载(例如，SRB1)发送给UE，由于本申请实施例中，MeNB未向UE下发MCG配置信息，因此，UE会维持原MCG配置信息不变。
步骤620：UE确定SCG配置失败。
UE从MeNB获得了SCG配置信息，若SCG配置失败，则UE不采用新的SCG配置信息，而维持原SCG配置信息不变，并确定SCG配置失败原因。
具体的，SCG配置失败原因有四种，即概括描述的“SCG配置失败”，以及具体描述的“超过UE能力”、“解析错误”和“参数错误”。在本场景中，以“解析错误”为SCG 配置失败原因为例进行说明，因此，UE将SCG配置失败原因确定为具体描述的“解析错误”。
步骤630：UE向MeNB发送SCG重配置失败信息，通知SCG配置失败原因。
UE确认SCG配置失败后，会以一条独立的RRC消息通过主承载(例如，SRB1)向MeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，具体描述的“解析错误”。
步骤640：MeNB向SeNB发送SCG重配置失败信息，通知SCG重配置失败原因。
MeNB接收到UE发送的SCG重配置失败信息，并向SeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，具体描述的“解析错误”。
步骤650：SeNB向UE下发新的SCG配置信息。
SeNB收到MeNB发送的SCG重配置失败信息后，SeNB会根据失败原因“解析错误”，在原SCG配置信息进行相应调整(如，对SCG配置信息进行重新编码等等)，生成相应的新的SCG配置信息，并将新的SCG配置信息下发给UE。
SeNB直接向UE下发新的SCG配置信息时，由于在步骤620中，如果UE维持原SCG配置信息不变，那么，SeNB需要使用原SCG配置信息，通过辅承载(SRB on the secondary)向UE发送携带有新的SCG配置信息的RRC消息。
至此，UE可以获得的新的SCG配置信息，并基于新的SCG配置信息进行SCG配置，在配置完成后，UE便可以开始使用新的SCG配置信息与网络侧进行数据传输。
当然，SeNB也可以通过MeNB向UE下发新的SCG配置信息，上述过程仅为举例，当SeNB通过MeNB向UE下发新的SCG配置信息时，MeNB接收到新的SCG配置信息后会产生RRC连接重配置消息，其中，RRC连接重配置消息包含了新的SCG配置信息，而在步骤610中，如果UE维持原MCG配置信息不变，那么，MeNB本次发送RRC连接重配置消息时，会继续使用上述MCG配置信息，且MeNB会将该RRC连接重配置消息通过主承载(例如，SRB1)发送给UE。
第三种场景为：由SeNB下发SCG配置信息，且UE发生“参数错误”的的情况。
参阅图7所示，第三种场景的具体流程如下：
步骤700：SeNB向UE发送SCG配置信息。
具体的，SeNB可以先获得UE状态信息，再基于UE状态信息设置相应的SCG配置信息，并将生成的SCG配置信息发送给UE。
步骤710：UE确定SCG配置失败。
UE直接从SeNB获得了SCG配置信息，若SCG配置失败，则确定SCG配置失败原 因。
由于本申请实施例中，MeNB并未向UE发送MCG配置信息，因此，UE维持原MCG配置信息不变。
具体的，SCG配置失败原因有四种，即概括描述的“SCG配置失败”，以及具体描述的“超过UE能力”、“解析错误”和“参数错误”。在本场景中，以“参数错误”为SCG配置失败原因为例进行说明，因此，UE将SCG配置失败原因确定为具体描述的“参数错误”。
步骤720：UE向MeNB发送SCG重配置失败信息，通知SCG配置失败原因。
UE确认SCG配置失败后，会以一条独立的RRC消息通过主承载(例如，SRB1)向MeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，具体描述的“参数错误”。
步骤730：MeNB向SeNB发送SCG重配置失败信息，通知SCG重配置失败原因。
MeNB接收到UE发送的SCG重配置失败信息，并向SeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，具体描述的“参数错误”。
步骤740：SeNB向MeNB发送新的SCG配置信息。
SeNB收到MeNB发送的SCG重配置失败信息后，SeNB会根据失败原因“参数错误”，在原SCG配置信息进行相应调整(如重新设置新的参数等等)，生成相应的新的SCG配置信息，并将新的SCG配置信息发送给MeNB。
步骤750：MeNB向UE下发新的SCG配置信息。
MeNB接收到新的SCG配置信息后会产生RRC连接重配置消息，其中，RRC连接重配置消息包含了新的SCG配置信息，而在步骤710中，如果UE维持原MCG配置信息不变，那么，MeNB本次发送RRC连接重配置消息时，会继续使用上述MCG配置信息，且MeNB会将该RRC连接重配置消息通过主承载(例如，SRB1)发送给UE。
至此，UE可以获得的新的SCG配置信息，并基于新的SCG配置信息进行SCG配置，在配置完成后，UE便可以开始使用新的SCG配置信息与网络侧进行数据传输。
当然，SeNB也可以直接向UE下发新的SCG配置信息，上述过程仅为举例，当SeNB直接向UE下发新的SCG配置信息时，如果UE维持原SCG配置信息不变，那么，SeNB需要使用原SCG配置信息，通过辅承载(SRB on the secondary)，例如，SRB3，向UE下发携带有新的SCG配置信息的RRC消息。
第四种场景为：由SeNB下发SCG配置信息，且UE发生“超过UE能力”的情况。
参阅图8所示，第四种场景的具体流程如下：
步骤800：SeNB向UE下发SCG配置信息。
具体的，SeNB可以先获得UE状态信息，再基于UE状态信息设置相应的SCG配置信息，并将生成的SCG配置信息发送给UE。
步骤810：UE确定SCG配置失败。
UE直接从SeNB获得了SCG配置信息，若SCG配置失败，则确定SCG配置失败原因。
由于本申请实施例中，由于MeNB并未向UE发送MCG配置信息，因此，UE维持原MCG配置信息不变。
具体的，SCG配置失败原因有四种，即概括描述的“SCG配置失败”，以及具体描述的“超过UE能力”、“解析错误”和“参数错误”。在本场景中，以“参数错误”为SCG配置失败原因为例进行说明，因此，UE将SCG配置失败原因确定为具体描述的“超过UE能力”。
步骤820：UE向MeNB发送SCG重配置失败信息，通知SCG配置失败原因。
UE确认SCG配置失败后，会以一条独立的RRC消息通过主承载(例如，SRB1)向MeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，具体描述的“超过UE能力”。
步骤830：MeNB向SeNB发送SCG重配置失败信息，通知SCG重配置失败原因。
MeNB接收到UE发送的SCG重配置失败信息，并向SeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，具体描述的“超过UE能力”。
步骤840：SeNB与MeNB进行UE能力协商。
SeNB收到MeNB发送的SCG重配置失败信息后，SeNB会根据失败原因“超过UE能力”，重新与MeNB协商，重新评估UE的能力后，产生相应的新的SCG配置信息，并将新的SCG配置信息直接发送给UE。
步骤850：SeNB向UE下发新的SCG配置信息。
SeNB产生新的SCG配置信息直接发送给UE，如果UE维持原SCG配置信息不变，那么，SeNB需要使用原SCG配置信息，通过辅承载(SRB on the secondary)，例如，SRB3，向UE下发携带有新的SCG配置信息的RRC消息。
至此，UE可以获得的新的SCG配置信息，并基于新的SCG配置信息进行SCG配置，在配置完成后，UE便可以开始使用新的SCG配置信息与网络侧进行数据传输。
当然，SeNB也可以通过MeNB向UE下发新的SCG配置信息，上述过程仅为举例，MeNB从SeNB接收到新的SCG配置信息后会产生RRC连接重配置消息，其中，RRC连 接重配置消息包含了新的SCG配置信息，而在步骤810中，如果UE维持原MCG配置信息不变，那么，MeNB本次发送RRC连接重配置消息时，会继续使用上述MCG配置信息，且MeNB会将该RRC连接重配置消息通过主承载(例如，SRB1)发送给UE。
以上四个实施例均为UE确定SCG配置失败时，会向网络侧发送SCG重配置失败信息，UE和网络侧会在确定MCG配置成功时维持上一次下发的原SCG配置信息不变。
除上述处理方式之外，当UE确定SCG配置失败时，会向网络侧发送SCG重配置失败信息，UE和网络侧还可以在确定MCG配置成功时触发执行SCG释放时，此时，网络侧并不会发送或者下发新的SCG配置信息。
第五种场景：以MeNB下发SCG配置信息，且UE发生“SCG配置失败”的情况为例，当UE确定SCG配置失败时，会向网络侧发送SCG重配置失败信息，UE和网络侧在确定MCG配置成功时触发执行SCG释放。
参阅图9，第五种场景的具体流程如下：
步骤900：SeNB向MeNB发送SCG配置信息。
具体的，SeNB可以先获得UE状态信息，再基于UE状态信息设置相应的SCG配置信息，如，采用抽象语法表示法(ASN)进行编译，产生SCG配置信息的ASN.1，并将生成的SCG配置信息发送给MeNB。
步骤910：MeNB向UE下发MCG配置信息和SCG配置信息。
MeNB从SeNB接收到SCG配置信息，将该SCG配置信息结合本地设置的MCG配置信息产生RRC消息，并将此RRC消息通过主承载(例如，SRB1)发送给UE。
步骤920：UE确定SCG配置失败。
UE从MeNB发送的RRC消息中获得了MCG配置信息和SCG配置信息，由于该RRC消息同时包含了两条配置信息，按照默认的处理优先级，UE会先处理MCG配置信息，再处理SCG配置信息。此时，若MCG配置成功，而SCG配置失败，则UE采用配置成功的MCG配置信息，而确定SCG配置失败原因，并执行SCG释放。
具体的，SCG配置失败原因有四种，即概括描述的“SCG配置失败”，以及具体描述的“超过UE能力”、“解析错误”和“参数错误”。在本场景中，以“SCG配置失败”为SCG配置失败原因为例进行说明，因此，UE将SCG配置失败原因确定为概括描述的“SCG配置失败”。
步骤930：UE向MeNB发送SCG重配置失败信息，通知SCG配置失败原因。
UE确认SCG配置失败后，会以一条独立的RRC消息通过主承载(例如，SRB1)向MeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，概括描述的“SCG 重配置失败”。
步骤940：MeNB向SeNB发送SCG重配置失败信息，通知SCG重配置失败原因。
MeNB接收到UE发送的SCG重配置失败信息，并向SeNB发送SCG重配置失败信息，其中，包含了SCG配置失败原因，即，概括描述的“SCG重配置失败”。
步骤950：SeNB执行SCG释放。
SeNB收到MeNB发送的SCG重配置失败信息后，SeNB会根据失败原因“SCG重配置失败”，确定UE执行SCG配置失败后，执行SCG释放。
而在场景二、场景三、场景四中，当SeNB收到由MeNB发送的SCG重配置失败信息后，SeNB会根据失败原因，确定UE执行SCG配置失败后，执行SCG释放，而不会发送或下发新的SCG配置信息，与实施例五相同，因此不再赘述。
至此，上述五个实施例中，SeNB与MeNB之间的交互均是通过X2接口完成，但是，在新的应用系统中，SeNB与MeNB之间的交互并不只限定于X2接口，也可以通过X1或X3、……、Xn完成，因此不再赘述。
参阅图10所示，本申请实施例中，一种小区配置装置(如，第一基站)至少包括第一触发单元100、第二触发单元101、处理单元102，其中，
第一触发单元100，用于触发设置辅小区组SCG配置信息；
第二触发单元101，用于触发将所述SCG配置信息发往用户设备UE，并触发所述UE进行SCG配置；
处理单元102，用于接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
可选的，触发设置SCG配置信息时，所述第一触发单元100用于：
若所述装置是MeNB，则触发SeNB针对UE设置相应的SCG配置信息。
若所述装置是SeNB，则在本地直接触发针对UE设置相应的SCG配置信息。
可选的，触发将所述SCG配置信息发往UE进行SCG配置时，所述第二触发单元101用于：
若所述装置是MeNB，则采用第一消息，将本地设置的MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，采用第一消息，仅将SeNB设置的SCG配置信息发往UE；
若所述装置是SeNB，则采用第一消息，直接将本地设置的SCG配置信息发往UE。
可选的，接收到SCG重配置失败信息时，确定UE执行SCG配置失败时，所述处理 单元102用于：
若所述装置是MeNB，则直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
若所述装置是SeNB，则接收MeNB发送的SCG重配置失败信息时，确定UE执行SCG配置失败；其中，接收到的MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向所述装置发送的。
可选的，确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一次下发的原SCG配置信息不变时，所述处理单元102用于：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
可选的，确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放，所述处理单元102用于：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，执行SCG释放。
可选的，所述处理单元102进一步用于：
所述装置基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
可选的，基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息时，所述处理单元102用于：
若所述装置是MeNB，则将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往所述装置，再由所述装置发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG 配置信息以及将新的SCG配置信息发往UE；
若所述装置是SeNB，则接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，直接将所述新的SCG配置信息下发给UE。
可选的，基于所述SCG配置失败原因，触发重新设置新的SCG配置信息时，所述处理单元102用于：
触发SeNB执行以下操作中的任意一种：
若确定SCG配置失败原因为“SCG配置失败”，则按照预设方式重新设置新的SCG配置信息；
若确定SCG配置失败原因为“超过UE能力”，则与MeNB重新进行协商，并在对UE能力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
若确定SCG配置失败原因为“解析错误”或“参数错误”，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
参阅图11所示，本申请实施例中，一种小区配置装置(如，用户设备)至少包括配置单元110、通信单元111、处理单元112，其中，
配置单元110，用于根据网络侧下发的辅小区组SCG配置信息并进行SCG配置；
通信单元111，用于确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
处理单元112，用于确定在主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，确定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变时，或者，执行SCG释放，所述处理单元112用于：
若还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
若未接收到网络侧下发的MCG配置信息，则维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，向网络侧发送SCG重配置失败信息时，所述通信单元111用于：
确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败信息；
向网络侧发送所述SCG重配置失败信息，触发网络侧基于所述SCG配置失败原因，重新设置并下发新的SCG配置信息。
可选的，确定SCG配置失败原因时，所述通信单元111用于：
确定SCG配置失败原因为以下原因中的任意一种：
“SCG配置失败”；
“超过UE能力”；
“解析错误”；
“参数错误”。
参阅图12所示，本申请实施例中，一种小区配置装置(如，第一基站)包括处理器120、收发机121和存储器122，其中，
处理器120，用于读取存储器122中的程序，执行下列过程：
通过收发机121发送SCG配置信息，或接收SCG重配置失败信息；
触发设置辅小区组SCG配置信息；
触发将所述SCG配置信息发往用户设备UE，并由所述UE进行SCG配置；
接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
收发机121，用于在处理器120的控制下接收和发送数据。
可选的，触发设置SCG配置信息时，处理器120具体用于：
若所述装置是MeNB，则触发SeNB针对UE设置相应的SCG配置信息。
若所述装置是SeNB，则在本地直接触发针对UE设置相应的SCG配置信息。
可选的，触发将所述SCG配置信息发往UE进行SCG配置时，处理器120具体用于：
若所述装置是MeNB，则采用第一消息，将本地设置的MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，采用第一消息，仅将SeNB设置的SCG配置信息发往UE；
若所述装置是SeNB，则采用第一消息，直接将本地设置的SCG配置信息发往UE。
可选的，接收到SCG重配置失败信息时，确定UE执行SCG配置失败时，处理器120具体用于：
若所述装置是MeNB，则直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
若所述装置是SeNB，则接收MeNB发送的SCG重配置失败信息时，确定UE执行SCG配置失败；其中，接收到的MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向所述装置发送的。
可选的，确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一 次下发的原SCG配置信息不变时，处理器120具体用于：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
可选的，确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放，处理器120具体用于：
若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，执行SCG释放。
可选的，处理器120进一步具体用于：
基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
可选的，基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息时，处理器120具体用于：
若所述装置是MeNB，则将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往所述装置，再由所述装置发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往UE；
若所述装置是SeNB，则接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，直接将所述新的SCG配置信息下发给UE。
可选的，基于所述SCG配置失败原因，触发重新设置新的SCG配置信息时，处理器120具体用于：
触发SeNB执行以下操作中的任意一种：
若确定SCG配置失败原因为“SCG配置失败”，则按照预设方式重新设置新的SCG配置信息；
若确定SCG配置失败原因为“超过UE能力”，则与MeNB重新进行协商，并在对UE能力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
若确定SCG配置失败原因为“解析错误”或“参数错误”，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
其中，处理器120、收发机121和存储器122可通过总线连接。在图12中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器120代表的一个或多个处理器和存储器122代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机121可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器120负责管理总线架构和通常的处理，存储器122可以存储处理器120在执行操作时所使用的数据。
参阅图13所示，本申请实施例中，一种小区配置装置(如，用户设备)包括处理器130、收发机131、存储器132和用户接口133，其中，
处理器130，用于读取存储器132中的程序，执行下列过程：
通过收发机131发送SCG重配置失败信息，或接收SCG配置信息；
根据网络侧下发的辅小区组SCG配置信息并进行SCG配置；
确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
确定在主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放。
收发机131，用于在处理器130的控制下接收和发送数据。
可选的，确定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变时，或者，执行SCG释放，处理器130具体用于：
若还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
若未接收到网络侧下发的MCG配置信息，则维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
可选的，向网络侧发送SCG重配置失败信息时，处理器130具体用于：
确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败 信息；
向网络侧发送所述SCG重配置失败信息。
可选的，确定SCG配置失败原因时，处理器130具体用于：
确定SCG配置失败原因为以下原因中的任意一种：
“SCG配置失败”；
“超过UE能力”；
“解析错误”；
“参数错误”。
其中，处理器130、收发机131、存储器132和用户接口133可通过总线连接。在图13中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器130代表的一个或多个处理器和存储器132代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。收发机131可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口133还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器130负责管理总线架构和通常的处理，存储器132可以存储处理器130在执行操作时所使用的数据。
综上所述，本申请实施例中，在MeNB和SeNB联合应用的场景下，第一基站将SCG配置信息发送给UE进行SCG配置，当UE确定SCG配置失败时，会向网络侧发送SCG重配置失败信息，此时，UE和网络侧会在确定MCG配置成功时，维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放，即在仅有SCG配置失败的情况下，不会频繁发起RRC重建，而是使用原来的SCG配置信息，这样，有效避免了严重的数据中断，保证了用户设备的正常通信，从而提高了数据传输效率，保证了系统性能，也提高了用户体验。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图 和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (39)

  1. 一种小区配置方法，应用于主基站MeNB和辅基站SeNB联合工作的场景，其特征在于，包括：
    第一基站触发设置辅小区组SCG配置信息；
    第一基站触发将所述SCG配置信息发往用户设备UE，并触发所述UE进行SCG配置；
    第一基站接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
  2. 如权利要求1所述的方法，其特征在于，第一基站触发设置SCG配置信息，包括：
    若第一基站是MeNB，则第一基站触发SeNB针对UE设置相应的SCG配置信息。
    若第一基站是SeNB，则第一基站在本地直接触发针对UE设置相应的SCG配置信息。
  3. 如权利要求1所述的方法，其特征在于，第一基站触发将所述SCG配置信息发往UE，包括：
    若第一基站是MeNB，则第一基站采用第一消息，将本地设置的MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，第一基站采用第一消息，将SeNB设置的SCG配置信息发往UE；
    若第一基站是SeNB，则第一基站采用第一消息，直接将本地设置的SCG配置信息发往UE。
  4. 如权利要求1、2或3所述的方法，其特征在于，第一基站接收到SCG重配置失败信息时，确定UE执行SCG配置失败，包括：
    若第一基站是MeNB，则第一基站直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
    若第一基站是SeNB，则第一基站接收MeNB发送的SCG重配置失败信息时，确定UE执行SCG配置失败；其中，MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向第一基站发送的。
  5. 如权利要求4所述的方法，其特征在于，第一基站确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，包括：
    若第一基站为MeNB，则第一基站确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，第一基站确定UE执行SCG配置失败后， 维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
    若第一基站为SeNB，则第一基站确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
  6. 如权利要求4所述的方法，其特征在于，第一基站确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放，包括：
    若第一基站为MeNB，则第一基站确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，第一基站确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
    若第一基站为SeNB，则第一基站确定UE执行SCG配置失败，以及确定MCG配置成功后，执行SCG释放。
  7. 如权利要求1、2或3所述的方法，其特征在于，进一步包括：
    第一基站基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
  8. 如权利要求7所述的方法，其特征在于，第一基站基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息，包括：
    若第一基站是MeNB，则第一基站将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往第一基站，再由第一基站发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往UE；
    若第一基站是SeNB，则第一基站接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，第一基站直接将所述新的SCG配置信息下发给UE。
  9. 如权利要求8所述的方法，其特征在于，第一基站基于所述SCG配置失败原因，触发重新设置新的SCG配置信息，包括：
    第一基站触发SeNB执行以下操作中的任意一种：
    若确定SCG配置失败原因为SCG配置失败，则按照预设方式重新设置新的SCG配置信息；
    若确定SCG配置失败原因为超过UE能力，则与MeNB重新进行协商，并在对UE能 力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
    若确定SCG配置失败原因为解析错误或参数错误，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
  10. 一种小区配置方法，应用于主基站MeNB和辅基站SeNB联合工作的场景，其特征在于，包括：
    用户设备UE根据网络侧下发的辅小区组SCG配置信息进行SCG配置；
    UE确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
    UE确定主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放。
  11. 如权利要求10所述的方法，其特征在于，UE确定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放，包括：
    若UE还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则UE使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
    若UE未接收到网络侧下发的MCG配置信息，则UE维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
  12. 如权利要求10或11所述的方法，其特征在于，UE向网络侧发送SCG重配置失败信息之前，还包括：
    UE确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败信息。
  13. 如权利要求12所述的方法，其特征在于，UE确定的SCG配置失败原因包括以下原因中的任意一种：
    SCG配置失败；
    超过UE能力；
    解析错误；
    参数错误。
  14. 一种小区配置装置，应用于主基站MeNB和辅基站SeNB联合工作的场景，其特征在于，包括：
    第一触发单元，用于触发设置辅小区组SCG配置信息；
    第二触发单元，用于触发将所述SCG配置信息发往用户设备UE，并触发所述UE进行SCG配置；
    处理单元，用于接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
  15. 如权利要求14所述的装置，其特征在于，所述第一触发单元用于采用如下方式触发设置SCG配置信息：
    若所述装置是MeNB，则触发SeNB针对UE设置相应的SCG配置信息。
    若所述装置是SeNB，则在本地直接触发针对UE设置相应的SCG配置信息。
  16. 如权利要求14所述的装置，其特征在于，所述第二触发单元用于采用如下方式触发将所述SCG配置信息发往UE：
    若所述装置是MeNB，则采用第一消息，将本地设置的主小区组MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，采用第一消息，将SeNB设置的SCG配置信息发往UE；
    若所述装置是SeNB，则采用第一消息，直接将本地设置的SCG配置信息发往UE。
  17. 如权利要求14、15或16所述的装置，其特征在于，所述处理单元用于采用如下方式，在接收到SCG重配置失败信息时，确定UE执行SCG配置失败：
    若所述装置是MeNB，则直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
    若所述装置是SeNB，则接收MeNB发送的SCG重配置失败信息时，确定UE执行SCG配置失败；其中，MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向所述装置发送的。
  18. 如权利要求17所述的装置，其特征在于，所述处理单元用于采用如下方式确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一次下发的原SCG配置信息不变：
    若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
    若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
  19. 如权利要求17所述的装置，其特征在于，所述处理单元用于采用如下方式，确 定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放：
    若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
    若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，执行SCG释放。
  20. 如权利要求15、16或17所述的装置，其特征在于，所述处理单元进一步用于：
    基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
  21. 如权利要求20所述的装置，其特征在于，所述处理单元用于采用如下方式基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息：
    若所述装置是MeNB，则将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往所述装置，再由所述装置发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往UE；
    若所述装置是SeNB，则接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，直接将所述新的SCG配置信息下发给UE。
  22. 如权利要求21所述的装置，其特征在于，基于所述SCG配置失败原因，触发重新设置新的SCG配置信息时，所述处理单元用于触发SeNB执行以下操作中的任意一种：
    若确定SCG配置失败原因为SCG配置失败，则按照预设方式重新设置新的SCG配置信息；
    若确定SCG配置失败原因为超过UE能力，则与MeNB重新进行协商，并在对UE能力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
    若确定SCG配置失败原因为解析错误或参数错误，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
  23. 一种小区配置装置，应用于主基站MeNB和辅基站SeNB联合工作的场景，其特征在于，包括：
    配置单元，用于根据网络侧下发的辅小区组SCG配置信息并进行SCG配置；
    通信单元，用于确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
    处理单元，用于确定在主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放。
  24. 如权利要求23所述的装置，其特征在于，所述处理单元用于采用如下方式，在确定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变时，或者，执行SCG释放：
    若还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
    若未接收到网络侧下发的MCG配置信息，则维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
  25. 如权利要求23或24所述的装置，其特征在于，所述通信单元用于采用如下方式向网络侧发送SCG重配置失败信息：
    确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败信息，向网络侧发送所述SCG重配置失败信息。
  26. 如权利要求25所述的装置，其特征在于，确定SCG配置失败原因时，所述通信单元用于确定SCG配置失败原因为以下原因中的任意一种：
    SCG配置失败；
    超过UE能力；
    解析错误；
    参数错误。
  27. 一种小区配置装置，其特征在于，包括处理器、收发机和存储器，其中，
    所述处理器，用于读取所述存储器中的程序，执行下列过程：
    通过所述收发机发送SCG配置信息，或接收SCG重配置失败信息；
    触发设置辅小区组SCG配置信息；
    触发将所述SCG配置信息发往用户设备UE进行SCG配置；
    接收到SCG重配置失败信息时，确定UE执行SCG配置失败，并且在确定主小区组MCG配置成功时，触发维持上一次下发的原SCG配置信息不变，或者，触发执行SCG释放。
    所述收发机，用于在处理器的控制下接收和发送数据。
  28. 如权利要27所述的装置，其特征在于，所述处理器用于采用如下方式触发设置SCG配置信息：
    若所述装置是MeNB，则触发SeNB针对UE设置相应的SCG配置信息。
    若所述装置是SeNB，则在本地直接触发针对UE设置相应的SCG配置信息。
  29. 如权利要求27所述的装置，其特征在于，所述处理器用于采用如下方式触发将所述SCG配置信息发往UE：
    若所述装置是MeNB，则采用第一消息，将本地设置的主小区组MCG配置信息和SeNB设置的SCG配置信息发往UE；或者，采用第一消息，将SeNB设置的SCG配置信息发往UE；
    若所述装置是SeNB，则采用第一消息，直接将本地设置的SCG配置信息发往UE。
  30. 如权利要求27、28或29所述的装置，其特征在于，所述处理器用于采用如下方式，在接收到SCG重配置失败信息时，确定UE执行SCG配置失败：
    若所述装置是MeNB，则直接接收到UE发送的SCG重配置失败信息时，确定UE执行SCG配置失败；
    若所述装置是SeNB，则接收MeNB发送的SCG重配置失败信息时，确定UE执行SCG配置失败；其中，MeNB发送的SCG重配置失败信息，是MeNB接收到UE发送的SCG重配置失败信息后，向所述装置发送的。
  31. 如权利要求30所述的装置，其特征在于，所述处理器用于采用如下方式确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发维持上一次下发的原SCG配置信息不变：
    若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB维持上一次下发的原SCG配置信息不变；或者，
    若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后，维持上一次下发的原SCG配置信息不变。
  32. 如权利要求30所述的装置，其特征在于，所述处理器用于采用如下方式，确定UE执行SCG配置失败，并且在确定MCG配置成功时，触发执行SCG释放：
    若所述装置为MeNB，则确定UE执行SCG配置失败后，若确定MCG配置成功，则使用配置成功的MCG配置信息，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，确定UE执行SCG配置失败后，维持原MCG配置信息不变，并向SeNB发送SCG重配置失败信息，触发SeNB执行SCG释放；或者，
    若所述装置为SeNB，则确定UE执行SCG配置失败，以及确定MCG配置成功后， 执行SCG释放。
  33. 如权利要求28、29或30所述的装置，其特征在于，所述处理器进一步用于：
    基于接收到的SCG重配置失败信息获取相应的SCG配置失败原因，并基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息。
  34. 如权利要求33所述的装置，其特征在于，所述处理器用于采用如下方式基于所述SCG配置失败原因，触发重新设置以及重新下发相应的新的SCG配置信息：
    若所述装置是MeNB，则将SCG配置失败原因发送给SeNB，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往所述装置，再由所述装置发往UE，或者，触发SeNB基于所述SCG配置失败原因，重新设置新的SCG配置信息以及将新的SCG配置信息发往UE；
    若所述装置是SeNB，则接收MeNB发送的SCG配置失败原因后，直接触发基于所述SCG配置失败原因在本地重新设置新的SCG配置信息，并将新的SCG配置信息发往MeNB，由MeNB下发给UE，或者，直接将所述新的SCG配置信息下发给UE。
  35. 如权利要求34所述的装置，其特征在于，基于所述SCG配置失败原因，触发重新设置新的SCG配置信息时，所述处理器用于触发SeNB执行以下操作中的任意一种：
    若确定SCG配置失败原因为SCG配置失败，则按照预设方式重新设置新的SCG配置信息；
    若确定SCG配置失败原因为超过UE能力，则与MeNB重新进行协商，并在对UE能力进行重新评估后，根据评估结果，重新设置新的SCG配置信息；
    若确定SCG配置失败原因为解析错误或参数错误，则对配置失败的SCG配置信息进行相应调整后，根据调整结果重新设置新的SCG配置信息。
  36. 一种小区配置装置，其特征在于，包括处理器、收发机、存储器和用户接口，其中，
    所述处理器，用于读取所述存储器中的程序，执行下列过程：
    通过所述收发机发送SCG重配置失败信息，或接收SCG配置信息；
    根据网络侧下发的辅小区组SCG配置信息并进行SCG配置；
    确定执行SCG配置失败时，向网络侧发送SCG重配置失败信息；
    确定在主小区组MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变，或者，执行SCG释放；
    所述收发机，用于在所述处理器的控制下接收和发送数据。
  37. 如权利要求36所述的装置，其特征在于，所述处理器用于采用如下方式，在确 定MCG配置成功时，维持网络侧上一次下发的原SCG配置信息不变时，或者，执行SCG释放：
    若还接收到网络侧下发的MCG配置信息，且确定MCG配置成功，则使用配置成功的MCG配置信息，并维护上一次下发的原SCG配置信息不变，或者，执行SCG释放；
    若未接收到网络侧下发的MCG配置信息，则维护上一次下发的原MCG配置信息不变，以及维护上一次下发的原SCG配置信息不变，或者，执行SCG释放。
  38. 如权利要求36或37所述的装置，其特征在于，所述处理器用于采用如下方式通过所述收发机向网络侧发送SCG重配置失败信息：
    确定SCG配置失败原因，并基于所述SCG配置失败原因生成相应的SCG重配置失败信息，通过所述收发机向网络侧发送所述SCG重配置失败信息。
  39. 如权利要求38所述的装置，其特征在于，确定SCG配置失败原因时，所述处理器用于确定SCG配置失败原因为以下原因中的任意一种：
    SCG配置失败；
    超过UE能力；
    解析错误；
    参数错误。
PCT/CN2017/094108 2016-08-05 2017-07-24 一种小区配置方法及装置 WO2018024128A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020197006344A KR102180383B1 (ko) 2016-08-05 2017-07-24 셀 구성 방법 및 장치
EP17836310.7A EP3496448A1 (en) 2016-08-05 2017-07-24 Cell configuration method and device
JP2019506437A JP2019525625A (ja) 2016-08-05 2017-07-24 セル構成の方法及び装置
US16/323,229 US20190182883A1 (en) 2016-08-05 2017-07-24 Cell configuration method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610635900.2 2016-08-05
CN201610635900.2A CN107690154B (zh) 2016-08-05 2016-08-05 一种小区配置方法及装置

Publications (1)

Publication Number Publication Date
WO2018024128A1 true WO2018024128A1 (zh) 2018-02-08

Family

ID=61072569

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/094108 WO2018024128A1 (zh) 2016-08-05 2017-07-24 一种小区配置方法及装置

Country Status (6)

Country Link
US (1) US20190182883A1 (zh)
EP (1) EP3496448A1 (zh)
JP (1) JP2019525625A (zh)
KR (1) KR102180383B1 (zh)
CN (1) CN107690154B (zh)
WO (1) WO2018024128A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020063453A1 (zh) * 2018-09-26 2020-04-02 维沃移动通信有限公司 一种用户设备能力确定方法及节点
JP2022520957A (ja) * 2019-02-14 2022-04-04 エルジー エレクトロニクス インコーポレイティド Ｍｃｇ失敗報告後の膠着状態からの復旧

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180124831A1 (en) * 2016-10-29 2018-05-03 Ofinno Technologies, Llc Dual connectivity scheduling request for wireless network and wireless device
CN109246839B (zh) * 2017-05-05 2023-11-28 华为技术有限公司 一种失败处理方法、切换方法及终端设备、网络设备
EP3659388A4 (en) * 2017-07-27 2021-04-21 FG Innovation Company Limited METHOD AND RELATED DEVICE FOR ADDING SECONDARY NODES
US10785817B2 (en) 2017-09-28 2020-09-22 Apple Inc. Signaling radio bearer type 3 (SRB3) and secondary cell group (SCG) failure handling
WO2019090489A1 (zh) * 2017-11-07 2019-05-16 Oppo广东移动通信有限公司 配置无线资源的方法、终端设备和网络设备
ES2929046T3 (es) * 2017-11-23 2022-11-24 Beijing Xiaomi Mobile Software Co Ltd Método y aparato de configuración de transmisión
CN110167123B (zh) * 2018-02-14 2021-06-15 华为技术有限公司 一种功率控制方法及装置
CN110278587B (zh) * 2018-03-16 2022-08-12 维沃移动通信有限公司 小区配置方法、终端和网络节点
WO2019223767A1 (zh) * 2018-05-25 2019-11-28 华为技术有限公司 一种数据传输方法及装置
CN110536487B (zh) * 2018-05-25 2021-12-10 华为技术有限公司 一种数据传输方法及装置
US11950307B2 (en) 2018-10-26 2024-04-02 Google Llc Efficient handling of a resource control state change and multi-node connectivity
WO2020103047A1 (zh) * 2018-11-21 2020-05-28 华为技术有限公司 一种数据传输方法和装置
WO2020150991A1 (en) * 2019-01-25 2020-07-30 Qualcomm Incorporated Blind secondary cell group configuration in multi-radio access technology-dual connectivity
WO2020150998A1 (en) * 2019-01-25 2020-07-30 Zte Corporation Method and apparatus for reporting master cell group failure
CN113330800B (zh) 2019-01-25 2024-05-14 高通股份有限公司 多无线电接入技术-双连通性和载波聚集中的副蜂窝小区群配置
CN111526536B (zh) * 2019-02-01 2022-08-09 大唐移动通信设备有限公司 信息上报方法、装置、终端及网络侧设备
WO2020166819A1 (en) * 2019-02-14 2020-08-20 Lg Electronics Inc. Fast cell setup for dual connectivity
WO2020227870A1 (zh) 2019-05-10 2020-11-19 Oppo广东移动通信有限公司 一种切换方法及装置、通信设备
CN112087785B (zh) * 2019-06-13 2023-12-12 夏普株式会社 无线链路失败恢复方法以及用户设备
CN118714619A (zh) * 2019-09-30 2024-09-27 华为技术有限公司 通信方法和通信装置
CN114631395A (zh) * 2019-11-08 2022-06-14 华为技术有限公司 通信方法和通信装置
WO2021195911A1 (en) * 2020-03-31 2021-10-07 Qualcomm Incorporated Connecting to multi-radio access technology service in non-standalone mode
WO2021212416A1 (en) * 2020-04-23 2021-10-28 Qualcomm Incorporated Recovery from repeated network configuration failure
US11917464B2 (en) * 2020-06-05 2024-02-27 Apple Inc. 5G NR efficient FR1/FR2 operation
US20220053397A1 (en) * 2020-08-12 2022-02-17 Industrial Technology Research Institute Method for handling secondary cell group failure and user equipment using the same
CN112188517A (zh) * 2020-09-07 2021-01-05 Oppo（重庆）智能科技有限公司 小区驻留方法、装置、终端及存储介质
CN113556758B (zh) * 2020-09-27 2022-11-18 华为技术有限公司 配置辅小区组的方法和装置
CN112367716B (zh) * 2020-10-30 2023-03-31 Oppo广东移动通信有限公司 无线通信方法、终端设备和网络设备
WO2022133902A1 (zh) * 2020-12-24 2022-06-30 华为技术有限公司 一种配置辅小区组的方法及装置
CN112672373B (zh) * 2020-12-31 2023-05-30 上海微波技术研究所（中国电子科技集团公司第五十研究所） Nr-dc中从节点小区配置的优化方法、系统及介质
WO2024011435A1 (zh) * 2022-07-12 2024-01-18 北京小米移动软件有限公司 一种失败处理方法及其装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219787A (zh) * 2014-09-10 2014-12-17 电信科学技术研究院 一种恢复无线链路的方法和设备
US20150215965A1 (en) * 2014-01-30 2015-07-30 Sharp Laboratories Of America, Inc. Systems and methods for dual-connectivity operation
WO2015140038A1 (en) * 2014-03-21 2015-09-24 Alcatel Lucent Dual connectivity network

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015115034A1 (en) * 2014-01-30 2015-08-06 Sharp Kabushiki Kaisha Systems and methods for dual-connectivity operation
GB2528913B (en) * 2014-08-04 2017-03-01 Samsung Electronics Co Ltd Signalling in dual connectivity mobile communication networks
EP4221055A1 (en) * 2014-08-06 2023-08-02 Mitsubishi Electric Corporation Mobile communication system, user equipment and base station
JP6353158B2 (ja) * 2014-08-08 2018-07-04 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおける二重連結のためのサービス解除を通報する方法及び装置
US9854568B2 (en) * 2014-10-03 2017-12-26 Qualcomm Incorporated Techniques for transmitting a control channel and a data channel over multiple component carriers
US10848977B2 (en) * 2016-11-02 2020-11-24 Comcast Cable Communications, Llc Dual connectivity with licensed assisted access
EP3585129B1 (en) * 2017-03-27 2022-05-04 LG Electronics Inc. Method and device for transmitting scg failure information message in wireless communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150215965A1 (en) * 2014-01-30 2015-07-30 Sharp Laboratories Of America, Inc. Systems and methods for dual-connectivity operation
WO2015140038A1 (en) * 2014-03-21 2015-09-24 Alcatel Lucent Dual connectivity network
CN104219787A (zh) * 2014-09-10 2014-12-17 电信科学技术研究院 一种恢复无线链路的方法和设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Discussion on S-RLF in Dual Connectivity", 3GPP TSG-RAN2 MEETING #87, R2-143409, 22 August 2014 (2014-08-22), XP050794436 *
CATT: "RRC Reconfiguration Failure", 3GPP TSG RAN WG2 MEETING #85BIS, R2-141570, 4 April 2014 (2014-04-04), XP050792723 *
See also references of EP3496448A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020063453A1 (zh) * 2018-09-26 2020-04-02 维沃移动通信有限公司 一种用户设备能力确定方法及节点
JP2022520957A (ja) * 2019-02-14 2022-04-04 エルジー エレクトロニクス インコーポレイティド Ｍｃｇ失敗報告後の膠着状態からの復旧
JP7270752B2 (ja) 2019-02-14 2023-05-10 エルジー エレクトロニクス インコーポレイティド Ｍｃｇ失敗報告後の膠着状態からの復旧
JP7508641B2 (ja) 2019-02-14 2024-07-01 エルジー エレクトロニクス インコーポレイティド Ｍｃｇ失敗報告後の膠着状態からの復旧
US12069759B2 (en) 2019-02-14 2024-08-20 Lg Electronics Inc. Recovery from deadlock after MCG failure report

Also Published As

Publication number Publication date
US20190182883A1 (en) 2019-06-13
JP2019525625A (ja) 2019-09-05
CN107690154A (zh) 2018-02-13
KR102180383B1 (ko) 2020-11-18
KR20190036555A (ko) 2019-04-04
EP3496448A4 (en) 2019-06-12
EP3496448A1 (en) 2019-06-12
CN107690154B (zh) 2019-09-17

Similar Documents

Publication Publication Date Title
WO2018024128A1 (zh) 一种小区配置方法及装置
US11950314B2 (en) Configuration method and apparatus, and system
JP6995995B2 (ja) 多重接続のための方法およびその装置
EP3562182B1 (en) Communication path switching method
US10582381B2 (en) Implementing radio access network slicing in a mobile network
CN109151915B (zh) 用于数据分组递送的方法、用户设备和基站
WO2018228126A1 (zh) 一种基于dc的切换方法及设备
US11622406B2 (en) Dual connectivity method and access network device
WO2018127219A1 (zh) 一种减少中断时延的方法、装置及用户设备
CN118714619A (zh) 通信方法和通信装置
EP4236424A1 (en) Data transmission control method, apparatus, and storage medium
WO2014023269A1 (zh) 一种切换控制方法及装置
WO2017079942A1 (zh) 对正在进行语音业务的终端进行处理的方法及装置、以及通信系统
US10779344B2 (en) Telecommunications method, telecommunications system, primary node, secondary node and user equipment
WO2022028297A1 (zh) 辅小区组的主小区更新方法、装置及存储介质
WO2022073431A1 (zh) 数据处理方法、设备、装置和存储介质
US10708891B2 (en) Method for establishing evolved packet system bearer and base station
US11381979B2 (en) Standalone unlicensed spectrum carrier aggregation combinations using dynamic frequency selection (DFS) spectrum
WO2020063441A1 (zh) 重复传输方法、终端和网络侧设备
US20240172084A1 (en) Data transmission method and apparatus
WO2019158117A1 (en) System and method for providing security in a wireless communications system with user plane separation
JP2023545849A (ja) Ｉａｂノードのマイグレーション方法及び装置
WO2016101617A1 (zh) 一种切换流程中安全信息的处理方法、接入网关及基站
CN114390622A (zh) 一种信息传输方法、装置及通信设备
WO2023221838A1 (zh) 交互方法和相关设备

Legal Events

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

Ref document number: 17836310

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019506437

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197006344

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017836310

Country of ref document: EP

Effective date: 20190305