Managing primary cell group configurations

Abstract

Examples of the present disclosure relate to managing primary cell group (MCG) configuration during PSCell (Primary Secondary Cell) changes. In an example of the present disclosure, a user equipment includes means for receiving at least one configuration table from a master node. The at least one configuration table notifies the user equipment whether the MCG configuration between different PSCells is changed or not. The user equipment further comprises means for performing a PSCell change from the source PSCell to the target PSCell and applying the MCG configuration to the target PSCell based on the at least one configuration table.

Description

Technical Field

[0001] Examples of the present disclosure relate to managing Master Cell Group (MCG) configuration. Some relate to managing Master Cell Group (MCG) configuration during PSCell (primary secondary cell) change. Background Art

[0002] In New Radio - Dual Connectivity (NR-DC), a user equipment (UE) is connected to a primary node (MN) and a secondary node (SN) simultaneously. Both MN and SN can be associated with multiple cells or carriers. Multiple cells or carriers can be referred to as a primary cell group (MCG) and a secondary cell group (SCG). Each group has one primary cell that carries a physical uplink control channel (PUCCH) and can have one or more secondary cells. The primary cell of an MCG is a PCell and the primary cell of a secondary cell is a PSCell. The corresponding cell group can change during the switching process. Summary of the invention

[0003] According to various but not necessarily all examples of the present disclosure, there is provided a user equipment, including components for:

[0004] receiving at least one configuration table from the master node, where the at least one configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and

[0005] Based on at least one configuration table, a PSCell change is performed from a source PSCell to a target PSCell and the MCG configuration is applied to the target PSCell.

[0006] When there is a PSCell change from a source PSCell to a target PSCell, the user equipment uses at least one received configuration table to determine whether there is a change in the MCG configuration, and applies the change if the configuration table indicates that there is a change in the MCG configuration, or maintains the MCG configuration for the source PSCell if the configuration table indicates that there is no change.

[0007] The at least one configuration table includes an MCG bearer configuration table, the MCG bearer configuration table includes MCG bearer configuration information, and the MCG bearer configuration information includes bearers that can be unloaded from the secondary cell group SCG when a change from a source PSCell to a target PSCell is performed.

[0008] The user equipment uses the information in the at least one configuration table to determine the difference between the MCG configuration for the target PSCell and the MCG configuration for the source PSCell.

[0009] The user equipment determines whether remapping of the MCG configuration is required based on whether a difference between the MCG configuration for the target PSCell and the MCG configuration for the source PSCell is determined.

[0010] The at least one configuration table includes a configuration table for each cell group, and the configuration table indicates whether the mapping identifiers used for the bearers within the cell group are the same after the PSCell changes.

[0011] According to various but not necessarily all examples of the present disclosure, there is provided a user equipment as herein, wherein the configuration table for each cell group includes at least one of the following:

[0012] MCG configuration;

[0013] SCG configuration;

[0014] MCG and SCG configurations.

[0015] In some examples, the at least one configuration table includes a configuration table that includes both configuration information for an SCG bearer and configuration information for an MCG bearer.

[0016] In some examples, at least one configuration table includes at least one of the following:

[0017] Radio link control parameters;

[0018] Packet Data Convergence Protocol parameters.

[0019] In some examples, the at least one configuration table is received in a radio resource control message.

[0020] According to various but not necessarily all examples of the present disclosure, there is provided a method comprising:

[0021] receiving at least one configuration table from the master node, where the at least one configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and

[0022] Based on at least one configuration table, a PSCell change is performed from a source PSCell to a target PSCell and a state transfer MCG configuration is applied to the state transfer target PSCell.

[0023] According to various but not necessarily all examples of the present disclosure, there is provided a computer program, the computer program comprising program instructions, which when executed by a user device, causes the user device to at least perform:

[0024] Receive at least one configuration table from the master node, wherein the state transfer at least one configuration table notifies the state transfer user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and

[0025] Based on the state transfer at least one configuration table, a PSCell change is performed from a source PSCell to a target PSCell and the state transfer MCG configuration is applied to the state transfer target PSCell.

[0026] According to various but not necessarily all examples of the present disclosure, there is provided a master node, including components for:

[0027] Requesting configuration information from one or more candidate target secondary nodes;

[0028] receiving requested state transfer configuration information from one or more candidate target secondary nodes for state transfer; and

[0029] Based on the requested state transfer configuration information, at least one configuration table is transmitted to the user equipment, and the state transfer configuration table notifies the state transfer user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

[0030] According to various but not necessarily all examples of the present disclosure, there is provided a method comprising:

[0031] Requesting configuration information from one or more candidate target secondary nodes;

[0032] receiving requested state transfer configuration information from one or more candidate target secondary nodes for state transfer; and

[0033] Based on the requested state transfer configuration information, at least one configuration table is transmitted to the user equipment, and the state transfer configuration table notifies the state transfer user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

[0034] According to various but not necessarily all examples of the present disclosure, there is provided a computer program comprising program instructions, the state transfer program instructions, when executed by a master node, causing the state transfer master node to at least execute:

[0035] Requesting configuration information from one or more candidate target secondary nodes;

[0036] receiving requested state transfer configuration information from one or more candidate target secondary nodes for state transfer; and

[0037] Based on the requested state transfer configuration information, at least one configuration table is transmitted to the user equipment, and the state transfer configuration table notifies the state transfer user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

[0038] Although the above examples and optional features of the present disclosure are described separately, it should be understood that their provisions in all possible combinations and arrangements are included in the present disclosure. It should be understood that various examples of the present disclosure may include any or all features described with respect to other examples of the present disclosure, and vice versa. In addition, it should be understood that any one or more or all features of any combination may be implemented / included / executable by devices, methods and / or computer program instructions as needed and appropriate. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Some examples will now be described with reference to the accompanying drawings, in which:

[0040] Figure 1 An example network is shown;

[0041] FIG. 2A to FIG. 2D Example PSCell changes are shown;

[0042] Figure 3A and 3B An example method is shown;

[0043] Figure 4 An example signaling procedure is shown;

[0044] Figure 5 An example signaling procedure is shown; and

[0045] Figure 6 An example controller is shown.

[0046] The drawings are not necessarily drawn to scale. For the sake of clarity and brevity, certain features and views of the drawings may be schematically shown or enlarged to scale. For example, the size of some elements in the drawings may be exaggerated relative to other elements to aid illustration. Corresponding reference numerals are used in the drawings to indicate corresponding features. For the sake of clarity, all reference numerals may not necessarily be shown in all drawings.

[0047] definition

[0048] CPA Condition PSCell Add

[0049] CPAC Condition PSCell Additions and Changes

[0050] PSCell changes under CPC conditions

[0051] DRB Data Radio Bearer

[0052] MAC Media Access Control

[0053] MCG master cell group

[0054] MN master node

[0055] MR measurement report

[0056] MR-DC Multi-RAT Dual Connectivity

[0057] NR-DC New Wireless Dual Connectivity

[0058] PDCP Packet Data Convergence Protocol

[0059] PSCell primary and secondary cells

[0060] PUCCH Physical Uplink Control Channel

[0061] RAT Radio Access Technology

[0062] RLC Radio Link Control

[0063] SCG secondary cell group

[0064] SCPAC and CPAC

[0065] SN Auxiliary Node

[0066] S-SN Source-SN

[0067] T-SN Target-SN DETAILED DESCRIPTION

[0068] Figure 1 An example of a network 100, such as a 5G NR network, is shown. The network 100 includes a plurality of different types of nodes 110, 120, 130. The different types of nodes may include terminal nodes 110 and network nodes. The network nodes may include service nodes 120 and core network nodes 130 and / or any other suitable type of device.

[0069] Service node 120 may be configured to communicate with terminal node 110. Core network node 130 communicates with service node 120. In some examples, core network node 130 communicates with terminal node 110.

[0070] In some examples, core network nodes 130 may be in communication with each other. In some examples, one or more service nodes 120 may be in communication with each other.

[0071] The network 100 may be a cellular network comprising a plurality of cells 122. Each cell is served by a serving node 120. The interface between the terminal node 110 and the serving node 120 defining the cells 122 is a wireless interface 124 in this example.

[0072] The serving node 120 comprises one or more cellular radio transceivers. The terminal node 110 comprises one or more cellular radio transceivers.

[0073] In the example shown, the cellular network 100 is a 3rd Generation Partnership Project (3GPP) network, where the terminal node 110 is a user equipment (UE) and the serving node 120 may be an access node such as a base station (gNB).

[0074] The term "user equipment" is used to designate a mobile device that includes a smart card for authentication / encryption, etc., such as a Subscriber Identity Module (SIM). In some examples, the term "user equipment" is used to designate a mobile device that includes circuitry embedded as part of the user equipment for authentication / encryption, such as a software SIM.

[0075] The service node 120 may be a base station. The service node 120 may be any suitable type of base station. A base station is an access node. The service node 120 may be a network entity responsible for radio transmission and reception in one or more cells to or from the UE 110. The service node 120 may be a network element in a radio access network (RAN) or any other suitable type of network.

[0076] In radio communications, node operations may be performed at least in part in a central / centralized unit CU (e.g., a server, host, or node) operatively coupled to a distributed unit DU (e.g., a radio head / node). Node operations may also be distributed between multiple servers, nodes, or hosts. It should also be understood that the distribution of work between core network operations and base station operations may vary depending on the implementation. Therefore, the 5G network architecture may be based on the so-called CU-DU split. One gNB-CU (gNB is an example of a base station or service node) may control one or more gNB-DUs. The term "gNB" in 5G may correspond to an eNB in ​​LTE. A gNB-CU (central node) may control multiple spatially separated gNB-DUs, acting at least as a transmit / receive (Tx / Rx) node. In some embodiments, a gNB-DU (also referred to as a DU) may include, for example, a radio link control (RLC), a media access control (MAC) layer, and a physical (PHY) layer, while a gNB-CU (also referred to as a CU) may include layers above the RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC), and an Internet Protocol (IP) layer. Other functional divisions are also possible. It is assumed that those skilled in the art are familiar with the OSI (Other Systems Information) model and the functions within each layer.

[0077] Core network node 130 may be part of a core network. Core network node 130 may be configured to manage functions related to connectivity of UE 110. For example, core network node 130 may be configured to manage functions such as connectivity, mobility, authentication, authorization, and / or other suitable functions.

[0078] exist Figure 1 In the example of FIG. 1 , core network node 130 is shown as a single entity. In some examples, core network node 130 may be distributed across multiple entities. For example, core network node 130 may be cloud-based or distributed in any other suitable manner.

[0079] For example, the network 100 may be a 4G or 5G network. For example, it may be a New Radio (NR) network using gNBs as access nodes. New Radio is the 3GPP name for 5G technology. In such a case, the service node 120 may include a gNodeB (gNB) 120, which is configured to provide user plane and control plane protocol termination to the UE 110 and / or perform any other suitable functions. The gNBs 120 are interconnected to each other via an X2 / Xn interface 126. The gNBs 120 are also connected to a core network node 130 via an N2 interface 128. Other types of networks and interfaces may be used in other examples. Other types of networks may include next generation mobile and communication networks, such as 6G networks.

[0080] In a dual connectivity mode such as New Radio - Dual Connectivity (NR-DC), UE 110 is simultaneously connected to a Primary Node (MN) and a Secondary Node (SN). MN is a radio access node that provides a control plane connection to the core network. It can be a primary gNB or any other suitable type of node. SN is a radio access node that does not have a control plane connection to the core network and provides additional resources to UE 110. It can be a secondary gNB or any other suitable type of node.

[0081] Both MN and SN can be associated with multiple cells or carriers. Multiple cells or carriers can be referred to as a master cell group (MCG) and a secondary cell group (SCG). MCG is a group of service cells associated with MN. SCG is a group of service cells associated with SN. Each group has a primary cell that carries a physical uplink control channel (PUCCH) and may have one or more secondary cells, the primary cell of the MCG is the PCell, and the primary cell of the secondary cell is the PSCell. The corresponding cell group may change during the switching process.

[0082] Figures 2A to 2DAn example PSCell change and a bearer change that may occur after the PSCell change are shown. The PSCell change may include a Conditional PSCell Change (CPC) procedure or a Conditional PSCell Addition and Change (CPAC). The CPC procedure and the CPAC procedure are PSCell change procedures that are performed only when the PSCell execution conditions are met. The CPC and CPAC procedures may occur without changes in the PCell. The MN may decide the CPC / CPAC execution conditions.

[0083] Figure 2A The example in shows an inter-SN PSCell change followed by an intra-SN PSCell change.

[0084] First, in Figure 2A In the example of FIG. 1 , the UE 110 first connects to the first master node 120M and the first secondary node 120S_1. The solid lines between the UE 110 and each serving node 120 indicate the bearers used.

[0085] As shown by arrow 200, a first PSCell change procedure is performed. The first PSCell change 200 may be performed because the UE 110 has moved or for any other suitable reason. After the first PSCell change 200, the UE 110 is connected to the second secondary node 120S_2. The second secondary node 120S_2 has replaced the first secondary node 120S_1. In this example, the first PSCell change is an inter-SN change because the SN connected to the UE 110 changes.

[0086] In this case, a PSCell change occurs because the UE 110 is now connected to a different SN and corresponding SCG. In this example, the second SN 120S_2 has the first PSCell1.

[0087] The first PSCell change 200 will result in changes in the bearer and MCG configuration. The MCG configuration is a configuration for maintaining the link to MN120M. The change of the bearer is indicated by arrow 202. The dashed line indicates the bearer that has been changed. In this case, the MCG bearer is added and the SCG bearer is released. The MCG configuration can, for example, define how to distribute the load between PSCell1 and MN. As an example, the bearer can be changed from PSCell1 to MN because the new PSCell1 cannot handle as much load as SN_1 (120S_1).

[0088] Figure 2AThe example in also shows a second PSCell change that can occur after the first PSCell change 200. The second PSCell is indicated by arrow 204. The second PSCell change 204 can be performed because the UE 110 has moved or for any other suitable reason. After the second PSCell change 204, the UE 110 remains connected to the second secondary node 120S_2. However, the PSCell of the SN has changed so that the second SN 120S_2 is now using the second PSCell. In this example, the second handover 205 is an intra-SN change because the SN connected to the UE 110 does not change.

[0089] The second PSCell may result in a remapping of the bearers and MCG configurations used as shown by arrow 206. However, in this case, remapping of the bearers and MCG configurations may not be necessary as there may not be any changes to these. In this case, the remapping may result in unnecessary interruptions due to the reset of the media access control (MAC), radio link control (RLC), and packet data convergence protocol (PDCP). This will also result in unnecessary processing and power consumption at the UE 110.

[0090] Figure 2B The example in shows an inter-SN PSCell change followed by another inter-SN PSCell change.

[0091] First, in Figure 2B In the example of FIG. 1 , the UE 110 is connected to the first master node 120M and the first secondary node 120S_1. The solid lines between the UE 110 and the corresponding serving nodes 120 indicate the bearers used.

[0092] As shown by arrow 210, a first PSCell change procedure is performed. The first PSCell change procedure 210 may be performed because the UE 110 has moved or for any other suitable reason. After the PSCell change 210, the UE 110 is connected to the second secondary node 120S_2. The second secondary node 120S_2 has replaced the first secondary node 120S_1. In this example, the first handover 210 is an inter-SN change because the SN connected to the UE 110 changes.

[0093] In this case, a PSCell change occurs because the UE 110 is now connected to a different SN and corresponding SCG. In this example, the second SN 120S_2 has the first PSCell1.

[0094] The first handover 210 will result in a change of bearer and MCG configuration. The change of bearer is indicated by arrow 212. In this case, the MCG bearer is added and the SCG bearer is released.

[0095] Figure 2B The example in also shows a second PSCell change that may occur after first PSCell change 210. The second PSCell change is indicated by arrow 214. Second PSCell change 214 may be performed because UE 110 has moved or for any other suitable reason.

[0096] The second PSCell change 214 causes the addition of MCG bearers and the release of SCG bearers, as indicated by arrow 218. The second PSCell change 214 may also cause remapping of existing MCG bearers, as indicated by arrow 216. Such remapping of existing MCG bearers may not be necessary as these may not have any changes.

[0097] Figure 2C The example in shows a conditional PSCell addition (CPA) change followed by an intra-frame PSCell change.

[0098] First, in Figure 2C In the example of FIG. 1 , UE 110 is connected to first master node 120M. Solid lines between UE 110 and each serving node 120 indicate the bearers used.

[0099] The CPA procedure is performed as indicated by arrow 220. The CPA procedure 220 may be performed because the UE 110 has moved or for any other suitable reason. After the CPA procedure 220, the UE 110 connects to the second secondary node 120S_2.

[0100] In this case, a PSCell has been added since the UE 110 is now connected to the SN 120S_2 and the corresponding SCG.In this example, the second SN 120S_2 has a first PSCell1.

[0101] The CPA procedure 220 results in a change of bearer and MCG configuration. The change of bearers is indicated by arrow 222. In this case, the MCG bearer is released and the SCG bearer is added.

[0102] Figure 2C The example in also shows an intra-SN PSCell change that may occur after CPA procedure 220. The intra-SN PSCell change is indicated by arrow 224. The intra-SN PSCell change 224 may be performed because UE 110 has moved or for any other suitable reason.

[0103] The intra-SN PSCell change 224 causes the addition of MCG bearers and the release of SCG bearers. This may result in a remapping of the SCG bearers, as shown by arrow 226. Such a remapping of existing SCG bearers may not be necessary as these may not have any changes.

[0104] Figure 2D The example in shows a CPA change followed by an inter-PSCell change.

[0105] First, in Figure 2D In the example of FIG. 1 , UE 110 is connected to a first master node 120M. The solid line between UE 110 and the corresponding serving node 120 indicates the bearers used.

[0106] The CPA procedure is performed as indicated by arrow 230. The CPA procedure 230 may be performed because the UE 110 has moved or for any other suitable reason. After the CPA procedure 230, the UE 110 connects to the second secondary node 120S_2.

[0107] In this case, a PSCell has been added since the UE 110 is now connected to the SN 120S_2 and the corresponding SCG.In this example, the second SN 120S_2 has a first PSCell1.

[0108] The CPA procedure 230 results in a change of bearer and MCG configuration. The change of bearers is indicated by arrow 232. In this case, the MCG bearer is released and the SCG bearer is added.

[0109] Figure 2D The example in also shows an inter-SN PSCell change that may occur after the CPA procedure 230. The inter-SN PSCell change 230 is indicated by arrow 234. The inter-SN PSCell change 234 may be performed because the UE 110 has moved or for any other suitable reason.

[0110] The inter-SN PSCell change 234 causes the release of MCG bearers and the addition of SCG bearers, as indicated by arrow 236. The inter-SN PSCell change 234 may also cause remapping of SCG bearers, as indicated by arrow 238. Such remapping of existing SCG bearers may not be necessary as these may not have any changes.

[0111] Examples of the present disclosure reduce these disruptions by avoiding unnecessary remapping of MCG configuration and SCG configuration and bearers after the CPAC process.

[0112] Figure 3A and 3B An example method is shown that may be used in examples of the present disclosure. Figure 3A The method may be implemented by UE110, Figure 3B The method can be implemented by MN 120M.

[0113] In the example of FIG. 3 , the method includes: at block 300 , receiving at least one configuration table from the MN 120M, wherein the at least one configuration table informs the UE 110 whether there is a change in MCG configuration between different PSCells.

[0114] The configuration table may include information related to MCG and / or SCG configurations to be applied before and after a PSCell change or addition process. In some examples, the configuration table received by UE 110 may include an MCG bearer configuration table including MCG bearer configuration information including bearers that can be offloaded from a secondary cell group SCG when a change from a source PSCell to a target PSCell is performed.

[0115] In some examples, the received configuration table may include a configuration table for each cell group, indicating whether the mapping identifiers for the bearers within the cell group are the same after the PSCell changes. The configuration table for each cell group includes at least one of the following: MCG configuration; SCG configuration; MCG and SCG configuration. In some examples, the received configuration table may include configuration information for SCG bearers and configuration information for MCG bearers.

[0116] If the bearer involved in the PSCell change is an MCG bearer, the UE 110 will use the configuration table including the MCG configuration. If the bearer involved in the PSCell change is an SCG bearer, the UE 110 will use the configuration table including the SCG configuration.

[0117] The configuration table may be received in any suitable message. In some examples, the indication may be received in a radio resource control (RRC) message (eg, an RRCReconfiguration message or any other suitable message).

[0118] The received configuration table may include any suitable information or parameters. In some examples, the corresponding parameters may include at least one of: a radio link control (RLC) parameter, a packet data convergence protocol (PDCP) parameter, or any other suitable information or parameter.

[0119] At block 302 , the method includes performing a PSCell change from a source PSCell to a target PSCell and applying an MCG configuration to the target PSCell based on at least one configuration table.

[0120] When performing a PSCell change, when there is a PSCell change from a source PSCell to a target PSCell, the UE 110 may use the received configuration table to determine whether there is a change in the MCG configuration. If the configuration table indicates that there is a change in the MCG configuration, the UE 110 will apply the change. Conversely, if the configuration table indicates that there is no change in the MCG configuration, the UE 110 will maintain the MCG configuration for the source PSCell.

[0121] In some examples, UE 110 may use information in the received configuration table to determine the difference between the MCG configuration for the target PSCell and the MCG configuration for the source PSCell. UE 110 may then determine whether remapping of the MCG configuration is required based on whether the difference between the state transfer MCG configuration for the state transfer target PSCell and the MCG configuration for the state transfer source PSCell is determined.

[0122] Maintaining the MCG configuration means there is no reset of the MCG configuration. This helps avoid unnecessary outages.

[0123] Figure 3B Example methods that may be performed by a MN are shown. Figure 3A The UE 110 may be connected to perform Figure 3B Methods of MN.

[0124] exist Figure 3B In an example of , the method includes: at block 310, requesting configuration information from one or more candidate target SNs. The request may be made using any suitable message, such as an SN add request.

[0125] At block 312, the method includes receiving the requested configuration information. The requested information may be received using any suitable message, such as, for example, SN Add Request Acknowledgement.

[0126] At block 314, the method includes transmitting at least one configuration table to the UE 110 based on the requested configuration information, wherein the configuration table informs the UE 110 whether there is a change in the MCG configuration between different PSCells.

[0127] UE 110 may use the configuration table to determine whether to maintain the MCG configuration when changing PSCells.

[0128] Figure 4An example signaling process that can be used in the examples of the present disclosure is shown. In this example, the configuration table sent from the MN 120M to the UE 110 can be an MCG bearer configuration table. The MCG bearer configuration includes information about the MCG bearer and can be used by the UE 110 to determine whether there is a change in the MCG bearer after the PSCell change. The MCG bearer configuration includes information including bearers that can be unloaded from the secondary cell group SCG when a change from a source PSCell to a target PSCell is performed. The MCG bearer can be used to maintain a link to the MN 120M after the PSCell change. The PSCell change does not involve changes in the PCell.

[0129] At block 400, UE 110 transmits a measurement report (MR) to a MN.

[0130] At block 402, MN 120M prepares a reference SCG configuration. This provides a reference against which the incremental SCG configuration can be compared. MN 120M may also initiate a CPAC procedure. In this example, it may be an inter-SN CPAC procedure involving an SN change. This may correspond to Figures 2A to 2D An inter-SN example is shown. An inter-SN CPAC process may be initiated based on the received MR.

[0131] At blocks 404 and 406, the MN sends a request for configuration information to the target SNs. At block 404, the MN sends an SN add request to the first target SN, and at block 406, the MN sends an SN add request to the second target SN. Figure 4 In the example of FIG. 5 , only two target SNs are shown, but the MN may send requests for configuration information to any number of target SNs.

[0132] The corresponding SN add request may include an indication of an MCG reference configuration. The MCG reference configuration may be the MCG configuration of the source PSCell. The MCG reference configuration may include information with which the incremental MCG configuration may be compared. The incremental configuration is a file indicating the difference between the reference configuration and the configuration to be applied.

[0133] The corresponding SN add request may also include an indication of an SCG reference configuration. The SCG reference configuration may be the SCG configuration of the source PSCell. The SCG reference configuration may include information that may be compared with the incremental SCG configuration.

[0134] The same reference configuration may be sent to each target SN.

[0135] At blocks 408 and 410, the MN 120M receives a response to the configuration information request. The received response may include the requested configuration information. The requested information may be received using any suitable message, such as an SN Add Request Acknowledgement.

[0136] At block 408, the MN 120M receives a request confirmation from the first target SN, and at block 410, the MN receives a request confirmation from the second target SN. The request confirmation may include an incremental SCG configuration for the PSCells of the respective target SNs. Figure 4 In the example of FIG. 5 , the MN is shown as receiving configuration information from two target SNs, however the MN may receive configuration information of any number of target SNs.

[0137] At block 412, MN 120M sends an RRCReconfiguration message to UE 110. The RRCReconfiguration message includes MN RRC reconfiguration information and SN conditional RRC reconfiguration.

[0138] The RRCReconfiguration message may include a configuration table. In this example, the configuration table includes an MCG bearer configuration table. Other types of configuration tables may be used in other examples.

[0139] Table 1 shows an example scenario, and Table 2 shows an example MCG bearer configuration table that can be used in the example scenario.

[0140] Service-PSCell MN DRB1 SN DRB2 SN DRB3 SN DRB4 Target-PSCell1 MN DRB1 MN DRB2-Reconstruction True SN DRB3 SN DRB4 Target-PSCell2 MN DRB1 MN DRB2-Reconstruction True SN DRB3 SN DRB4 Target-PSCell3 MN DRB1 MN DRB2-Reconstruction True MN DRB3-Reconstruction SN DRB4

[0141] Table 1

[0142] Table 1 indicates the CPAC configuration of each PSCell. Table 1 indicates whether SN or MN bearers are used for the corresponding data radio bearers (DRBs) of the available PSCells. In this scenario, if DRB1 is being used, MN bearers are used for all PSCells. If DRB2 is being used, SN bearers are used for the serving PSCell, but MN bearers are used for other PSCells. If DRB3 is being used, SN bearers are used for the serving PSCell, the first target PSCell 1, and the second target PSCell 2, and MN bearers are used for the third target PSCell 3. If DRB3 is being used, SN bearers are used for all PSCells.

[0143] The example scenarios shown in Table 1 are provided as examples only. The examples of the present disclosure may be used for different numbers of PSCells, different numbers of DRBs and different arrangements of bearers for the corresponding PSCells.

[0144] DRB ID PDCP Configuration RLC Configuration DRB ID1 PDCP-Configuration1 RLC-Configuration 1 DRB ID2 PDCP-Configuration2 RLC-Configuration 2 DRB ID3 PDCP-Configuration 3 RLC-Configuration 3 DRB ID4 PDCP Configuration 4 RLC-Configuration 3

[0145] Table 2

[0146] Table 2 shows an example MCG bearer configuration table. This includes the various PDCP parameters and RLC parameters to be used for each DRB ID. This will indicate whether the MCG configuration or the SCG configuration will be used for the PSCell for each of the corresponding DRBs. At block 412, the MCG bearer configuration table may be signaled to the UE 110.

[0147] At block 414, UE 110 responds to the RRCReconfiguration message by sending an RRCReconfigurationComplete message to MN 120M.

[0148] If the execution condition of the first PSCell is satisfied, then at block 416, UE 110 sends an RRCReconfigurationComplete message to MN 120M. The RRCReconfigurationComplete message indicates that the PSCell will be changed from the source PSCell to the first target PSCell 1.

[0149] At block 418, UE 110 references the received MCG bearer configuration table to determine which configurations should be applied. UE 110 may use the MCG bearer configuration table to determine whether there is a bearer change after a PSCell change. UE 110 may use the MCG bearer configuration table to determine whether there is a handover between a MN bearer and a SN bearer after a PSCell change.

[0150] For the example scenario shown in Table 1, if DRB1 is being used, a change from the serving PSCell to the first target PSCell 1 will not result in a change in bearer because the MN bearer is used for both on DRB1. Similarly, if DRB3 or DRB4 are being used, a change from the serving PSCell to the first target PSCell 1 will not result in a change in bearer because the SN bearer is used for each of these. However, if DRB2 is being used, a change from the serving PSCell to the first target PSCell 1 will result in a change in bearer because the SN is used for the serving cell, but the MN is used for the first target PSCell 1.

[0151] UE 110 can determine whether there are changes in the bearer by accessing the received MCG bearer configuration table. If the MCG bearer configuration table indicates that there are changes in the MCG configuration, these changes will be applied. In this example, if DRB2 is being used, the bearer will be unloaded from the SN and added to the MN. UE 110 will apply the PDCP and RLC configurations from the MCG bearer configuration table. This will result in a remapping or reset of the bearer.

[0152] If the MCG bearer configuration table indicates that there is no change in the MCG configuration, the MCG configuration can be maintained and there is no reset or remapping of bearers. In this example, if DRB1 is being used, the MN bearer is used for both the serving cell and PSCell1. UE 110 does not need to apply the PDCP and RLC configurations from the MCG bearer configuration table and thus avoids unnecessary remapping or resetting of bearers.

[0153] After applying the configuration according to the received configuration table, UE 110 and MN 120M may perform a PSCell change.

[0154] At block 420, the MN 120M sends an SN release request to the source SN, and at block 422, the source SN responds to the SN release request by sending an SN release request acknowledgement (ACK) to the MN 120M.

[0155] At block 424, the MN 120M sends an SN reconfiguration complete message including the first PSCell1 to the first target SN.

[0156] At block 426, UE 110 performs a random access procedure to PSCell1 of the first target SN.

[0157] At block 428, the source SN sends a state transfer to the MN 120M to enable data forwarding, and at block 430, the MN 120M sends an SN state transfer to the first target SN for data forwarding. At block 432, the MN 120M sends a UeContextRelease to the source SN.

[0158] At block 434, UE 110 continues to measure and check CPC conditions. If UE 110 detects that the execution conditions for the second PSCell2 are met, UE 110 sends RRCReconfigurationComplete to MN 120M at block 436. This message indicates that the PSCell will be changed to PSCell2.

[0159] After sending the RRCReconfigurationComplete message, UE 110 refers to the received configuration table to determine whether there is a change in the MCG configuration after the change from PSCell1 to PSCell2.

[0160] For the example scenario shown in Table 1, if DRB1 or DRB2 is being used, a change from PSCell1 to a second target PSCell2 will not result in a change in bearers because MN bearers are used for each of these. Similarly, if DRB3 or DRB4 is being used, a change from PSCell1 to a second target PSCell2 will not result in a change in bearers because SN bearers are used for each of these. Therefore, for this example, UE 110 determines that there is no change in the MCG configuration. UE 110 does not reset the MCG configuration, but applies the same MCG configuration again. UE 110 does not need to apply the PDCP and RLC configurations from the MCG bearer configuration table, and thus avoids unnecessary remapping or resetting of bearers.

[0161] After applying the configuration according to the received configuration table, UE 110 and MN 120M may perform a PSCell change. At block 440, the first target SN sends a state transfer to MN 120M to enable data forwarding, and at block 442, MN 120M sends an SN state transfer to the second target SN for data forwarding. At block 444, the MN sends a UeContextRelease to the first target SN.

[0162] Figure 5 Another example signaling process that can be used in the examples of the present disclosure is shown. In this example, the configuration table sent from MN120M to UE 110 includes a configuration table for each cell group, which indicates whether the mapping identifiers used for bearers within the cell group are the same after the PSCell change. In this example, the configuration table may include a CPAC to DRB mapping table. The CPAC to DRB mapping table can be used for MCG configuration, SCG configuration, or for both MCG and SCG configurations.

[0163] At block 500, UE 110 transmits a measurement report (MR) to a MN.

[0164] At block 502, the MN 120M prepares a reference SCG configuration. This provides a reference against which the ΔSCG configuration can be compared. The MN 120M may also initiate a CPAC procedure. In this example, it may be an inter-SN CPAC procedure involving an SN change. This may correspond to Figures 2A to 2D An inter-SN example is shown. An inter-SN CPAC process may be initiated based on the received MR.

[0165] At blocks 504 and 506, the MN sends a request for configuration information to the target SNs. At block 504, the MN sends an SN add request to the first target SN, and at block 506, the MN sends an SN add request to the second target SN. Figure 5In the example of FIG. 5 , only two target SNs are shown, but the MN may send requests for configuration information to any number of target SNs.

[0166] The corresponding SN add request may include an indication of an MCG reference configuration. The MCG reference configuration may be the MCG configuration of the source PSCell. The MCG reference configuration may include information with which the incremental MCG configuration may be compared. The incremental configuration is a file indicating the difference between the reference configuration and the configuration to be applied.

[0167] The corresponding SN add request may also include an indication of an SCG reference configuration. The SCG reference configuration may be the SCG configuration of the source PSCell. The SCG reference configuration may include information that may be compared with the incremental SCG configuration.

[0168] The same reference configuration may be sent to each target SN.

[0169] At blocks 508 and 510, the MN 120M receives a response to the configuration information request. The received response may include the requested configuration information. The requested information may be received using any suitable message, such as an SN Add Request Acknowledgement.

[0170] At block 508, the MN 120M receives a request confirmation from the first target SN, and at block 410, the MN receives a request confirmation from the second target SN. The request confirmation may include an incremental SCG configuration for the PSCell of the corresponding target SN. Figure 5 In the example of FIG. 5 , the MN is shown as receiving configuration information from two target SNs, however the MN may receive configuration information of any number of target SNs.

[0171] At block 512, MN 120M sends an RRCReconfiguration message to UE 110. The RRCReconfiguration message includes MN RRC reconfiguration information and SN conditional RRC reconfiguration.

[0172] The RRCReconfiguration message may include a configuration table. In this example, the configuration table includes an indication of whether the mapping identifiers for bearers within the cell group are the same after the PSCell change. In this example, the configuration table may include a CPAC to DRB mapping table.

[0173] Table 3 shows an example scenario, and Tables 4 and 5 show example configuration tables that may be used in the example scenario.

[0174]

[0175]

[0176] Table 3

[0177] Table 3 indicates the CPAC configuration for each PSCell. Table 1 indicates whether SN or MN bearers are used for the corresponding data radio bearers (DRBs) of the available PSCells. The first row of the table shows that all DRBSs are connected as part of the MCG before DC is established. In the case where DRB1 is being used, once DC has been established, MN bearers are used for all PSCells. If DRB2 is being used, SN bearers are used for the serving PSCell, but MN bearers are used for other PSCells. If DRB3 is being used, SN bearers are used for the serving PSCell, the first target PSCell 1, and the second target PSCell 2, and MN bearers are used for the third target PSCell 3. If DRB3 is being used, SN bearers are used for all PSCells.

[0178] Table 3 also shows the CPAC ID of each PSCell.

[0179] The example scenarios shown in Table 3 are provided as examples only. The examples of the present disclosure may be used for different numbers of PSCells, different numbers of DRBs and different arrangements of bearers for the corresponding PSCells.

[0180] Table 4 shows an example MCG CPAC to DRB mapping table.

[0181] CPAC ID DRB ID1 DRB ID2 DRB ID3 DRB ID4 ID1 1 null null null ID2 1 1 null null ID3 1 1 null null ID4 1 1 1 null

[0182] Table 4

[0183] The MCG CPAC to DRB mapping table indicates whether the MN bearer is used for the corresponding PSCell and DRB. In this table, a "null" value may indicate that the MN bearer is not used, while a value other than null may indicate that the MN bearer is used. In this case, a value of 1 is used to indicate that the MN bearer is to be used, but other values ​​may be used in other examples.

[0184] When applying the configuration from the MCG CPAC to DRB mapping table, UE 110 may compare the values ​​of the CPAC ID and DRB ID of the source PSCell with the values ​​of the CPAC ID and DRB ID of the target PSCell. If there is a change in the values, this indicates that the bearer has been offloaded from the MCG to the SCG and the change must be applied. Conversely, if there is no change in the values, this indicates that no bearer has been offloaded. The original MCG configuration may be maintained and no bearer remapping or resetting is required.

[0185] Table 5 shows an example MCG CPAC to DRB mapping table.

[0186] CPAC ID DRB ID1 DRB ID2 DRB ID3 DRB ID4 ID1 null 10 20 25 ID2 null null 20 25 ID3 null null 20 25 ID4 null null null 25

[0187] Table 5

[0188] The SCG CPAC to DRB mapping table indicates whether an SN bearer is used for the corresponding PSCell and DRB. In this table, a "null" value may indicate that the SN bearer is not used, and a value other than null may indicate that the SN bearer is used. In this case, the values ​​10, 20, 25 are used to indicate that the SN bearer is to be used, but other values ​​may be used in other examples. Different values ​​may represent different SN bearers.

[0189] When applying the configuration from the SCG CPAC to DRB mapping table, UE 110 may compare the values ​​of the CPAC ID and DRB ID of the source PSCell with the values ​​of the CPAC ID and DRB ID of the target PSCell. If there is a change in the values, this indicates that the bearer has been offloaded from the MCG to the SCG and the change must be applied. Conversely, if the values ​​have not changed, this indicates that no bearer has been offloaded. The original MCG configuration may be maintained and no bearer remapping or resetting is required.

[0190] Table 5 shows an example SCG CPAC to DRB mapping table.

[0191] CPAC ID DRB ID1 DRB ID2 DRB ID3 DRB ID4 ID1 null 10 20 25 ID2 null null 20 25 ID3 null null 20 25 ID4 null null null 25

[0192] Table 5

[0193] In an example of the present disclosure, the MN may send an MCG or an SCG or both an MCG and SCG table to the UE 110. If the mapping table includes both SCG and MCG configuration mappings, the entries in the table may indicate whether the DRB is mapped to the MN, whether the DRB is mapped to the Sn, or whether the DRB is not mapped to any node.

[0194] Other variations of configuration tables may be used in other examples.

[0195] At block 514, UE 110 responds to the RRCReconfiguration message by sending an RRCReconfigurationComplete message to MN 120M.

[0196] If the execution condition of the first PSCell is satisfied, then at block 516, UE 110 sends an RRCReconfigurationComplete message to MN 120M. The RRCReconfigurationComplete message indicates that the PSCell will be changed from the source PSCell to the first target PSCell 1.

[0197] At block 518, UE 110 refers to the received configuration table to determine which configurations should be applied. UE 110 may use the mappings in the received configuration table to determine whether there is a bearer change after a PSCell change. UE 110 may use the mappings in the received configuration table to determine whether there is a handover between a MN bearer and a SN bearer after a PSCell change.

[0198] For the example scenario shown in Table 3, if DRB1 is being used, a change from the serving PSCell to the first target PSCell 1 will not result in a change in bearer because the MN bearer is used for both on DRB1. The UE 110 can determine this by determining that the same value is used for the corresponding entry in the mapping table. Similarly, if DRB3 or DRB4 is being used, a change from the serving PSCell to the first target PSCell 1 will not result in a change in bearer because the SN bearer is used for each of these. The UE 110 can determine this by determining that the same value is used for the corresponding entry in the mapping table. However, if DRB2 is being used, a change from the serving PSCell to the first target PSCell 1 will result in a change in bearer because the SN is used for the serving cell, but the MN is used for the first target PSCell 1. The UE 110 can determine this by determining that different values ​​are used for the corresponding entries in the mapping table.

[0199] If the mapping table indicates that there is a change in the bearer, the UE 110 will apply the appropriate changes. In this example, if DRB2 is being used, the bearer will be offloaded from the SN and added to the MN. The UE 110 will apply the appropriate PDCP and RLC. This will result in a remapping or reset of the bearer.

[0200] If the mapping table indicates that the MCG configuration has not changed, the MCG configuration can be maintained and there is no reset or remapping of bearers. In this example, if DRB1 is being used, the MN bearer is used for both the serving cell and PSCell1. UE 110 does not need to apply the PDCP and RLC configurations from the MCG bearer configuration table and thus avoids unnecessary remapping or resetting of bearers.

[0201] After applying the configuration according to the received configuration table, UE 110 and MN 120M may perform a PSCell change.

[0202] At block 520, the MN 120M sends an SN release request to the source SN, and at block 522, the source SN responds to the SN release request by sending an SN release request acknowledgment to the MN 120M.

[0203] At block 524, the MN 120M sends an SN reconfiguration complete message including the first PSCell1 to the first target SN.

[0204] At block 526 , UE 110 performs a random access procedure to PSCell1 of the first target SN.

[0205] At block 528, the source SN sends a state transfer to the MN 120M to enable data forwarding, and at block 530, the MN 120M sends an SN state transfer to the first target SN for data forwarding. At block 532, the MN 120M sends a UeContextRelease to the source SN.

[0206] At block 534, UE 110 continues to measure and check CPC conditions. If UE 110 detects that the execution conditions for the second PSCell2 are met, UE 110 sends RRCReconfigurationComplete to MN 120M at block 536. This message indicates that the PSCell will be changed to PSCell2.

[0207] After sending the RRCReconfigurationComplete message, UE 110 refers to the received configuration table to determine whether there is a change in the MCG configuration after the change from PSCell1 to PSCell2.

[0208] For the example scenario shown in Table 3, if DRB1 or DRB2 is being used, a change from PSCell1 to a second target PSCell2 will not result in a change in bearers because MN bearers are used for each of these. Similarly, if DRB3 or DRB4 is being used, a change from PSCell1 to a second target PSCell2 will not result in a change in bearers because SN bearers are used for each of these. Therefore, for this example, UE 110 determines that there is no change in the MCG configuration. UE 110 does not reset the MCG configuration, but applies the same MCG configuration again. UE 110 does not need to apply PDCP and RLC configurations, thereby avoiding unnecessary remapping or resetting of bearers.

[0209] After applying the configuration according to the received configuration table, UE 110 and MN 120M may perform a PSCell change. At block 540, the first target SN sends a state transfer to MN 120M to enable data forwarding, and at block 542, MN 120M sends an SN state transfer to the second target SN for data forwarding. At block 544, the MN sends a UeContextRelease to the first target SN.

[0210] Figure 6An example controller 600 is shown. The controller 600 may be provided within an entity such as the UE 110 or MN or any other suitable device, or the controller may be, for example, the UE 110 or MN 120M. The controller 600 may be implemented as a controller circuit. The controller 600 may be implemented in hardware alone, with certain aspects of software including firmware alone, or may be a combination of hardware and software (including firmware).

[0211] like Figure 6 As shown, the controller 600 may be implemented using instructions that implement hardware functionality, for example, by using executable instructions of a computer program 606 in a general or special purpose processor 602, which may be stored on a computer readable storage medium (disk, memory, etc.) for execution by such a processor 602.

[0212] The processor 602 is used to read and write the memory 604. The processor 602 may also include an output interface through which the processor 602 outputs data and / or commands and an input interface through which data and / or commands are input to the processor 602.

[0213] The memory 604 stores a computer program 606, which includes computer program instructions (computer program code) that control the operation of the device when loaded into the processor 602. The computer program instructions of the computer program 606 provide the logic and routines that enable the device to perform the methods shown in the drawings. The processor 602 can load and execute the computer program 606 by reading the memory 604.

[0214] Thus, the controller 600 includes: at least one processor 602; and at least one memory 604 storing instructions, which when executed by the at least one processor 602, causes the UE 110 to at least perform:

[0215] Receive 300 at least one configuration table from the master node, the at least one configuration table notifying the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and

[0216] Based on the at least one configuration table, a PSCell change from a source PSCell to a target PSCell is performed 302 and a state transfer MCG configuration is applied to the state transfer target PSCell.

[0217] Thus, the controller 600 includes: at least one processor 602; and at least one memory 604 storing instructions, which when executed by the at least one processor 602, causes the MN 120M to at least perform:

[0218] Requesting 310 configuration information from one or more candidate target secondary nodes;

[0219] receiving 312 the requested configuration information from one or more candidate target secondary nodes; and

[0220] Based on the requested configuration information, at least one configuration table is transmitted 314 to the user equipment 110, the configuration table notifying the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

[0221] The computer program 606 may arrive at the apparatus via any suitable delivery mechanism 608. The delivery mechanism 608 may be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a recording medium such as a compact disk read-only memory (CD-ROM) or a digital versatile disk (DVD) or a solid-state memory, an article of manufacture including or tangibly embodying the computer program 606. The delivery mechanism may be a signal configured to reliably transmit the computer program 606. The apparatus may propagate or send the computer program 606 as a computer data signal.

[0222] The computer program 606 may include computer program instructions for causing the UE 110 to perform at least the following operations or for performing at least the following operations:

[0223] receiving 300 at least one configuration table from the master node 120M, wherein the at least one configuration table notifies the user equipment whether there is a change in the configuration of the primary cell group MCG between different primary and secondary cells PSCells; and

[0224] Based on the at least one configuration table, a PSCell change from a source PSCell to a target PSCell is performed 302 and a state transfer MCG configuration is applied to the state transfer target PSCell.

[0225] The computer program 606 may include computer program instructions for causing the MN 120M to perform at least the following operations or for performing at least the following operations:

[0226] Requesting 310 configuration information from one or more candidate target secondary nodes;

[0227] receiving 312 the requested configuration information from one or more candidate target secondary nodes; and

[0228] Based on the requested configuration information, at least one configuration table is transmitted 314 to the user equipment 110, the configuration table notifying the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

[0229] The computer program instructions may be included in a computer program, a non-transitory computer readable medium, a computer program product, a machine readable medium. In some but not necessarily all examples, the computer program instructions may be distributed over more than one computer program.

[0230] Although memory 604 is shown as a single component / circuit, it may be implemented as one or more separate components / circuit(s), some or all of which may be integrated / removable and / or may provide permanent / semi-permanent / dynamic / cached storage.

[0231] Although processor 602 is shown as a single component / circuit, it may be implemented as one or more separate components / circuit, some or all of which may be integrated / removable.Processor 602 may be a single-core or multi-core processor.

[0232] The term "comprising" is used herein in an inclusive, not exclusive, sense. That is, any reference to X comprising Y indicates that X may include only one Y or may include more than one Y. If "comprising" is intended to be used in an exclusive sense, it will be clear in the context by reference to "comprising only one ..." or by the use of "comprising".

[0233] In this specification, the terms "connected", "coupled" and "in communication" and their derivatives mean operationally connected / coupled / in communication. It should be understood that any number or combination of intermediate components (including no intermediate components) may be present, i.e., to provide direct or indirect connection / coupling / in communication. Any such intermediate components may include hardware and / or software components.

[0234] As used herein, the term "determine / determine" (and grammatical variations thereof) may include at least: calculate, compute, process, derive, measure, investigate, identify, look up (e.g., look up in a table, a database, or another data structure), ascertain, etc. In addition, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), obtaining, etc. Moreover, "determine / determine" may include resolving, selecting, choosing, establishing, etc.

[0235] In this specification, reference has been made to various examples. The description of features or functions of an example indicates that those features or functions are present in the example. The use of the term "example" or "for example" or "may" or "might" in the text indicates that, whether explicitly stated or not, such features or functions are present in at least the described example, whether described as an example or not, and they may but not necessarily be present in some or all other examples. Therefore, "example", "for example", "may" or "might" refers to a specific instance in a class of examples. The attributes of an instance may be attributes of only the instance or attributes of a class or attributes of a subclass of a class including some but not all instances in the class. Therefore, it is implicitly disclosed that a feature described with reference to one example rather than with reference to another example can be used as part of a working combination in the other example where possible, but does not necessarily have to be used in the other example.

[0236] Although the examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims.

[0237] Features described in the preceding description may be used in combinations other than the combinations explicitly described above.

[0238] Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not.

[0239] Although features have been described with reference to certain examples, those features may also be present in other examples whether described or not.

[0240] The terms "a", "an" or "the" are used herein in an inclusive, not exclusive, sense. That is, any reference to X that includes one or one Y indicates that X may include only one Y or may include more than one Y, unless the context clearly indicates otherwise. If "a", "an" or "the" is intended to be used in an exclusive sense, it will become clear from the context. In some cases, 'at least one' or 'one or more' may be used to emphasize an inclusive sense, but the absence of these terms should not be taken to infer any exclusive sense.

[0241] The presence of a feature (or combination of features) in a claim relates to the feature or (combination of features) itself, and also to features that achieve substantially the same technical effect (equivalent features). Equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. Equivalent features include, for example, features that perform substantially the same function in substantially the same way to achieve substantially the same result.

[0242] In this specification, reference has been made to various examples using adjectives or adjective phrases to describe features of the examples. Such description of a characteristic associated with an example indicates that the characteristic exists in some examples exactly as described, and in other examples substantially as described.

[0243] The above description describes some examples of the present disclosure, however, those of ordinary skill in the art will be aware of possible alternative structures and method features that provide equivalent functionality to the specific examples of such structures and features described above, and have been omitted from the above description for the sake of brevity and clarity. Nevertheless, unless such alternative structures or method features are explicitly excluded in the above description of examples of the present disclosure, the above description should be understood to implicitly include such alternative structures and method features that provide equivalent functionality.

[0244] While an effort has been made in the foregoing description to draw attention to those features regarded as important, it should be understood that the applicant may seek protection by way of the claims for any patentable feature or combination of features referenced above and / or shown in the accompanying drawings, whether or not emphasis has been placed thereon.

[0245] In some aspects, a user equipment is provided, comprising means for:

[0246] receiving at least one configuration table from the master node, where the at least one configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and

[0247] Based on at least one configuration table, a PSCell change is performed from a source PSCell to a target PSCell and the MCG configuration is applied to the target PSCell.

[0248] In some embodiments, when there is a PSCell change from a source PSCell to a target PSCell, the user equipment uses at least one received configuration table to determine whether there is a change in the MCG configuration, and applies the change if the configuration table indicates that there is a change in the MCG configuration, or maintains the MCG configuration for the source PSCell if the configuration table indicates that there is no change.

[0249] In some embodiments, at least one configuration table includes an MCG bearer configuration table, the MCG bearer configuration table includes MCG bearer configuration information, and the MCG bearer configuration information includes bearers that can be unloaded from the secondary cell group SCG when a change from a source PSCell to a target PSCell is performed.

[0250] In some embodiments, the user equipment uses information in at least one configuration table to determine the difference between the MCG configuration for the target PSCell and the MCG configuration for the source PSCell.

[0251] In some embodiments, the user equipment determines whether remapping of the MCG configuration is required based on whether a difference between the MCG configuration for the target PSCell and the MCG configuration for the source PSCell is determined.

[0252] In some embodiments, at least one configuration table includes a configuration table for each cell group, and the configuration table indicates whether the mapping identifiers used for bearers within the cell group are the same after the PSCell changes.

[0253] In some embodiments, the configuration table for each cell group includes at least one of the following:

[0254] MCG configuration;

[0255] SCG configuration;

[0256] MCG and SCG configurations.

[0257] In some embodiments, the at least one configuration table includes a configuration table including configuration information for an SCG bearer and configuration information for an MCG bearer.

[0258] In some embodiments, at least one configuration table includes at least one of the following:

[0259] Radio link control parameters;

[0260] Packet Data Convergence Protocol parameters.

[0261] In some embodiments, the at least one configuration table is received in a radio resource control message.

[0262] In some aspects, a method is provided, comprising:

[0263] receiving at least one configuration table from the master node, where the at least one configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and

[0264] Based on at least one configuration table, a PSCell change is performed from a source PSCell to a target PSCell and the MCG configuration is applied to the target PSCell.

[0265] In some aspects, a computer program is provided, comprising program instructions, which, when executed by a user device, cause the user device to at least perform:

[0266] receiving at least one configuration table from the master node, where the at least one configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and

[0267] Based on at least one configuration table, a PSCell change is performed from a source PSCell to a target PSCell and the MCG configuration is applied to the target PSCell.

[0268] In some aspects, a master node is provided, comprising components for:

[0269] Requesting configuration information from one or more candidate target secondary nodes;

[0270] receiving the requested configuration information from one or more candidate target secondary nodes; and

[0271] Based on the requested configuration information, at least one configuration table is transmitted to the user equipment, and the configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

[0272] In some aspects, a method is provided, comprising:

[0273] Requesting configuration information from one or more candidate target secondary nodes;

[0274] receiving the requested configuration information from one or more candidate target secondary nodes; and

[0275] Based on the requested configuration information, at least one configuration table is transmitted to the user equipment, and the configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

[0276] In some aspects, a computer program is provided, comprising program instructions, which when executed by a master node, cause the master node to at least perform:

[0277] Requesting configuration information from one or more candidate target secondary nodes;

[0278] receiving the requested configuration information from one or more candidate target secondary nodes; and

[0279] Based on the requested configuration information, at least one configuration table is transmitted to the user equipment, and the configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells.

Claims

1. A user equipment comprising components for: receiving at least one configuration table from the master node, wherein the at least one configuration table notifies the user equipment whether there is a change in the primary cell group MCG configuration between different primary and secondary cells PSCells; and Based on the at least one configuration table, a PSCell change is performed from a source PSCell to a target PSCell and the MCG configuration is applied to the target PSCell.

2. A user equipment according to claim 1, wherein when there is a PSCell change from a source PSCell to a target PSCell, the user equipment uses the at least one configuration table received to determine whether there is a change in the MCG configuration, and if the configuration table indicates that there is a change in the MCG configuration, applies the change, or if the configuration table indicates that there is no change, maintains the MCG configuration for the source PSCell.

3. A user equipment according to claim 1, wherein the at least one configuration table includes an MCG bearer configuration table, the MCG bearer configuration table includes MCG bearer configuration information, and the MCG bearer configuration information includes bearers that can be unloaded from the secondary cell group SCG when a change from a source PSCell to a target PSCell is performed.

4. The user equipment of claim 1, wherein the user equipment uses information in the at least one configuration table to determine a difference between the MCG configuration for the target PSCell and the MCG configuration for the source PSCell.

5. The user equipment of claim 4, wherein the user equipment determines whether remapping of the MCG configuration is required based on whether a difference between the MCG configuration for the target PSCell and the MCG configuration for the source PSCell is determined.

6. The user equipment according to any one of claims 1-5, wherein the at least one configuration table comprises a configuration table for each cell group, and the configuration table indicates whether the mapping identifiers used for the bearers within the cell group are the same after the PSCell changes.

7. The user equipment according to claim 6, wherein the configuration table for each cell group comprises at least one of the following: MCG configuration; SCG configuration; MCG and SCG configurations.

8. The user equipment according to any one of claims 1-5, wherein the at least one configuration table comprises a configuration table including configuration information for an SCG bearer and configuration information for an MCG bearer.

9. The user equipment according to any one of claims 1 to 5, wherein the at least one configuration table comprises at least one of the following: Radio link control parameters; Packet Data Convergence Protocol parameters.

10. User equipment according to any of the preceding claims, wherein the at least one configuration table is received in a radio resource control message.

Images