Secondary base station and method thereof
By implementing RAN nodes with processors to manage and reject inconsistent configurations, the issue of incomplete uplink setups in dual connectivity scenarios is resolved, ensuring proper resource utilization and maintaining effective dual connectivity.
Patent Information
- Application Number
- JP2022557541
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-10-20
- Filing Date
- 2021-10-19
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2041-10-19
AI Technical Summary
The inconsistency between the Cell Group ID IE and UL Configuration IE in 3GPP specifications for radio bearers in multi-connectivity scenarios can lead to situations where the SN does not configure UL resources, resulting in incomplete uplink configurations for MN terminated or SN terminated bearers.
Implementing RAN nodes with processors that transmit messages indicating radio bearer setups or modifications, rejecting or ignoring configurations that result in inconsistent or unused resources, and ensuring that both MCG and SCG resources are properly utilized.
Prevents incomplete uplink configurations by ensuring that RAN nodes correctly interpret and manage resources, avoiding situations where UL configurations are not set up in either the MN or SN, thereby maintaining effective dual connectivity.
Smart Images

Figure 0007578143000001 
Figure 0007578143000002 
Figure 0007578143000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to wireless communication systems, and more particularly to signaling between radio access network nodes for multi-connectivity (eg, dual connectivity). [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP) defines signaling between Radio Access Network (RAN) nodes, i.e., Master Node (MN) and Secondary Node (SN), for Multi-Radio Dual Connectivity (MR-DC) (see, for example, Non-Patent Documents 1 and 2). In MR-DC, an MN is a RAN node that provides a control plane connection to a core network for a User Equipment (UE), and an SN is a RAN node that does not provide the control plane connection to a UE. In MR-DC, a group of one or more serving cells associated with an MN is called a Master Cell Group (MCG), and a group of one or more serving cells associated with an SN is called a Secondary Cell Group (SCG).
[0003] For example, an MN can request the SN to add or modify SN resources for a PDU Session via an SN ADDITION REQUEST message or an SN MODIFICATION REQUEST message. Using these messages, an MN can request the SN to set up or modify SCG resources for a MN terminated bearer. In MR-DC, an MN terminated bearer is a data radio bearer for which a Packet Data Convergence Protocol (PDCP) is located at the MN. An MN terminated bearer that requires SCG resources is an MN terminated SCG bearer or an MN terminated split bearer. An SCG bearer is a radio bearer that has a Radio Link Control (RLC) bearer only in the SCG. A split bearer is a radio bearer that has both an RLC bearer in the MCG and an RLC bearer in the SCG. These MN terminated bearers requiring SCG resources require resources (i.e., Xn-U bearers or Xn-U tunnels) of the user plane interface (i.e., Xn-U interface) between the MN and the SN for delivery of PDCP data (i.e., PDCP Protocol Data Units (PDUs)).
[0004] Also, for example, the SN can request the MN to add or modify MN resources for a PDU Session via an SN ADDITION REQUEST ACKNOWLEDGE message, an SN MODIFICATION REQUEST ACKNOWLEDGE message, or an SN MODIFICATION REQUIRED message. Using these messages, the SN can request the MN to set up MCG resources for SN terminated bearers. An SN terminated bearer is a data radio bearer for which PDCP is located in the SN. An SN terminated bearer that requires MCG resources is an SN terminated MCG bearer or an SN terminated split bearer. An MCG bearer is a radio bearer that has an RLC bearer only in the MCG. These MN terminated bearers that require MCG resources require resources (i.e., Xn-U bearers or Xn-U tunnels) of the user plane interface (i.e., Xn-U interface) between the MN and the SN for delivery of PDCP data (i.e., PDCP PDUs). [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] 3GPP TS 37.340 V15.10.0 (2020-09) "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 15)", September 2020 [Non-Patent Document 2] 3GPP TS 38.423 V15.9.0 (2020-09) "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 15)", September 2020 Summary of the Invention [Problem to be solved by the invention]
[0006] According to the current 3GPP specification, when requesting the SN to set up SCG resources for a MN terminated bearer, the MN includes in the SN ADDITION REQUEST or SN MODIFICATION REQUEST message a PDU Session Resource Setup Info - MN terminated IE, which contains the DRBs to Be Setup Item information element (IE) associated with the MN terminated bearer. This DRBs to Be Setup Item IE can contain a UL Configuration IE. In the current specification, the UL Configuration IE is optional. The UL Configuration IE indicates how the UE uses the uplink of the SN for the MN terminated bearer. More specifically, the UL Configuration IE can be set to the value "no data", the value "shared" or the value "only". The value "no data" means that the UE does not use the uplink of the corresponding node (ie, SN) for the radio bearer (ie, MN terminated bearer). The value "shared" means that the UE uses both the uplink of the corresponding node (i.e., SN) and the uplink of the other node (i.e., MN) for the radio bearer (i.e., MN terminated bearer). The value "only" means that the UE uses only the uplink of the corresponding node (i.e., SN) for the radio bearer (i.e., MN terminated bearer).
[0007] On the other hand, in the current 3GPP specifications, the MN UL PDCP UP TNL Information IE is mandatory in the above DRBs to Be Setup Item IE. As described in Non-Patent Document 2, the MN UL PDCP UP TNL Information IE refers to the UP Transport Parameters IE (Section 9.2.3.76 in Non-Patent Document 2) and includes the UP Transport Layer Information IE and the Cell Group ID IE. Both the UP Transport Layer Information IE and the Cell Group ID IE are mandatory information elements. The UP Transport Layer Information IE indicates the MN endpoint of the Xn-U bearer for delivery of uplink (UL) PDCP PDUs of the MN terminated bearer. The Cell Group ID IE can be set to only the value "0" meaning MCG, or only the value "1" meaning SCG, or both the value "0" and the value "1". Therefore, although it is not explicitly stated in the current 3GPP specifications, it can be assumed that a Cell Group ID IE set to the value "0" means an MCG bearer, a Cell Group ID IE set to the value "1" means an SCG bearer, and a Cell Group ID IE set to both "0" and "1" means a split bearer.
[0008] However, inconsistencies may occur between the above Cell Group ID IE and the above UL Configuration IE. For example, in the above case of SCG resource setup for a MN terminated bearer, the Cell Group ID IE may be set to value “1” while the UL Configuration IE may be set to value “no data”. In other words, the Cell Group ID IE may imply that the MN terminated bearer is an SCG bearer, while the UL Configuration IE may indicate that the SN's UL is not used. According to the current 3GPP specifications, it is not clear how the SN should understand these IEs in this case. This may lead in the worst case to a situation where the SN does not configure UL resources for the UE and no uplink configuration for the MN terminated bearer exists in either the MN (MCG) or the SN (SCG).
[0009] The above problem may also occur when the MN requests the SN to modify SCG resources for a MN terminated bearer.Similarly, this problem may also occur when the SN requests the MN to set up or modify MCG resources for a SN terminated bearer.
[0010] 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 the above-mentioned problems. 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 problems and novel features will be apparent from the description of this specification or the accompanying drawings. [Means for solving the problem]
[0011] In a first aspect, a first RAN node includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive a first message from a second RAN node in a control procedure for dual connectivity for a User Equipment (UE) indicating a setup or modification of a radio bearer terminated at a second RAN node, the at least one processor configured to reject the setup or the modification of the radio bearer if a first IE in the first message indicates that the radio bearer uses only resources of a cell group of the first RAN node and a second IE in the first message indicates that the UE does not use an uplink of the first RAN node for the radio bearer.
[0012] In a second aspect, a method performed by a first RAN node includes the following steps: (a) receiving, from a second RAN node, a first message indicating a setup or modification of a radio bearer terminated at the second RAN node in a control procedure for dual connectivity for a User Equipment (UE); and (b) rejecting the setup or the modification of the radio bearer if a first IE in the first message indicates that the radio bearer uses only resources of a cell group of the first RAN node and a second IE in the first message indicates that the UE does not use an uplink of the first RAN node for the radio bearer.
[0013] In a third aspect, a first RAN node includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive a first message from a second RAN node in a control procedure for dual connectivity for a User Equipment (UE) indicating a setup or modification of a radio bearer terminated at a second RAN node, the at least one processor configured to ignore a first IE included in the first message with respect to an endpoint of the second RAN node of an inter-RAN node tunnel used for delivery of uplink PDUs if a second IE in the first message indicates that the UE does not use an uplink of the first RAN node for the radio bearer.
[0014] In a fourth aspect, a method performed by a first RAN node includes the steps of: (a) receiving, from a second RAN node, a first message indicating a setup or modification of a radio bearer terminated at the second RAN node in a control procedure for dual connectivity for a User Equipment (UE); and (b) if a second IE in the first message indicates that the UE does not use an uplink of the first RAN node for the radio bearer, ignoring a first IE included in the first message regarding the second RAN node endpoint of an inter-RAN node tunnel used for delivery of uplink PDUs.
[0015] In a fifth aspect, a RAN node configured to operate as a dual connectivity MN for a UE includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to include a first IE for a radio bearer terminated at the MN in a first message sent to the dual connectivity SN. The at least one processor is configured to include a second IE in the first message indicating how the UE uses an uplink of the SN for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of an MCG of the MN and resources of an SCG of the SN. The at least one processor is configured to transmit the first message to the SN.
[0016] In a sixth aspect, a method performed by a RAN node configured to act as a MN for dual connectivity for a UE includes the steps of: (a) including a first IE related to a radio bearer terminated at the MN in a first message transmitted to the dual connectivity SN; (b) including in the first message a second IE indicating how the UE uses the uplink of the SN for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of the MCG of the MN and resources of the SCG of the SN; and (c) sending the first message to the SN;
[0017] In a seventh aspect, a RAN node configured to operate as a dual connectivity SN for a UE includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to include a first IE for a radio bearer terminated at the SN in a first message sent to the dual connectivity MN. The at least one processor is configured to include a second IE in the first message indicating how the UE uses the MN's uplink for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of the MN's MCG and resources of the SN's SCG. The at least one processor is configured to transmit the first message to the MN.
[0018] In an eighth aspect, a method performed by a RAN node configured to operate as a dual connectivity SN for a UE includes the steps of: (a) including a first IE related to a radio bearer terminated at the SN in a first message transmitted to the dual connectivity MN; (b) including in the first message a second IE indicating how the UE uses the MN's uplink for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of the MN's MCG and resources of the SN's SCG; and (c) sending the first message to the MN;
[0019] A ninth aspect is directed to a program comprising instructions (software code) for causing a computer to carry out a method according to the second, fourth, sixth or eighth aspect above when the program is loaded into the computer. Effect of the Invention
[0020] According to the above aspects, it is possible to provide an apparatus, a method, and a program that contribute to solving the above-mentioned problems. [Brief description of the drawings]
[0021] [Figure 1] 1 is a diagram illustrating an example of the configuration of a wireless communication network according to an embodiment. [Diagram 2] 11 is a flowchart showing an example of an operation of a MN according to the embodiment. [Diagram 3] 1 is a flowchart showing an example of an operation of an SN according to an embodiment. [Figure 4] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Diagram 5] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 6] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 7] 11 is a flowchart showing an example of an operation of a MN according to the embodiment. [Figure 8] 1 is a flowchart showing an example of an operation of an SN according to an embodiment. [Figure 9] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 10] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 11] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 12] 11 is a flowchart showing an example of an operation of a MN according to the embodiment. [Figure 13] 1 is a flowchart showing an example of an operation of an SN according to an embodiment. [Figure 14] FIG. 2 is a block diagram showing an example of the configuration of an MN and an SN according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0022] 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.
[0023] 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.
[0024] 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). More specifically, the embodiments are described with a focus on MR-DC with 5G Core (5GC). However, these embodiments may be applied to other wireless communication systems that support technologies similar to 3GPP multi-connectivity (eg, 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.
[0025] <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, 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.
[0026] Each of RAN nodes 1 and 2 may be a Next Generation (NG) RAN node, more specifically a gNB or a ng-eNB. The ng-eNB is a node that provides Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the UE and can be connected to the 5GC via an NG interface. The Radio Access Technology (RAT) of RAN node 1 may be different from that of RAN node 2.
[0027] The RAN node 1 may be a Central Unit (eg, ng-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 (eg, ng-eNB-DUs or gNB-DUs). C-RAN is also referred to as CU / DU split. Furthermore, a CU may include a Control Plane (CP) Unit (eg, gNB-CU-CP) and one or more User Plane (UP) Units (eg, 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, the RAN node 2 may be a Central Unit (CU) or a combination of a CU and one or more Distributed Units (DUs). The RAN node 2 may be a CU-CP or a combination of a CU-CP and a CU-UP.
[0028] RAN node 1 and RAN node 2 communicate with each other via an inter-node interface (i.e., Xn interface) 103. RAN node 1 and RAN node 2 act as MN and SN, respectively, for dual connectivity. UE 3 communicates with MN 1 and SN 2 via air interfaces 101 and 102, and performs dual connectivity for MCG associated with MN 1 and SCG associated with SN 2.
[0029] This dual connectivity may be Multi-Radio Dual Connectivity (MR-DC). More specifically, the dual connectivity may be MR-DC with 5GC. MR-DC with 5GC includes NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), NR-E-UTRA Dual Connectivity (NE-DC), and NR-NR Dual Connectivity (NR-DC). Accordingly, MN1 may be either a master ng-eNB (in NGEN-DC) or a master gNB (in NR-DC and NE-DC). Similarly, SN2 may be either a secondary ng-eNB (in NE-DC) or a secondary gNB (in NR-DC and NGEN-DC). In NGEN-DC, UE3 is connected to an ng-eNB operating as MN1 and a gNB operating as SN2. In NE-DC, UE3 is connected to a gNB operating as MN1 and a ng-eNB operating as SN2. In NR-DC, UE3 is connected to one gNB (or gNB-DU) operating as MN1 and to another gNB (or gNB-DU) operating as SN2.
[0030] The MCG is a group of serving cells associated with (or provided by) the MN1. The MCG 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 by) the SN2. The SCG includes the primary cell of the SCG (i.e., a Primary SCG Cell (PSCell)) and optionally one or more Secondary Cells (SCells). The PSCell is the Special Cell (SpCell) of the SCG and supports Physical Uplink Control Channel (PUCCH) transmission and contention-based Random Access.
[0031] In the following, an example of the operation of MN1 and SN2 according to this embodiment will be described. Figure 2 shows an example of the operation of MN1. In step 201, MN1 receives an XnAP message from SN2 indicating the setup or modification of a radio bearer terminated in SN2 (SN terminated bearer). The XnAP message may request MN1 to add (or set up) or modify resources of MN1 for the SN terminated bearer. The XnAP message may request MN1 to prepare resources of MN1 for the SN terminated bearer or to prepare the modification of the resources. The XnAP message may be an SN ADDITION REQUEST ACKNOWLEDGE message, an SN MODIFICATION REQUEST ACKNOWLEDGE message, or an SN MODIFICATION REQUIRED message. In step 202, MN1 rejects the setup or modification of the radio bearer (i.e., SN terminated bearer) if the first IE in the XnAP message indicates that the radio bearer uses only MCG resources and the second IE in the XnAP message indicates that the radio bearer does not use MN1's UL resources. In other words, MN1 does not admit the setup or modification of MN resources or MCG resources or both for the radio bearer.
[0032] In some implementations, the first IE may be a Cell Group ID IE included in an SN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) associated with the radio bearer (i.e., SN terminated bearer). As described in 3GPP TS 2013-010666, the SN UL PDCP UP TNL Information IE refers to an UP Transport Parameters IE (Section 9.2.3.76 of 3GPP TS 2013-010666), and includes an UP Transport Layer Information IE and a Cell Group ID IE. The Cell Group ID IE can be set to only the value "0" meaning MCG, or to only the value "1" meaning SCG, or to both the value "0" and the value "1". If the Cell Group ID IE is set to only the value "0", this may indicate that the radio bearer uses only resources of the MCG.
[0033] Meanwhile, the second IE may be a UL Configuration IE included in the DRBs to Be Setup Item IE (or the DRBs to Be Modified Item IE). This UL Configuration IE indicates how the UE 3 uses the uplink of the corresponding RAN node (i.e., MN1) for the radio bearer (i.e., SN terminated bearer). More specifically, the UL Configuration IE can be set to the value "no data", "shared", or "only". The value "no data" means that the UE 3 does not use the uplink of the corresponding node (i.e., MN1) for the radio bearer (i.e., SN terminated bearer). The value "shared" means that the UE 3 uses both the uplink of the corresponding node (i.e., MN1) and the uplink of the other node (i.e., SN2) for the radio bearer (i.e., SN terminated bearer). The value "only" means that the UE3 will only use the uplink of the corresponding node (ie, MN1) for the radio bearer (ie, SN terminated bearer).
[0034] In some implementations, MN1 may operate as follows to reject the setup or modification of the radio bearer (i.e., SN terminated bearer): After receiving an SN ADDITION REQUEST ACKNOWLEDGE (or SN MODIFICATION REQUEST ACKNOWLEDGE) message from SN2, MN1 may initiate an SN Release procedure to release SN2 (or stop dual connectivity). Alternatively, after receiving an SN ADDITION REQUEST ACKNOWLEDGE (or SN MODIFICATION REQUEST ACKNOWLEDGE) message from SN2, MN1 may initiate an SN Modification procedure to request SN2 to release the radio bearer. Alternatively, in response to receiving an SN MODIFICATION REQUIRED message from SN2, MN1 may send an SN MODIFICATION REFUSE message to SN2 indicating that the entire requested modification is not allowed. Alternatively, in response to receiving the SN MODIFICATION REQUIRED message from SN2, MN1 may send an SN MODIFICATION CONFIRM message to SN2 indicating that modification of the MN resources for that radio bearer is not permitted.
[0035] Fig. 3 shows an example of the operation of SN2. In step 301, SN2 receives an XnAP message from MN1 indicating setup or modification for a radio bearer terminated in MN1 (MN terminated bearer). The XnAP message may request SN2 to add (or setup) or modify resources of SN2 for the MN terminated bearer. The XnAP message may request SN2 to prepare resources of SN2 for the MN terminated bearer or to prepare modification of said resources. The XnAP message may be an SN ADDITION REQUEST message or an SN MODIFICATION REQUEST message. In step 302, SN2 rejects setup or modification of the radio bearer (i.e., MN terminated bearer) if a first IE in the XnAP message indicates that the radio bearer uses only SCG resources and a second IE in the XnAP message indicates that the radio bearer does not use UL resources of SN2. In other words, SN2 does not admit the setup or modification of SN resources or SCG resources or both for that radio bearer.
[0036] In some implementations, the first IE may be a Cell Group ID IE included in an MN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) associated with the radio bearer (i.e., MN terminated bearer). As described in 3GPP TS 2013-010666, the MN UL PDCP UP TNL Information IE refers to an UP Transport Parameters IE (Section 9.2.3.76 of 3GPP TS 2013-010666), and includes an UP Transport Layer Information IE and a Cell Group ID IE. The Cell Group ID IE can be set to only the value "0" meaning MCG, or only the value "1" meaning SCG, or both the value "0" and the value "1". If the Cell Group ID IE is set to only the value "1", this may indicate that the radio bearer uses only resources of the SCG.
[0037] Meanwhile, the second IE may be a UL Configuration IE included in the DRBs to Be Setup Item IE (or the DRBs to Be Modified Item IE). This UL Configuration IE indicates how the UE 3 uses the uplink of the corresponding RAN node (i.e., SN2) for the radio bearer (i.e., MN terminated bearer). More specifically, the UL Configuration IE can be set to the value "no data", the value "shared", or the value "only". The value "no data" means that the UE 3 does not use the uplink of the corresponding node (i.e., SN2) for the radio bearer (i.e., MN terminated bearer). The value "shared" means that the UE 3 uses both the uplink of the corresponding node (i.e., SN2) and the uplink of the other node (i.e., MN1) for the radio bearer (i.e., MN terminated bearer). The value "only" means that the UE 3 will only use the uplink of the corresponding node (ie, SN2) for this radio bearer (ie, MN terminated bearer).
[0038] In some implementations, the SN2 may operate as follows to reject the setup or modification of the radio bearer (i.e., MN terminated bearer): In response to receiving an SN ADDITION REQUEST (or SN MODIFICATION REQUEST) message from the MN1, the SN2 may send an SN ADDITION REQUEST REJECT (or SN MODIFICATION REQUEST REJECT) message to the MN1, i.e., the SN2 may reject the entire requested SN addition procedure (or SN modification procedure). Alternatively, in response to receiving an SN ADDITION REQUEST (or SN MODIFICATION REQUEST) message from the MN1, the SN2 may send an SN ADDITION REQUEST ACKNOWLEDGE (or SN MODIFICATION REQUEST ACKNOWLEDGE) message indicating that the setup or modification of SN resources for the radio bearer is not allowed. MN1 may be sent to
[0039] In the following, a specific example of the operation of MN1 and SN2 described using Figures 2 and 3 will be described. The signaling shown in Figure 4 relates to an SN addition procedure and an SN modification procedure. The SN addition procedure is an S-NG-RAN node Addition Preparation procedure. The SN modification procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure.
[0040] In step 401, the MN1 sends an S-NODE ADDITION REQUEST message to the SN2. 3The S-NODE ADDITION REQUEST message indicates to the SN2 the setup of the MN terminated bearer for the PDU Session. In other words, the S-NODE ADDITION REQUEST message requests the SN2 to add or set up SN resources for the MN terminated bearer. More specifically, the S-NODE ADDITION REQUEST message contains a PDU Session Resources To Be Added Item IE for the PDU Session. The PDU Session Resources To Be Added Item IE contains a PDU Session Resource Setup Info - MN terminated IE. The PDU Session Resource Setup Info - MN terminated IE contains a DRBs to Be Setup Item IE for the MN terminated bearer. The DRBs to Be Setup Item IE contains a MN UL PDCP UP TNL Information IE which contains a Cell Group ID IE and further contains a UL Configuration IE. In the example of Figure 4, the Cell Group ID IE is set only to the value "1", which implies that the MN terminated bearer is an SCG bearer, while the UL Configuration IE is set to the value "no data", which indicates that the uplink of SN2 is not used for the MN terminated bearer.
[0041] In step 401, the MN1 may send an S-NODE MODIFICATION REQUEST message to the SN2. The S-NODE MODIFICATION REQUEST message is 3The S-NODE MODIFICATION REQUEST message indicates to the SN2 the setup or modification of the MN terminated bearer for the PDU Session. In other words, the S-NODE MODIFICATION REQUEST message requests the SN2 to add (or set up) or modify SN resources for the N terminated bearer. More specifically, the S-NODE MODIFICATION REQUEST message may contain a PDU Session Resources To Be Added Item IE for the setup of the PDU Session. The PDU Session Resources To Be Added Item IE contains a PDU Session Resource Setup Info - MN terminated IE. Alternatively, the S-NODE MODIFICATION REQUEST message may contain a PDU Session Resources To Be Modified Item IE for the modification of the PDU Session. The PDU Session Resources To Be Modified Item IE contains a PDU Session Resource Modification Info - MN terminated IE. The PDU Session Resource Setup Info - MN terminated IE (or PDU Session Resource Modification Info - MN terminated IE) contains a DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) for the MN terminated bearer. The DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) contains a MN UL PDCP UP TNL Information IE that contains a Cell Group ID IE, and further contains a UL Configuration IE.In the example of Figure 4, the Cell Group ID IE is set only to the value "1", which implies that the MN terminated bearer is an SCG bearer, while the UL Configuration IE is set to the value "no data", which indicates that the uplink of SN2 is not used for the MN terminated bearer.
[0042] In step 402, SN2 decides whether to accept the requested setup or modification of SN resources for the MN terminated bearer. In the example of Fig. 4, SN2 notices that the UL Configuration IE in the DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) for the MN terminated bearer is set to the value "no data" and the Cell Group ID IE included in the MN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) is set only to the value "1" meaning the SCG. In response, SN2 decides to reject (or not accept) the setup or modification of SN resources for the MN terminated bearer.
[0043] In step 403, the SN2 informs the MN1 of the rejection of the requested setup or modification of the MN terminated bearer. As already explained, the SN2 may reject the entire S-NG-RAN node addition preparation procedure. In this case, the SN2 may send an S-NODE ADDITION REQUEST REJECT message to the MN1. The Cause IE in the S-NODE ADDITION REQUEST REJECT message may indicate, for example but not limited to, "invalid bearer Option configuration", "Invalid UL configuration", "Invalid UL resource configuration" or "Bearer Option not Valid". Alternatively, the SN2 may selectively reject the setup of SN resources for the MN terminated bearer. In this case, the SN2 may send an S-NODE ADDITION REQUEST ACKNOWLEDGE message to the MN1 containing the PDU Session Resource Setup Response Info - MN terminated IE indicating that the setup of the MN terminated bearer is not allowed. The PDU Session Resource Setup Response Info - MN terminated IE contains a DRBs Not Admitted To Be Setup or Modified List IE containing the Data Radio Bearer (DRB) ID of the MN terminated bearer. The DRBs Not Admitted To Be Setup or Modified List IE may contain a Cause IE associated with the MN terminated bearer.The Cause IE may indicate, but is not limited to, for example, "invalid bearer Option configuration", "Invalid UL configuration", "Invalid UL resource configuration", or "Bearer Option not Valid".
[0044] Alternatively, in step 403, the SN2 may reject the entire S-NG-RAN node modification preparation procedure. In this case, the SN2 may send an S-NODE MODIFICATION REQUEST REJECT message to the MN1. The Cause IE in the S-NODE MODIFICATION REQUEST REJECT message may indicate, for example but not limited to, "invalid bearer Option configuration", "Invalid UL configuration", "Invalid UL resource configuration" or "Bearer Option not Valid". Alternatively, the SN2 may selectively reject the setup or modification of the MN terminated bearer. In this case, the SN2 may send an S-NODE Modification REQUEST ACKNOWLEDGE message to the MN1 containing a PDU Session Resource Setup Response Info - MN terminated IE (or a PDU Session Resource Modification Response Info - MN terminated IE) indicating that the setup or modification of the MN terminated bearer is not allowed. The PDU Session Resource Setup Response Info - MN terminated IE (or PDU Session Resource Modification Response Info - MN terminated IE) contains a DRBs Not Admitted To Be Setup or Modified List IE containing the DRB ID of the MN terminated bearer. The DRBs Not Admitted To Be Setup or Modified List IE may contain a Cause IE associated to the MN terminated bearer.The Cause IE may indicate, but is not limited to, for example, "invalid bearer Option configuration", "Invalid UL configuration", "Invalid UL resource configuration", or "Bearer Option not Valid".
[0045] The signaling shown in Figure 5 is related to the SN addition procedure and the SN modification procedure. The SN addition procedure is the S-NG-RAN node Addition Preparation procedure. The SN modification procedure is the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure.
[0046] In step 501, the SN2 sends an S-NODE ADDITION REQUEST ACKNOWLEDGE message to the MN1. The S-NODE ADDITION REQUEST ACKNOWLEDGE message is 3The S-NODE ADDITION REQUEST ACKNOWLEDGE message indicates to MN1 the setup of the SN terminated bearer for the PDU Session. In other words, the S-NODE ADDITION REQUEST ACKNOWLEDGE message requests MN1 to add or set up MN resources for the SN terminated bearer. More specifically, the S-NODE ADDITION REQUEST ACKNOWLEDGE message contains a PDU Session Resources Admitted To Be Added Item IE for the PDU Session. The PDU Session Resources Admitted To Be Added Item IE contains a PDU Session Resource Setup Response Info - SN terminated IE. The PDU Session Resource Setup Response Info - SN terminated IE contains an SN UL PDCP UP TNL Information IE which contains a Cell Group ID IE and further contains a UL Configuration IE. In the example of Fig. 5, the Cell Group ID IE is set only to the value "0", which implies that the SN terminated bearer is an MCG bearer. Meanwhile, the UL Configuration IE is set to the value "no data", which indicates that the uplink of MN1 is not used for the SN terminated bearer.
[0047] In step 501, the SN2 may send an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the MN1. The S-NODE MODIFICATION REQUEST ACKNOWLEDGE message may be sent to the UE 3The S-NODE MODIFICATION REQUEST ACKNOWLEDGE message indicates to MN1 the setup of the SN terminated bearer for the PDU Session. In other words, the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message requests MN1 to add or setup MN resources for the SN terminated bearer. More specifically, the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message may contain a PDU Session Resources Admitted To Be Added Item IE for the setup of the PDU Session. The PDU Session Resources Admitted To Be Added Item IE contains a PDU Session Resource Setup Response Info - SN terminated IE. Alternatively, the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message may contain a PDU Session Resources Admitted To Be Modified Item IE for the modification of the PDU Session. The PDU Session Resources Admitted To Be Modified Item IE contains a PDU Session Resource Modification Response Info - SN terminated IE. The PDU Session Resource Setup Response Info - SN terminated IE (or PDU Session Resource Modification Response Info - SN terminated IE) contains a DRBs to Be Setup Item IE for the SN terminated bearer. The DRBs to Be Setup Item IE contains a SN UL PDCP UP TNL Information IE which contains a Cell Group ID IE and further contains a UL Configuration IE.In the example of Fig. 5, the Cell Group ID IE is set only to the value "0", which implies that the SN terminated bearer is an MCG bearer, while the UL Configuration IE is set to the value "no data", which indicates that the uplink of MN1 is not used for the SN terminated bearer.
[0048] In step 502, MN1 decides whether to accept the setup of MN resources for the requested SN terminated bearer. In the example of Fig. 5, MN1 recognizes that the UL Configuration IE in the DRBs to Be Setup Item IE for the SN terminated bearer is set to the value "no data" and the Cell Group ID IE included in the MN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set only to the value "0" meaning MCG. In response, MN1 decides to reject (or not accept) the setup of MN resources for the SN terminated bearer.
[0049] In step 503, MN1 notifies the refusal of the requested SN terminated bearer setup. SN2As already explained, MN1 may initiate the M-NG-RAN node initiated S-NG-RAN node Release procedure to release SN2 (or stop dual connectivity). Specifically, MN1 may send an S-NODE RELEASE REQUEST message to SN2. Alternatively, MN1 may selectively reject the setup of MN resources for the SN terminated bearer. In this case, MN1 may initiate the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure to request SN2 to release the SN terminated bearer. Specifically, MN1 may send an S-NODE MODIFICATION REQUEST message to SN2. The S-NODE MODIFICATION REQUEST message contains a PDU Session Resource Modification Info - SN terminated IE containing a DRBs To Be Released List IE indicating the DRB ID of the SN terminated bearer.
[0050] The signaling shown in Figure 6 is related to an SN modification procedure, which is an S-NG-RAN node initiated S-NG-RAN node Modification procedure.
[0051] In step 601, the SN2 sends an S-NODE MODIFICATION REQUIRED message to the MN1. 3The S-NODE MODIFICATION REQUIRED message indicates to MN1 the setup or modification of the SN terminated bearer for the PDU Session. In other words, the S-NODE MODIFICATION REQUIRED message requests MN1 to add (or set up) or modify MN resources for the SN terminated bearer. More specifically, the S-NODE MODIFICATION REQUIRED message may contain a PDU Session Resources To Be Modified Item IE for the modification of the PDU Session. The PDU Session Resources To Be Modified Item IE contains a PDU Session Resource Modification Required Info - SN terminated IE. The PDU Session Resource Modification Required Info - SN terminated IE contains a DRBs to Be Setup Item IE (or a DRBs to Be Modified Item IE) for the SN terminated bearer. The DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) contains an SN UL PDCP UP TNL Information IE which contains a Cell Group ID IE, and further contains a UL Configuration IE. In the example of Fig. 6, the Cell Group ID IE is set only to the value "0", which implies that the SN terminated bearer is an MCG bearer. Meanwhile, the UL Configuration IE is set to the value "no data", which indicates that the uplink of MN1 is not used for the SN terminated bearer.
[0052] In step 602, MN1 decides whether to accept the requested setup or modification of MN resources for the SN terminated bearer. In the example of Fig. 6, MN1 notices that the UL Configuration IE in the DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) for the SN terminated bearer is set to the value "no data" and the Cell Group ID IE included in the SN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) is set only to the value "0" meaning MCG. In response, MN1 decides to reject (or not accept) the setup or modification of MN resources for the SN terminated bearer.
[0053] In step 603, MN1 informs SN2 of the rejection of the requested setup or modification of the SN terminated bearer. As already explained, MN1 may reject the entire S-NG-RAN node initiated S-NG-RAN node Modification procedure. In this case, MN1 may send an S-NODE MODIFICATION REFUSE message to SN2. The Cause IE in the S-NODE MODIFICATION REFUSE message may indicate, for example but not limited to, "invalid bearer Option configuration", "Invalid UL configuration", "Invalid UL resource configuration" or "Bearer Option not Valid". Alternatively, MN1 may selectively reject the setup or modification of the SN resources for the SN terminated bearer. In this case, MN1 may send an S-NODE MODIFICATION CONFIRM message containing the PDU Session Resource Modification Confirm Info - SN terminated IE indicating that the setup or modification of the SN terminated bearer is not allowed. SN2The PDU Session Resource Modification Confirm Info - SN terminated IE contains a DRBs Not Admitted To Be Setup or Modified List IE containing the DRB ID of the SN terminated bearer. The DRBs Not Admitted To Be Setup or Modified List IE may contain a Cause IE associated to the SN terminated bearer. The Cause IE may indicate, for example but not limited to, "invalid bearer Option configuration", "Invalid UL configuration", "Invalid UL resource configuration" or "Bearer Option not Valid".
[0054] According to the operation of MN1 described in this embodiment, MN1 can reject the setup or modification of MN resources for the SN terminated bearer if there is an inconsistency between the Cell Group ID IE and UL Configuration IE received from SN2 for the setup or modification of MN resources for the SN terminated bearer. This can avoid a situation where an uplink configuration for the SN terminated bearer does not exist in either MN (MCG) or SN (SCG). Similarly, according to the operation of SN2 described in this embodiment, SN2 can reject the setup or modification of SN resources for the MN terminated bearer if there is an inconsistency between the Cell Group ID IE and UL Configuration IE received from MN1 for the setup or modification of SN resources for the MN terminated bearer. This can avoid a situation where an uplink configuration for the MN terminated bearer does not exist in either MN (MCG) or SN (SCG).
[0055] <Second embodiment> A configuration example of a wireless communication network according to this embodiment is similar to the example shown in Fig. 1. This embodiment provides another example of the operation of the MN1 and the SN2.
[0056] FIG. 7 shows an example of the operation of MN1. In step 701, MN1 receives an XnAP message from SN2 indicating the setup or modification of a radio bearer terminated in SN2 (SN terminated bearer). The XnAP message may request MN1 to add (or set up) or modify resources of MN1 for the SN terminated bearer. The XnAP message may request MN1 to prepare resources of MN1 for the SN terminated bearer or to prepare the modification of the resources. The XnAP message may be an SN ADDITION REQUEST ACKNOWLEDGE message, an SN MODIFICATION REQUEST ACKNOWLEDGE message, or an SN MODIFICATION REQUIRED message. Steps 7 In 02, MN1 ignores the first IE included in the XnAP message regarding the SN endpoint of the Xn-U tunnel used for delivery of UL PDUs if the second IE in the XnAP message indicates that the radio bearer (i.e., SN terminated bearer) does not use UL resources of MN1. In other words, MN1 ignores the SN endpoint information (SN UL transport layer information) indicated by the first IE. Thus, MN1 may not use the SN endpoint information. MN1 may discard the SN endpoint information. MN1 may omit (skip) preparation or configuration for delivery of UL PDUs addressed to the SN endpoint.
[0057] In some implementations, the first IE may be an SN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE (or a DRBs to Be Modified Item IE) associated with the radio bearer (i.e., SN terminated bearer). Alternatively, the first IE may be an UP Transport Layer Information IE included in the SN UL PDCP UP TNL Information IE.
[0058] Meanwhile, the second IE may be a UL Configuration IE included in the DRBs to Be Setup Item IE (or the DRBs to Be Modified Item IE). This UL Configuration IE indicates how the UE 3 uses the uplink of the corresponding RAN node (i.e., MN1) for the radio bearer (i.e., SN terminated bearer). More specifically, the UL Configuration IE can be set to the value "no data", the value "shared", or the value "only". The value "no data" means that the UE 3 does not use the uplink of the corresponding node (i.e., MN1) for the radio bearer (i.e., SN terminated bearer). The value "shared" means that the UE 3 uses both the uplink of the corresponding node (i.e., MN1) and the uplink of the other node (i.e., SN2) for the radio bearer (i.e., SN terminated bearer). The value "only" means that the UE3 will only use the uplink of the corresponding node (ie, MN1) for the radio bearer (ie, SN terminated bearer).
[0059] An example of the operation of SN2 is shown in Figure 8. In step 801, SN2 receives an XnAP message from MN1 indicating the setup or modification of a radio bearer terminated in MN1 (MN terminated bearer). The XnAP message may request SN2 to add (or setup) or modify resources of SN2 for the MN terminated bearer. The XnAP message may request SN2 to prepare resources of SN2 for the MN terminated bearer or to prepare modifications of said resources. The XnAP message may be an SN ADDITION REQUEST message or an SN MODIFICATION REQUEST message. In step 802, SN2 ignores a first IE included in the XnAP message for the MN endpoint of the Xn-U tunnel used for delivery of UL PDUs if a second IE in the XnAP message indicates that the radio bearer (i.e., MN terminated bearer) does not use UL resources of SN2. In other words, the SN2 ignores the MN endpoint information (MN UL transport layer information) indicated by the first IE. Thus, the SN2 may not use the MN endpoint information. The SN2 may discard the MN endpoint information. The SN2 may skip preparing or setting up the delivery of UL PDUs addressed to the MN endpoint.
[0060] In some implementations, the first IE may be an MN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE (or a DRBs to Be Modified Item IE) associated with the radio bearer (i.e., MN terminated bearer). Alternatively, the first IE may be an UP Transport Layer Information IE included in the MN UL PDCP UP TNL Information IE.
[0061] Meanwhile, the second IE may be a UL Configuration IE included in the DRBs to Be Setup Item IE (or the DRBs to Be Modified Item IE). This UL Configuration IE indicates how the UE 3 uses the uplink of the corresponding RAN node (i.e., SN2) for the radio bearer (i.e., MN terminated bearer). More specifically, the UL Configuration IE can be set to the value "no data", the value "shared", or the value "only". The value "no data" means that the UE 3 does not use the uplink of the corresponding node (i.e., SN2) for the radio bearer (i.e., MN terminated bearer). The value "shared" means that the UE 3 uses both the uplink of the corresponding node (i.e., SN2) and the uplink of the other node (i.e., MN1) for the radio bearer (i.e., MN terminated bearer). The value "only" means that the UE 3 will only use the uplink of the corresponding node (ie, SN2) for this radio bearer (ie, MN terminated bearer).
[0062] In the following, a specific example of the operations of MN1 and SN2 described using Figures 7 and 8 will be described. Signaling shown in Figure 9 relates to an SN addition procedure and an SN modification procedure. The SN addition procedure is an S-NG-RAN node Addition Preparation procedure. The SN modification procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure.
[0063] In step 901, the MN1 sends an S-NODE ADDITION REQUEST message to the SN2. 3 The S-NODE ADDITION REQUEST message indicates to the SN2 the setup of the MN terminated bearer for the PDU Session. In other words, the S-NODE ADDITION REQUEST message requests the SN2 to add or set up SN resources for the MN terminated bearer. More specifically, the S-NODE ADDITION REQUEST message contains a PDU Session Resources To Be Added Item IE for the PDU Session. The PDU Session Resources To Be Added Item IE contains a PDU Session Resource Setup Info - MN terminated IE. The PDU Session Resource Setup Info - MN terminated IE contains a DRBs to Be Setup Item IE for the MN terminated bearer. The DRBs to Be Setup Item IE contains a MN UL PDCP UP TNL Information IE which contains a Cell Group ID IE and further contains a UL Configuration IE. In the example of FIG. 9, the UL Configuration IE is set to the value "no data", which indicates that the uplink of SN2 is not used for the MN terminated bearer.
[0064] In step 901, the MN1 may send an S-NODE MODIFICATION REQUEST message to the SN2. The S-NODE MODIFICATION REQUEST message is 3The S-NODE MODIFICATION REQUEST message indicates to the SN2 the setup or modification of the MN terminated bearer for the PDU Session. In other words, the S-NODE MODIFICATION REQUEST message requests the SN2 to add (or set up) or modify SN resources for the MN terminated bearer. More specifically, the S-NODE MODIFICATION REQUEST message may contain a PDU Session Resources To Be Added Item IE for the setup of the PDU Session. The PDU Session Resources To Be Added Item IE contains a PDU Session Resource Setup Info - MN terminated IE. Alternatively, the S-NODE MODIFICATION REQUEST message may contain a PDU Session Resources To Be Modified Item IE for the modification of the PDU Session. The PDU Session Resources To Be Modified Item IE contains a PDU Session Resource Modification Info - MN terminated IE. The PDU Session Resource Setup Info - MN terminated IE (or PDU Session Resource Modification Info - MN terminated IE) contains a DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) for the MN terminated bearer. The DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) contains a MN UL PDCP UP TNL Information IE that contains a Cell Group ID IE, and further contains a UL Configuration IE.In the example of FIG. 9, the UL Configuration IE is set to the value "no data", which indicates that the uplink of SN2 is not used for the MN terminated bearer.
[0065] In step 902, SN2 notices that the UL Configuration IE in the DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) for the requested MN terminated bearer is set to the value "no data". In response, SN2 ignores the UP transport layer information of MN1 indicated by the MN UL PDCP UP TNL Information IE in that DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE).
[0066] The signaling shown in Figure 10 is related to an SN addition procedure and an SN modification procedure. The SN addition procedure is an S-NG-RAN node Addition Preparation procedure. The SN modification procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure.
[0067] In step 1001, the SN2 sends an S-NODE ADDITION REQUEST ACKNOWLEDGE message to the MN1. The S-NODE ADDITION REQUEST ACKNOWLEDGE message is 3The S-NODE ADDITION REQUEST ACKNOWLEDGE message indicates to MN1 the setup of the SN terminated bearer for the PDU Session. In other words, the S-NODE ADDITION REQUEST ACKNOWLEDGE message requests MN1 to add or setup MN resources for the SN terminated bearer. More specifically, the S-NODE ADDITION REQUEST ACKNOWLEDGE message contains a PDU Session Resources Admitted To Be Added Item IE for the PDU Session. The PDU Session Resources Admitted To Be Added Item IE contains a PDU Session Resource Setup Response Info - SN terminated IE. The PDU Session Resource Setup Response Info - SN terminated IE contains an SN UL PDCP UP TNL Information IE which contains a Cell Group ID IE and further contains a UL Configuration IE. In the example of Fig. 10, the UL Configuration IE is set to the value "no data", indicating that the uplink of MN1 will not be used for the SN terminated bearer.
[0068] In step 1001, the SN2 may send an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the MN1. The S-NODE MODIFICATION REQUEST ACKNOWLEDGE message may be sent to the UE 3In other words, the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message requests MN1 to add or set up MN resources for the SN terminated bearer. More specifically, the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message may include a PDU Session Resources Admitted To Be Added Item IE for the setup of the PDU Session. The PDU Session Resources Admitted To Be Added Item IE includes a PDU Session Resource Setup Response Info - SN terminated IE. Alternatively, the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message may include a PDU Session Resources Admitted To Be Modified Item IE for the modification of the PDU Session. The PDU Session Resources Admitted To Be Modified Item IE contains a PDU Session Resource Modification Response Info - SN terminated IE. The PDU Session Resource Setup Response Info - SN terminated IE (or PDU Session Resource Modification Response Info - SN terminated IE) contains a DRBs to Be Setup Item IE for the SN terminated bearer. The DRBs to Be Setup Item IE contains a SN UL PDCP UP TNL Information IE which contains a Cell Group ID IE and further contains a UL Configuration IE.In the example of FIG. 10, the UL Configuration IE is set to the value "no data", which indicates that the uplink of MN1 is not used for the SN terminated bearer.
[0069] In step 1002, MN1 notices that the UL Configuration IE in the DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) for the requested SN terminated bearer is set to the value "no data". In response, MN1 ignores the UP transport layer information of SN2 indicated by the SN UL PDCP UP TNL Information IE in that DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE).
[0070] The signaling shown in Figure 11 is related to an SN modification procedure, which is an S-NG-RAN node initiated S-NG-RAN node Modification procedure.
[0071] In step 1101, the SN2 sends an S-NODE MODIFICATION REQUIRED message to the MN1. 3The S-NODE MODIFICATION REQUIRED message indicates to MN1 the setup or modification of the SN terminated bearer for the PDU Session. In other words, the S-NODE MODIFICATION REQUIRED message requests MN1 to add (or set up) or modify MN resources for the SN terminated bearer. More specifically, the S-NODE MODIFICATION REQUIRED message may contain a PDU Session Resources To Be Modified Item IE for the modification of the PDU Session. The PDU Session Resources To Be Modified Item IE contains a PDU Session Resource Modification Required Info - SN terminated IE. The PDU Session Resource Modification Required Info - SN terminated IE contains a DRBs to Be Setup Item IE (or a DRBs to Be Modified Item IE) for the SN terminated bearer. The DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) includes an SN UL PDCP UP TNL Information IE that includes a Cell Group ID IE, and further includes a UL Configuration IE. In the example of Fig. 11, the UL Configuration IE is set to the value "no data", which indicates that the uplink of MN1 is not used for the SN terminated bearer.
[0072] In step 1102, MN1 notices that the UL Configuration IE in the DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) for the requested SN terminated bearer is set to the value "no data". In response, MN1 ignores the UP transport layer information of SN2 indicated by the SN UL PDCP UP TNL Information IE in that DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE).
[0073] According to the operation of the MN1 described in this embodiment, the MN1 detects that the UL Configuration IE received from the SN2 for the setup or modification of MN resources for the SN terminated bearer is set to the value "no data" (i.e., MN1 SN2 ignores the information about SN endpoints received for the SN terminated bearer if the UL of the SN2 is not used for the SN terminated bearer. This ensures that MN1 is not affected by inconsistencies between the Cell Group ID IE and the UL Configuration IE received from SN2 for setup or modification of MN resources for the SN terminated bearer. Similarly, according to the operation of SN2 described in this embodiment, SN2 ignores the information about SN endpoints received for the SN terminated bearer if the UL Configuration IE received from MN1 for setup or modification of SN resources for the MN terminated bearer is set to the value "no data" (i.e. SN2If the UL in the MN 1 is not used for the MN terminated bearer, then SN2 ignores the information about the MN endpoints received for the MN terminated bearer. This ensures that SN2 is not affected by inconsistencies between the Cell Group ID IE and the UL Configuration IE received from MN1 for the setup or modification of SN resources for the MN terminated bearer.
[0074] <Third embodiment> A configuration example of a wireless communication network according to this embodiment is similar to the example shown in Fig. 1. This embodiment provides another example of the operation of the MN1 and the SN2.
[0075] FIG. 12 shows an example of the operation of MN1. In step 1201, MN1 includes a first IE related to a radio bearer terminated in MN1 in an XnAP message transmitted to SN2. The XnAP message may be an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message. In step 1202, MN1 includes a second IE in the XnAP message indicating how UE3 uses the uplink of SN2 for the radio bearer, on the condition that the first IE indicates that the radio bearer uses both MCG resources and SCG resources. In other words, the second IE is a conditional IE that is included in the XnAP message if a predetermined condition related to the first IE is satisfied. In step 1203, MN1 transmits the XnAP message to SN2.
[0076] In some implementations, the first IE may be a Cell Group ID IE included in an MN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) associated with the radio bearer (i.e., MN terminated bearer). The Cell Group ID IE may be set to only the value "0" meaning MCG, or only the value "1" meaning SCG, or both the value "0" and the value "1". If the Cell Group ID IE is set to both the value "0" and the value "1", this may indicate that the radio bearer (i.e., MN terminated bearer) uses both MCG resources and SCG resources.
[0077] Alternatively, the first IE may be an IE different from the Cell Group ID IE mentioned above. For example, the first IE may be a new IE indicating whether the radio bearer (i.e., MN terminated bearer) is an MCG bearer, a split bearer, or an SCG bearer. For example, the new IE may be set to the value "MCG bearer", "split bearer", or "SCG bearer". The name of the new IE may be, for example, but is not limited to, a Selected Bearer Type IE.
[0078] Meanwhile, the second IE may be a UL Configuration IE included in the DRBs to Be Setup Item IE (or the DRBs to Be Modified Item IE). This UL Configuration IE indicates how the UE 3 uses the uplink of the corresponding RAN node (i.e., SN2) for the radio bearer (i.e., MN terminated bearer). More specifically, the UL Configuration IE can be set to the value "no data", the value "shared", or the value "only". The value "no data" means that the UE 3 does not use the uplink of the corresponding node (i.e., SN2) for the radio bearer (i.e., MN terminated bearer). The value "shared" means that the UE 3 uses both the uplink of the corresponding node (i.e., SN2) and the uplink of the other node (i.e., MN1) for the radio bearer (i.e., MN terminated bearer). The value "only" means that the UE 3 will only use the uplink of the corresponding node (ie, SN2) for this radio bearer (ie, MN terminated bearer).
[0079] FIG. 13 shows an example of the operation of the SN2. In step 1301, the SN2 includes a first IE related to a radio bearer terminated in the SN2 in an XnAP message transmitted to the MN1. The XnAP message may be an S-NODE ADDITION REQUEST ACKNOWLEDGE message, an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, or an S-NODE MODIFICATION REQUIRED message. In step 1302, the SN2 includes a second IE in the XnAP message indicating how the UE3 uses the uplink of the MN1 for the radio bearer, on the condition that the first IE indicates that the radio bearer uses both the resources of the MCG and the resources of the SCG. In other words, the second IE is a conditional IE to be included in the XnAP message if a predetermined condition related to the first IE is satisfied. In step 1303, the SN2 includes the XnAP message in the XnAP message indicating how the UE3 uses the uplink of the MN1 for the radio bearer. MN1 Send to.
[0080] In some implementations, the first IE may be a Cell Group ID IE included in an SN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE (or DRBs to Be Modified Item IE) associated with the radio bearer (i.e., SN terminated bearer). The Cell Group ID IE may be set to only the value "0" meaning MCG, or only the value "1" meaning SCG, or both the value "0" and the value "1". If the Cell Group ID IE is set to both the value "0" and the value "1", this may indicate that the radio bearer (i.e., SN terminated bearer) uses both MCG resources and SCG resources.
[0081] Alternatively, the first IE may be an IE different from the Cell Group ID IE mentioned above. For example, the first IE may be a new IE indicating whether the radio bearer (i.e., SN terminated bearer) is an MCG bearer, a split bearer, or an SCG bearer. For example, the new IE may be set to the value "MCG bearer", "split bearer", or "SCG bearer". The name of the new IE may be, for example, but not limited to, a Selected Bearer Type IE.
[0082] Meanwhile, the second IE may be a UL Configuration IE included in the DRBs to Be Setup Item IE (or the DRBs to Be Modified Item IE). This UL Configuration IE indicates how the UE 3 uses the uplink of the corresponding RAN node (i.e., MN1) for the radio bearer (i.e., SN terminated bearer). More specifically, the UL Configuration IE can be set to the value "no data", the value "shared", or the value "only". The value "no data" means that the UE 3 does not use the uplink of the corresponding node (i.e., MN1) for the radio bearer (i.e., SN terminated bearer). The value "shared" means that the UE 3 uses both the uplink of the corresponding node (i.e., MN1) and the uplink of the other node (i.e., SN2) for the radio bearer (i.e., SN terminated bearer). The value "only" means that the UE3 will only use the uplink of the corresponding node (ie, MN1) for the radio bearer (ie, SN terminated bearer).
[0083] According to the operation of MN1 described in this embodiment, on condition that the first IE indicates that the MN terminated bearer uses both MCG resources and SCG resources, the UE3 includes in the XnAP message a second IE indicating how the UE3 uses the SN2's uplink for the MN terminated bearer. This allows the MN1 to prevent a contradiction from occurring between the first IE and the second IE. Similarly, according to the operation of SN2 described in this embodiment, the SN2 includes in the XnAP message a second IE indicating how the UE3 uses the MN1's uplink for the SN terminated bearer, on condition that the first IE indicates that the SN terminated bearer uses both MCG resources and SCG resources. This allows the SN2 to prevent a contradiction from occurring between the first IE and the second IE.
[0084] Next, configuration examples of MN1 and SN2 according to the above-mentioned embodiments will be described below. FIG. 14 is a block diagram showing a configuration example of MN1 according to the above-mentioned embodiments. The configuration of SN2 may also be similar to the configuration shown in FIG. 14. Referring to FIG. 14, 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 UE3. The RF transceiver 1401 may include multiple transceivers. The RF transceiver 1401 is coupled to an antenna array 1402 and a 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 reception signal based on the reception RF signal received by the antenna array 1402, and provides the baseband reception signal to the processor 1404. The RF transceiver 1401 may include an analog beamformer circuit for beamforming, which may include, for example, multiple phase shifters and multiple power amplifiers.
[0085] The network interface 1403 is used to communicate with network nodes (eg, MN1, and control nodes 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.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] In addition, when the MN1 (SN2) is a CU (eg, eNB-CU or gNB-CU) or a CU-CP, the MN1 (SN2) does not need to include the RF transceiver 1401 (and the antenna array 1402).
[0090] As described with reference to FIG. 14, each of the processors included in MN1 and SN2 according to the above-described embodiment executes one or more programs including instructions for making a computer execute the algorithm described with reference to the drawings. The programs can be stored and provided to a computer using various types of non-transitory computer readable media. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, programmable ROM (PROM), erasable PROM (EPROM), flash ROM, random access memory (RAM)). The programs may also be provided to a computer by various types of transitory computer readable media. Examples of the transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire or an optical fiber, or via a wireless communication path.
[0091] The above-described embodiments are merely examples of application of the technical ideas obtained by the inventors of the present invention. In other words, the technical ideas are not limited to the above-described embodiments, and various modifications can be made to these.
[0092] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes.
[0093] (Appendix 1) A first Radio Access Network (RAN) node, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: In a control procedure for dual connectivity for User Equipment (UE), receiving a first message from a second RAN node indicating setup or modification of a radio bearer terminated at the second RAN node; rejecting the setup or the modification of the radio bearer if a first information element (IE) in the first message indicates that the radio bearer uses only resources of a cell group of the first RAN node and a second IE in the first message indicates that the UE does not use an uplink of the first RAN node for the radio bearer. It is configured as follows: The first RAN node. (Appendix 2) the first IE is a Cell Group ID IE included in an MN UL PDCP UP TNL Information IE or an SN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE or a DRBs to Be Modified Item IE associated with the radio bearer; The second IE is a UL Configuration IE included in the DRBs to Be Setup Item IE or the DRBs to Be Modified Item IE, 2. The first RAN node according to claim 1. (Appendix 3) the first RAN node is a secondary node (SN) of the dual connectivity; the second RAN node is a master node (MN) of the dual connectivity; The radio bearer is a MN terminated bearer, The control procedure is an S-NG-RAN node addition preparation procedure, the first message is an S-NODE ADDITION REQUEST message containing a PDU Session Resources To Be Added Item IE containing a PDU Session Resource Setup Info - MN terminated information element (IE); The at least one processor is configured to reject the setup of the radio bearer if the UL Configuration IE in the DRBs to Be Setup Item IE included in the PDU Session Resource Setup Info - MN terminated IE is set to a value "no data" and the Cell Group ID IE included in the MN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set to only a value "1" indicating a Secondary Cell Group (SCG). 2. The first RAN node according to claim 1 . (Appendix 4) Rejecting the setup of the radio bearer includes rejecting the S-NG-RAN node addition preparation procedure by sending an S-NODE ADDITION REQUEST REJECT message to the MN. 4. The first RAN node according to claim 3. (Appendix 5) rejecting the setup of the radio bearer comprises sending an S-NODE ADDITION REQUEST ACKNOWLEDGE message to the MN containing a PDU Session Resource Setup Response Info - MN terminated IE, indicating that the setup of the radio bearer is not allowed. 4. The first RAN node according to claim 3. (Appendix 6) the first RAN node is a secondary node (SN) of the dual connectivity; the second RAN node is a master node (MN) of the dual connectivity; The radio bearer is a MN terminated bearer, the control procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure, the first message is an S-NODE MODIFICATION REQUEST message containing a PDU Session Resources To Be Added Item IE containing a PDU Session Resource Setup Info - MN terminated information element (IE); The at least one processor is configured to reject the setup of the radio bearer if the UL Configuration IE in the DRBs to Be Setup Item IE included in the PDU Session Resource Setup Info - MN terminated IE is set to a value "no data" and the Cell Group ID IE included in the MN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set to only a value "1" indicating a Secondary Cell Group (SCG). 2. The first RAN node according to claim 1 . (Appendix 7) Rejecting the setup of the radio bearer includes rejecting the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure by sending an S-NODE MODIFICATION REQUEST REJECT message to the MN. 7. The first RAN node according to claim 6. (Appendix 8) rejecting the setup of the radio bearer comprises sending an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the MN containing a PDU Session Resource Setup Response Info - MN terminated IE, indicating that the setup of the radio bearer is not allowed. 7. The first RAN node according to claim 6. (Appendix 9) the first RAN node is a secondary node (SN) of the dual connectivity; the second RAN node is a master node (MN) of the dual connectivity; The radio bearer is a MN terminated bearer, the control procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure, the first message is an S-NODE MODIFICATION REQUEST message containing a PDU Session Resources To Be Modified Item IE containing a PDU Session Resource Modification Info - MN terminated information element (IE); The at least one processor is configured to reject the setup of the radio bearer if the UL Configuration IE in the DRBs to Be Setup Item IE included in the PDU Session Resource Modification Info - MN terminated IE is set to a value "no data" and the Cell Group ID IE included in the MN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set to only a value "1" indicating a Secondary Cell Group (SCG). 2. The first RAN node according to claim 1 . (Appendix 10) Rejecting the setup of the radio bearer includes rejecting the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure by sending an S-NODE MODIFICATION REQUEST REJECT message to the MN. 10. The first RAN node of claim 9. (Appendix 11) rejecting the setup of the radio bearer comprises sending an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the MN, the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message including a PDU Session Resource Modification Response Info - MN terminated IE indicating that the setup of the radio bearer is not allowed. 10. The first RAN node of claim 9. (Appendix 12) the first RAN node is a secondary node (SN) of the dual connectivity; the second RAN node is a master node (MN) of the dual connectivity; The radio bearer is a MN terminated bearer, the control procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure, the first message is an S-NODE MODIFICATION REQUEST message containing a PDU Session Resources To Be Modified Item IE containing a PDU Session Resource Modification Info - MN terminated information element (IE); The at least one processor is configured to reject the modification of the radio bearer if the UL Configuration IE in the DRBs to Be Modified Item IE included in the PDU Session Resource Modification Info - MN terminated IE is set to a value "no data" and the Cell Group ID IE in the MN UL PDCP UP TNL Information IE in the DRBs to Be Modified Item IE is set to only a value "1" indicating a Secondary Cell Group (SCG). 2. The first RAN node according to claim 1 . (Appendix 13) Rejecting the modification of the radio bearer includes rejecting the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure by sending an S-NODE MODIFICATION REQUEST REJECT message to the MN. 13. The first RAN node of claim 12. (Appendix 14) rejecting the modification of the radio bearer comprises sending an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the MN containing a PDU Session Resource Modification Response Info - MN terminated IE indicating that the modification of the radio bearer is not allowed. 14. The first RAN node of claim 13. (Appendix 15) the first RAN node is a master node (MN) of the dual connectivity; the second RAN node is a secondary node (SN) of the dual connectivity; The radio bearer is an SN terminated bearer, The control procedure is an S-NG-RAN node addition preparation procedure, the first message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message containing a PDU Session Resources Admitted To Be Added Item IE containing a PDU Session Resource Setup Response Info - SN terminated information element (IE); The at least one processor is configured to reject the setup of the radio bearer if the UL Configuration IE in the DRBs to Be Setup Item IE included in the PDU Session Resource Setup Response Info - SN terminated IE is set to a value "no data" and the Cell Group ID IE included in the SN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set to only a value "0" indicating a Master Cell Group (MCG). 2. The first RAN node according to claim 1 . (Appendix 16) Rejecting the setup of the radio bearer includes initiating an M-NG-RAN node initiated S-NG-RAN node Release procedure. 16. The first RAN node of claim 15. (Appendix 17) rejecting the setup of the radio bearer includes initiating an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure to release the radio bearer. 16. The first RAN node of claim 15. (Appendix 18) the first RAN node is a master node (MN) of the dual connectivity; the second RAN node is a secondary node (SN) of the dual connectivity; The radio bearer is an SN terminated bearer, the control procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure, the first message is an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message containing a PDU Session Resources Admitted To Be Added Item IE containing a PDU Session Resource Setup Response Info - SN terminated information element (IE); The at least one processor is configured to reject the setup of the radio bearer if the UL Configuration IE in the DRBs to Be Setup Item IE included in the PDU Session Resource Setup Response Info - SN terminated IE is set to a value "no data" and the Cell Group ID IE included in the SN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set to only a value "0" indicating a Master Cell Group (MCG). 2. The first RAN node according to claim 1 . (Appendix 19) Rejecting the setup of the radio bearer includes initiating an M-NG-RAN node initiated S-NG-RAN node Release procedure. 19. The first RAN node of claim 18. (Appendix 20) rejecting the setup of the radio bearer includes initiating an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure to release the radio bearer. 19. The first RAN node of claim 18. (Appendix 21) the first RAN node is a master node (MN) of the dual connectivity; the second RAN node is a secondary node (SN) of the dual connectivity; The radio bearer is an SN terminated bearer, the control procedure is an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure, the first message is an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message containing a PDU Session Resources Admitted To Be Modified Item IE containing a PDU Session Resource Modification Response Info - SN terminated information element (IE); The at least one processor is configured to reject the setup of the radio bearer if the UL Configuration IE in the DRBs to Be Setup Item IE included in the PDU Session Resource Modification Response Info - SN terminated IE is set to a value "no data" and the Cell Group ID IE included in the SN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set to only a value "0" indicating a Master Cell Group (MCG). 2. The first RAN node according to claim 1 . (Appendix 22) Rejecting the setup of the radio bearer includes initiating an M-NG-RAN node initiated S-NG-RAN node Release procedure. 22. The first RAN node of claim 21. (Appendix 23) rejecting the setup of the radio bearer includes initiating an M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure to release the radio bearer. 22. The first RAN node of claim 21. (Appendix 24) the first RAN node is a master node (MN) of the dual connectivity; the second RAN node is a secondary node (SN) of the dual connectivity; The radio bearer is an SN terminated bearer, the control procedure is an S-NG-RAN node initiated S-NG-RAN node Modification procedure, the first message is an S-NODE MODIFICATION REQUIRED message containing a PDU Session Resources To Be Modified Item IE containing a PDU Session Resource Modification Required Info - SN terminated information element (IE); The at least one processor is configured to reject the setup of the radio bearer if the UL Configuration IE in the DRBs to Be Setup Item IE included in the PDU Session Resource Modification Required Info - SN terminated IE is set to a value "no data" and the Cell Group ID IE included in the SN UL PDCP UP TNL Information IE in the DRBs to Be Setup Item IE is set to only a value "0" indicating a Master Cell Group (MCG). 2. The first RAN node according to claim 1 . (Appendix 25) Rejecting the setup of the radio bearer includes rejecting the S-NG-RAN node initiated S-NG-RAN node Modification procedure. 25. The first RAN node of claim 24. (Appendix 26) Rejecting the setup of the radio bearer comprises sending an S-NODE MODIFICATION CONFIRM message to the SN containing a PDU Session Resource Modification Confirm Info - SN terminated IE, indicating that the setup of the radio bearer is not allowed. 25. The first RAN node of claim 24. (Appendix 27) the first RAN node is a master node (MN) of the dual connectivity; the second RAN node is a secondary node (SN) of the dual connectivity; The radio bearer is an SN terminated bearer, the control procedure is an S-NG-RAN node initiated S-NG-RAN node Modification procedure, the first message is an S-NODE MODIFICATION REQUIRED message containing a PDU Session Resources To Be Modified Item IE containing a PDU Session Resource Modification Required Info - SN terminated information element (IE); The at least one processor is configured to reject the modification of the radio bearer if the UL Configuration IE in the DRBs to Be Modified Item IE included in the PDU Session Resource Modification Required Info - SN terminated IE is set to a value "no data" and the Cell Group ID IE in the SN UL PDCP UP TNL Information IE in the DRBs to Be Modified Item IE is set to only a value "0" indicating a Master Cell Group (MCG). 2. The first RAN node according to claim 1 . (Appendix 28) Rejecting the modification of the radio bearer includes rejecting the S-NG-RAN node initiated S-NG-RAN node Modification procedure. 28. The first RAN node of claim 27. (Appendix 29) rejecting the modification of the radio bearer comprises sending an S-NODE MODIFICATION CONFIRM message to the SN containing a PDU Session Resource Modification Confirm Info - SN terminated IE, indicating that the modification of the radio bearer is not allowed. 28. The first RAN node of claim 27. (Appendix 30) 1. A method performed by a first Radio Access Network (RAN) node, comprising: receiving a first message from a second RAN node indicating a setup or modification of a radio bearer terminated at the second RAN node in a control procedure for dual connectivity for a User Equipment (UE); rejecting the setup or the modification of the radio bearer if a first information element (IE) in the first message indicates that the radio bearer uses only resources of a cell group of the first RAN node and a second IE in the first message indicates that the UE does not use an uplink of the first RAN node for the radio bearer; A method for providing the above. (Appendix 31) 1. A program for causing a computer to perform a method for a first Radio Access Network (RAN) node, the method comprising: receiving a first message from a second RAN node indicating a setup or modification of a radio bearer terminated at the second RAN node in a control procedure for dual connectivity for a User Equipment (UE); rejecting the setup or the modification of the radio bearer if a first information item (IE) in the first message indicates that the radio bearer uses only resources of a cell group of the first RAN node and a second IE in the first message indicates that the UE does not use an uplink of the first RAN node for the radio bearer; A program that includes: (Appendix 32) A first Radio Access Network (RAN) node, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: In a control procedure for dual connectivity for User Equipment (UE), receiving a first message from a second RAN node indicating setup or modification of a radio bearer terminated at the second RAN node; if a second information element (IE) in the first message indicates that the UE will not use an uplink of the first RAN node for the radio bearer, then ignore a first information element (IE) included in the first message regarding the second RAN node endpoint of an inter-RAN node tunnel used for delivery of uplink Protocol Data Units (PDUs); It is configured as follows: The first RAN node. (Appendix 33) the first IE is a UP Transport Layer Information IE included in an MN UL PDCP UP TNL Information IE or an SN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE or a DRBs to Be Modified Item IE associated with the radio bearer; The second IE is a UL Configuration IE included in the DRBs to Be Setup Item IE or the DRBs to Be Modified Item IE, 33. The first RAN node of claim 32. (Appendix 34) 1. A method performed by a first Radio Access Network (RAN) node, comprising: receiving a first message from a second RAN node indicating a setup or modification of a radio bearer terminated at the second RAN node in a control procedure for dual connectivity for a User Equipment (UE); ignoring a first information element (IE) included in the first message relating to an endpoint of the second RAN node of an inter-RAN node tunnel used for delivery of uplink Protocol Data Units (PDUs) included in the first message if a second information element (IE) in the first message indicates that the UE will not use an uplink of the first RAN node for the radio bearer; A method for providing the above. (Appendix 35) 1. A program for causing a computer to perform a method for a first Radio Access Network (RAN) node, the method comprising: receiving a first message from a second RAN node indicating a setup or modification of a radio bearer terminated at the second RAN node in a control procedure for dual connectivity for a User Equipment (UE); ignoring a first information element (IE) included in the first message relating to an endpoint of the second RAN node of an inter-RAN node tunnel used for delivery of uplink Protocol Data Units (PDUs), if a second information element (IE) in the first message indicates that the UE will not use an uplink of the first RAN node for the radio bearer; A program that includes: (Appendix 36) A Radio Access Network (RAN) node configured to operate as a dual connectivity Master Node (MN) for a User Equipment (UE), comprising: At least one memory; at least one processor coupled to the at least one memory; Equipped with A first message transmitted to a secondary node (SN) of the dual connectivity includes a first information element (IE) related to a radio bearer terminated at the MN; including in the first message a second IE indicating how the UE uses an uplink of the SN for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of a master cell group (MCG) of the MN and resources of a secondary cell group (SCG) of the SN; sending the first message to the SN; It is configured as RAN node. (Appendix 37) The first message is an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message; 36. The RAN node according to claim 36. (Appendix 38) The first IE is a Cell Group ID IE included in an MN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE or a DRBs to Be Modified Item IE associated with the radio bearer, The second IE is a UL Configuration IE included in the DRBs to Be Setup Item IE or the DRBs to Be Modified Item IE, 38. The RAN node of claim 36 or 37. (Appendix 39) When the value "0" indicating the MCG and the value "1" indicating the previous SCG are both set in the Cell Group ID IE, the Cell Group ID IE indicates that the radio bearer uses both the resources of the master cell group (MCG) of the MN and the resources of the secondary cell group (SCG) of the SN. 38. The RAN node of claim 38. (Appendix 40) 1. A Radio Access Network (RAN) node configured to operate as a secondary node (SN) 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 A first message transmitted to a master node (MN) of the dual connectivity includes a first information element (IE) related to a radio bearer terminated at the SN; including in the first message a second IE indicating how the UE uses the MN's uplink for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of the MN's Master Cell Group (MCG) and resources of the SN's Secondary Cell Group (SCG); Sending the first message to the MN; It is configured as RAN node. (Appendix 41) the first message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message, an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, or an S-NODE MODIFICATION REQUIRED message; 40. The RAN node of claim 40. (Appendix 42) The first IE is a Cell Group ID IE included in a SN UL PDCP UP TNL Information IE included in a DRBs to Be Setup Item IE or a DRBs to Be Modified Item IE associated with the radio bearer; The second IE is a UL Configuration IE included in the DRBs to Be Setup Item IE or the DRBs to Be Modified Item IE, 42. The RAN node of claim 40 or 41. (Appendix 43) When the value "0" indicating the MCG and the value "1" indicating the previous SCG are both set in the Cell Group ID IE, the Cell Group ID IE indicates that the radio bearer uses both the resources of the master cell group (MCG) of the MN and the resources of the secondary cell group (SCG) of the SN. 42. The RAN node of claim 42. (Appendix 44) 1. A method performed by a Radio Access Network (RAN) node configured to operate as a dual connectivity Master Node (MN) for a User Equipment (UE), comprising: including a first information element (IE) related to a radio bearer terminated at the MN in a first message transmitted to a secondary node (SN) of the dual connectivity; including in the first message a second IE indicating how the UE uses the uplink of the SN for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of a Master Cell Group (MCG) of the MN and resources of a Secondary Cell Group (SCG) of the SN; and sending the first message to the SN; A method for providing the above. (Appendix 45) 1. A method performed by a Radio Access Network (RAN) node configured to operate as a secondary node (SN) in dual connectivity for a User Equipment (UE), comprising: including in a first message transmitted to a dual connectivity master node (MN) a first information element (IE) related to a radio bearer terminated at the SN; including in the first message a second IE indicating how the UE uses the MN's uplink for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of the MN's Master Cell Group (MCG) and resources of the SN's Secondary Cell Group (SCG); and sending the first message to the MN; A method for providing the above. (Appendix 46) 1. 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) of dual connectivity for User Equipment (UE), the method comprising: including a first information element (IE) related to a radio bearer terminated at the MN in a first message transmitted to a secondary node (SN) of the dual connectivity; including in the first message a second IE indicating how the UE uses the uplink of the SN for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of a Master Cell Group (MCG) of the MN and resources of a Secondary Cell Group (SCG) of the SN; and sending the first message to the SN; A program that includes: (Appendix 47) 1. A program for causing a computer to perform a method for a Radio Access Network (RAN) node configured to operate as a secondary node (SN) in dual connectivity for User Equipment (UE), the method comprising: including in a first message transmitted to a dual connectivity master node (MN) a first information element (IE) related to a radio bearer terminated at the SN; including in the first message a second IE indicating how the UE uses the MN's uplink for the radio bearer, provided that the first IE indicates that the radio bearer uses both resources of the MN's Master Cell Group (MCG) and resources of the SN's Secondary Cell Group (SCG); and sending the first message to the MN; A program that includes:
[0094] (Appendix A1) A method for a secondary base station in Dual Connectivity, comprising: Receive a request message from a master base station in the dual connectivity; When the secondary base station uses an SN terminated bearer using both a Master Cell Group (MCG) resource and a Secondary Cell Group (SCG) resource, a request acknowledgement message including a UL Configuration information element (IE) is sent to the master base station in response to the request message. method. (Appendix A2) The method according to Supplementary Note A1, wherein the UL Configuration information element is an information element indicating how the terminal device uses the uplink of the secondary base station. (Appendix A3) The method according to claim 1 or 2, further comprising including in the request acknowledgement message a Cell Group ID information element indicating that the secondary base station uses the SN terminated bearer using both the resources of the Master Cell Group (MCG) and the resources of the Secondary Cell Group (SCG). (Appendix A4) 4. The method of any one of claims A1 to A3, wherein the request acknowledgement message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. (Appendix A5) 5. The method according to any one of claims A1 to A4, wherein the request message is an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message. (Appendix A6) A method for a master base station in dual connectivity, comprising: Sending a request message to a secondary base station in the dual connectivity; When the secondary base station uses an SN terminated bearer using both a Master Cell Group (MCG) resource and a Secondary Cell Group (SCG) resource, a request acknowledgement message including a UL Configuration information element (IE) is received from the secondary base station in response to the request message. method. (Appendix A7) The method according to Supplementary Note A6, wherein the UL Configuration information element is an information element indicating how the terminal device uses the uplink of the secondary base station. (Appendix A8) The method according to claim 6 or 7, further comprising including in the request acknowledgement message a Cell Group ID information element indicating that the secondary base station uses the SN terminated bearer using both the resources of the Master Cell Group (MCG) and the resources of the Secondary Cell Group (SCG). (Appendix A9) 9. The method according to any one of claims A6 to A8, wherein the request acknowledgement message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. (Appendix A10) 10. The method according to any one of claims A6 to A9, wherein the request message is an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message. (Appendix A11) A secondary base station in Dual Connectivity, comprising a receiving unit and a transmitting unit, The receiving unit receives a request message from a master base station in the dual connectivity; When the secondary base station uses an SN terminated bearer using both a Master Cell Group (MCG) resource and a Secondary Cell Group (SCG) resource, the transmission unit transmits a request acknowledgement message including a UL Configuration information element (IE) to the master base station in response to the request message. Secondary base station. (Appendix A12) The secondary base station according to Supplementary Note A11, wherein the UL Configuration information element is an information element indicating how a terminal device uses an uplink of the secondary base station. (Appendix A13) The secondary base station according to Supplementary Note A11 or A12, wherein the transmitting unit includes in the request acknowledgement message a Cell Group ID information element which means that the secondary base station uses the SN terminated bearer using both the resources of the Master Cell Group (MCG) and the resources of the Secondary Cell Group (SCG). (Appendix A14) The secondary base station according to any one of Supplementary Notes A11 to A13, wherein the request acknowledge message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. (Appendix A15) The secondary base station according to any one of Supplementary Notes A11 to A14, wherein the request message is an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message. (Appendix A16) A master base station in Dual Connectivity, comprising a transmitter and a receiver, The transmission unit transmits a request message to a secondary base station in the dual connectivity; When the secondary base station uses an SN terminated bearer using both a Master Cell Group (MCG) resource and a Secondary Cell Group (SCG) resource, the receiving unit receives a request acknowledgement message including a UL Configuration information element (IE) from the secondary base station in response to the request message. Master base station. (Appendix A17) The master base station according to Supplementary Note A16, wherein the UL Configuration information element is an information element indicating how the terminal device uses the uplink of the secondary base station. (Appendix A18) The master base station according to appendix A16 or A17, wherein the receiving unit receives the request acknowledgement message including a Cell Group ID information element which means that the secondary base station uses the SN terminated bearer using both the resources of the Master Cell Group (MCG) and the resources of the Secondary Cell Group (SCG). (Appendix A19) The master base station according to any one of appendices A16 to A18, wherein the request acknowledge message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. (Appendix A20) The master base station according to any one of Supplementary Notes A16 to A19, wherein the request message is an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message.
[0095] This application claims priority based on Japanese Patent Application No. 2020-176218, filed on October 20, 2020, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]
[0096] 1 Master Node (MN) 2 Secondary Node (SN) 3. User Equipment (UE) 1404 processor 1405 Memory 1406 Modules
Claims
1. A method for a secondary base station in Dual Connectivity, comprising: Receive a request message from a master base station in the dual connectivity; sending a request acknowledgement message to the master base station in response to the request message; Prepare for this. The request acknowledgement message further includes a UL Configuration information element (IE) indicating how the wireless terminal uses the uplink of the secondary base station for the radio bearer, provided that the request acknowledgement message includes a Cell Group ID information element indicating that the radio bearer terminated in the secondary base station uses both a Master Cell Group (MCG) resource and a Secondary Cell Group (SCG) resource. method.
2. The method according to claim 1, wherein, when a Cell Group ID information element indicating that the radio bearer terminated in the secondary base station uses only one of MCG resources and SCG resources is included in the request acknowledgement message, the UL Configuration IE is not included in the request acknowledgement message.
3. The method according to claim 1 or 2, wherein the request acknowledgement message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
4. The method according to claim 1 , wherein the request message is an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message.
5. A secondary base station in Dual Connectivity, comprising a receiving unit and a transmitting unit, The receiving unit receives a request message from a master base station in the dual connectivity; The transmitter transmits a request acknowledgement message to the master base station as a response to the request message; The request acknowledgement message further includes a UL Configuration information element (IE) indicating how the wireless terminal uses the uplink of the secondary base station for the radio bearer, provided that the request acknowledgement message includes a Cell Group ID information element indicating that the radio bearer terminated in the secondary base station uses both a Master Cell Group (MCG) resource and a Secondary Cell Group (SCG) resource. Secondary base station.
6. The secondary base station according to claim 5, wherein when a Cell Group ID information element indicating that the radio bearer terminated in the secondary base station uses only one of MCG resources and SCG resources is included in the request acknowledgement message, the UL Configuration IE is not included in the request acknowledgement message.
7. The secondary base station according to claim 5 or 6, wherein the request acknowledge message is an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
8. The secondary base station according to claim 5 , wherein the request message is an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message.
