WO2015062476A1 - 演进型基站的重配置方法、用户设备及演进型基站 - Google Patents

演进型基站的重配置方法、用户设备及演进型基站 Download PDF

Info

Publication number
WO2015062476A1
WO2015062476A1 PCT/CN2014/089687 CN2014089687W WO2015062476A1 WO 2015062476 A1 WO2015062476 A1 WO 2015062476A1 CN 2014089687 W CN2014089687 W CN 2014089687W WO 2015062476 A1 WO2015062476 A1 WO 2015062476A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrc reconfiguration
senb
menb
message
rrc
Prior art date
Application number
PCT/CN2014/089687
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 US15/033,345 priority Critical patent/US20160269241A1/en
Priority to EP14858578.9A priority patent/EP3065444B1/en
Publication of WO2015062476A1 publication Critical patent/WO2015062476A1/zh

Links

Images

Classifications

    • 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/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0846—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on copy from other elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/29—Control channels or signalling for resource management between an access point and the access point controlling device
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present application relates to the field of network communication device technologies, and in particular, to a method for reconfiguring an evolved base station, a user equipment, and an evolved base station.
  • the prior art proposes a network architecture for implementing cooperation/aggregation between multiple eNBs (evolved Node Bs) through non-ideal links.
  • eNBs evolved Node Bs
  • a part of the RB (Radio Bearer) of the UE (User Equipment) is on the MCell (Master Cell) managed by the MeNB (Master eNB).
  • the control plane SRB (Signaling Radio Bearer) and the user plane DRB (Data Radio Bearer) are included.
  • the other part of the same UE is on the SCell (Secondary Cell) cell managed by the SeNB (Secondary eNB).
  • bearer separation can be implemented by carrying a splitting manner.
  • the SeNB In the case of bearer offloading, in order to complete the radio parameter configuration for the SeNB, the SeNB needs to transmit the RRC (Radio Resource Control) reconfiguration parameter generated by the SeNB to the MeNB, and then forward it to the UE. Then, the RRC reconfiguration message sent by the MeNB to the UE includes not only the RRC reconfiguration parameter of the MeNB but also the RRC reconfiguration parameter of the SeNB, that is, the so-called RRC parameter parallel configuration.
  • RRC Radio Resource Control
  • An object of the present application is to provide a method for reconfiguring an evolved base station, a user equipment, and an evolved base station, to solve the problem of how to handle RRC parameter parallel configuration for the SeNB.
  • a method for reconfiguring an evolved base station comprising:
  • the user equipment receives the radio resource control RRC reconfiguration message sent by the primary evolved base station MeNB, where the RRC reconfiguration message carries the RRC reconfiguration parameter from the evolved base station SeNB and the RRC reconfiguration parameter of the MeNB;
  • the user equipment does not feed back a message to the MeNB, or returns an RRC reconfiguration result information of the SeNB to the MeNB.
  • the user equipment feeds back an RRC reconfiguration success message to the MeNB, where the RRC reconfiguration success message carries the RRC reconfiguration result information of the SeNB;
  • the user equipment initiates RRC reestablishment to the MeNB.
  • the RRC reconfiguration message received by the user equipment includes both the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration result for the MeNB
  • the RRC reconfiguration result of the SeNB is fed back in different manners, so that the network side knows the RRC reconfiguration result of the SeNB, and solves the problem of how the RRC parameter parallel configuration of the SeNB is handled.
  • the RRC reconfiguration result information of the SeNB is information that the RRC reconfiguration of the SeNB is successful, if the RRC reconfiguration of the SeNB is completed according to the RRC reconfiguration parameter of the SeNB. If an abnormality occurs in the RRC reconfiguration according to the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality.
  • the information of the RRC reconfiguration result carrying the SeNB is not fed back to the MeNB.
  • a method for reconfiguring an evolved base station comprising:
  • the MeNB receives an RRC reconfiguration message sent by the SeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter of the SeNB;
  • the MeNB sends the RRC reconfiguration message sent by the SeNB to the user equipment in the RRC reconfiguration message of the MeNB, where the RRC reconfiguration message of the MeNB further includes an RRC reconfiguration parameter of the MeNB.
  • the MeNB receives the RRC reconfiguration result information of the SeNB returned by the user equipment, the RRC reconfiguration result is fed back to the SeNB according to the RRC reconfiguration result information of the SeNB.
  • the MeNB transparently transmits the RRC reconfiguration message of the SeNB to the user equipment, and performs feedback to the SeNB according to the RRC reconfiguration result of the SeNB returned by the user equipment, so that the network side learns the SeNB.
  • the RRC reconfiguration result solves the problem of how the SeNB's RRC parameter parallel configuration is handled.
  • the RRC reconfiguration result is fed back to the SeNB according to the RRC reconfiguration result information of the SeNB, including:
  • the MeNB feeds back to the SeNB a message that the RRC reconfiguration succeeds;
  • the MeNB If the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality, the MeNB returns a message that the RRC reconfiguration is abnormal to the SeNB.
  • the RRC reconfiguration result is not fed back to the SeNB. If the RRC reconfiguration result information of the SeNB is not received, the RRC reconfiguration result is not fed back to the SeNB.
  • a method for reconfiguring an evolved base station comprising:
  • the MeNB When the MeNB receives the RRC reconfiguration message of the SeNB, parsing the RRC reconfiguration message of the SeNB;
  • the MeNB forwards the RRC reconfiguration message of the SeNB to the user equipment, and feeds back the RRC reconfiguration to the SeNB after determining that the RRC reconfiguration for the SeNB is successful. Successful news;
  • the MeNB sends a message to the SeNB that the RRC reconfiguration is abnormal.
  • the MeNB in the case of the bearer offloading, the MeNB first parses the RRC reconfiguration parameter of the SeNB, and sends a message of successfully configuring or reestablishing the RRC reconfiguration parameter to the SeNB according to different conditions of the parsed reconfiguration message.
  • the MeNB is enabled to effectively handle the RRC reconfiguration parameter parallel configuration problem of the UE for the SeNB.
  • the MeNB Based on the embodiment of the reconfiguration method of the evolved base station, preferably, if the RRC reconfiguration message of the SeNB is parsed, the MeNB does not perform any processing or sends an RRC reconfiguration message of the SeNB to the SeNB. Notification message.
  • a method for reconfiguring an evolved base station comprising:
  • the MeNB receives the RRC reconfiguration message of the SeNB, where the RRC reconfiguration message of the SeNB carries the first RRC transaction identifier and the RRC reconfiguration parameter of the SeNB;
  • the MeNB generates an RRC reconfiguration message of the MeNB and sends the RRC reconfiguration message to the user equipment, where the RRC reconfiguration message of the MeNB carries the second RRC transaction identifier and the RRC reconfiguration parameter of the SeNB.
  • the MeNB saves a correspondence between the first RRC transaction identifier and the second RRC transaction identifier
  • the MeNB receives the RRC reconfiguration response message returned by the user equipment, where the RRC reconfiguration response message includes a second RRC transaction identifier and RRC reconfiguration result information;
  • the eNB sends an RRC reconfiguration response message to the SeNB, and sends an RRC reconfiguration response message to the SeNB.
  • the foregoing includes the foregoing first RRC transaction identifier and the foregoing RRC reconfiguration result information.
  • the MeNB after receiving the RRC reconfiguration message of the SeNB, the MeNB constructs an RRC reconfiguration message of the MeNB, where the RRC reconfiguration parameter in the RRC reconfiguration message of the SeNB is saved. Correspondence of RRC transaction identifiers in messages. In this manner, the user equipment side processes only the received RRC reconfiguration message, and does not recognize whether it is the RRC reconfiguration of the MeNB or the RRC reconfiguration of the SeNB. The MeNB identifies the RRC feedback response for the SeNB according to the corresponding relationship of the saved RRC transaction identifier and feeds back to the SeNB, and solves the problem of how to handle the RRC reconfiguration parameter parallel configuration for the SeNB.
  • the embodiment of the present application further provides a user equipment, including:
  • the RRC reconfiguration information receiving module is configured to receive a radio resource control RRC reconfiguration message sent by the primary evolved base station MeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter from the evolved base station SeNB and an RRC reconfiguration parameter of the MeNB;
  • the RRC reconfiguration result processing module if the RRC reconfiguration parameter of the MeNB is negligible, the RRC reconfiguration result processing module is configured to not feed back the message to the MeNB, or return the RRC reconfiguration result information of the SeNB to the MeNB;
  • the RRC reconfiguration result processing module is configured to: feed back an RRC reconfiguration success message to the MeNB, where the RRC reconfiguration success message carries the RRC reconfiguration result information of the SeNB;
  • the RRC reconfiguration result processing module is configured to initiate RRC reestablishment to the MeNB.
  • the user equipment provided by the embodiment of the present application in the case of the bearer offloading, if the RRC reconfiguration message received by the user equipment includes both the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration for the MeNB As a result, the RRC reconfiguration result of the SeNB is used to feedback the RRC reconfiguration result of the SeNB in different manners, so that the network side knows the RRC reconfiguration result of the SeNB, and solves the problem of how the RRC parameter parallel configuration of the SeNB is handled.
  • the RRC reconfiguration result information of the SeNB is information that the RRC reconfiguration of the SeNB is successful.
  • the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality.
  • the RRC reconfiguration result processing module is further configured to not feed back information of the RRC reconfiguration result of the SeNB to the MeNB.
  • the embodiment of the present application further provides another user equipment, including a processor.
  • the processor is configured to receive a radio resource control RRC reconfiguration message sent by the primary evolved base station MeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter from the evolved base station SeNB and an RRC reconfiguration parameter of the MeNB; if the MeNB The RRC reconfiguration parameter is negligible, does not feed back the message to the MeNB, or returns the RRC reconfiguration result information of the SeNB to the MeNB; if the RRC reconfiguration of the MeNB is completed according to the RRC reconfiguration parameter of the MeNB, the RRC reconfiguration success message is fed back to the MeNB, The RRC reconfiguration success message carries the RRC reconfiguration result information of the SeNB; if an abnormality occurs when the RRC reconfiguration of the MeNB is performed according to the RRC reconfiguration parameter of the MeNB, the RRC reestablishment is initiated to the MeNB.
  • the user equipment provided by the embodiment of the present application in the case of the bearer offloading, if the RRC reconfiguration message received by the user equipment includes both the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration for the MeNB As a result, the RRC reconfiguration result of the SeNB is used to feedback the RRC reconfiguration result of the SeNB in different manners, so that the network side knows the RRC reconfiguration result of the SeNB, and solves the problem of how the RRC parameter parallel configuration of the SeNB is handled.
  • an evolved base station including:
  • An RRC reconfiguration message receiving module configured to receive an RRC reconfiguration message sent by the SeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter of the SeNB;
  • the RRC reconfiguration message sending module is configured to: send the RRC reconfiguration message sent by the SeNB to the user equipment in an RRC reconfiguration message of the MeNB, where the RRC reconfiguration message of the MeNB further includes an RRC reconfiguration parameter of the MeNB;
  • the RRC reconfiguration result feedback module is configured to: when receiving the RRC reconfiguration result information of the SeNB returned by the user equipment, feed back an RRC reconfiguration result to the SeNB according to the RRC reconfiguration result information of the SeNB.
  • the MeNB transmits the RRC reconfiguration message of the SeNB to the user equipment, and feeds back to the SeNB according to the RRC reconfiguration result of the SeNB returned by the user equipment, so that the network side learns the SeNB.
  • the RRC reconfiguration result solves the problem of how the SeNB's RRC parameter parallel configuration is handled.
  • the RRC reconfiguration result feedback module is specifically configured to:
  • the SeNB feeds back a message that the RRC reconfiguration succeeds;
  • the SeNB If the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality, the SeNB returns a message that the RRC reconfiguration is abnormal.
  • the RRC reconfiguration result feedback module is further configured to not feed back the RRC reconfiguration result to the SeNB if the RRC reconfiguration result information of the SeNB is not received.
  • the embodiment of the present application further provides an evolved base station, including a processor, where the processor is configured to receive an RRC reconfiguration message sent by the SeNB, where the RRC reconfiguration message carries the RRC weight of the SeNB.
  • the RRC reconfiguration message sent by the SeNB is sent to the user equipment in the RRC reconfiguration message of the MeNB, where the RRC reconfiguration message of the MeNB further includes the RRC reconfiguration parameter of the MeNB;
  • the RRC reconfiguration result information of the SeNB feeds back the RRC reconfiguration result to the SeNB according to the RRC reconfiguration result information of the SeNB.
  • the MeNB transmits the RRC reconfiguration message of the SeNB to the user equipment, and feeds back to the SeNB according to the RRC reconfiguration result of the SeNB returned by the user equipment, so that the network side learns the SeNB.
  • the RRC reconfiguration result solves the problem of how the SeNB's RRC parameter parallel configuration is handled.
  • an evolved base station including:
  • An RRC reconfiguration message parsing module configured to parse an RRC reconfiguration message of the SeNB when receiving an RRC reconfiguration message of the SeNB;
  • the RRC reconfiguration result feedback module is configured to: if the parameter configuration in the RRC reconfiguration message of the SeNB is parsed, the RRC reconfiguration message of the SeNB is forwarded to the user equipment, and after determining that the RRC reconfiguration for the SeNB is successful, The SeNB feeds back a message that the RRC reconfiguration succeeds. If the parameter configuration in the RRC reconfiguration message of the SeNB is unacceptable, the SeNB sends a message that the RRC reconfiguration is abnormal.
  • the MeNB in the case of the bearer offloading, the MeNB first parses the RRC reconfiguration parameter of the SeNB, and sends a message of successfully configuring or reestablishing the RRC reconfiguration parameter to the SeNB according to different conditions of the parsed reconfiguration message.
  • the MeNB is enabled to effectively handle the RRC reconfiguration parameter parallel configuration problem of the UE for the SeNB.
  • the RRC reconfiguration result feedback module is further configured to: if the RRC reconfiguration message of the SeNB is parsed is negligible, perform no processing or send a notification message that the SeNB's RRC reconfiguration message is negligible to the SeNB.
  • the embodiment of the present application further provides an evolved base station, including a processor.
  • the processor is configured to: when receiving the RRC reconfiguration message of the SeNB, parse the RRC reconfiguration message of the SeNB; if it is determined that the parameter configuration in the RRC reconfiguration message of the SeNB is acceptable, forwarding the SeNB to the user equipment RRC reconfiguration message, and after receiving the RRC reconfiguration success for the SeNB, the RRC reconfiguration success message is fed back to the SeNB; if the parameter configuration in the RRC reconfiguration message of the SeNB is unacceptable, the RRC reconfiguration is sent to the SeNB. An abnormal message occurred.
  • the MeNB in the case of the bearer offloading, the MeNB first parses the RRC reconfiguration parameter of the SeNB, and sends a configuration success or reestablishing the RRC to the SeNB according to different conditions of the parsed reconfiguration message.
  • the message of the reconfiguration parameter enables the MeNB to effectively handle the RRC reconfiguration parameter parallel configuration problem of the UE for the SeNB.
  • an evolved base station including:
  • the RRC reconfiguration message receiving module is configured to receive an RRC reconfiguration message of the SeNB, where the RRC reconfiguration message of the SeNB carries the first RRC transaction identifier and the RRC reconfiguration parameter of the SeNB;
  • An RRC reconfiguration message sending module configured to generate an RRC reconfiguration message of the MeNB, and send the RRC reconfiguration message to the user equipment, where the RRC reconfiguration message of the MeNB carries the second RRC transaction identifier and the RRC reconfiguration parameter of the SeNB;
  • a correspondence relationship saving module configured to save a correspondence between the first RRC transaction identifier and the second RRC transaction identifier
  • the RRC reconfiguration response receiving module is configured to receive an RRC reconfiguration response message returned by the user equipment, where the RRC reconfiguration response message includes a second RRC transaction identifier and RRC reconfiguration result information;
  • the RRC reconfiguration response sending module is configured to send an RRC reconfiguration response message to the SeNB, where the RRC reconfiguration response message sent to the SeNB includes the first RRC transaction identifier and the RRC reconfiguration result information.
  • the MeNB after receiving the RRC reconfiguration message of the SeNB, the MeNB constructs an RRC reconfiguration message of the MeNB, where the RRC reconfiguration parameter in the RRC reconfiguration message of the SeNB is saved. Correspondence of RRC transaction identifiers in messages. In this manner, the user equipment side processes only the received RRC reconfiguration message, and does not recognize whether it is the RRC reconfiguration of the MeNB or the RRC reconfiguration of the SeNB. The MeNB identifies the RRC feedback response for the SeNB according to the corresponding relationship of the saved RRC transaction identifier and feeds back to the SeNB, and solves the problem of how to handle the RRC reconfiguration parameter parallel configuration for the SeNB.
  • the embodiment of the present application further provides an evolved base station, including a processor, where the processor is configured to receive an RRC reconfiguration message of the SeNB, where the RRC reconfiguration message of the SeNB carries the first RRC.
  • Transmitting the identity and the RRC reconfiguration parameter of the SeNB Transmitting the identity and the RRC reconfiguration parameter of the SeNB; generating an RRC reconfiguration message of the MeNB, and transmitting the RRC reconfiguration message of the MeNB, where the RRC reconfiguration message of the MeNB carries the second RRC transaction identifier and the RRC reconfiguration parameter of the SeNB; Corresponding relationship between the transaction identifier and the second RRC transaction identifier; receiving an RRC reconfiguration response message returned by the user equipment, where the RRC reconfiguration response message includes a second RRC transaction identifier and RRC reconfiguration result information; And configuring the response message, where the RRC reconfiguration response message sent to the SeNB includes the first RRC transaction identifier and the RRC reconfiguration result information.
  • the MeNB after receiving the RRC reconfiguration message of the SeNB, the MeNB constructs an RRC reconfiguration message of the MeNB, where the RRC reconfiguration parameter in the RRC reconfiguration message of the SeNB is saved. Correspondence of RRC transaction identifiers in messages. In this manner, the user equipment side processes only the received RRC reconfiguration message, and does not identify whether it is the RRC reconfiguration of the MeNB or the SeNB. RRC reconfiguration.
  • the MeNB identifies the RRC feedback response for the SeNB according to the corresponding relationship of the saved RRC transaction identifier and feeds back to the SeNB, and solves the problem of how to handle the RRC reconfiguration parameter parallel configuration for the SeNB.
  • FIG. 1 is a schematic diagram of a method for reconfiguring a first evolved base station according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a method for reconfiguring a second evolved base station according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a method for reconfiguring a third evolved base station according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a method for reconfiguring a fourth evolved base station according to an implementation of the present application
  • FIG. 5 is a schematic diagram of a bearer separated network scenario according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a first user equipment according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a first evolved base station according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a second evolved base station according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a third evolved base station according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a second user equipment according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a fourth evolved base station according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a fifth evolved base station according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram of a sixth evolved base station according to an embodiment of the present application.
  • An embodiment of the present application provides a method for reconfiguring an evolved base station, a user equipment, and an evolved base station.
  • the embodiments of the present application will be described in detail below with reference to the accompanying drawings.
  • FIG. 1 is a schematic diagram of a method for reconfiguring an evolved base station according to an embodiment of the present disclosure, which specifically includes the following operations:
  • Step 100 The user equipment receives an RRC reconfiguration message sent by the MeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter of the SeNB and an RRC reconfiguration parameter of the MeNB.
  • step 110 If the RRC reconfiguration parameter of the MeNB is negligible, step 110 is performed, the user equipment does not feed back the message to the MeNB, or returns the RRC reconfiguration result information of the SeNB to the MeNB.
  • the user equipment feeds back an RRC reconfiguration success message to the MeNB, where the RRC reconfiguration success message carries the RRC reconfiguration result information of the SeNB.
  • step 130 If an abnormality occurs when the RRC reconfiguration of the MeNB is performed according to the RRC reconfiguration parameter of the MeNB, step 130 is performed, and the user equipment initiates RRC reestablishment to the MeNB.
  • the RRC reconfiguration message received by the user equipment includes both the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration result for the MeNB
  • the RRC reconfiguration result of the SeNB is fed back in different manners, so that the network side knows the RRC reconfiguration result of the SeNB, and solves the problem of how the RRC parameter parallel configuration of the SeNB is handled.
  • FIG. 2 is a schematic diagram of a method for reconfiguring an evolved base station according to an embodiment of the present disclosure, which specifically includes the following operations:
  • Step 200 The MeNB receives an RRC reconfiguration message sent by the SeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter of the SeNB.
  • Step 210 The MeNB sends the RRC reconfiguration message sent by the SeNB to the user equipment in the RRC reconfiguration message of the MeNB, where the RRC reconfiguration message of the MeNB further includes the RRC reconfiguration parameter of the MeNB.
  • Step 220 If the MeNB receives the RRC reconfiguration result information of the SeNB returned by the user equipment, the RRC reconfiguration result is fed back to the SeNB according to the RRC reconfiguration result information of the SeNB.
  • the MeNB transparently transmits the RRC reconfiguration message of the SeNB to the user equipment, and performs feedback to the SeNB according to the RRC reconfiguration result of the SeNB returned by the user equipment, so that the network side learns the SeNB.
  • the RRC reconfiguration result solves the problem of how the SeNB's RRC parameter parallel configuration is handled.
  • FIG. 3 is a schematic diagram of a method for reconfiguring an evolved base station according to an embodiment of the present disclosure, including:
  • Step 300 When the MeNB receives the RRC reconfiguration message of the SeNB, parse the RRC reconfiguration message of the SeNB.
  • step 310 the MeNB forwards the RRC reconfiguration message of the SeNB to the user equipment, and feeds back to the SeNB after determining that the RRC reconfiguration for the SeNB is successful.
  • RRC reconfiguration success message
  • step 320 is performed, and the MeNB sends a message that the RRC reconfiguration is abnormal to the SeNB.
  • the MeNB in the case of the bearer offloading, the MeNB first parses the RRC reconfiguration parameter of the SeNB, and sends a message of successfully configuring or reestablishing the RRC reconfiguration parameter to the SeNB according to different conditions of the parsed reconfiguration message.
  • the MeNB is enabled to effectively handle the RRC reconfiguration parameter parallel configuration problem of the UE for the SeNB.
  • FIG. 4 is a schematic diagram of a method for reconfiguring an evolved base station according to an embodiment of the present disclosure, including:
  • Step 400 The MeNB receives an RRC reconfiguration message of the SeNB, where the RRC reconfiguration message of the SeNB carries the first RRC transaction identifier and the RRC reconfiguration parameter of the SeNB.
  • Step 410 The MeNB generates an RRC reconfiguration message of the MeNB, and sends the RRC reconfiguration message to the user equipment.
  • the RRC reconfiguration message of the MeNB carries the second RRC transaction identifier and the RRC reconfiguration parameter of the SeNB.
  • Step 420 The MeNB saves a correspondence between the first RRC transaction identifier and the second RRC transaction identifier.
  • Step 430 The MeNB receives an RRC reconfiguration response message returned by the user equipment, where the RRC reconfiguration response message includes a second RRC transaction identifier and RRC reconfiguration result information.
  • Step 440 The MeNB sends an RRC reconfiguration response message to the SeNB, where the RRC reconfiguration response message sent to the SeNB includes the first RRC transaction identifier and the RRC reconfiguration result information.
  • the MeNB after receiving the RRC reconfiguration message of the SeNB, the MeNB constructs an RRC reconfiguration message of the MeNB, where the RRC reconfiguration parameter in the RRC reconfiguration message of the SeNB is saved. Correspondence of RRC transaction identifiers in messages. In this manner, the user equipment side processes only the received RRC reconfiguration message, and does not recognize whether it is the RRC reconfiguration of the MeNB or the RRC reconfiguration of the SeNB. The MeNB identifies the RRC feedback response for the SeNB according to the corresponding relationship of the saved RRC transaction identifier and feeds back to the SeNB, and solves the problem of how to handle the RRC reconfiguration parameter parallel configuration for the SeNB.
  • the bearer between the signaling gateway S-GW of the UE and the MeNB is offloaded by two SeNBs. There are three bearer paths between the UE and the MeNB.
  • the embodiment of the present application adopts the technical solutions shown in the following application example 1 to application embodiment 5.
  • the method when the RRC configuration message of the SeNB has negligible processing, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner.
  • the MeNB does not parse the RRC reconfiguration message, and the RRC reconfiguration message is sent to the UE in the newly generated Uu interface RRC reconfiguration message (that is, the RRC reconfiguration message of the MeNB), and the RRC reconfiguration message of the Uu interface is also Carrying the RRC reconfiguration parameter of the MeNB;
  • the UE separately checks the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB;
  • the RRC reconfiguration success message built by the UE does not carry any RRC reconfiguration of the SeNB.
  • Result information (specifically, does not carry the RRC container information of the SeNB);
  • the MeNB After receiving the RRC reconfiguration success message built by the UE, the MeNB understands that the configuration of the UE for the MeNB is successful, but the SeNB has a negligible error and does not perform any subsequent processing.
  • the method when the UE is configured successfully for both the MeNB and the SeNB, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB does not parse the RRC reconfiguration message, and the RRC reconfiguration message is sent to the UE in the newly generated Uu interface RRC reconfiguration message, and the RRC reconfiguration parameter of the Uu interface further carries the RRC reconfiguration parameter of the MeNB.
  • the UE separately checks the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB;
  • the UE constructs the RRC reconfiguration success message carrying the RRC reconfiguration success information including the SeNB (specifically, the RRC reconfiguration success message carrying the SeNB) Container) and sent to the MeNB;
  • the UE After receiving the RRC reconfiguration success message, the UE is configured to be successfully configured by the UE for the MeNB and the SeNB, and the RRC reconfiguration success message of the SeNB in the container is forwarded to the SeNB.
  • the SeNB receives the RRC reconfiguration success message on the Xn interface.
  • the method when the RRC reconfiguration process of the SeNB needs to be performed, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB does not parse the RRC reconfiguration message, and the RRC reconfiguration message is sent to the UE in the newly generated Uu interface RRC reconfiguration message, and the RRC reconfiguration parameter of the Uu interface further carries the RRC reconfiguration parameter of the MeNB.
  • the UE separately checks the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB;
  • the UE constructs an RRC reconfiguration success message carrying the information that the RRC reconfiguration of the SeNB is abnormal (specifically, the information may be carried by the new RRC IE) And sent to the MeNB;
  • the MeNB After receiving the RRC reconfiguration success message built by the UE, the MeNB understands that the MeNB configuration is successful, and the RRC reconfiguration process of the SeNB is abnormal.
  • the MeNB informs the SeNB that the RRC reconfiguration process is abnormal in the manner of Xn IE or RRC IE on the Xn interface. Specifically, the SeNB may be notified that the RRC reconfiguration process is abnormal by notifying the SeNB to perform reconfiguration of all bearers.
  • the SeNB After receiving the notification from the MeNB, the SeNB still uses the original wireless parameter configuration. Further, subsequent reconfiguration operations of all bearers can be performed.
  • the method when the RRC message of the MeNB itself has a decoding error, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB does not parse the RRC reconfiguration message, and the RRC reconfiguration message is sent to the UE in the newly generated Uu interface RRC reconfiguration message, and the RRC reconfiguration parameter of the Uu interface further carries the RRC reconfiguration parameter of the MeNB.
  • the UE separately checks the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB;
  • the UE may not reply any information to the MeNB;
  • the MeNB does not receive any response message, it is understood that the RRC reconfiguration operation of the MeNB and the SeNB has a negligible problem.
  • the method when the RRC reconfiguration process of the SeNB needs to be re-established, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB does not parse the RRC reconfiguration message, and the RRC reconfiguration message is included in the newly generated Uu interface RRC reconfiguration message, and the RRC reconfiguration message of the Uu interface further carries the RRC reconfiguration parameter of the MeNB.
  • the UE separately checks the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB;
  • the UE may initiate an RRC reestablishment procedure.
  • the embodiment of the present application adopts the technical solutions as shown in the application example 6 to the application embodiment 9.
  • the MeNB constructs a new RRC-Transaction Identifier and establishes a mapping relationship, and the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and the RRC reconfiguration message includes a first RRC-TransactionIdentifier; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB parses the RRC reconfiguration message, and takes out the first RRC-TransactionIdentifier;
  • the MeNB maps the value of the first RRC-TransactionIdentifier to the second RRC-TransactionIdentifier in the newly generated RRC reconfiguration message of the Uu interface, and saves the mapping relationship;
  • the MeNB sends an RRC reconfiguration message of the Uu interface to the UE, where the RRC reconfiguration message of the Uu interface carries the RRC configuration parameter of the SeNB in the Xn interface message, and further carries the RRC reconfiguration parameter of the MeNB.
  • the MeNB After receiving the RRC reconfiguration response message from the Uu interface, the MeNB extracts the corresponding second RRC-TransactionIdentifier, and finds the first RRC-TransactionIdentifier corresponding to the Xn interface, and adds the phase to the phase.
  • the RRC reconfiguration response message of the Xn interface should be;
  • the MeNB constructs an RRC reconfiguration response message of the SeNB and transmits it to the SeNB in an RRC container manner.
  • the method when the RRC configuration message of the SeNB has an encoding error, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB parses the RRC reconfiguration message. If the RRC reconfiguration message itself is negligible (if there is a codec error), the subsequent processing may not be performed, and the failure response may be returned to the SeNB, and the corresponding error type is indicated therein;
  • the SeNB may interpret that the message itself has a codec error because it has not received any response from the MeNB.
  • the method when the parameter configuration in the RRC reconfiguration message is acceptable, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB parses the RRC reconfiguration message. If the parameter configuration in the RRC reconfiguration message is acceptable, the MeNB constructs a new Uu interface RRC reconfiguration message and sends the message to the UE.
  • the Uu interface RRC reconfiguration message also carries the RRC reconfiguration parameter of the MeNB. ;
  • the MeNB After receiving the RRC reconfiguration success message from the Uu interface, the MeNB constructs an RRC reconfiguration success message of the SeNB;
  • the MeNB sends an RRC reconfiguration success message of the SeNB to the SeNB in an RRC container manner or an Xn IE manner on the Xn interface.
  • the parameter configuration in the RRC reconfiguration message is acceptable, that is, the parameter configuration does not exceed the capability of the UE, and the parameter configuration of the RRC reconfiguration message is abnormal during the execution.
  • the method when the parameter configuration in the RRC reconfiguration message is unacceptable, the method includes:
  • the SeNB constructs a new RRC reconfiguration message, and includes a new RRC configuration parameter in the RRC reconfiguration message; the RRC reconfiguration message is included in the Xn interface message, and is transmitted to the MeNB in an RRC container manner;
  • the MeNB parses the RRC reconfiguration message. If the parameter configuration in the RRC reconfiguration message is unacceptable, the SeNB needs to be notified that the RRC reconfiguration process is abnormal.
  • the MeNB directly responds to the SeNB, and the SeNB notifies the SeNB of the failure response in the manner of the Xn IE or the RRC IE.
  • the failure response indicates that the RRC reconfiguration process is abnormal, and further may notify the UE to perform the reconfiguration operation of all the bearers.
  • the SeNB After receiving the failure response, the SeNB adopts the original wireless parameter configuration, and further performs subsequent all bearer reconfiguration operations.
  • the parameter configuration in the RRC reconfiguration message is unacceptable, and the parameter configuration in the RRC reconfiguration message exceeds the capability of the UE, or the parameter configuration of the RRC reconfiguration message is abnormal during the execution. .
  • the embodiment of the present application further provides a user equipment, as shown in FIG. 6, including:
  • the RRC reconfiguration information receiving module 601 is configured to receive a radio resource control RRC reconfiguration message sent by the primary evolved base station MeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter from the evolved base station SeNB and an RRC reconfiguration parameter of the MeNB. ;
  • the RRC reconfiguration result processing module 602 if the RRC reconfiguration parameter of the MeNB is negligible, the RRC reconfiguration result processing module 602 is configured to not feed back the message to the MeNB, or return the RRC reconfiguration result information of the SeNB to the MeNB;
  • the RRC reconfiguration result processing module 602 is configured to feed back an RRC reconfiguration success message to the MeNB, where the RRC reconfiguration success message carries the RRC reconfiguration result information of the SeNB. ;
  • the RRC reconfiguration result processing module 602 is configured to initiate RRC reestablishment to the MeNB.
  • the user equipment provided by the embodiment of the present application in the case of the bearer offloading, if the RRC reconfiguration message received by the user equipment includes both the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration for the MeNB As a result, the RRC reconfiguration result of the SeNB is used to feedback the RRC reconfiguration result of the SeNB in different manners, so that the network side knows the RRC reconfiguration result of the SeNB, and solves the problem of how the RRC parameter parallel configuration of the SeNB is handled.
  • the RRC reconfiguration result information of the SeNB is information that the RRC reconfiguration of the SeNB is successful.
  • the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality.
  • the RRC reconfiguration result processing module 602 is further configured to not feed back information about the RRC reconfiguration result of the SeNB to the MeNB.
  • the embodiment of the present application further provides another user equipment, including a processor.
  • the processor is configured to receive a radio resource control RRC reconfiguration message sent by the primary evolved base station MeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter from the evolved base station SeNB and an RRC reconfiguration parameter of the MeNB; if the MeNB The RRC reconfiguration parameter is negligible, does not feed back the message to the MeNB, or returns the RRC reconfiguration result information of the SeNB to the MeNB; if the RRC of the MeNB is completed according to the RRC reconfiguration parameter of the MeNB Reconfiguring, feeding back an RRC reconfiguration success message to the MeNB, where the RRC reconfiguration success message carries the RRC reconfiguration result information of the SeNB; if an abnormality occurs during the RRC reconfiguration of the MeNB according to the RRC reconfiguration parameter of the MeNB, the MeNB is sent to the MeNB. Initiate an RRC rebuild.
  • the user equipment provided by the embodiment of the present application in the case of the bearer offloading, if the RRC reconfiguration message received by the user equipment includes both the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration for the MeNB As a result, the RRC reconfiguration result of the SeNB is used to feedback the RRC reconfiguration result of the SeNB in different manners, so that the network side knows the RRC reconfiguration result of the SeNB, and solves the problem of how the RRC parameter parallel configuration of the SeNB is handled.
  • an evolved base station as shown in FIG. 7, including:
  • the RRC reconfiguration message receiving module 701 is configured to receive an RRC reconfiguration message sent by the SeNB, where the RRC reconfiguration message carries an RRC reconfiguration parameter of the SeNB.
  • the RRC reconfiguration message sending module 702 is configured to send the RRC reconfiguration message sent by the SeNB to the user equipment in the RRC reconfiguration message of the MeNB, where the RRC reconfiguration message of the MeNB further includes an RRC reconfiguration parameter of the MeNB.
  • the RRC reconfiguration result feedback module 703 is configured to: when receiving the RRC reconfiguration result information of the SeNB returned by the user equipment, feed back an RRC reconfiguration result to the SeNB according to the RRC reconfiguration result information of the SeNB.
  • the MeNB transmits the RRC reconfiguration message of the SeNB to the user equipment, and feeds back to the SeNB according to the RRC reconfiguration result of the SeNB returned by the user equipment, so that the network side learns the SeNB.
  • the RRC reconfiguration result solves the problem of how the SeNB's RRC parameter parallel configuration is handled.
  • the RRC reconfiguration result feedback module 703 is specifically configured to:
  • the SeNB feeds back a message that the RRC reconfiguration succeeds;
  • the SeNB If the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality, the SeNB returns a message that the RRC reconfiguration is abnormal.
  • the RRC reconfiguration result feedback module 703 is further configured to not feed back the RRC reconfiguration result to the SeNB if the RRC reconfiguration result information of the SeNB is not received.
  • the embodiment of the present application further provides an evolved base station, including a processor, where the processor is configured to receive an RRC reconfiguration message sent by the SeNB, where the RRC reconfiguration message carries the RRC weight of the SeNB.
  • the RRC reconfiguration message sent by the SeNB is sent to the user equipment in the RRC reconfiguration message sent by the SeNB, and the RRC reconfiguration parameter of the MeNB further includes the RRC reconfiguration parameter of the MeNB; Receiving the RRC reconfiguration result information of the SeNB returned by the user equipment, and feeding back the RRC reconfiguration result to the SeNB according to the RRC reconfiguration result information of the SeNB.
  • the MeNB transmits the RRC reconfiguration message of the SeNB to the user equipment, and feeds back to the SeNB according to the RRC reconfiguration result of the SeNB returned by the user equipment, so that the network side learns the SeNB.
  • the RRC reconfiguration result solves the problem of how the SeNB's RRC parameter parallel configuration is handled.
  • the embodiment of the present application further provides an evolved base station, as shown in FIG. 8, including:
  • the RRC reconfiguration message parsing module 801 is configured to parse the RRC reconfiguration message of the SeNB when receiving the RRC reconfiguration message of the SeNB;
  • the RRC reconfiguration result feedback module 802 is configured to: if the parameter configuration in the RRC reconfiguration message of the SeNB is parsed, the RRC reconfiguration message of the SeNB is forwarded to the user equipment, and the RRC reconfiguration for the SeNB is determined to be successful. The message that the RRC reconfiguration succeeds is sent back to the SeNB. If the parameter configuration in the RRC reconfiguration message of the SeNB is unacceptable, the message that the RRC reconfiguration is abnormal is sent to the SeNB.
  • the MeNB in the case of the bearer offloading, the MeNB first parses the RRC reconfiguration parameter of the SeNB, and sends a message of successfully configuring or reestablishing the RRC reconfiguration parameter to the SeNB according to different conditions of the parsed reconfiguration message.
  • the MeNB is enabled to effectively handle the RRC reconfiguration parameter parallel configuration problem of the UE for the SeNB.
  • the RRC reconfiguration result feedback module 802 is further configured to: if the RRC reconfiguration message of the SeNB is parsed, the UE does not perform any processing or send a notification message that the SeNB's RRC reconfiguration message is negligible to the SeNB.
  • the embodiment of the present application further provides an evolved base station, including a processor.
  • the processor is configured to: when receiving the RRC reconfiguration message of the SeNB, parse the RRC reconfiguration message of the SeNB; if it is determined that the parameter configuration in the RRC reconfiguration message of the SeNB is acceptable, forwarding the SeNB to the user equipment The RRC reconfiguration message, and after the RRC reconfiguration succeeding for the SeNB is determined, the RRC reconfiguration success message is fed back to the SeNB; if the parameter configuration in the RRC reconfiguration message of the SeNB is unacceptable, the RRC is sent to the SeNB. Configure a message that an exception has occurred.
  • the MeNB in the case of the bearer offloading, the MeNB first parses the RRC reconfiguration parameter of the SeNB, and sends a message of successfully configuring or reestablishing the RRC reconfiguration parameter to the SeNB according to different conditions of the parsed reconfiguration message.
  • the MeNB is enabled to effectively handle the RRC reconfiguration parameter parallel configuration problem of the UE for the SeNB.
  • the embodiment of the present application further provides an evolved base station, as shown in FIG. include:
  • the RRC reconfiguration message receiving module 901 is configured to receive an RRC reconfiguration message of the SeNB, where the RRC reconfiguration message of the SeNB carries the first RRC transaction identifier and the RRC reconfiguration parameter of the SeNB;
  • the RRC reconfiguration message sending module 902 is configured to generate an RRC reconfiguration message of the MeNB, and send the RRC reconfiguration message to the user equipment, where the RRC reconfiguration message of the MeNB carries the second RRC transaction identifier and the RRC reconfiguration parameter of the SeNB.
  • the correspondence relationship saving module 903 is configured to save a correspondence between the first RRC transaction identifier and the second RRC transaction identifier.
  • the RRC reconfiguration response receiving module 904 is configured to receive an RRC reconfiguration response message that is returned by the user equipment, where the RRC reconfiguration response message includes a second RRC transaction identifier and RRC reconfiguration result information.
  • the RRC reconfiguration response sending module 905 is configured to send an RRC reconfiguration response message to the SeNB, where the RRC reconfiguration response message sent to the SeNB includes the first RRC transaction identifier and the RRC reconfiguration result information.
  • the MeNB after receiving the RRC reconfiguration message of the SeNB, the MeNB constructs an RRC reconfiguration message of the MeNB, where the RRC reconfiguration parameter in the RRC reconfiguration message of the SeNB is saved. Correspondence of RRC transaction identifiers in messages. In this manner, the user equipment side processes only the received RRC reconfiguration message, and does not recognize whether it is the RRC reconfiguration of the MeNB or the RRC reconfiguration of the SeNB. The MeNB identifies the RRC feedback response for the SeNB according to the corresponding relationship of the saved RRC transaction identifier and feeds back to the SeNB, and solves the problem of how to handle the RRC reconfiguration parameter parallel configuration for the SeNB.
  • the embodiment of the present application further provides an evolved base station, including a processor, where the processor is configured to receive an RRC reconfiguration message of the SeNB, where the RRC reconfiguration message of the SeNB carries the first RRC.
  • Transmitting the identity and the RRC reconfiguration parameter of the SeNB Transmitting the identity and the RRC reconfiguration parameter of the SeNB; generating an RRC reconfiguration message of the MeNB, and transmitting the RRC reconfiguration message of the MeNB, where the RRC reconfiguration message of the MeNB carries the second RRC transaction identifier and the RRC reconfiguration parameter of the SeNB; Corresponding relationship between the transaction identifier and the second RRC transaction identifier; receiving an RRC reconfiguration response message returned by the user equipment, where the RRC reconfiguration response message includes a second RRC transaction identifier and RRC reconfiguration result information; And configuring the response message, where the RRC reconfiguration response message sent to the SeNB includes the first RRC transaction identifier and the RRC reconfiguration result information.
  • the embodiment of the present application further provides a user equipment, as shown in FIG. 10, including:
  • the processor 1001 is configured to read a program in the memory 1004 and perform the following process:
  • the RRC reconfiguration message sent by the MeNB where the RRC reconfiguration message carries the RRC reconfiguration parameter of the SeNB and the RRC reconfiguration parameter of the MeNB; if the RRC reconfiguration parameter of the MeNB is If not, the message is not fed back to the MeNB, or the RRC reconfiguration result information of the SeNB is returned to the MeNB. If the RRC reconfiguration of the MeNB is completed according to the RRC reconfiguration parameter of the MeNB, the RRC reconfiguration success message is fed back to the MeNB. The configuration success message carries the RRC reconfiguration result information of the SeNB. If an abnormality occurs when the RRC reconfiguration of the MeNB is performed according to the RRC reconfiguration parameter of the MeNB, an RRC reestablishment is initiated to the MeNB.
  • the transceiver 1002 is configured to receive and transmit data under the control of the processor 1001.
  • the user equipment provided by the embodiment of the present application in the case of the bearer offloading, if the RRC reconfiguration message received by the user equipment includes both the RRC reconfiguration parameter of the MeNB and the RRC reconfiguration parameter of the SeNB, the RRC reconfiguration for the MeNB As a result, the RRC reconfiguration result of the SeNB is used to feedback the RRC reconfiguration result of the SeNB in different manners, so that the network side knows the RRC reconfiguration result of the SeNB, and solves the problem of how the RRC parameter parallel configuration of the SeNB is handled.
  • the RRC reconfiguration result information of the SeNB is information that the RRC reconfiguration of the SeNB is successful.
  • the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality.
  • the processor 1001 does not feed back information about the RRC reconfiguration result of the SeNB to the MeNB.
  • bus 1000 may include any number of interconnected buses and bridges, and bus 1000 will include one or more processors represented by processor 1001 and memory represented by memory 1004. The various circuits are linked together. The bus 1000 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • Bus interface 1003 provides an interface between bus 1000 and transceiver 1002.
  • the transceiver 1002 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium. For example, transceiver 1002 receives external data from other devices. The transceiver 1002 is configured to send the processed data of the processor 1001 to other devices.
  • a user interface 1005 such as a keypad, display, speaker, microphone, joystick, may also be provided.
  • the processor 1001 is responsible for managing the bus 1000 and the usual processing, running a general purpose operating system as described above, and also providing various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 1004 can be used to store data used by the processor 1001 in performing operations.
  • the processor 1001 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device).
  • CPU Central Embedded Device
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the embodiment of the present application further provides an evolved base station, as shown in FIG.
  • the processor 1101 is configured to read a program in the memory 1004 and perform the following process:
  • the RRC reconfiguration message sent by the SeNB receives, by the transceiver 1102, the RRC reconfiguration message sent by the SeNB, where the RRC reconfiguration message carries the RRC reconfiguration parameter of the SeNB, and the RRC reconfiguration message sent by the SeNB is carried in the RRC reconfiguration message of the MeNB and sent to the user equipment, where The RRC reconfiguration parameter of the MeNB further includes an RRC reconfiguration parameter of the MeNB. If the RRC reconfiguration result information of the SeNB returned by the user equipment is received, the RRC reconfiguration result is fed back to the SeNB according to the RRC reconfiguration result information of the SeNB.
  • the transceiver 1102 is configured to receive and transmit data under the control of the processor 1101.
  • the MeNB transmits the RRC reconfiguration message of the SeNB to the user equipment, and feeds back to the SeNB according to the RRC reconfiguration result of the SeNB returned by the user equipment, so that the network side learns the SeNB.
  • the RRC reconfiguration result solves the problem of how the SeNB's RRC parameter parallel configuration is handled.
  • the processor 1101 is specifically configured to:
  • the SeNB feeds back a message that the RRC reconfiguration succeeds;
  • the SeNB If the RRC reconfiguration result information of the SeNB is information that the SeNB reconfigures an abnormality, the SeNB returns a message that the RRC reconfiguration is abnormal.
  • the processor 1101 is further configured to not feed back the RRC reconfiguration result to the SeNB if the RRC reconfiguration result information of the SeNB is not received.
  • bus 1100 can include any number of interconnected buses and bridges, and bus 1100 will include one or more processors represented by processor 1101 and memory represented by memory 1104. The various circuits are linked together. The bus 1100 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art and, therefore, will not be further described herein.
  • Bus interface 1103 provides an interface between bus 1100 and transceiver 1102.
  • the transceiver 1102 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the processor 1101 is transmitted over the wireless medium via the antenna 1105. Further, the antenna 1105 also receives the data and transmits the data to the processor 1101.
  • the processor 1101 is responsible for managing the bus 1100 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory 1104 can be used to store the processor 1101 The data used in performing the operation.
  • the processor 1101 may be a CPU, an ASIC, an FPGA, or a CPLD.
  • the embodiment of the present application further provides an evolved base station, as shown in FIG. 12, including:
  • the processor 1201 is configured to read a program in the memory 1204 and perform the following process:
  • the RRC reconfiguration message of the SeNB is parsed; if the parameter configuration in the RRC reconfiguration message of the SeNB is parsed, the RRC of the SeNB is forwarded to the user equipment.
  • the transceiver 1202 is configured to receive and transmit data under the control of the processor 1201.
  • the MeNB in the case of the bearer offloading, the MeNB first parses the RRC reconfiguration parameter of the SeNB, and sends a message of successfully configuring or reestablishing the RRC reconfiguration parameter to the SeNB according to different conditions of the parsed reconfiguration message.
  • the MeNB is enabled to effectively handle the RRC reconfiguration parameter parallel configuration problem of the UE for the SeNB.
  • the processor 1201 is further configured to: if the RRC reconfiguration message of the SeNB is parsed is negligible, perform no processing or send a notification message that the SeNB's RRC reconfiguration message is negligible to the SeNB.
  • bus 1200 can include any number of interconnected buses and bridges, and bus 1200 will include one or more processors represented by processor 1201 and memory represented by memory 1204. The various circuits are linked together. The bus 1200 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • Bus interface 1203 provides an interface between bus 1200 and transceiver 1202. Transceiver 1202 may be an element or multiple elements, such as multiple receivers and transmitters, providing means for communicating with various other devices on a transmission medium. Data processed by processor 1201 is transmitted over wireless medium via antenna 1205. Further, antenna 1205 also receives data and transmits the data to processor 1201.
  • the processor 1201 is responsible for managing the bus 1200 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 1204 can be used to store data used by the processor 1201 in performing operations.
  • the processor 1201 may be a CPU, an ASIC, an FPGA, or a CPLD.
  • the embodiment of the present application further provides an evolved base station, as shown in FIG. 13, including:
  • the processor 1301 is configured to read a program in the memory 1304 and perform the following process:
  • an RRC reconfiguration message of the SeNB where the RRC reconfiguration message of the SeNB carries the first RRC transaction identifier and the RRC reconfiguration parameter of the SeNB; and generates an RRC reconfiguration message of the MeNB, and sends the RRC reconfiguration message to the user equipment, where the MeNB
  • the RRC reconfiguration message carries the second RRC transaction identifier and the RRC reconfiguration parameter of the SeNB; the correspondence between the first RRC transaction identifier and the second RRC transaction identifier is saved in the memory 1304; and the transceiver 1302 receives the user equipment return.
  • RRC reconfiguration response message the RRC reconfiguration response message includes a second RRC transaction identifier and RRC reconfiguration result information; the RRC reconfiguration response message sent by the transceiver 1302 to the SeNB, and the RRC reconfiguration response message sent to the SeNB
  • the first RRC transaction identifier and the foregoing RRC reconfiguration result information are included.
  • the transceiver 1302 is configured to receive and transmit data under the control of the processor 1301.
  • the MeNB after receiving the RRC reconfiguration message of the SeNB, the MeNB constructs an RRC reconfiguration message of the MeNB, where the RRC reconfiguration parameter in the RRC reconfiguration message of the SeNB is saved. Correspondence of RRC transaction identifiers in messages. In this manner, the user equipment side processes only the received RRC reconfiguration message, and does not recognize whether it is the RRC reconfiguration of the MeNB or the RRC reconfiguration of the SeNB. The MeNB identifies the RRC feedback response for the SeNB according to the corresponding relationship of the saved RRC transaction identifier and feeds back to the SeNB, and solves the problem of how to handle the RRC reconfiguration parameter parallel configuration for the SeNB.
  • bus 1300 can include any number of interconnected buses and bridges, and bus 1300 will include one or more processors represented by processor 1301 and memory represented by memory 1304. The various circuits are linked together. The bus 1300 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • Bus interface 1303 provides an interface between bus 1300 and transceiver 1302.
  • Transceiver 1302 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the processor 1301 is transmitted over the wireless medium via the antenna 1305. Further, the antenna 1305 also receives the data and transmits the data to the processor 1301.
  • the processor 1301 is responsible for managing the bus 1300 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 1304 can be used to store data used by the processor 1301 in performing operations.
  • the processor 1301 may be a CPU, an ASIC, an FPGA, or a CPLD.
  • the MeNB after receiving the RRC reconfiguration message of the SeNB, the MeNB constructs an RRC reconfiguration message of the MeNB, where the RRC reconfiguration parameter in the RRC reconfiguration message of the SeNB is saved. Correspondence of RRC transaction identifiers in messages. This processing mode is only on the user equipment side.
  • the received RRC reconfiguration message is processed without identifying whether it is an RRC reconfiguration of the MeNB or an RRC reconfiguration of the SeNB.
  • the MeNB identifies the RRC feedback response for the SeNB according to the corresponding relationship of the saved RRC transaction identifier and feeds back to the SeNB, and solves the problem of how to handle the RRC reconfiguration parameter parallel configuration for the SeNB.
  • 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 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种演进型基站的重配置方法、用户设备及演进型基站。其演进型基站的重配置方法包括：用户设备接收MeNB发送的RRC重配置消息，其中携带从SeNB的RRC重配置参数和MeNB的RRC重配置参数；如果MeNB的RRC重配置参数可忽略，不向MeNB反馈消息，或者返回SeNB的RRC重配置结果信息；如果完成MeNB的RRC重配置，向MeNB反馈RRC重配置成功消息，其中携带SeNB的RRC重配置结果信息；如果MeNB的RRC重配置时出现异常，向MeNB发起RRC重建。利用本申请实施例提供的方案收能够处理针对SeNB的RRC参数并行配置问题。

Description

演进型基站的重配置方法、用户设备及演进型基站
本申请要求在2013年11月01日提交中国专利局、申请号为201310535521.2、申请名称为“演进型基站的重配置方法、用户设备及演进型基站”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络通信设备技术领域，尤其涉及一种演进型基站的重配置方法、用户设备及演进型基站。
背景技术
随着越来越多的家庭基站、微小区、中继等众多本地节点的部署，传统的以宏基站为主的网络架构将逐步演变为更多类型基站共存的网络架构，并提供更多层次的网络覆盖。为了改善该多类型基站共存网络架构下的相关性能，现有技术提出了一种通过非理想链路实现多个eNB(evolved Node B，演进型基站)间协作/聚合的网络架构，在该网络架构下，UE(User Equipment，用户设备)的一部分RB(Radio Bearer，承载无线链路)在MeNB(Master eNB，主演进型基站)管理的MCell(Master Cell，主蜂窝)小区上，这部分RB包括控制面SRB(Signaling Radio Bearer，信令无线承载)和用户面DRB(Data Radio Bearer，数据无线承载)。而同一UE的另外一部分承载(包括SRB和DRB)在SeNB(Secondary eNB，从演进型基站)管理的SCell(Secondary Cell，从蜂窝)小区上。
进一步的，可以通过承载分流的方式实现承载分离。
承载分流是指，MeNB作为锚点，来自或者到达SeNB的数据均通过MeNB进行转发。
在承载分流情况下，为了完成对SeNB的无线参数配置，SeNB需要将其生成的RRC(Radio Resource Control，无线资源控制)重配置参数传送给MeNB，随后再转发给UE。那么，MeNB发送给UE的RRC重配置消息中不仅包含MeNB的RRC重配置参数，还包含SeNB的RRC重配置参数，即所谓的RRC参数并行配置。现有技术中并没有相应的技术方案来解决SeNB的RRC参数并行配置时，RRC重配置消息如何处理，以及RRC重配置结果如何处理的问题。
发明内容
本申请实施例的目的是提供一种演进型基站的重配置方法、用户设备及演进型基站，以解决针对SeNB的RRC参数并行配置如何处理的问题。
本申请实施例的目的是通过以下技术方案实现的：
一种演进型基站的重配置方法，包括：
用户设备接收主演进型基站MeNB发送的无线资源控制RRC重配置消息，该RRC重配置消息中携带从演进型基站SeNB的RRC重配置参数和MeNB的RRC重配置参数；
如果该MeNB的RRC重配置参数可忽略，上述用户设备不向该MeNB反馈消息，或者向该MeNB返回上述SeNB的RRC重配置结果信息；
如果根据该MeNB的RRC重配置参数完成MeNB的RRC重配置，上述用户设备向该MeNB反馈RRC重配置成功消息，该RRC重配置成功消息中携带上述SeNB的RRC重配置结果信息；
如果根据上述MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，上述用户设备向该MeNB发起RRC重建。
本申请实施例提供的方法，在承载分流情况下，如果用户设备接收到的RRC重配置消息中既包括MeNB的RRC重配置参数又包括SeNB的RRC重配置参数，则针对MeNB的RRC重配置结果以及SeNB的RRC重配置结果，采取不同的方式反馈SeNB的RRC重配置结果，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
基于上述演进型基站的重配置方法实施例，较佳地，如果根据上述SeNB的RRC重配置参数完成SeNB的RRC重配置，上述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息；如果根据上述SeNB的RRC重配置参数进行RRC重配置时出现异常，上述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息。
基于上述任意演进型基站的重配置方法实施例，较佳地，如果上述SeNB的RRC重配置参数可忽略，不向上述MeNB反馈携带SeNB的RRC重配置结果的信息。
一种演进型基站的重配置方法，包括：
MeNB接收SeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数；
该MeNB将该SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，该MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；
如果该MeNB接收上述用户设备返回的SeNB的RRC重配置结果信息，根据该SeNB的RRC重配置结果信息向该SeNB反馈RRC重配置结果。
本申请实施例提供的方法，在承载分流情况下，MeNB将SeNB的RRC重配置消息透传给用户设备，并根据用户设备返回的SeNB的RRC重配置结果向SeNB进行反馈，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
较佳地，根据上述SeNB的RRC重配置结果信息向该SeNB反馈RRC重配置结果，包括：
如果该SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息，上述MeNB向该SeNB反馈RRC重配置成功的消息；
如果该SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息，该MeNB向该SeNB返回RRC重配置出现异常的消息。
基于上述任意MeNB透传的方法实施例，较佳地，如果没有接收到上述SeNB的RRC重配置结果信息，不向该SeNB反馈RRC重配置结果。
一种演进型基站的重配置方法，包括：
当MeNB接收到SeNB的RRC重配置消息时，解析该SeNB的RRC重配置消息；
若解析出该SeNB的RRC重配置消息中的参数配置可接受，则MeNB向用户设备转发该SeNB的RRC重配置消息，并在确定针对该SeNB的RRC重配置成功后向该SeNB反馈RRC重配置成功的消息；
若解析出该SeNB的RRC重配置消息中的参数配置不可接受，则MeNB向该SeNB发送RRC重配置出现异常的消息。
本申请实施例提供的方法，在承载分流情况下，MeNB首先将SeNB的RRC重配置参数进行解析，并根据解析出的重配置消息的不同情况向SeNB发送配置成功或重建RRC重配置参数的消息，使MeNB能够有效地处理UE针对SeNB的RRC重配置参数并行配置问题。
基于上述演进型基站的重配置方法实施例，较佳地，若解析出上述SeNB的RRC重配置消息可忽略，则MeNB不做任何处理或向该SeNB发送该SeNB的RRC重配置消息可忽略的通知消息。
一种演进型基站的重配置方法，包括：
MeNB接收SeNB的RRC重配置消息，该SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；
该MeNB生成MeNB的RRC重配置消息并发送给用户设备，该MeNB的RRC重配置消息中携带第二RRC事务标识和上述SeNB的RRC重配置参数；
该MeNB保存该第一RRC事务标识与第二RRC事务标识之间的对应关系；
该MeNB接收上述用户设备返回的RRC重配置响应消息，该RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；
该MeNB向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息 中包括上述第一RRC事务标识和上述RRC重配置结果信息。
本申请实施例提供的方法，在承载分流情况下，MeNB接收到SeNB的RRC重配置消息后，构建MeNB的RRC重配置消息，其中SeNB的RRC重配置消息中的RRC重配置参数，且保存两个消息中的RRC事务标识的对应关系。这种处理方式，用户设备侧仅对接收到的RRC重配置消息进行处理，不识别其是MeNB的RRC重配置还是SeNB的RRC重配置。由MeNB根据保存的RRC事务标识的对应关系，识别针对SeNB的RRC反馈响应并反馈给SeNB，解决了针对SeNB的RRC重配置参数并行配置如何处理的问题。
基于与方法同样的发明构思，本申请实施例还提供一种用户设备，包括：
RRC重配置信息接收模块，用于接收主演进型基站MeNB发送的无线资源控制RRC重配置消息，该RRC重配置消息中携带从演进型基站SeNB的RRC重配置参数和MeNB的RRC重配置参数；
RRC重配置结果处理模块，如果上述MeNB的RRC重配置参数可忽略，RRC重配置结果处理模块用于，不向MeNB反馈消息，或者向MeNB返回SeNB的RRC重配置结果信息；
如果根据上述MeNB的RRC重配置参数完成MeNB的RRC重配置，RRC重配置结果处理模块用于，向MeNB反馈RRC重配置成功消息，该RRC重配置成功消息中携带SeNB的RRC重配置结果信息；
如果根据上述MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，RRC重配置结果处理模块用于，向MeNB发起RRC重建。
本申请实施例提供的用户设备，在承载分流情况下，如果用户设备接收到的RRC重配置消息中既包括MeNB的RRC重配置参数又包括SeNB的RRC重配置参数，则针对MeNB的RRC重配置结果以及SeNB的RRC重配置结果，采取不同的方式反馈SeNB的RRC重配置结果，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
较佳地，如果根据上述SeNB的RRC重配置参数完成SeNB的RRC重配置，上述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息；
如果根据上述SeNB的RRC重配置参数进行RRC重配置时出现异常，上述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息。
较佳地，如果上述SeNB的RRC重配置参数可忽略，RRC重配置结果处理模块还用于，不向MeNB反馈携带SeNB的RRC重配置结果的信息。
基于与方法同样的发明构思，本申请实施例还提供另一种用户设备，包括处理器。该 处理器被配置为接收主演进型基站MeNB发送的无线资源控制RRC重配置消息，该RRC重配置消息中携带从演进型基站SeNB的RRC重配置参数和MeNB的RRC重配置参数；如果该MeNB的RRC重配置参数可忽略，不向MeNB反馈消息，或者向MeNB返回SeNB的RRC重配置结果信息；如果根据该MeNB的RRC重配置参数完成MeNB的RRC重配置，向MeNB反馈RRC重配置成功消息，该RRC重配置成功消息中携带SeNB的RRC重配置结果信息；如果根据该MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，向MeNB发起RRC重建。
本申请实施例提供的用户设备，在承载分流情况下，如果用户设备接收到的RRC重配置消息中既包括MeNB的RRC重配置参数又包括SeNB的RRC重配置参数，则针对MeNB的RRC重配置结果以及SeNB的RRC重配置结果，采取不同的方式反馈SeNB的RRC重配置结果，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
基于与方法同样的发明构思，本申请实施例提供一种演进型基站，包括：
RRC重配置消息接收模块，用于接收SeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数；
RRC重配置消息发送模块，用于将上述SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，该MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；
RRC重配置结果反馈模块，用于如果接收到上述用户设备返回的SeNB的RRC重配置结果信息，根据该SeNB的RRC重配置结果信息向SeNB反馈RRC重配置结果。
本申请实施例提供的MeNB，在承载分流情况下，MeNB将SeNB的RRC重配置消息透传给用户设备，并根据用户设备返回的SeNB的RRC重配置结果向SeNB进行反馈，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
较佳地，RRC重配置结果反馈模块具体用于：
如果上述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息，向SeNB反馈RRC重配置成功的消息；
如果上述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息，向SeNB返回RRC重配置出现异常的消息。
较佳地，RRC重配置结果反馈模块还用于，如果没有接收到上述SeNB的RRC重配置结果信息，不向SeNB反馈RRC重配置结果。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括处理器，该处理器被配置为接收SeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数；将该SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，该MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；如果接收到上述用户设备返回的SeNB的RRC重配置结果信息，根据该SeNB的RRC重配置结果信息向SeNB反馈RRC重配置结果。
本申请实施例提供的MeNB，在承载分流情况下，MeNB将SeNB的RRC重配置消息透传给用户设备，并根据用户设备返回的SeNB的RRC重配置结果向SeNB进行反馈，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括：
RRC重配置消息解析模块，用于当接收到SeNB的RRC重配置消息时，解析该SeNB的RRC重配置消息；
RRC重配置结果反馈模块，用于若解析出该SeNB的RRC重配置消息中的参数配置可接受，则向用户设备转发SeNB的RRC重配置消息，并在确定针对SeNB的RRC重配置成功后向SeNB反馈RRC重配置成功的消息；若解析出该SeNB的RRC重配置消息中的参数配置不可接受，则向SeNB发送RRC重配置出现异常的消息。
本申请实施例提供的MeNB，在承载分流情况下，MeNB首先将SeNB的RRC重配置参数进行解析，并根据解析出的重配置消息的不同情况向SeNB发送配置成功或重建RRC重配置参数的消息，使MeNB能够有效地处理UE针对SeNB的RRC重配置参数并行配置问题。
较佳地，RRC重配置结果反馈模块还用于，若解析出上述SeNB的RRC重配置消息可忽略，则不做任何处理或向SeNB发送SeNB的RRC重配置消息可忽略的通知消息。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括处理器。该处理器被配置为当接收到SeNB的RRC重配置消息时，解析该SeNB的RRC重配置消息；若解析出该SeNB的RRC重配置消息中的参数配置可接受，则向用户设备转发SeNB的RRC重配置消息，并在确定针对SeNB的RRC重配置成功后向SeNB反馈RRC重配置成功的消息；若解析出该SeNB的RRC重配置消息中的参数配置不可接受，则向SeNB发送RRC重配置出现异常的消息。
本申请实施例提供的MeNB，在承载分流情况下，MeNB首先将SeNB的RRC重配置参数进行解析，并根据解析出的重配置消息的不同情况向SeNB发送配置成功或重建RRC 重配置参数的消息，使MeNB能够有效地处理UE针对SeNB的RRC重配置参数并行配置问题。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括：
RRC重配置消息接收模块，用于接收SeNB的RRC重配置消息，该SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；
RRC重配置消息发送模块，用于生成MeNB的RRC重配置消息并发送给用户设备，该MeNB的RRC重配置消息中携带第二RRC事务标识和上述SeNB的RRC重配置参数；
对应关系保存模块，用于保存第一RRC事务标识与第二RRC事务标识之间的对应关系；
RRC重配置响应接收模块，用于接收用户设备返回的RRC重配置响应消息，该RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；
RRC重配置响应发送模块，用于向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括第一RRC事务标识和上述RRC重配置结果信息。
本申请实施例提供的MeNB，在承载分流情况下，MeNB接收到SeNB的RRC重配置消息后，构建MeNB的RRC重配置消息，其中SeNB的RRC重配置消息中的RRC重配置参数，且保存两个消息中的RRC事务标识的对应关系。这种处理方式，用户设备侧仅对接收到的RRC重配置消息进行处理，不识别其是MeNB的RRC重配置还是SeNB的RRC重配置。由MeNB根据保存的RRC事务标识的对应关系，识别针对SeNB的RRC反馈响应并反馈给SeNB，解决了针对SeNB的RRC重配置参数并行配置如何处理的问题。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括处理器，该处理器被配置为接收SeNB的RRC重配置消息，该SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；生成MeNB的RRC重配置消息并发送给用户设备，该MeNB的RRC重配置消息中携带第二RRC事务标识和上述SeNB的RRC重配置参数；保存第一RRC事务标识与第二RRC事务标识之间的对应关系；接收用户设备返回的RRC重配置响应消息，该RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括第一RRC事务标识和上述RRC重配置结果信息。
本申请实施例提供的MeNB，在承载分流情况下，MeNB接收到SeNB的RRC重配置消息后，构建MeNB的RRC重配置消息，其中SeNB的RRC重配置消息中的RRC重配置参数，且保存两个消息中的RRC事务标识的对应关系。这种处理方式，用户设备侧仅对接收到的RRC重配置消息进行处理，不识别其是MeNB的RRC重配置还是SeNB的 RRC重配置。由MeNB根据保存的RRC事务标识的对应关系，识别针对SeNB的RRC反馈响应并反馈给SeNB，解决了针对SeNB的RRC重配置参数并行配置如何处理的问题。
附图说明
图1为本申请实施例提供的第一种演进型基站的重配置方法示意图；
图2为本申请实施例提供的第二种演进型基站的重配置方法示意图；
图3为本申请实施例提供的第三种演进型基站的重配置方法示意图；
图4为本申请实施提供的第四种演进型基站的重配置方法示意图；
图5为本申请实施例提供的承载分离的网络场景示意图；
图6为本申请实施例提供的第一种用户设备示意图；
图7为本申请实施例提供的第一种演进型基站示意图；
图8为本申请实施例提供的第二种演进型基站示意图；
图9为本申请实施例提供的第三种演进型基站示意图；
图10为本申请实施例提供的第二种用户设备示意图；
图11为本申请实施例提供的第四种演进型基站示意图；
图12为本申请实施例提供的第五种演进型基站示意图；
图13为本申请实施例提供的第六种演进型基站示意图。
具体实施方式
本申请实施例提供一种演进型基站的重配置方法、用户设备及演进型基站。下面将结合附图，对本申请实施例进行详细描述。
图1所示为本申请实施例提供的演进型基站的重配置方法，具体包括如下操作：
步骤100、用户设备接收MeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数和MeNB的RRC重配置参数。
如果该MeNB的RRC重配置参数可忽略，执行步骤110、用户设备不向MeNB反馈消息，或者向该MeNB返回SeNB的RRC重配置结果信息。
如果根据该MeNB的RRC重配置参数完成MeNB的RRC重配置，执行步骤120、用户设备向MeNB反馈RRC重配置成功消息，该RRC重配置成功消息中携带SeNB的RRC重配置结果信息。
如果根据该MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，执行步骤130、用户设备向该MeNB发起RRC重建。
本申请实施例提供的方法，在承载分流情况下，如果用户设备接收到的RRC重配置消息中既包括MeNB的RRC重配置参数又包括SeNB的RRC重配置参数，则针对MeNB的RRC重配置结果以及SeNB的RRC重配置结果，采取不同的方式反馈SeNB的RRC重配置结果，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
图2所示为本申请实施例提供的一种演进型基站的重配置方法，具体包括如下操作：
步骤200、MeNB接收SeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数。
步骤210、该MeNB将SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，该MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数。
步骤220、如果该MeNB接收用户设备返回的SeNB的RRC重配置结果信息，根据该SeNB的RRC重配置结果信息向SeNB反馈RRC重配置结果。
本申请实施例提供的方法，在承载分流情况下，MeNB将SeNB的RRC重配置消息透传给用户设备，并根据用户设备返回的SeNB的RRC重配置结果向SeNB进行反馈，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
图3所示为本申请实施例提供的一种演进型基站的重配置方法，包括：
步骤300、当MeNB接收到SeNB的RRC重配置消息时，解析该SeNB的RRC重配置消息；
若解析出该SeNB的RRC重配置消息中的参数配置可接受，则执行步骤310、MeNB向用户设备转发该SeNB的RRC重配置消息，并在确定针对该SeNB的RRC重配置成功后向SeNB反馈RRC重配置成功的消息；
若解析出该SeNB的RRC重配置消息中的参数配置不可接受，则执行步骤320、MeNB向该SeNB发送RRC重配置出现异常的消息。
本申请实施例提供的方法，在承载分流情况下，MeNB首先将SeNB的RRC重配置参数进行解析，并根据解析出的重配置消息的不同情况向SeNB发送配置成功或重建RRC重配置参数的消息，使MeNB能够有效地处理UE针对SeNB的RRC重配置参数并行配置问题。
图4所示为本申请实施例提供的一种演进型基站的重配置方法，包括：
步骤400、MeNB接收SeNB的RRC重配置消息，该SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数。
步骤410、MeNB生成MeNB的RRC重配置消息并发送给用户设备，该MeNB的RRC重配置消息中携带第二RRC事务标识和上述SeNB的RRC重配置参数。
步骤420、该MeNB保存第一RRC事务标识与第二RRC事务标识之间的对应关系。
步骤430、该MeNB接收所述用户设备返回的RRC重配置响应消息，该RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息。
步骤440、该MeNB向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括第一RRC事务标识和上述RRC重配置结果信息。
本申请实施例提供的方法，在承载分流情况下，MeNB接收到SeNB的RRC重配置消息后，构建MeNB的RRC重配置消息，其中SeNB的RRC重配置消息中的RRC重配置参数，且保存两个消息中的RRC事务标识的对应关系。这种处理方式，用户设备侧仅对接收到的RRC重配置消息进行处理，不识别其是MeNB的RRC重配置还是SeNB的RRC重配置。由MeNB根据保存的RRC事务标识的对应关系，识别针对SeNB的RRC反馈响应并反馈给SeNB，解决了针对SeNB的RRC重配置参数并行配置如何处理的问题。
下面将结合具体的应用场景，以用户设备和演进型基站配合实施为例，对本申请实施例进行详细说明。
如图5所示的承载分离的网络场景中，UE的信令网关S-GW与MeNB之间的承载通过两个SeNB分流。则UE与MeNB之间就有三条承载路径。
对于MeNB采用透传的方式将来自SeNB的RRC重配置消息传送给UE的情况，本申请实施例采用如下应用实施例一至应用实施例五所示的技术方案。
应用实施例一中，SeNB的RRC配置消息本身存在可忽略处理时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；该RRC重配置消息包含在Xn接口消息中，以RRC容器(RRC container)方式传送给MeNB；
MeNB不解析该RRC重配置消息，将该RRC重配置消息包含在新生成的Uu接口RRC重配置消息(即MeNB的RRC重配置消息)中发送给UE，该Uu接口的RRC重配置消息中还携带MeNB的RRC重配置参数；
UE分别检查MeNB的RRC重配置参数以及SeNB的RRC重配置参数；
如果MeNB的RRC配置成功，而SeNB的RRC重配置消息可忽略(如对RRC重配置消息中的参数解析错误等)时，在UE构建的RRC重配置成功消息中不携带任何SeNB的RRC重配置结果信息(具体的，不携带SeNB的RRC container信息)；
MeNB接收到UE构建的RRC重配置成功消息后，理解为UE针对MeNB的配置成功，但SeNB出现可忽略错误，不做任何后续处理。
应用实施例二中，UE针对MeNB和SeNB都配置成功时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；该RRC重配置消息包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB不解析该RRC重配置消息，将该RRC重配置消息包含在新生成的Uu接口RRC重配置消息中发送给UE，该Uu接口的RRC重配置消息中还携带MeNB的RRC重配置参数；
UE分别检查MeNB的RRC重配置参数以及SeNB的RRC重配置参数；
如果MeNB的RRC重配置成功，而如果SeNB的RRC重配置过程也成功时，UE构建RRC重配置成功消息中携带包含有SeNB的RRC重配置成功的信息(具体是携带SeNB的RRC重配置成功消息的container)并发送给MeNB；
MeNB接收到UE构建的RRC重配置成功消息后，理解为UE针对MeNB和SeNB都配置成功，相应的将container中的SeNB的RRC重配置成功消息转发给SeNB；
SeNB接收到Xn接口上的RRC重配置成功消息。
应用实施例三中，针对SeNB的RRC重配置过程需采用重建处理时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；该RRC重配置消息包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB不解析该RRC重配置消息，将该RRC重配置消息包含在新生成的Uu接口RRC重配置消息中发送给UE，该Uu接口的RRC重配置消息中还携带MeNB的RRC重配置参数；
UE分别检查MeNB的RRC重配置参数以及SeNB的RRC重配置参数；
如果MeNB的RRC配置成功，而如果针对SeNB的RRC重配置过程出现异常时，UE构建RRC重配置成功消息中携带SeNB的RRC重配置出现异常的信息(具体可以通过新的RRC IE携带该信息)并发送给MeNB；
MeNB接收到UE构建的RRC重配置成功消息后，理解为MeNB配置成功，而SeNB的RRC重配置过程出现异常；
MeNB在Xn接口以Xn IE或RRC IE的方式通知SeNB其RRC重配置过程出现异常。具体的，可以通过通知SeNB进行所有承载的重配置的方式告知SeNB其RRC重配置过程出现异常；
SeNB接收到MeNB的通知后，仍采用原有的无线参数配置。进一步的，可以进行后续的所有承载的重配置操作。
应用实施例四中，MeNB的RRC消息本身出现解码错误时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；该RRC重配置消息包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB不解析该RRC重配置消息，将该RRC重配置消息包含在新生成的Uu接口RRC重配置消息中发送给UE，该Uu接口的RRC重配置消息中还携带MeNB的RRC重配置参数；
UE分别检查MeNB的RRC重配置参数以及SeNB的RRC重配置参数；
如果MeNB的RRC消息本身可忽略(如出现解码错误等)时，UE可以不回复任何信息给MeNB；
如果MeNB没接收到任何响应消息，理解为MeNB和SeNB的RRC重配置操作都出现可忽略问题。
应用实施例五中，针对SeNB的RRC重配置过程需采用重建处理时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；该RRC重配置消息包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB不解析该RRC重配置消息，将该RRC重配置消息包含在新生成的Uu接口RRC重配置消息中，该Uu接口的RRC重配置消息中还携带MeNB的RRC重配置参数；
UE分别检查MeNB的RRC重配置参数以及SeNB的RRC重配置参数；
如果MeNB的RRC重配置过程需要重建处理，UE可以发起RRC重建过程。
对于MeNB解析来自SeNB的RRC重配置消息的情况，本申请实施例采用如应用实施例六至应用实施例九所示的技术方案。
应用实施例六中，MeNB构建新的RRC事务标识(RRC-TransactionIdentifier)并建立映射关系，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含第一RRC-TransactionIdentifier；该RRC重配置消息中包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB解析该RRC重配置消息，取出第一RRC-TransactionIdentifier；
MeNB将该第一RRC-TransactionIdentifier的值映射到Uu接口新生成的RRC重配置消息中的第二RRC-TransactionIdentifier上，并保存该映射关系；
MeNB发送Uu接口的RRC重配置消息给UE，该Uu接口的RRC重配置消息中携带上述Xn接口消息中的SeNB的RRC冲配置参数，还携带MeNB的RRC重配置参数；
MeNB接收到来自Uu接口的RRC重配置响应消息后，取出相应的第二RRC-TransactionIdentifier，并找到Xn接口对应的第一RRC-TransactionIdentifier，添加到相 应的Xn接口的RRC重配置响应消息中；
MeNB构建SeNB的RRC重配置响应消息并以RRC container方式传送给SeNB。
应用实施例七中，SeNB的RRC配置消息本身存在编码错误时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；该RRC重配置消息中包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB解析该RRC重配置消息，如果该RRC重配置消息本身可忽略(如存在编解码错误)，可以不进行后续处理，也可以向SeNB回复失败响应，在其中注明相应的错误类型；
如果MeNB不进行后续处理，SeNB由于没接收到来自MeNB的任何响应，可以解释为消息本身出现编解码错误。
应用实施例八中，RRC重配置消息中参数配置可接受时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；该RRC重配置消息中包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB解析该RRC重配置消息，如果该RRC重配置消息中参数配置可接受，MeNB构建新的Uu接口RRC重配置消息发送给UE，该Uu接口RRC重配置消息中还携带MeNB的RRC重配置参数；
MeNB接收到来自Uu接口的RRC重配置成功消息后，构建SeNB的RRC重配置成功消息；
MeNB在Xn接口以RRC container方式或Xn IE的方式将SeNB的RRC重配置成功消息发给SeNB。
本申请实施例中，所谓RRC重配置消息中参数配置可接受，是指其参数配置没有超过UE的能力，且对该RRC重配置消息的参数配置在执行过程中出现异常。
应用实施例九中，RRC重配置消息中参数配置不可接受时，该方法包括：
SeNB构建新的RRC重配置消息，在该RRC重配置消息中包含新的RRC配置参数；在该RRC重配置消息包含在Xn接口消息中，以RRC container方式传送给MeNB；
MeNB解析该RRC重配置消息，如果该RRC重配置消息中参数配置不可接受，需要通知SeNB其RRC重配置过程出现异常；
MeNB直接回复失败响应给SeNB，其中以Xn IE或RRC IE的方式通知SeNB失败响应，该失败响应中指示RRC重配置过程出现异常，进一步的还可以通知其执行所有承载的重配置操作；
SeNB接收到该失败响应后，采用原来的无线参数配置，进一步的可以执行后续的所有承载重配置操作。
本申请实施例中，所谓的RRC重配置消息中参数配置不可接受，是指RRC重配置消息中的参数配置超过了UE的能力，或者对该RRC重配置消息的参数配置在执行过程中出现异常。
基于与方法同样的发明构思，本申请实施例还提供一种用户设备，如图6所示，包括：
RRC重配置信息接收模块601，用于接收主演进型基站MeNB发送的无线资源控制RRC重配置消息，该RRC重配置消息中携带从演进型基站SeNB的RRC重配置参数和MeNB的RRC重配置参数；
RRC重配置结果处理模块602，如果上述MeNB的RRC重配置参数可忽略，RRC重配置结果处理模块602用于，不向MeNB反馈消息，或者向MeNB返回SeNB的RRC重配置结果信息；
如果根据上述MeNB的RRC重配置参数完成MeNB的RRC重配置，RRC重配置结果处理模块602用于，向MeNB反馈RRC重配置成功消息，该RRC重配置成功消息中携带SeNB的RRC重配置结果信息；
如果根据上述MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，RRC重配置结果处理模块602用于，向该MeNB发起RRC重建。
本申请实施例提供的用户设备，在承载分流情况下，如果用户设备接收到的RRC重配置消息中既包括MeNB的RRC重配置参数又包括SeNB的RRC重配置参数，则针对MeNB的RRC重配置结果以及SeNB的RRC重配置结果，采取不同的方式反馈SeNB的RRC重配置结果，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
较佳地，如果根据上述SeNB的RRC重配置参数完成SeNB的RRC重配置，上述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息；
如果根据上述SeNB的RRC重配置参数进行RRC重配置时出现异常，上述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息。
较佳地，如果上述SeNB的RRC重配置参数可忽略，RRC重配置结果处理模块602还用于，不向MeNB反馈携带SeNB的RRC重配置结果的信息。
基于与方法同样的发明构思，本申请实施例还提供另一种用户设备，包括处理器。该处理器被配置为接收主演进型基站MeNB发送的无线资源控制RRC重配置消息，该RRC重配置消息中携带从演进型基站SeNB的RRC重配置参数和MeNB的RRC重配置参数；如果该MeNB的RRC重配置参数可忽略，不向MeNB反馈消息，或者向MeNB返回所述SeNB的RRC重配置结果信息；如果根据该MeNB的RRC重配置参数完成MeNB的RRC 重配置，向该MeNB反馈RRC重配置成功消息，该RRC重配置成功消息中携带SeNB的RRC重配置结果信息；如果根据该MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，向MeNB发起RRC重建。
本申请实施例提供的用户设备，在承载分流情况下，如果用户设备接收到的RRC重配置消息中既包括MeNB的RRC重配置参数又包括SeNB的RRC重配置参数，则针对MeNB的RRC重配置结果以及SeNB的RRC重配置结果，采取不同的方式反馈SeNB的RRC重配置结果，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
基于与方法同样的发明构思，本申请实施例提供一种演进型基站，如图7所示，包括：
RRC重配置消息接收模块701，用于接收SeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数；
RRC重配置消息发送模块702，用于将SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，该MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；
RRC重配置结果反馈模块703，用于如果接收到用户设备返回的SeNB的RRC重配置结果信息，根据该SeNB的RRC重配置结果信息向SeNB反馈RRC重配置结果。
本申请实施例提供的MeNB，在承载分流情况下，MeNB将SeNB的RRC重配置消息透传给用户设备，并根据用户设备返回的SeNB的RRC重配置结果向SeNB进行反馈，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
较佳地，RRC重配置结果反馈模块703具体用于：
如果上述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息，向SeNB反馈RRC重配置成功的消息；
如果上述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息，向SeNB返回RRC重配置出现异常的消息。
较佳地，RRC重配置结果反馈模块703还用于，如果没有接收到SeNB的RRC重配置结果信息，不向SeNB反馈RRC重配置结果。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括处理器，该处理器被配置为接收SeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数；将SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，该MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；如果接 收到用户设备返回的SeNB的RRC重配置结果信息，根据SeNB的RRC重配置结果信息向SeNB反馈RRC重配置结果。
本申请实施例提供的MeNB，在承载分流情况下，MeNB将SeNB的RRC重配置消息透传给用户设备，并根据用户设备返回的SeNB的RRC重配置结果向SeNB进行反馈，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，如图8所示，包括：
RRC重配置消息解析模块801，用于当接收到SeNB的RRC重配置消息时，解析该SeNB的RRC重配置消息；
RRC重配置结果反馈模块802，用于若解析出该SeNB的RRC重配置消息中的参数配置可接受，则向用户设备转发SeNB的RRC重配置消息，并在确定针对该SeNB的RRC重配置成功后向SeNB反馈RRC重配置成功的消息；若解析出该SeNB的RRC重配置消息中的参数配置不可接受，则向SeNB发送RRC重配置出现异常的消息。
本申请实施例提供的MeNB，在承载分流情况下，MeNB首先将SeNB的RRC重配置参数进行解析，并根据解析出的重配置消息的不同情况向SeNB发送配置成功或重建RRC重配置参数的消息，使MeNB能够有效地处理UE针对SeNB的RRC重配置参数并行配置问题。
较佳地，RRC重配置结果反馈模块802还用于，若解析出该SeNB的RRC重配置消息可忽略，则不做任何处理或向SeNB发送SeNB的RRC重配置消息可忽略的通知消息。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括处理器。该处理器被配置为当接收到SeNB的RRC重配置消息时，解析该SeNB的RRC重配置消息；若解析出该SeNB的RRC重配置消息中的参数配置可接受，则向用户设备转发SeNB的RRC重配置消息，并在确定针对该SeNB的RRC重配置成功后向SeNB反馈RRC重配置成功的消息；若解析出该SeNB的RRC重配置消息中的参数配置不可接受，则向SeNB发送RRC重配置出现异常的消息。
本申请实施例提供的MeNB，在承载分流情况下，MeNB首先将SeNB的RRC重配置参数进行解析，并根据解析出的重配置消息的不同情况向SeNB发送配置成功或重建RRC重配置参数的消息，使MeNB能够有效地处理UE针对SeNB的RRC重配置参数并行配置问题。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，如图9所示，包 括：
RRC重配置消息接收模块901，用于接收SeNB的RRC重配置消息，该SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；
RRC重配置消息发送模块902，用于生成MeNB的RRC重配置消息并发送给用户设备，该MeNB的RRC重配置消息中携带第二RRC事务标识和上述SeNB的RRC重配置参数；
对应关系保存模块903，用于保存第一RRC事务标识与第二RRC事务标识之间的对应关系；
RRC重配置响应接收模块904，用于接收用户设备返回的RRC重配置响应消息，该RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；
RRC重配置响应发送模块905，用于向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括第一RRC事务标识和上述RRC重配置结果信息。
本申请实施例提供的MeNB，在承载分流情况下，MeNB接收到SeNB的RRC重配置消息后，构建MeNB的RRC重配置消息，其中SeNB的RRC重配置消息中的RRC重配置参数，且保存两个消息中的RRC事务标识的对应关系。这种处理方式，用户设备侧仅对接收到的RRC重配置消息进行处理，不识别其是MeNB的RRC重配置还是SeNB的RRC重配置。由MeNB根据保存的RRC事务标识的对应关系，识别针对SeNB的RRC反馈响应并反馈给SeNB，解决了针对SeNB的RRC重配置参数并行配置如何处理的问题。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，包括处理器，该处理器被配置为接收SeNB的RRC重配置消息，该SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；生成MeNB的RRC重配置消息并发送给用户设备，该MeNB的RRC重配置消息中携带第二RRC事务标识和上述SeNB的RRC重配置参数；保存第一RRC事务标识与第二RRC事务标识之间的对应关系；接收用户设备返回的RRC重配置响应消息，该RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括第一RRC事务标识和上述RRC重配置结果信息。
基于与方法同样的发明构思，本申请实施例还提供一种用户设备，如图10所示，包括：
处理器1001，用于读取存储器1004中的程序，执行下列过程：
通过收发机1002接收MeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数和MeNB的RRC重配置参数；如果上述MeNB的RRC重配置参数可 忽略，则不向MeNB反馈消息，或者向MeNB返回SeNB的RRC重配置结果信息；如果根据上述MeNB的RRC重配置参数完成MeNB的RRC重配置，则向MeNB反馈RRC重配置成功消息，该RRC重配置成功消息中携带SeNB的RRC重配置结果信息；如果根据上述MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，则向该MeNB发起RRC重建。
收发机1002，用于在处理器1001的控制下接收和发送数据。
本申请实施例提供的用户设备，在承载分流情况下，如果用户设备接收到的RRC重配置消息中既包括MeNB的RRC重配置参数又包括SeNB的RRC重配置参数，则针对MeNB的RRC重配置结果以及SeNB的RRC重配置结果，采取不同的方式反馈SeNB的RRC重配置结果，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
较佳地，如果根据上述SeNB的RRC重配置参数完成SeNB的RRC重配置，上述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息；
如果根据上述SeNB的RRC重配置参数进行RRC重配置时出现异常，上述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息。
较佳地，如果上述SeNB的RRC重配置参数可忽略，则处理器1001不向MeNB反馈携带SeNB的RRC重配置结果的信息。
在图10中，总线架构(用总线1000来代表)，总线1000可以包括任意数量的互联的总线和桥，总线1000将包括由处理器1001代表的一个或多个处理器和存储器1004代表的存储器的各种电路链接在一起。总线1000还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1003在总线1000和收发机1002之间提供接口。收发机1002可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。例如：收发机1002从其他设备接收外部数据。收发机1002用于将处理器1001处理后的数据发送给其他设备。取决于计算系统的性质，还可以提供用户接口1005，例如小键盘、显示器、扬声器、麦克风、操纵杆。
处理器1001负责管理总线1000和通常的处理，如前述所述运行通用操作系统，还可以提供各种功能、包括定时、外围接口，电压调节、电源管理以及其他控制功能。而存储器1004可以被用于存储处理器1001在执行操作时所使用的数据。
可选的，处理器1001可以是CPU(中央处埋器)、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)或 CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，如图11所示，包括：
处理器1101，用于读取存储器1004中的程序，执行下列过程：
通过收发机1102接收SeNB发送的RRC重配置消息，该RRC重配置消息中携带SeNB的RRC重配置参数；将SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，该MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；如果接收到用户设备返回的SeNB的RRC重配置结果信息，则根据该SeNB的RRC重配置结果信息向SeNB反馈RRC重配置结果。
收发机1102，用于在处理器1101的控制下接收和发送数据。
本申请实施例提供的MeNB，在承载分流情况下，MeNB将SeNB的RRC重配置消息透传给用户设备，并根据用户设备返回的SeNB的RRC重配置结果向SeNB进行反馈，使得网络侧获知SeNB的RRC重配置结果，解决了SeNB的RRC参数并行配置如何处理的问题。
较佳地，处理器1101具体用于：
如果上述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息，向SeNB反馈RRC重配置成功的消息；
如果上述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息，向SeNB返回RRC重配置出现异常的消息。
较佳地，处理器1101还用于，如果没有接收到SeNB的RRC重配置结果信息，不向SeNB反馈RRC重配置结果。
在图11中，总线架构(用总线1100来代表)，总线1100可以包括任意数量的互联的总线和桥，总线1100将包括由处理器1101代表的一个或多个处理器和存储器1104代表的存储器的各种电路链接在一起。总线1100还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1103在总线1100和收发机1102之间提供接口。收发机1102可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器1101处理的数据通过天线1105在无线介质上进行传输，进一步，天线1105还接收数据并将数据传送给处理器1101。
处理器1101负责管理总线1100和通常的处理，还可以提供各种功能，包括定时、外围接口、电压调节、电源管理以及其他控制功能。而存储器1104可以被用于存储处理器 1101在执行操作时所使用的数据。
可选的，处理器1101可以是CPU、ASIC、FPGA或CPLD。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，如图12所示，包括：
处理器1201，用于读取存储器1204中的程序，执行下列过程：
当通过收发机1202接收到SeNB的RRC重配置消息时，解析该SeNB的RRC重配置消息；若解析出该SeNB的RRC重配置消息中的参数配置可接受，则向用户设备转发SeNB的RRC重配置消息，并在确定针对该SeNB的RRC重配置成功后向SeNB反馈RRC重配置成功的消息；若解析出该SeNB的RRC重配置消息中的参数配置不可接受，则向SeNB发送RRC重配置出现异常的消息。
收发机1202，用于在处理器1201的控制下接收和发送数据。
本申请实施例提供的MeNB，在承载分流情况下，MeNB首先将SeNB的RRC重配置参数进行解析，并根据解析出的重配置消息的不同情况向SeNB发送配置成功或重建RRC重配置参数的消息，使MeNB能够有效地处理UE针对SeNB的RRC重配置参数并行配置问题。
较佳地，处理器1201还用于，若解析出该SeNB的RRC重配置消息可忽略，则不做任何处理或向SeNB发送SeNB的RRC重配置消息可忽略的通知消息。
在图12中，总线架构(用总线1200来代表)，总线1200可以包括任意数量的互联的总线和桥，总线1200将包括由处理器1201代表的一个或多个处理器和存储器1204代表的存储器的各种电路链接在一起。总线1200还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1203在总线1200和收发机1202之间提供接口。收发机1202可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器1201处理的数据通过天线1205在无线介质上进行传输，进一步，天线1205还接收数据并将数据传送给处理器1201。
处理器1201负责管理总线1200和通常的处理，还可以提供各种功能，包括定时、外围接口、电压调节、电源管理以及其他控制功能。而存储器1204可以被用于存储处理器1201在执行操作时所使用的数据。
可选的，处理器1201可以是CPU、ASIC、FPGA或CPLD。
基于与方法同样的发明构思，本申请实施例还提供一种演进型基站，如图13所示，包括：
处理器1301，用于读取存储器1304中的程序，执行下列过程：
通过收发机1301接收SeNB的RRC重配置消息，该SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；生成MeNB的RRC重配置消息并发送给用户设备，该MeNB的RRC重配置消息中携带第二RRC事务标识和上述SeNB的RRC重配置参数；将第一RRC事务标识与第二RRC事务标识之间的对应关系保存到存储器1304中；收发机1302接收用户设备返回的RRC重配置响应消息，该RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；通过收发机1302向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括第一RRC事务标识和上述RRC重配置结果信息。
收发机1302，用于在处理器1301的控制下接收和发送数据。
本申请实施例提供的MeNB，在承载分流情况下，MeNB接收到SeNB的RRC重配置消息后，构建MeNB的RRC重配置消息，其中SeNB的RRC重配置消息中的RRC重配置参数，且保存两个消息中的RRC事务标识的对应关系。这种处理方式，用户设备侧仅对接收到的RRC重配置消息进行处理，不识别其是MeNB的RRC重配置还是SeNB的RRC重配置。由MeNB根据保存的RRC事务标识的对应关系，识别针对SeNB的RRC反馈响应并反馈给SeNB，解决了针对SeNB的RRC重配置参数并行配置如何处理的问题。
在图13中，总线架构(用总线1300来代表)，总线1300可以包括任意数量的互联的总线和桥，总线1300将包括由处理器1301代表的一个或多个处理器和存储器1304代表的存储器的各种电路链接在一起。总线1300还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1303在总线1300和收发机1302之间提供接口。收发机1302可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器1301处理的数据通过天线1305在无线介质上进行传输，进一步，天线1305还接收数据并将数据传送给处理器1301。
处理器1301负责管理总线1300和通常的处理，还可以提供各种功能，包括定时、外围接口、电压调节、电源管理以及其他控制功能。而存储器1304可以被用于存储处理器1301在执行操作时所使用的数据。
可选的，处理器1301可以是CPU、ASIC、FPGA或CPLD。
本申请实施例提供的MeNB，在承载分流情况下，MeNB接收到SeNB的RRC重配置消息后，构建MeNB的RRC重配置消息，其中SeNB的RRC重配置消息中的RRC重配置参数，且保存两个消息中的RRC事务标识的对应关系。这种处理方式，用户设备侧仅 对接收到的RRC重配置消息进行处理，不识别其是MeNB的RRC重配置还是SeNB的RRC重配置。由MeNB根据保存的RRC事务标识的对应关系，识别针对SeNB的RRC反馈响应并反馈给SeNB，解决了针对SeNB的RRC重配置参数并行配置如何处理的问题。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (18)

  1. 一种演进型基站的重配置方法，其特征在于，包括：
    用户设备接收主演进型基站MeNB发送的无线资源控制RRC重配置消息，所述RRC重配置消息中携带从演进型基站SeNB的RRC重配置参数和MeNB的RRC重配置参数；
    如果所述MeNB的RRC重配置参数可忽略，所述用户设备不向所述MeNB反馈消息，或者向所述MeNB返回所述SeNB的RRC重配置结果信息；
    如果根据所述MeNB的RRC重配置参数完成MeNB的RRC重配置，所述用户设备向所述MeNB反馈RRC重配置成功消息，所述RRC重配置成功消息中携带所述SeNB的RRC重配置结果信息；
    如果根据所述MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，所述用户设备向所述MeNB发起RRC重建。
  2. 根据权利要求1所述的方法，其特征在于，如果根据所述SeNB的RRC重配置参数完成SeNB的RRC重配置，所述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息；
    如果根据所述SeNB的RRC重配置参数进行RRC重配置时出现异常，所述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息。
  3. 根据权利要求1或2所述的方法，其特征在于，如果所述SeNB的RRC重配置参数可忽略，不向所述MeNB反馈携带SeNB的RRC重配置结果的信息。
  4. 一种演进型基站的重配置方法，其特征在于，包括：
    MeNB接收SeNB发送的RRC重配置消息，所述RRC重配置消息中携带SeNB的RRC重配置参数；
    所述MeNB将所述SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，所述MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；
    如果所述MeNB接收所述用户设备返回的SeNB的RRC重配置结果信息，根据所述SeNB的RRC重配置结果信息向所述SeNB反馈RRC重配置结果。
  5. 根据权利要求4所述的方法，其特征在于，根据所述SeNB的RRC重配置结果信息向所述SeNB反馈RRC重配置结果，包括：
    如果所述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息，所述MeNB向所述SeNB反馈RRC重配置成功的消息；
    如果所述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息，所述MeNB向所述SeNB返回RRC重配置出现异常的消息。
  6. 根据权利要求4或5所述的方法，其特征在于，如果没有接收到所述SeNB的RRC重配置结果信息，不向所述SeNB反馈RRC重配置结果。
  7. 一种演进型基站的重配置方法，其特征在于，包括：
    当MeNB接收到SeNB的RRC重配置消息时，解析所述SeNB的RRC重配置消息；
    若解析出所述SeNB的RRC重配置消息中的参数配置可接受，则所述MeNB向用户设备转发所述SeNB的RRC重配置消息，并在确定针对所述SeNB的RRC重配置成功后向所述SeNB反馈RRC重配置成功的消息；
    若解析出所述SeNB的RRC重配置消息中的参数配置不可接受，则所述MeNB向所述SeNB发送所述RRC重配置出现异常的消息。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    若解析出所述SeNB的RRC重配置消息可忽略，则所述MeNB不做任何处理或向所述SeNB发送所述SeNB的RRC重配置消息可忽略的通知消息。
  9. 一种演进型基站的重配置方法，其特征在于，包括：
    MeNB接收SeNB的RRC重配置消息，所述SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；
    所述MeNB生成MeNB的RRC重配置消息并发送给用户设备，所述MeNB的RRC重配置消息中携带第二RRC事务标识和所述SeNB的RRC重配置参数；
    所述MeNB保存所述第一RRC事务标识与第二RRC事务标识之间的对应关系；
    所述MeNB接收所述用户设备返回的RRC重配置响应消息，所述RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；
    所述MeNB向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括所述第一RRC事务标识和所述RRC重配置结果信息。
  10. 一种用户设备，其特征在于，包括：
    RRC重配置信息接收模块，用于接收主演进型基站MeNB发送的无线资源控制RRC重配置消息，所述RRC重配置消息中携带从演进型基站SeNB的RRC重配置参数和MeNB的RRC重配置参数；
    RRC重配置结果处理模块，用于如果所述MeNB的RRC重配置参数可忽略，则不向所述MeNB反馈消息，或者向所述MeNB返回所述SeNB的RRC重配置结果信息；如果根据所述MeNB的RRC重配置参数完成MeNB的RRC重配置，则向所述MeNB反馈RRC重配置成功消息，所述RRC重配置成功消息中携带所述SeNB的RRC重配置结果信息；如果根据所述MeNB的RRC重配置参数进行MeNB的RRC重配置时出现异常，则向所述 MeNB发起RRC重建。
  11. 根据权利要求10所述的用户设备，其特征在于，如果根据所述SeNB的RRC重配置参数完成SeNB的RRC重配置，所述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息；
    如果根据所述SeNB的RRC重配置参数进行RRC重配置时出现异常，所述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息。
  12. 根据权利要求10或11所述的用户设备，其特征在于，所述RRC重配置结果处理模块还用于：
    如果所述SeNB的RRC重配置参数可忽略，则不向所述MeNB反馈携带SeNB的RRC重配置结果的信息。
  13. 一种演进型基站，其特征在于，包括：
    RRC重配置消息接收模块，用于接收SeNB发送的RRC重配置消息，所述RRC重配置消息中携带SeNB的RRC重配置参数；
    RRC重配置消息发送模块，用于将所述SeNB发送的RRC重配置消息携带在MeNB的RRC重配置消息中发送给用户设备，所述MeNB的RRC重配置消息中还包括MeNB的RRC重配置参数；
    RRC重配置结果反馈模块，用于如果接收到所述用户设备返回的SeNB的RRC重配置结果信息，根据所述SeNB的RRC重配置结果信息向所述SeNB反馈RRC重配置结果。
  14. 根据权利要求13所述的演进型基站，其特征在于，RRC重配置结果反馈模块具体用于：
    如果所述SeNB的RRC重配置结果信息为SeNB的RRC重配置成功的信息，向所述SeNB反馈RRC重配置成功的消息；
    如果所述SeNB的RRC重配置结果信息为SeNB重配置出现异常的信息，向所述SeNB返回RRC重配置出现异常的消息。
  15. 根据权利要求13或14所述的演进型基站，其特征在于，RRC重配置结果反馈模块还用于，如果没有接收到所述SeNB的RRC重配置结果信息，不向所述SeNB反馈RRC重配置结果。
  16. 一种演进型基站，其特征在于，包括：
    RRC重配置消息解析模块，用于当接收到SeNB的RRC重配置消息时，解析所述SeNB的RRC重配置消息；
    RRC重配置结果反馈模块，用于若解析出所述SeNB的RRC重配置消息中的参数配 置可接受，则向用户设备转发所述SeNB的RRC重配置消息，并在确定针对所述SeNB的RRC重配置成功后向所述SeNB反馈RRC重配置成功的消息；若解析出所述SeNB的RRC重配置消息中的参数配置不可接受，则向所述SeNB发送所述RRC重配置出现异常的消息。
  17. 根据权利要求16所述的演进型基站，其特征在于，RRC重配置结果反馈模块还用于：
    若解析出所述SeNB的RRC重配置消息可忽略，则不做任何处理或向所述SeNB发送所述SeNB的RRC重配置消息可忽略的通知消息。
  18. 一种演进型基站，其特征在于，包括：
    RRC重配置消息接收模块，用于接收SeNB的RRC重配置消息，所述SeNB的RRC重配置消息中携带第一RRC事务标识和SeNB的RRC重配置参数；
    RRC重配置消息发送模块，用于生成MeNB的RRC重配置消息并发送给用户设备，所述MeNB的RRC重配置消息中携带第二RRC事务标识和所述SeNB的RRC重配置参数；
    对应关系保存模块，用于保存所述第一RRC事务标识与第二RRC事务标识之间的对应关系；
    RRC重配置响应接收模块，用于接收所述用户设备返回的RRC重配置响应消息，所述RRC重配置响应消息中包括第二RRC事务标识和RRC重配置结果信息；
    RRC重配置响应发送模块，用于向SeNB发送RRC重配置响应消息，向SeNB发送的RRC重配置响应消息中包括所述第一RRC事务标识和所述RRC重配置结果信息。
PCT/CN2014/089687 2013-11-01 2014-10-28 演进型基站的重配置方法、用户设备及演进型基站 WO2015062476A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/033,345 US20160269241A1 (en) 2013-11-01 2014-10-28 Evolved node b reconfiguration method, user equipment and evolved node b
EP14858578.9A EP3065444B1 (en) 2013-11-01 2014-10-28 Evolved node b reconfiguration method, user equipment, and evolved node b

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310535521.2A CN104618927B (zh) 2013-11-01 2013-11-01 多演进型基站的重配置方法、用户设备及多演进型基站
CN201310535521.2 2013-11-01

Publications (1)

Publication Number Publication Date
WO2015062476A1 true WO2015062476A1 (zh) 2015-05-07

Family

ID=53003345

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/089687 WO2015062476A1 (zh) 2013-11-01 2014-10-28 演进型基站的重配置方法、用户设备及演进型基站

Country Status (4)

Country Link
US (1) US20160269241A1 (zh)
EP (1) EP3065444B1 (zh)
CN (1) CN104618927B (zh)
WO (1) WO2015062476A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2763784C2 (ru) * 2017-03-23 2022-01-11 Хуавей Текнолоджиз Ко., Лтд. Способ, устройство и система конфигурирования

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104936161B (zh) * 2014-03-18 2018-10-12 中国移动通信集团公司 一种参数配置处理方法、装置、终端及基站
KR102172469B1 (ko) * 2016-05-13 2020-10-30 주식회사 케이티 이종 무선 액세스 망 간의 연동 방법 및 그 장치

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102119554A (zh) * 2008-08-08 2011-07-06 交互数字专利控股公司 执行服务高速下行链路共享信道小区改变的方法和设备
CN102149146A (zh) * 2010-02-10 2011-08-10 中兴通讯股份有限公司 上行传输速率的控制方法和系统
CN102281633A (zh) * 2010-06-10 2011-12-14 华为技术有限公司 无线资源控制重配置处理方法和用户设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9100883B2 (en) * 2013-04-03 2015-08-04 Blackberry Limited Methods and systems for wireless communication in heterogeneous networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102119554A (zh) * 2008-08-08 2011-07-06 交互数字专利控股公司 执行服务高速下行链路共享信道小区改变的方法和设备
CN102149146A (zh) * 2010-02-10 2011-08-10 中兴通讯股份有限公司 上行传输速率的控制方法和系统
CN102281633A (zh) * 2010-06-10 2011-12-14 华为技术有限公司 无线资源控制重配置处理方法和用户设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3065444A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2763784C2 (ru) * 2017-03-23 2022-01-11 Хуавей Текнолоджиз Ко., Лтд. Способ, устройство и система конфигурирования
US11425779B2 (en) 2017-03-23 2022-08-23 Huawei Technologies Co., Ltd. Configuration method and apparatus, and system
US11950314B2 (en) 2017-03-23 2024-04-02 Huawei Technologies Co., Ltd. Configuration method and apparatus, and system

Also Published As

Publication number Publication date
US20160269241A1 (en) 2016-09-15
EP3065444A1 (en) 2016-09-07
EP3065444A4 (en) 2017-03-01
EP3065444B1 (en) 2019-07-10
CN104618927B (zh) 2019-04-19
CN104618927A (zh) 2015-05-13

Similar Documents

Publication Publication Date Title
JP6241556B2 (ja) 無線通信システムにおける電子機器及びモビリティ測定を行う方法
US10342066B2 (en) Method and apparatus for dual connectivity management
JP6661663B2 (ja) データ無線ベアラを再構成する方法及びユーザ装置
WO2018171398A1 (zh) QoS处理方法和设备
US11903051B2 (en) Network nodes and methods therein for enabling a switch between feeder links for an airbourne or orbital communication node in a non-terrestrial communications network
JP7210563B2 (ja) 複製送信の方法および装置
KR20180136862A (ko) 듀얼 rrc 시스템에서 이동성을 처리하는 방법 및 장치
JP6871408B2 (ja) 無線リソース構成方法および装置、ユーザ機器、ならびにネットワーク要素
CN104349389A (zh) 用于建立无线承载的方法和装置
US11202333B2 (en) Layer 2 processing method, central unit and distributed unit
KR20200043457A (ko) Rrc 재개/일시중단 시의 nr pdcp 보존을 위한 방법들 및 장치들
WO2019157985A1 (zh) 一种无线回传通信处理方法和相关设备
CN102215485A (zh) 多载波通信系统中保证多载波切换或重建安全性的方法
RU2741509C1 (ru) Контекст безопасности в системе беспроводной связи
WO2018059472A1 (zh) 终端能力协商方法、终端及基站
WO2022016473A1 (zh) 一种用于接入回传一体化iab系统中的通信方法和通信装置
EP3656175B1 (en) Apparatus for v2x-oriented local e2e path establishment and qos control
US20220174514A1 (en) Support for time sensitive communications with high reliability provided via network slicing and path diversity
CN109565728A (zh) 一种数据处理方法以及相关设备
US20190132226A1 (en) Data transmission method, device, and network system
WO2015062476A1 (zh) 演进型基站的重配置方法、用户设备及演进型基站
CN108810889A (zh) 通信方法、装置及系统
WO2020167644A1 (en) Secondary cell group failure in dual connectivity
WO2021026707A1 (zh) 一种去激活iab节点的方法及装置
US20190182116A1 (en) Configuration Method, Network Device, and User Equipment

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15033345

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014858578

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014858578

Country of ref document: EP