Enabling use of per target cell CU-UP in CPA / CPC initiation

By providing data forwarding TEID for each PSCell or PSCell group in the CPA/CPC scenario, the multi-PSCell management problem in the prior art is solved, the mobility robustness of UE and the flexibility of network resources are improved, and multiple user planes are realized distribute.

CN119014121APending Publication Date: 2024-11-22NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380032598.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-25
Filing Date
2023-03-02
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The prior art is difficult to effectively prepare and manage multiple PSCells in CPA/CPC scenarios, resulting in reduced mobility and robustness of UEs. The existing standards only support a single TEID, which cannot meet the needs of multi-user plane allocation.

Method used

Multi-TEID support is achieved by providing data forwarding TEID for each prepared PSCell in the target SN or PSCell group served by the same CU-UP, allowing network nodes to receive multiple PSCell requests and dynamically allocate and associate according to network connection conditions. TEID.

Benefits of technology

It improves the mobility and robustness of UE and the flexible allocation of network resources, increases the number of prepared PSCells, meets the needs of multi-user distribution, and improves the adaptability and efficiency of the network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119014121A_ABST
    Figure CN119014121A_ABST
Patent Text Reader

Abstract

A method is described for enabling a target SN to provide a data forwarding TEID for each prepared PSCell, or for a prepared PSCell group using the same CU-UP. Options for implementing this idea are described, including where a PSCell preparation process is repeated as many as the number of groups of PSCell, where the number of groups is based on the number of CU-UPs serving the prepared PSCell, or TEID information is provided for each prepared PSCell, or for each group served by the same CU-UP.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The exemplary and non-limiting embodiments relate generally to communications, and more particularly to enabling use of per-target cell CU-UP in CPA / CPC initiation. Background Art

[0002] It is known to implement dual connectivity and handover in a communication network. Summary of the invention

[0003] According to one aspect, a method for preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity includes: receiving a first request to add at least two PSCells from a master node serving the user equipment, determining how many of the at least two PSCells can be prepared, if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services, if the common user plane can be determined, associating a first TEID related to the common user plane and used for the two PSCells, and sending a confirmation message including an indication of the two PSCells and the associated first TEID toward the master node, if the common user plane cannot be determined, determining whether a network connection toward the master node supports a confirmation message including different TEIDs, and if the network connection supports different TEIDs, If a confirmation message including a different TEID is received, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent toward the master node; and / or if the network connection does not support confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and a first confirmation message including an indication of the first PSCell and the associated first TEID is sent toward the master node, and preparation of the second PSCell is stopped, or the second TEID associated with the second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent toward the master node.

[0004] According to one aspect, an apparatus for a network node of a cellular communication network includes at least one processor; and at least one non-volatile memory including computer program code, wherein the at least one non-volatile memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least: receive a first request to add at least two PSCells for a user equipment supporting dual connectivity, determine how many of the at least two PSCells can be prepared, and if the first PSCell and the second PSCell can be prepared, determine whether the two PSCells can be associated with a common user plane for forwarding data services, and if the common user plane cannot be determined, associate a first TEID associated with the first user plane with the first PSCell, and associate a second TEID associated with the second user plane with the second PSCell, and send a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID.

[0005] According to one aspect, an apparatus for a network node of a cellular communication network includes at least one processor; and at least one non-volatile memory including computer program code, wherein the at least one non-volatile memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least: receive a first request to add at least two PSCells for a user equipment supporting dual connectivity, determine how many of the at least two PSCells can be prepared, and if the first PSCell and the second PSCell can be prepared, determine whether the two PSCells can be associated with a common user plane for forwarding data services, and if the common user plane cannot be determined, associate a first TEID associated with the first user plane with the first PSCell, and send a first confirmation message including an indication of the first PSCell and the associated first TEID toward a master node, and stop preparation of the second PSCell, or associate a second TEID associated with the second user plane with the second PSCell, and send a second confirmation message including an indication of the second PSCell and the associated second TEID toward the master node.

[0006] According to one aspect, a non-transitory program storage device readable by a machine is provided, the device tangibly embodying an instruction program executable by the machine for performing operations, the operations including: preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, receiving a first request to add at least two PSCells from a master node serving the user equipment, determining how many PSCells of the at least two PSCells can be prepared, if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services, if the common user plane can be determined, associating a first TEID related to the common user plane and for the two PSCells, and sending a confirmation message including an indication of the two PSCells and the associated first TEID towards the master node, if the common user plane cannot be determined, determining whether the network connection towards the master node supports different TEIs. D, and if the network connection supports confirmation messages including different TEIDs, the first TEID associated with the first user plane and the first PSCell are associated, and the second TEID associated with the second user plane and the second PSCell are associated, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent toward the master node; and / or if the network connection does not support confirmation messages including different TEIDs, the first TEID associated with the first user plane and the first PSCell are associated, and a first confirmation message including an indication of the first PSCell and the associated first TEID is sent toward the master node, and preparation of the second PSCell is stopped, or the second TEID associated with the second user plane and the second PSCell are associated, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent toward the master node.

[0007] According to one aspect, an apparatus includes: a component for preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, a component for receiving a first request for adding at least two PSCells from a master node serving the user equipment, a component for determining how many of the at least two PSCells can be prepared, a component for determining whether the two PSCells can be associated with a common user plane for forwarding data services when a first PSCell and a second PSCell can be prepared, a component for associating a first TEID related to the common user plane and for the two PSCells and sending a confirmation message including an indication of the two PSCells and the associated first TEID toward the master node when the common user plane can be determined, a component for determining whether a network connection toward the master node supports a confirmation message including different TEIDs when the common user plane cannot be determined, and and if the network connection supports confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent toward the master node; and / or if the network connection does not support confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and a first confirmation message including an indication of the first PSCell and the associated first TEID is sent toward the master node, and preparation of the second PSCell is stopped, or the second TEID associated with the second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent toward the master node.

[0008] According to one aspect, an apparatus includes: at least one processor; and at least one non-volatile memory including computer program code, wherein the at least one non-volatile memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least: prepare at least one PSCell of a wireless network for a user equipment supporting dual connectivity, receive a first request to add at least two PSCells from a master node serving the user equipment, determine how many PSCells of the at least two PSCells can be prepared, if the first PSCell and the second PSCell can be prepared, determine whether the two PSCells can be associated with a common user plane for forwarding data services, if the common user plane can be determined, associate a first TEID related to the common user plane and used for the two PSCells, and send a confirmation message including an indication of the two PSCells and the associated first TEID toward the master node, if the common user plane cannot be determined, determine the network connection toward the master node. whether the network connection supports confirmation messages including different TEIDs, and if the network connection supports confirmation messages including different TEIDs, the first TEID related to the first user plane is associated with the first PSCell, and the second TEID related to the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent toward the master node; and / or if the network connection does not support confirmation messages including different TEIDs, the first TEID related to the first user plane is associated with the first PSCell, and a first confirmation message including an indication of the first PSCell and the associated first TEID is sent toward the master node, and preparation of the second PSCell is stopped, or the second TEID related to the second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent toward the master node.

[0009] According to one aspect, a method for a network node of a cellular communication network includes: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many of the at least two PSCells can be prepared, if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services, and if the common user plane cannot be determined, associating a first TEID associated with the first user plane with the first PSCell, and associating a second TEID associated with the second user plane with the second PSCell, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID.

[0010] According to one aspect, a non-volatile program storage device readable by a machine is provided, which tangibly embodies an instruction program executable by the machine for performing operations on a network node of a cellular communication network, the operations comprising: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many of the at least two PSCells can be prepared, if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services, and if the common user plane cannot be determined, associating a first TEID associated with the first user plane with the first PSCell, and associating a second TEID associated with the second user plane with the second PSCell, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID.

[0011] According to one aspect, an apparatus for a network node of a cellular communication network includes: a component for receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, a component for determining how many of the at least two PSCells can be prepared, a component for determining whether the first PSCell and the second PSCell can be associated with a common user plane for forwarding data services if the two PSCells can be prepared, and a component for associating a first TEID associated with the first user plane with the first PSCell and associating a second TEID associated with the second user plane with the second PSCell if the common user plane cannot be determined, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID.

[0012] According to one aspect, a method for a network node of a cellular communication network includes: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many of the at least two PSCells can be prepared, and if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services, and if the common user plane cannot be determined, associating a first TEID related to the first user plane with the first PSCell, and sending a first confirmation message including an indication of the first PSCell and the associated first TEID toward a master node, and stopping preparation of the second PSCell, or associating a second TEID related to the second user plane with the second PSCell, and sending a second confirmation message including an indication of the second PSCell and the associated second TEID toward the master node.

[0013] According to one aspect, a non-volatile program storage device readable by a machine is provided, the device tangibly embodying an instruction program executable by the machine for performing operations of a network node of a cellular communication network, the operations including: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many of the at least two PSCells can be prepared, if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services, and if the common user plane cannot be determined, associating a first TEID associated with the first user plane with the first PSCell, and sending a first confirmation message including an indication of the first PSCell and the associated first TEID toward a master node, and stopping preparation of the second PSCell, or associating a second TEID associated with the second user plane with the second PSCell, and sending a second confirmation message including an indication of the second PSCell and the associated second TEID toward the master node.

[0014] According to one aspect, an apparatus for a network node of a cellular communication network includes: a component for receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, a component for determining how many of the at least two PSCells can be prepared, a component for determining whether the first PSCell and the second PSCell can be associated with a common user plane for forwarding data services when the two PSCells can be prepared, and a component for performing the following operations when the common user plane cannot be determined: associating a first TEID associated with the first user plane with the first PSCell, and sending a first confirmation message including an indication of the first PSCell and the associated first TEID toward a master node, and stopping preparation of a second PSCell, or associating a second TEID associated with the second user plane with the second PSCell, and sending a second confirmation message including an indication of the second PSCell and the associated second TEID toward the master node. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The above-described aspects and other features are explained in the following description taken in conjunction with the accompanying drawings.

[0016] Figure 1 is a block diagram of one possible non-limiting system in which example embodiments may be practiced.

[0017] Figure 2 is a signaling diagram of Conditional PSCell Addition (CPA).

[0018] Figure 3 is a signaling diagram for implementing Option 1 of the examples described herein.

[0019] Figure 4 is a signaling diagram for implementing Option 2 of the examples described herein.

[0020] Figure 5A is a table showing the changes to TS38.423 section 9.2.3.30 to support enabling the use of per-target cell CU-UP in CPA / CPC initiation.

[0021] Figure 5B Changes to the GTP-TEID syntax element in TS 38.423 section 9.2.5 are shown to support enabling the use of per-target cell CU-UP in CPA / CPC initiation.

[0022] Fig. 6A The split bearer implemented using S-GW, MeNB, and en-gNB is shown, and the changes to Section 4.3.2 of TS37.340 are further shown.

[0023] Figure 6B The split bearer implemented using UPF, MN and SN is shown, and the changes to Section 4.3.2 of TS37.340 are further shown.

[0024] Figure 7 is a block diagram showing a central unit-control part controlling a first central unit-user part, and a second central unit-user part.

[0025] Figure 8 is a block diagram showing a central unit-control part controlling a first central unit-user part, a second central unit-user part, a third central unit-user part, and a fourth central unit-user part.

[0026] Fig. 9 Another example implementation of a network node is shown to facilitate the examples described herein.

[0027] Fig.10 is an example apparatus configured to implement the examples described herein.

[0028] Fig.11 is an example method for implementing the examples described herein.

[0029] Fig.12 is an example method for implementing the examples described herein.

[0030] Fig.13 is an example method for implementing the examples described herein. DETAILED DESCRIPTION

[0031] Go to Figure 1 , which shows a block diagram of one possible and non-limiting example of a wireless network 100 in which the example may be practiced. A user equipment (UE) 110, a radio access network (RAN) node 170, and (multiple) network elements 190 are shown. Figure 1In the example of , a user equipment (UE) 110 is in wireless communication with a RAN node 170. A UE is a device having a radio interface for accessing a wireless network 100. For example, the UE 110 includes: one or more processors 120, one or more memories 125 (on which computer program code is stored), and one or more transceivers 130 interconnected by one or more buses 127 or other wired connections. At least one of the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication device, etc. At least one of the one or more transceivers 130 is connected to at least one or more antennas 128. At least one of the one or more memories 125 includes a computer program code 123. The UE 110 includes a circuit system 140-1 and / or code 140-2 that can be implemented in a variety of ways. The circuit system 140-1 can be implemented in hardware, such as being implemented as part of the one or more processors 120. The circuit system 140-1 may also be implemented as an integrated circuit, or by other hardware such as a programmable gate array. In another example, the code 140-2 may be implemented as a computer program code 123 and may be executable by one or more processors 120. For example, one or more memories 125 and the computer program code 123 may be configured to, together with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations described herein. The UE 110 communicates with the RAN node 170 via a wireless or radio link 111. The circuit system 140-1 and / or the code 140-2 may provide L2 and / or L3 functions, such as L2 and / or L3 control plane signal processing.

[0032] In this example, RAN node 170 is a base station that provides access to UE 110. RAN node 170 may be, for example, a base station for 5G, also referred to as New Radio (NR). In 5G, RAN node 170 may be a NG-RAN node, such as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination towards the UE and is connected to the 5GC (e.g., (multiple) network elements 190) via an NG interface, such as connection 131. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination towards the UE and is connected to the 5GC via an NG interface, such as connection 131. An NG-RAN node may include multiple gNBs. A gNB may include a central unit (CU) (gNB-CU) 196 and one or more distributed units (DUs) (gNB-DUs), of which DU 195 is shown. Note that DU 195 may include or be coupled to and control a radio unit (RU). The gNB-CU 196 is a logical node that can host the radio resource control (RRC), SDAP and PDCP protocols of a gNB, or the RRC and PDCP protocols of an en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU 196 terminates the F1 interface connected to the gNB-DU 195. The F1 interface is illustrated as reference numeral 198, although reference numeral 198 also illustrates a link between a remote element of the RAN node 170 and a centralized element of the RAN node 170, such as a link between the gNB-CU 196 and the gNB-DU 195. The gNB-DU 195 is a logical node that can host the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is controlled in part by the gNB-CU 196. One gNB-DU 195 supports one or more cells. One cell can be supported by one gNB-DU 195, or one cell can be supported / shared by multiple DUs under RAN sharing. The gNB-DU 195 terminates the F1 interface 198 connected to the gNB-CU 196. Note that the gNB-DU 195 may include at least one processor and at least one memory with computer program code stored thereon, and a transceiver 160, for example, as part of a radio unit (RU), but some examples thereof may have the transceiver 160 as part of a separate RU, for example, under the control of the gNB-DU 195 and connected to the gNB-DU 195. One or more transceivers 160 are connected to one or more antennas 158. The gNB-DU 195 may also include circuit systems and / or code that may provide L2 functions (e.g., L2 control plane signal processing). The RAN node 170 may also be an eNB (evolved Node B) base station for LTE (Long Term Evolution), or any other suitable base station or node.

[0033] The gNB-CU 196 (and / or the RAN node 170) may include one or more processors 152, one or more memories 155, and one or more network interfaces (N / WI / F) 161 interconnected by one or more buses 157 or other wired connections. At least one of the one or more memories 155 includes computer program code 153, such as computer-readable instructions. The DU 195 may also include its own one or more memories, as well as (multiple) processors, and / or other hardware.

[0034] The RAN node 170 (and / or CU 196 and / or DU 195) includes a circuit system 150-1 and / or code 150-2 that can be implemented in a variety of ways. The circuit system 150-1 can be implemented in hardware, such as being implemented as part of one or more processors 152. The circuit system 150-1 can also be implemented as an integrated circuit or through other hardware such as a programmable gate array. In another example, the code 150-2 can be implemented as a computer program code 153 and can be executed by one or more processors 152. For example, one or more memories 155 and computer program code 153 can be configured to, together with one or more processors 152, cause the gNB-CU 196 (and / or RAN node 170 and / or DU 195) to perform one or more of the operations described herein. The circuit system 150-1 and / or code 150-2 can provide L3 functions, such as L3 control plane signal processing.

[0035] One or more network interfaces 161 communicate over a network, such as via links 176 and 131. Two or more gNBs 170 may communicate using, for example, link 176. Link 176 may be wired, wireless, or both, and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0036] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of wires on a motherboard or integrated circuit, optical fiber or other optical communication device, wireless channel, etc. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE, or a distributed unit (DU) 195 for a gNB implementation for 5G, where other elements of the RAN node 170 may be physically located at a different location from the RRH / DU 195, and the one or more buses 157 may be implemented in part, for example, as fiber optic cables or other suitable network connections for connecting other elements of the RAN node 170 (e.g., central unit (CU), gNB-CU 196) to the RRH / DU 195. Reference numeral 198 also indicates these suitable network links (multiple).

[0037] Note that the description herein indicates that a "cell" performs a function, but it should be clear that the device that forms the cell can perform the function. A cell constitutes part of a base station. That is, each base station can have multiple cells. For example, a single carrier frequency and associated bandwidth can have three cells, each covering one-third of a 360-degree area, so the coverage area of ​​a single base station covers an approximate ellipse or circle. In addition, each cell can correspond to a single carrier, and a base station can use multiple carriers. So if each carrier has 3 120-degree cells and there are 2 carriers, the base station has a total of 6 cells.

[0038] The wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to other networks such as telephone networks and / or data communication networks (e.g., the Internet) via one or more links 181. Such core network functions for 5G may include: (multiple) location management functions (LMFs), and / or (multiple) access and mobility management functions (AMFs), and / or (multiple) user plane functions (UPFs), and / or (multiple) session management functions (SMFs). Such core network functions for LTE may include MME (mobility management entity) / SGW (serving gateway) functions. Such core network functions may include SON (self-organizing / optimizing network) functions. These are merely exemplary functions that may be supported by (multiple) network elements 190, and it is noted that both 5G and LTE functions may be supported. The RAN node 170 is coupled to the network element 190 via a link 131. Link 131 may be implemented, for example, as an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected by one or more buses 185. The one or more memories 171 include computer program code 173.

[0039] The wireless network 100 can implement network virtualization, which is a process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). Network virtualization involves platform virtualization, which is usually used in conjunction with resource virtualization. Network virtualization is divided into external network virtualization or internal network virtualization. External network virtualization combines many networks or network parts into virtual units, while internal network virtualization provides network-like functions for software containers on a single system. Note that the virtualized entities generated by network virtualization are still implemented to some extent using hardware such as processors 152 or 175, and memories 155 and 171, and such virtualized entities also produce technical effects.

[0040] Computer readable memories 125, 155, and 171 may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-volatile memory, volatile memory, fixed memory, and removable memory. Computer readable memories 125, 155, and 171 may be components for performing storage functions. Processors 120, 152, and 175 may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Processors 120, 152, and 175 may be components for performing functions such as control of UE 110, RAN node 170, (multiple) network elements 190, and other functions described herein.

[0041] In general, various embodiments of user device 110 may include, but are not limited to, a cellular telephone with wireless communication capabilities (such as a smart phone, a tablet computer, a personal digital assistant (PDA)), a portable computer with wireless communication capabilities, an image capture device with wireless communication capabilities (such as a digital camera), a gaming device with wireless communication capabilities, a music storage and playback device with wireless communication capabilities, an Internet device allowing wireless Internet access and browsing, a tablet computer with wireless communication capabilities, a head-mounted display such as a head-mounted display implementing virtual / augmented / mixed reality, and a portable unit or terminal incorporating a combination of such functionality.

[0042] Thus, UE 110, RAN node 170, and / or network element(s) 190 (and associated memory, computer program code, and modules) may be configured to implement (e.g., in part) the examples described herein, including enabling use of each target cell CU-UP in CPA / CPC initiation. Figure 1 The computer program code 123, circuit system 140-1, code 140-2, and other elements / features shown in the RAN node 170 may be configured to implement the user equipment related aspects of the examples described herein. Figure 1 The computer program code 153, circuit system 150-1, code 150-2 and other elements / features (including CU 196 and DU 195) shown in the figure can be configured to implement the example RAN / gNB / TRP related aspects described herein. Figure 1 The computer program code 173 and other elements / features shown in may be configured to implement the network element related aspects of the examples described herein.

[0043] Having thus introduced a suitable but non-limiting technical context for practicing example embodiments, example embodiments are now described in a more specific manner.

[0044] The examples described in this article involve the preparation of multiple PSCells, especially in CPA and / or CPAC scenarios. The description of such examples in this article will contribute to the 3GPP RAN2 / 3 meeting. Therefore, the examples described in this article provide a solution for preparing multiple PSCells. At present, the preparation of PSCell is enabled only for PSCells belonging to or only assigned to one user plane (1TEID). The examples described in this article involve modifying the message or message flow between MN and SN, so that PSCells can be allocated and prepared more flexibly, especially PSCells belonging to or assigned to different user planes with 2 different TEIDs. The advantages, technical effects, and improvements of the examples described in this article include enabling efficient and flexible allocation of PSCells, and increasing the number of PSCells potentially prepared, thereby improving UE mobility robustness. The solution described in this article also fills the gap in standardization. In particular, the solution described in this article may require changes to TS36.423 and TS 38.423 of the 3GPP standard. The examples described in this article are likely to become standard basic patents in NR.

[0045] One of the enhancements added to NR and EN-DC in Rel.17 is Conditional PSCell Addition (CPA), which can also be part of Conditional PSCell Addition or Change (CPAC). CPA assumes that when the MN initiates the add procedure, it provides the target SN with a list of possible PSCells that the UE can eventually access, and the target SN selects which of them to be prepared with the target cell configuration. The target SN then provides the prepared PSCell list back to the MN.

[0046] In designing the signaling, RAN3 reuses the existing add preparation procedure, which is designed for classic add, where the target SN selects a target PSCell and prepares it for immediate access.

[0047] Figure 2 A high level signaling diagram 200 of a CPA is shown.

[0048] In steps 1 (201) and 2 (202), source MN 170 proposes a list of PSCells to be prepared by each target SN (170-2, 170-3). In addition, source MN 170 indicates the maximum number of PSCells that the target SN (170-2, 170-3) can prepare.

[0049] In steps 3 (203) and 4 (204), the target SN (170-2, 170-3) decides the candidate target PSCell(s) to be prepared in the suggestion list. The target SN (170-2, 170-3) cannot select a PSCell not included in the list.

[0050] In steps 5 (205) and 6 (206), the target SN (170-2, 170-3) sends the CPC configuration of each prepared target PSCell and the ID of the prepared target PSCell(s) to the MN 170.

[0051] If some bearers are configured with PDCP in the SN (170-2, 170-3), the MN 170 sends the TEID in the Xn address indication in steps 7 (207) and 8 (208).

[0052] In step 9 (209), MN 170 sends a conditional (re)configuration to UE 110, which includes CPC configurations of (multiple) candidate target PSCells and CPC execution conditions determined by MN 170.

[0053] In step 10 (210), UE 110 sends a message to MN 170 to confirm receipt of the conditional configuration.

[0054] In step 11 (211), UE 110 evaluates CPC execution conditions of the prepared target PSCell(s).

[0055] In step 12 (212), for example, the PSCell candidate in the target SN 1 170-2 satisfies the CPC execution condition.

[0056] In step 13, UE 110 sends a message to MN 170 to indicate the execution of CPC configuration. The message includes the embedded SN RRC Reconfiguration Complete sent to target SN 1 170-2 in step 14 (214).

[0057] In step 15, UE 110 completes random access to target PSCell / SN 170-2 (215).

[0058] The classic addition preparation of NR Re.15 procedure assumes the preparation of a single PSCell. Therefore, the procedure enables the target SN to provide a single set of tunnel endpoints (TEID) for DL ​​data forwarding.

[0059] In NR Rel.17 CPA, the target SN (gNB) can prepare more than one PSCell that can belong to different gNB-DUs. When processing CPA, RAN3 is not aware of these DUs, and thus the prepared PSCells can belong to different CU-UPs. Therefore, the single set of TEIDs inherited from the classic addition preparation of Rel.15 is not sufficient to support CPA of Rel.17.

[0060] There is no direct prior art for this problem. In Conditional HO (CHO) (which is the first case of conditional mobility), the HO preparation procedure is initiated for a single target PCell. Therefore, this problem does not exist.

[0061] Another solution to this problem is to assume that CPA is limited to a set of PSCells belonging to one or more DUs served by a single CU-UP, and therefore, a SN supporting CPA can be connected to only a single CU-UP. However, at this stage of NR development, this is a completely unrealistic assumption. There may be multiple logical CU-UPs in a gNB, not only from a service or slice perspective, but also from a simple load balancing and scaling perspective. Moreover, even from a logistics and failure perspective, a smaller manageable CU-UP is preferred over one large CU-UP.

[0062] The core of the proposed solution is to enable the target SN to provide a data forwarding TEID for each prepared PSCell or for a group of prepared PSCells using the same CU-UP.

[0063] In more detail, there are two options to implement this idea: Option 1) the PSCell preparation process is repeated as many times as the number of PSCell groups (the number of groups is based on the number of CU-UPs serving the prepared PSCells), or Option 2) TEID information is provided for each prepared PSCell (or for a group of prepared PSCells served by the same CU-UP).

[0064] Option 1

[0065] In option 1, the classic add preparation process remains the same as the design in Rel.17. However, it is assumed that the process is initiated as many times as the number of CU-UPs serving the prepared PSCells. This means that the MN must be made aware of how many times the preparation of the PSCell must be repeated before the entire set of prepared PSCells is signaled. This can be done in two ways (following 1-2):

[0066] 1) When responding to a PSCell preparation procedure, the target SN includes a flag indicating "more cells are prepared" and signals to the source MN that the conditional configuration of the preparation requires a new preparation request from the initiating node (MN). If this flag is included, the MN will reinitialize the preparation (which can now be another add preparation or modify preparation procedure). This operation is repeated until the target SN indicates that no more PSCells need to be prepared (or does not indicate that there are more PSCells). In the case of XnAP, the Xn address indication must also be sent multiple times from the target MN to the target SN.

[0067] 2) In response to the initial CPA request, the target SN provides the total number of preparations that need to be initiated (including the initial preparation or the total remaining preparations). The MN then initiates as many additional preparations as indicated (which can now be another add preparation or a modify preparation process) without any further indication. In this case, if additional transaction IDs are used in these processes, the additional preparations can be run in parallel instead of initiating them sequentially (in practice this can be a bit different: the maximum number of PSCells that the target SN can prepare is 8, so it is unlikely that they belong to so many UPs that parallel preparations will bring a noticeable improvement). In the case of XnAP, the target MN may also need to send Xn address indications to the target SN multiple times, and may need to include a transaction ID so that the message can be matched with the parallel preparation processes.

[0068] Figure 3 300 is a signaling diagram of option 1 of the example described herein. At 301, MN 170 sends an SgNB add request for multi-RAT PSCell1 and PSCell2 to SN1-CU-CP 196-1. At 301-2, SN1-CU-CP 196-1 determines that PSCell1 and PSCell2 are served by different CU-UPs. At 301-a, SN1-CU-CP 196-1 sends an E1 bearer context establishment request for PSCell1 to SN1-CU-UP1 196-2. At 301-b, SN1-CU-UP1 196-2 sends an E1 bearer context establishment response including TEID1 to SN1-CU-CP 196-1. At 302, SN1-CU-CP 196-1 sends an SgNB add request confirmation including PSCell1-TEID1 and a preparation incomplete indication to MN 170. At 302-2, MN 170 determines that PSCell preparation is not completed, and determines to send an SgNB add request for PSCell2.

[0069] At 301-1, MN 170 sends an SgNB add request for multi-RAT PSCell2 to SN1-CU-CP 196-1. At 301-1-a, SN1-CU-CP 196-1 sends an E1 bearer context establishment request for PSCell2 to SN1-CU-UP2 196-3. At 301-1-b, SN1-CU-UP2 196-3 sends an E1 bearer context establishment response including TEID2 to SN1-CU-CP 196-1. At 302-1, SN1-CU-CP 196-1 sends an SgNB add request confirmation including PSCell2 TEID2 and a preparation completion indication to MN 170.

[0070] At 303, MN 170 sends an RRC connection reconfiguration message to UE 110, wherein the MN RRC connection reconfiguration includes the SN RRC reconfiguration. At 304, UE 110 sends an RRC connection reconfiguration complete message to MN 170. At 304-a, UE 110 sends an RRC connection reconfiguration complete message including an SN RRC reconfiguration complete indication to MN 170. At 305, MN 170 sends an SgNB reconfiguration complete message to SN1-CU-CP 196-1. At 306, UE 110 and SN1-CU-CP 196-1 participate in the random access procedure. At 307, MN 170 sends an SN state transfer message to SN1-CU-CP 196-1.

[0071] At 308-1, data arriving at MN 170 from S-GW 190-1 begins to be forwarded to SN1-CU-UP1 196-2. At this point, MN 170 begins data forwarding toward SN1-CU-UP1 196-2. At 308-2, MN 170 forwards the data to SN1-CU-UP1 196-2. At 314, a path update process occurs, which at least partially includes items 309, 310, 311, and 312. At 309, MN 170 sends an E-RAB modification indication to S-GW 190-1. At 310, S-GW 190-1 and MME 190-2 exchange bearer modification information. At 311, MN 170 sends an end marker packet to SN1-CU-UP1 196-2. At this time (311), MN 170 forwards the last packet as the end marker to SN1-CU-UP1196-2. At this time (311), data forwarding stops. At 312, S-GW 190-1 sends an E-RAB modification confirmation message to MN 170.

[0072] Option 2

[0073] In option 2, the message sent by the target SN in response to the CPA preparation is significantly modified so that the data forwarding information (and bearer establishment in the case of XnAP) is added to the existing list of prepared PSCells. This can be added for each prepared PSCell, or the prepared PSCells are grouped based on their corresponding serving CU-UP and the information is provided for the PSCell group. In the case of XnAP, the Xn address indication must also be modified: it is either sent multiple times (and then enhanced with information that enables matching each message to a PSCell or PSCell group), or the message is enhanced so that the TEIDs of all prepared PSCells or PSCell groups are included in a single message.

[0074] The choice of option depends on further discussion in 3GPP, but option 2 may be more suitable for XnAP, where the bearer establishment is a single information block and can be easily added to the existing list. In the case of X2AP, where the forwarding information is distributed over the prepare response message, option 1 may be more suitable.

[0075] Figure 4 An example signaling diagram for Option 2 is illustrated in , for the case where the target SN prepares two PSCells (PSCell1 and PSCell2) served by different CU-UPs, ie, PSCell1 and 2 are identified based on the Measurement Report (MR) received from the source MN.

[0076] At 401, MN 170 sends an SgNB add request for multi-RAT PSCell1, PSCell2, PSCell3, and PSCell4 to SN1-CU-CP 196-1. At 401-2, SN1-CU-CP 196-1 determines that PSCell1, PSCell2, and PSCell3, PSCell4 are served by different CU-UPs. At 401-a, SN1-CU-CP 196-1 sends an E1 bearer context establishment request for PSCell1 and PSCell2 to SN1-CU-UP1 196-1. At 401-b, SN1-CU-UP1 196-2 sends an E1 bearer context establishment response including TEID1 to SN1-CU-CP 196-1. At 401-c, SN1-CU-CP 196-1 sends an E1 bearer context establishment request message for PSCell3 and PSCell4 to SN1-CU-UP2 196-3. At 401-d, SN1-CU-UP2 196-3 sends an E1 bearer context establishment response message including TEID2 to SN1-CU-CP 196-1. At 402, SN1-CU-CP 196-1 sends an SgNB add request confirmation including TEID1 for PSCell1 and PSCell2 and TEID2 for PSCell3 and PSCell4 to MN 170.

[0077] At 403, MN 170 sends an RRC connection reconfiguration message to UE 110, wherein the MN RRC connection reconfiguration includes the SN RRC reconfiguration. At 404, UE 110 sends an RRC connection reconfiguration complete message to MN 170. At 404-a, UE 110 sends an RRC connection reconfiguration complete message including an SN RRC reconfiguration complete indication to MN 170. At 405, MN 170 sends an SgNB reconfiguration complete message to SN1-CU-CP 196-1. At 406, UE 110 and SN1-CU-CP 196-1 participate in the random access procedure. At 407, MN 170 sends an SN state transfer message to SN1-CU-CP 196-1.

[0078] At 408-1, data arriving at MN 170 from S-GW 190-1 begins to be forwarded to SN1-CU-UP1 196-2. At this point, MN 170 begins data forwarding to SN1-CU-UP1 196-2. At 408-2, MN 170 forwards the data to SN1-CU-UP1 196-2. At 414, a path update process occurs, which at least partially includes items 409, 410, 411, and 412. At 409, MN 170 sends an E-RAB modification indication to S-GW 190-1. At 410, S-GW 190-1 and MME 190-2 exchange bearer modification information. At 411, MN 170 sends an end marker packet to SN1-CU-UP1 196-2. At this time (411), MN170 forwards the last packet to SN1-CU-UP1 196-2, which is the end mark. At this time (411), data forwarding stops. At 412, S-GW 190-1 sends an E-RAB modification confirmation message to MN 170.

[0079] therefore, Figure 3 and Figure 4 SN1 The CU-CP may implement a method for preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, wherein the method comprises: receiving a first request to add at least two PSCells from a master node serving the user equipment, determining how many PSCells of the at least two PSCells can be prepared, if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services, if the common user plane can be determined, associating a first TEID associated with the common user plane and used for the two PSCells, and sending a confirmation message including an indication of the two PSCells and the associated first TEID toward the master node, if the common user plane cannot be determined, determining whether a network connection toward the master node supports a confirmation message including different TEIDs, if the network connection supports a confirmation message including different TEIDs, associating the first TEID associated with the first user plane with the first PSCell, and associating the second TEID associated with the second user plane with the second PSCell, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID toward the master node [Option 2, Figure 4], and / or if the network connection does not support confirmation messages including different TEIDs, then the first TEID associated with the first user plane is associated with the first PSCell, and a first confirmation message including an indication of the first PSCell and the associated first TEID is sent towards the master node, and preparation of the second PSCell is stopped [option in accordance with the current 3GPP standard], or the second TEID associated with the second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node [option 1, Figure 3 ].

[0080] The method may further include: if the network connection does not support a confirmation message including a different TEID, sending a first confirmation message, the first confirmation message also including an indication that at least one additional PSCell can be prepared (or an indication that preparation of the PSCell is not completed, or an indication that an additional addition request is requested) [Option 1, Figure 3 ].

[0081] The method may also include: receiving a second request to add at least one additional PSCell [Option 1, Figure 3 ].

[0082] The method may further include: if the network connection does not support a confirmation message including a different TEID, sending a second confirmation message, the second confirmation message further including: an indication that another PSCell cannot be prepared (or an indication that preparation of the PSCell is complete) [Option 1, Figure 3 ].

[0083] The method may further include: wherein the first TEID and / or the second TEID is associated with downlink data traffic [all options].

[0084] The method may further include: wherein the TEID corresponds to GTP-TEID (GPRS Tunneling Protocol - Tunnel Endpoint Identifier) ​​[all options].

[0085] The method may further include: wherein the first request is related to a conditional PSCell change (CPC), or a conditional PSCell addition or change (CPAC).

[0086] For option 2, the CU-CP of SN1 may include an apparatus for a network node of a cellular communication network, the apparatus comprising: at least one processor; and at least one non-volatile memory comprising computer program code, wherein the at least one non-volatile memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least: receive a first request to add at least two PSCells for a user equipment supporting dual connectivity, determine how many of the at least two PSCells can be prepared, and if the first PSCell and the second PSCell can be prepared, determine whether the two PSCells can be associated with a common user plane for forwarding data services, and if the common user plane cannot be determined, associate a first TEID associated with the first user plane with the first PSCell, and associate a second TEID associated with the second user plane with the second PSCell, and send a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID.

[0087] Potential modifications, implementations, and technical alternatives and advantages may include changes to TS38.423 Section 9.2.3.30 UP Transport Layer Information. This element is used to provide transport layer information associated with NG or Xn user plane transport. In this version, it corresponds to the IP address and GTP tunnel endpoint identifier. When the NR-DC UE is connected to the IAB, in the case where the S-NG-RAN node serves the IAB and packets belonging to the MN terminated split bearer / SCG bearer are sent from the M-NG-RAN node to the S-NG-RAN node, and in the case where the M-NG-RAM node serves the IAB and packets belonging to the SN terminated split bearer / MCG bearer are sent from the S-NG-RNA node to the M-NG-RAN node, the QoS mapping information is used to set the IP header of the packet.

[0088] The table in Section 9.2.3.30 can be written as Figure 5A As shown, it is changed to include the IE / group name "GTP-TEID" (item 502), and changed so that the IE type and reference "associated with a first cell, and optional additional OCTECT string(s) associated with additional cells" (item 504).

[0089] Section 9.2.5 may be modified so that the description of the GTP-TEID syntax element "is associated with the first cell, and the optional additional OCTECT string(s) are associated with the additional cells", as follows and Figure 5B As shown (reference item 506):

[0090] GTP-TEID::=OCTET STRING (SIZE(4) associated with the first cell and optional additional OCTECT strings(s) associated with additional cells)

[0091]

[0092]

[0093] TS 37.340 may be modified to include "For split bearers, MN terminated SCG bearers and SN terminated MCG bearers, PDCP data is transferred between the MN and the SN via the MN-SN user plane interface," as shown below.

[0094] "4.3.2 User plane

[0095] 4.3.2.1 Common MR-DC principles

[0096] For a certain UE, the MN and SN involved in MR-DC have different U-plane connection options.

[0097] like Figure 4 .3.2.1-1. The U-plane connection depends on the configured bearer option:

[0098] - For MN terminated bearers, the user plane connection with the CN entity is terminated in the MN;

[0099] - For SN terminated bearers, the user plane connection with the CN entity is terminated in the SN;

[0100] - The transmission of user plane data over Uu involves MCG or SCG radio resources or both:

[0101] -For MCG bearers, only MCG radio resources are involved;

[0102] -For SCG bearers, only SCG radio resources are involved;

[0103] - For split bearers, both MCG and SCG radio resources are involved.

[0104] - For split bearers, MN terminated SCG bearers and SN terminated MCG bearers, PDCP data is transferred between the MN and the SN via the MN-SN user plane interface. "

[0105] In the above changes to TS37.340, Fig. 6A Item 176-2 was added to the Figure 6BItem 176-1 is added to the specification, for split bearers, MN (170-1, 170) terminated SCG bearers and SN (170-3, 170-2) terminated MCG bearers, PDCP data is transmitted between MN (170-1, 170) and SN (170-3, 170-2) via the MN-SN user plane interface (176-2, 176-1). Fig. 6A As shown in FIG, the bearer is split between MeNB 170-1 to S-GW 190-1 via S1-U 131-3 and en-gNB 170-3 to S-GW 190-1 via S1-U 131-4. Figure 6B As shown in FIG, the bearer is split between the MN 170 through the NG-U 131 to the UPF 190-3 and the SN 170-2 through the NG / U 131-2 to the UPF 190-3.

[0106] If the SN is implemented using multiple user planes, the MN needs to know to which user plane the message should be forwarded, so the SN needs to inform the MN of the corresponding DL GTP TEID.

[0107] In an example implementation of a network node, such as used as a secondary node (SN), Figure 7 As shown, the central unit-control part 796 controls a first central unit-user part 796-1 and a second central unit-user part 796-2. The distributed unit 795 provides two cells (701, 702) which may be configured as PSCells, for example.

[0108] If the CU-CP 796 receives a request from the master node (MN) including preparing / adding at least two PSCells (see Figure 3 and Figure 4 ), the CU-CP 794 may perform one or more of the following operations:

[0109] 1) Determine how many PSCells of at least two PSCells can be prepared. The determination may depend on one or more parameters, such as the load condition of the PSCells, for example, when PSCell2 is overloaded, only PSCell1 can be prepared.

[0110] 2) If the first PSCell and the second PSCell can be prepared, determine whether the two PSCells can be associated with a common user plane for forwarding data traffic. The configuration of the CU-UP may depend on one or more parameters, such as i) the CU-UP is assigned to different network slices, the CU-CP determines which slice the request is related to, and selects the associated CU-UP associated with the first PSCell and the second PSCell, ii) the CU-UP is permanently assigned to a single cell, such as CU-UP1 is permanently assigned to Cell1, CU-UP2 is permanently assigned to Cell2, or iii) the CU-UP can be dynamically configured and temporarily assigned to Cell1 and / or Cell2, for example, CU-UP1 can be associated with Cell1 and Cell2 for forwarding downlink data traffic from the MN, or, for example, due to overload or other criteria, the allocation of Cell1 and Cell2 needs to be split with respect to the allocated user plane, such as Cell1 associated with CU-UP1, Cell2 associated with CP-UP2.

[0111] 3) If a common user plane can be determined, the first TEID associated with the common user plane and used for both PSCells is associated and a confirmation message including an indication of the two PSCells and the associated first TEID is sent. A common user plane for both cells may be considered a beneficial option because, for example, in the case of CPC, only one resource may be reserved which is then used if the condition (or conditions) for one cell is met and then, for example, cell 1 is used as the new SN cell towards the UE.

[0112] 4) If a common user plane can be determined, determine whether the network connection toward the primary node supports a confirmation message including different TEIDs. The user plane is typically associated with a TEID to provide an address that the MN can use to forward downlink data traffic, for example for splitting bearers. Currently, the 3GPP standard specification includes a format for the SgNB message that only supports the inclusion of one TEID, where the TEID is valid for all prepared cells. If cell 1 and cell 2 are prepared and associated with the same user plane, and thus associated with the TEID, the MN is enabled to forward data traffic and can address the data traffic to the correct destination. In previous networks, the SN included only one user plane and therefore only one TEID, however, with the evolution of the network and greater flexibility within the network and in the network topology, network nodes can now include more than one user plane. This requires managing the allocation / association of available cells to available user planes, which may not be an easy problem to solve given the potential conflicting requirements within the network, which makes it more difficult to optimize all of these requirements. Example: The UE can be optimized based on mobility robustness, for example, in the case of CPC, the risk of radio link failure can be reduced by preparing as many cells as possible. The SN may reserve the opportunity to assign cells to the user plane as dynamically as possible without restrictions, for example to optimize load distribution, etc. In the case of CPC, where multiple cells are prepared, flexibility may be reduced considering the possible restriction that all cells that may be prepared use one common user plane. For example, considering the restriction that the SgNB Add Request Confirm message only supports one TEID to be added.

[0113] 5) If the network connection supports confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent [Option 2, Figure 4 ].

[0114] Related to (5), however, as described above, it may be necessary to assign cell 1 and cell 2 to different user planes, or this may be more efficient from the perspective of the SN. In order to enable the assignment of multiple cells, it is recommended to amend the current 3GPP standard specification because, for example, without modification, one or more cells cannot be prepared, resulting in reduced mobility robustness of the UE. For example, one option for the SN at present is to include only cell 1 with TEID1 in the SgNB add request confirmation message and discard it without preparing cell 2 (due to the association with TEID2). When the format of the SgNB add request confirmation message is amended, for example, there is an opportunity to include at least a second TEID, which will have the following benefits, namely, both cell 1 (associated with TEID1) and cell 2 (associated with TEID2) can be prepared, thereby improving the mobility robustness of the UE. One way to include one or more TEIDs in the SgNB add request confirmation message may typically be to provide a list of PSCell IDs, such as PSCell1 ID, PSCell2 ID, PSCell3 ID, etc. The current TEID field can be extended by other fields associated with the listed cells, such as TEID1, TEID2, TEID3, etc., where TEID1 is located in the first position, indicating that it is associated with PSCell1 in the first position, TEID2 is located in the first position, indicating that it is associated with PSCell2 in the first position, TEID3 is located in the first position, indicating that it is associated with PSCell3 in the first position, and so on.

[0115] An example combined group of PSCell1-4 associated with TEID1 and PSCell5-6 associated with TEID2 can be encoded, for example, using a PSCell-ID list: PSCell1 ID, PSCell2 ID, PSCell3 ID, PSCell4 ID, PSCell5 ID, PSCell6 ID, and the associated TEID fields: TEID1, TEID1, TEID1, TEID1, TEID2, TEID2.

[0116] 5) the above and / or 6) if the network connection does not support confirmation messages including different TEIDs, the first TEID related to the first user plane is associated with the first PSCell, and a first confirmation message including an indication of the first PSCell and the associated first TEID is sent, and preparation of the second PSCell is stopped [option in accordance with current 3GPP standards].

[0117] In order to remain compliant with the criteria, the SN may choose to prepare as many cells as possible, for example cells that can be associated with one common user plane so that only one TEID is used. However, not all cells that can be prepared are actually prepared, resulting in lower mobility robustness of the UE. Another potential disadvantage is that if other cells can be grouped together (associated with common user planes and TEIDs) and the criterion for selecting which cell should be prepared is to select as many cells as possible, then the cell with the highest RSRP measured by the UE, and therefore the cell that can be beneficial for handover if the relevant CPC conditions are met, may not be prepared. However, if the SN knows the cell with the highest measured RSRP, and uses this criterion as a segmentation criterion, the best cell (the cell that currently has the best chance of a successful handover) will be selected, prepared, and forwarded to the MN, while discarding and / or not preparing a large number of other cells that could have been prepared. These are some of the constraints faced by the SN, and therefore the selection process needs to be coordinated or optimized to fully meet the needs of different sites (e.g., MN, SN, UE, core network, etc.).

[0118] 6) Continue: or associate the second TEID associated with the second user plane with the second PSCell, and send a second confirmation message including an indication of the second PSCell and the associated second TEID [Option 1, Figure 3 ].

[0119] Another option for amending the standard is to enable the SN to send two subsequent SgNB Add Request Confirm messages (each including a current TEID). This would require minor changes to the current format of the messages. A first SgNB Add Request Confirm message is sent (e.g., with PSCell1 and TEID1), followed by a second SgNB Add Request Confirm message (e.g., with PSCell2 and TEID2). The standard may be amended to include support for the MN to receive two subsequent SgNB Add Request Confirm messages. Another option is to include an indication in the first SgNB Add Request Confirm message that at least one additional PSCell can be prepared. In a network implementation, the network nodes may support different 3GPP releases, such as Rel.16, 17, 18. Regarding whether the network connection between the secondary node and the primary node supports confirmation messages including different TEIDS, it is likely that the UE connected to the primary node supports Rel.16 or Rel.17, but not Rel.18, and / or the primary node supports Rel.16, 17, 18, and the secondary node supports Rel-16 and 17, but not Rel.18. Therefore, a solution is provided that makes the action of the secondary node depend on the network connection, such as supporting UEs supporting Rel 17 and UEs supporting Rel 18.

[0120] Therefore, if the network and / or UE supports different standard versions, for example, Rel. 16 and / or 17 (ack with 1 TEID) do not support the new concepts described herein, while Rel. 18 (ack with 2 TEIDs) supports the new concepts described herein. The actions of the secondary node may be different and adapted to the specific actual connection and its related support features. For example, Rel. 18 and / or another Rel. enables or allows sending one ack message including 2 TEIDs, and / or sending two ack messages in sequence, for example a first ack message including a first TEID and a second ack message including a second TEID, the first TEID and the second TEID being different.

[0121] 7) If the network connection does not support a confirmation message including a different TEID, a first confirmation message is sent, the first confirmation message also including an indication that at least one additional PSCell can be prepared (or an indication that the preparation of the PSCell is not complete, or an indication that another addition request is requested) [Option 1, Figure 3 ]. The indication may be, for example, a flag indicating that the preparation is not complete. The MN then regards this as a trigger for sending a second SgNB add request so that the SN can send a second SgNB add request confirmation message (e.g., PSCell2 and TEID2).

[0122] The method may also include receiving a second request to add at least one additional PSCell [Option 1, Figure 3 ]. A flag indicating that preparation is not complete may trigger the MN to evaluate whether to send a second SgNB add request. Taking into account other factors, the MN may consider not sending a second request because this would require additional messages and time delays. For example, in time-critical situations, such as URLLC, preparing additional cells may delay the UE's reconfiguration. Alternatively, the RRC reconfiguration may be sent to the UE after receiving the first SgNB add request confirmation message, and the second SgNB add request message is sent in parallel or thereafter. This may require a second RRC reconfiguration thereafter.

[0123] The method may further include: if the network connection does not support a confirmation message including a different TEID, sending a second confirmation message, the second confirmation message also including an indication that another PSCell cannot be prepared (or an indication that preparation of the PSCell is complete) [Option 1, Figure 3]. The SgNB add request confirmation message may include a flag indicating that the preparation is now complete, for example indicating that further cells cannot be prepared at this time. This flag may be optional, because without this flag, the MN may inherently consider that the preparation is complete, because the MN expects only one confirmation per request, and / or if the flag preparation is not complete is not included, the preparation is already completed. Or, in fact, it can be the same flag (encoded with 1 bit), which indicates, for example, with "1" that the preparation of the cell is complete, and for example with "0" to indicate that the preparation is not complete. This indeed only introduces very minor corrections, the effect of which is that multiple cells associated with multiple user planes can be prepared, thereby increasing the flexibility of the SN to dispatch and allocate resources. In order to avoid sending too many SgNB add request confirmation messages, the SN can configure the cell-user plane allocation in an efficient way, for example, grouping as many available cells as possible into a common user plane to form a single TEID, for example requesting to add 8 cells, determining that 6 of the 8 cells are available for preparation due to other criteria, associating cells 1-3 with user plane 1 and cells 4-6 with user plane 2. In this way, the number of resources reserved in the user plane is also efficiently utilized.

[0124] In another embodiment, the SN may be Figure 8 Specifically, in another example implementation of a network node, such as used as a secondary node (SN), as shown in Figure 8 As shown, the central unit-control section 896 controls the first central unit-user section 896-1 and the second central unit-user section 896-2, as well as the third central unit-user section 896-3 and the fourth central unit-user section 896-4.

[0125] The first distributed unit 895-1 provides two cells (cell 1 801, cell 2 802), which can be configured as PSCells, for example. The second distributed unit 895-2 provides two cells (cell 3 803, cell 4 804), which can be configured as PSCells, for example.

[0126] If CU-CP1 896 receives a request to add cells 1 (801) and 3 (803) as PSCells, and both cells are available and can be prepared, due to the topology of the network, it is clear that cell 1 801 can only be associated with CU-UP1 896-1 or CU-UP2 896-2, and cell 3 803 can only be associated with CU-UP3 896-3 or CU-UP4 896-4. If a situation arises where two different TEIDs need to be associated with cells 1 801 and 3 803, such that the SN needs to determine whether both cells can be prepared, for example, if the network supports a 3GPP standard version that supports an SgNB Add Request Confirm message with only one TEID, then only cell 1 801 or cell 3 803 can be prepared. If the network supports an SgNB Add Request Confirm message with only one or more TEIDs, then both cell 1 801 and cell 3 803 can be prepared. If the network supports SgNB Add Request Confirm messages, with only one TEID per message, but with an additional indication that additional cells may be prepared, both Cell 1 801 and Cell 3 803 may be prepared, for example using two different SgNB Add Request Confirm messages.

[0127] Fig. 9 Another example implementation of the network node 900 is shown, for example for use as a secondary node, which increases flexibility, for example in terms of resource usage, and taking into account load balancing, or using different user planes for different services and / or slices, and / or based on other criteria / parameters such as URLLC, BWP (bandwidth part), eMBB, mMTC, etc., whereby further coordination may be required when selecting the associated user plane to enable efficient addition of PSCells and efficient use of resources.

[0128] Fig. 9A network node 900 is shown including CU-UP1 996-1, CU-UP2 996-2, CU-UP3 996-3, and CU-UP4 996-4, any of which may be connected to DU1 995-1, DU2 995-2, DU3 995-3, DU4 995-4, DU5 995-5, DU6 995-6, DU7 995-7, DU8 995-8, DU9 995-9, and / or DU10 995-10. The network node 900 includes CU-UP5 996-5, CU-UP6 996-6, CU-UP7 996-7, and CU-UP8 996-8, any of which can be connected to DU11 995-11, DU12 995-12, DU13 995-13, DU14 995-14, DU15 995-15, DU16995-16, DU17 995-17, DU18 995-18, DU19 995-19, and / or DU20995-20.

[0129] More details of procedures such as CPC (Conditional PSCell Change), Radio Resource Configuration (RRC), Dual Connectivity (DC), inter-node communication, and related procedures are described in 3GPP specifications, for example, related to LTE and / or 5G NR, such as TS37.340 v16.8.0 (2021-12), in particular Section 10.2 Secondary Node Addition, Section 10.3 Secondary Node Modification (MN / SN Initiated), Section 10.5 Secondary Node Change (MN / SN Initiated), Section 10.5.2 MR-DC for 5GC, Section 10.6 PSCell Change, Section 10.10.2 MR-DC for 5GC, Section 10.3.2 MR-DC for 5GC, S38.423 v17.0.0 (2022-04), in particular Section 9.1.2 Messages of Dual Connectivity Procedure, and TS38.331 v16.7.0 (2021-12), in particular Section 5.5.4 Measurement Report Trigger, Section 5.5.5 Measurement Report, Section 5.3.5 RRC Reconfiguration, Section 4.4 Functionality, Section 5.2 System Information, Section 5.2.1 Introduction, Section 5.7.2a UL Information Transmission of MR-DC, and Section 6.3.2 Radio Resource Control Information Elements, such as ConditionalReconfiguration. IE ConditionalReconfiguration is used to add, modify, and release conditional reconfiguration configurations. The references cited are incorporated herein by reference. In future releases, the description of one or more embodiments herein may be used to modify and / or adapt the relevant 3GPP specifications.

[0130] For example, TS36.423 v17.0.0 (2022-04) can be modified as follows:

[0131] Each or at least one cell in the prepared candidate cell list has an optional new "forwarding group ID". If not included, the information from the main message body applies (so that the UE and / or node and / or UE connection with a node supporting the previous version can or will operate according to the previous process, while the UE and / or node and / or UE connection with a node supporting the new version using the new "forwarding group ID" can, may, or will operate according to the new process. For example, the new "additional forwarding information" list enables more than one TEID set to be provided. Each element therein is identified with an ID so that it can be matched with a candidate PSCell.

[0132] Section 9.1.4.2 SGNB Add Request Confirmation

[0133] This message is sent by en-gNB to confirm the SgNB addition preparation to MeNB. Direction: from en-gNB to MeNB.

[0134]

[0135]

[0136]

[0137]

[0138]

[0139]

[0140]

[0141]

[0142]

[0143]

[0144]

[0145]

[0146] At least one of the following sections may be adapted / modified in a similar manner as above, e.g. Section 9.1.4.5 SGNB Modification Request,

[0147] 9.1.4.6SGNB modification request confirmation,

[0148] 9.1.4.8 requires SGNB modification,

[0149] 9.1.4.18SGNB change confirmation.

[0150] Similarly, at least one of the following parts of TS38.423 may be adapted / modified in a similar manner as described above:

[0151] 9.1.1.11XN-U Address Indication

[0152] This message is sent by the new NG-RAN node to transmit data forwarding information to the old NG-RAN node, or by the M-NG-RAN node to provide data forwarding of SN terminated bearers, or information related to the Xn-U bearer address to the S-NG-RAM node.

[0153] Direction: From new NG-RAN nodes to old NG-RAM nodes, from M-NG-RAN nodes to S-NG-RAN nodes.

[0154]

[0155]

[0156]

[0157]

[0158] and / or chapter

[0159] 9.1.2.2S Node Add Request Confirmation

[0160] This message is sent by the S-NG-RAN node to confirm the S-NG-RAN node addition preparation to the M-NG-RAN node.

[0161] Direction: From S-NG-RAN node to M-NG-RAM node.

[0162]

[0163]

[0164]

[0165]

[0166]

[0167]

[0168]

[0169]

[0170]

[0171] and / or similarly

[0172] 9.1.2.5S Node Modification Request

[0173] 9.1.2.6S Node Modification Request Confirmation

[0174] 9.1.2.8 S node modification required

[0175] 9.1.2.12S Node Change Confirmation

[0176] According to 3GPP TS23.501v17.4.0 (2022-03), the 5G system architecture is defined to support data connectivity and services to enable deployment using technologies such as network function virtualization and software defined networking. The 5G system architecture should utilize service-based interactions between control plane (CP) network functions (where identified). Some key principles and concepts are: a) separating the user plane (UP) function (UPF) from the control plane (CP) function to allow independent scalability, evolution, and flexible deployment, such as centralized locations or distributed (remote) locations, b) modular functional design, such as to enable flexible and efficient network slicing, c) where applicable, defining processes (i.e., sets of interactions between network functions) as services so that their reuse is possible, and d) enabling each network function (NF) and its network function services to interact directly or indirectly with another NF and its network function services via a service communication agent, if necessary. The architecture does not exclude the use of another intermediate function to help route control plane messages (e.g., DRA).

[0177] The user plane in this patent specification can, for example, support one or more UPFs and / or user plane connections listed in the above-mentioned TS23.501 (and / or its future versions) in one or more architectures, and can be implemented using, for example, one or more processors, and / or one or more memories, and / or (multiple) routers, and / or (multiple) software modules, and / or firmware, and / or (multiple) switches, and / or user plane components, and / or (multiple) user plane nodes.

[0178] The UPF provides encapsulation and decapsulation of the GPRS tunneling protocol of the user plane (GTP U), for example, the interconnection point between the mobile infrastructure and the data network (DN).

[0179] A Protocol Data Unit (PDU) session is the anchor point for providing mobility within and between Radio Access Technologies (RATs), including sending one or more end marker packets to the gNB.

[0180] (Multiple) User Plane Functions handle the user plane path of a PDU Session. 3GPP specifications support the deployment of a single UPF or multiple UPFs for a given PDU Session. UPF selection is performed by the SMF. Details of UPF selection are given in clause 6.3.3. The number of UPFs supported for a PDU Session is not restricted.

[0181] For IPv4 type PDU sessions without multi-homing, or IPv6 type PDU sessions, or IPv4v6 type PDU sessions, when multiple PDU session anchors are used (due to the insertion of UL CL), only one IPv4 address and / or IPv6 prefix is ​​allocated to the PDU session. For IPv6 multi-homing PDU sessions, as described in Section 5.6.4.3 of TS23.501, multiple IPv6 prefixes are allocated to the PDU session. A PDU session can be associated with multiple IPv6 prefixes. This is called a multi-homing PDU session. A multi-homing PDU session provides access to a data network via more than one PDU session anchor. Different user plane paths leading to different PDU session anchors branch at a "common" UPF, which is called a UPF that supports the "branching point" function. The branch point provides forwarding of UL services toward different PDU session anchors and merging of DL services to the UE, that is, merging services toward the UE from different PDU session anchors on the link.

[0182] The features of using multiple IPv6 prefixes in a PDU session are as follows: The UPF supporting the branching point function is configured by the SMF to propagate UL traffic between PDU session anchors based on the source prefix of the PDU (the source prefix can be selected by the UE based on routing information and preferences received from the network).

[0183] The TEID is associated with a user plane node.

[0184] The CN tunnel information is the core network address of the N3 / N9 tunnel corresponding to the PDU session. It includes the TEID and IP address, which the UPF uses for the PDU session on the N3 / N9 tunnel.

[0185] The allocation and release of CN tunnel information is performed by UPF. SMF shall indicate to UPF when UPF is required to allocate / release CN tunnel information.

[0186] The UPF shall manage the CN tunnel information space. When new CN tunnel information is needed, the SMF shall request the UPF to allocate CN tunnel information for the applicable N3 / N9 reference point via N4. In response, the UPF provides the CN tunnel information to the SMF. If the PDU session is released or the UPF is deleted from the user plane path of the existing PDU session, the SMF shall request the UPF to release the CN tunnel information of the PDU session. If the corresponding N4 session is released, the UPF releases the relevant CN tunnel information.

[0187] The nodes may include user plane nodes, and / or central unit functions.

[0188] The common user plane can be considered as a (central unit) user plane node with one associated TEID. For example, "if the first PSCell and the second PSCell can be prepared, it is determined whether the two PSCells can be associated with a common (central unit) user plane (node) for forwarding data services" can be considered that the two PSCells can be associated with one user plane node associated with the same TEID.

[0189] Fig.10 An example apparatus 1000 is configured to implement the examples described herein, which may be implemented in hardware. The apparatus 1000 includes at least one processor 1002 (e.g., an FPGA and / or a CPU), at least one memory 1004 including computer program code 1005, wherein the at least one memory 1004 and the computer program code 1005 are configured to, together with the at least one processor 1002, enable the apparatus 1000 to implement circuit systems, processes, components, modules, or functions (collectively referred to as controls 1006) to implement the examples described herein, including enabling the use of each target cell CU-UP in CPA / CPC initiation.

[0190] The device 1000 optionally includes a display and / or I / O interface 1008, which can be used to display various aspects or states of the methods described herein (e.g., when one of the methods is being executed or when executed at a subsequent time), or to receive input from a user, such as using a keypad, a touch screen, a touch area, a microphone, a biometric circuit system, etc. The device 1000 includes one or more network (N / W) interfaces (I / F) 1010. (Multiple) N / WI / F 1010 can be wired and / or wireless, and communicate through the Internet / (multiple) other networks using any communication technology. (Multiple) N / WI / F 1010 can include one or more transmitters and one or more receivers. (Multiple) N / WI / F 1010 can include standard well-known components such as amplifiers, filters, frequency converters, modulators (demodulators), and encoder / decoder circuit systems and one or more antennas.

[0191] The apparatus 1000 for implementing the functions of the control 1006 may be a UE (110), a RAN node 170, a (multiple) network element 190, or Figure 3-Figure 4 and Figure 6- Fig. 9 196-3, S-GW 190-1, MME 190-2, UPF 190-3, CU-CP1796, CU-CP1896, and device 900. Device 1000 may be part of a self-organizing / optimizing network (SON) node, such as in a cloud. Device 1000 may also be distributed throughout network 100, including within device 1000 and between device 1000 and any network element (such as network control element (NCE) 190 and / or RAN node 170 and / or UE 110), including Figure 3-Figure 4 and Figure 6- Fig. 9 The network elements shown in .

[0192] like Fig.10 As shown in , interface 1012 enables data communication between various items of device 1000. For example, interface 1012 can be one or more buses, such as address, data or control buses, and can include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication devices, etc. Computer program code 1005 including control 1006 can include object-oriented software that is configured to pass data / messages between objects within computer program code 1005. Device 1000 need not include each of the features described above, or may also include other features.

[0193] Fig.11The invention discloses a method 1100 for preparing at least one PSCell of a wireless network for a user device supporting dual connectivity. At 1110, the method includes: receiving a first request to add at least two PSCells from a master node serving the user device. At 1120, the method includes: determining how many PSCells of at least two PSCells can be prepared. At 1130, the method includes: if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services. At 1140, the method includes: if the common user plane can be determined, associating a first TEID related to the common user plane and used for the two PSCells, and sending a confirmation message including an indication of the two PSCells and the associated first TEID toward the master node. At 1150, the method includes: if the common user plane cannot be determined, determining whether the network connection toward the master node supports a confirmation message including different TEIDs. At 1160, the method includes: if the network connection supports confirmation messages including different TEIDs, associating a first TEID associated with the first user plane with the first PSCell, and associating a second TEID associated with the second user plane with the second PSCell, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID toward the master node; and / or if the network connection does not support confirmation messages including different TEIDs, associating the first TEID associated with the first user plane with the first PSCell, and sending a first confirmation message including an indication of the first PSCell and the associated first TEID toward the master node, and stopping preparation of the second PSCell, or associating the second TEID associated with the second user plane with the second PSCell, and sending a second confirmation message including an indication of the second PSCell and the associated second TEID toward the master node. Method 1100 can be performed with a secondary node control unit control plane device such as SN1-CU-CP196-1.

[0194] Fig.12An example method 1200 of a network node of a cellular communication network. At 1210, the method includes: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity. At 1220, the method includes: determining how many of the at least two PSCells can be prepared. At 1230, the method includes: if the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data services. At 1240, the method includes: if the common user plane cannot be determined, associating a first TEID associated with the first user plane with the first PSCell, and associating a second TEID associated with the second user plane with the second PSCell, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID. The method 1200 can be performed with a secondary node control unit control plane device such as SN1-CU-CP 196-1.

[0195] Fig.13 An example method 1300 of a network node of a cellular communication network is provided. At 1310, the method includes receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity. At 1320, the method includes determining how many PSCells of the at least two PSCells can be prepared. At 1330, the method includes determining whether the first PSCell and the second PSCell can be associated with a common user plane for forwarding data services if the first PSCell and the second PSCell can be prepared. At 1340, the method includes associating a first TEID associated with the first user plane with the first PSCell, and sending a first confirmation message including an indication of the first PSCell and the associated first TEID toward the master node if the common user plane cannot be determined, and stopping the preparation of the second PSCell, or associating a second TEID associated with the second user plane with the second PSCell, and sending a second confirmation message including an indication of the second PSCell and the associated second TEID toward the master node. The method 1300 can be performed with a secondary node control unit control plane device such as SN1-CU-CP 196-1.

[0196] References to "computers," "processors," and the like should be understood to include not only computers having different architectures (such as single / multi-processor architectures, sequential or parallel architectures), but also special-purpose circuits, such as field-programmable gate arrays (FPGAs), application-specific circuits (ASICs), signal processing devices, and other processing circuit systems. References to computer programs, instructions, codes, and the like should be understood to include software or firmware for programmable processors, such as programmable content of hardware devices, whether instructions for a processor, or configuration settings for a fixed-function device, gate array, or programmable logic device, and the like.

[0197] The memory(s) described herein (including memory 1004) may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-transitory memory, transient memory, volatile memory, non-volatile memory, fixed memory, and removable memory. The memory(s) may include a database for storing data.

[0198] As used herein, the term "circuitry" may refer to the following: (a) hardware circuit implementations, such as implementations in analog and / or digital circuitry, and (b) combinations of circuitry and software (and / or firmware), such as, as applicable: (i) a combination of processor(s), or (ii) portions of processor(s) / software, including digital signal processor(s), software, and memory(s), which work together to enable the device to perform various functions, and (c) circuitry, such as microprocessor(s) or portions of microprocessor(s), which require software or firmware to operate, even if the software or firmware is not physically present. As a further example, as used herein, the term "circuitry" would also cover only an implementation of a processor (or processors) or portion of a processor and its accompanying software and / or firmware. For example, if applicable to the particular element, the term "circuitry" would also cover a baseband integrated circuit or application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, cellular network device, or another network device.

[0199] The following description may provide additional details of alternatives, modifications, and variations: The gNB includes, for example, a node that provides NR user plane and control plane protocol termination towards the UE and is connected to the 5GC via an NG interface, for example in accordance with Section 3.2 of 3GPP TS 38.300 V16.6.0 (2021-06) incorporated by reference.

[0200] The gNB Central Unit (gNB-CU) includes, for example, a logical node that hosts, for example, the RRC, SDAP, and PDCP protocols of the gNB, or the RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface with the gNB-DU.

[0201] The gNB distributed unit (gNB-DU) includes logical nodes such as hosting the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface with the gNB-CU.

[0202] The gNB-CU control plane (gNB-CU-CP) comprises, for example, a logical node that hosts the control plane portion of the protocols such as RRC and PDCP for an en-gNB or gNB-CU of a gNB. The gNB-CU-CP terminates the E1 interface with the gNB-CU-UP and the F1-C interface with the gNB-DU.

[0203] The gNB-CU user plane (gNB-CU-UP) includes, for example, a logical node that hosts, for example, the user plane portion of the PDCP protocol for the gNB-CU of the en-gNB, and the user plane portions of the PDCP protocol and the SDAP protocol for the gNB-CU of the gNB. The gNB-CU-UP terminates the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU, for example, according to Section 3.1 of 3GPP TS 38.401 V16.6.0 (2021-07) incorporated by reference.

[0204] There can be different functional splits between the central unit and the distributed units, called options for example:

[0205] Option 1 (Class 1A Split)

[0206] - The functional split in this option is similar to the 1A architecture in DC. RRC is located in the central unit. PDCP, RLC, MAC, physical layer, and RF are in the distributed unit.

[0207] Option 2 (Class 3C Split)

[0208] - The functional split in this option is similar to the 3C architecture in DC. RRC and PDCP are located in the central unit. RLC, MAC, physical layer, and RF are in the distributed unit.

[0209] Option 3 (split within RLC)

[0210] - Low RLC (part of the RLC function), MAC, physical layer, and RF are in the distributed unit. PDCP and High RLC (another part of the RLC function) are in the central unit.

[0211] Option 4 (RLC-MAC Split)

[0212] -MAC, physical layer, and RF are in the distributed unit. PDCP and RLC are in the central unit.

[0213] Or, for example according to section 11 of 3GPP TR 38.801 V14.0.0 (2017-03), incorporated by reference.

[0214] gNB supports different protocol layers, e.g.

[0215] Layer 1 (L1) – Physical layer.

[0216] NR's Layer 2 (L2) is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), where for example:

[0217] -The physical layer provides transport channels to the MAC sublayer;

[0218] -The MAC sublayer provides logical channels to the RLC sublayer;

[0219] -The RLC sublayer provides RLC channels to the PDCP sublayer;

[0220] -The PDCP sublayer provides radio bearers to the SDAP sublayer;

[0221] -SDAP sublayer provides QoS flow to 5GC;

[0222] - Comp. refers to header compression, and segm. refers to segmentation;

[0223] -Control channels include (BCCH, PCCH).

[0224] Layer 3 (L3) includes, for example, Radio Resource Control (RRC) according to Section 6 of 3GPP TS 38.300 V16.6.0 (2021-06), which is incorporated herein by reference.

[0225] A RAN (Radio Access Network) node or network node (such as a gNB, base station, gNB CU or gNB DU or part thereof) may be implemented using, for example, a device having at least one processor, and / or at least one memory having computer-readable instructions (computer program) configured to support and / or provide and / or process CU and / or DU related functions and / or features, and / or at least one protocol (sub) layer of a RAN (Radio Access Network), such as Layer 2 and / or Layer 3.

[0226] The gNB CU and gNB DU parts may be collocated or physically separated. The gNB DU may be even further split, for example into two parts, for example one part including processing equipment and the other part including antennas. The Central Unit (CU) may also be referred to as BBU / REC / RCC / C-RAN / V-RAN, O-RAN, or a part thereof. The Distributed Unit (DU) may also be referred to as RRH / RRU / RE / RU, or a part thereof.

[0227] The gNB-DU supports one or more cells and can thus serve as, for example, a serving cell for a user equipment (UE).

[0228] A user equipment (UE) may include a wireless or mobile device, a device having a radio interface that interacts with a RAN (Radio Access Network), a smartphone, an in-vehicle device, an IoT device, an M2M device, or other device. Such a UE or device may include: at least one processor; and at least one memory including a computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to perform at least certain operations, such as an RRC connection with the RAN. The UE is, for example, configured to generate a message (e.g., including a cell ID) to be sent to the RAN via radio (e.g., to reach a serving cell and communicate with it). The UE may generate, send, and receive an RRC message containing one or more RRC PDUs (packet data units).

[0229] The UE may have different states (e.g., according to 3GPP TS 38.331 V16.5.0 (2021-06) Sections 42.1 and 4.4, incorporated herein by reference).

[0230] When the RRC connection has been established, the UE is in, for example, an RRC_CONNECTED state or an RRC_INACTIVE state.

[0231] In the RRC_CONNECTED state, the UE can:

[0232] -Store AS context;

[0233] -Transmit unicast data to / from UE;

[0234] - monitoring a control channel associated with a shared data channel to determine whether data is scheduled for the data channel;

[0235] -Provide channel quality and feedback information;

[0236] -Perform neighbor cell measurements and measurement reporting;

[0237] The RRC protocol includes the following main functions:

[0238] -RRC connection control;

[0239] - Measurement configuration and reporting;

[0240] - Establish / modify / release measurement configurations (e.g., intra-frequency, inter-frequency, and inter-RAT measurements);

[0241] -Measurement of gap creation and release;

[0242] - Measurement report.

[0243] Multicast operation (also includes bicast operation (original + copy / duplicate):

[0244] In the downlink, the multicast operation includes sending a message to a single user equipment (UE) from at least two different cells, for example, sending a message from a first serving cell to the UE, such as an RRC message or an RRC PDU (packet data unit), and sending a copy or repetition of the message or at least its payload, such as an RRC payload or an RRC SDU (service data unit), to the UE from a secondary cell. In this way, the UE receives the "same" message via at least two different radio links, for example at least twice. If one radio link is interfered, the message is received at least once. The message and its repetitions are preferably sent simultaneously or quickly one after another, for example within milliseconds. The message can be a control plane signaling message, such as an RRC message including an RRC payload, or a user plane message including data. The message can include a header and a payload, and can also include a footer.

[0245] In the uplink, the multicast operation includes sending a message from a single user equipment (UE) to at least two different cells, such as sending a message (e.g., an acknowledgement (ACK) message) from the UE to the first serving cell, and / or sending a message or at least a copy or repetition of its content from the UE to the secondary cell. The message and its repetitions are preferably sent simultaneously or quickly one after another, such as within milliseconds. The message can be a control plane signaling message, such as an ACK message, or a user plane message including data.

[0246] With respect to the description in this document, multicast may be referred to as a repeated operation since multicast is typically point-to-multipoint, whereas as described herein, there are two unicast messages transmitted via different radio links, one unicast message being the original message and the other unicast message being a copy / repetition thereof (at least the payload), however, as used in this document, this concept is also referred to as multicast.

[0247] Among the examples, the following examples 1 - 34 are provided herein. Features of the dependent device claims / examples may also be added to the method claims / examples.

[0248] Example 1: A method for preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, wherein the method comprises:

[0249] receiving a first request to add at least two PSCells from a master node serving a user equipment,

[0250] Determine how many of the at least two PSCells can be prepared,

[0251] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic,

[0252] If a common user plane can be determined, a first TEID related to the common user plane and used for the two PSCells is associated, and a confirmation message including an indication of the two PSCells and the associated first TEID is sent towards the master node,

[0253] If a common user plane cannot be determined, determining whether the network connection towards the primary node supports confirmation messages including different TEIDs, and

[0254] If the network connection supports confirmation messages including different TEIDs, a first TEID associated with the first user plane is associated with the first PSCell, and a second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or

[0255] If the network connection does not support confirmation messages that include different TEIDs, then

[0256] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0257] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0258] Example 2. The method according to claim 1, wherein the method further comprises:

[0259] If the network connection does not support confirmation messages including different TEIDs, a first confirmation message is sent, the first confirmation message also including: an indication that at least one additional PSCell can be prepared, or an indication that preparation of the PSCell is not complete, or an indication that an additional add request is requested.

[0260] Example 3. The method according to Example 2, wherein the method further comprises:

[0261] A second request to add at least an additional PSCell is received.

[0262] Example 4. The method according to any one of Examples 2 to 3, wherein the method further comprises:

[0263] If the network connection does not support confirmation messages including different TEIDs, a second confirmation message is sent, the second confirmation message also including: an indication that another PSCell cannot be prepared, or an indication that preparation of the PSCell is complete.

[0264] Example 5. The method according to any one of Examples 1 to 4, wherein the method further comprises:

[0265] The first TEID and / or the second TEID are related to the downlink data service.

[0266] Example 6. The method according to any one of Examples 1 to 5, wherein the method further comprises:

[0267] TEID corresponds to GTP-TEID (GPRS Tunneling Protocol-Tunnel Endpoint Identifier).

[0268] Example 7. The method according to any one of Examples 1 to 6, wherein the method further comprises:

[0269] The first request is related to a conditional PSCell change (CPC), or a conditional PSCell addition or change (CPAC).

[0270] Example 8. An apparatus for a network node of a cellular communication network, comprising:

[0271] at least one processor; and

[0272] at least one non-transitory memory including computer program code, wherein the at least one non-transitory memory and the computer program code are configured to, with at least one processor, cause the apparatus to at least:

[0273] receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0274] Determine how many of the at least two PSCells can be prepared,

[0275] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0276] If the common user plane cannot be determined, the first TEID related to the first user plane is associated with the first PSCell, and the second TEID related to the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

[0277] Example 9. The apparatus of Example 8, wherein the apparatus further comprises:

[0278] The first TEID and / or the second TEID are related to the downlink data service.

[0279] Example 10. The device according to any one of Examples 8 to 9, wherein the device further comprises:

[0280] TEID corresponds to GTP-TEID (GPRS Tunneling Protocol-Tunnel Endpoint Identifier).

[0281] Example 11. The device according to any one of Examples 8 to 9, wherein the device further comprises:

[0282] The first request is related to a conditional PSCell change (CPC), or a conditional PSCell addition or change (CPAC).

[0283] Example 12. The apparatus of any one of Examples 8 to 11, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0284] If the common user plane cannot be determined, then

[0285] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0286] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0287] Example 13. The apparatus of any one of Examples 8 to 12, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0288] Determine whether the network connection towards the master node supports confirmation messages including different TEIDs,

[0289] If the network connection does not support confirmation messages including different TEIDs, a first confirmation message is sent, the first confirmation message also including: an indication that at least one additional PSCell can be prepared, or an indication that preparation of the PSCell is not complete, or an indication that an additional add request is requested.

[0290] Example 14. The apparatus of Example 13, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0291] A second request to add at least an additional PSCell is received.

[0292] Example 15. The apparatus of Example 13, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0293] If the network connection does not support confirmation messages including different TEIDs, a second confirmation message is sent, the second confirmation message also including: an indication that another PSCell cannot be prepared, or an indication that preparation of the PSCell is complete.

[0294] Example 16. The apparatus of any one of Examples 8 to 15, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0295] If a common user plane can be determined, a first TEID related to the common user plane and for both PSCells is associated and a confirmation message including an indication of the two PSCells and the associated first TEID is sent towards the master node.

[0296] Example 17. An apparatus for a network node of a cellular communication network, comprising:

[0297] at least one processor; and

[0298] at least one non-transitory memory including computer program code, wherein the at least one non-transitory memory and the computer program code are configured to, with at least one processor, cause the apparatus to at least:

[0299] receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0300] Determine how many of the at least two PSCells can be prepared,

[0301] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0302] If the common user plane cannot be determined, then

[0303] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0304] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0305] Example 18. The apparatus of Example 17, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0306] Determine whether the network connection towards the master node supports confirmation messages including different TEIDs,

[0307] If the network connection does not support confirmation messages including different TEIDs, a first confirmation message is sent, the first confirmation message also including: an indication that at least one additional PSCell can be prepared, or an indication that preparation of the PSCell is not complete, or an indication that an additional add request is requested.

[0308] Example 19. The apparatus of Example 18, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0309] A second request to add at least an additional PSCell is received.

[0310] Example 20. The apparatus of any of Examples 18 to 19, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0311] If the network connection does not support confirmation messages including different TEIDs, a second confirmation message is sent, the second confirmation message also including: an indication that another PSCell cannot be prepared, or an indication that preparation of the PSCell is complete.

[0312] Example 21. The device according to any one of Examples 17 to 20, wherein the device further comprises:

[0313] The first TEID and / or the second TEID are related to the downlink data service.

[0314] Example 22. The device according to any one of Examples 17 to 21, wherein the device further comprises:

[0315] TEID corresponds to GTP-TEID (GPRS Tunneling Protocol-Tunnel Endpoint Identifier).

[0316] Example 23. The device according to any one of Examples 17 to 22, wherein the device further comprises:

[0317] The first request is related to a conditional PSCell change (CPC), or a conditional PSCell addition or change (CPAC).

[0318] Example 24. The apparatus of any one of Examples 17 to 23, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0319] If the common user plane cannot be determined, the first TEID related to the first user plane is associated with the first PSCell, and the second TEID related to the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

[0320] Example 25. The apparatus of any one of Examples 17 to 24, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least:

[0321] If the common user plane can be determined, a first TEID related to the common user plane and for both PSCells is associated and a confirmation message including an indication of the two PSCells and the associated first TEID is sent towards the master node.

[0322] Example 26. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations comprising:

[0323] Preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity,

[0324] receiving a first request to add at least two PSCells from a master node serving a user equipment,

[0325] Determine how many of the at least two PSCells can be prepared,

[0326] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic,

[0327] If a common user plane can be determined, a first TEID related to the common user plane and used for the two PSCells is associated, and a confirmation message including an indication of the two PSCells and the associated first TEID is sent towards the master node,

[0328] If a common user plane cannot be determined, determining whether the network connection towards the primary node supports confirmation messages including different TEIDs, and

[0329] If the network connection supports confirmation messages including different TEIDs, a first TEID associated with the first user plane is associated with the first PSCell, and a second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or

[0330] If the network connection does not support confirmation messages that include different TEIDs, then

[0331] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0332] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0333] Example 27. An apparatus comprising:

[0334] means for preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity,

[0335] means for receiving a first request to add at least two PSCells from a master node serving a user equipment,

[0336] means for determining how many PSCells of at least two PSCells can be prepared,

[0337] means for determining whether the first PSCell and the second PSCell can be associated with a common user plane for forwarding data traffic if the first PSCell and the second PSCell can be prepared,

[0338] means for associating, if a common user plane can be determined, a first TEID related to the common user plane and for the two PSCells and sending towards the master node a confirmation message including an indication of the two PSCells and the associated first TEID,

[0339] means for determining whether the network connection towards the primary node supports confirmation messages including different TEIDs if a common user plane cannot be determined, and

[0340] If the network connection supports confirmation messages including different TEIDs, a first TEID associated with the first user plane is associated with the first PSCell, and a second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or

[0341] If the network connection does not support confirmation messages that include different TEIDs, then

[0342] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0343] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0344] Example 28. An apparatus comprising:

[0345] at least one processor; and

[0346] at least one non-transitory memory including computer program code, wherein the at least one non-transitory memory and the computer program code are configured to, with at least one processor, cause the apparatus to at least:

[0347] Preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity,

[0348] receiving a first request to add at least two PSCells from a master node serving a user equipment,

[0349] Determine how many of the at least two PSCells can be prepared,

[0350] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic,

[0351] If a common user plane can be determined, a first TEID related to the common user plane and used for the two PSCells is associated, and a confirmation message including an indication of the two PSCells and the associated first TEID is sent towards the master node,

[0352] If a common user plane cannot be determined, determining whether the network connection towards the primary node supports confirmation messages including different TEIDs, and

[0353] If the network connection supports confirmation messages including different TEIDs, a first TEID associated with the first user plane is associated with the first PSCell, and a second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or

[0354] If the network connection does not support confirmation messages that include different TEIDs, then

[0355] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0356] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0357] Example 29. A method for a network node of a cellular communication network, comprising:

[0358] receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0359] Determine how many of the at least two PSCells can be prepared,

[0360] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0361] If the common user plane cannot be determined, the first TEID related to the first user plane is associated with the first PSCell, and the second TEID related to the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

[0362] Example 30. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations on a network node of a cellular communication network, the operations comprising:

[0363] receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0364] Determine how many of the at least two PSCells can be prepared,

[0365] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0366] If the common user plane cannot be determined, the first TEID related to the first user plane is associated with the first PSCell, and the second TEID related to the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

[0367] Example 31. An apparatus for a network node of a cellular communication network, comprising:

[0368] means for receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0369] means for determining how many PSCells of at least two PSCells can be prepared,

[0370] means for determining, if the first PSCell and the second PSCell can be prepared, whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0371] A component for associating a first TEID related to a first user plane with a first PSCell, and associating a second TEID related to a second user plane with a second PSCell, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID, when a common user plane cannot be determined.

[0372] Example 32. A method for a network node of a cellular communication network, comprising:

[0373] receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0374] Determine how many of the at least two PSCells can be prepared,

[0375] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0376] If the common user plane cannot be determined, then

[0377] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0378] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0379] Example 33. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations of a network node of a cellular communication network, the operations comprising:

[0380] receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0381] Determine how many of the at least two PSCells can be prepared,

[0382] If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0383] If the common user plane cannot be determined, then

[0384] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0385] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0386] Example 34. An apparatus for a network node of a cellular communication network, comprising:

[0387] means for receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity,

[0388] means for determining how many PSCells of at least two PSCells can be prepared,

[0389] means for determining, if the first PSCell and the second PSCell can be prepared, whether the two PSCells can be associated with a common user plane for forwarding data traffic, and

[0390] Components for performing the following operations when the public user plane cannot be determined:

[0391] associating a first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or

[0392] A second TEID related to the second user plane is associated with the second PSCell and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

[0393] In the figure, the arrows between the individual boxes indicate the operational couplings between them, and the direction of data flow over these couplings.

[0394] It should be understood that the above description is illustrative only. Those skilled in the art may design various alternatives and modifications. For example, the features described in the various dependent claims may be combined with each other in any suitable combination. In addition, the features from the above-mentioned different embodiments may be selectively combined into new embodiments. Therefore, this specification is intended to include all such alternatives, modifications, and variations that fall within the scope of the appended claims.

[0395] The following acronyms and abbreviations that may appear in the specification and / or drawings are defined as follows (the abbreviations may be appended together or with other words / characters, for example by using a dash / hyphen, such as in gNB-CU-CP formed by appending the abbreviations gNB and CU-CP, or by appending "s" after multiple abbreviations such as PDU):

[0396] 1A: 3GPP configuration where user plane data is split in the core network

[0397] 3C: 3GPP configuration where user plane data is split in the MeNB

[0398] 3GPP: Third Generation Partnership Project

[0399] 4G: Fourth Generation

[0400] 5G: Fifth Generation

[0401] 5GC: 5G core network

[0402] ack or ACK: Acknowledgement

[0403] AMF: Access and Mobility Management Function

[0404] AS: Access layer

[0405] ASIC: Application-Specific Integrated Circuit

[0406] BBU: Baseband Unit

[0407] BCCH: Broadcast Control Channel

[0408] BWP: Bandwidth Part

[0409] C: conditional in an existential context

[0410] C: Control or control surface

[0411] CL: Classifier

[0412] CG: Cell Group

[0413] CGI: Community Global Identity

[0414] CHO: Conditional Switch

[0415] CN: Core Network

[0416] Comp.: Compression

[0417] config: configuration

[0418] CP: Control plane

[0419] CPA: Conditional PSCell Addition

[0420] CPAC: Conditional PSCell addition or change

[0421] CPC: Conditional PSCell Change

[0422] CPU: Central Processing Unit

[0423] C-RAN: Centralized, idle, cloud, and / or collaborative RAN

[0424] CU: Central Unit or Centralized Unit

[0425] CU-CP: Central Unit Control Panel

[0426] CU-UP: Central Unit User Plane

[0427] DC: Dual Connect

[0428] DL: Downlink

[0429] DN: Data Network

[0430] DRB: Data Radio Bearer

[0431] DRA: Diameter Routing Agent

[0432] DSP: Digital Signal Processor

[0433] DU: Distributed Unit

[0434] E1: Interface that connects the decomposed user plane to the decomposed control plane (e.g., point-to-point interface between gNB-CU-CP and gNB-CU-UP)

[0435] eMBB: enhanced mobile broadband

[0436] eNB: Evolved Node B (e.g., LTE base station)

[0437] EN-DC: E-UTRA-NR Dual Connectivity

[0438] en-gNB: A node that provides NR user plane and control plane protocol termination towards the UE and acts as a secondary node in EN-DC

[0439] E-RAB: E-UTRAN Radio Access Bearer

[0440] E-UTRA: Evolved Universal Terrestrial Radio Access, also known as LTE radio access technology

[0441] E-UTRAN: Evolved Universal Terrestrial Radio Access Network

[0442] F1: Interface between CU and DU, such as F1-C or F1-U

[0443] FPGA: Field Programmable Gate Array

[0444] GBR: Guaranteed Bit Rate

[0445] gNB: A base station for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination towards the UE and is connected to the 5GC via the NG interface GPRS: General Packet Radio Service

[0446] GTP: GPRS Tunneling Protocol

[0447] HO: Handover

[0448] IAB: Integrated Access and Backhaul

[0449] ID: Identifier

[0450] IE: Information Element

[0451] I / F: Interface

[0452] I / O: Input / Output

[0453] IP: Internet Protocol

[0454] IoT: Internet of Things

[0455] L1: Layer 1

[0456] L2: Layer 2

[0457] L3: Layer 3

[0458] LCID: Logical Channel ID

[0459] LMF: Location Management Function

[0460] LTE: Long Term Evolution (4G)

[0461] M: Primary (e.g., M-NG-RAN) or mandatory, depending on the context

[0462] M2M: Machine to Machine

[0463] MAC: Media Access Control

[0464] MCG: Master Cell Group

[0465] MeNB: Master eNB

[0466] MME: Mobility Management Entity

[0467] mMTC: massive machine type communications

[0468] MN: Master Node

[0469] MR: Multi-RAT or Measurement Report, depending on the context

[0470] N3: Interface that conveys user data from RAN to user plane functions

[0471] N4: Interface connecting UPF and SMF

[0472] N9: Interface between two UPFs

[0473] NCE: Network Control Element

[0474] NF: Network Function

[0475] ng or NG: New Generation

[0476] ng-eNB: Next-generation eNB

[0477] NG-RAN: Next Generation Radio Access Network

[0478] NG-U: defines the interface between NG-RAN nodes and UPF

[0479] NR: New Radio (5G)

[0480] N / W: Network

[0481] O: Optional

[0482] O-RAN: Open Radio Access Network

[0483] PCCH: Paging Control Channel

[0484] PCell: Primary cell

[0485] PDCP: Packet Data Convergence Protocol

[0486] PDU: Protocol Data Unit

[0487] PHY: Physical layer

[0488] Prep or PREP: Preparation

[0489] PSCell: Primary SCG cell

[0490] QoS: Quality of Service

[0491] RAN: Radio Access Network

[0492] RAN#: Radio Layer# or 3GPP Technical Specification Group Radio Access Network WG# (e.g., RAN1)

[0493] RAT: Radio Access Technology

[0494] RCC: Radio Resource Control Connection

[0495] Re.: Release

[0496] RE: Radio equipment

[0497] REC: Radio Equipment Controller

[0498] Reconfig: Reconfigure

[0499] Rel: version

[0500] RF: Radio Frequency

[0501] RLC: Radio Link Control

[0502] RRC: Radio Resource Control (protocol)

[0503] RRH: Remote Radio Head

[0504] RRU: Remote Radio Unit

[0505] RSRP: Reference Signal Received Power

[0506] RU: Radio Unit

[0507] Rx: Receive or Receiver or Receiving

[0508] S: Secondary (e.g., S-NG-RAN)

[0509] S1: Interface between RAN node and MME or S-GW

[0510] S1-U: defines the user plane external interface between LTE eNB and LTE S-GW

[0511] SCG: Secondary Cell Group

[0512] SDAP: Service Data Adaptation Protocol

[0513] SDU: Service Data Unit

[0514] segm.: segmentation

[0515] SgNB or SgNB: Secondary gNB

[0516] SGW or S-GW: Serving Gateway

[0517] SMF: Session Management Function

[0518] SN: Secondary Node

[0519] SON: Self-Organizing / Optimizing Network

[0520] SRB: Signalling Radio Bearer

[0521] TEID: Tunnel Endpoint Identifier

[0522] TNL: Transport Network Layer

[0523] TR: Technical Report

[0524] TRP: Transmission Reception Point

[0525] TS: Technical Specification

[0526] Tx: Send or Transmitter or Transmit

[0527] U: User or User Plane

[0528] UE: User Equipment (e.g., wireless device, typically a mobile device)

[0529] UL: Uplink

[0530] UP: User plane

[0531] UPF: User Plane Function

[0532] URLLC: Ultra-Reliable Low-Latency Communications

[0533] Uu: air interface between UE and RAN network nodes

[0534] v or V: version

[0535] V-RAN: Virtual Radio Access Network

[0536] WG: Working Group

[0537] X2: Interface between two radio nodes (e.g., two eNBs)

[0538] X2AP: X2 Application Protocol

[0539] Xn: Interface between two NG-RAN nodes

[0540] XnAP: Xn Application Protocol

Claims

1. A method for preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, wherein the method comprises: receiving a first request to add at least two PSCells from a master node serving the user equipment, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, If a common user plane can be determined, associating a first TEID related to the common user plane and for two PSCells, and sending a confirmation message including an indication of the two PSCells and the associated first TEID towards the master node, If a common user plane cannot be determined, determining whether the network connection towards the primary node supports confirmation messages including different TEIDs, and If the network connection supports confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or If the network connection does not support confirmation messages including different TEIDs, then associating the first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

2. The method according to claim 1, wherein the method further comprises: If the network connection does not support confirmation messages including different TEIDs, the first confirmation message is sent, and the first confirmation message also includes: an indication that at least one additional PSCell can be prepared, or an indication that preparation of the PSCell is not complete, or an indication that an additional addition request is requested.

3. The method according to claim 2, wherein the method further comprises: A second request to add at least an additional PSCell is received.

4. The method according to any one of claims 2 to 3, wherein the method further comprises: If the network connection does not support confirmation messages including different TEIDs, the second confirmation message is sent, and the second confirmation message also includes: an indication that another PSCell cannot be prepared, or an indication that preparation of the PSCell is complete.

5. The method according to any one of claims 1 to 4, wherein the method further comprises: The first TEID and / or the second TEID are related to downlink data services.

6. The method according to any one of claims 1 to 5, wherein the method further comprises: TEID corresponds to GTP-TEID (GPRS Tunneling Protocol-Tunnel Endpoint Identifier).

7. The method according to any one of claims 1 to 6, wherein the method further comprises: The first request is related to a conditional PSCell change (CPC) or a conditional PSCell addition or change (CPAC).

8. An apparatus for a network node of a cellular communication network, comprising: at least one processor; as well as at least one non-transitory memory comprising computer program code, wherein the at least one non-transitory memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and If the common user plane cannot be determined, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

9. The device according to claim 8, wherein the device further comprises: The first TEID and / or the second TEID are related to downlink data services.

10. The device according to any one of claims 8 to 9, wherein the device further comprises: TEID corresponds to GTP-TEID (GPRS Tunneling Protocol-Tunnel Endpoint Identifier).

11. The device according to any one of claims 8 to 9, wherein the device further comprises: The first request is related to a conditional PSCell change (CPC) or a conditional PSCell addition or change (CPAC).

12. The apparatus of any one of claims 8 to 11, wherein the at least one non-transitory memory and the computer program code are further configured to, together with the at least one processor, cause the apparatus to at least: If the common user plane cannot be determined, then associating the first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards a master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

13. The apparatus of any one of claims 8 to 12, wherein the at least one non-transitory memory and the computer program code are further configured to, together with the at least one processor, cause the apparatus to at least: determining whether the network connection towards the master node supports confirmation messages including different TEIDs, If the network connection does not support confirmation messages including different TEIDs, sending the first confirmation message, the first confirmation message further comprising: An indication that at least one further PSCell can be prepared, or an indication that preparation of a PSCell is not complete, or an indication that a further add request is requested.

14. The apparatus of claim 13, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: A second request to add at least an additional PSCell is received.

15. The apparatus of claim 13, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: If the network connection does not support a confirmation message including a different TEID, sending a second confirmation message, the second confirmation message further comprising: An indication that another PSCell cannot be prepared, or an indication that preparation of the PSCell is complete.

16. The apparatus of any one of claims 8 to 15, wherein the at least one non-transitory memory and the computer program code are further configured to, together with the at least one processor, cause the apparatus to at least: If the common user plane can be determined, the first TEID related to the common user plane and for two PSCells is associated and a confirmation message including an indication of the two PSCells and the associated first TEID is sent towards the master node.

17. An apparatus for a network node of a cellular communication network, comprising: at least one processor; as well as at least one non-transitory memory comprising computer program code, wherein the at least one non-transitory memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and If the common user plane cannot be determined, then associating a first TEID associated with a first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards a master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

18. The apparatus of claim 17, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: determining whether the network connection towards the master node supports confirmation messages including different TEIDs, If the network connection does not support confirmation messages including different TEIDs, sending the first confirmation message, the first confirmation message further comprising: An indication that at least one further PSCell can be prepared, or an indication that preparation of a PSCell is not complete, or an indication that a further add request is requested.

19. The apparatus of claim 18, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: A second request to add at least an additional PSCell is received.

20. The apparatus of any one of claims 18 to 19, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: If the network connection does not support confirmation messages including different TEIDs, sending the second confirmation message, the second confirmation message further comprising: An indication that another PSCell cannot be prepared, or an indication that preparation of the PSCell is complete.

21. The device according to any one of claims 17 to 20, wherein the device further comprises: The first TEID and / or the second TEID are related to downlink data services.

22. The device according to any one of claims 17 to 21, wherein the device further comprises: TEID corresponds to GTP-TEID (GPRS Tunneling Protocol-Tunnel Endpoint Identifier).

23. The device according to any one of claims 17 to 22, wherein the device further comprises: The first request is related to a conditional PSCell change (CPC) or a conditional PSCell addition or change (CPAC).

24. The apparatus of any one of claims 17 to 23, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: If the common user plane cannot be determined, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

25. The apparatus of any one of claims 17 to 24, wherein the at least one non-transitory memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: If the common user plane can be determined, the first TEID related to the common user plane and for two PSCells is associated and a confirmation message including an indication of the two PSCells and the associated first TEID is sent towards the master node.

26. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations comprising: Preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, receiving a first request to add at least two PSCells from a master node serving the user equipment, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, If a common user plane can be determined, associating a first TEID related to the common user plane and for two PSCells, and sending a confirmation message including an indication of the two PSCells and the associated first TEID towards the master node, If a common user plane cannot be determined, determining whether the network connection towards the primary node supports confirmation messages including different TEIDs, and If the network connection supports confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or If the network connection does not support confirmation messages including different TEIDs, then associating the first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

27. An apparatus comprising: means for preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, means for receiving a first request to add at least two PSCells from a master node serving the user equipment, means for determining how many of the at least two PSCells can be prepared, means for determining whether the first PSCell and the second PSCell can be associated with a common user plane for forwarding data traffic if the first PSCell and the second PSCell can be prepared, means for associating a first TEID related to the common user plane and for two PSCells if the common user plane can be determined and sending a confirmation message towards the master node including an indication of the two PSCells and the associated first TEID, means for determining, if a common user plane cannot be determined, whether the network connection towards the primary node supports confirmation messages including different TEIDs, and If the network connection supports confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or If the network connection does not support confirmation messages including different TEIDs, then associating the first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

28. An apparatus comprising: at least one processor; as well as at least one non-transitory memory comprising computer program code, wherein the at least one non-transitory memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: Preparing at least one PSCell of a wireless network for a user equipment supporting dual connectivity, receiving a first request to add at least two PSCells from a master node serving the user equipment, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, If a common user plane can be determined, associating a first TEID related to the common user plane and for two PSCells, and sending a confirmation message including an indication of the two PSCells and the associated first TEID towards the master node, If a common user plane cannot be determined, determining whether the network connection towards the primary node supports confirmation messages including different TEIDs, and If the network connection supports confirmation messages including different TEIDs, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent towards the master node; and / or If the network connection does not support confirmation messages including different TEIDs, then associating the first TEID associated with the first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards the master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

29. A method for a network node of a cellular communication network, comprising: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and If the common user plane cannot be determined, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

30. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations on a network node of a cellular communication network, the operations comprising: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and If the common user plane cannot be determined, the first TEID associated with the first user plane is associated with the first PSCell, and the second TEID associated with the second user plane is associated with the second PSCell, and a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID is sent.

31. An apparatus for a network node of a cellular communication network, comprising: means for receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, means for determining how many of the at least two PSCells can be prepared, means for determining, if the first PSCell and the second PSCell can be prepared, whether the two PSCells can be associated with a common user plane for forwarding data traffic, and A component for associating the first TEID related to the first user plane with the first PSCell, and associating the second TEID related to the second user plane with the second PSCell when the common user plane cannot be determined, and sending a confirmation message including an indication of the first PSCell and the associated first TEID, and the second PSCell and the associated second TEID.

32. A method for a network node of a cellular communication network, comprising: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and If the common user plane cannot be determined, then associating a first TEID associated with a first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards a master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

33. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations of a network node of a cellular communication network, the operations comprising: receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, determining how many PSCells of the at least two PSCells can be prepared, If the first PSCell and the second PSCell can be prepared, determining whether the two PSCells can be associated with a common user plane for forwarding data traffic, and If the common user plane cannot be determined, then associating a first TEID associated with a first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards a master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.

34. An apparatus for a network node of a cellular communication network, comprising: means for receiving a first request to add at least two PSCells for a user equipment supporting dual connectivity, means for determining how many of the at least two PSCells can be prepared, means for determining, if the first PSCell and the second PSCell can be prepared, whether the two PSCells can be associated with a common user plane for forwarding data traffic, and Components for performing the following operations when the public user plane cannot be determined: associating a first TEID associated with a first user plane with the first PSCell and sending a first confirmation message including an indication of the first PSCell and the associated first TEID towards a master node, and stopping preparation of the second PSCell, or A second TEID related to a second user plane is associated with the second PSCell, and a second confirmation message including an indication of the second PSCell and the associated second TEID is sent towards the master node.