Radio access network node and method thereof
By preventing concurrent inter-SN CPC configurations and managing rejection causes, the complexity and service disruptions in inter-SN CPC procedures are mitigated, ensuring stable and efficient dual connectivity in wireless communication systems.
Patent Information
- Application Number
- JP2023535146
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-07-14
- Filing Date
- 2022-04-27
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2042-04-27
AI Technical Summary
The processing complexity and potential service disruption in inter-SN Conditional PSCell Change (CPC) procedures in wireless communication systems, particularly when both MN-initiated and SN-initiated inter-SN CPCs are configured simultaneously, and the inability to distinguish rejection causes by the target SN, leading to potential service interruptions and limited inter-SN CPC opportunities.
Implementing mechanisms in RAN nodes to prevent concurrent configuration of MN-initiated and SN-initiated inter-SN CPCs, and to differentiate and manage rejection causes during inter-SN CPC procedures, ensuring proper handling and coordination among MN, S-SN, and T-SN nodes.
This approach reduces processing complexity and avoids service disruptions by managing inter-SN CPCs effectively, allowing for better resource allocation and preventing unnecessary rejections, thereby enhancing the stability and efficiency of dual connectivity in wireless communication systems.
Smart Images

Figure 0007593499000001 
Figure 0007593499000002 
Figure 0007593499000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to wireless communication systems, and more particularly to mobility of wireless terminals in multi-connectivity (eg, dual connectivity). [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) is currently studying Release 17. 3GPP is discussing the application of conditional mobility to cell changes (i.e., inter-SN PSCell change) between secondary nodes (SNs) of a primary cell (PSCell) of a secondary cell group (SCG) of a dual connectivity (DC) (see, for example, non-patent documents 1-7). This is called inter-SN conditional PSCell change (CPC). The PSCell is a special cell (SpCell) of the SCG of the DC. When performing a handover procedure (or a reconfiguration with sync procedure), the UE randomly accesses the PSCell. An SCG is a group of serving cells associated with an SN, including an SpCell (ie, a PSCell) and optionally one or more Secondary Cells (SCells).
[0003] CPC is a PSCell change procedure that is executed only when one or more execution conditions are met or satisfied. After receiving a PSCell change instruction from a Master Node (MN), a wireless terminal (i.e., User Equipment (UE)) maintains a connection with a Source SN (S-SN) and an SCG, and starts evaluation of execution condition(s) configured by the instruction. Then, the UE starts accessing a Target SN (T-SN) in response to the execution condition(s) being satisfied. That is, CPC differs from a normal PSCell change in that the UE starts accessing a target PSCell (or a new PSCell) in response to the execution condition(s) being satisfied, not in response to a PSCell change instruction.
[0004] An inter-SN CPC can be initiated by the MN or a source SN. An inter-SN CPC initiated by an MN is called an MN initiated inter-SN CPC. On the other hand, an inter-SN CPC initiated by an S-SN is called an SN initiated inter-SN CPC. In an MN initiated inter-SN CPC, the MN generates a CPC execution condition, and the T-SN generates an SCG configuration. In contrast, in an SN initiated inter-SN CPC, the S-SN generates a CPC execution condition and sends it to the MN. In both the MN-initiated CPC and SN-initiated CPC, the T-SN generates an SCG configuration and sends it to the MN. Then, the MN transmits a CPC configuration (e.g., a Conditional Reconfiguration Information Element (IE)) including the CPC execution condition and the SCG configuration to the UE via a Radio Resource Control (RRC) (Connection) Reconfiguration message. [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] Vice Chairman (Nokia), "Report on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing", R2-2106471, 3GPP TSG-RAN WG2 Meeting #114-e, May 19-27, 2021 [Non-Patent Document 2] CATT, "TS 37.340 CR for CPA and inter-SN CPC", R2-2105062, 3GPP TSG-RAN WG2 Meeting #114-e, May 19-27, 2021 [Non-Patent Document 3] Huawei, "(TP to CPAC TS 37.340 BL CR) Consideration on conditional PSCell change / addition", R3-212833, 3GPP TSG-RAN WG3 Meeting #112-e, May 17-28, 2021 [Non-Patent Document 4] Samsung, "(TP to TS 38.423, LTE_NR_DC_enh2-Core) Adding CPAC Procedure", R3-212968, 3GPP TSG-RAN WG3 Meeting #112-e, May 17-27, 2021 [Non-Patent Document 5] Samsung, "(TP to TS 36.423, LTE_NR_DC_enh2-Core) Adding CPAC Procedure", R3-212969, 3GPP TSG-RAN WG3 Meeting #112-e, May 17-27, 2021 [Non-Patent Document 6] Huawei, "Support of Conditional PSCell Change and Addition", R3-212995, 3GPP TSG-RAN WG3 Meeting #112-e, May 17-27, 2021 [Non-Patent Document 7] Nokia, Nokia Shanghai Bell, "CPAC BL CR to TS 36.423", R3-212994, 3GPP TSG-RAN WG3 Meeting #112-e, May 17-28, 2021 Summary of the Invention [Problem to be solved by the invention]
[0006] The inventors have studied inter-SN CPC and found various problems. One of these problems is related to the complexity of inter-SN CPC processing. Specifically, if both MN-initiated inter-SN CPC and SN-initiated inter-SN CPC are configured at the same time, the processing of the network (i.e., Radio Access Network (RAN)) or UE, or both, may become complicated.
[0007] Another problem that the inventors have found relates to the details of the MN-initiated inter-SN CPC procedure. In the MN-initiated CPC, the S-SN receives an SN Release Request message from the MN. However, if the S-SN cannot distinguish that this SN Release Request message is for the MN-initiated inter-SN CPC, the S-SN may stop providing user data to the UE in response to receiving the SN Release Request message.
[0008] Another problem that the inventors have found relates to the behavior of the T-SN when rejecting a request for an inter-SN CPC. The T-SN may reject a request for an inter-SN CPC because it cannot accept any inter-SN CPC. This may be because the T-SN does not support inter-SN CPC in the first place or because the load of the T-SN is temporarily high. Alternatively, the T-SN may reject a request for an inter-SN CPC because it cannot accept only the inter-SN CPC for one or more candidate cells (candidate PSCells) specified by the request for an inter-SN CPC. It may be preferable for the MN in the case of an MN-initiated inter-SN CPC, or the S-SN in the case of an SN-initiated inter-SN CPC, to be able to distinguish between these reasons for rejection. If the MN or S-SN does not send any new inter-SN CPC requests to the T-SN, even though the T-SN cannot accept only inter-SN CPC for one or more designated candidate cells (candidate PSCells), the opportunities for inter-SN CPC may be unduly limited.
[0009] One of the objectives that the embodiments disclosed in this specification aim to achieve is to provide an apparatus, a method, and a program that contribute to solving at least one of the problems including the problems described above. It should be noted that this objective is only one of the objectives that the embodiments disclosed in this specification aim to achieve. Other objectives or objectives and novel features will be apparent from the description of this specification or the accompanying drawings. [Means for solving the problem]
[0010] A first aspect is directed to a RAN node configured to operate as a MN associated with a Master Cell Group (MCG) in dual connectivity for a UE, the RAN node including at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to not establish, prepare or allow an SN-initiated inter-SN CPC to at least the T-SN for the UE while an MN-initiated inter-SN CPC from an S-SN to a T-SN for a PSCell of an SCG for the UE is ongoing.
[0011] A second aspect is directed to a method performed by a RAN node configured to act as an MN associated with an MCG in dual connectivity for a UE, the method including not configuring, preparing or allowing an SN-initiated inter-SN CPC to at least a T-SN for the UE while an MN-initiated inter-SN CPC from an S-SN to a T-SN for the UE is ongoing for a PSCell of an SCG for the UE.
[0012] A third aspect is directed to a RAN node configured to operate as an S-SN associated with an SCG in dual connectivity for a UE, the RAN node including at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to not initiate an SN-initiated inter-SN CPC for the UE to at least the T-SN while an MN-initiated inter-SN CPC from the S-SN to a T-SN for the UE is ongoing.
[0013] A fourth aspect is directed to a method performed by a RAN node configured to act as an S-SN associated with an SCG in dual connectivity for a UE, the method including not initiating an SN-initiated inter-SN CPC for the UE to at least the T-SN while an MN-initiated inter-SN CPC from the S-SN to a T-SN is ongoing for a PSCell of the SCG of the UE.
[0014] A fifth aspect is directed to a RAN node configured to act as a MN associated with an MCG in dual connectivity for a UE, the RAN node including at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to send an SN Release Request message to the S-SN during a procedure for preparing an MN-initiated inter-SN CPC from an S-SN to a T-SN for a PSCell of an SCG of the UE, the SN Release Request message including information indicating that the message is for an inter-SN CPC.
[0015] A sixth aspect is directed to a method performed by a RAN node configured to act as an MN associated with an MCG in dual connectivity for a UE, the method including, during a procedure for preparing an MN-initiated inter-SN CPC from an S-SN to a T-SN for a PSCell of an SCG of the UE, sending an SN Release Request message to the S-SN, the SN Release Request message including information indicating that the message is for an inter-SN CPC.
[0016] A seventh aspect is directed to a RAN node configured to act as an S-SN associated with an SCG in dual connectivity for a UE, the RAN node including at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive from an MN a SN Release Request message containing information indicating that the message is for an inter-SN CPC during a procedure for preparing an MN-initiated inter-SN CPC from an S-SN to a T-SN for a PSCell of an SCG of the UE.
[0017] An eighth aspect is directed to a method performed by a RAN node configured to act as an S-SN associated with an SCG in dual connectivity for a UE, the method including receiving, during a procedure for preparing an MN-initiated inter-SN CPC from an S-SN to a T-SN for a PSCell of an SCG of the UE, an SN Release Request message from an MN that includes information indicating that the message is for an inter-SN CPC.
[0018] A ninth aspect is directed to a RAN node configured to act as a T-SN associated with an SCG in dual connectivity for a UE, the RAN node including at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to send a rejection message to a MN if a request for an inter-SN CPC from an S-SN to the T-SN is rejected, the rejection message indicating whether no inter-SN CPCs are accepted by the target SN or only the inter-SN CPCs for one or more candidate cells specified by the request are accepted.
[0019] A tenth aspect is directed to a method performed by a RAN node configured to act as a T-SN associated with an SCG in dual connectivity for a UE, the method including sending a rejection message to a MN when rejecting a request for inter-SN CPCs from an S-SN to the T-SN, the rejection message indicating whether no inter-SN CPCs are accepted by the target SN or only the inter-SN CPCs for one or more candidate cells specified by the request are accepted.
[0020] An eleventh aspect is directed to a program comprising a set of instructions (software code) for causing a computer to carry out a method according to the second, fourth, sixth, eighth or tenth aspect when the program is loaded into the computer. Effect of the Invention
[0021] According to the above-mentioned aspects, it is possible to provide an apparatus, a method, and a program that contribute to solving at least one of a number of problems related to inter-SN CPC, including the problems described above. [Brief description of the drawings]
[0022] [Figure 1] 1 is a diagram illustrating an example of the configuration of a wireless communication network according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating a configuration example of a RAN node according to an embodiment. [Diagram 3] 11 is a flowchart showing an example of a process performed by an MN according to the embodiment. [Figure 4] 11 is a flowchart showing an example of a process performed by an MN according to the embodiment. [Diagram 5] 13 is a flowchart showing an example of processing performed by an S-SN according to the embodiment. [Figure 6] FIG. 1 is a sequence diagram showing an example of processing performed by an MN and an S-SN according to an embodiment. [Figure 7] 11 is a flowchart showing an example of a process performed by an MN according to the embodiment. [Figure 8] 13 is a flowchart showing an example of processing performed by an S-SN according to the embodiment. [Figure 9] FIG. 1 is a sequence diagram showing an example of processing performed by an MN and an S-SN according to an embodiment. [Figure 10] FIG. 1 is a sequence diagram showing an example of processing performed by an MN and an S-SN according to an embodiment. [Figure 11] FIG. 1 is a sequence diagram showing an example of processing performed by an MN and an S-SN according to an embodiment. [Figure 12] 13 is a flowchart illustrating an example of processing performed by a T-SN according to an embodiment. [Figure 13] FIG. 1 is a sequence diagram showing an example of processing performed by an MN, an S-SN, and a T-SN according to an embodiment. [Figure 14] FIG. 2 is a block diagram showing a configuration example of a RAN node according to the embodiment. [Figure 15] FIG. 2 is a block diagram showing an example of the configuration of a UE according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0023] In the following, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and duplicated descriptions will be omitted as necessary for clarity of explanation.
[0024] The multiple embodiments described below can be implemented independently or in appropriate combination. These multiple embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different objects or problems and provide different effects.
[0025] The following embodiments are described with a focus on the 3GPP Long Term Evolution (LTE) system and the fifth generation mobile communication system (5G system). However, these embodiments may be applied to other wireless communication systems that support technologies similar to 3GPP multi-connectivity (e.g. Dual Connectivity). In addition, the term LTE used in this specification includes improvements and developments of LTE and LTE-Advanced to enable interworking with the 5G system, unless otherwise specified.
[0026] As used herein, depending on the context, "if" may be interpreted to mean "when," "at or around the time," "after," "upon," "in response to determining," "in accordance with a determination," or "in response to detecting." These expressions may be interpreted to have the same meaning, depending on the context.
[0027] <First embodiment> Fig. 1 illustrates an example of a configuration of a wireless communication network according to a number of embodiments including the present embodiment. In the example of Fig. 1, the wireless communication network includes a RAN node 1, a RAN node 2, a RAN node 4, and a UE 3. Each element (network function) illustrated in Fig. 1 can be implemented, for example, as a network element on dedicated hardware, as a software instance running on the dedicated hardware, or as a virtualized function instantiated on an application platform.
[0028] The RAN node 1 may be a Central Unit (e.g., eNB-CU or gNB-CU) in a cloud RAN (C-RAN) deployment, or may be a combination of a CU and one or more Distributed Units (e.g., eNB-DUs or gNB-DUs). C-RAN is also referred to as a CU / DU split. Furthermore, a 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). Thus, the RAN node 1 may be a CU-CP or a combination of a CU-CP and a CU-UP. Similarly, each of the RAN nodes 2 and 4 may be a CU or a combination of a CU and one or more DUs. Each of the RAN nodes 2 and 4 may be a CU-CP or a combination of a CU-CP and a CU-UP.
[0029] Each of the RAN nodes 1, 2, and 4 may 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 en-gNB is a node that provides NR user plane and control plane protocol terminations towards the UE and acts as a secondary node (SN) in E-UTRA-NR Dual Connectivity (EN-DC). The ng-eNB is a node that provides E-UTRA user plane and control plane protocol terminations towards the UE and is connected to the 5GC via the NG interface. The Radio Access Technology (RAT) of the RAN node 1 may be different from that of the RAN nodes 2 and 4.
[0030] RAN node 1 and RAN node 2 communicate with each other via an inter-node interface (i.e., X2 interface or Xn interface) 103. RAN node 1 and RAN node 2 act as a master node (MN) and a secondary node (SN) of dual connectivity, respectively. Furthermore, RAN node 1 and RAN node 4 communicate with each other via an inter-node interface (i.e., X2 interface or Xn interface) 105. RAN node 1 and RAN node 4 can act as a MN and a SN of a DC, respectively. RAN nodes 1, 2, and 4 support inter-SN CPC from an SCG provided by RAN node 2 to an SCG provided by RAN node 4. In the following, RAN node 1 may be referred to as MN 1, RAN node 2 may be referred to as source SN (S-SN) 2, and RAN node 4 may be referred to as target SN (T-SN) 4. UE 3 communicates with MN 1 and S-SN 2 via air interfaces 101 and 102 to perform dual connectivity of MCG provided by MN 1 and SCG provided by S-SN 2. Also, by performing inter-SN CPC, the UE 3 communicates with the MN 1 and the T-SN 4 via the air interfaces 101 and 104, and performs dual connectivity of the MCG provided by the MN 1 and the SCG provided by the T-SN 4.
[0031] This dual connectivity may be Multi-Radio Dual Connectivity (MR-DC). MR-DC includes E-UTRA-NR Dual Connectivity (EN-DC), NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), NR-E-UTRA Dual Connectivity (NE-DC), and NR-NR Dual Connectivity (NR-DC). Accordingly, the MN1 may be any of a master eNB (in EN-DC), a master ng-eNB (in NGEN-DC), and a master gNB (in NR-DC and NE-DC). Similarly, each of the S-SN2 and the T-SN4 may be any of an en-gNB (in EN-DC), a secondary ng-eNB (in NE-DC), and a secondary gNB (in NR-DC and NGEN-DC). In the EN-DC, the UE3 is connected to an eNB operating as the MN1 and is connected to an en-gNB operating as the S-SN2 or the T-SN4. In NGEN-DC, UE3 is connected to an ng-eNB operating as MN1 and to a gNB operating as S-SN2 or T-SN4. In NE-DC, UE3 is connected to a gNB operating as MN1 and to an ng-eNB operating as S-SN2 or T-SN4. In NR-DC, UE3 is connected to one gNB (or gNB-DU) operating as MN1 and to another gNB (or gNB-DU) operating as S-SN2 or T-SN4.
[0032] The MCG is a group of serving cells associated with (or provided to) the MN1, and includes an SpCell (i.e., a Primary Cell (PCell)) and, optionally, one or more Secondary Cells (SCells). On the other hand, the SCG is a group of serving cells associated with (or provided to) the S-SN2 or T-SN4, and includes a Primary SCG Cell (PSCell) and, optionally, one or more Secondary Cells (SCells). The PSCell is a Special Cell (SpCell) of the SCG, and supports Physical Uplink Control Channel (PUCCH) transmission and contention-based Random Access. Note that in LTE (e.g., LTE-DC and NE-DC), PSCell may be an abbreviation for Primary SCell.
[0033] As used herein, the term "primary SCG cell" and its abbreviation "PSCell" refer to a cell included in a cell group provided by a dual connectivity SN, having an uplink component carrier, and having uplink control channel (e.g. PUCCH) resources configured. Specifically, the term "primary SCG cell" and its abbreviation "PSCell" may refer to a Primary SCG Cell of a cell group provided by an SN supporting 5G NR (e.g. en-gNB in EN-DC, gNB in NGEN-DC, or gNB in NR-DC), or may refer to a Primary SCell of a cell group provided by an SN supporting E-UTRA (e.g. eNB in LTE DC, or ng-eNB in NE-DC).
[0034] One or more of the MN1, S-SN2, and T-SN4 may have the configuration shown in FIG. 2. Each element (network function) shown in FIG. 2 may be implemented, for example, as a network element on dedicated hardware, as a software instance running on the dedicated hardware, or as a virtualized function instantiated on an application platform. One or more of the MN1, S-SN2, and T-SN4 may include, but are not limited to, a CU21 and one or more DUs 22 as shown in FIG. 2. The CU21 and each DU 22 are connected by an interface 201. The UE3 is connected to at least one DU 22 via at least one air interface 202.
[0035] The CU21 may be a logical node that hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols (or the RRC and PDCP protocols) of the gNB. The DU22 may be a logical node that hosts the Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers of the gNB. If the CU21 is a gNB-CU and the DUs22 are gNB-DUs, the interface 201 may be an F1 interface. The CU21 may include a CU-CP and a CU-UP.
[0036] In the following, the operations of MN1, S-SN2, and T-SN4 regarding inter-SN CPC are described. FIG. 3 shows an example of the operation of MN1. In step 301, MN1 configures, prepares, or triggers MN-initiated inter-SN CPC from S-SN2 to T-SN4 regarding the PSCell of UE3. Specifically, MN1 transmits CPC configuration to UE3, and UE3 initiates evaluation of CPC execution condition. More specifically, MN1 transmits MN RRC (connection) reconfiguration message including CPC configuration to UE3 to instruct UE3 to perform conditional reconfiguration for CPC. The CPC configuration includes SCG configuration of each of one or more candidate PSCells and CPC execution condition of each candidate PSCell. The SCG configuration may be the configuration of the candidate PSCell (or the target PSCell). The SCG configuration (or PSCell configuration) may be an SN RRC Reconfiguration message that includes the SCG configuration. The CPC configuration may be a ConditionalReconfiguration IE in a MN RRC (Connection) Reconfiguration message. The ConditionalReconfiguration IE may include a condReconfigToAddModList IE. The condReconfigToAddModList IE may map each candidate PSCell's PSCell configuration (e.g., SN RRC Reconfiguration message) to a corresponding CPC execution condition.
[0037] By way of example and not limitation, MN-initiated inter-SN CPC may be configured, prepared, or triggered as follows: MN1 initiates the inter-SN CPC procedure by requesting T-SN4 to allocate resources for UE3 using the SN Addition procedure. Specifically, MN1 may send an SN Addition Request message (e.g., SgNB Addition Request, or S-NODE Addition Request) to T-SN4. In this message, MN1 may indicate CPC initiation to T-SN4 and provide the T-SN4 with an upper limit (or maximum number) of candidate cells (candidate PSCells). T-SN4 sends cell identifiers (e.g., PSCell ID(s)) of one or more prepared candidate PSCells to MN1 via an SN Addition Request Acknowledge message. In addition, T-SN4 sends the SCG configuration (e.g., CG-Config) of each accepted candidate PSCell to MN1 via an SN Addition Request Acknowledge message. The MN1 generates a CPC execution condition for each candidate PSCell. Then, the MN1 sends the CPC configuration (e.g. ConditionalReconfiguration IE) to the UE3 via an MN RRC (Connection) Reconfiguration message. The CPC configuration includes one or more SCG configurations set by the T-SN4 for one or more candidate PSCells and one or more CPC execution conditions set by the MN1 for these one or more candidate PSCells. The MN1 may notify the S-SN2 that the MN-initiated inter-SN CPC has been configured, prepared, or triggered. This notification may be sent to the S-SN2 via an SN Release Request message (e.g. SgNB Release Request, or S-NODE Release Request).The SN Release Request message may include a new IE (e.g. CPC indication, CPC preparation indication / notification) or a new Cause (e.g. CPC is prepared / configured) for X2 / Xn. Alternatively, this notification may be sent to the S-SN2 via a new X2 / Xn message (e.g. MN-initiated CPC notification). The SN Release Request message or the new X2 / Xn message may include an identifier of the T-SN4 (e.g. global gNB / NG-RAN node ID).
[0038] In step 302, the MN1 does not configure an SN-initiated inter-SN CPC for at least the same T-SN4 with respect to the same UE3 while the MN-initiated inter-SN CPC is in progress. The expression that the MN-initiated inter-SN CPC is in progress can also be expressed as that the MN-initiated inter-SN CPC is prepared, configured, or triggered. The MN-initiated inter-SN CPC in progress may mean a situation in which the MN-initiated inter-SN CPC is not successfully completed or canceled after it is prepared. The successful completion of the CPC is notified to the MN1 by the UE3 sending an MN RRC (Connection) Reconfiguration Complete message including an SN RRC Reconfiguration Complete message to the MN1 in response to the establishment of the CPC execution condition. The cancellation of the CPC is performed, for example, by the MN1 notifying the UE3 of the cancellation or removal of the conditional reconfiguration for the CPC, and the NN1 receiving a response from the UE3.
[0039] Specifically, MN1 may inform S-SN2 that MN-initiated inter-SN CPC is in progress. This may be sent to S-SN2 via an SN Release Request message (e.g. SgNB Release Request) or other X2 / Xn message, as described above. In response to receiving the message, S-SN2 may understand that MN-initiated inter-SN CPC is in progress and refrain from initiating an SN-initiated inter-SN CPC procedure to the same T-SN4 for the same UE3. Additionally or alternatively, if MN1 receives an inter-node message from S-SN2 indicating a request for SN-initiated inter-SN CPC to the same T-SN4 while MN-initiated inter-SN CPC is in progress, MN1 may send a response message to S-SN2 indicating that the request is rejected because MN-initiated inter-SN CPC is in progress.
[0040] According to the operation described with reference to Fig. 3, the MN1 can prevent an SN-initiated inter-SN CPC to at least the same T-SN4 from proceeding simultaneously with respect to the same UE3 while an MN-initiated inter-SN CPC is in progress with respect to the same UE3. This can contribute to avoiding complex processing in the network (e.g., one or both of the MN1 and the T-SN4). This can also contribute to avoiding complex processing in the UE3.
[0041] In step 302, the MN1 may operate not to set an SN-initiated inter-SN CPC to the same T-SN4 for the same UE3 while an MN-initiated inter-SN CPC is in progress. In other words, the MN1 may determine whether to set a new SN-initiated inter-SN CPC for the UE3 on a T-SN basis. This may enable the MN1 to specify in detail the inter-SN CPC procedures to be suppressed for the UE3. This may contribute to avoiding excessive suppression of the SN-initiated inter-SN CPC procedures for the UE3. Alternatively, the MN1 may operate not to set an SN-initiated inter-SN CPC to any T-SN for the same UE3 while an MN-initiated inter-SN CPC is in progress for the UE3. In other words, the MN1 may determine whether to set a new SN-initiated inter-SN CPC for the UE3 on a UE basis. This may contribute to avoiding complex processing in the MN1 and the UE3, for example.
[0042] FIG. 4 shows an example of the operation of MN1. In step 401, MN1 configures, prepares, or triggers SN-initiated inter-SN CPC from S-SN2 to T-SN4 for a PSCell of UE3. Specifically, MN1 transmits a CPC configuration to UE3, and UE3 initiates evaluation of CPC execution conditions. More specifically, MN1 transmits an MN RRC (connection) reconfiguration message including the CPC configuration to UE3 to instruct UE3 to perform conditional reconfiguration for CPC. The CPC configuration includes SCG configuration of each of one or more candidate PSCells and CPC execution conditions of each candidate PSCell. The SCG configuration may be a configuration of a candidate PSCell (or a target PSCell). The SCG configuration (or a PSCell configuration) may be an SN RRC Reconfiguration message including the SCG configuration. The CPC configuration may be a ConditionalReconfiguration IE in a MN RRC (Connection) Reconfiguration message. The ConditionalReconfiguration IE may include a condReconfigToAddModList IE. The condReconfigToAddModList IE may map each candidate PSCell's PSCell configuration (eg, SN RRC Reconfiguration message) to a corresponding CPC execution condition.
[0043] By way of example and not limitation, SN-initiated inter-SN CPC may be configured, prepared, or triggered as follows: S-SN2 initiates inter-SN CPC procedure by sending SN Change Required message (e.g. SgNB Change Required or S-NODE Change Required) to MN1. In the message, S-SN2 indicates CPC initiation to MN1. The message includes T-SN4's identifier (e.g. global gNB / NG-RAN node ID). The message further includes CPC execution condition. MN1 may or may not be able to comprehend the CPC execution condition set by S-SN2. The CPC execution condition may be included in an RRC container (e.g. CG-Config or RRC level IE) transparent to MN1. MN1 then requests T-SN4 to allocate resources for UE3 using SN Addition procedure. Specifically, the MN1 may send an SN Addition Request message (e.g., SgNB Addition Request, or S-NODE Addition Request) to the T-SN4. In this message, the MN1 may indicate CPC initiation to the T-SN4 and provide an upper limit of candidate PSCells to the T-SN4. The T-SN4 sends PSCell ID(s) of one or more prepared (or accepted) candidate PSCells to the MN1 via an SN Addition Request Acknowledge message. In addition, the T-SN4 sends the SCG configuration (e.g., CG-Config) of each accepted candidate PSCell to the MN1 via an SN Addition Request Acknowledge message. The MN1 sends the CPC configuration (e.g., ConditionalReconfiguration IE) to the UE3 via an RRC (Connection) Reconfiguration message.The CPC configuration includes one or more SCG configurations set by the T-SN4 for one or more candidate PSCells and one or more CPC execution conditions set by the S-SN2 for these one or more candidate PSCells. The MN1 may notify the S-SN2 that the SN-initiated inter-SN CPC has been configured, prepared, or triggered. This notification may be sent to the S-SN2 via a SN Change Confirm message (e.g., SgNB Change Confirm). Alternatively, this notification may be sent to the S-SN2 via another X2 / Xn message, e.g., a Conditional PSCell Change Notification message.
[0044] In step 402, the MN1 does not configure an MN-initiated inter-SN CPC for at least the same T-SN4 with respect to the same UE3 while the SN-initiated inter-SN CPC is in progress. The expression that the SN-initiated inter-SN CPC is in progress can also be expressed as that the SN-initiated inter-SN CPC is prepared, configured, or triggered. The SN-initiated inter-SN CPC in progress may mean a situation in which the SN-initiated inter-SN CPC is not successfully completed or canceled after it is prepared. The successful completion of the CPC is notified to the MN1 by the UE3 transmitting an MN RRC (Connection) Reconfiguration Complete message including an SN RRC Reconfiguration Complete message to the MN1 in response to the establishment of the CPC execution condition. The cancellation of the CPC is performed, for example, by the MN1 notifying the UE3 of the cancellation or removal of the conditional reconfiguration for the CPC, and the NN1 receiving a response from the UE3.
[0045] In addition, the S-SN2 may not know the identifier of the T-SN4 (e.g., global gNB / NG-RAN node ID). Specifically, the S-SN2 may know the neighbor cell identifier but may not know the identifier of the RAN node providing the neighbor cell. In this case, the cell identifier of the candidate cell (candidate PSCell) (e.g., Cell Global Identifier (CGI), or a combination of Physical Cell Identity (PCI) and frequency) may be used instead of the identifier of the T-SN4. For example, in step 401, the S-SN2 may indicate the identifiers of the candidate cells (candidate PSCells) to the MN1 in an inter-node message (e.g., SN Change Required message) for starting the inter-SN CPC procedure. The MN1 may identify the identifier of the T-SN4 (e.g., global gNB / NG-RAN node) based on the correspondence between the cell identifiers of the neighbor cells and the RAN node identifiers held by the MN1. Similarly, in step 402, MN1 may detect T-SN4 for which SN-initiated inter-SN CPC is in progress based on the correspondence between the cell identifiers of neighboring cells and the identifiers of T-SN4 (e.g. global gNB / NG-RAN node) that it holds.
[0046] According to the operation described with reference to Fig. 4, the MN1 can prevent an MN-initiated inter-SN CPC to at least the same T-SN4 from proceeding simultaneously with respect to the same UE3 while an SN-initiated inter-SN CPC is in progress with respect to the UE3. This can contribute to avoiding complex processing in the network (e.g., one or both of the MN1 and the T-SN4). This can also contribute to avoiding complex processing in the UE3.
[0047] In step 402, the MN1 may operate not to set only an MN-initiated inter-SN CPC to the same T-SN4 for the same UE3 while an SN-initiated inter-SN CPC is in progress for the UE3. In other words, the MN1 may determine whether to set a new MN-initiated inter-SN CPC for the UE3 on a T-SN basis. This may enable the MN1 to specify in detail the inter-SN CPC procedures to be suppressed for the UE3. This may contribute to avoiding excessive suppression of the MN-initiated inter-SN CPC procedures for the UE3. Alternatively, the MN1 may operate not to set an MN-initiated inter-SN CPC to any T-SN for the same UE3 while an SN-initiated inter-SN CPC is in progress for the UE3. In other words, the MN1 may determine whether to set a new MN-initiated inter-SN CPC for the UE3 on a UE basis. This may contribute to avoiding complex processing in the MN1 and the UE3, for example.
[0048] The MN1 may perform only one of the operations described with reference to FIG. 3 and the operations described with reference to FIG. 4, or may perform both of them.
[0049] FIG. 5 shows an example of the operation of the S-SN2. In step 501, the S-SN2 exchanges signaling (i.e., X2 / Xn messages) with the MN1 to prepare an MN-initiated inter-SN CPC from the S-SN2 to the T-SN4 for the PSCell of the UE3. By way of example and not limitation, the S-SN2 may be notified by the MN1 that the MN-initiated inter-SN CPC has been configured, prepared, or triggered. This notification may be sent from the MN1 to the S-SN2 via a SN Release Request message (e.g., SgNB Release Request, or S-NODE Release Request). The SN Release Request message may include a new IE (e.g., CPC indication, CPC preparation indication / notification) or a new Cause (e.g., CPC is prepared / configured) for X2 / Xn. Alternatively, this notification may be sent to the S-SN2 via another X2 / Xn message (e.g., Conditional PSCell Change Notification message). This notification may be sent to the S-SN2 via a new X2 / Xn message (e.g., MN-initiated CPC notification). The SN Release Request message or another (new) X2 / Xn message may include the T-SN4's identifier (e.g., global gNB / NG-RAN node ID). The S-SN2 may send a response message (e.g., SgNB Release Request Acknowledge, or S-NODE Release Request Acknowledge) to the MN1.
[0050] In step 502, the S-SN2 does not initiate an SN-initiated inter-SN CPC to at least the same T-SN4 with respect to the same UE3 while the MN-initiated inter-SN CPC is in progress. The expression that the MN-initiated inter-SN CPC is in progress can also be expressed as that the MN-initiated inter-SN CPC is prepared, configured, or triggered. The MN-initiated inter-SN CPC in progress may mean a situation in which the MN-initiated inter-SN CPC is not successfully completed or canceled after it is prepared. The successful completion of the CPC is notified to the MN1 by the UE3 sending an MN RRC (Connection) Reconfiguration Complete message including an SN RRC Reconfiguration Complete message to the MN1 in response to the establishment of the CPC execution condition. The cancellation of the CPC is performed, for example, by the MN1 notifying the UE3 of the cancellation or removal of the conditional reconfiguration for the CPC, and the NN1 receiving a response from the UE3.
[0051] For example, if the S-SN2 receives a notification from the MN1 indicating that an MN-initiated inter-SN CPC is in progress, being prepared, or being triggered (step 501), it may operate not to initiate an SN-initiated inter-SN CPC to the same T-SN4 for the same UE 3. More specifically, if the S-SN2 receives an inter-node message (e.g., an SN Release Request message) including information indicating that the message is for a CPC from the MN1 during the procedure of preparing the MN-initiated inter-SN CPC (step 501), it may operate not to initiate an SN-initiated inter-SN CPC to the same T-SN4 for the same UE 3.
[0052] FIG. 6 shows an example of the operation of MN1 and S-SN2. The procedure shown in FIG. 6 is similar to that in FIG. 5. Step 601 is similar to step 501 in FIG. 5. Specifically, in step 601, MN1 sends an inter-node message for preparation of MN-initiated inter-SN CPC to S-SN2. The message indicates to S-SN2 that MN-initiated inter-SN CPC is in progress, prepared, or triggered. The message may be an SN Release Request message (e.g., SgNB Release Request, or S-NODE Release Request). The SN Release Request message may include a new IE of X2 / Xn (e.g., CPC indication, CPC preparation indication / notification) or a new Cause (e.g., CPC is prepared / configured). Alternatively, the message may be another X2 / Xn message (e.g., Conditional PSCell Change Notification message). The message may be a new X2 / Xn message. The inter-node message of step 601 may include an identifier of the T-SN4 (e.g. global gNB / NG-RAN node ID).
[0053] Step 602 is similar to step 502 of Figure 5. Specifically, in step 602, in response to receiving the message of step 602, the S-SN 2 operates to not initiate SN-initiated inter-SN CPC for the same UE 3, at least to the same T-SN 4.
[0054] As already described, the S-SN2 may not know the identifier of the T-SN4 (e.g., global gNB / NG-RAN node ID). Specifically, the S-SN2 may know the neighbor cell identifier but may not know the identifier of the RAN node providing the neighbor cell. In this case, the cell identifier of the candidate cell (candidate PSCell) (e.g., Cell Global Identifier (CGI), or a combination of Physical Cell Identity (PCI) and frequency) may be used instead of the identifier of the T-SN4. For example, in steps 501 and 601, the MN1 may indicate the identifiers of the candidate cells (candidate PSCells) to the S-SN2 in an inter-node message (e.g., SN Release Request message) for preparing the MN-initiated inter-SN CPC. The S-SN2 may identify the identifier of the T-SN4 (e.g., global gNB / NG-RAN node) based on the correspondence between the cell identifiers of the neighbor cells and the RAN node identifiers held by the S-SN2. Similarly, in steps 502 and 602, S-SN2 may detect T-SN4 for which MN-initiated inter-SN CPC is in progress based on the correspondence between the cell identifiers of neighboring cells and the identifiers of T-SN4 (e.g. global gNB / NG-RAN node) that it holds.
[0055] According to the operations described with reference to Figures 5 and 6, the S-SN 2 can prevent an SN-initiated inter-SN CPC to at least the same T-SN 4 for the same UE 3 from proceeding simultaneously while an MN-initiated inter-SN CPC is in progress for the same UE 3. This can contribute to avoiding complex processing in the network (e.g., one or both of the MN 1 and the T-SN 4). This can also contribute to avoiding complex processing in the UE 3.
[0056] In steps 502 and 602, the S-SN2 may operate not to initiate only an SN-initiated inter-SN CPC to the same T-SN4 for the same UE3 while an MN-initiated inter-SN CPC is in progress for the UE3. In other words, the S-SN2 may determine whether to initiate a new SN-initiated inter-SN CPC for the UE3 on a T-SN basis. This may enable the SN2 to finely specify the inter-SN CPC procedures to be suppressed for the UE3. This may contribute to avoiding excessive suppression of the SN-initiated inter-SN CPC procedures for the UE3. Alternatively, the S-SN2 may operate not to initiate an SN-initiated inter-SN CPC to any T-SN for the same UE3 while an MN-initiated inter-SN CPC is in progress for the UE3. In other words, the S-SN2 may determine whether to initiate a new SN-initiated inter-SN CPC for the UE3 on a UE basis. This can help to avoid complex processing in the MN 1, the S-SN 2 and the UE 3, for example.
[0057] 7 shows an example of the operation of MN1. In step 701, MN1 receives an inter-node message from S-SN2 indicating a request for SN-initiated inter-SN CPC to the same T-SN4 for UE3 while MN-initiated inter-SN CPC to T-SN4 for the same UE3 is in progress. The message may be an SN Change Required message (e.g. SgNB Change Required, or S-NODE Change Required). In the message, S-SN2 indicates CPC initiation to MN1. The message may include an identifier of T-SN4 and a CPC execution condition.
[0058] In step 702, MN1 replies to S-SN2 with a response message indicating that the request is rejected because MN-initiated inter-SN CPC is ongoing. The response message may be a SN Change Refuse message (e.g. SgNB Change Refuse, or S-NODE Change Refuse). The response message causes S-SN2 not to initiate a new SN-initiated inter-SN CPC to T-SN4 for UE3. In some implementations, the response message of step 702 is a SN Change Refuse message and may include a new IE (e.g. CPC preparation indication / notification) for X2 / Xn or a new cause (e.g. CPC is prepared / configured).
[0059] FIG. 8 shows an example of the operation of the S-SN2. The operation of the S-SN2 shown in FIG. 8 corresponds to the operation of the MN1 shown in FIG. 7. In step 801, the S-SN2 sends an inter-node message to the MN1 indicating a request for an SN-initiated inter-SN CPC. The message may be an SN Change Required message (e.g., SgNB Change Required, or S-NODE Change Required). In step 802, the S-SN2 receives a response message from the MN1 indicating that the request of step 801 is rejected. The response message indicates that the request is rejected because an MN-initiated inter-SN CPC is in progress. The response message may be an SN Change Refuse message (e.g., SgNB Change Refuse, or S-NODE Change Refuse). In step 803, in response to receiving the response message, the S-SN2 operates not to trigger a new SN-initiated inter-SN CPC to the same T-SN4 for the same UE3.
[0060] Figure 9 shows an example of the operation of MN1 and S-SN2. The procedure shown in Figure 9 is based on the operation of MN1 shown in Figure 7 and the operation of S-SN2 shown in Figure 8. In step 901, S-SN2 sends an inter-node message (e.g. SN Change Required) for SN-initiated inter-SN CPC to MN1. In step 902, MN1 responds with a reject message (e.g. SN Change Refuse) to S-SN2, indicating that the request is rejected because an MN-initiated inter-SN CPC is in progress. In step 903, in response to receiving the reject message, S-SN2 operates not to initiate (trigger) a new SN-initiated inter-SN CPC to the same T-SN4 for the same UE3.
[0061] As already described, the S-SN2 may not know the identifier of the T-SN4 (e.g., global gNB / NG-RAN node ID). Specifically, the S-SN2 may know the neighbor cell identifier but may not know the identifier of the RAN node providing the neighbor cell. In this case, the cell identifier of the candidate cell (candidate PSCell) (e.g., Cell Global Identifier (CGI), or a combination of Physical Cell Identity (PCI) and frequency) may be used instead of the identifier of the T-SN4. For example, in steps 701, 801, and 901, the S-SN2 may indicate the identifiers of the candidate cells (candidate PSCells) to the MN1 in an inter-node message (e.g., SN Change Required message) for initiating the inter-SN CPC procedure. The MN1 may identify the identifier of the T-SN4 (e.g., global gNB / NG-RAN node) based on the correspondence between the cell identifiers of the neighbor cells and the RAN node identifiers that it holds. In steps 702, 802, and 902, the MN1 may indicate identifiers of rejected candidate cells (candidate PSCells) to the S-SN2 in a rejection message (e.g., SN Change Refuse message). The S-SN2 may identify an identifier of the T-SN4 (e.g., global gNB / NG-RAN node) based on a correspondence relationship between the cell identifiers of neighboring cells and RAN node identifiers held by the S-SN2. Similarly, in steps 803 and 903, the S-SN2 may detect the T-SN4 for which the MN-initiated inter-SN CPC is in progress based on a correspondence relationship between the cell identifiers of neighboring cells and the identifiers of the T-SN4 (e.g., global gNB / NG-RAN node) held by the S-SN2.
[0062] According to the operations described with reference to Figures 7, 8, and 9, MN1 and S-SN2 can prevent SN-initiated inter-SN CPC to at least the same T-SN4 for the same UE3 from proceeding simultaneously while MN-initiated inter-SN CPC for the same UE3 is in progress. This can contribute to avoiding complex processing in the network (e.g., one or both of MN1 and T-SN4). This can also contribute to avoiding complex processing in UE3.
[0063] In steps 702, 802, and 902, the MN1 may operate not to accept only an MN-initiated inter-SN CPC to the same T-SN4 for the same UE3 while an SN-initiated inter-SN CPC is in progress for the UE3. In other words, the MN1 may determine whether to accept a request for a new SN-initiated inter-SN CPC for the UE3 on a T-SN basis. Similarly, in steps 803 and 903, the S-SN2 may operate not to initiate only a new SN-initiated inter-SN CPC to the same T-SN4 for the same UE3 while an MN-initiated inter-SN CPC is in progress for the UE3. In other words, the S-SN2 may determine whether to initiate a new SN-initiated inter-SN for the UE3 on a T-SN basis. This allows the MN1 and the S-SN2 to specify in detail the inter-SN CPC procedures to be suppressed for the UE3. This may contribute to avoiding excessive suppression of SN-initiated inter-SN CPC procedures for UE3. Alternatively, MN1 may operate not to accept a request for SN-initiated inter-SN CPC to any T-SN for the same UE3 while MN-initiated inter-SN CPC is in progress for the same UE3. In other words, MN1 may determine whether to accept a request for a new SN-initiated inter-SN CPC for the UE3 on a per-UE basis. Similarly, S-SN2 may operate not to start an SN-initiated inter-SN CPC to any T-SN for the same UE3 while MN-initiated inter-SN CPC is in progress for the UE3. In other words, S-SN2 may determine whether to start a new SN-initiated inter-SN CPC for the UE3 on a per-UE basis. This may contribute to avoiding complex processing in, for example, MN1, S-SN2, and UE3.
[0064] <Second embodiment> A configuration example of a wireless communication network according to this embodiment is similar to the example shown in Figures 1 and 2. In the following, the operations of MN1 and S-SN2 regarding inter-SN CPC will be described.
[0065] Fig. 10 shows an example of the operation of MN1 and S-SN2. In step 1001, MN1 transmits to S-SN2 an SN Release Request message (e.g. SgNB Release Request, or S-NODE Release Request) including information indicating that this message is for inter-SN CPC during a procedure of preparing MN-initiated inter-SN CPC from S-SN2 to T-SN4 for the PSCell of UE3. The information may be a new IE (e.g. CPC indication, CPC preparation indication / notification) of X2 / Xn included in the SN Release Request message. Alternatively, the information may be a new Cause (e.g. CPC preparation / mobility, CPC is prepared / requested / configured) included in the SN Release Request message. Here, the procedure for preparing an MN-initiated inter-SN CPC may include multiple steps for MN1 to enable UE3 to initiate evaluation of CPC execution conditions by sending a CPC configuration to UE3, the CPC configuration including CPC execution conditions and SCG configuration.
[0066] The SN Release Request message in step 1001 causes the S-SN2 to continue providing user data to the UE3 until a future CPC execution. In step 1002, in response to receiving the SN Release Request message, the S-SN2 continues providing user data to the UE3 until a future CPC execution. In other words, the S-SN2 receives the SN Release Request message but does not stop providing user data to the UE3.
[0067] The operation described with reference to Figure 10 can enable the S-SN2 to recognize that the SN Release Request message is for an inter-SN CPC. In other words, the S-SN2 can distinguish whether the SN Release Request message received in the MN-initiated inter-SN CPC preparation procedure is for a normal SCG release (or SN change) or for an inter-SN CPC. This can therefore prevent the S-SN2 from stopping the provision of user data to the UE3 in response to the reception of the SN Release Request message before the CPC execution condition is met.
[0068] FIG. 11 shows an example of the operation of the MN 1 and the S-SN 2. Steps 1101 and 1102 are the same as steps 1001 and 1002 in FIG. 10. In step 1103, the MN 1 detects the establishment of the execution condition of the inter-SN CPC. The MN 1 may detect the establishment of the execution condition of the inter-SN CPC by receiving an RRC message transmitted from the UE 3 in response to the establishment of the CPC execution condition. More specifically, the UE 3 may transmit an MN RRC (Connection) Reconfiguration Complete message including an SN RRC Reconfiguration Complete message (to the T-SN 3) to the MN 1 in response to the establishment of the CPC execution condition. The MN 1 may detect the establishment of the execution condition of the inter-SN CPC by receiving the MN RRC (Connection) Reconfiguration Complete message including the SN RRC Reconfiguration Complete message. Additionally or alternatively, the UE 3 may transmit information indicating which candidate cell (candidate PSCell) the inter-SN CPC execution condition is met for (i.e., which candidate cell CPC is to be executed for) to the MN 1 in the RRC message.
[0069] If the MN RRC connection reconfiguration procedure is successful, the MN1 informs the T-SN4 via a SN Reconfiguration Complete message (not shown) which includes the SN RRC Reconfiguration Complete message received from the UE3. Further, in step 1104, the MN1 transmits an inter-node message to the S-SN2 in response to the CPC execution or the satisfaction of the CPC execution condition. The inter-node message may be a Conditional PSCell Change Notification message or an (additional) SN Release Request message. The message of step 1104 may include an indication of the CPC execution or an indication of the satisfaction of the CPC execution condition. In step 1105, in response to receiving the message of step 1104, the S-SN2 stops providing user data to the UE3. Further, if applicable, the S-SN2 may start data forwarding.
[0070] The operation described with reference to FIG. 11 enables the S-SN 2 to stop providing user data to the UE 3 in a timely manner in the case of a MN initiated CPC.
[0071] <Third embodiment> A configuration example of a wireless communication network according to this embodiment is similar to the example shown in Figures 1 and 2. In the following, the operations of MN1, S-SN2, and T-SN4 regarding the inter-SN CPC will be described.
[0072] Figure 12 shows an example of the operation of T-SN4. In step 1201, T-SN4 receives a request from MN1 for inter-SN CPC from S-SN2 to T-SN4 for UE3. This inter-SN CPC may be initiated by MN1 or by S-SN2. The request message in step 1201 may be an SN Addition Request message (e.g. SgNB Addition Request, or S-NODE Addition Request). In this message, MN1 may indicate CPC initiation to T-SN4 and provide an upper limit (or maximum number) of candidate PSCells to T-SN4.
[0073] In step 1202, the T-SN4 decides to reject the request and sends a rejection message to the MN1. The rejection message may be an SN Addition Request Reject (e.g., SgNB Addition Request Reject, or S-NODE Addition Request Reject). The rejection message indicates whether any inter-SN CPC is not accepted by the T-SN4, or only inter-SN CPC for one or more candidate cells (candidate PSCells) specified by the request is not accepted. Specifically, the rejection message may indicate any of a plurality of causes including a first cause and a second cause. The first cause indicates that the T-SN4 is not able to accept any inter-SN CPC. In contrast, the second cause indicates that the T-SN4 is able to accept an inter-SN CPC, but is not able to accept an inter-SN CPC for all of the one or more candidate cells specified by the request. In other words, the second cause indicates that the T-SN4 is able to accept an inter-SN CPC, but rejects the inter-SN CPC for one or more candidate cells specified by the request.
[0074] The operation described with reference to FIG. 12 may enable MN1 to distinguish between multiple causes of inter-SN CPC rejection. Specifically, MN1 may know whether T-SN4 cannot accept any inter-SN CPC. In other words, MN1 may determine whether any inter-SN CPC is not accepted by T-SN4, or whether only inter-SN CPCs for one or more candidate cells specified by the request are not accepted. If T-SN4 can accept inter-SN CPCs, but only inter-SN CPCs for one or more candidate cells specified by the request are rejected, MN1 may send a request for a new inter-SN CPC specifying another candidate PSCell to T-SN4. This may prevent the opportunity for inter-SN CPC from being excessively restricted.
[0075] In the case of SN-initiated inter-SN CPC, MN1 may inform S-SN2 of the cause of CPC rejection. This may be sent to S-SN2 via a SN Change Refuse message (e.g. SgNB Change Refuse or S-NODE Change Refuse). This allows S-SN2 to determine whether any inter-SN CPC is not accepted by T-SN4 or only inter-SN CPC for one or more candidate cells specified by the request is not accepted. If T-SN4 is able to accept inter-SN CPC but only inter-SN CPC for one or more candidate cells specified by the request is rejected, S-SN2 may send a request for a new inter-SN CPC specifying other candidate PSCells to T-SN4 via MN1. This may prevent the opportunity for inter-SN CPC from being overly restricted.
[0076] Figure 13 shows an example of the operation of MN1, S-SN2 and T-SN4. In case of SN-initiated inter-SN CPC, in step 1301, S-SN2 sends an SN Change Required message for the inter-SN CPC to MN1. In case of MN-initiated inter-SN CPC, step 1301 is skipped. In step 1302, MN1 sends an SN Addition Request message for the inter-SN CPC to T-SN4. Step 1302 corresponds to step 1201 in Figure 12. In step 1303, T-SN4 responds with an SN Addition Request Reject message to MN1. The SN Addition Request Reject message indicates whether T-SN4 cannot accept any inter-SN CPC. Step 1303 corresponds to step 1202 in Figure 12. In the case of an SN-initiated inter-SN CPC, in step 1304, MN1 responds with an SN Change Refuse message to T-SN2, indicating whether T-SN4 cannot accept any inter-SN CPC.
[0077] Next, configuration examples of the MN1, S-SN2, T-SN4, and UE3 according to the above-mentioned embodiments will be described below. FIG. 14 is a block diagram showing a configuration example of the MN1 according to the above-mentioned embodiments. The configurations of the S-SN2 and T-SN4 may also be similar to the configuration shown in FIG. 14. Referring to FIG. 14, the MN1 includes a Radio Frequency transceiver 1401, a network interface 1403, a processor 1404, and a memory 1405. The RF transceiver 1401 performs analog RF signal processing to communicate with UEs including the UE3. The RF transceiver 1401 may include multiple transceivers. The RF transceiver 1401 is coupled to the antenna array 1402 and the processor 1404. The RF transceiver 1401 receives modulation symbol data from the processor 1404, generates a transmission RF signal, and provides the transmission RF signal to the antenna array 1402. The RF transceiver 1401 also generates a baseband receive signal based on the receive RF signal received by the antenna array 1402 and supplies the baseband receive signal to the processor 1404. The RF transceiver 1401 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
[0078] The network interface 1403 is used to communicate with network nodes (e.g., S-SN2, T-SN4, and control and forwarding nodes of the core network). The network interface 1403 may include, for example, a network interface card (NIC) that complies with the IEEE 802.3 series.
[0079] The processor 1404 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The processor 1404 may include multiple processors. For example, the processor 1404 may include a modem processor (e.g., Digital Signal Processor (DSP)) performing digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) performing control plane processing. The processor 1404 may include a digital beamformer module for beamforming. The digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and a precoder.
[0080] The memory 1405 is configured by a combination of volatile memory and non-volatile memory. The volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof. The memory 1405 may include storage located remotely from the processor 1404. In this case, the processor 1404 may access the memory 1405 via the network interface 1403 or an I / O interface not shown.
[0081] The memory 1405 may store one or more software modules (computer programs) 1406 including instructions and data for performing the processing by MN1 described in the above-mentioned embodiments. In some implementations, the processor 1404 may be configured to read the software modules 1406 from the memory 1405 and execute them to perform the processing by MN1 described in the above-mentioned embodiments.
[0082] In addition, when the MN1 is a CU (eg, eNB-CU or gNB-CU) or a CU-CP, the MN1 does not need to include the RF transceiver 1401 (and the antenna array 1402).
[0083] FIG. 15 is a block diagram showing a configuration example of the UE3. A radio frequency (RF) transceiver 1501 performs analog RF signal processing to communicate with the MN1, the S-SN2, and the T-SN4. The RF transceiver 1501 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 1501 includes frequency up-conversion, frequency down-conversion, and amplification. The RF transceiver 1501 is coupled to an antenna array 1502 and a baseband processor 1503. The RF transceiver 1501 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1503, generates a transmission RF signal, and provides the transmission RF signal to the antenna array 1502. The RF transceiver 1501 also generates a baseband reception signal based on the reception RF signal received by the antenna array 1502, and provides the baseband reception signal to the baseband processor 1503. The RF transceiver 1501 may include an analog beamformer circuit for beamforming. The analog beamformer circuitry includes, for example, multiple phase shifters and multiple power amplifiers.
[0084] The baseband processor 1503 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of transmission format (transmission frame), (d) transmission line coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). On the other hand, the control plane processing includes communication management of layer 1 (e.g., transmission 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).
[0085] For example, the digital baseband signal processing by the baseband processor 1503 may include 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. Also, the control plane processing by the baseband processor 1503 may include processing of a Non-Access Stratum (NAS) protocol, an RRC protocol, and a MAC Control Element (CE).
[0086] The baseband processor 1503 may perform MIMO encoding and precoding for beamforming.
[0087] The baseband processor 1503 may include a modem processor (e.g., DSP) that performs digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1504 described later.
[0088] The application processor 1504 is also called a CPU, an MPU, a microprocessor, or a processor core. The application processor 1504 may include multiple processors (multiple processor cores). The application processor 1504 executes a system software program (operating system (OS)) and various application programs (e.g., a calling application, a web browser, a mailer, a camera operation application, and a music playback application) read from the memory 1506 or a memory not shown, thereby implementing various functions of the UE3.
[0089] In some implementations, the baseband processor 1503 and the application processor 1504 may be integrated on a single chip, as shown by the dashed line (1505) in Figure 15. In other words, the baseband processor 1503 and the application processor 1504 may be implemented as a single System on Chip (SoC) device 1505. An SoC device may also be called a system Large Scale Integration (LSI) or a chipset.
[0090] The memory 1506 is a volatile memory or a non-volatile memory, or a combination thereof. The memory 1506 may include a plurality of physically independent memory devices. The volatile memory is, for example, an SRAM or a DRAM, or a combination thereof. The non-volatile memory is an MROM, an EEPROM, a flash memory, or a hard disk drive, or any combination thereof. For example, the memory 1506 may include an external memory device accessible from the baseband processor 1503, the application processor 1504, and the SoC 1505. The memory 1506 may include an internal memory device integrated in the baseband processor 1503, the application processor 1504, or the SoC 1505. Furthermore, the memory 1506 may include a memory in a Universal Integrated Circuit Card (UICC).
[0091] The memory 1506 may store one or more software modules (computer programs) 1507 including instructions and data for performing processing by the UE 3 described in the above-mentioned embodiments. In some implementations, the baseband processor 1503 or the application processor 1504 may be configured to read the software modules 1507 from the memory 1506 and execute them to perform processing by the UE 3 described in the above-mentioned embodiments using the drawings.
[0092] In addition, the control plane processing and operations performed by UE3 described in the above embodiment can be realized by elements other than the RF transceiver 1501 and the antenna array 1502, i.e., at least one of the baseband processor 1503 and the application processor 1504, and the memory 1506 storing the software module 1507.
[0093] As described with reference to FIG. 14 and FIG. 15, each of the processors of MN1, S-SN2, T-SN4, and UE3 according to the above-mentioned embodiments can execute one or more programs including instructions for making a computer perform the algorithms described with reference to the drawings. The programs include instructions (or software codes) for making a computer perform one or more functions described in the embodiments when the programs are loaded into a computer. The programs may be stored in a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable media or tangible storage media include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disk (DVD), Blu-ray (registered trademark) disk or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The programs may be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, the transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.
[0094] <Other embodiments> In the above-mentioned embodiment, there is a MN initiated inter-SN CPC initiated by MN1 and a SN initiated inter-SN CPC initiated by S-SN2. As shown in some of the above-mentioned embodiments, these two procedures may not be initiated (or configured) at the same time for one UE3. However, it is also assumed that they may be initiated (or configured) at the same time unintentionally. This may happen especially when MN1 and S-SN2 are configured and managed by different network vendors. In this case, UE3 may consider the inter-SN CPC that is initiated (or configured) earlier as valid (or high priority) and the inter-SN CPC that is initiated (or configured) later as invalid (or low priority). UE3 may determine (or recognize) whether the indicated conditional reconfiguration is for MN initiated CPC or SN initiated CPC from the execution conditions of CPC. For example, in the case of MN initiated CPC, the execution conditions may be indicated to UE3 as a measurement configuration of MCG or a similar configuration. Conversely, in the case of SN initiated CPC, the execution conditions may be indicated to the UE 3 as a measurement configuration of the SCG or a similar configuration. Based on these differences, the UE 3 may determine (or recognize) whether the CPC is MN initiated or SN initiated. Additionally or alternatively, the MN 1 or S-SN 2 may transmit information to the UE 3 explicitly indicating whether the CPC is MN initiated or SN initiated.
[0095] In the above embodiment, when the execution conditions for the candidate cell of the CPC are met or satisfied, the UE3 may check (eg, compliance check) the SCG setting of the candidate cell (i.e., the target PSCell) included in the CPC setting (eg, ConditionalReconfiguration IE) at this point. If there is no problem in checking the SCG setting, the UE3 may start random access to the candidate cell (T-SN4 that manages the candidate cell). However, if there is a problem in checking the SCG setting, the UE3 may transmit SCG Failure Information for the candidate cell to the MN1 by the SRB of the MCG. Alternatively, the UE3 may start random access to one of the other candidate cells (e.g., the cell with the best reception quality) to attempt connection to the target cell by the CPC. At this time, the UE3 may select the target cell to be randomly accessed from other candidate cells for which the execution conditions are met, or from other candidate cells for which the execution conditions are not met. Furthermore, in order to select a target cell for random access, the UE3 may distinguish between the MN initiated inter-SN CPC from the MN1 and the SN initiated inter-SN CPC from the S-SN2. For example, if the candidate cell for which the execution condition is satisfied is set for the SN initiated CPC, the UE3 may select other candidate cells only from among the candidate cells set for the SN initiated CPC. Conversely, if the candidate cell for which the execution condition is satisfied is set for the MN initiated CPC, the UE3 may select other candidate cells only from among the candidate cells set for the MN initiated CPC. Note that the UE3 may also perform a similar operation in the case where the UE3 initiates random access to the candidate cell for which the execution condition is satisfied but fails (Random access failure).
[0096] In one or more of the above-mentioned embodiments, the MN1 can send a CPC configuration (e.g., ConditionalReconfiguration IE) including the CPC execution condition and the SCG configuration to the UE3 in an MN RRC (Connection) Reconfiguration message. When the UE3 successfully receives (and checks compliance with) the RRC (Connection) Reconfiguration message, it sends an RRC response message (e.g., an MN RRC (Connection) Reconfiguration Complete message) to the MN1. This triggers the MN1 to send an SN Release Request message to the S-SN2. The MN1 indicates that the SN Release Request message is for inter-SN CPC, so that the S-SN2 can recognize it. Then, when the CPC execution condition is satisfied in one of the candidate cells, the UE3 again sends an MN RRC message (e.g., an MN RRC (Connection) Reconfiguration Complete message) to the MN1. The MN RRC message includes an SN RRC Reconfiguration Complete message to the T-SN3. When MN1 receives the MN RRC message, it transmits a Conditional PSCell Change Notification message to S-SN2. On the other hand, if the execution of CPC fails after transmitting the first MN RRC message to MN1, it is assumed that UE3 transmits SCG Failure Information to MN1. In this case, MN1 may release S-SN2 and cancel DC, or may request SN Addition to another SN. However, since MN1 has already transmitted an SN Release Request message to S-SN2, it cannot transmit another SN Release Request message to the same S-SN2 indicating that the SN will be released normally (completely). Therefore, MN1 may transmit a new X2 / Xn message to S-SN2 to notify the release of DC or the release of S-SN2.In this case, the new X2 / Xn message may be, for example, an SN Release Notification. Alternatively, the MN1 may retransmit an SN Release Request message including a new Cause (e.g., CPC is failed, recovery from CPC failure). This allows the S-SN2 to recognize that the UE3 has failed in CPC and the MN1 is performing a recovery procedure.
[0097] In one or more of the above-mentioned embodiments, the T-SN4 decides whether to accept CPC for one or more candidate PSCells in response to receiving an SN Addition Request message indicating a request for CPC from the MN1. The T-SN4 transmits information indicating the accepted candidate PSCells to the MN1 in an SN Addition Request Acknowledge message. At this time, the information indicating the accepted candidate PSCells may be indicated in an X2 / Xn level IE or an RRC container (e.g., CG-Config or an RRC level IE) included in the message. Furthermore, these may be indicated in a list format. The MN1 may forward or transmit the information indicating the accepted candidate PSCells received from the T-SN4 in a message (e.g., an SN Release Request message) addressed to the S-SN2 indicating a notification that the MN-initiated inter-SN CPC has been configured, prepared, or triggered. This allows the S-SN2 to recognize that an MN-initiated inter-SN CPC has been configured, prepared, or triggered for the accepted candidate PSCells.
[0098] Furthermore, the above-described embodiment is merely an example of application of the technical idea obtained by the inventor of the present invention. In other words, the technical idea is not limited to the above-described embodiment, and various modifications are possible.
[0099] For example, some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes.
[0100] (Appendix 1) A Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for a User Equipment (UE), comprising: At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor is configured to not configure, prepare, or allow an SN-initiated inter-SN Conditional PSCell Change (CPC) for the UE to at least the target SN while an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN for the UE is in progress. RAN node. (Appendix 2) the at least one processor is configured to notify the source SN that the MN-initiated inter-SN CPC is in progress; RAN node as described in Appendix 1. (Appendix 3) The at least one processor is configured to, during the procedure of preparing the MN-initiated inter-SN CPC, send an inter-node message to the source SN, the inter-node message including information indicating that the message is for a CPC. 3. A RAN node as defined in claim 1 or 2. (Appendix 4) The inter-node message is an SN Release Request message; RAN node as described in Appendix 3. (Appendix 5) the at least one processor is configured, if receiving an inter-node message indicating a request for an SN-initiated inter-SN CPC from the source SN to the target SN while the MN-initiated inter-SN CPC is in progress, to send a response message to the source SN indicating that the request is rejected because an MN-initiated inter-SN CPC is in progress. 3. A RAN node as defined in claim 1 or 2. (Appendix 6) The at least one processor is configured to not configure or prepare an MN-initiated inter-SN CPC for the UE to at least the target SN while an SN-initiated inter-SN CPC for the UE to the target SN is ongoing for the PSCell of the UE. 6. The RAN node according to claim 1 . (Appendix 7) 1. A method performed by a Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for a User Equipment (UE), comprising: not configuring, preparing, or allowing an SN-initiated inter-SN Conditional PSCell Change (CPC) for the UE to at least the target SN while an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN for a Primary SCG Cell (PSCell) of a Secondary Cell Group (SCG) of the UE is in progress; method. (Appendix 8) A program for causing a computer to perform a method for a Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for User Equipment (UE), the method comprising: The method comprises not configuring, preparing or allowing, for the UE, an SN-initiated inter-SN Conditional PSCell Change (CPC) to at least the target SN from a source Secondary Node (SN) for a Primary SCG Cell (PSCell) of a Secondary Cell Group (SCG) of the UE while an MN-initiated inter-SN Conditional PSCell Change (CPC) to the target SN is in progress. program. (Appendix 9) 1. A Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for a User Equipment (UE), comprising: At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor is configured to not initiate an SN-initiated inter-SN Conditional PSCell Change (CPC) for the UE to at least the target SN while an MN-initiated inter-SN Conditional PSCell Change (CPC) from the source SN to a target SN for the UE is in progress. RAN node. (Appendix 10) The at least one processor is configured to not initiate an SN-initiated inter-SN CPC to the target SN for the UE if a notification is received from a Master Node (MN) indicating that the MN-initiated inter-SN CPC is in progress. RAN node as described in Supplementary Note 9. (Appendix 11) The at least one processor is configured not to initiate an SN-initiated inter-SN CPC to the target SN for the UE if an inter-node message including information indicating that the message is for a CPC is received from a Master Node (MN) during a procedure of preparing the MN-initiated inter-SN CPC. RAN node as described in Supplementary Note 9. (Appendix 12) The inter-node message is an SN Release Request message; 13. The RAN node according to claim 11. (Appendix 13) The at least one processor is configured to not initiate a new SN-initiated inter-SN CPC to the target SN for the UE if a response message is received from a Master Node (MN) indicating that a request for an SN-initiated inter-SN CPC is rejected because an MN-initiated inter-SN CPC is in progress. RAN node as described in Supplementary Note 9. (Appendix 14) 1. A method performed by a Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for a User Equipment (UE), comprising: not initiating an SN-initiated inter-SN Conditional PSCell Change (CPC) for the UE to at least the target SN while an MN-initiated inter-SN Conditional PSCell Change (CPC) from the source SN to a target SN for the UE is in progress. method. (Appendix 15) 1. A program for causing a computer to perform a method for a Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for User Equipment (UE), the method comprising: The method comprises not initiating an SN-initiated inter-SN Conditional PSCell Change (CPC) for the UE to at least the target SN while an MN-initiated inter-SN Conditional PSCell Change (CPC) from the source SN to a target SN for the UE is ongoing for a Primary SCG Cell (PSCell) of the SCG of the UE. program. (Appendix 16) A Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for a User Equipment (UE), comprising: At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor is configured to, during a procedure of preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN for a Primary SCG Cell (PSCell) of a Secondary Cell Group (SCG) of the UE, send an SN Release Request message to the source SN, the SN including information indicating that the message is for an inter-SN CPC. RAN node. (Appendix 17) The SN Release Request message causes the source SN to continue providing user data to the UE until execution of the CPC. 16. The RAN node according to claim 16. (Appendix 18) The at least one processor is configured to send an inter-node message to the source SN in response to execution of the CPC or establishment of an execution condition of the CPC after sending the SN Release Request message. 18. The RAN node of claim 16 or 17. (Appendix 19) The inter-node message causes the source SN to stop providing user data to the UE. 17. The RAN node according to claim 18. (Appendix 20) 1. A method performed by a Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for a User Equipment (UE), comprising: During a procedure of preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN for a Primary SCG Cell (PSCell) of a Secondary Cell Group (SCG) of the UE, sending an SN Release Request message to the source SN, the SN Release Request message including information indicating that the message is for an inter-SN CPC. method. (Appendix 21) A program for causing a computer to perform a method for a Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for User Equipment (UE), the method comprising: The method comprises, during a procedure of preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN for a Primary SCG Cell (PSCell) of a Secondary Cell Group (SCG) of the UE, sending an SN Release Request message to the source SN, the SN Release Request message including information indicating that the message is for an inter-SN CPC. program. (Appendix 22) 1. A Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for a User Equipment (UE), comprising: At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor is configured to receive, during a procedure of preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from the source SN to a target SN for a Primary SCG Cell (PSCell) of the SCG of the UE, an SN Release Request message including information indicating that the message is for an inter-SN CPC from a Master Node (MN); RAN node. (Appendix 23) The at least one processor is configured, in response to receiving the SN Release Request message, to continue providing user data to the UE until execution of the CPC. 23. The RAN node according to claim 22. (Appendix 24) The at least one processor is configured to stop providing user data to the UE in response to receiving, after receiving the SN Release Request message, an inter-node message indicating execution of the CPC or establishment of a condition for executing the CPC from the MN. 24. The RAN node of claim 22 or 23. (Appendix 25) 1. A method performed by a Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for a User Equipment (UE), comprising: receiving an SN Release Request message from a Master Node (MN) during a procedure of preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from the source SN to a target SN for a Primary SCG Cell (PSCell) of the SCG of the UE, the SN Release Request message including information indicating that the message is for an inter-SN CPC; method. (Appendix 26) 1. A program for causing a computer to perform a method for a Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for User Equipment (UE), the method comprising: The method comprises receiving, during a procedure of preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from the source SN to a target SN for a Primary SCG Cell (PSCell) of the SCG of the UE, an SN Release Request message containing information indicating that the message is for an inter-SN CPC from a Master Node (MN); program. (Appendix 27) A Radio Access Network (RAN) node configured to operate as a target Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for a User Equipment (UE), comprising: At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor is configured to send a rejection message to a Master Node (MN) when rejecting a request for an inter-SN Conditional Primary SCG Cell (PSCell) Change (CPC) from a source SN to the target SN; The rejection message indicates whether any inter-SN CPCs are not accepted by the target SN, or only the inter-SN CPCs for one or more candidate cells specified by the request are not accepted. RAN node. (Appendix 28) The rejection message indicates any of a number of reasons, The multiple causes include: A first cause indicating that the target SN does not accept any inter-SN CPCs; and A second cause indicating that the target SN is capable of accepting inter-SN CPCs but is not capable of accepting inter-SN CPCs for any of the one or more candidate cells specified by the request; Including, 27. The RAN node according to claim 27. (Appendix 29) 1. A method performed by a Radio Access Network (RAN) node configured to operate as a target Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for a User Equipment (UE), comprising: If a request for an inter-SN Conditional Primary SCG Cell (PSCell) Change (CPC) from a source SN to the target SN is rejected, a rejection message is sent to a Master Node (MN); The rejection message indicates whether any inter-SN CPCs are not accepted by the target SN, or only the inter-SN CPCs for one or more candidate cells specified by the request are not accepted. method. (Appendix 30) 1. A program for causing a computer to perform a method for a Radio Access Network (RAN) node configured to operate as a target Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for User Equipment (UE), the method comprising: The method comprises: if a request for an inter-SN Conditional Primary SCG Cell (PSCell) Change (CPC) from a source SN to the target SN is rejected, sending a rejection message to a Master Node (MN); The rejection message indicates whether any inter-SN CPCs are not accepted by the target SN, or only the inter-SN CPCs for one or more candidate cells specified by the request are not accepted. program.
[0101] This application claims priority based on Japanese Patent Application No. 2021-116604, filed on July 14, 2021, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]
[0102] 1 Master Node (MN) 2. Source Secondary Node (S-SN) 3. User Equipment (UE) 4. Target Secondary Node (T-SN) 1404 processor 1405 Memory 1406 Modules 1503 Baseband Processor 1504 Application Processor 1506 Memory 1507 Modules
Claims
1. A Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for User Equipment (UE), comprising: In a procedure for preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN with respect to a Primary SCG Cell (PSCell) of the UE, a means for transmitting first information including a CPC execution condition and configuration information to the UE; means for transmitting, after transmitting the first information to the UE, a first inter-node message to the source SN, the first inter-node message including information indicating that the message is for an inter-SN CPC; A means for transmitting a second inter-node message to the source SN in response to receiving a Radio Resource Control (RRC) Reconfiguration Complete message transmitted from the UE in response to the establishment of the CPC execution condition; RAN node comprising:
2. The first inter-node message causes the source SN to continue providing user data to the UE until execution of the CPC.
2. The RAN node of claim 1.
3. The second inter-node message causes the source SN to stop providing user data to the UE.
3. A RAN node according to claim 1 or 2.
4. A method performed by a Radio Access Network (RAN) node configured to operate as a Master Node (MN) associated with a Master Cell Group (MCG) in dual connectivity for User Equipment (UE), comprising: In a procedure for preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN with respect to a Primary SCG Cell (PSCell) of the UE, sending first information to the UE, the first information including a CPC execution condition and configuration information; After sending the first information to the UE, sending a first inter-node message to the source SN, the first inter-node message including information indicating that the message is for an inter-SN CPC; In response to receiving an RRC Reconfiguration Complete message transmitted from the UE in response to the establishment of the CPC execution condition, transmitting a second inter-node message to the source SN. method.
5. A Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for User Equipment (UE), comprising: In a procedure for preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN with respect to a Primary SCG Cell (PSCell) of the UE, after a Master Node (MN) transmits first information including a CPC execution condition and configuration information to the UE, a means for receiving a first inter-node message from the MN including information indicating that the message is for an inter-SN CPC; A means for receiving, from the MN, a second inter-node message that is transmitted by the MN in response to receiving an RRC Reconfiguration Complete message transmitted from the UE in response to the establishment of the CPC execution condition; RAN node comprising:
6. The method further comprises: in response to receiving the first inter-node message, continuing to provide user data to the UE until execution of the CPC.
6. The RAN node of claim 5.
7. The method further comprises: a means for stopping provision of user data to the UE in response to receiving, after receiving the first inter-node message, the second inter-node message indicating execution of the CPC or establishment of the CPC execution condition from the MN.
7. A RAN node according to claim 5 or 6.
8. A method performed by a Radio Access Network (RAN) node configured to operate as a source Secondary Node (SN) associated with a Secondary Cell Group (SCG) in dual connectivity for User Equipment (UE), comprising: In a procedure for preparing an MN-initiated inter-SN Conditional PSCell Change (CPC) from a source Secondary Node (SN) to a target SN with respect to a Primary SCG Cell (PSCell) of the UE, after a Master Node (MN) transmits first information including a CPC execution condition and configuration information to the UE, receiving a first inter-node message from the MN including information indicating that the message is for an inter-SN CPC; receiving, from the MN, a second inter-node message transmitted by the MN in response to receiving an RRC Reconfiguration Complete message transmitted from the UE in response to the establishment of the CPC execution condition; method.
Citation Information
Patent Citations
Method and apparatus for conditional pscell change
US20210099926A1
