Primary node, secondary node and method thereof
By introducing the SCG portion of the separate signaling radio bearer between MN and SN, the problem of SN being unable to recognize MCG faults is solved, enabling configuration adjustments during the rapid MCG recovery process and ensuring smooth signaling transmission.
Patent Information
- Application Number
- CN202080063213.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-07-29
- Filing Date
- 2020-06-10
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-06-10
AI Technical Summary
In radio communication systems, the secondary node (SN) cannot recognize the occurrence of a primary cell group (MCG) failure, which prevents timely configuration adjustments and affects the rapid MCG recovery process.
By introducing the SCG portion of the separate signaling radio bearer between the primary node (MN) and the secondary node (SN), the SN is allowed to receive indications related to MCG failures and send RRC messages through this signaling bearer to achieve recovery from MCG failures.
This enables the SN to promptly identify MCG faults, make corresponding configuration adjustments, ensure the smooth progress of the rapid MCG recovery process, and reduce interference with signaling transmission between the MN and the UE.
Smart Images

Figure CN114365531B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to radio communication systems, and in particular to recovery from a Master Cell Group (MCG) failure in multiple connectivity (eg dual connectivity). Background Art
[0002] The 3rd Generation Partnership Project (3GPP) is discussing fast recovery of MCG failure when multi-radio dual connectivity (MR-DC) is in progress (see, for example, non-patent documents 1 to 5). An MCG failure is, for example, a disconnection of a radio link (radio link failure (RLF)). In order to recover from an MCG failure when MR-DC is in progress, fast MCG recovery uses signaling between a master node (MN) and a user equipment (UE) via a secondary cell group (SCG) provided by a secondary node (SN). Therefore, fast MCG recovery enables the use of other methods other than radio resource control (RRC) connection reestablishment (such as an intra-MN handover process or an inter-MN handover process, etc.) to quickly recover the MCG link (or quickly recover from an MCG failure). In 5G NR, a process called "synchronous reconfiguration" is defined, which is used for handover and also for PSCell (i.e., primary SCG cell or primary and secondary cell) changes and SN changes in MR-DC. Intra-MN handover and inter-MN handover in this specification may involve the release of an SN of an MR-DC within the handover process. Inter-MN handover in this specification may include a role change between an MN and an SN. In the role change, the SN (and MN) of the MR-DC before the handover is changed to the MN (and SN) of the MR-DC during the handover.
[0003] The signaling required for fast MCG recovery (i.e., MN RRC messages) is transmitted between the MN and the UE via the SCG branch of the separate signaling bearer 1 (SRB1) or via SRB3. The separate SRB1 is an SRB between the MN and the UE used for RRC messages, and has a radio link control (RLC) bearer in the MCG and an RLC bearer in the SCG. The separate SRB1 supports transmission via the MCG and the SCG, and enables replication of the RRC protocol data units (PDUs) generated by the MN. However, since the MN RRC messages sent by the separate SRB1 are protected by the MN security key, the SN cannot read the content of the MN RRC messages, and thus the MNRRC messages are transparently sent to the UE. The RLC bearers in the MCG and SCG of the separate SRB are respectively referred to as the MCG branch (or MCG part) and the SCG branch (or SCG part). On the other hand, SRB3 is a direct SRB between the SN and the UE, which can be used by the SN to send SN RRC messages to the UE in the DC via the SCG cell. Incidentally, fast MCG recovery may be triggered (or performed) only after security at the access stratum (AS) layer has been activated and SRB2 and at least one DRB have been established.
[0004] Citation List
[0005] Non-patent literature
[0006] [Non-patent document 1] Ericsson: “Fast MCG recovery in MR-DC”, 3GPP TSG-RAN WG2#105 R2-1901414, February 2019
[0007] [Non-patent document 2] Ericsson: “Fast MCG recovery in (NG) EN-DC”, 3GPP TSG-RANWG2#105 R2-1901416, February 2019
[0008] [Non-patent document 3] Qualcomm Incorporated: “Fast Recovery from MCG failure”, 3GPP TSG-RAN WG2#105 R2-1900113, February 2019
[0009] [Non-patent document 4] Huawei, HiSilicon: “MCG failure recovery via split SRB1”, 3GPP TSG-RAN WG2#106 R2-1907493, May 2019
[0010] [Non-patent document 5] Huawei, HiSilicon: “Discussion on MCG failure recovery via SRB3”, 3GPP TSG-RAN WG2#106 R2-1907497, May 2019 Summary of the invention
[0011] Problem that the invention aims to solve
[0012] The inventors studied fast MCG recovery and found various problems. For example, in the case where the UE sends an MN RRC message (e.g., an MCG failure information message) indicating an MCG failure to the MN via the SCG branch of the separated SRB1, the SN cannot read the content of the MN RRC message. In other words, in the process for sending MCG failure information via the separated SRB1, the SN cannot be aware of the occurrence of the MCG failure. However, it may be useful for the SN to be aware of the occurrence of an MCG failure (or the execution of MCG recovery). For example, as described above, in fast MCG recovery, signaling (MN RRC messages) between the MN and the UE is transmitted via the SN. Therefore, the SN may need to control (or adjust) the timing for modifying or releasing the configuration or resources in the SN so as not to interfere with the transmission of the MN RRC messages between the MN and the UE. For example, becoming aware of the occurrence of an MCG failure (or the execution of MCG recovery) enables the SN to perform such control (or adjustment).
[0013] One of the purposes of the embodiments disclosed herein is to provide a device, method and program that enables the SN to be informed of the occurrence of an MCG failure. It should be noted that this purpose is only one of the purposes of the embodiments disclosed herein. Other purposes or problems and novel features will become clear from the following description and drawings.
[0014] Solutions for solving problems
[0015] In a first aspect, a master node comprises at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to support dual connectivity enabling a radio terminal to use a primary cell group, i.e., an MCG, provided by the master node and a secondary cell group, i.e., an SCG, provided by a secondary node. In addition, the at least one processor is configured to send an indication related to a failure of the MCG to the secondary node. The at least one processor is also configured to send a radio resource control message, i.e., an RRC message, related to recovery from a failure of the MCG to the radio terminal via an SCG portion of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0016] In a second aspect, the secondary node includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to support dual connectivity that enables a radio terminal to use a primary cell group, i.e., an MCG, provided by the primary node and a secondary cell group, i.e., an SCG, provided by the secondary node. In addition, the at least one processor is configured to receive an indication related to a failure of the MCG from the primary node. The at least one processor is also configured to send a radio resource control message, i.e., an RRC message, related to recovery from a failure of the MCG to the radio terminal via an SCG portion of a separate signaling radio bearer configured between the primary node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0017] In a third aspect, the method performed by the master node includes: (a) controlling the master node to enable dual connection for the radio terminal using a main cell group, i.e., MCG, provided by the master node and a secondary cell group, i.e., SCG, provided by the secondary node; (b) sending an indication related to a failure of the MCG to the secondary node; and (c) sending a radio resource control message, i.e., an RRC message, related to recovery from the failure of the MCG to the radio terminal via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0018] In a fourth aspect, the method performed by the secondary node includes: (a) controlling the secondary node to enable dual connection for the radio terminal using a primary cell group, i.e., MCG, provided by the primary node and a secondary cell group, i.e., SCG, provided by the secondary node; (b) receiving an indication related to a failure of the MCG from the primary node; and (c) sending a radio resource control message, i.e., an RRC message, related to recovery from the failure of the MCG to the radio terminal via an SCG part of a separate signaling radio bearer configured between the primary node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0019] In a fifth aspect, the program includes instructions (software codes), which, when loaded into a computer, cause the computer to perform the method according to the third aspect or the fourth aspect.
[0020] Effects of the Invention
[0021] According to the above aspects, an apparatus, method, and program that enable a SN to learn of the occurrence of an MCG failure may be provided. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] Figure 1is a diagram showing a structural example of a radio communication network according to an embodiment;
[0023] Figure 2 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0024] Figure 3 is a flowchart showing an example of the operation of the MN according to the embodiment;
[0025] Figure 4 is a flowchart showing an example of the operation of the SN according to an embodiment;
[0026] Figure 5 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0027] Figure 6 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0028] Figure 7 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0029] Figure 8 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0030] Fig. 9 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0031] Fig.10 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0032] Fig.11 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0033] Fig.12 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0034] Fig.13 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0035] Fig.14 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0036] Fig.15 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0037] Fig.16 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0038] Fig.17 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0039] Fig.18 is a diagram showing an example of the format of an RRC TRANSFER message;
[0040] Fig.19 is a sequence diagram showing an example of operations of a CU and a DU according to an embodiment;
[0041] Fig. 20 is a diagram showing an example of the format of a DL RRC MESSAGE TRANSFER message;
[0042] Fig.21 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0043] Fig. 22 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0044] Fig.23 is a sequence diagram showing an example of the operation of a UE according to an embodiment;
[0045] Fig.24 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0046] Fig.25 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0047] Fig.26 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0048] Fig. 27 is a diagram showing an example of the format of an RRC TRANSFER message;
[0049] Fig.28 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0050] Fig.29 is a diagram showing an example of the format of a MN MODIFICATION INDICATION message;
[0051] Fig.30 is a diagram showing an example of the format of a CG-ConfigInfo information element;
[0052] Fig.31is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0053] Fig.32 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0054] Fig.33 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0055] Fig.34 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0056] Fig.35 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0057] Fig.36 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0058] Fig.37 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0059] Fig.38 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0060] Fig.39 is a sequence diagram showing an example of operations of the MN and the SN according to the embodiment;
[0061] Fig.40 is a block diagram showing a structural example of an MN according to an embodiment; and
[0062] Fig.41 is a block diagram showing a structural example of a UE according to an embodiment. DETAILED DESCRIPTION
[0063] The specific embodiments will be described in detail below with reference to the accompanying drawings. In the entire drawings, the same or corresponding elements are represented by the same symbols, and for the sake of clarity, repeated descriptions are omitted when necessary.
[0064] Each embodiment described below can be used alone, or two or more embodiments thereof can be appropriately combined with each other. These embodiments include novel features that are different from each other. Therefore, these embodiments help to achieve different purposes or solve different problems from each other, and help to obtain different advantages from each other.
[0065] The following description of the embodiments mainly focuses on 3GPP Long Term Evolution (LTE) systems and 5G systems. However, these embodiments may be applicable to other radio communication systems that support technologies similar to 3GPP multi-connectivity (e.g., dual connectivity). Unless otherwise specified, the term "LTE" used in this specification includes enhancements / evolutions of LTE and LTE-Advanced to provide interoperability with 5G systems. The 5G system includes not only NR (new air interface), but also a network structure in which an LTE eNodeB (eNB) is connected to a 5G core network (5GC). The eNB may be referred to as ng-eNB. The ng-eNB may also be referred to as eNB / 5GC, which means an eNB connected to a 5GC. On the other hand, a 5GgNB that performs DC with an LTE eNB connected to an evolved packet core (EPC) may be referred to as an en-gNB.
[0066] First embodiment
[0067] Figure 1 An example of the structure of a radio communication network according to the present embodiment is shown. The radio communication network according to the present embodiment includes a master node (MN) 1 and a secondary node (SN) 2. MN 1 and SN 2 communicate with each other via an inter-node interface 103. Although not shown, at least MN 1 is connected to the core network, and SN 2 may also be connected to the core network. UE 3 communicates with MN 1 and SN 2 via air interfaces 101 and 102 to perform dual connectivity (DC) between a master cell group (MCG) and a secondary cell group (SCG). MCG is a group of service cells associated with MN 1 (or provided by MN 1), and includes SpCell (i.e., primary cell (PCell)) and optionally includes one or more secondary cells (SCell). On the other hand, SCG is a group of service cells associated with SN 2 used as an SN in DC (or provided by SN 2), and includes the primary cell of SCG and optionally includes one or more secondary cells (SCell). The primary cell of SCG is referred to as a primary SCG cell (PSCell) or a primary secondary cell (PSCell). PSCell is a special cell (SpCell) of SCG.
[0068] MN 1 and SN 2 may each be an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (EUTRAN) node or a Next Generation Radio Access Network (NG-RAN) node. The EUTRAN node may be an eNB or an en-gNB. The NG-RAN node may be a gNB or an ng-eNB. The radio access technology (RAT) of MN 1 may be different from the RAT of SN 2.
[0069] DC can be multi-radio dual connectivity (MR-DC). MR-DC includes E-UTRA-NR dual connectivity (EN-DC), NR-E-UTRA DC (NE-DC), NG-RAN EN-DC (NGEN-DC) and NR-NR DC (NRDC). EN-DC uses EPC, while NE-DC, NGEN-DC and NR DC use 5GC.
[0070] Figure 2 An example of signaling between MN 1 and SN 2 is shown. In step 201, MN 1 sends a message related to modification or release of configuration or resources in SN 2 related to DC to SN 2. That is, the message is a control message of the RAN inter-node interface (i.e., Xn interface or X2 interface). The message may be a message requesting SN 2 to modify or release configuration or resources in SN 2 related to DC. Figure 2 As shown, the message in step 201 may be a SN MODIFICATION REQUEST message or a SN RELEASE REQUEST message. The SN MODIFICATION REQUEST message is sent from the MN to the SN to request modification of the configuration or resources in the SN 2 regarding the DC. On the other hand, the SN RELEASE REQUEST message is sent from the MN to the SN to request release of the configuration or resources in the SN. Alternatively, the message in step 201 may be a new XnAP / X2AP message (e.g., MN MODIFICATION NOTIFICATION message). The configuration in the SN 2 may be, for example, SCG configuration information (e.g., SCG configuration) or bearer configuration information (e.g., radio bearer configuration) configured by the SN 2 and sent to the UE 3 and also maintained by the SN 2. The resources in the SN 2 may be, for example, resources of a signaling connection associated with the UE 3 between the MN 1 and the SN 2, radio resources in the SCG set by the SN 2 for the UE 3, or terminal information related to the UE 3 (e.g., UE context).
[0071] In addition, the message in step 201 explicitly or implicitly indicates that the modification or release of the configuration (or resources) in SN 2 is related to an MCG failure (e.g., MCG RLF) or its recovery. In other words, the message in step 201 explicitly or implicitly indicates that the modification or release of the configuration (or resources) in SN 2 is due to an MCG failure. For example, the message may include an indication of an MCG failure. The indication may, for example, indicate that an MCG failure has occurred, that an MCG failure has been detected, or the type of MCG failure (e.g., MCG failure type). Additionally or alternatively, the message may include an indication of recovery from an MCG failure (or recovery of an MCG link). The indication may, for example, indicate that it is intended, intended, or attempted to recover from an MCG failure (or recovery of an MCG link). Additionally or alternatively, the message may include an indication of recovery from an MCG failure (or recovery of an MCG link) via an SN (or SCG, or a separate SRB, or SRB3). RLF is an example of an MCG failure. An MCG failure may be, for example, a handover failure, a reconfiguration failure of the MN (or MCG) (synchronous reconfiguration failure or reconfiguration failure), or an integrity protection check failure (integrity protection check failure). An MCG failure type may indicate any of these other MCG failures.
[0072] This enables SN 2 to know that the modification or release of the configuration (or resources) requested by the message in step 201 is due to an MCG failure. In other words, SN 2 can become aware that the message in step 201 is associated with an MCG failure or its recovery. Therefore, SN 2 can distinguish the message in step 201 from other SN MODIFICATION and SN RELEASEREQUEST messages that are not related to MCG recovery. In other words, SN 2 can distinguish the message related to the modification or release of the SN configuration (or resources) sent from MN 1 to SN 2 to recover from an MCG failure (or restore an MCG link) from other messages.
[0073] In some implementations, MN 1 may decide to initiate an MCG recovery procedure in response to receiving MCG failure information (or MCG failure indication) from UE 3 via SN 2 (i.e., via a separate SRB, or SRB3 and Xn / X2). The MCG recovery procedure may be an intra-MN handover or an inter-MN handover involving the transmission of an MN RRC message via a separate SRB or via SRB3 and Xn / X2. MN 1 may then send the message of step 201 to SN 2 during the MCG recovery procedure. In addition, during the MCG recovery procedure, MN 1 may send an MN RRC message related to recovery of the MCG failure to UE 3 via the SCG (i.e., a separate SRB or SRB3). In other words, SN2 may send an MNRRC message related to recovery of the MCG failure and sent by MN 1 to UE 3 via the SCG (i.e., a separate SRB or SRB3).
[0074] Alternatively, MN 1 may decide to initiate an MCG recovery procedure and send a message of step 201 to SN 2 in response to (autonomous) detection of an MCG failure, independently of reception of MCG failure information from UE 3. In addition, in the MCG recovery procedure, MN1 may send an MN RRC message related to recovery of the MCG failure to UE 3 via SCG (i.e., a separate SRB or SRB3). By way of example and not limitation, the detection of an MCG failure in MN 1 may be the same as a detection method in an existing LTE or NR radio network. For example, an MCG failure may be detected based on any of the following: a success or failure status of uplink or downlink data transmission (e.g., the number of RLC retransmissions); a status of uplink radio quality (e.g., received power or received quality of a sounding reference signal (SRS)); and a status of downlink radio quality (e.g., a CQI report value, or RSRP, RSRQ, or SINR value of a synchronization signal / PBCH block (SSB) or CSI-RS).
[0075] In addition, SN 2 may perform step 202. In step 202, SN 2 determines whether the modification or release of the configuration (or resources) in SN 2 requested by the message of step 201 is related to the MCG failure or its recovery. In other words, SN 2 determines whether the message of step 201 is associated with the MCG failure recovery procedure. In other words, SN 2 determines whether the message of step 201 is due to the MCG failure. If SN 2 determines that the message is due to the MCG failure (or associated with the MCG failure recovery procedure), SN 2 delays the modification or release of the configuration (or resources) in SN 2 until a predetermined condition associated with the sending of the MN RRC message from MN 1 to UE 3 via SN 2 (i.e., detaching SRB or SRB3) is met. The MN RRC message is sent for recovery from the MCG failure (or recovery of the MCG link). The MN RRC message may be, for example, a MN RRC (connection) reconfiguration message containing a reconfigurationWithSync information element (IE) or a mobilityControlInfo IE.
[0076] SN 2 may postpone only a portion of the multiple modifications or releases requested by the message in step 201. Specifically, SN 2 may postpone modifications or releases that may prevent the transmission of RRC messages from MN 1 to UE 3 via SN 2 (i.e., detaching SRB or SRB3). In some implementations, SN 2 may delay the update (modification) of security keys applied to direct radio bearers (e.g., SRB3, DRB) between SN 2 and UE 3. Additionally or alternatively, SN 2 may delay layer 2 reconfiguration (e.g., any one or combination of PDCP reestablishment, PDCP data resumption, RLC reestablishment, and MAC reset). In some implementations, SN 2 may delay the release of resources for a signaling connection associated with UE 3 between MN 1 and SN 2. Additionally or alternatively, SN 2 may postpone the release of radio resources that have been allocated to UE 3 (e.g., SCG configuration). Additionally or alternatively, SN 2 may delay the release of terminal information associated with UE 3 (e.g., UE context). Such operation enables SN 2 to control (or adjust) when to modify or release the configuration or resources in SN 2 so as not to interfere with the transmission of MN RRC messages between MN 1 and UE 3 through SN 2.
[0077] The predetermined condition associated with the transmission of the MN RRC message via SN 2 may, for example, include at least one of the following examples. In some implementations, the predetermined condition may include that SN 2 has completed the transmission of the MN RRC message to UE 3. In some implementations, the predetermined condition may include that SN 2 has received a response sent by UE 3 in response to receiving the MN RRC message. In the case of forwarding the MN RRC via a separate SRB, the response from UE 3 may be one or both of a hybrid automatic repeat request (HARQ) acknowledgement (ACK) and an RLC ARQ ACK. On the other hand, in the case of forwarding the MN RRC via SRB3, the response may be an SN RRC (connection) reconfiguration complete message from UE 3. In addition, in some implementations, the predetermined condition may include that SN 2 has received an SN reconfiguration complete message from MN 1 (in the case of intra-MN handover) or a target MN (in the case of inter-MN handover).
[0078] Figure 3 is a flow chart showing an example of the operation of MN 1. In step 301, MN 1 initiates an MCG failure recovery procedure in response to detecting an MCG failure. As described above, MN 1 may detect an MCG failure based on receiving MCG failure information from UE 3, or MN 1 may autonomously detect an MCG failure without relying on the reception of MCG failure information.
[0079] In step 302, MN 1 sends an SN MODIFICATION REQUEST or SN RELEASE REQUEST message to SN 2 in the MCG recovery procedure, which explicitly or implicitly indicates modification or release of configuration (or resources) in SN 2 related to MCG failure or its recovery. As described above, MN 1 can send another XnAP / X2AP message different from the SN MODIFICATION / RELEASE REQUEST message to SN 2. The message of step 302 causes SN 2 to postpone modification or release of configuration (or resources) in SN 2 until a predetermined condition associated with the sending of MN RRC messages through SN 2 is met.
[0080] Figure 4is a flow chart showing an example of the operation of SN 2. In step 401, SN 2 receives a SNMODIFICATION REQUEST or SN RELEASE REQUEST message from MN 1. In step 402, SN 2 determines, based on the message in step 401, whether the modification or release of the configuration (or resources) in SN 2 requested by the message in step 401 is related to an MCG failure or its recovery. In other words, SN 2 determines whether the message of step 401 is associated with an MCG failure recovery procedure. In other words, SN 2 determines whether the message of step 401 is due to an MCG failure. If the message is related to an MCG failure or its recovery, SN 2 postpones the modification or release of the configuration (or resources) in SN 2 until a predetermined condition associated with the sending of an MN RRC message from MN 1 to UE 3 via SN 2 (i.e., detaching SRB or SRB3) is met (step 403).
[0081] Second embodiment
[0082] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 In this embodiment, when an MCG failure is detected in the case where a separate SRB (eg, separate SRB1) has been configured between MN 1 and UE 3, MN 1 performs an intra-MN handover without SN change to recover from the MCG failure.
[0083] Figure 5 An example of signaling of MN 1 and SN 2 performed during an intra-MN handover without SN change is shown. In step 501, MN 1 sends an SN MODIFICATION REQUEST message to SN 2. The SN MODIFICATION REQUEST message requests SN 2 to modify (or update) configuration or resources associated with UE 3 in SN 2. For example, the message may indicate information related to a new security key to request modification (or update) of a security key (e.g., SgNB security key) applicable to a bearer terminated in SN 2 (SN terminated bearer).
[0084] The SN MODIFICATION REQUEST message of step 501 also includes an indication to SN 2 that the message is associated with an MCG failure or its recovery. The indication may be referred to as, for example, an MCG Failure Recovery Notification, an MCG Link Recovery Notification, or an MCG Failure Notification. The indication may be an IE or a cause value contained in the message. Alternatively, the cause value may be, for example, MCG Radio Connection With UE Lost or MCG RLF. In response to receiving the indication, SN 2 delays modification of the configuration (or resources) in SN 2.
[0085] In step 502, SN 2 sends an SN MODIFICATION REQUEST ACKNOWLEDGE message to MN 1 to confirm the request for modification of SN (or SCG) resources used by UE 3 from MN 1. The message may include a CG-Config message generated by SN 2. The CG-Config message includes the SCG radio configuration (e.g., one or both of scg-CellGroupConfig and scg-RB-Config) generated by SN 2 based on the SN MODIFICATION REQUEST message of step 501.
[0086] In step 503, MN 1 sends an MN RRC message (e.g., RRC reconfiguration including reconfigurationWithSync) to UE 3 via the SCG branch of the detached SRB1. Specifically, MN 1 sends an RRC TRANSFER message to SN 2, which includes a Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) encapsulating the MN RRC message. SN 2 receives the RRC TRANSFER message and sends the PDCP PDU (encapsulating the MN RRC message) to UE 3 via the SCG branch of the detached SRB1. In 5G terminology, PDCP PDU is also called PDCP-C PDU because the PDCP PDU contains the RRC message of the control plane (CP). PDCP PDU of PDCP hosted by the gNB Central Unit (CU) control plane (CP) is also called PDCP-C PDU in the same way.
[0087] When the MN RRC message is received in step 503, UE 3 performs intra-MN handover without SN change according to the RRC configuration information (e.g., one or both of securityConfig(HO) and sk-Counter) included in the MN RRC message. The RRC message may include an SN RRC message (or SN RRC configuration) for intra-MN handover without SN change. In this case, the MCG RRC entity of UE 3 transfers the SN RRC message to the SCG RRC entity of UE 3. UE 3 performs intra-MN handover without SN change according to the MN RRC message and the SN RRC message.
[0088] In step 504, after sending the PDCP PDU (encapsulating the MN RRC message) to UE 3, SN 2 modifies (or updates) the SN (SCG) resources (e.g., configuration or resources in SN 2) used by UE 3 as requested by the SN MODIFICATION REQUEST message in step 501. SN 2 may modify (update) the SN (SCG) resources in response to sending the PDCP PDU to UE 3. That is, in Figure 5 In the example of , the SN modification preparation procedure initiated by the MN interacts with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In other words, the SN modification preparation procedure initiated by the MN is associated with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In some implementations, if SN 2 (e.g., immediately) receives an RRC TRANSFER message further after receiving the SN MODIFICATION REQUEST message from MN 1, and the RRC TRANSFER message contains an SN RRC container (e.g., PDCP-C PDU) to be sent in a separate SRB, SN 2 prioritizes the sending of the SN RRC container to UE 3 over the SN modification preparation procedure.
[0089] Figure 6 Show Figure 5 The behavior of MN 1 and SN 2 in steps 601 to 603 is the same as in steps 501 to 503. In step 604, SN 2 receives HARQ-ACK (and RLC ARQ-ACK) from UE 3. In response to receiving the MN RRC message via the SCG branch (i.e., SCG RLC bearer) in step 603, UE 3 sends HARQ-ACK (and RLC ARQ-ACK) to the medium access control (MAC) sublayer (and RLC sublayer) of SN 2.
[0090] In step 605, after receiving the HARQ-ACK (and RLC ARQ-ACK) from UE 3, SN 2 modifies (or updates) the SN (SCG) resources used by UE 3 as requested by the SN MODIFICATION REQUEST message in step 601. SN 2 may modify (update) the SN (SCG) resources in response to receiving the HARQ-ACK (and RLC ARQ-ACK) from UE 3. That is, Figure 6 In the example of , the SN modification preparation procedure initiated by the MN interacts with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In other words, the SN modification preparation procedure initiated by the MN is associated with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In some implementations, if SN 2 (e.g., immediately) receives an RRC TRANSFER message further after receiving the SN MODIFICATION REQUEST message from MN 1, and the RRC TRANSFER message contains an SN RRC container (e.g., PDCP-C PDU) to be sent in a separate SRB, SN 2 sends the SN RRC container to UE 3 in priority over the SN modification preparation procedure.
[0091] Note that in a normal handover, the UE is enabled to omit sending HARQ-ACK (and RLC ARQ-ACK) upon receiving an RRC (connection) reconfiguration message containing the reconfigurationWithSync IE (or mobilityControlInfo IE). Figure 6 As shown, if UE 3 receives reconfigurationWithSyncIE (or mobilityControlInfo IE) via the SCG branch of the separated SRB, UE 3 may operate to always send HARQ-ACK (and RLC ARQ-ACK) to SN 2. UE 3 may operate to always send HARQ-ACK (and RLC ARQ-ACK) to SN 2 only when UE 3 has reported the detection of MCG failure to MN 1 via SCG and SN 2. Specifically, for example, in the case where UE 3 has sent MCG failure information, UE 3 may operate in this manner. Alternatively, in the case where a predetermined time has not passed since UE 3 sent MCG failure information, UE 3 may operate in this manner. Alternatively, in the case where UE 3 has been permitted to send MCG failure information, UE 3 may operate in this manner. Alternatively, in the case where UE 3 has received configuration information for sending MCG failure information from MN, UE 3 may operate in this manner.
[0092] Figure 7 Show Figure 5 Another variation of the process shown. Steps 701 to 704 are Figure 6 , steps 601 to 604 in . However, the HARQ-ACK (and RLC ARQ-ACK) transmission in step 704 can be omitted. In step 705, UE 3 sends an RRC reconfiguration complete message to MN 1 via the new PCell indicated by the SpCellConfig IE (servCellIndex of SpCellConfig IE) containing the ReconfigurationWithSync IE. If the MobilityControlInfo IE is used instead of the ReconfigurationWithSync IE, the new PCell can be specified by the targetPhysCellId contained in the IE. In step 706, MN 1 sends a SN RECONFIGURATION COMPLETE message to SN 2. The SN RECONFIGURATION COMPLETE message indicates that UE 3 has successfully applied the SCG radio configuration (e.g., one or both of the scg-CellGroupConfig and scg-RB-Config) included in the SNMODIFICATION REQUEST ACKNOWLEDGE message in step 702.
[0093] In step 707, after receiving the SN RECONFIGURATION COMPLETE message from MN 1, SN 2 modifies (or updates) the SN (SCG) resources used by UE 3 as requested by the SN MODIFICATION REQUEST message in step 701. SN 2 may modify (or update) its SN (SCG) resources in response to receiving the SN RECONFIGURATION COMPLETE message. That is, in Figure 7 In the example of , the SN modification preparation process initiated by the MN interacts with the SN reconfiguration completion process. In other words, the SN modification preparation process initiated by the MN is associated with the SN reconfiguration completion process.
[0094] In some implementations, if SN 2 accepts (or grants) the terminal information (e.g., UE context) modification (i.e., SN MODIFICATION REQUEST) that requires reporting the success of the RRC reconfiguration procedure to MN 1, SN 2 may start a timer (e.g., T DCoverallTXn DCoverall ). SN2 may then stop the timer upon receiving the SN RECONFIGURATION COMPLETE message. In addition, if SN 2 further receives an RRC TRANSFER message (e.g., immediately after) receiving the SN MODIFICATION REQUEST message from MN 1, and if the RRC TRANSFER message contains an SN RRC container (e.g., PDCP-C PDU) to be sent in a separate SRB, SN 2 prioritizes the sending of the SN RRC container to UE 3 over the SN modification preparation procedure. That is, SN 2 does not modify (or update) the terminal information (i.e., SN (SCG) resources), at least until SN 2 receives the SN RECONFIGURATION COMPLETE message.
[0095] Figure 8 Show Figure 5 Another variant of the process shown. As already explained, instead of the SN MODIFICATIONREQUEST / ACKNOWLEDGE message, a new XnAP / X2AP message can be used. Figure 8 In the example of , MN 1 sends a MN MODIFICATION NOTIFICATION message to SN 2 (step 801). The MN MODIFICATION NOTIFICATION message indicates to SN 2 that SCG modification (or reconfiguration) associated with MCG modification (or change or reconfiguration) is required. Like the SN MODIFICATION REQUEST message, the MN MODIFICATION NOTIFICATION message requests SN 2 to modify (or update) the configuration or resources used by UE 3 in SN 2. The MN MODIFICATION NOTIFICATION message may include an indication to SN 2 that the message is associated with an MCG failure or recovery thereof. Alternatively, the sending of the MN MODIFICATION NOTIFICATION message itself may be associated with an MCG failure or recovery thereof (that is, it may imply an MCG failure or recovery thereof). In other words, the MN MODIFICATION NOTIFICATION message is sent to recover from an MCG failure, and SN 2, by receiving (in response to receiving) the message, may be aware that MN 1 is attempting to recover from an MCG failure.
[0096] In step 802, SN 2 sends a MN MODIFICATION NOTIFICATION RESPONSE message to MN 1 to acknowledge the request for SN (SCG) resource modification used by UE 3 from MN 1. This message may contain a CG-Config message generated by SN 2 in the same manner as the SN MODIFICATION REQUEST ACKNOWLEDGE message.
[0097] In step 803, MN 1 sends an MNRRC message (e.g., RRC reconfiguration including reconfigurationWithSync) to UE 3 via the SCG branch of detached SRB1 as in step 503. However, in step 803, a new XnAP / X2AP message (e.g., MN MODIFICATION REQUEST message) is used instead of the RRCTRANSFER message. The MN MODIFICATION REQUEST message indicates to SN 2 that the MNRRC message associated with the MCG modification needs to be forwarded to UE 3.
[0098] In step 804, SN 2 receives HARQ-ACK (and RLC ARQ-ACK) from UE 3. The transmission of HARQ-ACK (and RLC ARQ-ACK) in step 804 may be omitted.
[0099] In step 805, after sending the PDCP PDU (encapsulating the MN RRC message) to UE 3, SN 2 modifies (or updates) the SN (SCG) resources used by UE 3 as requested by the MN MODIFICATION NOTIFICATION message in step 801. SN 2 may modify (or update) the SN (SCG) resources in response to sending the PDCP PDU to UE 3. Alternatively, SN 2 may modify (or update) the SN (SCG) resources used by UE 3 after receiving HARQ-ACK (and RLC ARQ-ACK) from UE 3. SN 2 may modify (or update) the SN (SCG) resources in response to receiving HARQ-ACK (and RLC ARQ-ACK) from UE 3.
[0100] and Figure 7 The process is the same as in Figure 8In the process, after receiving the SN RECONFIGURATION COMPLETE message from the MN 1, the SN 2 may modify (or update) the SN (SCG) resources used by the UE 3 requested by the MN MODIFICATION NOTIFICATION message of step 801.
[0101] The MN MODIFICATION NOTIFICATION message in step 801, the MN MODIFICATION NOTIFICATION RESPONSE message in 802, and the MN MODIFICATION REQUEST message in 803 may be specified as a single (combined) process. In this process, these actions may be performed as a series of actions (i.e., in conjunction with each other). This process may be referred to, for example, as a MN MODIFICATION preparation process or a MN RECOVERY preparation process.
[0102] Fig. 9 Show Figures 5 to 7 A specific example of the process shown. Fig. 9 Steps 904 to 906 are Figure 5 Steps 501 to 503, Figure 6 Steps 601 to 603 and Figure 7 The steps 701 to 703 correspond to each other. Fig. 9 Step 907 and Figure 6 Step 604 and Figure 7 Corresponding to step 704. Fig. 9 Steps 909 and 910 are the same as Figure 7 The steps 705 and 706 correspond to each other.
[0103] exist Fig. 9 In step 901, UE 3 detects an MCG failure (e.g., MCG RLF). In step 902, UE 3 sends MCG failure information to MN 1 via the SCG branch of detached SRB1. The RRC TRANSFER message can be used to transmit the MCG failure information from SN 2 to MN 1. In step 903, MN 1 determines an MCG failure recovery procedure in response to receiving the MCG failure information. The MCG failure recovery procedure includes an intra-MN handover procedure without SN change (i.e., steps 904 to 911).
[0104] Fig.10 Show Figure 8 A specific example of the process shown. Fig.10 Steps 1004 to 1007 in Figure 8Corresponding to steps 801 to 804 in . Fig.10 Steps 1001 to 1003 in Fig. 9 Steps 901 to 903 in are the same. Fig.10 Steps 1008 to 1011 in Fig. 9 Steps 908 to 911 in are the same.
[0105] Third embodiment
[0106] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 In this embodiment, when an MCG failure is detected in the case where a separate SRB (eg, separate SRB1) has been configured between MN 1 and UE 3, MN 1 performs an inter-MN handover without SN change to recover from the MCG failure.
[0107] Fig.11 An example of signaling of MN 1 and SN 2 performed during an inter-MN handover without SN change is shown. In step 1101, MN 1 sends an SN RELEASE REQUEST message to SN 2. MN 1 includes a UE context retention indicator IE set to "true" in the SN RELEASE REQUEST message to indicate to SN 2 that the UE context in SN 2 is to be maintained (kept).
[0108] The SN RELEASE REQUEST message in step 1101 also includes an additional indication to indicate to SN 2 that the message is associated with an MCG failure or its recovery. The additional indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or a cause value contained in the message. In response to receiving the additional indication, SN 2 delays the release of a configuration (or resource) within SN 2. Specifically, SN 2 may delay the release of resources for a signaling connection associated with UE 3 between MN 1 and SN 2. Additionally or alternatively, SN 2 may postpone the release of radio resources allocated to UE 3.
[0109] In step 1102, SN 2 sends an SN RELEASE REQUEST ACKNOWLEDGE message to MN 1 to confirm the request from MN 1 for releasing SN (SCG) resources used by UE 3.
[0110] In step 1103, MN 1 sends a MN RRC message (eg, RRC reconfiguration including reconfigurationWithSync) to UE 3 via the SCG branch of detached SRB1. Figure 5 The same as step 503.
[0111] In step 1104, after sending the PDCP PDU (encapsulating the MN RRC message) to UE 3, SN 2 releases the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 501. SN 2 may release the SN (SCG) resources in response to sending the PDCP PDU to UE 3. That is, in Fig.11 In the example of , the SN release procedure initiated by the MN interacts with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In other words, the SN release procedure initiated by the MN is associated with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In some implementations, if SN 2 (e.g., immediately) receives an RRC TRANSFER message after further receiving the SN RELEASE REQUEST message from MN 1, and the RRC TRANSFER message contains an SN RRC container (e.g., PDCP-C PDU) to be sent via a separate SRB, SN2 sends the SN RRC container to UE 3 in priority over the SN release procedure.
[0112] Fig.12 Show Fig.11 The operations of MN 1 and SN 2 in steps 1201 to 1203 are the same as those in steps 1101 to 1103. In step 1204, SN 2 receives HARQ-ACK (and RLC ARQ-ACK) from UE 3. In response to receiving the MN RRC message in step 1203 via the SCG branch (i.e., SCG RLC bearer), HARQ-ACK (and RLC ARQ-ACK) is sent from UE 3 to the MAC sublayer (and RLC sublayer) of SN 2.
[0113] In step 1205, after receiving the HARQ-ACK (and RLC ARQ-ACK) from UE 3, SN 2 releases the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 1201. SN 2 may release the SN (SCG) resources in response to receiving the HARQ-ACK (and RLC ARQ-ACK) from UE 3. That is, Fig.12In the example of , the SN release procedure initiated by the MN interacts with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In other words, the SN release procedure initiated by the MN is associated with the RRC transfer procedure (or the MN RRC reconfiguration procedure). In some implementations, if SN 2 (e.g., immediately) receives an RRC TRANSFER message after further receiving the SN RELEASE REQUEST message from MN 1, and if the RRC TRANSFER message contains an SN RRC container (e.g., PDCP-C PDU) to be sent in a separated SRB, SN 2 prioritizes the sending of the SN RRC container to UE 3 over the SN release procedure.
[0114] Note that in a normal handover, the UE is enabled to omit sending HARQ-ACK (and RLC ARQ-ACK) upon receiving an RRC (connection) reconfiguration message containing the reconfigurationWithSync IE (or mobilityControlInfo IE). Fig.12 As shown, if UE 3 receives reconfigurationWithSync IE (or mobilityControlInfo IE) via the SCG branch of the separated SRB, UE 3 may operate to always send HARQ-ACK (and RLC ARQ-ACK) to SN2. UE 3 may operate to always send HARQ-ACK (and RLC ARQ-ACK) to SN 2 only in the case where UE 3 has reported to MN 1 via SCG and SN 2 that an MCG failure has been detected. Specifically, for example, in the case where UE 3 sends MCG failure information, UE 3 may operate in this manner. Alternatively, in the case where a predetermined time has not passed since UE 3 sent MCG failure information, UE 3 may operate in this manner. Alternatively, in the case where UE 3 has been permitted to send MCG failure information, UE 3 may operate in this manner. Alternatively, in the case where UE 3 has received configuration information for sending MCG failure information from MN, UE 3 may operate in this manner.
[0115] Fig.13 Show Fig.11 Another variation of the process shown. Steps 1301 to 1304 are Fig.121304. However, the HARQ-ACK (and RLC ARQ-ACK) transmission in step 1304 may be omitted. In step 1305, UE3 sends an RRC reconfiguration complete message to the target MN 4 via the new PCell indicated by the SpCellConfig IE (servCellIndex of the SpCellConfig IE) containing the ReconfigurationWithSync IE. If the MobilityControlInfo IE is used instead of the ReconfigurationWithSync IE, the new PCell may be specified by the targetPhysCellId included in the IE. In step 1306, the target MN 4 sends an SNRECONFIGURATION COMPLETE message (or MN RECONFIGURATION COMPLETE message) to SN 2.
[0116] In step 1307, after receiving the SN RECONFIGURATION COMPLETE message from the target MN 4, SN2 releases the SN (SCG) resources used by the UE 3 as requested by the SN RELEASE REQUEST message in step 1301. SN2 may release the SN (SCG) resources in response to receiving the SN RECONFIGURATION COMPLETE message. Fig.13 In the example of , the SN release procedure initiated by the MN interacts with the SN reconfiguration completion procedure. In other words, the SN release procedure initiated by the MN is associated with the SN reconfiguration completion procedure. Instead of step 1306, the target MN 4 may send a MNRECONFIGURATION COMPLETE message to the source MN 1, and the source MN 1 may send a SN RECONFIGURATION COMPLETE message to the SN 2.
[0117] Can be further modified Fig.11 Instead of the SN RELEASE REQUEST / ACKNOWLEDGE message, a new XnAP / X2AP message may be used. For example, Figure 8 Similar to the process in, MNMODIFICATION NOTIFICATION / RESPONSE (MN modification notification / response) message can be used. In addition or alternatively, a new XnAP / X2AP message (for example, Figure 8The MN MODIFICATION REQUEST message in the RRCTRANSFER message is used instead of the RRCTRANSFER message. Figure 8 As described above, the MN MODIFICATION NOTIFICATION, MN MODIFICATION RESPONSE (MN modification response) and MN MODIFICATION REQUEST messages may be specified together as a single (combined) procedure.
[0118] Fig.14 Show Figures 11 to 13 A specific example of the process shown. Fig.14 Steps 1406 to 1408 and Fig.11 Steps 1101 to 1103, Fig.12 Steps 1201 to 1203 and Fig.13 Corresponding to steps 1301 to 1303. Fig.14 Steps 1409 and 1410 are the same as Fig.13 The steps 1305 and 1306 correspond to each other. Fig.14 In the embodiment, upon receiving the SN RECONFIGURATION COMPLETE message (or MN RECONFIGURATION COMPLETE message) from the target MN 4 (step 1410), the SN 2 may release the SN (SCG) resources used by the UE 3 requested by the SN RELEASE REQUEST message of step 1406, except for the terminal information (e.g., UE context) of the UE 3. For example, the SN 2 may release the radio resources associated with the UE 3 (e.g., the source SCG lower layer configuration (e.g., CellGroupConfig)) for the MR-DC with the source MN 1.
[0119] exist Fig.14 In step 1401, UE 3 sends MCG failure information to MN 1 via the SCG branch of detached SRB1. MN1 determines the MCG failure recovery process in response to receiving the MCG failure information. The MCG failure recovery process includes an inter-MN handover process without SN change (i.e., steps 1402 to 1413). The inter-MN handover process without SN change includes signaling with the core network (CN) 5 for path switching (step 1411). When SN 2 receives a UE CONTEXT RELEASE message from the source MN 1 (step 1413), SN 2 releases the terminal-related resources of UE 3 maintained for the MR-DC with the source MN 1 (e.g., C-plane resources with the source MN 1 related to the UE context).
[0120] Fourth embodiment
[0121] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 In this embodiment, when an MCG failure is detected when a separate SRB (e.g., separate SRB1) has been configured between MN 1 and UE 3, MN 1 performs an MN to gNB change procedure involving SN release to recover from the MCG failure.
[0122] Fig.15 A specific example of the MN to gNB change procedure involving SN release is shown. Fig.15 In step 1501, UE 3 sends MCG failure information to MN 1 via the SCG branch of detached SRB1. MN 1 determines the MCG failure recovery process based on the reception of the MCG failure information. The MCG failure recovery process includes a MN to gNB change process involving SN release (i.e., steps 1502 to 1513).
[0123] In step 1504, MN 1 (i.e., the source MN) sends an SN RELEASE REQUEST message to SN 2. The SN RELEASE REQUEST message of step 1504 also includes an indication to SN 2 that the message is associated with an MCG failure or its recovery. The indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or a cause value included in the message. In response to receiving the indication, SN 2 postpones the release of the configuration (or resources) in SN 2. Specifically, SN 2 may delay the release of resources for a signaling connection associated with UE 3 between MN 1 and SN 2. In addition, SN 2 may postpone the release of terminal information (e.g., UE context) associated with UE 3. In addition, SN 2 may postpone the release of radio resources (e.g., SCG configuration) associated with UE 3.
[0124] In step 1505 , SN 2 sends an SN RELEASE REQUEST ACKNOWLEDGE message to MN 1 to acknowledge the request from MN 1 for releasing SN (SCG) resources used by UE 3 .
[0125] In step 1506, MN 1 sends a MN RRC message (eg, RRC reconfiguration including reconfigurationWithSync) to UE 3 via the SCG branch of detached SRB1. Step 1506 is, for example, Figure 5 Step 503 and Fig.11 The same as step 1103.
[0126] In some implementations, SN 2 may release the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 1504 in response to sending a PDCP PDU (encapsulating an MN RRC message) to UE 3 (step 1506). Alternatively, SN 2 may release the SN (SCG) resources in response to receiving a HARQ-ACK (and RLC ARQ-ACK) from UE 3 (step 1507). Alternatively, SN 2 may release the SN (SCG) resources in response to receiving a SN RECONFIGURATION COMPLETE message (or MN RECONFIGURATION COMPLETE message) from the target gNB 6 (step 1509). For example, SN 2 may perform the release of the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 1504, except for the terminal information (e.g., UE context) of UE 3.
[0127] Fifth embodiment
[0128] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 The example shown is the same. In this embodiment, when an MCG failure is detected when a separate SRB (e.g., separate SRB1) has been configured between MN 1 and UE 3, MN 1 performs an SN to gNB change (role change) procedure to recover from the MCG failure.
[0129] Fig.16 A specific example of the SN to gNB change process is shown. Fig.16 In step 1601, UE 3 sends MCG failure information to MN 1 via the SCG branch of detached SRB1. The MCG failure recovery process includes a SN to gNB change process (ie, steps 1602 to 1610).
[0130] In step 1602, MN 1 (i.e., source MN) sends a HANDOVER REQUEST message to SN 2. The HANDOVER REQUEST message in step 1602 may contain information that explicitly or implicitly indicates that SN 2 is expected to manage UE 3 as an MN (or in a standalone (SA) manner) after the handover. For example, MN 1 may indicate this by including a UE Context Reference at the SgNB IE in the message. When SN 2 receives the information (e.g., UE Context Reference at the SgNB IE), SN 2 understands (or recognizes) that SN 2 is expected (or required) to perform a handover as a (target) MN (or in a SA manner) for UE 3 that is undergoing MR-DC with MN 1 and accepts the UE 3.
[0131] In step 1603, SN 2 sends a HANDOVER REQUEST ACKNOWLEDGE message to MN 1 to indicate that it accepts the handover of UE 3. SN 2 may include a UE context retention indicator IE (i.e., set to true) in the message, thereby indicating to MN 1 that SN 2 will manage UE 3 as a MN (or in SA mode).
[0132] In step 1604, MN 1 (i.e., the source MN) sends an SN RELEASE REQUEST message to SN 2. The SN RELEASE REQUEST message in step 1604 may include a UE context retention indicator IE. In addition, the SN RELEASE REQUEST message includes an indication to SN 2 that the message is associated with an MCG failure or its recovery. The indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or a cause value included in the message. In response to receiving the indication, SN 2 postpones the release of the configuration (or resources) in SN 2. Specifically, SN 2 may delay the release of resources for a signaling connection associated with UE 3 between MN 1 and SN 2. In addition, SN 2 may postpone the release of terminal information (e.g., UE context) associated with UE 3. In addition, SN 2 may postpone the release of radio resources (e.g., SCG lower layer configuration) associated with UE 3 for an MR-DC with the source MN 1.
[0133] In step 1605 , SN 2 sends an SN RELEASE REQUEST ACKNOWLEDGE message to MN 1 to acknowledge the request from MN 1 for releasing SN (SCG) resources used by UE 3 .
[0134] In step 1606, MN 1 sends a MN RRC message (eg, including RRC reconfiguration of reconfigurationWithSync) to UE 3 via the SCG branch of detached SRB1. Step 1606 is, for example, Figure 5 Step 503 and Fig.11 Specifically, although SN 2 is the target RAN node (MN or SA gNB) for handover, SN 2 is used as the source SN at least until the sending of the MNRRC message.
[0135] In some implementations, SN 2 may release the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 1604 in response to sending a PDCP PDU (encapsulating an MN RRC message) to UE 3 (step 1606). Alternatively, SN 2 may release the SN (SCG) resources used for the MR-DC with the source MN 1 in response to receiving a HARQ-ACK (and RLC ARQ-ACK) from UE 3 (step 1607).
[0136] Sixth embodiment
[0137] The configuration example of the radio communication network according to the present embodiment is Figure 1 The examples shown are the same. This embodiment provides an improvement of the RRC TRANSFER message sent from the MN 1 to the SN 2 to transfer the MN RRC message.
[0138] Fig.17 An example of the operation of MN 1 and SN 2 is shown. In step 1701, MN 1 sends an RRCTRANSFER message to SN 2. MN 1 may also include information related to the MN RRC message contained in the RRC TRANSFER message (e.g., a Delivery Requirement IE or a Delivery Priority IE) in the RRC TRANSFER message. The Delivery Requirement IE indicates whether the MN RRC message should be delivered to UE 3. The Delivery Priority IE indicates whether the MN RRC message should be delivered to UE 3 in priority to other messages or information.
[0139] Fig.18 A specific example of the format of the RRC TRANSFER message including the Delivery Requirement IE is shown. Fig.18 In the example of , if the value of the Delivery Requirement IE is set to “Required”, this means that the PDCP PDU (encapsulating the MN RRC message) should be delivered to UE 3.
[0140] SN 2 may include a central unit (CU) (e.g., gNB-CU) and one or more distributed units (DU) (e.g., gNB-DU). In addition, the CU may include a control plane (CP) unit (e.g., gNB-CU-CP) and one or more user plane (UP) units (e.g., gNB-CU-UP). In this case, Fig.19 As shown, CU (or CU-CP) 1901 may include the delivery requirement IE into a message (F1AP: DL RRC MESSAGE TRANSFER message) to be sent to DU 1902 to forward the RRC message to UE 3 (step 1911).
[0141] Fig. 20 A specific example of the format of a DL RRC MESSAGE TRANSFER message including a delivery requirement IE is shown. Fig. 20 In the example of , in case the value of the Delivery Requirement IE is set to “Required”, this means that the PDCP PDU (encapsulating the RRC message) should be delivered to UE 3.
[0142] Fig.21 An example of the MCG recovery process is shown. Fig.21 In the example of , when an MCG failure is detected in a case where a separate SRB (eg, separate SRB1) has been configured between MN 1 and UE 3, MN 1 performs an inter-MN handover without SN change to recover from the MCG failure.
[0143] Fig.21 The process and Fig.14 However, in Fig.21 , the RRC transfer process (step 2106) occurs before the SN release process (steps 2107 and 2108). In step 2106, MN 1 sends an MN RRC message (e.g., an RRC reconfiguration including reconfigurationWithSync) to UE 3 via the SCG branch of detached SRB1. Specifically, MN 1 sends an RRC TRANSFER message including a PDCP PDU encapsulating the MN RRC message to SN 2. The RRC TRANSFER message indicates that the PDCP PDU should be delivered to UE 3. The RRC TRANSFER message may include a delivery requirement IE set to "necessary". On the other hand, in step 2107, MN 1 does not have to include any indication in the SN RELEASE REQUEST message to associate the message with an MCG failure or its recovery.
[0144] If SN 2 has received an RRC TRANSFER message containing a Delivery Requirement IE set to "Required" (step 2106), then Fig.21 The process in enables SN 2 to delay (or postpone) the release of resources used by UE 3 requested by the SN RELEASE REQUEST message (step 2107) until the delivery of the PDCP PDU (encapsulating the MN RRC message) to UE 3 has been completed. If the Delivery Priority IE is used instead of the Delivery Requirement IE and the value of the IE is set to "High", SN 2 can operate in the same manner as described above.
[0145] It can be modified as follows Fig.21 For example, in the RRC transmission process (equivalent to Fig.21 SN release process (equivalent to step 2106 in Fig.21 2107 and 2108 in the SN RELEASE REQUEST message). In this case, the SN RELEASE REQUEST message does not have to contain any indication that the message is associated with an MCG failure or its recovery. If SN 2 receives an RRC TRANSFER message containing a Delivery Requirement IE after receiving the SN RELEASE REQUEST message, and the value of the IE is set to "Necessary", SN 2 postpones the release of the configuration (or resources) in SN 2. This enables SN 2 to delay (or postpone) the release of resources used by UE 3 requested by the SN RELEASE REQUEST message until the delivery of the PDCP PDU (encapsulating the MN RRC message) to UE 3 is completed.
[0146] Seventh embodiment
[0147] The configuration example of the radio communication network according to the present embodiment is Figure 1 The examples shown are the same. This embodiment provides an improvement in the inter-node messages sent from the MN 1 to the SN 2 (ie, XnAP / X2AP messages).
[0148] As mentioned above, the XnAP / X2AP message requesting SN 2 to modify or change the configuration (or resources) in SN 2 used by UE 3 may include an indication related to an MCG failure. The indication may be an indication of an MCG failure or an indication of recovery from an MCG failure (or recovery of an MCG link). The indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or cause value included in the XnAP / X2AP message. The XnAP / X2AP message may be, for example, an SN MODIFICATION REQUEST message or an SN RELEASE REQUEST message.
[0149] Additionally or alternatively, in this embodiment, any other XnAP / X2AP message (e.g., RRC TRANSFER message or HANDOVER REQUEST message) may include an indication related to an MCG failure. The indication may be an indication of an MCG failure or an indication of recovery from an MCG failure (or recovery of an MCG link).
[0150] exist Fig. 22 In the example of , MN 1 includes an indication of the MCG failure (e.g., MCG failure notification) into an XnAP / X2AP message (e.g., RRC TRANSFER message) sent to SN 2 (step 2201). This enables SN 2 to be aware of the occurrence of the MCG failure. In other words, SN 2 can know that the received XnAP / X2AP message is related to (or due to) the MCG failure or its recovery. In other words, SN 2 can know that the received XnAP / X2AP message is associated with the MCG failure or its recovery.
[0151] Eighth embodiment
[0152] The configuration example of the radio communication network according to the present embodiment is Figure 1 The examples shown are the same. This embodiment provides an improvement to enable notification of MCG failures from the UE 3 to the SN 2.
[0153] In fast MCG recovery using detached SRB1, UE 3 sends an MN RRC message (e.g., MCG Failure Information message) indicating an MCG failure to MN 1 via the SCG branch of detached SRB1. The RLC sublayer of SN 2 receives a PDCP PDU encapsulating the MCG Failure Information message from the SCG RLC sublayer of UE 3, and sends the PDCP PDU to the PDCP sublayer of MN 1. Therefore, the RRC layer of SN 2 cannot know the occurrence of the MCG failure.
[0154] To solve this problem, UE 3 of this embodiment works as follows: UE 3 sends MCG failure information to MN1 via the SCG branch of the separated SRB1. In addition, UE 3 sends a notification of MCG failure to SN 2 via direct control signaling between SN 2 and UE 3. The direct control signaling can be a MAC control element (CE) or SRB3.
[0155] Fig.23An example of the operation of UE 3 is shown. In step 2301, MCG RRC 31 of UE 3 detects an MCG failure (e.g., MCG RLF). In steps 2311-2313, in response to detecting the MCG failure, UE 3 sends MCG failure information to MN 1 via the SCG branch of detached SRB1. In step 2311, MCG RRC 31 of UE 3 generates an MN RRC: MCG failure information message and passes it to MCG PDCP 32. In step 2312, MCG PDCP 32 generates a PDCP PDU (PDCP-C PDU) encapsulating the MCG failure information message and sends the PDCP PDU to MN PDCP 12 of MN 1 via SCG RLC 34 of UE 3, SCG MAC 35 of UE 3, SN MAC 23 of SN 2, and SN RLC 22 of SN 2. At step 2313 , MN RRC11 of MN1 receives the MCG Failure Information message from MN PDCP12 .
[0156] In addition, in steps 2351 to 2354, in response to detecting the MCG failure, UE 3 sends a notification of the MCG failure to SN 2. In step 2351, MCG RRC 31 of UE 3 generates an MCG failure notification to SN 2 and delivers the MCG failure notification to SCG RRC 33 of UE 3. In step 2352, SCG RRC 33 delivers the MCG failure notification to SCGMAC 35 of UE 3. In step 2353, SCG MAC 35 generates a MAC CE indicating the MCG failure notification and sends the MAC CE to SN MAC 23 of SN2. The MAC CE may be included in the same MAC PDU as the PDCP-C PDU in step 2312, or may be included in a MAC PDU different from the PDCP-C PDU. In step 2354, in response to receiving the MAC CE, SN MAC 23 of SN 2 delivers the MCG failure notification to SN RRC 21 of SN 2. This enables UE 3 to notify SN 2 of the MCG failure even in the case where MCG failure information is sent to MN 1 via the SCG branch of the split SRB. Therefore, this enables SN 2 to be aware of the MCG failure.
[0157] exist Fig.23 In FIG. 2 , for the sake of illustration, the direct control signaling process from UE 3 to SN 2 (steps 2351 to 2354) is shown as occurring before the process for sending MCG failure information via the SCG branch of the detached SRB (steps 2311 to 2313). However, the order in which these two processes are performed is not limited. The steps in each process are as follows: Fig.23 It is sufficient to show that the two processes can be performed independently of each other. For example, steps 2351-2354 can be performed after steps 2311-2313 or in parallel with steps 2311-2313.
[0158] Ninth embodiment
[0159] The configuration example of the radio communication network according to the present embodiment is Figure 1 is the same as the example shown. MN 1 in this embodiment, when configuring a separate SRB (e.g., SRB1) to UE 3, notifies UE 3 that the primary path of the uplink is MCG (e.g., the CellGroup of primaryPath is set to MCG). In addition, MN 1 explicitly or implicitly sends permission to UE 3 in advance to switch the uplink primary path of the separate SRB from MCG to SCG. In response to detecting an MCG failure (e.g., MCG RLF) when the separate SRB has been set and the UE has received permission, the UE sends MCG failure information to MN 1 via the SCG branch of the separate SRB. The sending of the MCG failure information from UE 3 to MN 1 is similar to, for example, Fig. 9 After the MCG fault information is sent, the following steps can be performed: Figures 5 to 8 etc., etc. On the other hand, in the case where UE 3 has not received permission, UE 3 can perform an RRC (connection) re-establishment procedure. This enables MN 1 to control the behavior of UE 3 when an MCG failure occurs (i.e., the sending of MCG failure information or RRC re-establishment). The permission can further specify the type of MCG failure. That is, in the event that UE 3 detects one or more specific types of MCG failures, MN 1 can allow UE 3 to switch the uplink main path of the separated SRB from MCG to SCG. Depending on the type of MCG failure detected, UE 3 can choose to send MCG failure information to MN 1 via the SCG branch of the separated SRB.
[0160] The switching of the uplink main path from MCG to SCG may mean that UE 3 (autonomously) switches the configuration of the uplink main path (i.e., RRC configuration) from the configuration for MCG to another configuration for SCG. Alternatively, the switching of the uplink main path from MCG to SCG may mean that UE 3 uses the SCG uplink (i.e., SCG branch) instead of the MCG uplink (i.e., MCG branch). In other words, UE 3 may additionally use the SCG uplink without changing the configuration of the uplink main path.
[0161] Tenth embodiment
[0162] The configuration example of the radio communication network according to the present embodiment is Figure 1 The example shown is the same. In this embodiment, MN 1 sends in advance to UE 3 that configures (or has configured) a detached SRB, an indication (or RRC configuration information) indicating which of the RRC reconnection processing (RRC (connection) re-establishment process) and the MCG recovery processing (MCG (link) recovery process) should be performed when UE 3 detects an MCG failure (e.g., MCG RLF). The MCG recovery process includes: UE 3 sends MCG failure information (e.g., MCG Failure Information) to MN 1 via SN 2 in the detached SRB. This enables MN 1 to control the behavior of UE 3 when an MCG failure occurs (i.e., the sending of MCG failure information or RRC reconnection).
[0163] MN 1 may send information that explicitly indicates a process (procedure) to be performed by UE 3. For example, when MN 1 sends RRC information (e.g., MCG-FailureRecovery IE) indicating a method for recovering an MCG failure (e.g., MCG RLF) to UE 3, MN 1 may notify UE 3 which process should be performed (i.e., RRC reconnection process (e.g., rr-Reestablishment) or MCG failure information sending via the SCG branch of the detached SRB (e.g., fast-MCG-recovery or MCG-failure-indication)). In the case where UE 3 has been notified to send the MCG failure information, UE 3 sends the MCG failure information to MN 1 via the SCG branch of the detached SRB in response to detecting the MCG failure. The sending of the MCG failure information from UE 3 to MN 1 is similar to, for example, Fig. 9 After the MCG fault information is sent, the following steps can be performed: Figures 5 to 8 On the other hand, in the case where the UE 3 has been notified to perform the RRC reconnection process, the UE 3 performs the RRC (connection) reestablishment process.
[0164] Eleventh Embodiment
[0165] The configuration example of the radio communication network according to the present embodiment is Figure 1The example shown is the same. UE 3 in this embodiment switches its uplink main path from MCG to SCG in response to detecting an MCG failure (e.g., MCG RLF), and sends MCG failure information (e.g., MCG FailureInformation) to MN 1 via the SCG branch of the separated SRB (e.g., SRB1). At this time, UE 3 can operate as follows. UE 3 can trigger a report on the uplink transmission buffer status (buffer status report (BSR)) in the SCG in response to the uplink main path being switched from MCG to SCG. For example, when the MCGRRC entity of UE 3 detects an MCG failure, the MCG RRC entity sends an indication to the MCG PDCP entity to switch the uplink main path from MCG to SCG. The MCG MAC entity obtains the buffer amount (data amount) of the MCG failure information (and other data to be sent) from the SCG PDCP entity and the SCG RLC entity to send the MCG failure information in the SCG. Then, the MCG MAC entity sends a buffer information report (BSR) to SN 2 in the SCG via the MCGPHY.
[0166] SN 2 may send an uplink (UL) grant to UE 3 in response to receiving the BSR. In response to receiving the UL grant, UE 3 may send a MN RRC message containing MCG failure information to MN 1 in the SCG branch of detached SRB1. The sending of MCG failure information from UE 3 to MN 1 is similar to, for example, Fig. 9 After the MCG fault information is sent to MN 1, the following steps may be performed: Figures 5 to 8 The process for recovering from an MCG failure described in et al.
[0167] Additionally or alternatively, in response to detecting an MCG failure (e.g., MCG RLF), UE 3 may switch the primary path of each of one or more separate DRBs (MN terminated bearers) terminated by MN 1 and whose uplink primary path has been set to MCG to SCG. Additionally or alternatively, in response to detecting an MCG failure (e.g., MCG RLF), UE 3 may switch the primary path of each of one or more separate DRBs (SN terminated bearers) terminated by SN 2 and whose uplink primary path has been set to MCG to SCG. UE 3 may perform such control on the separate DRBs in the same manner as the control of the separate SRBs described above. Specifically, if UE 3 is instructed (or permitted) to switch the uplink primary path of the separate SRB from MCG to SCG, UE 3 may be deemed to be instructed (or permitted) to switch the uplink primary path of the separate DRB from MCG to SCG as well. Alternatively, MN1 may explicitly or implicitly notify UE 3 in advance whether UE 3 is permitted to switch the primary path of the separate DRB. The MN 1 may notify the UE 3 whether to permit the UE 3 to switch the primary path in units of DRBs.
[0168] Twelfth Embodiment
[0169] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 The example shown is the same. In this embodiment, a direct SRB (ie, SRB3) is configured between SN 2 and UE 3. In this case, upon detecting an MCG failure, MN 1 performs an intra-MN handover without SN change to recover from the MCG failure.
[0170] Fig.24 An example of signaling of MN 1 and SN 2 performed during an intra-MN handover without SN change is shown. In step 2401, MN 1 sends an SN MODIFICATION REQUEST message to SN 2. The SN MODIFICATION REQUEST message requests SN 2 to modify (or update) configuration or resources associated with UE 3 in SN 2. For example, the message may indicate information related to a new security key to request modification (or update) of a security key (e.g., SgNB security key) applicable to an SN terminated bearer terminated in SN 2.
[0171] The SN MODIFICATION REQUEST message of step 2401 also includes an indication to SN 2 that the message is associated with an MCG failure or its recovery. The indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or a cause value contained in the message. Alternatively, the cause value may be, for example, an MCG radio connection or MCG RLF lost by the UE. In response to receiving the indication, SN 2 postpones the modification of the configuration (or resources) in SN 2.
[0172] In step 2402, SN 2 sends an SN MODIFICATION REQUEST ACKNOWLEDGE message to MN 1 to acknowledge the request for modification of SN (or SCG) resources used by UE 3 from MN 1. The message may include a CG-Config message generated by SN 2. The CG-Config message includes the SCG radio configuration (e.g., one or both of scg-CellGroupConfig and scg-RB-Config) generated by SN 2 based on the SN MODIFICATION REQUEST message of step 501.
[0173] In steps 2403 and 2404, MN 1 sends an MN RRC message (e.g., RRC reconfiguration including reconfigurationWithSync) to UE 3 via SRB3. Specifically, in step 2403, MN 1 sends an RRC TRANSFER message including an MNRRC message (or an inter-RAN node message between MN 1 and SN 2 including the MN RRC message) to SN 2. In step 2404, SN 2 generates an SN RRC reconfiguration message including an MN RRC message (or at least a portion of an inter-RAN node message between MN 1 and SN 2 including the MN RRC message), and sends the SN RRC reconfiguration message to UE 3 via SRB3. At this time, SN 2 encrypts the SN RRC reconfiguration message using the security key used by the bearer of SN 2 (e.g., S-KgNB).
[0174] The SCG RRC entity of UE 3 decodes the SN RRC reconfiguration message, extracts the MN RRC message, and passes it to the MCG RRC entity of UE 3. When UE 3 receives the MN RRC message, UE 3 performs intra-MN handover without SN change according to the RRC configuration information (e.g., one or both of securityConfig(HO) and sk-Counter) contained in the MN RRC message. The MN RRC message may include an SN RRC message (or SN RRC configuration) for intra-MN handover without SN change. In this case, the MCG RRC entity of UE 3 passes the SN RRC message to the SCG RRC entity of UE 3. UE 3 performs intra-MN handover without SN change according to the MN RRC message and the SN RRC message.
[0175] In step 2405, after sending the SN RRC reconfiguration message including the MN RRC message (or at least a portion of the RAN node inter-message between MN 1 and SN 2 including the MN RRC message) to UE 3, SN 2 modifies (or updates) the SN (SCG) resources (e.g., the configuration or resources in SN 2) used by UE 3 as requested by the SN MODIFICATION REQUEST message in step 2401. SN 2 may modify (or update) the SN (SCG) resources in response to sending the SN RRC reconfiguration message to UE 3. That is, in Fig.24 In the example of , the SN modification preparation procedure initiated by the MN interacts with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In other words, the SN modification preparation procedure initiated by the MN is associated with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In some implementations, if SN 2 (for example, immediately) receives an RRC TRANSFER message further after receiving the SN MODIFICATIONREQUEST message from MN 1, and if the RRC TRANSFER message contains an MN RRC message to be sent in SRB3 (or an inter-RAN node message between MN 1 and SN 2 containing the MN RRC message), then SN 2 prioritizes the sending of the MN RRC message (or at least a part of the inter-RAN node message between MN 1 and SN 2 containing the MN RRC message) to UE 3 over the SN modification preparation procedure.
[0176] Fig.25 Show Fig.24The operations of MN 1 and SN 2 in steps 2501 to 2504 are the same as those in steps 2401 to 2404. In step 2505, SN 2 receives an SN RRC reconfiguration complete message from UE 3.
[0177] In step 2506, after receiving the SN RRC reconfiguration complete message from UE 3, SN 2 performs the modification (or update) of the SN (SCG) resources used by UE 3 as requested by the SN MODIFICATION REQUEST message in step 2501. SN 2 may modify (update) the SN (SCG) resources in response to receiving the SN RRC reconfiguration complete message from UE 3. That is, in Fig.25 In the example of , the SN modification preparation procedure initiated by the MN interacts with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In other words, the SN modification preparation procedure initiated by the MN is associated with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In some implementations, if SN 2 (for example, immediately) receives an RRC TRANSFER message further after receiving the SN MODIFICATION REQUEST message from MN 1, and if the RRC TRANSFER message contains an MN RRC message to be sent in SRB3 (or an inter-RAN node message between MN 1 and SN 2 containing the MN RRC message), then SN 2 prioritizes the sending of the MN RRC message (or at least a part of the inter-RAN node message between MN 1 and SN2 containing the MN RRC message) to UE 3 over the SN modification preparation procedure.
[0178] Fig.26 Show Fig.24 Steps 2601 to 2605 are different from the process shown in FIG. Fig.25 Steps 2501 to 2505 are the same as in FIG.
[0179] In step 2606, UE 3 sends an RRC reconfiguration complete message to MN 1 via the new PCell indicated by the SpCellConfig IE (servCellIndex of SpCellConfig IE) containing the ReconfigurationWithSync IE. If the MobilityControlInfo IE is used instead of the ReconfigurationWithSync IE, the new PCell can be specified by the targetPhysCellId contained in the IE. In step 2607, MN 1 sends a SNRECONFIGURATION COMPLETE message to SN 2. The SN RECONFIGURATION COMPLETE message indicates that UE 3 has successfully applied the SCG radio configuration (e.g., one or both of the scg-CellGroupConfig and scg-RB-Config) included in the SN MODIFICATION REQUEST ACKNOWLEDGE message in step 2602.
[0180] In step 2608, after receiving the SN RECONFIGURATION COMPLETE message from MN 1, SN 2 performs the modification (or update) of the SN (SCG) resources used by UE 3 as requested by the SN MODIFICATION REQUEST message in step 2601. SN 2 may modify (or update) its SN (SCG) resources in response to receiving the SN RECONFIGURATION COMPLETE message. That is, in Fig.26 In the example of , the SN modification preparation process initiated by the MN interacts with the SN reconfiguration completion process. In other words, the SN modification preparation process initiated by the MN is associated with the SN reconfiguration completion process.
[0181] In some implementations, if SN 2 accepts (or grants) the terminal information (e.g., UE context) modification (i.e., SN MODIFICATION REQUEST) that requires reporting the success of the RRC reconfiguration procedure to MN 1, SN 2 may start a timer (e.g., T DCoverall TXn DCoverall). SN2 may then stop the timer upon receiving the SN RECONFIGURATION COMPLETE message. In addition, if SN 2 further receives an RRC TRANSFER message (for example, immediately after) receiving the SN MODIFICATION REQUEST message from MN 1, and if the RRC TRANSFER message includes an MN RRC message to be sent in SRB3 (or an inter-RAN node message between MN 1 and SN 2 including the MN RRC message), SN 2 prioritizes the sending of the MN RRC message (or at least a portion of the inter-RAN node message between MN 1 and SN 2 including the MN RRC message) to UE 3 over the SN modification preparation procedure. That is, SN 2 does not modify (or update) the terminal information (i.e., SN (SCG) resources), at least until SN 2 receives the SN RECONFIGURATION COMPLETE message.
[0182] Fig. 27 A specific example of the format of the improved RRC TRANSFER message for sending the MN RRC message on SRB3 is shown. Fig. 27 The RRC TRANSFER message in the MN 1 may include an RRC container IE, which includes the MN RRC message (or the RAN node inter-message between MN 1 and SN 2 including the MN RRC message). The RRC container IE may be a sub-IE of a newly defined IE (e.g., MN SRB IE) in the RRC TRANSFER message. In some implementations, if SN 2 receives the RRC container IE in the MN SRB IE, SN 2 will explicitly send the MN RRC message (or at least a part of the RAN node inter-message between MN 1 and SN 2 including the message) contained in the RRC container IE to UE 3. If the RRC TRANSFER message received from MN 1 includes the MN SRB IE (in response to detecting the MN SRB IE), SN 2 may operate to send the RRC message contained in the MN SRB IE in SRB3.
[0183] and Fig.18 Similar to the example in, Fig. 27The MN SRB IE shown may include a Delivery Requirement IE. The Delivery Requirement IE indicates whether the MN RRC message (or at least a portion of the RAN node inter-node message between MN 1 and SN 2 containing the MN RRC message) should be explicitly delivered to UE 3. Alternatively, the Delivery Priority IE indicates whether the MN RRC message (or at least a portion of the RAN node inter-node message between MN 1 and SN 2 containing the MN RRC message) should be delivered to UE 3 in priority to other messages or information. For example, if the value of the Delivery Requirement IE is set to "Required", this means that the MN RRC message (or at least a portion of the RAN node inter-node message between MN 1 and SN 2 containing the MN RRC message) must be delivered to UE 3.
[0184] A new XnAP / X2AP message different from the RRC TRANSFER message may be defined for sending the MNRRC message via SRB3. Fig.28 Show Fig.24 Another variation of the process shown. Steps 2801 and 2802 are Fig.24 Steps 2401 and 2402 in are the same.
[0185] exist Fig.28 In the example of , MN 1 sends an MN MODIFICATION INDICATION message to SN 2 to send an MN RRC message to UE 3 via SRB3 (step 2803). SN 2 sends an SNRRC message (e.g., RRC reconfiguration) containing the requested MN RRC message to UE 3 (step 2804), and receives an SN RRC reconfiguration complete message from UE 3 (step 2805). SN 2 may send a reply message (e.g., MNRECONFIGURATION COMPLETE message or MN MODIFICATION COMPLETE message) to MN 1 in response to the MN MODIFICATION INDICATION message (step 2806). For example, SN 2 may send an MNRECONFIGURATION COMPLETE message to MN 1 in response to receiving the SN RRC reconfiguration complete message from UE 3.
[0186] In step 2807, after receiving the SN RRC reconfiguration complete message from UE 3, SN 2 performs the modification (or update) of the SN (SCG) resources used by UE 3 as requested by the SN MODIFICATION REQUEST message in step 2801. SN 2 may modify (or update) the SN (SCG) resources after sending the MN RECONFIGURATION COMPLETE message to MN 1.
[0187] Fig.29 A specific example of the format of the MN MODIFICATION INDICATION message is shown. Fig.29 In the example of FIG. 1 , the MN MODIFICATION INDICATION message includes an M-NG-RAN node to S-NG-RAN node container IE. The IE includes a CG-ConfigInfo message. The CG-ConfigInfo message indicates a MN RRC message (e.g., an RRC (connection) reconfiguration message). Fig.30 The CG-ConfigInfo message shown may include a sourceConfigMCG field 3001, wherein the sourceConfigMCG field 3001 includes an MN RRC message (e.g., an RRC (connection) reconfiguration message). In the case where MN 1 and SN 2 use different radio access technologies (RATs) (e.g., in the case of EN-DC), the sourceConfigMCG field 3001 may transparently include an RRC message of the source RAT (i.e., an MN RRC message). In other words, SN 2 may forward the information in the sourceConfigMCG field 3001 to UE 3 without parsing or identifying the information in the sourceConfigMCG field 3001. On the other hand, in the case where MN 1 and SN 2 use the same RAT or the same kind of PDCP (e.g., NR PDCP) (e.g., in the case of NR-DC or NGEN-DC), the sourceConfigMCG field 3001 may explicitly include an RRC message of the source RAT.
[0188] Fig.31 Show Fig.28 A variation of the process shown. Fig.31 In the example of , the MN MODIFICATION NOTIFICATION / RESPONSE message (steps 3101 and 3102) is used instead of the SN MODIFICATION REQUEST / ACKNOWLEDGE message. Fig.31In the example of , MN 1 sends a MN MODIFICATION NOTIFICATION message to SN 2 (step 3101). The MN MODIFICATION NOTIFICATION message indicates to SN 2 that modification (or reconfiguration) of the SCG associated with the MCG modification (or change or reconfiguration) is required. Like the SN MODIFICATION REQUEST message, the MN MODIFICATION NOTIFICATION message requests SN 2 to modify (or update) the configuration or resources used by UE 3 in SN 2. The MN MODIFICATION NOTIFICATION message may include an indication to SN 2 that the message is associated with an MCG failure or recovery thereof. Alternatively, the sending of the MN MODIFICATION NOTIFICATION message itself may be associated with an MCG failure or recovery thereof (i.e., it may imply an MCG failure or recovery thereof). In other words, the MN MODIFICATION NOTIFICATION message is sent to recover from an MCG failure, and SN 2 may recognize that MN 1 is attempting to recover from an MCG failure by receiving (in response to receiving) the message.
[0189] In step 3102, SN 2 sends a MN MODIFICATION NOTIFICATION RESPONSE message to MN 1 to acknowledge the request for SN (SCG) resource modification used by UE 3 from MN 1. This message may contain a CG-Config message generated by SN 2 in the same manner as the SN MODIFICATION REQUEST ACKNOWLEDGE message.
[0190] In step 3103, MN 1 sends a MN MODIFICATION INDICATION message to SN 2 to send a MN RRC message (eg, RRC reconfiguration including reconfigurationWithSync) to UE 3 via SRB3.
[0191] Steps 3104 to 3105 and Fig.28 Upon receiving the SN RRC reconfiguration complete message from UE 3, SN 2 may send a MN MODIFICATION COMPLETE message to MN 1 (step 3106). The MN MODIFICATION COMPLETE message may be referred to as a MN RECONFIGURATION COMPLETE message. In step 3107, Fig.28Similar to step 2807 in step 3101, SN 2 modifies (or updates) the SN (SCG) resources used by UE 3 as requested by the MN MODIFICATION NOTIFICATION message in step 3101.
[0192] The MN MODIFICATION NOTIFICATION in step 3101, the MN MODIFICATION NOTIFICATION RESPONSE in step 3102, and the MN MODIFICATION REQUEST message in step 3103 (and the MN MODIFICATION COMPLETE message in step 3106) may be specified as a single (combined) process. In this process, these actions may be performed as a series of actions (i.e., in conjunction with each other). This process may be referred to, for example, as a MN MODIFICATION preparation process or a MN RECOVERY preparation process.
[0193] Fig.32 Show Figure 24 to Figure 26 A specific example of the process shown. Fig.32 Steps 3205 to 3208 and Fig.24 Steps 2401 to 2404, Fig.25 Steps 2501 to 2504 and Fig.26 Corresponding to steps 2601 to 2604. Fig.32 Step 3209 and Fig.25 Step 2505 and Fig.26 Corresponding to step 2605. Fig.32 Steps 3212 and 3213 are the same as Fig.26 Corresponding to steps 2606 and 2607.
[0194] exist Fig.32 In step 3201, UE 3 detects an MCG failure (e.g., MCG RLF). In step 3202, UE 3 sends MCG failure information to SN 2 via SRB3. In step 3203, SN 2 forwards the MCG failure information to MN 1. The RRCTRANSFER message can be used to transmit the MCG failure information from SN 2 to MN 1. In step 3204, MN 1 determines an MCG failure recovery procedure in response to receiving the MCG failure information. The MCG failure recovery procedure includes an intra-MN handover procedure without SN change (i.e., steps 3205 to 3214).
[0195] exist Fig.32In the example of , the RRC TRANSFER message (step 3207) can be replaced by the MN MODIFICATION INDICATION message (step 2803) or the MN MODIFICATION REQUEST message (step 3103). In this case, SN 2 can send a MN RECONFIGURATION COMPLETE message (or MN MODIFICATION COMPLETE message) to MN 1 (step 3210).
[0196] Thirteenth Embodiment
[0197] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 In this embodiment, when MCG failure is detected in the case where a direct SRB (eg, SRB3) has been configured between SN 2 and UE 3, MN 1 performs an inter-MN handover without SN change to recover from the MCG failure.
[0198] Fig.33 FIG. 3 shows an example of signaling between MN 1 and SN 2 performed during an inter-MN handover without SN change. Steps 3301 and 3302 are similar to Fig.11 Steps 1101 and 1102 are the same. Specifically, in step 3301, MN 1 sends a SN RELEASE REQUEST message to SN 2. MN 1 includes a UE context retention indicator IE set to "true" in the SN RELEASE REQUEST message to indicate to SN 2 that the UE context in SN 2 is to be maintained (kept).
[0199] The SN RELEASE REQUEST message in step 3301 also includes an additional indication to indicate to SN 2 that the message is associated with an MCG failure or its recovery. The additional indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or a cause value contained in the message. In response to receiving the additional indication, SN 2 postpones the release of a configuration (or resource) within SN 2. Specifically, SN 2 may delay the release of resources for a signaling connection associated with UE 3 between MN 1 and SN 2. Additionally or alternatively, SN 2 may postpone the release of radio resources allocated to UE 3.
[0200] In step 3302, SN 2 sends an SN RELEASE REQUEST ACKNOWLEDGE message to MN 1 to acknowledge the request from MN 1 for releasing SN (SCG) resources used by UE 3.
[0201] In steps 3303 and 3304, MN 1 sends an MN RRC message (eg, RRC reconfiguration including reconfigurationWithSync) to UE 3 via SRB3. Steps 3303 and 3304 are similar to Fig.24 Steps 2403 and 2404 in are the same.
[0202] In step 3305, after sending the MN RRC message to UE 3 (or at least a part of the RAN node inter-node message between MN 1 and SN 2 including the MN RRC message), SN 2 releases the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 3301. SN 2 may release the SN (SCG) resources in response to sending the MN RRC message to UE 3 (or at least a part of the RAN node inter-node message between MN 1 and SN 2 including the MN RRC message). That is, in step 3306, Fig.33 In the example of , the SN release procedure initiated by the MN interacts with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In other words, the SN release procedure initiated by the MN is associated with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In some implementations, if SN 2 (for example, immediately) receives an RRC TRANSFER message further after receiving the SN RELEASE REQUEST message from MN 1, and the RRC TRANSFER message contains an MN RRC message to be sent to UE 3 (or an inter-RAN node message between MN 1 and SN 2 containing the MN RRC message), then SN 2 prioritizes the sending of the MN RRC message (or at least a portion of the inter-RAN node message between MN 1 and SN 2 containing the MN RRC message) to UE 3 over the SN release procedure.
[0203] Fig.34 Show Fig.33 The operations of MN 1 and SN 2 in steps 3401 to 3404 are the same as those in steps 3301 to 3304. In step 3405, SN 2 receives an SN RRC reconfiguration complete message from UE 3.
[0204] In step 3406, after receiving the SN RRC reconfiguration complete message from UE 3, SN 2 releases the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 3501. SN 2 may release the SN (SCG) resources in response to receiving the SN RRC reconfiguration complete message from UE 3. That is, in Fig.34 In the example of , the SN release procedure initiated by the MN interacts with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In other words, the SN release procedure initiated by the MN is associated with the RRC transfer procedure (or the SN RRC reconfiguration procedure). In some implementations, if SN 2 (for example, immediately) receives an RRC TRANSFER message further after receiving the SN RELEASE REQUEST message from MN 1, and the RRC TRANSFER message contains an MN RRC message to be sent to UE 3 (or an inter-RAN node message between MN 1 and SN 2 containing the MN RRC message), then SN 2 prioritizes the sending of the MN RRC message (or at least a part of the inter-RAN node message between MN 1 and SN 2 containing the MN RRC message) to UE 3 over the SN release procedure.
[0205] Fig.35 Show Fig.33 Steps 3501 to 3505 are similar to Fig.34 The steps 3401 to 3405 are the same as in step 3506. In step 3507, the target MN 4 sends an SN RECONFIGURATION COMPLETE message to the target MN 4 via the new PCell indicated by the SpCellConfig IE (servCellIndex of the SpCellConfig IE) containing the ReconfigurationWithSync IE.
[0206] In step 3508, after receiving the SN RECONFIGURATION COMPLETE message from the target MN 4, SN2 releases the SN (SCG) resources used by the UE 3 as requested by the SN RELEASE REQUEST message in step 3501. SN2 may release the SN (SCG) resources in response to receiving the SN RECONFIGURATION COMPLETE message. Fig.35 In the example of , the SN release process initiated by the MN interacts with the SN reconfiguration completion process. In other words, the SN release process initiated by the MN is associated with the SN reconfiguration completion process.
[0207] Can be further modified Fig.33 Instead of the SN RELEASE REQUEST / ACKNOWLEDGE message, the new XnAP / X2AP message can be used. For example, Fig.31 Similar to the process in, MN MODIFICATION NOTIFICATION / RESPONSE message may be used. Additionally or alternatively, a new XnAP / X2AP message (e.g., Fig.31 The MN MODIFICATION REQUEST message in the RRC TRANSFER message is used instead of the RRC MODIFICATION REQUEST message in the RRC TRANSFER message. Fig.31 As described above, the MN MODIFICATION NOTIFICATION, MN MODIFICATION RESPONSE and MN MODIFICATION REQUEST messages may be specified together as a single (combined) procedure.
[0208] Fig.36 Show Figures 33 to 35 A specific example of the process shown. Fig.36 Steps 3607 to 3610 and Fig.33 Steps 3301 to 3304, Fig.34 Steps 3401 to 3404 and Fig.35 Corresponding to steps 3501 to 3504. Fig.36 Step 3611 and Fig.34 Step 3405 and Fig.35 Corresponding to step 3505. Fig.36 Steps 3612 and 3613 are the same as Fig.35 The steps 3506 and 3507 correspond to each other. Fig.36 In step 3613, upon receiving the SN RECONFIGURATION COMPLETE message (or MNRECONFIGURATION COMPLETE message) from the target MN 4, SN 2 may release the SN (SCG) resources used by UE 3 requested by the SN RELEASEREQUEST message of step 3607, except for the terminal information (e.g., UE context) of UE 3. For example, SN 2 may release the radio resources associated with UE 3 for the MR-DC with the source MN 1 (e.g., the source SCG lower layer configuration (e.g., CellGroupConfig)).
[0209] exist Fig.36In step 3601, UE 3 sends MCG fault information to SN 2 via SRB 3. In step 3602, SN 2 forwards the MCG fault information to MN 1. MN 1 determines the MCG fault recovery procedure based on the reception of the MCG fault information. The MCG fault recovery procedure includes an inter-MN handover procedure without SN change (i.e., steps 3603 to 3616). The inter-MN handover procedure without SN change includes signaling with the core network (CN) 5 for path switching (step 3614). When SN 2 receives a UE CONTEXT RELEASE message from the source MN 1 (step 3616), SN 2 releases the terminal-related resources of UE 3 maintained for the MR-DC with the source MN 1 (e.g., C-plane resources with the source MN 1 related to the UE context).
[0210] Fourteenth Embodiment
[0211] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 The example shown is the same. In this embodiment, when an MCG failure is detected when a direct SRB (e.g., SRB3) has been configured between SN 2 and UE 3, MN 1 performs a MN to gNB change procedure with SN release to recover from the MCG failure.
[0212] Fig.37 A specific example of the MN to gNB change procedure involving SN release is shown. Fig.37 In step 3701, UE 3 sends MCG failure information to SN 2 via SRB 3. In step 3702, SN 2 forwards the MCG failure information to MN 1. MN 1 determines the MCG failure recovery process in response to receiving the MCG failure information. The MCG failure recovery process includes a MN to gNB change process involving SN release (i.e., steps 3703 to 3714).
[0213] In step 3705, MN 1 (i.e., the source MN) sends an SN RELEASE REQUEST message to SN 2. The SN RELEASE REQUEST message of step 3705 also includes an indication to SN 2 that the message is associated with an MCG failure or its recovery. The indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or a cause value included in the message. In response to receiving the indication, SN 2 postpones the release of the configuration (or resources) in SN 2. Specifically, SN 2 may delay the release of resources for a signaling connection associated with UE 3 between MN 1 and SN 2. In addition, SN 2 may postpone the release of terminal information (e.g., UE context) associated with UE 3. In addition, SN 2 may postpone the release of radio resources (e.g., SCG configuration) associated with UE 3.
[0214] In step 3706, SN 2 sends an SN RELEASE REQUEST ACKNOWLEDGE message to MN 1 to acknowledge the request from MN 1 for releasing the SN (SCG) resources used by UE 3.
[0215] In steps 3707 and 3708, MN 1 sends an MN RRC message (eg, RRC reconfiguration including reconfigurationWithSync) to UE 3 via SRB3. Steps 3707 and 3708 are similar to Fig.24 Steps 2403 and 2404 and Fig.33 Steps 3303 and 3304 are the same.
[0216] In some implementations, in response to sending (step 3708) an MN RRC message (or at least a portion of an inter-RAN node message between MN 1 and SN 2 that includes the MN RRC message) to UE 3, SN 2 may release the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 3705. Alternatively, SN 2 may release the SN (SCG) resources in response to receiving an SN RRC reconfiguration complete message from UE 3 (step 3709). Alternatively, SN 2 may release the SN (SCG) resources in response to receiving an SN RECONFIGURATION COMPLETE message from the target gNB 6 (step 3711). For example, SN 2 may perform the release of the SN (SCG) resources used by UE 3 as requested by the SN RELEASE REQUEST message in step 3705, except for the terminal information (e.g., UE context) of UE 3.
[0217] Fifteenth Embodiment
[0218] This embodiment provides a specific example of the operation of the MN 1 and the SN 2 explained in the first embodiment. The configuration example of the radio communication network according to this embodiment is similar to that of the MN 1 and the SN 2. Figure 1 The example shown is the same. In this embodiment, when an MCG failure is detected when a direct SRB (e.g., SRB3) has been configured between SN 2 and UE 3, MN 1 performs an SN to gNB change (role change) procedure to recover from the MCG failure.
[0219] Fig.38 A specific example of the SN to gNB change process is shown. Fig.38 In step 3801, UE 3 sends MCG failure information to SN 2 via SRB 3. In step 3802, SN 2 forwards the MCG failure information to MN 1. MN 1 determines the MCG failure recovery process in response to receiving the MCG failure information. The MCG failure recovery process includes a SN to gNB change process (i.e., steps 3803 to 3812).
[0220] In step 3803, MN 1 (i.e., source MN) sends a HANDOVER REQUEST message to SN 2. The HANDOVER REQUEST message in step 3803 may contain information that explicitly or implicitly indicates that SN 2 is expected to manage UE 3 as an MN (or in a standalone (SA) manner) after the handover. For example, MN 1 may indicate this by including a UE Context Reference IE at the SgNB in the message. When SN 2 receives the information (e.g., UE Context Reference IE at the SgNB), SN 2 understands (or recognizes) that SN 2 is expected (or required) to perform a handover as a (target) MN (or in a SA manner) for UE 3 that is undergoing MR-DC with MN 1 and accepts the UE 3.
[0221] In step 3804, SN 2 sends a HANDOVER REQUEST ACKNOWLEDGE message to MN 1 to indicate that it accepts the handover of UE 3. SN 2 may include a UE context retention indicator IE (i.e., set to true) in the message, thereby indicating to MN 1 that SN 2 will manage UE 3 as a MN (or in SA mode).
[0222] In step 3805, MN 1 (i.e., source MN) sends an SN RELEASE REQUEST message to SN 2. The SN RELEASE REQUEST message in step 3805 may include a UE context retention indicator IE. In addition, the SN RELEASE REQUEST message includes an indication to SN 2 that the message is associated with an MCG failure or its recovery. The indication may be, for example, referred to as an MCG failure recovery notification, an MCG link recovery notification, or an MCG failure notification. The indication may be an IE or a cause value included in the message. In response to receiving the indication, SN 2 postpones the release of the configuration (or resources) in SN 2. Specifically, SN 2 may delay the release of resources for a signaling connection associated with UE 3 between MN 1 and SN 2. In addition, SN 2 may postpone the release of terminal information (e.g., UE context) associated with UE 3. In addition, SN 2 may postpone the release of radio resources (e.g., SCG lower layer configuration) associated with UE 3 for MR-DC with source MN 1.
[0223] In step 3806, SN 2 sends an SN RELEASE REQUEST ACKNOWLEDGE message to MN 1 to acknowledge the request from MN 1 for releasing SN (SCG) resources used by UE 3.
[0224] In steps 3807 and 3808, MN 1 sends an MN RRC message (eg, RRC reconfiguration including reconfigurationWithSync) to UE 3 via SRB3. Steps 3807 and 3808 are similar to Fig.24 Steps 2403 and 2404 and Fig.34 Steps 3403 and 3404 are the same. Specifically, although SN 2 is the target RAN node (MN or SAgNB) for the handover, SN 2 serves as the source SN at least until the sending of the MN RRC message.
[0225] In some implementations, SN 2 may release the SN (SCG) resources used by UE 3 as requested by the SNRELEASE REQUEST message in step 3805 in response to sending (step 3808) an MN RRC message (or at least a portion of an inter-RAN node message between MN 1 and SN 2 that includes the MNRRC message) to UE 3. Alternatively, SN 2 may release the SN (SCG) resources used for the MR-DC with the source MN 1 in response to receiving a HARQ-ACK (and RLC ARQ-ACK) from UE 3 (step 3809) or receiving an RRC reconfiguration complete message from UE 3 (step 3810).
[0226] Sixteenth Embodiment
[0227] The configuration example of the radio communication network according to the present embodiment is Figure 1 The examples shown are the same. This embodiment provides an improvement of the RRC TRANSFER message sent from the MN 1 to the SN 2 to transfer the MN RRC message.
[0228] Fig.39 An example of the MCG recovery process is shown. Fig.39 In the example of , when an MCG failure is detected in a case where a direct SRB (ie, SRB3) has been configured between SN 2 and UE 3, MN 1 performs an inter-MN handover without SN change to recover from the MCG failure.
[0229] Fig.39 The process and Fig.36 However, in Fig.39 In the process of MN RRC message transmission from MN 1 to UE 3 via SRB3 (steps 3907 to 3910) occurs before the SN release process (steps 3911 and 3912). Steps 3907 to 3910 are related to Fig.28 Upon receiving the MN MODIFICATION INDICATION message in step 3907, SN 2 recognizes that the MN RRC message must be delivered to UE 3. On the other hand, in step 3911, MN 1 does not have to include in the SN RELEASE REQUEST message any indication to associate the message with the MCG failure or its recovery.
[0230] The RRC TRANSFER message may be used instead of the MN MODIFICATION INDICATION message in step 3907. In this case, the RRC TRANSFER message indicates that the PDCP PDU must be delivered to the UE 3. The RRC TRANSFER message may contain a Delivery Requirement IE set to "Required".
[0231] Seventeenth Embodiment
[0232] The configuration example of the radio communication network according to the present embodiment is Figure 1The example shown is the same. In this embodiment, MN 1 sends an indication (or RRC configuration information) in advance to UE 3 indicating which of RRC reconnection processing (RRC (connection) re-establishment process) and MCG recovery processing (MCG (link) recovery process) should be performed when UE 3, which has been configured to be able to send RRC messages to SN 2 via SRB3, detects an MCG failure (e.g., MCG RLF). The MCG recovery process includes: UE3 sends MCG failure information (e.g., MCG Failure Information) to SN 2 via SRB3. In addition, the MCG recovery process may include: SN 2, which receives the MCG failure information, sends the MCG failure information or control information derived therefrom to MN 1. This enables MN 1 to control the behavior of UE 3 when an MCG failure occurs (i.e., the sending of MCG failure information or RRC reconnection).
[0233] MN 1 may send information that explicitly indicates a process (procedure) to be performed by UE 3. When (or after) SN 2 sends RRC configuration (e.g., RadioBearerConfig IE) of SRB3 to UE 3, MN 1 may notify UE 3 of the process (procedure) via an MN RRC message (e.g., RRC (connection) reconfiguration). For example, when MN 1 sends RRC information (e.g., MCG-FailureRecovery IE) indicating a method for recovering an MCG failure (e.g., MCG RLF) to UE 3, MN 1 may notify UE 3 of which process should be performed (i.e., RRC reconnection process (e.g., rr-Reestablishment) or MCG failure information transmission to SN 2 via SRB3 (e.g., fast-MCG-recovery or MCG-failure-indication)). In the case where UE 3 has been notified to send MCG failure information, UE 3 sends the MCG failure information to SN 2 via SRB3 in response to detecting an MCG failure. SN 2 may send the received MCG failure information or control information derived therefrom to MN 1. The sending of MCG failure information from UE 3 to SN 2 and MN 1 is similar to Fig.32 After the MCG fault information is sent, the following steps can be performed: Figures 24 to 26etc., for recovering from an MCG failure. On the other hand, in the case where UE 3 has been notified to perform an RRC reconnection process, UE 3 performs an RRC (connection) re-establishment process. The notification may also specify the type of MCG failure. In other words, in the case where UE 3 detects one or more than one specific type of MCG failure among multiple types of MCG failures, MN 1 may allow UE 3 to send MCG failure information to SN 2 via SRB3. Depending on the type of MCG failure detected, UE 3 may decide whether to send MCG failure information to SN 2 in SRB3 or perform an RRC reconnection process.
[0234] MN 1 may detect whether SRB3 is established based on bearer information (e.g., scg-RB-Config) included in SCG configuration information (e.g., CG-Config message) received from SN 2. Alternatively, SN 2 may explicitly notify MN 1 of information indicating whether SRB3 is established using IE of an XnAP / X2AP message.
[0235] SN 2 may determine which process UE 3 is to perform (i.e., RRC reconnection process (e.g., rr-Reestablishment) or sending MCG failure information (e.g., fast-MCG-recovery or MCG-failure-indication) to SN 2 in SRB3), and notify MN 1 of the decision. Alternatively, SN 2 may decide whether to allow UE 3 to send MCG-Failure-indication using SRB3, and notify MN 1 of the result (permitted or not permitted). MN 1 may send information indicating the process (procedure) to be performed by UE 3 according to or based on the notification from SN 2.
[0236] Eighteenth Embodiment
[0237] The configuration example of the radio communication network according to the present embodiment is Figure 1The example shown is the same. In this embodiment, SN 2 sends an indication (or RRC configuration information) in advance to UE 3 indicating which of the RRC reconnection processing (RRC (connection) re-establishment process) and the MCG recovery processing (MCG (link) recovery process) should be performed when UE 3, which has been configured to be able to send RRC messages to SN 2 via SRB3, detects an MCG failure (e.g., MCG RLF). The MCG recovery process includes: UE3 sends MCG failure information (e.g., MCG Failure Information) to SN 2 via SRB3. In addition, the MCG recovery process may include: SN 2, which receives the MCG failure information, sends the MCG failure information or control information derived therefrom to MN 1. This enables SN 2 to control the behavior of UE 3 when an MCG failure occurs (i.e., the sending of MCG failure information or RRC reconnection).
[0238] In some implementations, SN 2 may send an SN RRC message (e.g., RRC (connection) reconfiguration) to UE 3 via SRB 3 or via MN 1, the SN RRC message including information (e.g., rr-Reestablishment, fast-MCG-recovery, or MCG-failure-indication) explicitly indicating the processing (procedure) to be performed by UE 3. In the case of transmission via MN 1, the SN RRC message is included in the MN RRC message sent from MN 1 to UE 3.
[0239] Alternatively, when (or after) sending the RRC configuration of SRB3 (e.g., RadioBearerConfig IE) to UE 3, SN 2 may send information to UE 3 indicating whether UE 3 is allowed to send MCG failure information in SRB3 (or UE 3 is allowed to do so). For example, SN 2 may include the information in the bearer configuration information (e.g., RadioBearerConfig) or SCG configuration information (e.g., CellGroupConfig) within the SN RRC message (e.g., RRC (Connection) Reconfiguration) to be sent to UE 3. The SN RRC message may be sent by SRB3 or via MN 1. Alternatively, SN 2 may send the information to MN 1 via a RAN inter-node message (e.g., CG-Config), and MN 1 may include the information in the SCG configuration information (e.g., scg-RB-Config or nr-RadioBearerConfig) within the MN RRC message to be sent to UE 3. The permission may further specify the type of MCG failure. In other words, if UE 3 detects a specific one or more than one MCG failure types among multiple MCG failure types, SN 2 may allow UE 3 to send MCG failure information to SN 2 in SRB 3. Depending on the type of MCG failure detected, UE 3 may decide whether to send MCG failure information to SN 2 in SRB 3 or perform RRC reconnection processing.
[0240] In some implementations, SN 2 sends RRC configuration (e.g., RadioBearerConfig IE) of SRB3 to UE 3 (i.e., instructs UE 3 to establish SRB3), which may implicitly indicate to UE 3 that UE 3 is allowed to send MCG failure information on SRB3. In the case that UE 3 receives the RRC configuration for establishing SRB3, UE 3 may deem that, when UE 3 detects MCG failure after establishing SRB3, UE 3 is instructed (or allowed) to send MCG failure information to SN 2 in SRB3.
[0241] In the case where UE 3 is instructed, configured or allowed to send MCG failure information, UE 3 sends MCG failure information to SN 2 via SRB 3 in response to detecting an MCG failure. In this case, SN 2 may send the received MCG failure information or control information derived therefrom to MN 1. The sending of MCG failure information from UE 3 to SN 2 and MN 1 is similar to Fig.32 After the MCG fault information is sent, the following steps can be performed: Figures 24 to 26On the other hand, when UE 3 is instructed or configured to perform an RRC re-establishment procedure, or when UE 3 is not allowed to send MCG failure information in SRB3, UE 3 performs an RRC (connection) re-establishment procedure.
[0242] SN 2 may explicitly transmit information indicating which process (i.e., RRC reconnection process or MCG recovery process) UE 3 should perform to MN 1 in an IE included in an XnAP / X2AP message. Alternatively, MN 1 may identify which process (i.e., RRC reconnection process or MCG recovery process) UE 3 performs based on SCG configuration information (e.g., CG-Config message) received from SN 2. MN 1 may detect whether SRB3 is established based on bearer information (e.g., scg-RB-Config) included in SCG configuration information (e.g., CG-Config message) received from SN 2. Alternatively, SN 2 may explicitly notify MN 1 of information indicating whether SRB3 is established using an IE of an XnAP / X2AP message.
[0243] The following provides structural examples of the MN 1, SN 2, and UE 3 according to the above-described embodiment. Fig.40 is a block diagram showing a structural example of the MN 1 according to the above-described embodiment. The SN 2 may have Fig.40 The same structure as shown. Fig.40 MN 1 includes a radio frequency transceiver 4001, a network interface 4003, a processor 4004, and a memory 4005. The RF transceiver 4001 performs analog RF signal processing to communicate with the UE. The RF transceiver 4001 may include multiple transceivers. The RF transceiver 4001 is coupled to the antenna array 4002 and the processor 4004. The RF transceiver 4001 receives modulation symbol data from the processor 4004, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 4002. In addition, the RF transceiver 4001 generates a baseband receive signal based on the receive RF signal received by the antenna array 4002, and supplies the baseband receive signal to the processor 4004. The RF transceiver 4001 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
[0244] The network interface 4003 is used to communicate with network nodes (eg, MN 1 and control nodes and transmission nodes in the core network). The network interface 4003 may, for example, include a network interface card (NIC) compliant with the IEEE 802.3 series.
[0245] The processor 4004 performs digital baseband signal processing (i.e., data plane processing) and control plane processing for radio communication. The processor 4004 may include multiple processors. The processor 4004 may, for example, include a modulation and demodulation processor (e.g., a digital signal processor (DSP)) for performing digital baseband signal processing and a protocol stack processor (e.g., a central processing unit (CPU) or a microprocessing unit (MPU)) for performing control plane processing. The processor 4004 may include a digital beamformer module for beamforming. The digital beamformer module may include a multiple-input multiple-output (MIMO) encoder and a precoder.
[0246] The memory 4005 is composed of a combination of volatile memory and non-volatile memory. The volatile memory is, for example, a static random access memory (SRAM), a dynamic RAM (DRAM) or a combination thereof. The non-volatile memory is, for example, a mask read-only memory (MROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk drive or any combination thereof. The memory 4005 may include a storage unit located separately from the processor 4004. In this case, the processor 4004 can access the memory 4005 via the network interface 4003 or an I / O interface (not shown).
[0247] The memory 4005 may store one or more software modules (computer programs) 4006 including instructions and data for performing the processing of the MN 1 described in the above embodiments. In some implementations, the processor 4004 may be configured to load the software module 4006 from the memory 4005 and execute the loaded software module, thereby performing the processing of the MN 1 described in the above embodiments.
[0248] In the case where MN 1 is a central unit in a C-RAN deployment (e.g., eNB-CU or gNB-CU), MN 1 does not need to include RF transceiver 4001 (and antenna array 4002).
[0249] Fig.414 is a block diagram showing a structural example of UE 3. A radio frequency (RF) transceiver 4101 performs analog RF signal processing to communicate with MN 1 and SN 2. The RF transceiver 4101 may include a plurality of transceivers. The analog RF signal processing performed by the RF transceiver 4101 includes up-conversion, down-conversion, and amplification. The RF transceiver 4101 is coupled to an antenna array 4102 and a baseband processor 4103. The RF transceiver 4101 receives modulation symbol data (or OFDM symbol data) from the baseband processor 4103, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 4102. In addition, the RF transceiver 4101 generates a baseband receive signal based on the receive RF signal received by the antenna array 4102, and supplies the baseband receive signal to the baseband processor 4103. The RF transceiver 4101 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.
[0250] The baseband processor 4103 performs digital baseband signal processing (i.e., data plane processing) and control plane processing for radio communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data separation / concatenation, (c) synthesis / decomposition of transmission format (i.e., transmission frame), (d) channel coding / decoding, (e) modulation (i.e., symbol mapping) / demodulation, and (f) generation of OFDM symbol data (i.e., baseband OFDM signal) using inverse fast Fourier transform (IFFT). On the other hand, control plane processing includes communication management of layer 1 (e.g., transmit power control), layer 2 (e.g., radio resource management and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., signaling related to attachment, mobility, and call management).
[0251] The digital baseband signal processing of the baseband processor 4103 may include, for example, signal processing of a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a MAC layer, and a PHY layer. In addition, the control plane processing performed by the baseband processor 4103 may include processing of a non-access stratum (NAS) protocol, an RRC protocol, and a MAC CE.
[0252] The baseband processor 4103 may perform MIMO encoding and precoding for beamforming.
[0253] The baseband processor 4103 may include a modulation and demodulation processor (e.g., DSP) for performing digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) for performing control plane processing. In this case, the protocol stack processor for performing control plane processing may be integrated with the application processor 4104 described later.
[0254] The application processor 4104 is also referred to as a CPU, an MPU, a microprocessor, or a processor core. The application processor 4104 may include a plurality of processors (or processor cores). The application processor 4104 loads a system software program (operating system (OS)) and various application programs (e.g., a call application, a WEB browser, a mail program, a camera operation application, and a music player application) from the memory 4106 or from other memories, and executes these programs, thereby providing various functions of the UE 3.
[0255] In some implementations, such as Fig.41 As shown by the dotted line (4105) in FIG. 4 , the baseband processor 4103 and the application processor 4104 may be integrated on a single chip. In other words, the baseband processor 4103 and the application processor 4104 may be implemented in a single system on chip (SoC) device 4105. The SoC device may be referred to as a large scale integration (LSI) or a chipset.
[0256] The memory 4106 is a volatile memory, a non-volatile memory, or a combination thereof. The memory 4106 may include a plurality of memory devices that are physically independent of each other. The volatile memory is, for example, an SRAM, a DRAM, or a combination thereof. The non-volatile memory is, for example, an MROM, an EEPROM, a flash memory, a hard disk drive, or any combination thereof. The memory 4106 may, for example, include an external memory device accessible from the baseband processor 4103, the application processor 4104, and the SoC 4105. The memory 4106 may include an internal memory device integrated in the baseband processor 4103, the application processor 4104, or the SoC 4105. In addition, the memory 4106 may include a memory in a universal integrated circuit card (UICC).
[0257] The memory 4106 may store one or more software modules (computer programs) 4107 including instructions and data for performing the processing of the UE 3 described in the above embodiments. In some implementations, the baseband processor 4103 or the application processor 4104 may load these software modules 4107 from the memory 4106 and execute the loaded software modules, thereby performing the processing of the UE 3 described in the above embodiments with reference to the drawings.
[0258] The control plane processing and operations performed by UE 3 described in the above embodiment can be implemented by elements other than the RF transceiver 4101 and the antenna array 4102, that is, by a memory 4106 for storing a software module 4107, and one or both of the baseband processor 4103 and the application processor 4104.
[0259] As mentioned above Fig.40 and 41As described, the processors included in MN 1, SN 2 and UE 3 according to the above-mentioned embodiment each execute one or more programs, and the one or more programs include instructions for causing the computer to execute the algorithm described with reference to the accompanying drawings. These programs can be stored and provided to the computer using any type of non-transitory computer-readable medium. Non-transitory computer-readable media include any type of tangible storage media. Examples of non-transitory computer-readable media include magnetic storage media (such as floppy disks, tapes, hard disk drives, etc.), optical magnetic storage media (for example, magneto-optical disks), compact disk read-only memories (CD-ROMs), CD-Rs, CD-R / Ws, and semiconductor memories (such as mask ROMs, programmable ROMs (PROMs), erasable PROMs (EPROMs), flash ROMs, random access memories (RAMs), etc.). These programs can be provided to the computer using any type of temporary computer-readable media. Examples of temporary computer-readable media include electrical signals, optical signals, and electromagnetic waves. Temporary computer-readable media can provide programs to the computer via wired communication lines (such as wires and optical fibers) or wireless communication lines.
[0260] Other embodiments
[0261] In the above-described embodiment, the separation SRB2 may be used instead of the separation SRB1.
[0262] The above embodiment provides an example in which SN 2 uses the RRC TRANSFER message to send information related to MCG failure (e.g., MCG failure information) received from UE 3 to MN 1 (e.g., step 902 and step 3203). Alternatively, SN 2 may use the SN MODIFICATION REQUIRED message to send the MCG failure information. In the case where SN 2 recognizes that the RRC message it received from UE 3 contains the MCG failure information, SN 2 may use the SN MODIFICATION REQUIRED message. For example, in the case where SN 2 receives the MCG failure information from UE 3 via SRB 3, SN 2 may include the MCG failure information in the SN MODIFICATION REQUIRED message and send the message to MN 1. Alternatively, in the case where SN 2 receives an MCG failure notification from UE 3 via SCG signaling (e.g., MAC CE), SN 2 may include the content of a separate SRB (e.g., PDCP-C PDU) containing MCG failure information into an SN MODIFICATION REQUIRED message and send the message to MN 1. Upon receiving the SN MODIFICATION REQUIRED message from SN 2, MN 1 may perform (or initiate) the process for recovery from MCG failure in the above-mentioned embodiment.
[0263] In the above embodiment, SN 2 waits (postpones) the execution of modification or release of configuration or resources in SN 2 until a predetermined timing, so as to perform the process of MCG fault recovery. The predetermined timing may be receiving a delivery confirmation (e.g., HARQ ACK, RLC ARQ ACK) from UE 3 for a separated SRB (e.g., PDCP-C PDU) sent by SN 2, or receiving a delivery confirmation from UE 3 for SRB3. Additionally or alternatively, SN 2 may wait (delay) for a predetermined time period to modify or release the configuration or resources in SN 2. The predetermined time period may be set as a timer. The value of the timer may be provided to SN 2 by MN 1 in an XnAP / X2AP message (e.g., SN MODIFICATION REQUEST message or SN RELEASE REQUEST message), or may be specified in advance in the specification. For example, in the case where the predetermined timing (i.e., event) has not been detected by the time the predetermined time period expires, SN 2 may modify or release the configuration or resources in SN 2 after the predetermined time period expires.
[0264] The above-mentioned embodiment basically assumes that the fast MCG recovery via SN 2 (SCG) is successful. However, it may also fail. In one example, it may happen that UE 3 detects an SCG failure after sending MCG failure information via SCG. In this case, UE 3 can perform RRC reconnection processing to re-establish PCell. In another example, it may happen that SN 2 detects an SCG failure after it has received an XnAP / X2AP message (or information) from MN 1 indicating that the SCG needs to be modified (or reconfigured) due to an MCG failure, and it has sent an MN RRC message from MN 1 to UE 3. As already explained, the XnAP / X2AP message (or information) may contain an indication of an MCG failure or an indication of recovery from an MCG failure. Alternatively, the XnAP / X2AP message (or information) may indicate that an SCG modification (or reconfiguration) associated with an MCG modification (or change or reconfiguration) is required. In this case, SN 2 may notify MN 1 of the detection of an SCG failure or the failure to send an MN RRC message via an XnAP / X2AP message. The XnAP / X2AP message may be, for example, an RRC TRANSFER FAILURE message, an SN MODIFICATION FAILURE message, or an MCG MODIFICATION FAILURE message.
[0265] The operations and processes related to MN 1, SN 2, and UE 3 described in the above embodiments can be used to recover from a failure (SCG failure) occurring in the SCG. In a conventional MR-DC, when a UE detects an SCG failure, the UE sends SCG failure information to the MN via the SRB (e.g., SRB1) of the MCG. Based on the SCG failure information, the MN decides whether to release the SN, change the SN to another RAN node (e.g., gNB), or change the PSCell to another cell in the same SN. Instead of these operations, MN 1, SN 2, and UE 3 may, for example, operate as follows.
[0266] SN 2 may establish a direct SRB (i.e., SRB3) between SN 2 and UE 3, and establish a separate SRB (e.g., SN separate SRB) to send the SN RRC message sent by SRB3 to UE 3 via MN 1 (MCG). The SN separate SRB is an SRB between SN 2 and UE 3 for SN RRC messages, and has an RLC bearer in the MCG (i.e., MCG branch) and an RLC bearer in the SCG (i.e., SCG branch). The SN separate SRB supports transmission on the MCG and SCG, and enables duplication of the RRC protocol data unit (PDU) generated by the SN. In other words, the SN separate SRB enables duplication of the PDCP PDU containing RRC information.
[0267] Upon detecting an SCG failure, UE 3 may send SCG failure information (e.g., SCG RLF) to SN 2 via MN1 in the MCG branch (i.e., SN RRC message) of the SN separation SRB. SN 2 may decide whether to release the SN itself, change the SN to another RAN node, or change the PSCell to another cell of the SN itself based on the SCG failure information. Then, SN 2 may initiate (or trigger) an SN modification procedure or an SN release procedure, for example, by sending an SN MODIFICATION REQUIRED message or an SN RELEASE REQUIRED message to MN 1. The message may include an indication of an SCG failure or an indication of recovery from an SCG failure. Upon receiving a message including an indication from SN 2, MN 1 may prioritize processing related to the message. For example, MN 1 may suspend or delay modification or release of configuration or resources in the MN (MCG) used by UE 3, and prioritize processing related to the message.
[0268] In some implementations, when SN 2 configures the SN separation SRB to UE 3, it can notify UE 3 that the primary path of the uplink is SCG (for example, the CellGroup of primaryPath is set to SCG). In addition, SN 2 can explicitly or implicitly send permission to UE 3 in advance to switch the uplink primary path of the SN separation SRB from SCG to MCG. In the case where the SN separation SRB has been set and the permission has been received, UE 3 can send SCG failure information to SN 2 via the MCG branch of the SN separation SRB in response to detecting an SCG failure (for example, SCG RLF). On the other hand, in the case where UE 3 has not yet received the permission, UE 3 can send SCG failure information to MN 1 via MCG. This enables SN 2 to control the behavior of UE 3 when an SCG failure occurs (i.e., sending SCG failure information to MN or SN).
[0269] In some implementations, SN 2 may send an indication (or RRC configuration information) in advance to UE 3 that is setting up (or has already set up) an SN separation SRB, indicating whether UE 3 should send SCG failure information in the MCG or should perform SCG recovery (SCG (link) recovery procedure) when UE 3 detects an SCG failure (e.g., SCG RLF). The SCG recovery process involves UE 3 sending SCG failure information (e.g., SCG Failure Information) to SN 2 via MN 1 in the SN separation SRB. This enables SN 2 to control the behavior of UE 3 when an SCG failure occurs (i.e., the sending of SCG failure information to the MN or SN or RRC reconnection).
[0270] SN 2 may send information that explicitly indicates a process (procedure) to be performed by UE 3. For example, when SN 2 sends RRC information (e.g., SCG-FailureRecovery IE) indicating a method for recovery from an SCG failure (e.g., SCG RLF) to UE 3, SN 2 may explicitly indicate to UE 3 which process to perform (i.e., sending SCG failure information to the MN, or sending SCG failure information via the MCG branch of the SN separation SRB (e.g., fast-SCG-Failure-RecoveryIE)). In the case where UE 3 has been notified to send the SCG failure information in the SN separation SRB, UE 3 sends the SCG failure information to SN 2 via the MCG branch of the SN separation SRB in response to detecting the SCG failure. On the other hand, in the case where UE 3 has been notified to send the SCG failure information to the MN, UE 3 sends the SCG failure information through the MN RRC.
[0271] In the above embodiment, MN 1 may explicitly notify SN 2 of the configuration (or resources) in SN 2 that should be modified or released, and SN 2 may follow accordingly. For example, MN 1 may use IE in XnAP / X2AP message to notify SN 2 of the new security key (e.g., S-KgNB) to be used by SN 2. Alternatively, MN 1 may use RRC container (e.g., CG-ConfigInfo message) contained in XnAP / X2AP message to notify SN 2 of the configuration (e.g., configRestrictInfo) to be followed by SN 2.
[0272] Alternatively, in the above embodiment, MN 1 may indicate to SN 2 which configurations (or resources) in MN 1 are to be modified or released, and SN 2 may determine whether it is necessary to modify or release the configurations (or resources) in SN 2 based on the indication. SN 2 may modify or release the configurations (or resources) in SN 2 as needed. For example, MN 1 may use IE in an XnAP / X2AP message to indicate to SN 2 which configurations (or resources) in MN 1 are to be modified or released. Alternatively, MN 1 may use an RRC container (e.g., a CG-ConfigInfo message) included in an XnAP / X2AP message to notify SN 2 of the configurations (e.g., measConfigMN) in MN 1 that MN 1 has modified or released.
[0273] The above-described embodiments are merely examples of application of the technical ideas obtained by the present inventors. These technical ideas are not limited to the above-described embodiments, and various modifications can be made to these technical ideas.
[0274] The whole or part of the embodiments disclosed above may be described as, but not limited to, the following supplementary descriptions.
[0275] (Supplementary Note 1)
[0276] A master node, comprising:
[0277] at least one memory; and
[0278] at least one processor coupled to the at least one memory and configured to:
[0279] Supporting dual connectivity enabling a radio terminal to use a primary cell group (MCG) provided by the primary node and a secondary cell group (SCG) provided by a secondary node;
[0280] sending an indication to the secondary node regarding a failure of the MCG; and
[0281] A radio resource control message, RRC message, related to recovery from a failure of the MCG is sent to the radio terminal via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0282] (Supplementary Note 2)
[0283] The primary node according to Supplementary Note 1, wherein the at least one processor is configured to send a first message related to modification or release of a configuration or resource in the secondary node related to the dual connectivity to the secondary node, wherein:
[0284] The first message includes the indication, and
[0285] The indication explicitly or implicitly indicates that the modification or release is related to a failure of the MCG or a recovery from the failure.
[0286] (Supplementary Note 3)
[0287] The primary node according to Supplementary Note 2, wherein the first message causes the secondary node to delay modification or release of the configuration or resources until a predetermined condition associated with the transmission of the RRC message via the secondary node is met.
[0288] (Supplementary Note 4)
[0289] The primary node according to Supplementary Note 3, wherein the predetermined condition includes: the secondary node has completed sending the RRC message to the radio terminal.
[0290] (Supplementary Note 5)
[0291] The primary node according to Supplementary Note 3, wherein the predetermined condition includes: the secondary node receiving a response sent by the radio terminal in response to receiving the RRC message.
[0292] (Supplementary Note 6)
[0293] A master node according to any one of Supplementary Notes 2 to 5, wherein:
[0294] The first message requests modification of the configuration or resource, and
[0295] The configuration or resources comprises security keys applied for a direct radio bearer between the secondary node and the radio terminal.
[0296] (Supplementary Note 7)
[0297] A master node according to any one of Supplementary Notes 2 to 5, wherein:
[0298] The first message requests the release of the configuration or resource, and
[0299] The configuration or resources include resources for a signaling connection between the primary node and the secondary node associated with the radio terminal.
[0300] (Supplementary Note 8)
[0301] A master node according to any one of Supplementary Notes 1 to 7,
[0302] The at least one processor is configured to send a second message carrying the RRC message to the secondary node to deliver the RRC message to the radio terminal,
[0303] The second message explicitly or implicitly indicates that the delivery of the RRC message is related to the failure of the MCG or the recovery from the failure.
[0304] (Supplementary Note 9)
[0305] A master node according to any one of Supplementary Notes 1 to 7,
[0306] The at least one processor is configured to send a second message carrying the RRC message to the secondary node to deliver the RRC message to the radio terminal,
[0307] The second message indicates to the secondary node that the RRC message should be delivered.
[0308] (Supplementary Note 10)
[0309] The master node according to any one of supplementary notes 1 to 9, wherein the at least one processor is configured to send, to the radio terminal, permission for switching an uplink primary path of the split signaling radio bearer from the MCG to the SCG.
[0310] (Supplementary Note 11)
[0311] The master node according to Supplementary Note 10, wherein
[0312] in response to the radio terminal detecting a failure of the MCG during which the radio terminal has received the grant, the grant causing the radio terminal to send information related to the failure of the MCG to the master node over the SCG portion of the split signalling radio bearer, and
[0313] In response to the radio terminal detecting a failure of the MCG during a period in which the radio terminal has not received the grant, the grant causes the radio terminal to perform an RRC connection re-establishment procedure.
[0314] (Supplementary Note 12)
[0315] The master node according to any one of Supplementary Notes 1 to 9, wherein the at least one processor is configured to indicate to the radio terminal whether the radio terminal should perform an RRC connection re-establishment procedure or an MCG recovery procedure when the radio terminal detects a failure of the MCG,
[0316] The MCG recovery process includes sending information related to the failure of the MCG from the radio terminal to the master node via the SCG part of the separate signaling radio bearer.
[0317] (Supplementary Note 13)
[0318] A secondary node, comprising:
[0319] at least one memory; and
[0320] at least one processor coupled to the at least one memory and configured to:
[0321] Supporting dual connectivity enabling the radio terminal to use a primary cell group, i.e., MCG, provided by the primary node and a secondary cell group, i.e., SCG, provided by the secondary node;
[0322] receiving an indication from the master node regarding a failure of the MCG; and
[0323] A radio resource control message, RRC message, related to recovery from a failure of the MCG is sent to the radio terminal via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0324] (Supplementary Note 14)
[0325] The secondary node according to Supplementary Note 13, wherein the at least one processor is configured to receive from the primary node a first message related to modification or release of a configuration or resource in the secondary node related to the dual connectivity, wherein:
[0326] The first message includes the indication, and
[0327] The indication explicitly or implicitly indicates that the modification or release is related to a failure of the MCG or a recovery from the failure.
[0328] (Supplementary Note 15)
[0329] The secondary node according to Supplementary Note 14, wherein the at least one processor is configured to:
[0330] determining, based on the indication, whether the modification or release is related to a failure of the MCG or the failure; and
[0331] In response to determining that the modification or release is related to a failure of the MCG or the failure, delaying the modification or release of the configuration or resources until a predetermined condition associated with the sending of the RRC message via the secondary node is met.
[0332] (Supplementary Note 16)
[0333] The secondary node according to supplementary note 15, wherein the predetermined condition includes: the secondary node has completed sending the RRC message to the radio terminal.
[0334] (Supplementary Note 17)
[0335] The secondary node according to Supplementary Note 15, wherein the predetermined condition comprises: the secondary node receiving a response sent by the radio terminal in response to receiving the RRC message.
[0336] (Supplementary Note 18)
[0337] The auxiliary node according to any one of Supplementary Notes 14 to 17, wherein:
[0338] The first message requests modification of the configuration or resource, and
[0339] The configuration or resources comprises security keys applied for a direct radio bearer between the secondary node and the radio terminal.
[0340] (Supplementary Note 19)
[0341] The auxiliary node according to any one of Supplementary Notes 14 to 17, wherein:
[0342] The first message requests the release of the configuration or resource, and
[0343] The configuration or resources include resources for a signaling connection between the primary node and the secondary node associated with the radio terminal.
[0344] (Supplementary Note 20)
[0345] The secondary node according to any one of Supplementary Notes 13 to 19, wherein the at least one processor is configured to receive a second message carrying the RRC message from the primary node,
[0346] The second message explicitly or implicitly indicates that the delivery of the RRC message is related to the failure of the MCG or the recovery from the failure.
[0347] (Supplementary Note 21)
[0348] The secondary node according to any one of Supplementary Notes 13 to 19, wherein the at least one processor is configured to receive a second message carrying the RRC message from the primary node,
[0349] The second message indicates to the secondary node that the RRC message should be delivered.
[0350] (Supplementary Note 22)
[0351] A method performed by a master node, the method comprising:
[0352] Controlling the master node to enable dual connectivity for a radio terminal using a primary cell group (MCG) provided by the master node and a secondary cell group (SCG) provided by a secondary node;
[0353] sending an indication to the secondary node regarding a failure of the MCG; and
[0354] A radio resource control message, RRC message, related to recovery from a failure of the MCG is sent to the radio terminal via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0355] (Supplementary Note 23)
[0356] A method performed by a secondary node, the method comprising:
[0357] Controlling the secondary node to enable dual connectivity for the radio terminal using a primary cell group (MCG) provided by the primary node and a secondary cell group (SCG) provided by the secondary node;
[0358] receiving an indication from the master node regarding a failure of the MCG; and
[0359] A radio resource control message, RRC message, related to recovery from a failure of the MCG is sent to the radio terminal via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0360] (Supplementary Note 24)
[0361] A program for causing a computer to perform a method used by a master node, the method comprising:
[0362] Controlling the master node to enable dual connectivity for a radio terminal using a primary cell group (MCG) provided by the master node and a secondary cell group (SCG) provided by a secondary node;
[0363] controlling the primary node to send an indication related to a failure of the MCG to the secondary node; and
[0364] The master node is controlled to send a radio resource control message (RRC message) related to recovery from a failure of the MCG to the radio terminal via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0365] (Supplementary Note 25)
[0366] A program for causing a computer to perform a method used by a secondary node, the method comprising:
[0367] Controlling the secondary node to enable dual connectivity for the radio terminal using a primary cell group (MCG) provided by the primary node and a secondary cell group (SCG) provided by the secondary node;
[0368] controlling the secondary node to receive an indication from the primary node regarding a failure of the MCG; and
[0369] The secondary node is controlled to send a radio resource control message (RRC message) related to recovery from a failure of the MCG to the radio terminal via an SCG part of a separate signaling radio bearer configured between the primary node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0370] (Supplementary Note B1)
[0371] A radio terminal, comprising:
[0372] at least one memory; and
[0373] at least one processor coupled to the at least one memory and configured to:
[0374] Support dual connectivity using the primary cell group (MCG) provided by the master node and the secondary cell group (SCG) provided by the secondary node;
[0375] sending information related to a failure of the MCG to the master node via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG; and
[0376] A notification of the failure of the MCG is sent to the secondary node via direct control signaling between the secondary node and the radio terminal.
[0377] (Supplementary Note B2)
[0378] The radio terminal according to supplementary note B1, wherein the direct control signaling is a medium access control control element (MAC control element).
[0379] (Supplementary Note B3)
[0380] A method performed by a radio terminal, the method comprising:
[0381] Perform dual connectivity using a primary cell group (MCG) provided by the primary node and a secondary cell group (SCG) provided by the secondary node;
[0382] sending information related to a failure of the MCG to the master node via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG; and
[0383] A notification of the failure of the MCG is sent to the secondary node via direct control signaling between the secondary node and the radio terminal.
[0384] (Supplementary Note B4)
[0385] The method according to Supplementary Note B3, wherein the direct control signaling is a medium access control control element, i.e., a MAC control element.
[0386] (Supplementary Note B5)
[0387] A program for causing a computer to perform a method used by a radio terminal, the method comprising:
[0388] Controlling the radio terminal to perform dual connectivity using a primary cell group (MCG) provided by a primary node and a secondary cell group (SCG) provided by a secondary node;
[0389] controlling the radio terminal to send information related to a failure of the MCG to the master node via an SCG part of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG; and
[0390] The radio terminal is controlled to send a notification of a failure of the MCG to the secondary node via direct control signaling between the secondary node and the radio terminal.
[0391] (Supplementary Note C1)
[0392] A radio terminal, comprising:
[0393] at least one memory; and
[0394] at least one processor coupled to the at least one memory and configured to:
[0395] Support dual connectivity using the primary cell group (MCG) provided by the master node and the secondary cell group (SCG) provided by the secondary node;
[0396] receiving, from the master node, permission for switching an uplink primary path of a split signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG; and
[0397] In response to detecting a failure of the MCG during the period in which the radio terminal has received the grant, information related to the failure of the MCG is sent to the master node over the SCG portion of the separate signaling radio bearer.
[0398] (Supplementary Note C2)
[0399] The radio terminal according to Supplementary Note C1, wherein the at least one processor is configured to perform a radio resource control connection re-establishment procedure (RRC connection re-establishment procedure) in response to detecting a failure of the MCG during a period when the radio terminal has not received the grant.
[0400] (Supplementary Note C3)
[0401] A master node, comprising:
[0402] at least one memory; and
[0403] at least one processor coupled to the at least one memory and configured to:
[0404] Supporting dual connectivity that enables a radio terminal to use a primary cell group, ie, MCG, provided by a primary node and a secondary cell group, ie, SCG, provided by a secondary node; and
[0405] A grant is sent to the radio terminal for switching an uplink primary path of a separate signaling radio bearer configured between the master node and the radio terminal and supporting transmission via both the MCG and the SCG.
[0406] (Supplementary Note D1)
[0407] A master node, comprising:
[0408] at least one memory; and
[0409] at least one processor coupled to the at least one memory and configured to:
[0410] Supporting dual connectivity that enables a radio terminal to use a primary cell group, ie, MCG, provided by a primary node and a secondary cell group, ie, SCG, provided by a secondary node; and
[0411] In a case where the radio terminal detects a failure of the MCG during the time when the radio terminal has been configured to be able to send a radio resource control message (RRC message) to the primary node via the secondary node, indicating to the radio terminal whether the radio terminal should perform an RRC connection re-establishment procedure or an MCG recovery procedure,
[0412] The MCG recovery process includes sending information related to the failure of the MCG from the radio terminal to the primary node via the secondary node.
[0413] (Supplementary Note D2)
[0414] A radio terminal, comprising:
[0415] at least one memory; and
[0416] at least one processor coupled to the at least one memory and configured to:
[0417] Supporting dual connectivity using a primary cell group (MCG) provided by a primary node and a secondary cell group (SCG) provided by a secondary node; and
[0418] receiving, in a case where the radio terminal detects a failure of the MCG during the time when the radio terminal has been configured to be able to send a radio resource control message (RRC message) to the primary node via the secondary node, an indication from the primary node indicating whether the radio terminal should perform an RRC connection re-establishment procedure or an MCG recovery procedure,
[0419] The MCG recovery process includes sending information related to the failure of the MCG from the radio terminal to the primary node via the secondary node.
[0420] (Supplementary Note E1)
[0421] A radio terminal, comprising:
[0422] at least one memory; and
[0423] at least one processor coupled to the at least one memory and configured to:
[0424] Supporting dual connectivity using a primary cell group (MCG) provided by a primary node and a secondary cell group (SCG) provided by a secondary node; and
[0425] configuring a separate signaling radio bearer supporting transmission between the master node and the radio terminal via both the MCG and the SCG; and
[0426] In response to the switching of the uplink primary path of the split signaling radio bearer from the MCG to the SCG, a report of an uplink transmission buffer status (buffer status report (BSR)) is triggered in the SCG.
[0427] (Supplementary Note E2)
[0428] The radio terminal according to Supplementary Note E1, wherein the at least one processor is configured to provide an MCG radio resource control entity, i.e., an MCG RRC entity, an MCG packet data convergence protocol entity, i.e., an MCG PDCP entity, an MCG medium access control entity, i.e., an MCG MAC entity, an SCG PDCP entity, and an SCG radio link control entity, i.e., an SCG RLC entity, wherein
[0429] The MCG RRC entity is configured to, upon detecting a failure of the MCG, send an indication to the MCG PDCP entity for switching the uplink primary path from the MCG to the SCG,
[0430] The MCG MAC entity is configured to obtain a buffered amount of data to be transmitted including information related to a failure of the MCG from the SCG PDCP entity and the SCG RLC entity, and
[0431] The MCG MAC entity is configured to send the BSR to the secondary node via the SCG.
[0432] (Supplementary Note E3)
[0433] A method performed by a radio terminal, the method comprising:
[0434] controlling the radio terminal to perform dual connectivity using a primary cell group (MCG) provided by a primary node and a secondary cell group (SCG) provided by a secondary node; and
[0435] configuring a separate signaling radio bearer supporting transmission between the master node and the radio terminal via both the MCG and the SCG; and
[0436] In response to the switching of the uplink primary path of the split signaling radio bearer from the MCG to the SCG, a report of an uplink transmission buffer status (buffer status report (BSR)) is triggered in the SCG.
[0437] (Supplementary Note E4)
[0438] A program for causing a computer to perform a method used by a radio terminal, the method comprising:
[0439] controlling the radio terminal to perform dual connectivity using a primary cell group (MCG) provided by a primary node and a secondary cell group (SCG) provided by a secondary node; and
[0440] controlling the radio terminal to configure a separate signaling radio bearer supporting transmission between the master node and the radio terminal via both the MCG and the SCG; and
[0441] The radio terminal is controlled to trigger a report of an uplink transmission buffer status (buffer status report (BSR)) in the SCG in response to a switch of an uplink primary path of the split signaling radio bearer from the MCG to the SCG.
[0442] This application is based upon and claims the benefit of priority from Japanese patent application No. 2019-139250, filed on Jul. 29, 2019, the disclosure of which is incorporated herein in its entirety by reference.
[0443] Reference numerals list
[0444] 1 Master Node (MN)
[0445] 2 Secondary Node (SN)
[0446] 3 User Equipment (UE)
[0447] 4 Target MN
[0448] 5 Core Network
[0449] 6 Target gNB
[0450] 4004 Processor
[0451] 4005 Memory
[0452] 4006 Module
[0453] 4103 Baseband Processor
[0454] 4104 Application Processor
[0455] 4106 Memory
[0456] 4107 Module
Claims
1. A method for a primary node having dual connection with a secondary node, the method comprising: communicating with the user terminal using a master cell group (MCG), the MCG being a group of serving cells associated with the master node; receiving a first radio resource control transmission message (i.e., a first RRC transmission message) from the secondary node, the first RRC transmission message comprising information indicating a failure related to the MCG; as well as After receiving the first RRC transmit message, a second RRC transmit message is sent to the secondary node, the second RRC transmit message comprising an RRC reconfiguration message, and the second RRC transmit message further comprises, in addition to the RRC reconfiguration message, information indicating to the secondary node that the RRC reconfiguration message is related to recovery of the MCG.
2. The method according to claim 1, wherein: The RRC reconfiguration message is sent from the secondary node to the user terminal using a Signalling Radio Bearer 3, SRB3, established between the secondary node and the user terminal.
3. The method according to claim 1, wherein: The RRC reconfiguration message and the second RRC transmission message including the information enable the secondary node to recognize that the secondary node is required to send the RRC reconfiguration message to the user terminal.
4. A method for a secondary node having dual connection with a primary node, the method comprising: communicating with the user terminal using an SCG, the SCG being a set of serving cells associated with the secondary node; sending a first RRC transmit message to the master node, the first RRC transmit message including information indicating a failure related to an MCG, the MCG being a group of serving cells associated with the master node; as well as After sending the first RRC transmit message, a second RRC transmit message is received from the primary node, the second RRC transmit message comprising an RRC reconfiguration message, and the second RRC transmit message further comprises, in addition to the RRC reconfiguration message, information indicating to the secondary node that the RRC reconfiguration message is related to recovery of the MCG.
5. The method according to claim 4, wherein: The RRC reconfiguration message is sent from the secondary node to the user terminal using a Signalling Radio Bearer 3, SRB3, established between the secondary node and the user terminal.
6. The method according to claim 4, further comprising: In response to receiving both the RRC reconfiguration message and the information in the second RRC transfer message, it is recognized that the secondary node is required to send the RRC reconfiguration message to the user terminal.
7. A primary node having dual connections with a secondary node, the primary node comprising: at least one memory; as well as at least one processor coupled to the memory and configured to: communicating with a user terminal using an MCG, the MCG being a set of serving cells associated with the master node; receiving a first RRC transmit message from the secondary node, the first RRC transmit message comprising information indicating a failure related to the MCG; as well as After receiving the first RRC transmit message, a second RRC transmit message is sent to the secondary node, the second RRC transmit message comprising an RRC reconfiguration message, and the second RRC transmit message further comprises, in addition to the RRC reconfiguration message, information indicating to the secondary node that the RRC reconfiguration message is related to recovery of the MCG.
8. The master node according to claim 7, wherein: The RRC reconfiguration message is sent from the primary node to the user terminal using a Signalling Radio Bearer 3, SRB3, established between the secondary node and the user terminal.
9. The master node according to claim 7, wherein: The RRC reconfiguration message and the second RRC transmission message including the information enable the secondary node to recognize that the secondary node is required to send the RRC reconfiguration message to the user terminal.
10. A secondary node having dual connections with a primary node, the secondary node comprising: at least one memory; as well as at least one processor coupled to the memory and configured to: communicating with the user terminal using an SCG, the SCG being a set of serving cells associated with the secondary node; sending a first RRC transmit message to the master node, the first RRC transmit message including information indicating a failure related to an MCG, the MCG being a group of serving cells associated with the master node; as well as After sending the first RRC transmit message, a second RRC transmit message is received from the primary node, the second RRC transmit message comprising an RRC reconfiguration message, and the second RRC transmit message further comprises, in addition to the RRC reconfiguration message, information indicating to the secondary node that the RRC reconfiguration message is related to recovery of the MCG.
11. The secondary node according to claim 10, wherein: The RRC reconfiguration message is sent from the primary node to the user terminal using a Signalling Radio Bearer 3, SRB3, established between the secondary node and the user terminal.
12. The secondary node according to claim 10, wherein: The at least one processor is configured to, in response to receiving both the RRC reconfiguration message and the information in the second RRC transfer message, recognize that the secondary node is required to send the RRC reconfiguration message to the user terminal.
