Patent Publication Number: US-2021185748-A1

Title: Multi-base station connection management method, user terminal and computer readable storage medium

Description:
This is a National Stage Application, filed under 35 U.S.C. 371, of International Patent Application No. PCT/CN2018/113309, filed on Nov. 1, 2018, which claims priority to Chinese patent application No. 201711059902.2 filed with the CNIPA on Nov. 1, 2017, contents of both of which are incorporated herein by reference in their entireties. 
    
    
     TECHNICAL FIELD 
     The present application relates to the field of network convergence, for example, to a multi-base station connection management method, a user equipment (UE) and a computer readable storage medium. 
     BACKGROUND 
     In a wireless communication network, a base station delivers measurement reconfiguration signaling to a UE through a cell and performs reporting configurations for a user equipment (UE) in a connected state. The UE performs air interface measurement according to these reporting configurations and sends a report of measurement results to the base station. 
     Each set of reporting configuration is a combination of one measurement object identity (measObjectId) and one reporting configuration identity (reportConfigId), and is identified by a unique measurement identity (measId). Each measObjectId corresponds to one measurement object, that is, a measurement frequency point at which the UE performs the air interface measurement. Each reportConfigId corresponds to one set of reporting configuration which defines criterion and format configurations of a measurement report. 
     A 3rd Generation Partnership Project (3GPP) 36.331 protocol defines that measObjectId, reportConfigId and measId are each non-multiplexable resources, that is, the measObjectId, reportConfigId and measId cannot be repeated in measurement delivered by the base station to the UE. In addition, the protocol also stipulates that contents identified by different measObjectIds or measIds cannot be repeated. If the measObjectId, reportConfigId and measId are repeated in the measurement delivered by the base station to the UE, or the contents identified by different measObjectIds or measIds are repeated, an abnormal measurement result or other abnormal behaviors such as re-establishment of the UE may be caused. 
     In the related art, the UE may be simultaneously connected to two or more base stations. These base stations may belong to a same communication network or different communication networks. One of these base stations serves as a master node (MN), and each of the other base stations serves as a secondary node (SN). In addition to basic measurement, the MN needs to deliver measurement for SN addition to the UE. The SN needs to deliver measurement for SN deletion and modification to the UE. Since there is no negotiation path between the MN and the SN, their independent measurement mechanisms will cause conflicts in the measObjectIds, reportConfigIds and measIds of different measurement received by a UE side, which will cause the abnormal measurement result or other abnormal behaviors of the UE. 
     SUMMARY 
     The following is a summary of the subject matter described herein in detail. This summary is not intended to limit the scope of the claims. 
     Embodiments of the present application provide a multi-base station connection management method, a user equipment and a computer readable storage medium, which can avoid a conflict between identities of different measurement received by a UE side due to independent measurement mechanisms of an MN and an SN. 
     An embodiment of the present application provides a multi-base station connection management method. The method includes: after receiving measurement reconfiguration signaling from a cell, extracting, by a terminal, a measurement parameter carried in the measurement reconfiguration signaling; calling a local measurement configuration list of the terminal and an identity mapping list corresponding to the cell, where the local measurement configuration list is used for recording a local measurement configuration parameter and a local identity corresponding to the local measurement configuration parameter, and the identity mapping list is used for recording a correspondence between a cell identity in the measurement reconfiguration signaling from the cell and a local identity reallocated by the terminal; processing the measurement parameter carried in the measurement reconfiguration signaling according to the local measurement configuration list of the terminal and the identity mapping list; sending connection reconfiguration complete signaling to the cell; and in response to determining that a measurement reporting condition is satisfied, sending measurement report signaling to the cell by using a measurement identity of the cell. 
     An embodiment of the present application provides a user equipment, including a processor, a memory and a communication bus. The communication bus is configured to implement connection communications between the processor and the memory. The processor is configured to perform at least one program stored in the memory to implement the multi-base station connection management method described above. 
     An embodiment of the present application further provides a computer readable storage medium, storing at least one program executable by at least one processor to implement the multi-base station connection management method described above. 
     An embodiment of the present application further provides a processor, which is configured to execute programs which, when executed, perform the multi-base station connection management method described above. 
     Other aspects can be understood after the drawings and the detailed description are read and understood. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIG. 1  is a flowchart of a multi-base station connection management method according to an embodiment of the present application; 
         FIG. 2  is a structural diagram of a multi-base station connection management device according to an embodiment of the present application; 
         FIG. 3  is a structural diagram of a user equipment according to an embodiment of the present application; 
         FIG. 4  is a schematic diagram of communication networking involved in an embodiment of the present application; 
         FIG. 5  is a flowchart of a multi-base station connection management method according to an embodiment of the present application; 
         FIG. 6  is a method flowchart in a case where measurement object identities conflict according to an embodiment of the present application; 
         FIG. 7  is a method flowchart in a case where measurement frequency points of measurement objects conflict according to an embodiment of the present application; 
         FIG. 8  is a method flowchart in a case where reporting configuration identities conflict according to an embodiment of the present application; 
         FIG. 9  is a method flowchart in a case where measurement identities conflict according to an embodiment of the present application; and 
         FIG. 10  is a method flowchart in a case where local identity resources are insufficient according to an embodiment of the present application. 
     
    
    
     DETAILED DESCRIPTION 
     Embodiments of the present application are described below in detail in conjunction with the drawings and specific embodiments. It is to be understood that the specific embodiments described herein are merely intended to explain the present application and not to limit the present application. 
     A measurement parameter carried in measurement reconfiguration signaling involved in the present application includes identities, such as a measurement object identity (measObjectId), a reporting configuration identity (reportConfigId) and a measurement identity (measId), and all parameters corresponding to the identities, such as a measurement frequency point, reporting configuration contents, and the measurement object identity and the reporting configuration identity associated with the measurement identity. 
     For ease of description, in the present application, the measurement object identity (measObjectId), the reporting configuration identity (reportConfigId), the measurement identity (measId) and the like carried in the measurement reconfiguration signaling sent by a cell to a user equipment are recorded as cell identities such as a cell measurement object identity, a cell reporting configuration identity and a cell measurement identity; and a measurement object identity (measObjectId), a reporting configuration identity (reportConfigId), a measurement identity (measId) and the like stored by the user equipment in a local measurement configuration list of a terminal are recorded as local identities such as a local measurement object identity, a local reporting configuration identity and a local measurement identity. 
     The local measurement configuration list of the terminal involved in the present application refers to a list for recording a local measurement configuration parameter and a local identity corresponding to the local measurement configuration parameter. In the present application, the local measurement configuration list of the terminal stores the measurement object identity (measObjectId), the reporting configuration identity (reportConfigId) and the measurement identity (measId). 
     A mapping list involved in the present application refers to a list for recording a correspondence between a cell identity in the measurement reconfiguration signaling from the cell and a local identity reallocated by the terminal. In the present application, in an example in which the user equipment is merely connected to two cells of an MN and an SN, that is, the UE accesses a primary secondary cell (Pscell) provided by the SN while accessing a primary cell (Pcell) provided by the MN, the mapping list is stored in the form of 6 lists, including a measurement object identity (measObjectId) mapping list, a reporting configuration identity (reportConfigId) mapping list and a measurement identity (measId) mapping list configured for the Pcell and a measurement object identity (measObjectId) mapping list, a reporting configuration identity (reportConfigId) mapping list and a measurement identity (measId) mapping list configured for the Pscell. 
     Referring to  FIG. 1 , a multi-base station connection management method according to an embodiment of the present application includes steps S 101  to S 105 , which can avoid a conflict between identities of different measurement received by a UE side due to independent measurement mechanisms of an MN and an SN. 
     In step S 101 , after receiving measurement reconfiguration signaling from a cell, a terminal extracts a measurement parameter carried in the measurement reconfiguration signaling. 
     In step S 102 , a local measurement configuration list of the terminal and an identity mapping list corresponding to the cell are called. The local measurement configuration list is used for recording a local measurement configuration parameter and a local identity corresponding to the local measurement configuration parameter, and the identity mapping list is used for recording a correspondence between a cell identity in the measurement reconfiguration signaling from the cell and a local identity reallocated by the terminal. 
     In step S 103 , the measurement parameter carried in the measurement reconfiguration signaling is processed according to the local measurement configuration list of the terminal and the identity mapping list. 
     In step S 104 , connection reconfiguration complete signaling is sent to the cell. 
     In step S 105 , in response to determining that a measurement reporting condition is satisfied, measurement report signaling is sent to the cell by using a measurement identity of the cell. 
     In some embodiments of the present application, in a case where the measurement parameter includes a cell measurement object identity of a measurement object to be deleted in the cell, step S 103  includes: checking whether a local measurement object identity reallocated to the cell measurement object identity exists in the identity mapping list; in response to existence of the local measurement object identity reallocated to the cell measurement object identity, taking the local measurement object identity as a key value, and in response to absence of the local measurement object identity reallocated to the cell measurement object identity, taking the cell measurement object identity as the key value; and deleting a measurement object corresponding to the key value from the local measurement configuration list of the terminal. 
     In some embodiments of the present application, in the case where the measurement parameter includes the cell measurement object identity of the measurement object to be deleted in the cell, step S 103  further includes: checking whether a local measurement object identity associated with another measurement exists as the key value according to the local measurement configuration list of the terminal; in response to existence of the local measurement object identity associated with the another measurement as the key value, not deleting the measurement object corresponding to the key value; and in response to absence of the local measurement object identity associated with the another measurement as the key value, deleting the measurement object corresponding to the key value. 
     In some embodiments of the present application, in a case where the measurement parameter includes a cell measurement object identity of a measurement object to be added in the cell, step S 103  includes: comparing the measurement object in the measurement parameter with a measurement object on which measurement is being performed locally in the local measurement configuration list of the terminal to check whether a measurement frequency point conflict or a measurement object identity conflict exists; in response to existence of the measurement frequency point conflict, replacing the cell measurement object identity with a local measurement object identity at a same frequency point, adding a correspondence between the cell measurement object identity and the local measurement object identity to the identity mapping list, and locally merging all configurations of two measurement objects; and in response to existence of the measurement object identity conflict, allocating a local measurement object identity which is unused to the cell measurement object identity, adding a correspondence between the cell measurement object identity and the local measurement object identity to the identity mapping list, and adding the measurement object to the local measurement configuration list of the terminal. 
     In some embodiments of the present application, in a case where the measurement parameter includes a cell reporting configuration identity of a reporting configuration to be deleted in the cell, step S 103  includes: checking whether a local reporting configuration identity reallocated to the cell reporting configuration identity exists in the identity mapping list; in response to existence of the local reporting configuration identity reallocated to the cell reporting configuration identity, taking the local reporting configuration identity as a key value, and in response to absence of the local reporting configuration identity reallocated to the cell reporting configuration identity, taking the cell reporting configuration identity as the key value; and deleting a reporting configuration corresponding to the key value from the local measurement configuration list of the terminal. 
     In some embodiments of the present application, in a case where the measurement parameter includes a cell reporting configuration identity of a reporting configuration to be added in the cell, step S 103  includes: comparing the reporting configuration in the measurement parameter with a reporting configuration corresponding to measurement which is being performed locally in the local measurement configuration list of the terminal to check whether a reporting configuration identity conflict exists; and in response to existence of the reporting configuration identity conflict, allocating a local reporting configuration identity which is unused to the cell reporting configuration identity, adding a correspondence between the cell reporting configuration identity and the local reporting configuration identity to the identity mapping list, and adding the reporting configuration to the local measurement configuration list of the terminal. 
     In some embodiments of the present application, in a case where the measurement parameter includes a cell measurement identity of measurement to be deleted in the cell, step S 103  includes: checking whether a local measurement identity reallocated to the cell measurement identity exists in the identity mapping list; in response to existence of the local measurement identity reallocated to the cell measurement identity, taking the local measurement identity as an index; in response to absence of the local measurement identity reallocated to the cell measurement identity, taking the cell measurement identity as the index; and deleting a combination of a measurement object identity and a reporting configuration identity, which are associated with the index, from the local measurement configuration list of the terminal. 
     In some embodiments of the present application, in a case where the measurement parameter includes a cell measurement identity of measurement to be added in the cell, step S 103  includes: comparing the measurement in the measurement parameter with measurement which is being performed locally in the local measurement configuration list of the terminal to check whether a measurement identity conflict exists, or comparing whether a combination of a measurement object identity and a reporting configuration identity, which are associated with a measurement identity, in the measurement parameter is identical to a combination of a measurement object identity and a reporting configuration identity, which are associated with a measurement identity of the measurement which is being performed locally; in response to existence of the measurement identity conflict or identical combinations, reallocating a local measurement identity which is unused to the cell measurement identity, and adding a correspondence between the cell measurement identity and the local measurement identity to the identity mapping list; and in response to existence of at least one of a reallocated local measurement object identity or a reallocated local reporting configuration identity associated with the cell measurement identity, replacing with the at least one of the reallocated cell measurement object identity or the reallocated cell reporting configuration identity, and adding the measurement to the local measurement configuration list of the terminal. 
     In some embodiments of the present application, step S 105  includes: performing local measurement and generating a measurement report; searching the identity mapping list for a cell measurement identity corresponding to a local measurement identity; and adding the cell measurement identity to the measurement report, and sending the measurement report to a cell corresponding to the cell measurement identity. 
     In some embodiments of the present application, the multi-base station connection management method shown in  FIG. 1  further includes: in response to existence of a conflict between any of a measurement identity, a reporting configuration identity or a measurement object identity in the measurement parameter and an identity list, determining whether an available local identity resource exists; in response to existence of the available local identity resource, allocating a local identity to a conflicting identity; and in response to absence of the available local identity resource, sending measurement reconfiguration invalid signaling to the cell. 
     As shown in  FIG. 2 , a multi-base station connection management device  2  according to an embodiment includes an extraction module  21 , a calling module  22 , a processing module  23 , a feedback module and a reporting module  25 . 
     The extraction module  21  is configured to: after receiving measurement reconfiguration signaling from a cell, extract a measurement parameter carried in the measurement reconfiguration signaling. 
     The calling module  22  is configured to call a local measurement configuration list of the terminal and an identity mapping list corresponding to the cell. The local measurement configuration list is used for recording a local measurement configuration parameter and a local identity corresponding to the local measurement configuration parameter, and the identity mapping list is used for recording a correspondence between a cell identity in the measurement reconfiguration signaling from the cell and a local identity reallocated by the terminal. 
     The processing module  23  is configured to process the measurement parameter carried in the measurement reconfiguration signaling according to the local measurement configuration list of the terminal and the identity mapping list. 
     The feedback module  24  is configured to send connection reconfiguration complete signaling to the cell. 
     The reporting module  25  is configured to: in response to determining that a measurement reporting condition is satisfied, send measurement report signaling to the cell by using a measurement identity of the cell. 
     As shown in  FIG. 3 , an embodiment of the present application provides a user equipment, including a processor  31 , a memory  32  and a communication bus  33 . The communication bus  33  is configured to implement connection communications between the processor  31  and the memory  32 . The processor  31  is configured to perform at least one program stored in the memory  32  to implement the method according to any one of the embodiments of the present application. 
     The present application is construed and described below in conjunction with examples. 
     In this embodiment, a network convergence scenario where 4G Long Term Evolution (LTE) and 5G New Radio Access Technology (NR) are converged is used as an example for description. 
     In a pure 4G or 5G networking scenario, a 4G LTE base station (i.e., an eNodeB) or a 5G NR base station (i.e., a gNodeB) performs reporting configurations for a user equipment (UE) in a radio resource control (RRC) connected state through RRC connection reconfiguration signaling, and the UE performs air interface measurement according to these reporting configurations and reports measurement results to the base station. A 3GPP 36.331 protocol defines that measObjectId, reportConfigId and measId are each non-multiplexable resources, that is, the measObjectId, reportConfigId and measId cannot be repeated in measurement delivered to the UE. In addition, the protocol also stipulates that contents corresponding to different measObjectIds or measIds cannot be repeated. If the measObjectId, reportConfigId and measId are repeated in the measurement delivered by the base station to the UE, or the contents corresponding to different measObjectIds or measIds are repeated, an abnormal behavior such as re-establishment will the UE may be caused. Moreover, an R12 protocol defines that a value range of each of three ids is 1 to 64. 
     In a scenario where a multi-connection technology with option3\3A\3X, option4 and option7\7A\7X architecture described in 3GPP 37.340 is used for a 4G and 5G network convergence, since there is no negotiation path between an MN and an SN, their independent measurement mechanisms might cause conflicts in the measObjectId, reportConfigId and measId of different measurement on a UE side and repeated contents corresponding to different measurement identifiers, which will cause the abnormal behavior such as re-establishment of the UE. 
     In this embodiment, a mapping list and an identity list are locally configured, and a case where measurement-related Id resources of different RRC connection entities conflict on the UE side in the multi-connection technology at a 4G and 5G network convergence stage is avoided based on the identity list and the mapping list. This has no impact on a base station side and does not require interactions of X2 interface messages between different stations to be increased. For the UE side, merely one set of measurement lists is practically measured, avoiding repeated measurement between different systems. The is implemented by a simple and efficient method. 
     In this embodiment, a local measurement configuration list of a terminal includes a measObjectList, a reportConfigList and a MeasIdList. 
     Networking involved in this embodiment is shown in  FIG. 4 . The UE accesses both a Pcell provided by the MN and a Pscell provided by the SN. 
     As shown in  FIG. 5 , a method according to this embodiment includes steps S 501  to S 508 . 
     In step S 501 , the UE configures an identity mapping list for the Pcell and the Pscell separately. 
     The UE is first connected to the Pcell provided by the MN and then accesses the Pscell provided by the SN. After accessing the Pscell, the UE maintains the identity mapping list for the Pcell and the Pscell locally (inside the UE) separately for recording a mapping relationship between an Id resource delivered through a corresponding cell by each of two different RRC connection entities, the MN and the SN, and an Id resource reallocated by the UE. The identity mapping list includes a measurement object identity (measObjectId) mapping list, a reporting configuration identity (reportConfigId) mapping list and a measurement identity (measId) mapping list configured for the Pcell, and a measurement object identity (measObjectId) mapping list, a reporting configuration identity (reportConfigId) mapping list and a measurement identity (measId) mapping list configured for the Pscell. 
     In step S 502 , the UE deletes a measurement object. 
     The UE receives measurement reconfiguration signaling from any RRC connection entity (the MN or the SN). If a measObjectToRemoveList cell exists in the reconfiguration signaling, the UE searches a measObjectId mapping list of the RRC connection entity for a reallocated measObjectId corresponding to the measObjectToRemoveList cell. 
     If the reallocated measObjectId corresponding to the measObjectToRemoveList cell exists, the reallocated measObjectId (that is, a local measObjectId, which is the same hereinafter and will not be described again) is used a key value. If the reallocated measObjectId corresponding to the measObjectToRemoveList cell does not exist, an original measObjectId (that is, a cell measObjectId, which is the same hereinafter and will not be described again) in the signaling is used as the key value. It is checked whether a measObjectId associated with another measurement exists as the key value in a local measIdList. 
     If the measObjectId associated with the another measurement exists as the key value in the local measIdList, the measurement object is not deleted this time. If the measObjectId associated with the another measurement does not exist as the key value in the local measIdList, a local measurement object list (measObjectList) is searched for a measurement object whose measObjectId is identical to the key value, and the measurement object is deleted. 
     In step S 503 , the UE adds a measurement object. 
     If a measObjectToAddModList exists in the measurement reconfiguration signaling, a measObjectToAddModList cell is compared with a measurement object in the local measObjectList to check whether a measurement frequency point conflict or a measObjectId conflict exists. 
     If the measurement frequency point conflict exists, a measObjectId of the measurement object is replaced with a measObjectId of a measurement object which is at a same frequency point and already exists in the measObjectList, and all configurations of the measurement objects are merged. 
     If the measObjectId conflict exists, a local measObjectId which is unused is allocated to the measurement object. A correspondence between an original measObjectId and the reallocated measObjectId is recorded in the measObjectId mapping list of the corresponding RRC connection entity. 
     The UE adds the measurement object to the local measObjectList. 
     In step S 504 , the UE deletes a reporting configuration. 
     If a reportConfigToRemoveList exists in the measurement reconfiguration signaling, the reportConfigId mapping list of the corresponding RRC connection entity is searched for a reallocated reportConfigId corresponding to the reportConfigToRemoveList. 
     If the reallocated reportConfigId corresponding to the reportConfigToRemoveList exists in the reportConfigId mapping list of the corresponding RRC connection entity, the reallocated reportConfigId is used as a key value. If the reallocated reportConfigId corresponding to the reportConfigToRemoveList does not exists in the reportConfigId mapping list of the corresponding RRC connection entity, an original reportConfigId in the signaling is used as the key value. It is checked whether a reportConfigId associated with another measurement exists as the key value in the local measIdList. 
     If the reportConfigId associated with the another measurement exists as the key value in the local measIdList, the reporting configuration is not deleted this time. If the reportConfigId associated with the another measurement does not exist as the key value in the local measIdList, a local reportConfigList is searched for a reporting configuration whose reportConfigID is identical to the key value, and the reporting configuration is deleted. 
     In step S 505 , the UE adds a reporting configuration. 
     If a reportConfigToAddModList exists in the measurement reconfiguration signaling, the UE compares a reportConfigToAddModList cell with a reporting configuration in the local reportConfigList to check whether a reportConfigId conflict exists. 
     If the reportConfigId conflict exists, a local reportConfigId which is unused is allocated to the reporting configuration. A correspondence between the original reportConfigId and the reallocated reportConfigId is recorded in the reportConfigId mapping list of the corresponding RRC connection entity. 
     The reporting configuration is added to the local reportConfigList. 
     In step S 506 , the UE deletes measurement. 
     If a measIdToRemoveList exists in the measurement reconfiguration signaling, the measId mapping list of the corresponding RRC connection entity is searched for a reallocated measId corresponding to the measIdToRemoveList. 
     If the reallocated measId corresponding to the measIdToRemoveList exists in the measId mapping list of the corresponding RRC connection entity, a record corresponding to the reallocated measId is deleted from the local measIdList. 
     If the reallocated measId corresponding to the measIdToRemoveList does not exist in the measId mapping list of the corresponding RRC connection entity, a record corresponding to an original measId is deleted from the local measIdList and a reporting configuration with a reportConfigId associated with the original measId as a key value is deleted from the reportConfigList. 
     In step S 507 , the UE adds measurement. 
     If a measIdToAddModList exists in the measurement reconfiguration signaling, the UE compares a measIdToAddModList cell with a measId in the local measIdList to determine whether a conflict exists, or the UE compares a combination of a measObjectId and a reportConfigId, which are associated with a measId to be added this time in the measIdToAddModList cell, with a combination associated with an existing measId in the local measIdList to determine whether they are completely identical. 
     If the measIdToAddModList cell conflicts with the measId in the local measIdList, or the combination of the measObjectId and the reportConfigId, which are associated with the measId to be added this time in the measIdToAddModList cell, is completely identical to the combination associated with the existing measId in the local measIdList, a local measId which is unused is allocated to the measurement. A correspondence between an original measId and the reallocated measId is recorded in the measId mapping list of the corresponding RRC connection entity. 
     If a reallocated measObjectId and a reallocated reportConfigId associated with the measId exist, the UE replaces with the reallocated measObjectId and the reallocated reportConfigId. The UE adds measId information to the local measIdList. 
     In step S 508 , the UE reports a measurement report. 
     When an air interface satisfies a measurement condition, the UE sends the measurement report to the corresponding RRC connection entity. It is checked whether a measId corresponding to the measurement in the measIdList is the reallocated measId in the measId mapping list of the corresponding RRC connection entity. 
     If the measId is reallocated by the UE before the measurement, an original measId corresponding to the reallocated measId in the mapping list is filled into a measId cell in measurementReport signaling, and the measurementReport signaling is sent to the corresponding RRC connection entity. 
     This embodiment will be described below in conjunction with  5  scenarios. 
     In scenario 1, measurement object Ids in measurement reconfiguration signaling delivered by different RRC connection entities conflict. As shown in  FIG. 6 , the method includes steps S 601  to S 609 . 
     In step S 601 , a Pcell delivers signaling for adding measurement  1  to a UE. 
     After the UE accesses the Pcell, the Pcell delivers measurement with measId 1  to the UE through measurement reconfiguration signaling (delivery manners are various which are the same hereinafter and will not be described again), where the measurement with measId 1  is associated with a measurement object with measObjectId 1  and a reporting configuration with reportConfigId 1 . The measurement object with measObjectId of 1 has a frequency point f 1 . 
     In step S 602 , the UE adds measurement  1 . 
     After receiving the measurement reconfiguration signaling, the UE stores the measurement object and its identity, the reporting configuration and its identity, and the measurement identity, etc. to a measObjectList, a reportConfigList and a MeasIdList, respectively. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1 ; and the MeasIdList includes MeasId 1  associated with a measurement identity combination of measObjectId 1  and reportConfigId 1 . 
     In step S 603 , the UE sends reconfiguration complete signaling to the Pcell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pcell to notify that measurement addition is completed. 
     In step S 604 , a Pscell delivers signaling for adding measurement  2  to the UE. 
     After an SN addition success, the Pscell delivers measurement with MeasId 2  to the UE, where the measurement with MeasId 2  is associated with a measurement object with measObjectId 1  and a reporting configuration with reportConfigId 2 . The measurement object with measObjectId 1  has a frequency point f 2 . 
     In step S 605 , the UE adds measurement  2 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE compares the measurement object in a measObjectToAddModList cell with a measurement object in a local measObjectList and finds that a measObjectId of a local measurement frequency point f 1  and a measObjectId of a measurement frequency point f 2  in the cell are both 1, which cannot uniquely identify one measurement object. The UE sequentially finds a first local Id  2  which is unused within a protocol value range of the measObjectId. A correspondence between the original measObjectId 1  and the reallocated measObjectId 2  is recorded in a measObjectId mapping list of an RRC connection entity of the Pscell. A measObjectId of the measurement object is changed from 1 to 2 and measObjectId 2  is added to the measObjectList. The correspondence between the original measObjectId 1  and the reallocated measObjectId 2  is recorded in the measObjectId mapping list of the RRC connection entity of the Pscell. 
     The UE compares the reporting configuration in a reportConfigToAddModList cell with a reportConfigId in a local reportConfigList, finds no conflict, and adds the reporting configuration with reportConfigId 2  to the reportConfigList. 
     The UE replaces an associated measObjectId  1  in a measIdToAddMod cell in a measIdToAddModList with the reallocated  2 , maintains the reportConfigId and the measId unchanged, and stores in the measIdList. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1  and measObjectId 2 : frequency point  2 . The reportConfigList includes reportConfigId 1  and reportConfigId 2 . The MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 , and MeasId 2  associated with a measurement identity combination of measObjectId 2  and reportConfigId 2 . The measObjectId mapping list of the Pscell includes a correspondence between a Pscell identity  1  and a local identity  2 . 
     In step S 606 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement addition is completed. 
     In step S 607 , the Pscell delivers signaling for deleting measurement  2  to the UE. 
     The Pscell delivers RRC connection reconfiguration signaling to the UE to delete the measurement with measId 2 . 
     In step S 608 , the UE deletes measurement  2 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE finds that the original measObjectId 1  in measObjectToRemoveList signaling corresponds to measObjectId 2  reallocated by the UE in the measObjectId mapping list of the RRC connection entity of the Pscell. It is checked that no measObjectId associated with another measurement is 2 in a local measIdList. The measurement object with measObjectId 2  is deleted from the local measObjectList. The correspondence between the original measObjectId 1  and the reallocated measObjectId 2  is deleted from the measObjectId mapping list of the RRC connection entity of the Pscell. 
     The UE fails to find a same original reportConfigId in a reportConfigId mapping list of the RRC connection entity of the Pscell matching with the original reportConfigId 2  in reportConfigToRemoveList signaling. It is checked that no reportConfigId associated with another measurement is 2 in the local measIdList. The reporting configuration with reportConfigId 2  is deleted from the local reportConfigList. 
     The UE fails to find a same original measId in a measId mapping list of the RRC connection entity of the Pscell matching with the original measId 2  in measIdToRemoveList signaling. A measurement item with measId 2  is deleted from the local measIdList. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1 ; the MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 ; and the measObjectId mapping list of the Pscell is void. 
     In step S 609 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement deletion is completed. 
     In scenario 2, measurement frequency points of measurement objects in measurement reconfiguration signaling delivered by different RRC connection entities conflict. As shown in  FIG. 7 , the method includes steps S 701  to S 709 . 
     In step S 701 , a Pcell delivers signaling for adding measurement  1  to a UE. 
     After the UE access the Pcell, the Pcell delivers measurement with MeasId 1  to the UE, where the measurement with MeasId 1  is associated with a measurement object with measObjectId 1  and a reporting configuration with reportConfigId 1 . The measurement object with measObjectId 1  has a frequency point f 1 . 
     In step S 702 , the UE adds measurement  1 . 
     After receiving measurement reconfiguration signaling, the UE stores the measurement object, the reporting configuration and measurement Id information to a measObjectList, a reportConfigList and a measIdList, respectively. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1 ; the MeasIdList includes MeasId 1  associated with a measurement identity combination of measObjectId 1  and reportConfigId 1 . 
     In step S 703 , the UE sends reconfiguration complete signaling to the Pcell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pcell to notify that measurement addition is completed. 
     In step S 704 , a Pscell delivers signaling for adding measurement  2  to the UE. 
     After an SN addition success, the Pscell delivers measurement with measId 2  to the UE, where the measurement with measId 2  is associated with a measurement object with measObjectId 2  and a reporting configuration with reportConfigId 2 . The measurement object with measObjectId 2  also has the frequency point f 1 . 
     In step S 705 , the UE adds measurement  2 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE compares the measurement object in a measObjectToAddModList cell with a measurement object in a local measObjectList and finds that a local measurement object with measObjectId 1  and the measurement object with measObjectId 2  in the cell both have the measurement frequency point f 1 , which breaches protocol stipulations. 
     The UE does not add the measurement object to the measObjectList, and this measurement uses the local measurement object with measObjectId 1 . 
     A correspondence between an original measObjectId 2  and the reallocated measObjectId 1  is recorded in a measObjectId mapping list of an RRC connection entity of the Pscell. 
     The UE adds the reporting configuration with reportConfigId 2  in a reportConfigToAddModList cell to the reportConfigList. 
     The UE replaces a measObjectId  2  in a measIdToAddMod cell in a measIdToAddModList with  1  and maintains the reportConfigId and the measId unchanged, which are stored in the measIdList. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1  and reportConfigId 2 ; the MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 , and MeasId 2  associated with a measurement identity combination of measObjectId 1  and reportConfigId 2 ; and the measObjectId mapping list of the Pscell includes a correspondence between a Pscell identity  1  and a local identity  2 . 
     In step S 706 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement addition is completed. 
     In step S 707 , the Pscell delivers signaling for deleting measurement  2  to the UE. 
     The Pscell delivers RRC connection reconfiguration signaling to the UE to delete the measurement with measId 2 . 
     In step S 708 , the UE deletes measurement  2 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE finds that the original measObjectId 2  in measObjectToRemoveList signaling corresponds to measObjectId 1  reallocated by the UE in the measObjectId mapping list of the RRC connection entity of the Pscell. It is checked that the measurement with MeasId 1  is associated with measObjectId 1  in a local measIdList. No deletion operation is performed on the local measObjectList. The correspondence between the original measObjectId 2  and the reallocated measObjectId 1  is deleted from the measObjectId mapping list of the RRC connection entity of the Pscell. 
     The UE fails to find a same original reportConfigId in a reportConfigId mapping list of the RRC connection entity of the Pscell matching with the original reportConfigId 2  in reportConfigToRemoveList signaling. It is checked that no reportConfigId associated with another measurement is 2 in the local measIdList. The reporting configuration with reportConfigId 2  is deleted from a local reportConfigList. 
     The UE fails to find a same original measId in a measId mapping list of the RRC connection entity of the Pscell matching with the original measId 2  in measIdToRemoveList signaling. A measurement item with measId 2  is deleted from the local measIdList. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 . The reportConfigList includes reportConfigId 1 . The MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 . The measObjectId mapping list of the Pscell is void. 
     In step S 709 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement deletion is completed. 
     In scenario 3, reporting configuration Ids in measurement reconfiguration signaling delivered by different RRC connection entities conflict. As shown in  FIG. 8 , the method includes steps S 801  to S 809 . 
     In step S 801 , a Pcell delivers signaling for adding measurement  1  to a UE. 
     After the UE access the Pcell, the Pcell delivers measurement with MeasId 1  to the UE, where the measurement with MeasId 1  is associated with a measurement object with measObjectId 1  and a reporting configuration with reportConfigId 1 . The measurement object with measObjectId 1  has a frequency point f 1 . 
     In step S 802 , the UE adds measurement  1 . 
     After receiving measurement reconfiguration signaling, the UE stores the measurement object, the reporting configuration and measurement Id information to a measObjectList, a reportConfigList and a MeasIdList, respectively. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1 ; and the MeasIdList includes MeasId 1  associated with a measurement identity combination of measObjectId 1  and reportConfigId 1 . 
     In step S 803 , the UE sends reconfiguration complete signaling to the Pcell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pcell to notify that measurement addition is completed. 
     In step S 804 , a Pscell delivers signaling for adding measurement  2  to the UE. 
     After an SN addition success, the Pscell delivers measurement with measId 2  to the UE, where the measurement with measId 2  is associated with a measurement object with measObjectId 2  and a reporting configuration with reportConfigId 1 . The measurement object with measObjectId 2  has a frequency point f 2 . 
     In step S 805 , the UE adds measurement  2 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE compares the measurement object in a measObjectToAddModList cell with a measurement object in a local measObjectList and finds no conflict. The UE adds the measurement object to the measObjectList. 
     The UE compares the reporting configuration in a reportConfigToAddModList cell with a reportConfigId in a local reportConfigList and finds that the reporting configuration with reportConfigId 1  already exists locally. A reportConfigId of value 1 cannot uniquely identify one reporting configuration. 
     The UE sequentially finds a first local Id  2  which is unused within a protocol value range of 1 to 64 of the reportConfigId. The UE changes a reportConfigId of the reporting configuration in the reportConfigToAddModList cell from 1 to 2, and adds the reporting configuration to the reportConfigList. A correspondence between the original reportConfigId 1  and the reallocated reportConfigId 2  is recorded in a reportConfigId mapping list of the RRC connection entity of the Pscell. A reportConfigId  1  in a measIdToAddMod cell in a measIdToAddModList is replaced with  2 , and the measObjectId and the measId are maintained unchanged, which are stored in the measIdList. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1  and measObjectId 2 : frequency point  2 ; the reportConfigList includes reportConfigId 1  and reportConfigId 2 ; the MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 , and MeasId 2  associated with a measurement identity combination of measObjectId 2  and reportConfigId 2 ; and the reportConfigId mapping list of the Pscell includes a correspondence between a Pscell identity  1  and a local identity  2 . 
     In step S 806 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement addition is completed. 
     In step S 807 , the Pscell delivers signaling for deleting measurement  2  to the UE. 
     The Pscell delivers RRC connection reconfiguration signaling to the UE to delete the measurement with measId 2 . 
     In step S 808 , the UE deletes measurement  2 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE fails to find a same original measObjectId in the measObjectId mapping list of the RRC connection entity of the Pscell matching with the original measObjectId 2  in measObjectToRemoveList signaling. It is checked that no measObjectId associated with another measurement is 2 in a local measIdList. The measurement object with measObjectId 2  is deleted from the local measObjectList. 
     The UE finds that the original reportConfigId 1  in reportConfigToRemoveList signaling corresponds to reportConfigId 2  reallocated by the UE in the reportConfigId mapping list of the RRC connection entity of the Pscell. It is checked that no reportConfigId associated with another measurement is 2 in the local measIdList. The reporting configuration with reportConfigId 2  is deleted from the local reportConfigList. The correspondence between the original reportConfigId 1  and the reallocated reportConfigId 2  is deleted from the reportConfigId mapping list of the RRC connection entity of the Pscell. 
     The UE fails to find a same original measId in a measId mapping list of the RRC connection entity of the Pscell matching with the original measId 2  in measIdToRemoveList signaling. A measurement item with measId 2  is deleted from the local measIdList. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1 ; the MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 ; and the reportConfigId mapping list of the Pscell is void. 
     In step S 809 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement deletion is completed. 
     In scenario 4, measurement Ids in measurement reconfiguration signaling delivered by different RRC connection entities conflict. As shown in  FIG. 9 , the method includes steps S 901  to S 910 . 
     In step S 901 , a Pcell delivers signaling for adding measurement  1  to a UE. 
     After the UE access the Pcell, the Pcell delivers measurement with measId 1  to the UE, where the measurement with measId 1  is associated with a measurement object with measObjectId 1  and a reporting configuration with reportConfigId 1 . The measurement object with measObjectId 1  has a frequency point f 1 . 
     In step S 902 , the UE adds measurement  1 . 
     After receiving measurement reconfiguration signaling, the UE stores the measurement object, the reporting configuration and measurement Id information to a measObjectList, a reportConfigList and a MeasIdList, respectively. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1 ; and the MeasIdList includes MeasId 1  associated with a measurement identity combination of measObjectId 1  and reportConfigId 1 . 
     In step S 903 , the UE sends reconfiguration complete signaling to the Pcell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pcell to notify that measurement addition is completed. 
     In step S 904 , a Pscell delivers signaling for adding measurement  1  to the UE. 
     After an SN addition success, the Pscell delivers measurement with measId 1  to the UE, where the measurement with measId 1  is associated with a measurement object with measObjectId 2  and a reporting configuration with reportConfigId 2 . The measurement object with measObjectId 2  has a frequency point f 2 . 
     In step S 905 , the UE adds measurement  1 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE compares the measurement object in a measObjectToAddModList cell with a measurement object in a local measObjectList and finds no conflict. The UE adds the measurement object to the measObjectList. 
     The UE compares the reporting configuration in a reportConfigToAddModList cell with a reportConfigId in a local reportConfigList, finds no conflict, and adds the reporting configuration to the reportConfigList. 
     The UE compares a measIdToAddMod cell in a measIdToAddModList with a local measIdList, and finds that a measurement identity combination with measId 1  already exists locally. A measId of value 1 cannot uniquely identify one measurement identity combination. 
     The UE sequentially finds a first local Id  2  which is unused within a protocol value range of 1 to 64 of the measId. A measId in the measIdToAddMod cell in the measIdToAddModList is changed from 1 to 2, and the measObjectId and the reportConfigId are maintained unchanged, which are stored in the measIdList. A correspondence between the original measId 1  and the reallocated measId 2  is recorded in a measId mapping list of an RRC connection entity of the Pscell. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1  and measObjectId 2 : 
     frequency point  2 ; the reportConfigList includes reportConfigId 1  and reportConfigId 2 ; the MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 , and MeasId 2  associated with a measurement identity combination of measObjectId 2  and reportConfigId 2 ; and the MeasId mapping list of the Pscell includes a correspondence between a Pscell identity  1  and a local identity  2 . 
     In step S 906 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement addition is completed. 
     In step S 907 , the UE sends measurement report signaling to the Pscell. 
     MeasId 2  in the MeasIdList satisfies a measurement reporting condition. After the UE acquires a measurement result of a measurement item associated with a local measId 2  through measurement, the measurement result is filled in the measurement report signaling of an RRC connection, the measId mapping list of the RRC connection entity of the Pscell is searched for the corresponding original measId 1 , and a measId cell in the measurement report signaling is filled in with  1 . The measurement report signaling is sent to the Pscell. 
     In step S 908 , the Pscell delivers signaling for deleting measurement  1  to the UE. 
     The Pscell delivers RRC connection reconfiguration signaling to the UE to delete the measurement with measId 1 . 
     In step S 909 , the UE deletes measurement  1 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE fails to find a same original measObjectId in the measObjectId mapping list of the RRC connection entity of the Pscell matching with the original measObjectId 2  in measObjectToRemoveList signaling. It is checked that no measObjectId associated with another measurement is 2 in the local measIdList. 
     The measurement object with measObjectId 2  is deleted from the local measObjectList. 
     The UE fails to find a same original reportConfigId in a reportConfigId mapping list of the RRC connection entity of the Pscell matching with the original reportConfigId 2  in reportConfigToRemoveList signaling. It is checked that no reportConfigId associated with another measurement is 2 in the local measIdList. The reporting configuration with reportConfigId 2  is deleted from the local reportConfigList. 
     The UE finds that the original measId 1  in measIdToRemoveList signaling corresponds to measId 2  reallocated by the UE in the measId mapping list of the RRC connection entity of the Pscell. A measurement item with measId 2  is deleted from the local measIdList. The correspondence between the original measId 1  and the reallocated measId 2  is deleted from the measId mapping list of the RRC connection entity of the Pscell. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 ; the reportConfigList includes reportConfigId 1 ; the MeasIdList includes MeasId 1  associated with the measurement identity combination of measObjectId 1  and reportConfigId 1 ; and the MeasId mapping list of the Pscell is void. 
     In step S 910 , the UE sends reconfiguration complete signaling to the Pscell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pscell to notify that measurement deletion is completed. 
     In scenario 5, after Ids of different RRC connection entities conflict, a UE has no allocable Id resources. As shown in  FIG. 10 , the method includes steps S 1001  to S 1007 . 
     In step S 1001 , a Pcell delivers signaling for adding measurement  1  to  64  to the UE. 
     After the UE access the Pcell, the Pcell delivers 64 measurements with measIds  1  to  64  to the UE, where the measurements with measIds  1  to  64  are associated with measurement objects with measObjectIds  1  to  64  and reporting configurations with reportConfigIds  1  to  64 , respectively. The measurement objects with measObjectIds  1  to  64  have frequency point f 1  to f 64 . 
     In step S 1002 , the UE adds measurements  1  to  64 . 
     After receiving measurement reconfiguration signaling, the UE stores the measurement objects, the reporting configurations and measurement Id information to a measObjectList, a reportConfigList and a measIdList, respectively. 
     At this time, the measObjectList includes measObjectId 1 : frequency point  1 , . . . , measObjectIdi: frequency point i, . . . , and measObjectId 64 : frequency point  64 . The reportConfigList includes reportConfigId 1 , . . . , reportConfigIdi, . . . , and reportConfigId 64 ; the MeasIdList includes MeasId 1  associated with a measurement identity combination of measObjectIdi and reportConfigId 1 , . . . , MeasIdi associated with a measurement identity combination of measObjectIdi and reportConfigIdi, . . . , and MeasId 64  associated with a measurement identity combination of measObjectId 64  and reportConfigId 64 . 
     In step S 1003 , the UE sends reconfiguration complete signaling to the Pcell. 
     The UE sends RRC connection reconfiguration complete signaling to the Pcell to notify that measurement addition is completed. 
     In step S 1004 , a Pscell delivers signaling for adding measurement  2  to the UE. 
     After an SN addition success, the Pscell delivers measurement with measId 2  to the UE, where the measurement with measId 2  is associated with a measurement object with measObjectIdi and a reporting configuration with reportConfigId 2 . The measurement object with measObjectId 1  has a frequency point f 65 . 
     In step S 1005 , the UE fails to add measurement  2 . 
     After receiving measurement reconfiguration signaling from the Pscell, the UE compares the measurement object in a measObjectToAddModList cell with a measurement object in a local measObjectList and finds that a measObjectId of a local measurement frequency point f 1  and a measObjectId of a measurement frequency point f 65  in the cell are both 1, which cannot uniquely identify one measurement object. 
     The UE sequentially finds a local Id which is unused within a protocol value range of 1 to 64 of the measObjectId, and finds that there are no available Id resources. The measurement object is not added to the measObjectList. 
     In step S 1006 , the UE sends invalid reconfiguration signaling to the Pscell. 
     The UE sends invalid RRC measurement reconfiguration signaling to the Pscell. 
     In step S 1007 , the Pscell invalidates measurement  2 . 
     After the Pscell receives invalid RRC connection reconfiguration signaling, measurement  2  does not take effect on a cell side. 
     The present application further provides a computer readable storage medium, storing at least one program which is executed to implement all methods provided by the present application. 
     According to the multi-base station connection management method, the user equipment and the computer readable storage medium provided by the embodiments of the present application, after receiving the measurement reconfiguration signaling from the cell, the user equipment calls the local measurement configuration list of the terminal and the identity mapping list corresponding to the cell, and processes the measurement parameter carried in the measurement reconfiguration signaling. In this way, even if a measurement parameter received this time conflicts with a measurement parameter of measurement which is being performed by the user equipment, the conflict can be solved according to the local measurement configuration list of the terminal and the identity mapping list corresponding to the cell, achieving detection on a user equipment side of a conflict between identities of measurement delivered by different cells and reallocation and mapping of conflicting identities, avoiding a conflict between identities of different measurement received by the UE side, the abnormal measurement result or other abnormal behaviors due to the conflict between identities of different measurement, and the conflict between identities of different measurement received by the UE side due to independent measurement mechanisms of the MN and the SN in the related art, and improving user experience. 
     Each of the modules or the steps in the above-mentioned embodiments of the present application may be implemented by a general-purpose computing device. They may be concentrated on a single computing device or distributed over a network composed of multiple computing devices. For example, the modules or the steps may be implemented by program codes executable by the computing device, so that the modules or the steps may be stored in a computer storage medium such as a read only memory/random access memory (ROM/RAM), a magnetic disk and an optical disk and executed by the computing device. In some circumstances, the illustrated or described steps may be performed in sequences different from those described herein, or the modules or the steps may be made into various integrated circuit modules separately, or multiple modules or steps therein may be made into a single integrated circuit module for implementation. Therefore, the present application is not limited to any specific combination of hardware and software.