Reconfiguration message during multi-connectivity in wireless communications

Abstract

A method comprising: during multi-connectivity, sending a reconfiguration message for execution by a user equipment; and sending a flag indicating an action to be taken by the user equipment during or after the user equipment executes an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions: discarding the reconfiguration message; executing the reconfiguration message after executing the existing reconfiguration message; or prioritizing execution of the reconfiguration message over execution of the existing reconfiguration message.

Description

Technical Field

[0001] Examples of this disclosure relate to reconfiguration messages during multiple connectivity in wireless communications. Some examples relate to radio resource control (RRC) reconfiguration messages during Evolved Universal Terrestrial Radio Access (E-UTRA) – 5G New Radio (NR) multiple connectivity. Background Technology

[0002] Multiple Radio Dual Connectivity (MR-DC) is an example of multi-connectivity. MR-DC enables User Equipment (UE) with multiple receivers / transmitters to use resources provided by different nodes. During multi-connectivity, the UE stores its configuration.

[0003] Established multi-connectivity connections can be reconfigured by sending a reconfiguration message. In 3GPP systems, this reconfiguration message is called an RRC reconfiguration message or RRC reconfiguration message.

[0004] In some cases, it may be necessary to provide improved reconfiguration message handling in multiple connections. Summary of the Invention

[0005] According to various, but not all, embodiments, a method is provided that includes: during multiple connections,

[0006] Send a reconfiguration message for execution by the user equipment; and

[0007] Sending a flag indicating the action to be taken by the user equipment during or after the user equipment executes an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions:

[0008] Discard the reconfiguration message;

[0009] Execute the reconfiguration message after executing the existing reconfiguration message; or

[0010] This makes the execution of this reconfiguration message take precedence over the execution of existing reconfiguration messages.

[0011] According to various, but not all, embodiments, a method is provided that includes: during multiple connections,

[0012] A query is received from the first master node, wherein the query is initiated by a decision of the first master node to send a reconfiguration message for execution by the user equipment, wherein the reconfiguration message includes a master node switch from the first master node to the target master node;

[0013] Obtain the configuration information associated with the reconfiguration message; and

[0014] Based on this configuration information, a response to the query is sent, enabling the first master node to send a flag indicating the action to be taken by the user equipment during or after the user equipment executes an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions:

[0015] Discard the reconfiguration message;

[0016] Execute the reconfiguration message after executing the existing reconfiguration message; or

[0017] This makes the execution of this reconfiguration message take precedence over the execution of existing reconfiguration messages.

[0018] According to various, but not all, embodiments, a method is provided that includes: during multiple connections,

[0019] Receive a query from the master node, wherein the query indicates a decision initiated by the master node to send a reconfiguration message for execution by the user equipment; and

[0020] A response to the query is sent, wherein the response includes a flag indicating an action to be taken by the user equipment during or after the user equipment executes an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions:

[0021] Discard the reconfiguration message;

[0022] Execute the reconfiguration message after executing the existing reconfiguration message; or

[0023] This makes the execution of this reconfiguration message take precedence over the execution of existing reconfiguration messages.

[0024] According to various, but not all, embodiments, a method is provided that includes: during multiple connections,

[0025] Receive configuration messages for execution by the user equipment;

[0026] A flag indicating the action to be taken by the user equipment during or after the user equipment executes an existing reconfiguration message; and

[0027] The action indicated by the flag is performed during or after the user equipment executes an existing reconfiguration message.

[0028] The flag is configured to distinguish between at least two of the following actions:

[0029] Discard the reconfiguration message;

[0030] Execute the reconfiguration message after executing the existing reconfiguration message; or

[0031] This makes the execution of this reconfiguration message take precedence over the execution of existing reconfiguration messages.

[0032] According to various, but not all, embodiments, a method is provided that includes: during multiple connections,

[0033] Send reconfiguration message information associated with the reconfiguration message to be performed by the user equipment; and

[0034] Sending a flag or information indicating the action to be taken by the user equipment during or after the user equipment executes an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions:

[0035] Discard the reconfiguration message;

[0036] Execute the reconfiguration message after executing the existing reconfiguration message; or

[0037] This makes the execution of this reconfiguration message take precedence over the execution of existing reconfiguration messages.

[0038] According to various, but not all, embodiments, an apparatus is provided that includes components for causing any one or more of the above-described methods to be performed. According to various, but not all, embodiments, a system comprising multiple means is provided.

[0039] According to various, but not all, embodiments, a computer program is provided that, when run on a computer, causes any one or more of the above methods to be performed.

[0040] According to various, but not all, embodiments, examples as claimed in the appended claims are provided. Attached Figure Description

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

[0042] Figure 1 Examples of the topics described in this article are shown;

[0043] Figure 2 Here is another example of the topic described in this article;

[0044] Figure 3 Here is another example of the topic described in this article;

[0045] Figure 4Here is another example of the topic described in this article;

[0046] Figure 5 Here is another example of the topic described in this article;

[0047] Figure 6 Here is another example of the topic described in this article;

[0048] Figure 7 Here is another example of the topic described in this article;

[0049] Figure 8 Here is another example of the topic described in this article;

[0050] Figure 9 Here is another example of the topic described in this article;

[0051] Figure 10 Here is another example of the topic described in this article;

[0052] Figure 11 Here is another example of the topic described in this article;

[0053] Figure 12 Here is another example of the topic described in this article;

[0054] Figure 13 Here is another example of the topic described in this article;

[0055] Figure 14 Here is another example of the topic described in this article;

[0056] Figure 15 Here is another example of the topic described in this article;

[0057] Figure 16 This provides another example of the topics described in this article; and

[0058] Figure 17 Here is another example of the topic described in this article. Detailed Implementation

[0059] definition

[0060] 3GPP Third Generation Partnership Project

[0061] 5G fifth-generation cellular network standard

[0062] CPC conditional PSCell changes

[0063] E-UTRA Evolutionary Universal Terrestrial Radio Access eNB eNodeB

[0064] gNB gNodeB gNB-CU gNodeB Centralized Unit

[0065] gNB-DU gNodeB Distributed Unit

[0066] MCG Main Cell Group

[0067] MN master node

[0068] NR New Radio

[0069] PCell main cell

[0070] PSCell Primary and Secondary Communities

[0071] RAN (Radio Access Network)

[0072] RAT Radio Access Technology

[0073] RLC Radio Link Control

[0074] RLF radio link failure

[0075] RRC Radio Resource Control

[0076] SCell Auxiliary Community

[0077] SCG Auxiliary Community Group

[0078] SgNB auxiliary gNodeB

[0079] SN auxiliary node

[0080] UE User Equipment

[0081] Figure 1 This is a schematic block diagram illustrating a wireless communication network system 1 configured for multiple connections. In at least some examples, system 1 is a network system defined by 3GPP.

[0082] Figure 1 The system includes UE 100, RAN including at least first node 102 and second node 104, and core network (NW) entity 108. Figure 1 The diagram also illustrates the third node 112 and the fourth node 114 of the RAN, enabling the UE 100 to change nodes during mobility.

[0083] In this document, the term "node" refers to an access node. In System 1 as defined by 3GPP, a node is a base station. A base station implementing NR is called a gNB. A base station implementing E-UTRA is called an eNB.

[0084] Figure 2 An example of nodes 104 / 114 (e.g., gNBs) configured to implement a first radio access technology (RAT) (e.g., NR) is illustrated. In this example, node 104 has a decomposed (split) architecture. gNB 104 includes one or more distributed units (gNB-DUs) 20 and a centralized unit (gNB-CU) 10. The apparatus 2 is configured to implement the functionality of at least a portion of nodes 104, 114 (such as gNB-CUs, and / or one or more gNB-DUs, or the entire gNB).

[0085] gNB-CU 10 is a logical node configured to host the Radio Resource Control (RRC) layer and other layers of gNB 120. gNB-CU 10 controls the operation of one or more gNB-DU 20s. gNB-DU 20 is a logical node configured to host the Radio Link Control Protocol (RLC), Media Access Control (MAC), and Physical (PHY) layers of the access node (gNB) 120. gNB-DU 20 communicates with the RRC layer hosted by gNB-CU via a dedicated interface (F1).

[0086] One gNB-DU 20 can support one or more cells (not shown in the figure). A cell is supported by only one gNB-DU 20.

[0087] Figure 3 An example of nodes 102 / 112 (e.g., eNBs) configured to implement a second RAT (e.g., E-UTRA) is illustrated. In this example, node 102 does not have a decomposed architecture. eNB 102 is a logical node configured to host the Radio Resource Control (RRC) layer and other layers of eNB 102. Device 2 is configured to implement at least a portion of the functionality of nodes 102, 112 such as eNBs.

[0088] Return to reference Figure 1 Nodes 102, 104, 112, and 114 are operatively coupled to each other via network interface 103. In the example implementation, network interface 103 includes an X2 interface.

[0089] UE 100 can be operatively coupled to node 102 via radio interface 101. In this example, radio interface 101 is a wireless interface. In the example implementation, radio interface 101 includes a Uu interface. During multiple connections, UE 100 can be simultaneously coupled to another node 104 via radio interface 105. In some examples, radio interfaces 101 and 105 include the same type of interface.

[0090] A node 102 to which UE 100 is operatively coupled can be configured to act as a primary node (MN). Another node 104 to which UE 100 is operatively coupled can be configured to act as a secondary node (SN).

[0091] exist Figure 1 In the diagram, the first node 102 is the first master node (MN 1), the second node 104 is the first auxiliary node (SN 1), the third node 112 is the second master node (MN2), and the fourth node 114 is the second auxiliary node (SN2). Figure 1 In the diagram, MN1 102 and SN1 104 are service (source) nodes.

[0092] At least MN 102 and 112 can be operatively coupled to core network entity 108 via interface 107. SN 104 and 114 can also be operatively coupled to core network entity 108. Figure 1 In this context, MN1102 and MN2112 can be operatively coupled to different core network entities 108 via interface 107, or can be operatively coupled to the same entity.

[0093] In the first example, MNs 102 and 112 are eNBs configured to implement E-UTRA. Core network entity 108 includes an evolved packet core (EPC) entity. Entity 108 may include a mobility management entity (MME) and / or a serving gateway (S-GW). Interface 107 includes an S1 interface.

[0094] In the second example, MNs 102 and 112 are gNBs configured to implement NR. Core network entity 108 includes a 5G core (5GC) entity. Entity 108 may include Access and Mobility Management Functions (AMF). Interface 107 includes an NG-C interface.

[0095] Below are examples of multiple connections. In most, but not all, of these examples, SN 104, 114 implements a different RAT than MN 102, 112.

[0096] One example is the E-UTRA–NR dual-connection (EN-DC), where the eNB acts as MN102 / 112 and the gNB acts as SN 104 / 114. This example is referenced throughout this specification. However, aspects of this disclosure also apply to other examples set forth below.

[0097] Another example is the next-generation RAN (NG-RAN) E-UTRA–NR dual connectivity (NGEN-DC), where the eNB (e.g., next-generation eNB: ng-eNB) acts as the MN and the gNB acts as the SN.

[0098] Another example of dual connectivity is the NR–E-UTRA dual connectivity (NE-DC), where the gNB acts as the MN and the ng-eNB acts as the SN.

[0099] Another example of dual connectivity is NR–NR dual connectivity (NR-DC), where one gNB acts as the MN and the other gNB acts as the SN. In another example of NR-DC, UE 100 is connected to two gNB-DUs, one serving the primary cell group (MCG) and the other serving the secondary cell group (SCG), which are connected to the same gNB-CU, acting as both the MN and SN.

[0100] In at least some examples of multi-connectivity, nodes 102, 104, 112, and 114 comprise cell groups of one or more cells. A cell group comprises a primary cell and zero or more secondary cells.

[0101] A cell refers to a geographical area with radio signals (i.e., covered by a base station in which a UE can connect and obtain service). Cells can be identified by a lower-layer physical cell identifier (PCI) and a higher-layer cell identifier.

[0102] The primary cell is a cell operating on the primary frequency (where UE 100 performs the initial connection establishment procedure or initiates a connection re-establishment procedure), or a cell designated as the primary cell during handover. In at least some examples, the primary cell is a cell configured to provide non-access stratum (NAS) mobility information during connection establishment, re-establishment, or handover. The primary cell can be configured to provide security input during connection re-establishment or handover.

[0103] A secondary cell is a cell operating on a secondary frequency. Once an RRC connection is established, it can be configured and used to provide additional radio resources. A secondary cell (SCell) can be configured to form a serving cell set together with a PCell.

[0104] In multi-connectivity, the cell group of MN 102 / 112 is the primary cell group (MCG). The cell group of SN 104 / 114 is the secondary cell group (SCG). The MCG includes a primary cell (PCell) and zero or more secondary cells (SCells). The SCG includes a primary and secondary cell (PSCell) and zero or more secondary cells (SCells). In at least some examples, in addition to a PCell or a PSCell, the MCG and SCG also include at least one SCell.

[0105] When multiple connections are established for the first time, UE 100 stores a configuration in its memory. This configuration includes information identifying the MCG, which includes a PCell and zero or more SCells, the SCG, which includes a PSCell and zero or more SCells, and one or more bearers.

[0106] The configuration may include one or more of the following: information for measurement configuration; information for mobility control; radio resource configuration information (including radio bearer, MAC master configuration and physical channel configuration); and / or access stratum (AS) security configuration.

[0107] After the application (execution) configuration is completed, the UE can receive and transmit data on the MCG and SCG bearers using the radio links provided by the MN and SN.

[0108] Multi-connectivity connections can be reconfigured by sending a reconfiguration message performed by the UE 100. When performed, the stored configuration is updated. 3GPP standard 37.340 for multi-connectivity defines the reconfiguration message as an RRC reconfiguration message.

[0109] SN-initiated RRC reconfiguration messages can be sent from PSCell or SCell, or both (in the case of carrier aggregation repetition). MN-initiated RRC reconfiguration messages can be sent from PCell or SCell, or both.

[0110] Examples of reconfiguration messages in multiple connections include, but are not limited to:

[0111] a) SN modifications (initiated by MN / SN) are used to modify, establish (add), or release (remove) bearer contexts (configurations / features) to transfer bearers to or from SN 104, or to modify other features of the UE context within the same SN 104. Examples include adding, modifying, or releasing SCG bearers and SCG RLC bearers for segmented bearers, and configuration changes for MCG bearers used for SN termination. A bearer is a data tunnel associated with a termination point in the RAN or core network. Modifications to a bearer may include changing the termination point (e.g., from MN to SN), changing the mapping of Quality of Service (QoS) flows to radio bearers, changing the logical channel identifier, changing RLC bearer features (including timers), and changing the RLC mode (e.g., changing the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and RLC features).

[0112] b) SN change (initiated by MN / SN) to transfer the UE context from source SN 104 to target SN 114, and to change the SCG configuration in UE100 from source SN 104 to the configuration of target SN 114.

[0113] c) Inter-MN handover (with / without MN-initiated SN change) to transfer context data from source MN 102 to target MN 112, while the context at SN 104 is maintained or moved to another SN 114. During the inter-MN handover, target MN 112 may decide whether to maintain or change source SN 104, or release source SN 104.

[0114] Figure 4 This is a message sequence diagram illustrating an example reconfiguration message that includes an SN modification request initiated by the SN (without the MN participating). Since SN 104 remains unchanged, this is referred to as an intra-SN reconfiguration message.

[0115] This reconfiguration message can be used to modify the configuration of SN 104 without requiring coordination with MN 102. This includes adding, modifying, and releasing SCG Scells, as well as changing PSCells, without altering SN 104. In at least the examples described below, the reconfiguration message includes PSCell changes.

[0116] In operation 401, SN 104 sends an RRC reconfiguration message ('NRRRCConnectionReconfiguration') to UE 100. This message can be sent via a bearer such as Signal Radio Bearer 3 (SRB3). UE 100 executes the RRC reconfiguration message to modify (e.g., replace / update) its stored configuration. If UE 100 cannot comply with at least a portion of the configuration included in the RRC reconfiguration message, UE 100 may execute a reconfiguration failure procedure.

[0117] In operation 403, if instructed by SN 104, UE 100 performs access to the new target PSCell ('random access procedure'). This procedure may include synchronization toward the target PSCell of SN 104. Performing access may include a RACH procedure (random access channel procedure).

[0118] In operation 405, UE 100 sends a reply ('NR RRCConnectionReconfigurationComplete') to SN 104, reporting that the configuration of the reconfiguration message has been applied (e.g., reporting that UE 100 has modified its stored configuration to the new configuration enabled by the RRC reconfiguration message).

[0119] In at least some examples, the reconfiguration message can be a conditional reconfiguration message. This is in Figure 5 It is shown in the middle, Figure 5 The illustration shows an example of a conditional PSCell change (CPC). Like... Figure 4 Similarly, the reconfiguration message shown in the diagram is an SN modification request initiated by the SN (without the MN participating).

[0120] Operation 501 involves UE 100 sending measurements ('measurement reports') to SN 104. These measurements may include signal power and / or signal quality measurements, such as Reference Signal Received Power (RSRP) or Reference Signature Received Quality (RSRQ). After receiving the measurements from UE 100, source SN 104 can prepare multiple candidate target PSCells within the same SN 104 based on these measurements. The term "source" means the currently serving node or cell. Preparing candidate target PSCells may include reserving resources, such as RACH resources (contention-free random access preamble), Cell Radio Network Temporary Identifier (C-RNTI), or radio resources for guaranteed bit rate service, etc.

[0121] Operation 503 involves the source PSCell sending an RRC reconfiguration message ('RRC(Connection)Reconfiguration') to UE 100. This includes sending one or more CPC execution conditions to UE 100, and sending the configuration of one or more candidate PSCells to UE 100. CPC execution conditions can be, for example, offset-based and / or threshold-based. Offset-based conditions can be satisfied when Mt > Ms + Offset, where Mt is the measurement of the target PSCell, Ms is the measurement of the serving PSCell, and Offset is the configured offset. Threshold-based conditions can be satisfied when Ms < threshold 1 (Ms becomes worse than threshold 1) and Mt > threshold 2 (Mt becomes better than threshold 2). Both offset and threshold methods can be applied simultaneously, and a CPC execution condition can be satisfied if at least one of them is satisfied.

[0122] In operation 504, UE 100 sends a reply ('RRC(Connection)ReconfigurationComplete') to SN 104, reporting that the reconfiguration has been applied. Figure 5 In the process, a report that the reconfiguration has been applied is sent before the CPC execution conditions are met. The term "application" does not mean that the UE has completed the instruction to execute the RRC reconfiguration message (e.g., CPC execution conditions).

[0123] Operation 505 includes UE 100 determining that the CPC execution conditions are met. For example, UE 100 may determine that a specific cell of SN 104 meets the execution conditions and may select that cell as the new PSCell.

[0124] Operation 507 is similar to operation 403 and is executed depending on the fulfillment of the conditions.

[0125] Operation 509 is similar to operation 504, but is sent to a new PSCell, indicating that the UE has completed the CPC execution process (e.g., UE 100 has executed operation 507).

[0126] In the above Figure 4 and Figure 5 In both cases, MN 102 is unaware that UE 100 is performing a PSCell change. Therefore, when UE 100 is performing an existing RRC reconfiguration message #1 (PSCell change), UE 100 continues radio communication with MN 102 and can receive the new RRC reconfiguration message #2 from MN 102.

[0127] One approach is to store the new RRC reconfiguration message #2 for UE 100, continue executing the existing RRC reconfiguration message #1 (PSCell changed), and then apply the new RRC reconfiguration.

[0128] The problem with the above method is that UE 100 may not comply with the new RRC reconfiguration message received from MN 102, because in some cases, it is not possible to execute a new RRC reconfiguration message after UE 100 has already performed a PSCell change. This will cause UE 100 to perform a re-establishment as defined in 3GPP TS 36.331 Release 15 (5.3.5.5). This problem exists in... Figure 6 It is shown in the middle.

[0129] Operations 601, 603, 604, and 605 involve existing reconfiguration message #1 and correspond to... Figure 5 Operations 501, 503, 504, and 505. Alternatively, the existing reconfiguration message #1 can be unconditional, such as... Figure 4 As defined in operations 401 and 403.

[0130] Operation 607 includes MN 102 determining to send RRC reconfiguration message #2 ('MN decides RRCReconfiguration') to UE 100 without knowing the existing RRC reconfiguration message #1. In the first example, the new RRC reconfiguration message #2 is an SN modification procedure initiated by MN. In the second example, the new RRC reconfiguration message #2 is an SN modification procedure initiated by SN (with MN participation).

[0131] Operation 609 includes MN 102 sending an RRC reconfiguration message #2 ('RRC(Connection)Reconfiguration#2') to UE 100. The RRC reconfiguration message #2 may or may not be conditional.

[0132] Operation 611 includes UE 100 receiving and storing RRC reconfiguration message #2 ('UE stores RRC(Connection)Reconfiguration#2').

[0133] Operation 613 includes UE 100 performing access to the new target PSCell as part of the execution of its ongoing existing RRC reconfiguration message #1 ('Random Access Procedure').

[0134] Operation 615 is similar to the previously described operation 509.

[0135] In operation 617, UE 100 fails to comply with RRC reconfiguration message #2. Therefore, in operation 619, UE 100 may perform an RRC re-establishment, which could result in service interruption for the user.

[0136] Below is a non-exhaustive example of when UE 100 cannot comply with the new RRC reconfiguration message #2 after a change in PSCell.

[0137] Example 1: RRC reconfiguration message #2 includes an SN modification initiated by the MN without changing SN104 or MN 102, to perform a modification such as modifying the SCG bearer X. MN 102 first sends an SgNB Modification Request message to SN 104. SN104 responds with an SgNB Modification Request Acknowledge message containing the new SCG radio configuration, allowing MN 102 to provide the new SCG radio configuration to UE100 (operations 609, 611). After UE 100 has performed the PSCell change of the existing RRC reconfiguration message #1 (operation 613), the new target PSCell of RRC reconfiguration message #2 may have released the SCG bearer X and therefore cannot be modified. UE 100 performs a re-establishment because it cannot comply with the new RRC reconfiguration message #2. The solution for Example 1 will be discussed later. Figure 8 To describe.

[0138] Example 2: RRC reconfiguration message #2 includes an SN change initiated by the MN without an MN change, to perform an inter-SN change from source SN1104 to target SN2 114. In this example, MN 102 sends an SgNB / SN Addition Request message to SN2 114. SN2 114 responds with an SgNB / SN Addition Request Acknowledge message, which includes the configuration that MN 102 can then provide to UE 100. SN2's response may include an indication of whether to provide UE 100 with a full configuration or an incremental configuration. Incremental configuration depends on a reference configuration stored in UE 100, while full configuration does not depend on the reference configuration. Incremental configuration is an incremental update that provides only the changed portion of the configuration to UE 100. UE 100 applies these portions on top of the existing reference configuration (e.g., SCG configuration) to save time and bandwidth. In contrast, full configuration includes the entire configuration. If RRC reconfiguration message #2 includes incremental configuration, UE 100 may not be able to apply the incremental configuration on top of the new reference configuration (e.g., a new source SCG configuration) after an existing RRC reconfiguration message #1 has been executed (completed). For example, the incremental configuration might request UE 100 to modify the SCG bearer X that has been released by the new source SN. UE 100 performs a re-establishment. The solution for Example 2 will be discussed later. Figure 9 To describe.

[0139] Example 3: RRC reconfiguration message #2 includes an inter-MN handover with / without SN change, performing an inter-MN change from MN1 102 to MN2 112 and an inter-SN change from SN1 104 to SN2 114. In this example, MN1 102 sends a Handover Request message to MN2 112. MN2 112 then obtains the configuration from SN2 114 and responds to MN1 102 with a Handover Request Acknowledge, which includes the configuration that MN1 102 can provide to UE 100. Similar to Example 2, incremental configuration may fail. The solution for Example 3 will be discussed later. Figure 10 To describe.

[0140] Another issue is that the new RRC reconfiguration message #2 provided by MN1 102 can sometimes have a higher priority than executing the existing RRC reconfiguration message #1 (e.g., PSCell change). This can happen, for example, if MN1 102 wants to trigger a PCell change (inter-MN or intra-MN handover). Waiting until the PSCell change is complete before triggering the PCell change can lead to a radio link failure (RLF).

[0141] In the example, the network node (PCell in MN 1 or PSCell in SN 1) can instruct the UE whether a new RRC reconfiguration received from MN 1 during a PSCell change should be discarded or applied after the PSCell change (conditional or traditional) is completed. This decision can be made by the network node based on whether the UE can comply with the new RRC reconfiguration after the PSCell change. The UE can notify the source PCell in MN whether it has discarded the new RRC reconfiguration after the PSCell change is completed.

[0142] In another example, the network node (PCell in MN 1 or PSCell in SN 1) indicates to the UE whether the execution of the new RRC reconfiguration can take precedence over the PSCell change. In this example, if the network indicates to the UE that the new RRC reconfiguration should take precedence, the UE terminates the execution of the PSCell change and executes the new RRC reconfiguration. The UE can also indicate to the network (PCell in MN 1 or PSCell in SN 1) the termination of the PSCell change.

[0143] This disclosure presents various methods for reducing the need for connection re-establishment in multi-connectivity scenarios, through various aspects and examples. These methods collectively include identifying flags and sending them to the UE 100, which influence / determine the decisions to be made.

[0144] This flag indicates how UE 100 should process RRC reconfiguration message #2 during or after UE 100 executing an existing RRC reconfiguration message #1, where the initiator of message #2 is not involved in or unaware of the existing RRC reconfiguration message #1. Examples of such an existing RRC reconfiguration message #1 include a PSCell change initiated by the SN (without the MN involved), such as... Figure 4-5 Defined in [the document / reference].

[0145] Figure 7 This indicates a first general method, wherein the flag may indicate that the second RRC reconfiguration message #2 is discarded after the first RRC reconfiguration message #1 is executed, or the second RRC reconfiguration message #2 is executed after the first RRC reconfiguration message #1 is executed. Figure 11 This indicates the second general method, where the flag can indicate priority and thus interrupt the ongoing execution of the existing RRC reconfiguration message #1.

[0146] In at least some examples, the way the flag is determined may depend on whether RRC reconfiguration message #2 is an SN modification, SN change, and / or MN change. Figure 8-10 These individual cases (according to) Figure 7 (Methods).

[0147] from Figure 7 Initially, operations 701, 703, 704, 705, and 707 involve existing CPC reconfiguration messages #1 and correspond to... Figure 6 Operations 601, 603, 604, 605, and 607. Alternatively, the existing reconfiguration message #1 can be unconditional, such as... Figure 4 As defined in operations 401 and 403.

[0148] Operation 709 includes MN 102 sending RRC reconfiguration message #2 (including reconfiguration message information) to UE 100, and also includes MN 102 sending a flag to UE 100 indicating the action to be taken by UE 100 after executing an existing RRC reconfiguration message. This flag is configured to distinguish between:

[0149] 'Discard' = Discard RRC reconfiguration message #2 without starting the execution of RRC reconfiguration message #2; or

[0150] 'execute' = Execute RRC reconfiguration message #2 after executing the existing RRC reconfiguration message #1.

[0151] In a broader sense, the term "flag" refers to an "indicator" of which action to take. This flag can be a Boolean value of 0 or 1. One value indicates 'discard', and the other indicates 'execute'.

[0152] Various methods exist for determining how the flag should be set. Some examples involve providing an entity (e.g., MN or SN) with knowledge of both messages #1 and #2, enabling that entity to determine whether UE100 will be able to comply with RRC reconfiguration message #2 after executing the known existing reconfiguration message #1 (compliance determination). Some examples involve determining whether the new configuration will be an incremental or full configuration, where, in the case of incremental configuration, the flag can indicate 'discard'. Use cases for these examples will be described later.

[0153] After operation 709, UE 100 receives the flag and can store it for later review after executing an existing RRC reconfiguration message #1 (e.g., after operations 711 and 713 (corresponding to operations 613, 615)). UE 100 can then perform the action indicated by the value of the flag.

[0154] In the case of CPC, this flag can be specific to each prepared target PSCell within the same SN 104, as they can have different configurations. For example, if the existing RRC reconfiguration message #1 is a CPC, the transmission flags can include multiple flags associated with transmission of different cells within the same SN 104, where the different cells have different configurations. Therefore, if the execution of the first RRC reconfiguration message #1 involves selecting a first cell as the new PSCell, the UE 100 can check the first flag, and if the execution of the first RRC reconfiguration message #1 involves selecting a different cell as the new PSCell, the UE 100 can check the second flag.

[0155] If UE 100 is not currently executing an existing RRC reconfiguration message #1, UE 100 may not check the flag. For example, if RRC reconfiguration message #2 is received while UE 100 is not executing an existing RRC reconfiguration message #1, UE 100 may execute RRC reconfiguration message #2 without performing the action indicated by the flag, such as not checking the flag. This includes whether RRC reconfiguration message #2 was received between operations 704 and 705 while waiting for the CPC execution conditions to be met.

[0156] In at least some examples, the UE 100 can check the flag when the existing RRC reconfiguration message #1 does not involve an MN. In at least some examples, the flag can be checked when the existing RRC reconfiguration message #1 includes a PSCell change (without an MN).

[0157] Return to reference Figure 7 If the flag indicates that the new RRC reconfiguration message #2 is to be executed after the first RRC reconfiguration message #1, then UE 100 executes the new RRC reconfiguration message #2 at operation 715.

[0158] At operation 717, UE 100 sends a report of the action taken by UE 100 to MN 102. In this case, the action is to execute a new RRC reconfiguration message #2 after executing the existing RRC reconfiguration message #1.

[0159] If the flag indicates that the new RRC reconfiguration message #2 should be discarded, then UE 100 discards (e.g., ignores) the new RRC reconfiguration message #2 at operation 719 without executing message #2. At operation 721, UE 100 sends a report of the action taken by UE 100 to MN 102. In this case, the action is discarding.

[0160] Figure 8-10 It details various measures targeting Figure 7 Use cases for the method.

[0161] Figure 8 Involving Figure 7 The method in the first scenario. Figure 8 In the RRC reconfiguration message #2, there is an MN-initiated SN modification (without changing SN 104 or MN 102) to perform a modification such as modifying the SCG bearer X. The existing reconfiguration message #1 includes a PSCell change, optionally, where the change is a CPC as shown.

[0162] exist Figure 8 In the diagram, operations 801, 803, 804, and 805 correspond to operations 701, 703, 704, and 705. Operation 807 corresponds to operation 707. Figure 8 Examples include additional operations 809 and 811 for obtaining the flag (executed after 807 and before 813).

[0163] At operation 809, MN 102 sends a query to service SN 104, which will be affected by RRC reconfiguration message #2. SN 104 is a node that can initiate an existing RRC reconfiguration message #1 (without MN involvement). This query can be a modification request. If SN 104 is a gNB, then the modification request can be an SgNB modification request. At least because request #2 is an SN modification (without SN / MN changes), this query is sent to service SN 104.

[0164] In response to operation 809, after knowing about SN 104, SN 104 makes a compliance determination as to whether UE 100 will be able to comply with RRC reconfiguration message #2 after executing the existing reconfiguration message #1. Since SN 104 knows about both messages #1 and #2, SN 104 is able to make this decision. The knowledge of message #2 comes from the SgNB modification request. SN 104 knows about the ongoing RRC reconfiguration message #1 because SN 104 sent the ongoing message #1 and may have received a reply (e.g., operation 804). In this example, SN 104 may set a flag.

[0165] At operation 811, SN 104 sends a response to MN 102, such as an acknowledgment message (e.g., an SgNB Modification Response). Sending this response may include sending a reconfiguration message to MN along with flags indicating a new configuration for message #2 (e.g., a new SCG configuration for SN2 114, including the target PSCell).

[0166] Having obtained the flag, MN 102 can then forward the flag obtained from SN 104 and the reconfiguration message information of the new RRC reconfiguration message #2 to UE 100 (operation 813). MN 102 may not need to know or look up the flag / compliance determination made by SN 104. Subsequent operations 815, 817, 819, 821, 823, and 825 correspond to operations 711, 713, 715, 717, 719, and 721.

[0167] In an alternative example, MN 102 can obtain the flag by receiving a compliance determination from the SN that enables the flag to be set. MN 102 then sets the flag.

[0168] In another example, for a new RRC reconfiguration #2 that includes SCG modifications, the source PSCell in SN 1 can make a decision about the flag because it provides the new SCG configuration (containing these modifications) and knows the configuration of the new target PSCell in the same SN.

[0169] In the example, for a new RRC reconfiguration #2 (initiated by the MN or SN) involving an inter-SN PSCell change, the source PCell in MN 1 can make a decision about this flag based on an indication received from the target PSCell in SN2 regarding whether to apply a full or incremental configuration for the PSCell change. In this paper, in the case of full configuration, the source PCell in MN 1 can configure the UE to apply the new RRC reconfiguration after the PSCell change.

[0170] In another alternative example, MN 102 can set this flag by receiving information associated with an existing reconfiguration message from SN 104. For example, SN 104 can notify the source MN 102 about existing PSCell changes (CPC or unconditional) that have been provided to UE 100. This information can indicate 1) the configuration of the existing configuration message and / or 2) whether the existing configuration message includes full or incremental configuration.

[0171] In another example, for a new RRC reconfiguration #2 involving inter-MN handover (with / without MN-initiated SN change), the source PCell in MN 1 can make a decision regarding this flag: In one embodiment, the new target MN2 notifies the source MN 1 whether the new target PSCell in SN2 is configured with a full or incremental configuration relative to the source PSCell in SN 1. In the case of full configuration, MN 1 can configure the UE to apply the new RRC reconfiguration after the PSCell change.

[0172] Figure 9 Involving Figure 7 The method in the second scenario. Figure 9 In the RRC reconfiguration message #2, there is an MN-initiated SN change (without an MN change) to perform an inter-SN change from source SN1 104 to target SN2 114. The existing reconfiguration message #1 includes a PSCell change, optionally, where the change is a CPC as shown.

[0173] exist Figure 9 In the diagram, operations 901, 903, 904, 905, and 907 correspond to operations 701, 703, 704, 705, and 707. Figure 9 Examples include additional operations 909 and 911, which occur after 907 and before 913.

[0174] At operation 909, MN 102 sends a query to the target SN (SN2 114) that will be affected by RRC reconfiguration message #2. This query is sent to SN2 114 because message #2 includes an SN change to SN2 114. This query could be an add request for adding SN2 114. If SN2 114 is a gNB, then the add request could be an SgNB add request (SgNBAddition Request).

[0175] At operation 911, SN2 114 sends a response to MN 102, such as an acknowledgment message (e.g., an SgNB / SN add request acknowledgment). Sending this response may include sending a reconfiguration message indicating the new configuration for message #2 (such as a new SCG configuration for SN2 114, including the target PSCell). This reconfiguration message may include an indication of whether to provide UE 100 with a full configuration or incremental configuration.

[0176] At operation 913, MN 102 determines whether to provide UE 100 with a full configuration or incremental configuration, along with a new RRC reconfiguration message #2. In this example, MN 102 obtains this flag by setting the flag itself. If incremental configuration is to be provided, the flag can be set to 'discard'. If full configuration is to be provided, the flag can be set to 'execute'. In an alternative example, this flag can be set by another node that has knowledge of the full / incremental configuration.

[0177] In some examples, source SN1 104 can send a reconfiguration message to MN 102 indicating the configuration associated with the existing RRC reconfiguration message #1 (e.g., the configuration of the target PSCell of SN1 104). This allows MN 102 to determine whether UE 100 will not comply with the new RRC reconfiguration message #2 (if executed after the existing RRC reconfiguration message #1). Therefore, if MN 102 can determine that compliance is possible, incremental configuration can sometimes be 'execute'.

[0178] In operation 915, MN 102 sends a new RRC reconfiguration message #2 (including reconfiguration message information for message #2) and the flag to UE 100. Subsequent operations 917, 919, 921, 923, 925, and 927 correspond to 711, 713, 715, 717, 719, and 721.

[0179] Figure 10 Involving Figure 7 The method in the third scenario. Figure 10In the RRC reconfiguration message #2, an inter-MN handover with an MN-initiated SN change is included to perform an inter-MN change from MN1 102 to MN2 112 and an inter-SN change from SN1 104 to SN2 114. Alternatively, message #2 may not include an SN change. The existing reconfiguration message #1 includes a PSCell change, optionally wherein the change is a CPC as shown.

[0180] exist Figure 10 In the diagram, operations 1001, 1003, 1004, 1005, and 1007 correspond to operations 701, 703, 704, 705, and 707. Figure 10 Examples include additional operations 1009, 1011, 1013, and 1015, which occur after 1007 and before 1017.

[0181] At operation 1009, MN1 102 sends a query to target MN2 112, which is the node affected by RRC reconfiguration message #2. This query could be a switch request message. At least because message #2 includes MN changes, this query is sent to MN2 112.

[0182] If an inter-SN change is to be performed, operations 1011 and 1013 are executed, which include the same type of query and response as operations 909 and 911 as previously described, except that they are transmitted between MN2 112 and the target SN2 114. This allows MN2 112 to obtain reconfiguration message information indicating the new configuration for message #2 (e.g., the SCG configuration of SN2 114). The response from SN2 may include an indication of whether to provide UE 100 with a full configuration or incremental configuration.

[0183] At operation 1015, MN2 112 sends a response to the query to MN1 102 (e.g., a handover request confirmation message), and MN1 102 may provide UE 100 with the configuration as part of RRC reconfiguration message #2. MN2's response may also include an indication of whether to provide UE 100 with a full or incremental configuration. This enables MN1 102 to perform operation 1017 (setting flags), equivalent to operation 913: discard if incremental, execute if full. Alternatively, another node may perform compliance determination and / or flag determination.

[0184] In operation 1019, MN1 102 sends a new RRC reconfiguration message #2 (including reconfiguration message information) and the flag to UE 100. Subsequent operations 1021, 1023, 1025, 1027, 1029, and 1031 correspond to 711, 713, 715, 717, 719, and 721.

[0185] Figure 11 This indicates a second general method, where a flag can indicate whether the new RRC reconfiguration message #2 should be prioritized. Prioritizing the execution of the new RRC reconfiguration message #2 over the existing RRC reconfiguration message #1 includes terminating the ongoing execution of the existing reconfiguration message #1 (e.g., CPC / PSCell change within the SN) and executing the new RRC reconfiguration message #2. UE 100 can indicate to one or more nodes (e.g., MN 102 or SN 104) that the existing RRC reconfiguration message has been terminated.

[0186] In 11, operations 1101, 1103, 1104, 1105, and 1107 correspond to operations 601, 603, 604, 605, and 607.

[0187] Operation 1109 includes MN 102 sending RRC reconfiguration message #2 to UE 100, and also includes MN 102 sending a flag to UE 100 indicating the action to be taken by UE 100 during or after executing the existing RRC reconfiguration message #1. This flag is configured to distinguish between:

[0188] 'Prioritize' = to prioritize the execution of the new RRC reconfiguration message #2 over the execution of the existing RRC reconfiguration message #1; or

[0189] As previously mentioned, 'discard' and / or 'execute'.

[0190] The example case where RRC reconfiguration message #2 should be of high priority is a PCell change, i.e., a switch within or between MNs. Therefore, this flag reduces the chance of an RLF.

[0191] After operation 1109, UE 100 can decode and check the flag without waiting for the existing RRC reconfiguration message #1 to complete.

[0192] If the flag is 'prioritize', UE 100 executes the new RRC reconfiguration message #2 at operation 1111. UE 100 first terminates the execution of the existing reconfiguration message #1 that is in progress, for example, by not executing operations 711 / 713.

[0193] If the new RRC reconfiguration message #2 includes an incremental configuration for serving SN 104, UE 100 can first restore its original SN configuration to provide the correct reference configuration for the new incremental configuration. Then, the increment is applied. This method involves UE 100 storing a recoverable copy of its original SN configuration during the execution of the existing RRC reconfiguration message #1. If the new RRC reconfiguration message #2 includes a full configuration, no restoration is required.

[0194] At operation 1113, UE 100 sends a reply to MN 102 that is similar to operation 713 but involves message #2 instead of message #1.

[0195] In some examples, UE 100 may send a report to one or more nodes that an existing RRC reconfiguration message #1 was terminated before completion (e.g., due to the priority of the new RRC reconfiguration message #2). At operation 1115, UE 100 sends this report to MN 102. At operation 1117, UE 100 sends this report to SN 104, which indicated message #1.

[0196] Operations 1113 and / or 1115 and / or 1117 can be sent as part of a Successful Handover Report as defined in 3GPP.

[0197] In at least some examples, another value for this flag indicates whether RRC reconfiguration message #2 should be discarded or applied after an existing reconfiguration message #1 has been completed (in... Figure 7-10 (Then). In one example, another value for this flag is 'discard'. In another example, another value for this flag is 'execute'. In yet another example, this flag can distinguish between the three described actions: 'prioritize', 'discard', and 'execute'. In some examples, this flag can distinguish between even more actions than those described herein.

[0198] In some, but not all, examples, the existing RRC reconfiguration message #1 can be restarted after the UE100 has executed the prioritized RRC reconfiguration message #2 (e.g., after operation 1111 / 1115 / 1117).

[0199] although Figure 11 The 'prioritize' method is described as beneficial for PCell changes, but this method can be applied to other scenarios.

[0200] The two methods mentioned above ( Figure 11right Figure 7-10 This is not necessarily an alternative. For example, UE 100 can immediately check the flag to determine whether to wait before performing the action 'discard' or 'execute', or to perform the action 'prioritize' immediately.

[0201] Figure 12 The illustration shows method 1200 that can be executed at one or more nodes as described herein. The method includes: during multiple connections,

[0202] At block 1202 (e.g., operation 709), reconfiguration message information associated with the reconfiguration message performed by UE 100 is transmitted (e.g., the reconfiguration message is transmitted); and

[0203] At block 1204 (e.g., operation 709), a flag indicating the action to be taken by UE 100 after UE 100 executes the existing reconfiguration message #1, or information causing the flag to be set (e.g., full / incremental configuration), is sent, wherein the flag is configured to distinguish between at least two of the following actions as previously defined: 'discard'; 'execute'; or 'prioritize'. In some examples, method 1200 is performed by an MN such as MN1 102, which sends both the reconfiguration message and the flag to the UE. Optionally, method 1200 may also include the previously... Figure 7-11 And one or more of the send / receive / determine operations of MN1 102 as described. MN1 102 can also be configured to perform the role of MN2 112 in sessions with other UEs.

[0204] Figure 13 The diagram shows that it can be used Figure 10 Method 1300, executed at an MN such as MN2 112, during inter-MN switching. This method includes, in the case of multiple connections:

[0205] At box 1302 (e.g., operation 1009), a query is received from the first (serving) MN 102, wherein the query is initiated by the first MN 102 sending a reconfiguration message for execution by the UE 100, wherein the reconfiguration message includes an inter-MN handover from the first MN 102 to the target MN 112;

[0206] At block 1304 (e.g., operations 1011, 1013), obtain the configuration information associated with the reconfiguration message; and

[0207] At block 1306 (e.g., operation 1015), based on the configuration information, a response to the query is sent to enable the first MN 102 to send a flag indicating the action to be taken by the UE 100 during or after the UE 100 executes an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions as previously defined: 'discard'; 'execute'; or 'prioritize'. Optionally, method 1300 may also include the previously... Figure 7-11 And one or more of the send / receive / determine operations of MN2 112 as described. MN2112 can also be configured to perform the role of MN1 102 in sessions with other UEs.

[0208] Figure 14 The illustration shows method 1400 that can be executed at an SN such as SN1 104. The method includes: during multiple connections,

[0209] At box 1402, a query is received from master node 102, wherein the query indicates a decision initiated by the master node to send a reconfiguration message for execution by UE 100; and

[0210] At box 1404, a response to the query is sent, wherein the response includes a flag indicating an action to be taken by UE 100 during or after UE 100 executes an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions as previously defined: 'discard'; 'execute'; or 'prioritize'. Optionally, method 1400 may also include a previous... Figure 7-11 And one or more of the SN1 104 send / receive / confirm operations described. SN1 104 can also be configured to perform the role of SN2 114 in sessions with other UEs.

[0211] Figure 15 The illustration shows method 1500 that can be performed at UE 100. This method includes: during multiple connections,

[0212] At box 1502, a reconfiguration message for UE 100 to perform is received;

[0213] At box 1504, a flag indicating the action to be taken by UE 100 during or after UE 100 performs an existing reconfiguration message is received; and

[0214] At box 1506, during or after the UE 100 executes an existing reconfiguration message, the action indicated by the flag is executed, wherein the flag is configured to distinguish between at least two of the following actions as previously defined: 'discard'; 'execute'; or 'prioritize'. Optionally, method 1500 executed at mobile device 100 may also include the previously... Figure 7-11 And one or more of the send / receive / determine operations of UE 100 as described.

[0215] Figure 16 An example of controller 1600 is illustrated. Controller 1600 can be implemented as a controller circuit. Controller 1600 can be implemented solely in hardware, have some aspects of software including only firmware, or can be a combination of hardware and software (including firmware).

[0216] like Figure 16 As shown, the controller 1600 can be implemented using instructions that enable / enable hardware functions, for example, by using executable instructions of a computer program 1606 in a general-purpose or special-purpose processor 1602. These instructions can be stored on a computer-readable storage medium (disk, memory, etc.) for execution by such processor 1602.

[0217] Processor 1602 is configured to read from memory 1602 and write to memory 1604. Processor 1602 may also include an output interface through which processor 1602 outputs data and / or commands and an input interface through which data and / or commands are input to processor 1602.

[0218] Memory 1604 stores a computer program 1606, including computer program instructions (computer program code), which controls the operation of device 2 when loaded into processor 1602. The computer program instructions of computer program 1606 provide logic and routines that enable the device to execute... Figure 4-15 The method shown is illustrated. By reading memory 1604, processor 1602 is able to load and execute computer program 1606.

[0219] Therefore, the device 2 includes: at least one processor 1602; and at least one memory 1604 including computer program code, the at least one memory 1604 and the computer program code being configured together with the at least one processor 1602 to cause the device 2 to perform at least any one or more methods described herein.

[0220] Device 2 may be a base station device that implements at least a portion of the functions of a base station. For example, device 2 may be a gNB device or an eNB device. Base station device 2 may be used as a node in multiple connections. For example, base station device 2 may be configured to implement at least a portion of the functions of MN102, 112 or SN 104, 114.

[0221] like Figure 17 As shown, computer program 1606 can reach device 2 via any suitable transmission mechanism 1700. Transmission mechanism 1700 can be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a storage device, a recording medium such as an optical disc read-only memory (CD-ROM) or digital versatile optical disc (DVD) or solid-state storage, or a manufactured product that includes or tangibly embodies computer program 1606. The transmission mechanism can be a signal configured to reliably transmit computer program 1606. Device 2 can propagate or transmit computer program 1606 as computer data signals.

[0222] Provided for causing a device (e.g., a computer) to perform at least the following operations or for performing at least the following operations. Figure 4-15 Computer program instructions for any one or more of the methods shown.

[0223] Computer program instructions can be included in a computer program, a non-transitory computer-readable medium, a computer program product, or a machine-readable medium. In some, but not all, examples, computer program instructions can be distributed across more than one computer program.

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

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

[0226] References to “computer-readable storage medium,” “computer program product,” “tangible computer program,” or “controller,” “computer,” “processor,” etc., should be understood to encompass not only computers with different architectures such as single / multiple processor architectures and serial (von Neumann) / parallel architectures, but also special-purpose circuits such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other processing circuits. References to computer programs, instructions, code, etc., should be understood to encompass software for programmable processors, or firmware that may include programmable content such as hardware devices that may include instructions for processors, or configuration settings for fixed-function devices, gate arrays, or programmable logic devices, etc.

[0227] As used in this application, the term "circuit" may refer to one or more of the following:

[0228] (a) Hardware circuit implementation only (such as implementation of analog and / or digital circuits only);

[0229] (b) A combination of hardware circuitry and software, such as (if applicable):

[0230] (i) a combination of analog and / or digital hardware circuitry with software / firmware; and

[0231] (ii) Any part of a hardware processor having software (including digital signal processors, software, and memory, which work together to enable a device such as a mobile phone or server to perform various functions); and

[0232] (c) Hardware circuitry and / or processors, such as microprocessors or parts thereof, which require software (e.g., firmware) to operate, but may be absent when operation does not require software.

[0233] This definition of "circuit" applies to all uses of the term in this application, including its use in any claim. As another example, as used in this application, the term "circuit" also covers only the implementation of hardware circuitry or processors and their accompanying software and / or firmware. The term "circuit" also covers (e.g., and if applicable, baseband integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices).

[0234] Figure 4-15 The boxes shown may represent steps in the method and / or code segments in computer program 1606. The illustration of a particular order of boxes does not imply a desired or preferred order for these boxes, but rather that the order and arrangement of the boxes can be varied. Furthermore, some boxes may be omitted.

[0235] The term "operably coupled" means that any number of intermediate elements or combinations thereof can be present (including no intermediate elements).

[0236] Where structural features have been described, they can be used as a substitute for components that perform one or more functions of those structural features, whether or not the function or those functions are explicitly described or implicitly described.

[0237] The examples described above enable applications of components such as: automotive systems; telecommunications systems; electronic systems, including consumer electronics; distributed computing systems; media systems for generating or rendering media content, including audio, visual, and audiovisual content, as well as mixed, mediated, virtual, and / or augmented reality; personal systems, including personal medical systems or personal health / fitness systems; navigation systems; user interfaces, also known as human-machine interfaces; networks, including cellular, non-cellular, and optical networks; self-organizing networks; the Internet; the Internet of Things; virtualized or non-virtualized networks; and related software and services.

[0238] The term “comprising” as used herein has an inclusive rather than exclusive meaning. That is, any statement “X includes Y” means that X may include only one Y or may include more than one Y. If the intention is to use “comprising” with an exclusive meaning, it will be made clear in the context by referring to “only one…” or by using “consisting of…”.

[0239] Various examples have been referenced in this description. Descriptions of features or functions for an example indicate that those features or functions exist in that example. Whether explicitly stated or not, the use of the terms "example," "for example," "may," or "can" in the text indicates that such a feature or function exists at least in the described example, whether or not it is described as an example, and that such a feature or function may, but is not required to, exist in some or all other examples. Therefore, "example," "for example," "may," or "can" refers to a specific instance of a class of examples. The properties of an instance may be properties of that instance alone, properties of the class of instances, or properties of subclasses of the class that include some but not all instances of that class. Therefore, it is implicitly disclosed that features described for one example but not for another can be used in other examples as part of a working composition, but are not required to be used in other examples.

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

[0241] The features described in the preceding description can be used in combinations other than those explicitly described above.

[0242] Although functions have been described with reference to certain features, these functions can be performed by other features, whether or not they are described.

[0243] Although features have been described with reference to some examples, these features may also exist in other examples, whether or not they are described.

[0244] The terms “one” or “the” as used herein have an inclusive rather than exclusive meaning. That is, any reference to “X includes one / the Y” indicates that “X may include only one Y” or “X may include more than one Y”, unless the context clearly indicates otherwise. If the intention to use “one” or “the” with an exclusive meaning is to do so, it will be clearly stated in the context. In some contexts, “at least one” or “one or more” may be used to emphasize an inclusive meaning, but the absence of these terms should not be construed as indicating any non-exclusivity.

[0245] The presence of a feature (or combination of features) in a claim is a reference to that feature (or combination of features) itself, and also a reference to a feature (equivalent feature) that achieves substantially the same technical effect. Equivalent features include, for example, features that are variations and achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.

[0246] This description has referenced various examples using adjectives or adjective phrases to describe the characteristics of the examples. This description of the characteristics of the examples indicates that the characteristic is exactly the same as described in some examples, and substantially the same as described in others.

[0247] Although the foregoing description attempts to point out those features considered important, it should be understood that an applicant may seek protection by means of the claims for any patentable features or combinations thereof shown herein with reference to the accompanying drawings and / or the drawings, whether or not they have been emphasized.

Claims

1. A method executed by a master node in a multi-connection setup, comprising: During multiple connections, Send a reconfiguration message to the user equipment for execution by the user equipment, the user equipment applying multiple connections to the primary node and at least one secondary node, the reconfiguration message updating the configuration stored in the user equipment when executed by the user equipment; as well as Send a flag to the user equipment indicating an action to be taken by the user equipment during or after executing an existing reconfiguration message previously received by the user equipment from the at least one secondary node, wherein the flag is configured to distinguish between at least two of the following actions: Discard the reconfiguration message; Execute the reconfiguration message after executing the existing reconfiguration message; or The execution of the reconfiguration message takes precedence over the execution of existing reconfiguration messages.

2. A method performed by a user equipment that applies multiple connections to a primary node and at least one secondary node, comprising: During multiple connections, The master node receives a reconfiguration message for execution by the user equipment, which, when executed by the user equipment, updates the configuration stored in the user equipment. Receive from the master node a flag indicating the action to be taken by the user equipment during or after executing an existing reconfiguration message previously received by the user equipment from the at least one secondary node; as well as The action indicated by the flag is performed during or after the user equipment executes the existing reconfiguration message. The flag is configured to distinguish between at least two of the following actions: Discard the reconfiguration message; Execute the reconfiguration message after executing the existing reconfiguration message; or The execution of the reconfiguration message takes precedence over the execution of existing reconfiguration messages.

3. The method according to claim 2, wherein, The flag is configured to depend on whether the user equipment will be able to comply with the reconfiguration message after executing an existing reconfiguration message.

4. The method according to claim 3, wherein, The actions include: determining that the user equipment cannot comply with the reconfiguration message after executing the existing reconfiguration message, discarding the reconfiguration message, or The determination indicates that the user equipment can comply with the reconfiguration message after executing the existing reconfiguration message, and executes the reconfiguration message after executing the existing reconfiguration message.

5. The method according to claim 2 or 3, wherein, The flag is configured to depend on whether the reconfiguration message includes an indication of incremental configuration or full configuration, wherein the incremental configuration depends on a reference configuration stored in the user equipment that can be changed by existing reconfiguration messages, and wherein the full configuration does not depend on the reference configuration stored in the user equipment.

6. An apparatus for serving as at least a portion of a master node in a multi-connection setup, comprising components for performing the following operations: Sending a reconfiguration message to a user equipment (UE) for execution by the UE, the UE applying multiple connections to the primary node and at least one secondary node, the reconfiguration message updating the configuration stored in the UE when executed by the UE; and Send a flag to the user equipment indicating the action to be taken by the user equipment during or after executing an existing reconfiguration message previously received by the user equipment from the at least one secondary node, wherein, The flag is configured to distinguish between at least two of the following actions: Discard the reconfiguration message; Execute the reconfiguration message after executing the existing reconfiguration message; or The execution of the reconfiguration message takes precedence over the execution of existing reconfiguration messages.

7. A user equipment that applies multiple connections to a primary node and at least one secondary node, comprising components for performing the following operations: The master node receives a reconfiguration message for execution by the user equipment, which, when executed by the user equipment, updates the configuration stored in the user equipment. Receive from the master node a flag indicating the action to be taken by the user equipment during or after executing an existing reconfiguration message previously received by the user equipment from the at least one secondary node; as well as The action indicated by the flag is performed during or after the user equipment executes the existing reconfiguration message. The flag is configured to distinguish between at least two of the following actions: Discard the reconfiguration message; Execute the reconfiguration message after executing the existing reconfiguration message; or The execution of the reconfiguration message takes precedence over the execution of existing reconfiguration messages.

8. The user equipment according to claim 7, wherein, The flag is configured to depend on whether the user equipment will be able to comply with the reconfiguration message after executing an existing reconfiguration message.

9. The user equipment according to claim 8, wherein, The actions include: Based on the determination, the user equipment is instructed to discard the reconfiguration message if it cannot comply with the existing reconfiguration message after execution. The determination indicates that the user equipment can comply with the reconfiguration message after executing the existing reconfiguration message, and executes the reconfiguration message after executing the existing reconfiguration message.

10. The user equipment according to claim 8 or 9, wherein, The flag is configured to depend on whether the reconfiguration message includes an indication of incremental configuration or full configuration, wherein the incremental configuration depends on a reference configuration stored in the user equipment that can be changed by existing reconfiguration messages, and wherein the full configuration does not depend on the reference configuration stored in the user equipment.

11. A computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement the method according to any one of claims 1 to 5.

Images