Coordinated segmentation between multiple nodes in dual connectivity

Abstract

A method performed by a first node (111). The method is used to process a message destined for a third node (113). The message includes content from at least a first second node (114) among one or more second nodes (112). The first node (111) coordinates with one or more second nodes (112) to process radio communication with the third node (113). The first node (111) sends (809) a message to the third node (113), which may or may not be segmented. Whether the message is sent segmented or not is based on: i) whether the size of the message exceeds a size limit, ii) whether the third node (113) supports message segmentation, iii) whether the first node (111) supports message segmentation, and iv) whether at least a first second node (114) among one or more second nodes (112) supports message segmentation.

Description

Technical Field

[0001] This disclosure generally relates to a first node and a method executed thereon for processing messages destined for a third node. This disclosure also generally relates to a second node and a method executed thereon for processing messages destined for a third node. This disclosure also generally relates to a computer program and a computer-readable storage medium on which a computer program for performing these methods is stored. Background Technology

[0002] Nodes within a communication network can be wireless devices such as user equipment (UE), station (STA), mobile terminal, wireless terminal, terminal, and / or mobile station (MS). Wireless devices are enabled to conduct wireless communication within a cellular communication network or wireless communication system (sometimes also referred to as a cellular radio system, cellular system, or cellular network). Communication can be performed via a radio access network (RAN) and possibly via one or more core networks included within the communication network, for example, between two wireless devices, between a wireless device and a regular telephone, and / or between a wireless device and a server. Wireless devices can also be referred to (to name just a few other examples) as mobile phones, cellular phones, laptop computers, or wirelessly capable tablets. In the current context, wireless devices can be, for example, portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile devices capable of transmitting voice and / or data via the RAN to another entity (e.g., another terminal or server).

[0003] Nodes can also be network nodes, such as radio network nodes, such as transport points (TPs). Wireless communication network coverage can be divided into geographical areas of cell regions, each served by network nodes such as base stations (BSs) (e.g., radio base stations (RBSs)). Base stations may sometimes be referred to as gNBs, evolved Node Bs (“eNBs”), “eNodeBs”, “NodeBs”, “B-nodes”, or BTSs (Base Transceiver Stations), depending on the technology and terminology used. Based on transmit power and thus also on cell size, base stations can have different classes, such as wide-area base stations, mid-range base stations, local base stations, and home base stations. A cell is a geographical area of ​​radio coverage provided by a base station at a base station site. A base station located at a base station site can serve one or more cells. Furthermore, each base station can support one or more communication technologies. Communication networks can also be non-cellular systems, including network nodes that can serve receiving nodes (e.g., wireless devices) using a serving beam. In the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations (which may be referred to as eNodeBs or even eNBs) can be directly connected to one or more core networks. In the context of this disclosure, the expression downlink (DL) can be used to describe the transmission path from a base station to a wireless device.

[0004] From a radio perspective, the so-called 5G system is beginning to be standardized in 3GPP, and the so-called New Radio (NR) is the name of the radio interface. The NR architecture is being discussed within 3GPP. In the current concept, gNB stands for NR BS, where one NR BS can correspond to one or more transmit / receive points. The uplink (UL) indicates that it can be used for the transmission path in the opposite direction (i.e., from the wireless device to the base station). The standardization organization 3GPP is currently specifying the new radio interface (referred to as NR or 5G-UTRA) and the fifth-generation (5G) packet core network (which can be referred to as the next-generation (NG) core network, or simply NG-CN, NGC, or 5G CN).

[0005] RRC segmentation

[0006] Segmentation of Radio Resource Control (RRC) messages is being introduced for 3GPP Release 16. Segmentation may be necessary to support the transmission of large RRC messages that may exceed the Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size limit, which may be 9000 bytes for NR and 8188 bytes for LTE [3GPP TS37.873 Release 16.0.0]. Other (R)ANs may have additional limitations.

[0007] For example, RRC messages that are expected to be sent in the UL and contain UE radio capability signaling may exceed the above limits. RRC messages that are also expected to be sent in the DL and contain UE configuration may also exceed the above limits.

[0008] Dual connection

[0009] Figure 1 This is a schematic diagram illustrating several architectural options for Multiple Radio Dual Connectivity (MR-DC) as described in 3GPP Release 15 [2]. Currently, 3GPP Release 15 supports up to seven architectural options, which can include both standalone and non-standalone scenarios. Figure 1 The diagram only shows options 1, 2, 3, 4, 5, and 7. Option 1 corresponds to standalone LTE connected to the EPC, option 2 corresponds to standalone NR connected to the 5GCN or corresponds to NR-NR DC, option 3 corresponds to LTE-NR Dual Connectivity (DC) (EN-DC) connected to the EPC, option 4 corresponds to NR-E-UTRA Dual Connectivity (NE-DC), option 5 corresponds to LTE (eLTE or LTE-5GC) connected to the 5GCN, and option 7 corresponds to E-UTRA-NR Dual Connectivity (NGEN-DC). In principle, NR and LTE can be deployed without any interoperability, which is represented by NR standalone (SA) operation, i.e., an eNB can be connected to the EPC, and a gNB in ​​NR can be connected to the 5G core network (5GC), with no interconnection between them, as shown in options 1 and 2 in the diagram, respectively. On the other hand, the first supported NR version is the so-called Evolved Universal Terrestrial Radio Access Network (E-UTRAN)-NR Dual Connectivity (EN-DC), as shown in option 3. In such a deployment, dual connectivity between NR and LTE can be applied, with LTE acting as the primary node and NR as the secondary node. The RAN node (gNB) supporting NR may not have a control plane connection to the EPC core network, but may instead rely on LTE as the primary node (MeNB). This is also known as "non-standalone NR". Note that in this case, the functionality of the NR cell may be limited, and it may be used as an enhancer and / or diversity tributary for connected-mode UEs, while RRC_IDLE UEs cannot camp on these NR cells. With the introduction of 5GC, other options are also effective. As mentioned above, Option 2 supports standalone NR deployment, where the gNB can be connected to the 5GC. Similarly, LTE can also be connected to the 5GC (also known as eLTE, E-UTRA / 5GC, or LTE / 5GC) using Option 5, and the node can be referred to as an ng-eNB. In these cases, both NR and LTE can be considered part of the NG-RAN, and both the ng-eNB and gNB can be referred to as NG-RAN nodes.

[0010] In this document, particular attention can be paid to the architecture options that support dual connectivity, specifically: Option 3 (which is EN-DC), Option 4 (which is NE-DC), and Option 7 (which is NGEN-DC). Options 4 and 7 are other variations of dual connectivity between LTE and NR, which will be standardized as part of the NG-RAN connected to 5GC, represented by Multi-Radio Dual Connectivity (MR-DC).

[0011] Because the migration of these options may vary from operator to operator, it is possible to have multiple options deployed in parallel within the same network. For example, in the same network that supports NR base stations with options 2 and 4, there may be eNB base stations that support options 3, 5, and 7. Figure 1 The bottom shows different UEs that support different types of deployments. The leftmost UE supports LTE / EPC, the middle UE also supports NR / EPC, and the rightmost UE also supports LTE / 4GC and NR / 5GC.

[0012] As part of the MR-DC configuration, each UE can be configured to have two separately scheduled cell groups: the primary cell group (MCG) and the secondary cell group (SCG).

[0013] The primary cell group (MCG) can be understood as belonging to the primary node (MN), and the secondary cell group can be understood as belonging to the secondary node (SN). Based on the MR-DC type, MN and SN can be LTE cells or NR cells.

[0014] Bearer termination option in UE's MR-DC

[0015] One important aspect to understand in MR-DC is bearer termination. Figure 2 This is a schematic diagram showing the bearer types as arrows based on the termination point in the UE used for MR-DC. In this diagram, MN uses NR and SN uses LTE. Other dual connectivity variants can exist, where MN and SN can use different combinations of NR and LTE. Corresponding variants are possible when dual connectivity can be used with the 5G core network (5GC). There are three main types of bearer termination in MR-DC: a) MN termination bearer or primary cell group (MCG) bearer 1: In MR-DC, the PDCP may be located in the radio bearer in MN; b) SN termination bearer or secondary cell group (SCG) bearer 2: In MR-DC, the PDCP may be located in the radio bearer in SN; and c) split bearer 3: Radio bearers with radio link control (RLC) in both MN and SN. Figure 2This illustrates how each of MCG bearer 1 and SCG bearer 2 has a corresponding Packet Data Convergence Protocol (PDCP) entity 4 (NR PDCP for MCG 1 and split bearer 3, and LTE / NR PDCP for SCG 2) and Radio Link Controller (RLC) entity 5 (each RLC entity 5 is connected to a corresponding Media Access Control (MAC) entity 6). Split bearer 3 has a PDCP entity in MN and is connected to each MAC entity 6 for MCG bearer 1 and SCG bearer 2 via the corresponding RLC entity.

[0016] Dual connectivity with two RANs (e.g., E-UTRAN and NR) can be achieved in a variety of ways. For example, 3GPP TS37.340[2] describes the following variations.

[0017] The first variant could be Multiple Radio Dual Connectivity (MR-DC), which can be understood as a generalization of E-UTRA dual connectivity, where the UE can be connected to two different nodes (e.g., base stations), one node using NR access and the other using either E-UTRA or NR access. One node can act as the primary node (MN), and the other node can act as the secondary node (SN). At least the MN can be connected to the core network (CN).

[0018] The second variant can be an MR-DC (EN-DC) with an EPC, which can be understood as an MR-DC where the CN can be an Evolved Packet Core (EPC), and where the eNB can act as the MN and the en-gNB can act as the SN. The MN can be connected to the EPC via the S1 interface. The SN can also be connected to the EPC via the S1-U interface. The MN and SN can be connected via the X2 interface.

[0019] The third variant can be E-UTRA-NR dual connectivity (NGEN-DC), in which the UE can be connected to an ng-eNB and a gNB, where the ng-eNB can act as the MN and the gNB can act as the SN. The ng-eNB can be connected to the 5GC. The MN can be connected to the 5GC. The MN and SN can be connected via the X2 interface.

[0020] The fourth variant can be NR-E-UTRA dual connectivity (NE-DC), in which the UE can be connected to a gNB acting as the MN and also to an ng-eNB acting as the SN. The MN can be connected to the 5GC. The MN and SN can be connected via the X2 interface.

[0021] The fifth variant can be NR-NR dual connectivity (NR-DC), in which the UE can be connected to two gNBs, one acting as the MN and the other as the SN. The MN can be connected to the 5GC. The SN can also be connected to the 5GC via the NG-U interface.

[0022] The above variations can be applied to user plane signaling. Control plane signaling can be transmitted in the MCG using Signaling Radio Bearer (SRB) 1 (SRB1) and SRB2.

[0023] More details are described in 3GPP TS 37.340[2].

[0024] Dual connectivity in RAN

[0025] Figure 3 This is a schematic diagram illustrating the network-side radio protocol termination options for MCG, SCG, and decoupled bearers in MN 7 and SN 8 of MR-DC (EN-DC) with EPC, according to existing methods, see 3GPP TS 37.340 version 16.1.0 Figure 4 2.2-3. When using an MR-DC with an EPC, the SN can be configured from MN 7 via the X2 9 interface. When SN 8 creates a DL configuration message (e.g., Cell Group (CG)-config or CG-configinfo), the configuration message can be sent to MN 7 via X2 interface 9 and then from MN 7 to the UE. Figure 3 This diagram illustrates how each of the MCG bearer 10, SCG bearer 11, and split bearer 12 has a corresponding Packet Data Convergence Protocol (PDCP) entity 13 and Radio Link Controller (RLC) entity 14, each entity 14 being connected to a corresponding Media Access Control (MAC) entity 15 in each of the MN and SN. The split bearer 16 has a PDCP entity in MN 11 and is connected to each MAC entity 19 in MN 11 and SN 12 respectively via the RLC entities located in each of MN 11 and SN 12. According to the EN-DC variant, MN 7 uses E-UTRA, and SN 8 uses NR.

[0026] Figure 4 This is based on 3GPP TS 37.340 version 16.1.0. Figure 4.2.2-4 illustrates the network-side radio protocol termination options for MCG, SCG, and decoupled bearers in MN 16 and SN 17 for MR-DCs (NGEN-DC, NE-DC, and NR-DC) with 5GC. When using an MR-DC with 5GC, SN 17 can be configured from MN 16 via Xn interface 18. When SN 17 creates a DL configuration message (e.g., CG-config or CG-configinfo), this configuration message can be sent to MN 16 via X2 interface 18 and then from MN 16 to the UE. Figure 4 As shown, the DRB can be terminated in MN 16 or SN 17 and transmitted via the primary cell group (via MCG bearer 19), the secondary cell group (via SCG bearer 20), or both (via split bearer 21). The MN and SN termination bearers, as well as any combination of MCG, SCG, and split bearers, can be configured for the UE. Figure 4 The schematic diagram also shows how the Quality of Service (QoS) flow 22 reaches the SDAP layer 23 at each of MN 16 and SN 17, and how each of the MCG bearer 19, SCG bearer 20 and decoupled bearer crosses each of the NRPDCP layer 24, RLC layer 25 and MAC layer 26 at each of MN 16 and SN 17, thereby interconnecting between MN 16 and SN 17 themselves via the Xn interface 18.

[0027] MR-DC control plane architecture

[0028] Figure 5 This is a schematic representation of the control plane architecture for an EN-DC (left) and an MR-DC with 5GC (right), where MeNB 27 represents an eNB acting as an MN, and SgNB 28 represents an en-gNB acting as an SN. MeNB 27 can be connected to the EPC via S1 interface 29. MeNB 27 and SgNB 28 can be connected via X2-C interface 30. The UE 31 in the MR-DC can have a single control plane connection to the core network and a single RRC state 32 controlled by the MN. Both the MN and SN can have their own RRC entities 32 for creating RRC messages or information elements (IEs) for configuring the UE 31; see [link to relevant documentation]. Figure 5Because the SN can manage its own resources, it can provide the secondary cell group (SCG) configuration to UE 31 in the RRC message and the radio bearer configuration in the IE for all bearers that can be terminated in the SN. The MN, in turn, can create the primary cell group (MCG) configuration and radio bearer configuration for all bearers terminated in the MN. The cell group configuration can include L1 (physical layer), Media Access Control (MAC), and RLC configurations. The radio bearer configuration can include PDCP configuration and, in the case of 5GC, Serving Data Protocol (SDAP) configuration. Figure 5 The diagram also shows the Uu interface 33 between UE 31 and each of MN and SN. Figure 5 The panel on the right shows the same connection for the MR-DC variant with 5GC, where MN 34 has a connection to NGC via NG-C interface 35.

[0029] Figure 6 According to existing methods.

[0030] LTE-New Radio (NR) DC (also known as LTE-NR Tight Interoperability, EN-DC when the UE is connected to the EPC, or NGEN-DC when the UE is connected to the 5GC) has been standardized in 3GPP rel-15. The main changes to LTE DC can be understood as: a) the introduction of a separate bearer from the SN, referred to as SCG separate bearer; b) the introduction of separate bearers for RRC, namely separate SRB1 36, separate SRB2 37; and c) the introduction of direct RRC from the SN, also referred to as SCG SRB or SRB3 38. Figure 6This is a schematic representation of network-side protocol termination options for SRBs in MR-DC, showing different SRB types. SRB1 39 and SRB2 40 refer to signaling radio bearers that can be used to carry RRC messages. RRC configurations created by the SN can be sent to the UE via the MN using SRB1, or directly to the UE using SRB3 (if configured). In the case of SRB1, the MN can receive an RRC message containing the SCG configuration and an IE containing the radio bearer configuration from the SN. The MN can encapsulate these RRC messages and IEs into an RRC message it can create itself, which can also include changes to the MCG and radio bearer configurations of the bearer terminated in the MN. Thus, the MCG and SCG configurations can be sent in the same RRC message, which can be understood as meaning that the RRC message can be the aggregate size of the MCG and SCG configurations plus the RRC message encapsulation overhead, which is limited by PDCP size constraints. Alternatively, the MCG and SCG configurations can also be sent in separate RRC messages, which can be understood as meaning that the PDCP size limit can be applied separately to RRC messages carrying the MCG and SCG configurations respectively. Figure 6 The diagram illustrates how each of the indicated DC options, SRB1 39, SRB2 40, Separate SRB1 36, Separate SBR2 37, and SBR3 38, passes through the PDCP, PLC, and MAC layers of each of the MCG and SCG.

[0031] Current solution for sending DL configuration messages to the UE

[0032] As described above, when dual connectivity is configured, the SN can send an RRC message containing the SCG configuration and radio bearer configuration, along with an IE, to the MN using the inter-node RRC message CG-config on X2 / Xn. Therefore, the MN can have two RRC configuration messages to send to the UE, one for the MCG and the other for the SCG. Furthermore, there may be an IE containing the radio bearer configuration created by the SN, which may need to be included in the RRC message created by the MN.

[0033] If the size of the resulting RRC message created by the MN is small enough, i.e., does not exceed the PDCP size limit, the MN can encapsulate all the contents in a single RRC message. However, if the resulting RRC message would exceed the PDCP size limit, the MN can also send the configurations generated by the MN and SN in separate RRC messages. The MN can then make the necessary changes to the MCG configuration during the first RRC reconfiguration, and then make changes to the SCG configuration and the SN termination radio bearer during the second RRC reconfiguration. Later in this description, this traditional solution may be referred to as the "fallback" method.

[0034] The MN may not need to understand the SCG configuration provided by the SN, because the SCG configuration can be transparently included in the RRC message created by the MN.

[0035] UE support for RRC segmentation

[0036] In the current solution for RRC segmentation in DL [4], it is defined that the UE can declare in its UE capabilities whether it supports RRC segmentation. The MN can use this information to determine whether the segmentation can be used for RRC messages in DL, and if not, it is also used to limit the size of DL configuration messages. The UE's receiver buffer may also impose restrictions on DL segmentation. In the current 3GPP specification, it is defined that the UE may need to have a receiver buffer of at least 45KB. Therefore, the current solution for RRC segmentation limits DL segmentation to a maximum of 5 segments. Summary of the Invention

[0037] As part of the development of embodiments of this article, one or more challenges of the prior art will first be identified and discussed.

[0038] The current solution in 3GPP describes the PDCP size limit for each corresponding (R)AN, namely, when using NRPDCP, the size can be limited to 9000 bytes [3GPP TS38.323 version 16.0.0], and when using LTE PDCP, the size can be limited to 8188 bytes [3GPP TS 36.323 version 16.0.0], which is also described in TR 37.873 version 16.0.0 [3].

[0039] The current solution in 3GPP describes how to segment RRC messages if the PDCP limit is exceeded [1]. However, for NR and LTE, segmentation is specified independently. Dual connectivity has not yet been addressed.

[0040] Therefore, there is currently no method for handling RR segmentation in dual connectivity scenarios (including multi-RAT dual connectivity scenarios, e.g., if MN is NR and SN is LTE).

[0041] If it is not defined whether it is MN or SN, a segmentation method may need to be executed.

[0042] The interaction methods between the MN and SN are not defined. For example: Does the MN know whether the SN supports fragmentation? Does the MN need to know this? If so, how does the MN obtain this information? Does the MN configure the SN? How is it configured? What protocols and interfaces are used for this configuration? Or, for example, when configuring dual connectivity, does the MN receive some type of capability information from the SN? How is it received? What protocols and interfaces are used? Does the SN know whether the MN supports fragmentation? Does the SN need to know this? If so, how does the SN obtain this information? If the MN does not support fragmentation, should the SN also be prevented from using fragmentation (if it does)? And vice versa?

[0043] There is no defined approach to support the requirement for segmentation in the MN, SN, or UE within the overall downlink segmentation solution. If one of the involved nodes does not support segmentation, how will the other nodes know this, and how will they react to the creation and processing of RRC messages?

[0044] For dual connectivity scenarios, there is no defined method for requiring the UE to support segmentation. The UE can indicate whether it supports segmentation in capability information that can be sent to the network. Different information elements may exist for LTE and NR. Therefore, the UE can report segmentation capability independently for LTE and NR. However, if the UE supports segmentation for one of the two RATs, it is unclear whether the UE might need to support segmentation for both RATs. If the UE is allowed to have different segmentation support for LTE and NR, how the MN and SN might handle this issue is undefined.

[0045] Another scenario where no method for handling segmentation is defined is the handover scenario. In the handover scenario, the same problem described for dual connectivity may occur, except that it occurs between the node from which the UE may handover (referred to as the source node) and the node to which the UE may handover (referred to as the target node).

[0046] One objective of the embodiments described herein is to improve message processing in wireless communication networks. Specifically, it can be understood that one objective of the embodiments described herein is to improve message segmentation processing in wireless communication networks. More specifically, it can be understood that one objective of the embodiments described herein is to improve segmentation for use, for example, in coordinating among multiple nodes in dual connectivity.

[0047] According to a first aspect of the embodiments herein, this objective is achieved by a method performed by a first node. The method is used to process a message destined for a third node. The message includes content from at least a first second node among one or more second nodes. The first node coordinates with the one or more second nodes to process radio communication with the third node. The first node operates in a wireless communication network. The first node sends the message to the third node. The message may or may not be segmented. Whether the message is sent segmented or not is based on: i) whether the size of the message exceeds a size limit, ii) whether the third node supports message segmentation, iii) whether the first node supports message segmentation, and iv) whether at least the first second node among the one or more second nodes supports message segmentation.

[0048] According to a second aspect of the embodiments herein, this objective is achieved by a method performed by a first and second node. The method is used to process a message destined for the third node. The message includes content from at least the first and second node among one or more second nodes. The first and second nodes coordinate with at least a first node to process radio communications with the third node. The first and second nodes operate in a wireless communication network, and the first and second nodes determine whether to segment the message based on: i) whether the size of the message exceeds a size limit, ii) whether the third node supports message segmentation, iii) whether the first node supports message segmentation, and iv) whether at least the first and second nodes among the one or more second nodes support message segmentation. Based on the determined fourth result, the first and second nodes initiate processing of the message.

[0049] According to a fourth aspect of the embodiments herein, this objective is achieved by a first node, which is configured to process the message destined for the third node. The message is configured to include content from at least a first second node among one or more second nodes. The first node is configured to coordinate with the one or more second nodes to process radio communication with the third node. The first node is configured to operate within the wireless communication network. The first node is also configured to send the message to the third node. The message is configured to be segmented or not segmented. Whether the message is segmented or not segmented is configured based on: i) whether the size of the message exceeds a size limit, ii) whether the third node supports message segmentation, iii) whether the first node supports message segmentation, and iv) whether at least the first second node among the one or more second nodes is configured to support message segmentation.

[0050] According to a fifth aspect of the embodiments herein, this objective is achieved through a first and second node, the first and second node being configured to process the message destined for the third node. The message is configured to include content from at least the first and second node of one or more second nodes. The first and second nodes are configured to coordinate with at least the first node in processing radio communications with the third node. The second nodes are configured to operate within the wireless communication network. The first and second nodes are further configured to determine whether to segment the message based on: i) whether the size of the message exceeds a size limit, ii) whether the third node supports message segmentation, iii) whether the first node supports message segmentation, and iv) whether at least the first and second node of the one or more second nodes supports message segmentation. The first and second nodes are further configured to initiate message processing based on the determined fourth result.

[0051] By sending messages to a third node, where segmentation and non-segmentation are based on: i) whether the message size exceeds a size limit, ii) whether the third node supports message segmentation, iii) whether the first node supports message segmentation, and iv) whether at least one of one or more second nodes supports message segmentation, the first node can decide to segment the message only if the involved nodes support it and only if necessary (due to the message size exceeding the size limit). Thus, the first node 111 can ensure that a consistent segmentation method can be applied in both dual-connectivity and handover scenarios. This can be performed when optimizing resource usage in the wireless communication network. Attached Figure Description

[0052] Examples of embodiments described herein are illustrated with reference to the accompanying drawings and the following description.

[0053] Figure 1 This is a schematic representation of the architectural options in 3GPP Release 15 according to existing methods;

[0054] Figure 2 This is a schematic representation illustrating bearer termination in MR-DC according to existing methods;

[0055] Figure 3 This is a schematic representation illustrating the network-side protocol termination option according to existing methods;

[0056] Figure 4 This is a schematic representation illustrating other network-side protocol termination options according to existing methods;

[0057] Figure 5 This is a schematic representation of the control plane architecture for EN-DC (left) and MR-DC (right) with 5GC, according to existing methods;

[0058] Figure 6 This is a schematic representation of the network-side protocol termination options for SRBs in MR-DC according to existing methods;

[0059] Figure 7 This is a schematic diagram illustrating a wireless communication network according to embodiments of this document;

[0060] Figure 8 This is a flowchart illustrating an example of a method in a first node according to an embodiment of this document;

[0061] Figure 9 This is a flowchart illustrating an example of a method in a first or second node according to embodiments of this document;

[0062] Figure 10 This is a signaling diagram illustrating a non-limiting example of a method in a wireless communication network according to embodiments of this document;

[0063] Figure 11 This is a signaling diagram illustrating another non-limiting example of a method in a wireless communication network according to embodiments of this document;

[0064] Figure 12 This is a signaling diagram illustrating yet another non-limiting example of a method in a wireless communication network according to embodiments of this document;

[0065] Figure 13 This is a signaling diagram illustrating another non-limiting example of a method in a wireless communication network according to embodiments of this document;

[0066] Figure 14 This is a schematic block diagram illustrating two non-limiting examples a) and b) of the first node according to embodiments of this document;

[0067] Figure 15 This is a schematic block diagram illustrating two non-limiting examples a) and b) of the first and second nodes according to embodiments of this document;

[0068] Figure 16 This is a schematic block diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to embodiments herein;

[0069] Figure 17 This is a general block diagram of a host computer communicating with a user equipment via a base station through a partial wireless connection according to embodiments of this document;

[0070] Figure 18 This is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station, and a user equipment according to embodiments of this document;

[0071] Figure 19 This is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station, and a user equipment according to embodiments of this document;

[0072] Figure 20 This is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station, and a user equipment according to embodiments of this document;

[0073] Figure 21 This is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station, and a user equipment, according to embodiments of this document. Detailed Implementation

[0074] Specific aspects and embodiments thereof in this disclosure may provide solutions to the challenges discussed in the "Summary of the Invention" section or other challenges. Various embodiments are presented herein to address one or more problems disclosed herein.

[0075] The embodiments described herein can be understood as relating to methods for segmentation to coordinate among multiple nodes. The embodiments described herein can be understood as relating to methods for segmentation for dual-connectivity, particularly for RRC segmentation for dual-connectivity.

[0076] Some contemplated embodiments will now be described more fully with reference to the accompanying drawings, in which examples are illustrated. In this section, embodiments thereof will be shown in more detail by way of several exemplary embodiments. However, other embodiments are included within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components from one embodiment may be assumed to be present in another embodiment, and how these components can be used in other exemplary embodiments will be apparent to those skilled in the art.

[0077] Note that although the terms from LTE / 5G have been used to illustrate the embodiments herein, this should not be construed as limiting the scope of the embodiments herein to the systems described above. Other wireless systems with similar characteristics may also benefit from utilizing the concepts covered within this disclosure.

[0078] Figure 7A non-limiting example of a wireless communication network 100 (sometimes referred to as a wireless communication system, cellular radio system, or cellular network) in which embodiments of this document may be implemented is shown. Wireless communication network 100 may be a 5G system, a 5G network, NR-U or a next-generation system or network, LAA, MulteFire. Wireless communication network 100 may support systems newer than 5G systems. Wireless communication network 100 may support other technologies such as Long Term Evolution (LTE), LTE-Advanced / LTE-Advanced Pro, such as LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in unlicensed frequency bands, etc. In a specific example of the embodiments herein, wireless communication network 100 may support MR-DC. Other examples of technologies that the wireless communication network 100 may support include Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile Communications (GSM) networks, GSM / Enhanced Data Rate Evolution of GSM (EDGE) Radio Access Network (GERAN) networks, Ultra Mobile Broadband (UMB), EDGE networks, networks including any combination of Radio Access Technologies (RATs) (e.g., Multi-Standard Radio (MSR) base stations, multi-RAT base stations, etc.), any 3GPP cellular network, WiFi networks, Global Microwave Access Interoperability (WiMax), Internet of Things (IoT), Narrowband IoT (NB-IoT), or any cellular network or system. Therefore, although terms from 5G / NR and LTE may be used in this disclosure to illustrate embodiments thereof, this should not be construed as limiting the scope of the embodiments herein to the systems described above.

[0079] The wireless communication network 100 may include multiple nodes, in Figure 7 The non-limiting example shows a first node 111, one or more second nodes 112, and a third node 113. One or more second nodes 112 include a first second node 114. For example, in... Figure 7 In some embodiments shown in the non-limiting examples, one or more second nodes 112 include only the first second node 114. In other examples, one or more second nodes 112 include the first second node 114 and additional nodes. For simplicity... Figure 7 This is in Figure 7 It is not shown in the text.

[0080] Any one of the first node 111, one or more second nodes 112, and the third node 113 can be a radio network node. That is, a transmission point (e.g., a radio base station, such as a gNB or eNB), or any other network node with similar characteristics to serve wireless devices (e.g., user equipment or machine-type communication devices) in the wireless communication network 100. Figure 7 In other examples not shown, any one of the first node 111 and one or more second nodes 112 can be a distributed node (e.g., a virtual node in the cloud) and can cooperate with radio network nodes to perform its functions fully or partially in the cloud. In some examples, at least one of the first node 111 and one or more second nodes 112 can be located in the same location or be on the same network node. For example... Figure 7 In the typical example shown, the first node 111, one or more second nodes 112 (especially the first and second nodes 114), and the third node 113 can be different nodes.

[0081] In other typical examples, the first node 111 may be a first network node, any one of the first or one or more second nodes 112 may be a second network node, and the third node 113 may be a wireless device. A description of the wireless device is provided subsequently.

[0082] In other specific examples, the first node 111 may be a first radio network node, any one of one or more second nodes 112 may be a second radio network node, and the third node 113 may be a wireless device. A description of the wireless device is provided subsequently.

[0083] The wireless communication network 100 covers a geographical area that can be divided into cell areas, each of which can be served by a network node, but a single radio network node can serve one or more cells. The wireless communication network 100 includes at least a first cell 121 and one or more second cells 122. A first node 111 can serve the first cell 121, while one or more second nodes 112 can each serve one of the one or more second cells 122.

[0084] In some examples, the wireless communication network 100 may include one of the following: a first group of cells 120-1 and one or more second groups of cells 120-2. The first group of cells 120-1 may include a first cell 121 and one or more third cells 123. Figure 7 In the non-limiting example shown, only one of the one or more third cells 123 is depicted for simplification. However, it will be understood that the one or more third cells 123 may include many other cells. In some non-limiting examples, the first group of cells 120-1 may be a primary cell group (MCG).

[0085] One or more second-group cells 120-2 may include one or more second cells 122 and one or more fourth cells 124. Figure 7 In the non-limiting example shown, only one fourth cell 124 is depicted for simplification. However, it will be understood that one or more fourth cells 124 may include more fourth cells. In some non-limiting examples, any one or all of one or more second group cells 120-2 may be a secondary cell group (SCG).

[0086] In some examples, such as in multi-connection or dual-connection scenarios, the first node 111 can be MN, and one or more second nodes 112 (e.g., first and second nodes 114) can be SN.

[0087] In other examples, such as in multi-connection or dual-connection scenarios, the first node 111 can be SN, the first second node 114 can be MN, and other second nodes in one or more second nodes 112 can be SN.

[0088] In other examples, such as in a scene transition, the first node 111 can be the source node, and the first and second nodes 114 can be the target nodes.

[0089] In other examples, such as in a scene transition, the first node 111 can be the target node, and the first and second nodes 114 can be the source nodes.

[0090] In other examples, such as a central unit (CU)-distributed unit (DU) separation architecture (where network nodes can be separated between CUs and one or more distributed units (DUs), the first node 111 can be a DU, and the first second node 114 can be a CU. Other second nodes (if any) in one or more second nodes 112 can be other DUs.

[0091] In other examples, such as for a CU-DU split architecture, the first node 111 can be the first DU, and the first second node 114 can be either a CU or a second DU. Other second nodes (if any) in one or more second nodes 112 can be other DUs.

[0092] Based on transmit power and thus also based on cell size, any one of the first node 111 and one or more second nodes 112 can belong to different classes, such as macro base stations, femto base stations, or pico base stations. Any one of the first node 111 and the first and second nodes 114 can support one or more communication technologies, and their names can depend on the technologies and terminology used. In 5G / NR, any one of the first node 111 and the first and second nodes 114 can be referred to as a gNB and can be directly connected to one or more core networks, which in... Figure 7 It is not shown in the text.

[0093] Multiple wireless devices can be included in the wireless communication network 100, in Figure 7 The wireless device 130 is shown in a non-limiting example. The wireless device 130 included in the wireless communication network 100 can be a wireless communication device such as a 5G UE or UE, and can also be referred to as, for example, a mobile terminal, wireless terminal and / or mobile station, mobile phone, cellular phone, or wireless-capable laptop computer, to name just a few other examples. Any wireless device included in the wireless communication network 100 can be, for example, portable, pocket-sized, handheld, including computers or vehicle-mounted mobile devices, capable of transmitting voice and / or data via the RAN to another entity, such as a server, laptop computer, personal digital assistant (PDA) or tablet computer (sometimes referred to as a wireless-capable tablet computer), machine-to-machine (M2M) device, device equipped with a wireless interface (e.g., printer or file storage device), modem, or any other radio network unit capable of communicating via a radio link in the communication system. The wireless device 130 included in the wireless communication network 100 is capable of wireless communication within the wireless communication network 100. Communication can be performed, for example, via the RAN and possibly via one or more core networks that can be included within the wireless communication network 100.

[0094] The third node 113 can be configured to communicate with the first node 111 in the first cell 121 via a first link 141 (e.g., a radio link) within the wireless communication network 100. The third node 113 can be configured to communicate with the first node 111 in each of one or more third cells 123 via a corresponding second link 142 (e.g., a radio link) within the wireless communication network 100. The third node 113 can be configured to communicate with each of one or more second nodes 112 in the second cell 122 via a corresponding third link 143 (e.g., a radio link) within the wireless communication network 100. The third node 113 can be configured to communicate with one or more second nodes 112 in any one of one or more fourth cells 124 via a corresponding fourth link 144 (e.g., a radio link) within the wireless communication network 100.

[0095] Any one of the first node 111 and one or more second nodes 112 can be configured to communicate within the wireless communication network 100 via a corresponding fifth link 150 (e.g., a wired link or an X2 or Xn interface).

[0096] Generally speaking, the use of “first,” “second,” “third,” “fourth,” “fifth,” “sixth,” and / or “seventh” in this article can be understood as any way of referring to different units or entities, and can be understood as not giving the nouns they modify any cumulative or chronological characteristics.

[0097] This document includes multiple embodiments. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be assumed to exist in another embodiment, and how these components can be used in other exemplary embodiments will be apparent to those skilled in the art.

[0098] More specifically, the following are embodiments involving a first node (e.g., first node 111, such as a gNB or eNB) and embodiments involving a second node (e.g., first second node 114, such as another gNB or another eNB).

[0099] Now refer to Figure 8 The flowchart shown illustrates an embodiment of the method performed by the first node 111. This method can be understood as processing a message destined for the third node 113. The message includes content from at least a first second node 114 among one or more second nodes 112. The first node 111 coordinates with one or more second nodes 112 to process radio communication with the third node 113. For example, the coordination of radio communication can be based on multi-connectivity (e.g., dual-connectivity), handover, or a split architecture. Multi-connectivity (e.g., dual-connectivity) can be multi-radio (MR) multi-connectivity.

[0100] The first node 111 operates in the wireless communication network 100.

[0101] This method can be understood as a computer-implemented method.

[0102] node

[0103] In some embodiments, at least one of the following options may be applied. In the first option, the first node 111 may serve the third node 113 with multiple connections to one or more second nodes 112.

[0104] In embodiments where coordination may include dual connections, examples of embodiments herein can be understood to include processing for both the dual connection establishment phase and the runtime phase.

[0105] In the second option, the first node 111 may want to switch its connection (e.g., radio communication) with the third node 113 to the first second node 114 or switch its connection (e.g., radio communication) with the third node 113 from the first second node 114.

[0106] In the third option, in multiple connections, the first node 111 can be the master node (MN) of the third node 113, and one or more second nodes 112 can be the auxiliary nodes (SN) of the third node 113.

[0107] In the fourth option, in a multi-connection scenario, the first second node 114 can be the MN of the third node 113, and the first node 111 and one or more other second nodes 112 can be the SN of the third node 113.

[0108] In the fifth option, for example in a scene switching scenario, the first node 111 can be the source node of the third node 113, and the first and second nodes 114 can be the target node of the third node 113.

[0109] In the sixth option, for example in a scene switching scenario, the first node 111 can be the target node of the third node 113, and the first and second nodes 114 can be the source nodes of the third node 113.

[0110] In the seventh option, for example in a split architecture scenario, the first node 111 can be a distributed unit (DU), and the first and second nodes 114 can be centralized units (CU).

[0111] In the eighth option, for example in a split architecture scenario, the first node 111 can be a CU, and each of one or more second nodes 112 can be a DU.

[0112] In the ninth option, for example in a split architecture scenario, the first node 111 can be the first DU, and any one of one or more second nodes 112 can be another DU.

[0113] In some embodiments, at least one of the first node 111 and the first and second nodes 114 can be MN, and the other can be SN. In some embodiments of these embodiments, only MN and the third node 113 can support segmentation. In some other embodiments of these embodiments, MN, SN, and the third node 113 can all support segmentation.

[0114] This document includes multiple embodiments. In some embodiments, all actions may be performed. In some embodiments, one or more actions may be performed. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments may be combined. For the sake of simplicity, not all possible combinations have been described. Components from one embodiment may be assumed to be present in another embodiment, and how these components can be used in other exemplary embodiments will be apparent to those skilled in the art. Figure 8 The diagram shows a non-restrictive example of a method executed by the first node 111. Some actions can be performed in conjunction with... Figure 8 The different sequences shown will be executed.

[0115] exist Figure 8 In the text, optional actions are indicated by dashed boxes.

[0116] Action 801

[0117] During communication in the wireless communication network 100, a first node 111 may send a message to a third node 113. Because the first node 111 coordinates with one or more second nodes 112 to process radio communication 112 with the third node 113, the message may include content from at least the first and second nodes 114. Therefore, the message may be large and exceed size limits, such as the PDCP limits for LTE and NR. Embodiments herein can be understood as defining the behavior of the first node 111 (e.g., MN) and the first and second nodes 114 (e.g., SN) to handle such messages (e.g., RRC messages) that may exceed size limits (e.g., the PDCP limits for LTE and NR). To handle messages exceeding size limits, the first node 111 may need to segment the message. Therefore, embodiments herein can be understood as providing a method for processing segmentation (e.g., RRC message segmentation) in radio communication between the first node 111 and one or more second nodes 112 and the third node 113, for example in a multi-connectivity scenario, and can be understood as defining the behavior of the first node 111 and the first and second nodes 114 in this regard.

[0118] To determine whether a message may need to be segmented, the first node 111 may first need to determine whether the third node 113 is capable of processing segmented messages. As described above, in action 801, the first node 111 can obtain a first indication indicating whether the third node 113 supports message segmentation. Therefore, the first indication can indicate the third node 113's ability to support message segmentation.

[0119] Acquisition can include receiving, retrieving, obtaining, etc. A first indication can be obtained, for example, by receiving a first indication from a third node 113 via a first link 141. When the third node 113 can register to the network, it can typically upload the first indication, and then a dual connection can be established. It is also possible that the dual connection can be enabled and disabled several times without receiving new capabilities from the third node 113. The first indication may need to be updated because the segmentation capabilities of the third node 113 may change, for example, if the third node 113 may need to conserve battery power.

[0120] In some embodiments, the message may be a Radio Resource Control (RRC) message. For example, the message may be an RRC configuration or reconfiguration message.

[0121] However, the embodiments described herein can be extended to other RRC messages.

[0122] In this document, the following can be used as an example: a first node 111 (e.g., MN) can send an RRC reconfiguration message to a third node 113 (e.g., UE), which may include portions that may have been provided and / or created by the MN and the first and second nodes 114 (e.g., SN). However, this should be understood as merely one example of an RRC message to which the embodiments can be applied. Other large RRC messages can also use the same approach.

[0123] The 3GPP specification allows the MCG+SCG configuration message to be sent in two RRC messages: a) RRCReconfiguration and b) RRCResume.

[0124] By receiving the first instruction in action 801, the first node 111 can subsequently determine whether to segment the message based on whether the third node 113 supports message segmentation.

[0125] Action 802

[0126] When coordinating one or more second nodes 112 to establish radio communication with a third node 113 (e.g., when establishing dual connectivity), the first node 111 (e.g., MN) may need to notify the first and second nodes 114 (e.g., SN) whether segmentation is supported. This may require the exchange of the following information between the first and second nodes 111 and 114: whether segmentation can be used, and size limitations that the first and second nodes 114 may need to apply when preparing the configuration of one or more second groups of cells 120-2 (e.g., SCG configuration). That is, the first node 111 and the first and second nodes 114 may need to exchange information, for example, as information exchange between the MN and the SN.

[0127] If the segmentation capability of the first node 111 and / or the first and second nodes 114 changes, for example in the case of handover, if the first node 111 (e.g., MN), the first and second nodes 114 (e.g., SN), or both switch to a new cell with different segmentation capabilities, this information may need to be updated.

[0128] This information can be exchanged via the Xn / X2 interface.

[0129] Based on the above description, in some embodiments, during action 802, the first node 111 may send one or more second indications to at least one of one or more second nodes 112 (e.g., a first second node 114). The one or more second indications may indicate at least one of the following: i) whether the third node 113 supports message segmentation, for example based on the first indication received in action 801; ii) whether the first node 111 supports message segmentation; iii) a first version of the segmentation supported by the first node 111; and iv) a first size limit, combined size limit, or both supported by the first node 111 for segmenting the message.

[0130] The version can be based on a radio access technology (RAT) and can be, for example, NR or LTE. The version can be, for example, a PDCP version. Versions can be understood as related because the maximum size of a message (e.g., a PDCP PDU) may differ in different versions (e.g., between LTE PDCP and NR PDCP), and when determining the size of the reconfiguration information, the first node 111 may consider the version used by the first and second nodes 114.

[0131] The size limit can be one of the following. According to the first option, the size limit can be a first size limit, a combined size limit, or both supported by the first node 111 for segmenting messages; the first size limit can be, for example, one of the following: a limit of the first node 111, a size limit of the SCG configuration (e.g., Size1 in the single size limit cell of Table 2), or an upper limit of any SCG configuration (e.g., Size3 in Table 2); the combined size limit can be, for example, one of the following: a limit for sending both MCG and SCG configurations in the same PDCP packet (e.g., Size1 in the two or three size limit cells of Table 2), or a limit for sending MCG and SCG configurations in different PDCP packets (e.g., Size2 in the two or three size limit cells of Table 2). According to the second option, the size limit can be a second size limit, a combined size limit, or both supported by the first and second nodes 114 for segmenting messages; the second size limit can be, for example, one of the following: a limit of the first and second nodes 114, a size limit of the SCG configuration, or an upper limit of any SCG configuration; the combined size limit can be, for example, one of the following: a limit for sending both MCG and SCG configurations in the same PDCP packet or a limit for sending MCG and SCG configurations in different PDCP packets. According to the third option, the size limit can be a corresponding second size limit, a combined size limit, or both supported by one or more second nodes 112 for segmenting messages.

[0132] As an example, a size limit could be, for instance, a PDCP SDU size limit.

[0133] Examples of embodiments described herein may include sending a size limit from the MN signaling to the SN. Which size can be signaled may depend on several factors, such as: which RAT (e.g., NR, LTE) the MN can use, which RAT (e.g., NR, LTE) the SN can use, whether the MN and / or SN support segmentation, whether the UE supports segmentation, and / or, for example, the presupposed grouping volume when both MCG and SCG configurations are encapsulated in the same RRC message.

[0134] Determine appropriate size limits

[0135] Table 1 shows non-limiting examples of how size limits can be determined for different combinations of the factors listed above. Table 1 only covers two possible combinations: when the MN uses LTE and the SN uses NR, and when the MN uses NR and the SN uses LTE. It can be understood that other combinations are possible.

[0136]

[0137] Table 1. Examples of Size Limit Selection

[0138] Another alternative is to send two or more size limit signaling messages to the SN, and then use these size limits as described in Table 2:

[0139]

[0140]

[0141] Table 2. One or more size limitations and examples of their use in SN and MN.

[0142] The transmission in action 802 can be performed, for example, via the corresponding fifth link 150.

[0143] By sending one or more second instructions in action 801, the first node 111 enables at least one of one or more second nodes 112 to subsequently determine whether to segment the message and how segmentation might need to be performed, based on whether the third node 113 and / or the first node 111 support message segmentation. Thus, the first node 111 can ensure that a consistent segmentation method can be applied in a dual-connectivity scenario.

[0144] An alternative to sending size limits from the MN signaling to the SN is to pre-configure the SN with one or more of these limits.

[0145] Action 803

[0146] When coordinating one or more second nodes 112 to establish radio communication with a third node 113 (e.g., when establishing dual connectivity), the first node 111 (e.g., MN) may also need to determine whether the first and second nodes 114 (e.g., SN) can support segmentation (e.g., RRC segmentation). This may require the exchange of the following information between the first node 111 and the first and second nodes 114: whether segmentation can be used, and the size limitations that the first and second nodes 114 may need to apply when preparing the configuration of one or more second groups of cells 120-2 (e.g., SCG configuration). That is, the first node 111 and the first and second nodes 114 may need to exchange information, for example, as information exchange between the MN and the SN.

[0147] In the event of a handover, if the first node 111 (e.g., MN), the first and second nodes 114 (e.g., SN), or both, switch to a new cell with different segmentation capabilities, this information may also need to be updated.

[0148] This information can be exchanged via the Xn / X2 interface.

[0149] Based on the above description, in action 803, the first node 111 may receive one or more corresponding third instructions from one or more second nodes 112. The one or more corresponding third instructions may respectively indicate at least one of the following: i) whether one or more second nodes 112 support message segmentation, ii) corresponding second versions of segments supported by one or more second nodes 112, and iii) corresponding second size limits, combined size limits, or both for message segmentation supported by one or more second nodes 112.

[0150] The first node 111 may receive one or more corresponding third instructions from one or more second nodes 112, for example, via a corresponding fifth link 150.

[0151] By receiving the first instruction in action 801, the first node 111 can subsequently determine whether and how to segment the message based on whether one or more second nodes 112 support message segmentation and how they support it. This allows the first node 111 to ensure that a consistent segmentation method can be applied in a dual-connectivity scenario.

[0152] Action 804

[0153] According to action 803, in action 804, the first node 111 can receive a third instruction from the first and second nodes 114. The third instruction may indicate at least one of the following: i) whether the first and second nodes 114 support message segmentation, ii) a second version of segmentation supported by the first and second nodes 114, and iii) a second size limit, a combined size limit, or both supported by the first and second nodes 114 for message segmentation. Thus, the first node 111 can ensure that a consistent segmentation method can be applied in a dual-connection scenario.

[0154] The first node 111 can receive a third instruction from the first and second nodes 114, for example, via a corresponding fifth link 150.

[0155] Action 805

[0156] In action 805, the first node 111 may determine at least one of the following: i) a corresponding second version of the segment supported by one or more second nodes 112, ii) a corresponding second size limit, combined size limit or both for segmenting the message supported by one or more second nodes 112, iii) a second version of the segment supported by the first second node 114, and iv) a second size limit, combined size limit or both for segmenting the message supported by the first second node 114.

[0157] Determining can be understood as calculation or derivation.

[0158] To determine, in action 805, a second size limit, a combined size limit, or both, supported by the first and second nodes 114 for message segmentation, one possibility is that the first node 111 can retrieve capability information from the first and second nodes 114 to determine whether the first and second nodes 114 support segmentation. Another possibility is that the first and second nodes 114 can also send this information to the first node 111 according to action 804, even if no specific request or command is received from the first node 111. Yet another possibility is that the MN can be pre-configured with the capabilities of the first and second nodes 114.

[0159] During a handover, the segmentation capabilities of the target MN or target SN may differ from those of the source MN or SN, respectively. This can be interpreted as meaning that action 805 may need to be repeated, even if no new capabilities are received from the third node 113.

[0160] By performing the determination in action 805 by the first node 111, the first node 111 can know how to perform message segmentation so that the message can be segmented in a manner supported by one or more second nodes 112 (the first node 111 can coordinate with one or more second nodes 112 to handle radio communication with the third node 113) so that the message can be segmented in a coordinated and optimized manner.

[0161] Thus, the first node 111 can ensure that a consistent segmentation method can be applied in a dual-connection scenario.

[0162] Action 806

[0163] In some embodiments where the first node 111 may send a second indication indicating that the first node 111 does not support segmentation in action 802, in which action 806, the first node 111 may receive from at least the first and second nodes 114 a sub-message (referred to herein as a second sub-message) to be included in the message destined for the third node 113. The size of the second sub-message may be lower than a first size limit that may not require segmentation. The sub-message may be understood herein to refer to another message to be included in the message to be sent.

[0164] The size of the second sub-message can be lower than the first size limit, which may not require segmentation.

[0165] The first node 111 can perform the receiving action 806, for example, via the corresponding third link 143.

[0166] Action 806 can be performed, for example, under method 1 in the examples of the embodiments herein, which will be described later.

[0167] By receiving the second sub-message in action 806, the segmentation of messages by the first and second nodes 114 can be achieved even if the first node 111 may not support segmentation.

[0168] Action 807

[0169] In action 807, the first node 111 may determine whether to segment the message based on: i) whether the size of the message exceeds the size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first second node 114 of one or more second nodes 112 supports message segmentation, and v) wherein the message is sent based on the determined second result.

[0170] Determining can be understood as calculation or derivation.

[0171] In the example of the embodiments relating to this article, the determination in action 807 may be based on at least one of i)-iv) or, for example, all of i)-iv).

[0172] In some embodiments, determining whether to segment a message based on whether the message size exceeds a size limit may include further determining at least one of the following: a) whether a first sub-message from the first node 111 to be included in a message destined for the third node 113 exceeds a first size limit; b) whether one or more second sub-messages received from one or more second nodes 112 and to be included in a message destined for the third node 113 exceed a corresponding second size limit; and c) whether a combination of the first sub-message and one or more second sub-messages exceeds a combination size limit.

[0173] In a specific example of the embodiments herein, the determination in action 807 may include selecting between a fallback method and two methods based on the capabilities of the MN and SN, namely: method 1 (also referred to herein as "Solution 1"), which can be used if, in coordinated radio communication (e.g., in a dual-connectivity scenario), the MN is allowed to perform downlink message (e.g., RRC message) segmentation instead of the SN; and method 2 (also referred to herein as "Solution 2"), which can be used if, in coordinated radio communication (e.g., in a dual-connectivity scenario), both the MN and the SN are allowed to perform downlink message (e.g., RRC message) segmentation. The following applies to... Figure 11 , Figure 12 and Figure 13Using RRC messages and a dual-connection scenario as examples, this section describes these two methods and the choice between them in more detail. A similar description can be applied to switching scenarios, as described below. This similar description can be understood to apply to messages.

[0174] During a handover, the segmentation capabilities of the target MN or target SN may differ from those of the source MN or SN, respectively. This can be understood as meaning that action 807 may need to be repeated, even if new capabilities may not be received from the third node 113. During a handover, it is also possible that new capabilities may be received from the third node 113, for example, because the capabilities from the third node 113 have changed, which may depend on the new MN and / or SN capabilities in the target MN and / or SN. It is also possible that the third node 113 may need to disable certain features, such as to conserve battery power, which could mean that the third node 113 may need to upload its new capabilities to the network.

[0175] By performing the determination in action 807, the first node 111 can decide to segment the message only if the involved nodes support it and only if necessary (because the message size exceeds the size limit). Thus, the first node 111 can ensure that a consistent segmentation method can be applied in a dual-connection scenario.

[0176] Action 808

[0177] In this action 808, the first node 111 may segment at least one of the following: a) a first sub-message from the first node 111 to be included in a message to the third node 113, b) at least one corresponding second sub-message received from one or more second nodes 112 and to be included in a message to the third node 113, and c) a combination of the first sub-message and at least one corresponding second sub-message.

[0178] The first sub-message can be understood as the first message. The second sub-message can be understood as the second sub-message. One of the first and second sub-messages can be, for example, an MCG reconfiguration message, and the other of the first and second sub-messages can be, for example, an SCG reconfiguration message.

[0179] In some embodiments where the first node 111 can be an SN and the first and second nodes 114 can be an MN, the segmentation in action 808 can be performed according to a third size constraint of the MN (e.g., a constraint that the first and second nodes 114 may have when they become an MN).

[0180] In some embodiments where the combination of the first sub-message and one or more second sub-messages exceeds a combination size limit, the method may further include segmenting the combination in that action.

[0181] The segmentation in action 808 can be based on the result determined in action 807. That is, the message can only be segmented in action 808 if the first node 111 has already determined to segment the message in action 807.

[0182] Action 809

[0183] In action 809, the first node 111 sends a message to the third node 113. The message may or may not be segmented. Whether the message is sent segmented or not is based on: i) whether the message size exceeds a size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first second node 114 of one or more second nodes 112 supports message segmentation.

[0184] The transmission can be performed, for example, via the first link 141.

[0185] In some embodiments where the first node 111 can serve the third node 113 via multiple connections with one or more second nodes 112, at least one of the first node 111 and the first and second nodes 114 can be MN, and the other can be SN. In some of these embodiments, only MN and the third node 113 can support segmentation.

[0186] In some embodiments where the first node 111 can serve the third node 113 via multiple connections with one or more second nodes 112, at least one of the first node 111 and the first and second nodes 114 can be MN, and the other can be SN. MN, SN, and the third node 113 can all support segmentation. The sent message can be segmented based on whether at least one of the one or more second sub-messages from one or more second nodes 112 that are to be included in the message destined for the third node 113 is segmented.

[0187] In some embodiments, the message may be sent based on a determined second result performed in action 807.

[0188] In some embodiments, the message may be sent based on a further determined third result performed in action 807.

[0189] In some embodiments, the message may be sent based on the first result of the segment performed in action 808.

[0190] By performing the transmission in action 809, the first node 111 can optimize message processing and radio resources in the wireless communication network 100 by transmitting messages only when the involved nodes support segmentation and only when necessary (due to the message size exceeding the size limit) in coordinated radio communication with one or more second nodes 112. Thus, the first node 111 can ensure that a consistent segmentation method can be applied in a dual-connectivity scenario.

[0191] Examples of these actions and instructions are provided later in this document.

[0192] Now refer to Figure 9 The flowchart shown illustrates an embodiment of a method performed by first and second nodes 114. This method can be understood as processing a message destined for a third node 113. The message includes content from at least the first and second nodes 114 among one or more second nodes 112. That is, the message may include content from at least one of one or more second nodes 112. The first and second nodes 114 at least coordinate with the first node 111 to handle radio communication with the third node 113. In some examples, the first and second nodes 114 may coordinate with the first node 111 and one or more second nodes 112 to handle radio communication with the third node 113. For example, the coordination of radio communication may be based on multi-connectivity (e.g., dual-connectivity), handover, or a split architecture.

[0193] The first and second nodes 114 operate in the wireless communication network 100.

[0194] In some embodiments, the message may be an RRC message. For example, the message may be an RRC configuration or reconfiguration message.

[0195] This method can be understood as a computer-implemented method.

[0196] This method may include the following actions. This document includes multiple embodiments. In some embodiments, all actions may be performed. In some embodiments, two or more actions may be performed. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments may be combined. For simplicity, not all possible combinations have been described. Components from one embodiment may be assumed to be present in another embodiment, and how these components can be used in other exemplary embodiments will be apparent to those skilled in the art. Figure 9 The diagram shows a non-limiting example of a method executed by the first and second nodes 114. Some actions can be performed in conjunction with... Figure 9 The different sequences shown will be executed.

[0197] exist Figure 9In the text, optional actions are represented by dashed lines.

[0198] Some of the detailed descriptions below correspond to the same references provided above regarding the actions described for the first node 111, and therefore will not be repeated here for the sake of simplicity. For example, in some embodiments, at least one of the following options may be applied. In a first option, the first second node 114 may serve the third node 113 with multiple connections to the first node 111, one or more second nodes 112, or both.

[0199] In the second option, the first node 114 may want to switch the connection (e.g., radio communication) with the third node 113 to the first node 111 or switch the connection (e.g., radio communication) with the third node 113 from the first node 111.

[0200] In the third option, in multiple connections, the first node 111 can be the master node (MN) of the third node 113, and one or more second nodes 112 can be the auxiliary nodes (SN) of the third node 113.

[0201] In the fourth option, in a multi-connection scenario, the first second node 114 can be the MN of the third node 113, and the first node 111 and one or more other second nodes 112 can be the SN of the third node 113.

[0202] In the fifth option, for example in a scene switching scenario, the first node 111 can be the source node of the third node 113, and the first and second nodes 114 can be the target node of the third node 113.

[0203] In the sixth option, for example in a scene switching scenario, the first node 111 can be the target node of the third node 113, and the first and second nodes 114 can be the source nodes of the third node 113.

[0204] In the seventh option, for example in a split architecture scenario, the first node 111 can be a DU, and the first and second nodes 114 can be CUs.

[0205] In the eighth option, for example in a split architecture scenario, the first node 111 can be a CU, and each of one or more second nodes 112 can be a DU.

[0206] In the ninth option, for example in a split architecture scenario, the first node 111 can be the first DU, and any one of one or more second nodes 112 can be another DU.

[0207] Multiple connections (e.g., dual connections) can be multiple radio (MR) multiple connections.

[0208] In some embodiments, at least one of the first node 111 and the first and second nodes 114 can be MN, and the other can be SN. In some embodiments of these embodiments, only MN and the third node 113 can support segmentation. In some other embodiments of these embodiments, MN, SN, and the third node 113 can all support segmentation.

[0209] Action 901

[0210] In this action 901, the first and second nodes 114 can obtain a first indication of whether the third node 113 supports message segmentation.

[0211] Acquisition can include receiving, retrieving, obtaining, etc. The first instruction can be obtained, for example, by receiving the first instruction from the third node 113 via the corresponding third link 141.

[0212] Action 902

[0213] In action 902, the first and second nodes 114 may receive one or more second instructions from the first node 111. The one or more second instructions may indicate at least one of the following: i) whether the third node 113 supports message segmentation, ii) whether the first node 111 supports message segmentation, iii) a first version of the segmentation supported by the first node 111, and iv) a first size limit, a combined size limit, or both supported by the first node 111 for segmenting the message.

[0214] As mentioned earlier, the version can be based on RAT and can be, for example, NR or LTE.

[0215] The first and second nodes 114 may receive one or more second instructions from the first node 111, for example, via a corresponding fifth link 150.

[0216] Action 903

[0217] In action 903, the first second node 114 may receive one or more corresponding third indications from one or more second nodes 112. The one or more corresponding third indications may respectively indicate at least one of the following: i) whether one or more second nodes 112 support message segmentation, ii) a corresponding second version of the segmentation supported by one or more second nodes 112 respectively, and iii) a corresponding second size limit, combined size limit or both for segmenting the message supported by one or more second nodes 112 respectively.

[0218] The first and second nodes 114 may receive one or more corresponding third instructions from one or more second nodes 112, for example, via corresponding links.

[0219] Action 904

[0220] In action 904, the first and second nodes 114 may send a third instruction to at least one of the following: the first node 111, and other nodes in one or more of the second nodes 112. The third instruction may indicate at least one of the following: i) whether the first and second nodes 114 support message segmentation, ii) a second version of the segmentation supported by the first and second nodes 114, and iii) a second size limit, a combined size limit, or both supported by the first and second nodes 114 for segmenting the message.

[0221] Action 905

[0222] In action 905, the first and second nodes 114 may determine at least one of the following: i) a corresponding second version of a segment supported by one or more second nodes 112, ii) a corresponding second size limit, combined size limit, or both for segmenting a message supported by one or more second nodes 112, iii) a first version of a segment supported by the first node 111, and iv) a first size limit, combined size limit, or both for segmenting a message supported by the first node 111.

[0223] Additionally or alternatively, the first or second node 114 may determine a second size limit, a combined size limit, or both supported by the first or second node 114 for segmenting messages.

[0224] Determining can be understood as calculation or derivation.

[0225] Action 906

[0226] In action 906, the first and second nodes 114 determine whether to segment the message based on the following: i) whether the message size exceeds the size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first and second nodes 114 of one or more second nodes 112 support message segmentation.

[0227] Determining can be understood as calculation or derivation.

[0228] In the example of the embodiments relating to this article, the determination in action 906 may be based on at least one of i)-iv) or, for example, all of i)-iv).

[0229] In some embodiments, determining whether to segment a message based on whether the message size exceeds a size limit in action 906 may include further determining at least one of the following: a) whether a first sub-message from the first node 111 to be included in a message destined for the third node 113 exceeds a first size limit; b) whether a second sub-message from the first and second nodes 114 to be included in a message destined for the third node 113 exceeds a second size limit; c) whether one or more corresponding second sub-messages received from one or more second nodes 112 and to be included in a message destined for the third node 113 exceed their respective second size limits; and d) whether a combination of the first sub-message, the second sub-message, and / or one or more corresponding second sub-messages exceeds a combination size limit.

[0230] In a particular example of the embodiments herein, the determination in action 906 may include selecting between a rollback method, method 1, and method 2, as previously described and further described below.

[0231] Action 907

[0232] In action 907, the first and second nodes 114 initiate a processing message based on the determined fourth result. The initiation processing message may include one or more of actions 908, 909, and 910, as described below.

[0233] Action 908

[0234] In some embodiments, initiating processing message 907 may include, in action 908, the first and second nodes 114 segmenting at least one of the following: a) a second sub-message from the first and second nodes 114 to be included in a message destined for the third node 113; b) a first sub-message from the first node 111 to be included in a message destined for the third node 113; c) at least one corresponding second sub-message received from one or more second nodes 112 and to be included in a message destined for the third node 113; and d) a combination of the following: a first sub-message, and at least one of the second sub-messages and at least one corresponding second sub-message. The segmentation in action 908 may be based on a determined fourth result.

[0235] In some embodiments where the combination exceeds the combination size limit, the method may also include segmenting the combination in the action.

[0236] In some embodiments, the combination of a first sub-message and one or more second sub-messages may exceed the combination size limit, and the method may further include segmenting the combination 908.

[0237] In some embodiments where the first node 111 can be an SN and the first and second nodes 114 can be an MN, the segmentation in action 908 can be performed according to a third size constraint of the MN (e.g., a constraint that the first and second nodes 114 may have when they become an MN).

[0238] The segmentation in action 908 can be based on the fourth result determined in action 906.

[0239] A sub-message can be understood as another message to be included in the message to be sent. The first sub-message can be understood as the first message. The second sub-message can be understood as the second sub-message. One of the first and second sub-messages can be, for example, an MCG reconfiguration message, and the other can be, for example, an SCG reconfiguration message.

[0240] Action 909

[0241] In some embodiments, where the first and second nodes 114 may receive a second indication that the first node 111 does not support segmentation, a start processing 907 message may be included in action 909, in which the first and second nodes 114 may send a second sub-message to be included in a message destined for the third node 113 to the first node 111. The size of the second sub-message may be lower than a first size limit that may not require segmentation.

[0242] In some embodiments, the message may be sent based on a further determined fifth result performed in action 906.

[0243] The first and second nodes 114 can, for example, perform the transmission action 909 via the corresponding fifth link 150.

[0244] Action 910

[0245] In some embodiments, initiating message processing 907 may include, in action 910, the first second node 114 sending the message to the third node 113. The message may or may not be segmented. Whether the message is sent segmented or not is based on: i) whether the message size exceeds a size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first second node 114 of one or more second nodes 112 supports message segmentation. For example, whether one or more second nodes 112 support message segmentation.

[0246] Size limitations can be, for example, PDCP SDU size limitations.

[0247] The size limit may be one of the following: a) a first size limit, combined size limit, or both supported by the first and second nodes 114 for segmenting the message; b) a second size limit, combined size limit, or both supported by the first and second nodes 114 for segmenting the message; and c) a corresponding second size limit, combined size limit, or both supported by one or more second nodes 112 for segmenting the message.

[0248] In the examples of embodiments relating to this article, whether a message is sent in segments or not can be based on at least one of i)-iv) or, for example, all of i)-iv).

[0249] The transmission can be performed, for example, via the third link 143.

[0250] In some embodiments where the first and second nodes 114 can serve the third node 113 via multiple connections with one or more second nodes 112 and the first node 111, at least one of the first node 111 and the first and second nodes 114 can be MN, and the other can be SN. In some of these embodiments, only MN and the third node 113 can support segmentation.

[0251] In some embodiments where the first second node 114 can serve the third node 113 via multiple connections with one or more second nodes 112 and the first node 111, at least one of the first node 111 and the first second node 114 can be MN, and the other can be SN. MN, SN, and the third node 113 can all support segmentation. The determination in action 906 can be based on whether at least one second sub-message from one or more second nodes 112, which is to be included in the message destined for the third node 113, can be segmented.

[0252] Messages can be sent based on the first result of a segment.

[0253] The message can be sent based on the determined second result of the action performed in action 906.

[0254] The message can be sent based on a further determined fifth result performed in action 906.

[0255] Examples of these actions and instructions are provided later in this document.

[0256] Some embodiments described herein will now be further described using some non-limiting examples.

[0257] In the following description, any reference to one / the MN (or simply "MN") may be understood to mean equally any one of the first node 111, one or more second nodes 112, and the first second node 114; any reference to one / the SN (or simply "SN") may be understood to mean equally any other one of the first node 111, one or more second nodes 112, and the first second node 114, that is, if MN is understood to be the first node 111, then SN is understood to be any one of the first second node 114 or one or more second nodes 112, and If MN is understood to be any one of one or more second nodes 112 or a first second node 114, then SN is understood to be a first node 111; any reference to a UE (or simply "UE") may be understood to equally refer to a third node 113; any reference to an X2 or Xn interface may be understood to equally refer to the corresponding fifth link 150; LTE may be considered a non-limiting example of a first radio technology (e.g., a first radio access technology), and NR may be considered a non-limiting example of a second radio technology (e.g., a second radio access technology). Any reference to an RRC message may be understood to equally apply to that message. Any reference to dual connectivity scenarios or handover may be understood to equally apply to coordinated radio communications between the first node 111 and one or more second nodes 112 (e.g., the first second node 114).

[0258] Some examples of the embodiments described herein can be understood as defining MN and SN behaviors for processing RRC messages that may exceed the PDCP limits for LTE and NR. More specifically, some examples of the embodiments described herein can be understood as providing a method for segmenting RRC messages in dual-connectivity scenarios, and can be understood as defining MN and SN behaviors in this regard. Examples of the embodiments described herein can be understood as proposing two approaches based on MN and SN capabilities, namely:

[0259] Method 1 (also referred to as "Solution 1" in this paper): Method 1 can be used if downlink RRC message segmentation is allowed for MN instead of SN in a dual-connectivity scenario. For Figure 12 Method 1 is described in detail.

[0260] Method 2 (also referred to as "Solution 2" in this paper): Method 2 can be used if both MN and SN can perform downlink RRC message segmentation in a dual-connectivity scenario. For Figure 13 Method 2 is described in detail.

[0261] These two methods are described in more detail below.

[0262] Examples of embodiments described herein can also be understood as providing methods for exchanging information about support for segmentation between MN and SN to ensure a consistent segmentation solution in dual-connectivity scenarios.

[0263] The examples of embodiments described herein can be understood to include processing for both the dual-connection establishment phase and the runtime phase.

[0264] Figure 10 This is a schematic signaling diagram illustrating a non-limiting example of a high-level signaling flow, particularly for RRC segmentation of messages, between a third node 113 (UE in this case), a first node 111 (MN in this case), and a first and second node 114 (SN in this case), according to embodiments of this document. Other variations are possible and will be described in several examples. In step 1001, the first node 111 determines, according to action 805, whether the first and second node 114 supports RRC segmentation and the applicable size limits. Step 1001 can be performed in several ways. One possibility is that the MN can retrieve capability information from the SN according to action 804 to determine whether the SN supports RRC segmentation. Another possibility is that the SN can also send this information to the MN according to action 804, even if no specific request or command is received from the MN. Yet another possibility is that the MN can be pre-configured with the capabilities of the SN. Furthermore, the MN can also determine other information related to RRC segmentation, such as, but not limited to, which size limits can be applied in the SN; or the maximum number of segments allowed. In step 1002, the first node 111 can obtain a first indication of its UE capabilities from the third node 113 according to action 801. Steps 1001 and 1002 may not need to follow... Figure 10The sequence described is executed. Step 1002 can also be executed before step 1001 because when the UE can register to the network, it can typically upload UE capabilities and then establish dual connectivity. It is also possible that dual connectivity can be enabled and disabled multiple times without receiving new UE capabilities from the UE. During handover, it is possible that the segmentation capabilities of the target MN or target SN may differ from those of the source MN or SN, respectively. This can be understood as meaning that step 1001 may need to be repeated, even if new UE capabilities may not be received from the UE. During handover, it is also possible that new UE capabilities can be received, for example, because the UE capabilities have changed, which may depend on the new MN and / or SN capabilities in the target MN and / or SN. It is also possible that the UE may need to disable certain features, such as to save battery, which may mean that the UE may need to upload new UE capabilities to the network. In step 1003, as part of action 807, the MN can determine whether RRC segments can be used for the current UE after receiving UE capabilities. As part of action 807, the MN can choose between solution 1, solution 2, and a fallback solution. Then, in step 1004, the MN can send this information to the SN according to action 802. However, several alternatives are possible. One alternative is that the MN can send its own RRC segmentation capability to the SN early in the initialization phase, possibly even before receiving the UE capability, according to action 802, and can then forward the UE capability or a subset thereof to the SN. In this case, the MN can delegate to the SN to determine whether the RRC segmentation can be used by the current UE. Therefore, in the embodiments herein, the first node 111 can be understood as a node that, after collecting information from the nodes involved in coordinating wireless communications, can determine whether the message segmentation can be used by the third node 113, regardless of whether the first node 111 is the MN or the SN. Another alternative could be, as an example of one or more second indications, sending only “RRC message size limit” signaling to the SN, which can then implicitly describe whether the SN is allowed to use the RRC segmentation. Yet another alternative to signaling “RRC message size limit” could be signaling “PDCP message size limit” or “SCG message configuration size limit”. If the segmentation capabilities of the MN and / or SN change, for example after handover to another cell (where the target MN and / or SN may have different segmentation capabilities than before the handover), step 1004 may also need to be updated. For example, if the UE may need to conserve battery power, the UE's segmentation capabilities may also change. Steps 1001, 1002, 1003, and 1004 may be included in the dual connectivity establishment phase.As part of the runtime phase, the first node 111 may receive the UE configuration of the SCG from the first and second nodes 114 in step 1005. If permitted and required, the UE configuration of the SCG is segmented to be included in the message to be sent by the first node 111 to the third node 113. In step 1006, according to action 807, the first node 111 may determine how to send the MCG and SCG configuration to the UE. Finally, in step 1007, according to action 809, the first node 111 may send a message to the third node 113, which includes the MCG and SCG configuration, and if permitted and required, the message is segmented as determined in action 807.

[0265] Figure 11 This is a signaling diagram illustrating a non-limiting example flowchart of a process for selecting a method (i.e., selecting between a fallback method, method 1, and method 2) as part of action 807 or action 906 according to embodiments herein. Other flowcharts may be possible. Although these steps are described as being performed by a first node 111, they may alternatively be performed by a node that makes the determination (e.g., a first or second node 114 in some examples). In step 1101, the first node 111 may, for example, determine a third node 113 (in the case of a first instruction received) based on a first instruction received. Figure 11 The first node 111 determines whether the UE supports RRC segmentation. If not, the first node 111 can determine whether to use a fallback method. The fallback method can be understood to include sending the MCG and SCG configurations to the UE using existing methods, and therefore will not be described further. If the third node 113 supports RRC segmentation, the first node 111 can determine whether the MN and / or SN support RRC segmentation. If neither the MN nor the SN supports RRC segmentation, the first node 111 can determine whether to use a fallback method. If only the MN supports RRC segmentation, the first node 111 can determine whether to use method 1. If both the MN and SN support RRC segmentation, the first node 111 can determine whether to use method 2.

[0266] Detailed description of Method 1

[0267] According to the first method (Method 1), in a dual-connectivity scenario, only the MN can be allowed to perform downlink RRC message segmentation. Figure 12A non-limiting example flowchart of Method 1 is shown. In this method, both the MN and the third node 113 (e.g., the UE) support RRC segmentation in the DL, but the SN does not. In step 1201, the SN sends a DL SCG reconfiguration message to the MN. When the MN receives the SCG reconfiguration from the SN, in step 1202, the MN can determine the size of the combined MCG+SCG reconfiguration message. In step 1203, the MN can determine, for example, according to action 807, whether the message size of the combined MCG+SCG reconfiguration message (MCG reconfiguration information includes the SCG reconfiguration message) might exceed the PDCP SDU size limit. In step 1204, if the size does not exceed the PDCP SDU size limit, the MN can send the MCG and SCG reconfigurations to the third node 113 in a single PDCP packet using existing methods. In step 1205, the MN can determine whether both the MCG and SCG reconfiguration messages are below the size limit. In step 1206, if the size of the combined MCG+SCG reconfiguration message exceeds the PDCP SDU size limit, but neither of the two reconfiguration messages exceeds the PDCP SDU size limit, then the MN can use existing methods to send the MCG and SCG reconfiguration messages to the third node 113 in different PDCP packets. In step 1207, if the size exceeds the PDCP SDU size limit, and if either of the two reconfiguration messages exceeds the PDCP SDU size limit, then the MN can segment the combined MCG+SCG reconfiguration message. Alternatively ( Figure 12 (Not shown in the image), if only one of the two MCG and SCG reconfiguration messages exceeds the PDCPSDU size limit, the MN may also choose to segment only the reconfiguration message that exceeds the size limit and send the other reconfiguration message in a separate PDCP packet. Alternatively ( Figure 12 (not shown in the image) If both the MCG and SCG reconfiguration messages exceed the PDCP SDU size limit, the MN can segment them separately without combining them into a combined MCG+SCG reconfiguration message.

[0268] Several alternatives to method 1 are possible, and these alternatives are described in the following examples.

[0269] 1.1 Example 1

[0270] In one example of the embodiments described herein, when processing SN-based RRC reconfiguration messages, the following sequence can be used in the MN. The SN can send a downlink SCG RRC reconfiguration message to the MN via backhaul. The RRC reconfiguration message may exceed the maximum PDCP SDU size of the configured SRB. The MN embeds the SCG RRC reconfiguration message into an MCG RRC reconfiguration message. The resulting message exceeds the maximum PDCP SDU size of the configured SRB. The MN can segment the resulting MCG RRC reconfiguration message into segments smaller than or equal to the maximum PDCP SDU size of the configured SRB, and can transmit these segments to the PDCP entity for transmission to the third node 113 (e.g., the UE). The difference compared to what is described above for method 1 can be understood as the MN possibly being unsure whether the MCG and SCG reconfiguration messages can be sent in separate PDCP packets, but can, for example, proceed directly to segmenting the combined MCG+SCG reconfiguration message according to action 308 (if performed by the first node 111).

[0271] 1.2 Example 2

[0272] In another example of the embodiments described herein, the MN may notify the SN of its support for segmentation, as described in action 802, for example. This can be done, for example, via the Xn / X2 interface in an initial configuration message (e.g., CG-config / CG-configinfo). Alternatively, this may be done during the setup of the Xn / X2 interface.

[0273] 1.3 Example 3

[0274] In another example based on Example 2 above, if the MN indicates to the SN that the MN, the third node 113 (e.g., the UE), or both do not support segmentation, the SN can ensure that the size of the reconfiguration message does not exceed the MN's PDCP size limit.

[0275] 1.4 Example 4

[0276] In another example, when the SN can send SCG reconfiguration information to the MN, the SN can consider information related to the type of PDCP entity that the MN can use to send RRC messages to the UE. For example, the SN can consider whether the MN can use an LTE PDCP entity defined in 3GPP TS 36.323 Release 16.0.0, or whether the MN can use an NR PDCP entity defined in 3GPP TS 38.323 Release 16.0.0. The maximum size of the PDCP PDU can differ in LTE PDCP and NR PDCP, and the SN can consider the version used by the MN when determining the size of the reconfiguration information. If the SN determines that the MN uses LTE PDCP, the SN can ensure that the reconfiguration information is small enough to comply with LTE PDCP limitations, taking into account any additional information that the MN may add. If the SN determines that the MN uses NR PDCP to send the reconfiguration information to the UE, the SN can consider the size limitations associated with the NR PDCP specification.

[0277] The SN can determine which PDCP version the MN can use based on indications from the MN (e.g., one or more indications sent in action 802). Alternatively, the SN can determine which PDCP version the MN can use based on what type of node the MN is. For example, if the node is an NR node, the SN can determine that the MN uses NR PDCP to send reconfiguration information to the UE, while if the MN is an LTE node, the SN may not implicitly know whether the MN is using LTE PDCP or LTE PDCP. In this case, the SN can determine the PDCP version. If the SN cannot explicitly determine which PDCP version the MN uses, the SN can assume that the MN uses the PDCP version with the minimum PDCP PDU size, such as LTE PDCP.

[0278] Another way to allow the SN to determine which PDCP version the MN uses is by having the SN determine this based on the RRC configuration in the MN that is applicable to the UE. Alternatively, in the case of handover (as described in the section titled "Handover" below), the target can determine this based on the configuration the UE has in the source node.

[0279] 1.5 Example 5

[0280] In another example, the source can determine whether the third node 113 (e.g., the UE) supports DL RRC segmentation. Furthermore, considering the potential overhead at the MN, the SN can ensure that the size of the reconfiguration message does not exceed the PDCP size limit at the MN. In one version of this example, the SN can determine this based on a first indication (e.g., UE capabilities). During dual connectivity establishment, the SN can obtain UE capabilities from the MN. In the case of handover (see later sections), the SN can obtain UE capabilities during the handover preparation phase.

[0281] Detailed description of Method 2

[0282] In Method 2, in a dual-connectivity scenario, both MN and SN are allowed to perform downlink RRC message segmentation. Figure 13 A non-limiting example flowchart of Method 2 is shown. In this method, both the MN and SN can support RRC segmentation in the DL. Because both the MN and SN can support RRC segmentation, in step 1301, the SN can segment the SCG reconfiguration message (if necessary) and then send it to the MN. In step 1302, the MN can then determine the size of the MCG reconfiguration message (including the SCG reconfiguration message). In step 1303, the MN can, for example, determine according to action 807 whether the message size exceeds the size limit. In step 1304, if the size does not exceed the PDCP SDU size limit, the MN can use existing methods to send the MCG and SCG reconfigurations to the UE in a single PDCP packet. In step 1305, the MN can, for example, determine according to action 807 whether the MCG reconfiguration message is below the size limit and whether the SCG reconfiguration message has been segmented. If the size of the combined MCG+SCG reconfiguration message exceeds the PDCP SDU size limit, but neither of the two reconfiguration messages exceeds the PDCP SDU size limit, the MN can use existing methods, such as according to action 809, to send the MCG and SCG reconfiguration messages to the UE in different PDCP packets. In step 1306, if the SN has already segmented the SCG reconfiguration message, the MN can, for example, according to action 809, send the MCG reconfiguration message (segmented if necessary) to the UE independently of the SCG reconfiguration information. In step 1307, if the MCG reconfiguration message (excluding the SCG reconfiguration information) exceeds the size limit, the MN can create a combined MCG+SCG reconfiguration message, and, for example, segment the combined MCG+SCG reconfiguration message according to action 808, then send it to the UE. Alternatively ( Figure 13(Not shown in the image), if the SCG reconfiguration message has been segmented, but the segment size does not match the segment size of the MN, the MN can merge the SCG reconfiguration messages and, for example, perform new segmentation according to action 808. This may include first creating a combined MCG+SCG reconfiguration message.

[0283] Several alternatives to Method 2 are possible, and these alternatives are described in the examples below.

[0284] 2.1 Example 6

[0285] In one example of Method 2, MN and SN can, for example, exchange support for segments during the initial DC setup via the X2 or Xn interface using, for example, CG-config / CG-configinfo messages, according to actions 802, 803, and 804.

[0286] 2.2 Example 7

[0287] In another example of the embodiments described herein, if both MN and SN support segmentation, but the third node 113 (e.g., UE) does not support segmentation, then MN can, for example, notify SN via the X2 or Xn interface that the UE does not support segmentation according to action 802.

[0288] 2.3 Example 8

[0289] In another example of the embodiments described herein, when processing SN-based RRC reconfiguration messages, the following sequence can be followed. The SN can segment the SCG RRC message and send it via backhaul to the MN, where the RRC reconfiguration message may exceed the maximum PDCP SDU size of the configured SRB. The MN can embed the segmented SCG RRC reconfiguration message into an MCG RRC reconfiguration message, where the resulting RRC reconfiguration message may also exceed the maximum PDCP SDU size of the configured SRB. If the resulting message exceeds the PDCP limit, the MN can, for example, according to action 808, segment the resulting MCG RRC reconfiguration message into smaller segments based on the currently configured maximum PDCP SDU size of the SRB, and can transmit these segments to the PDCP entity for transmission to a third node 113 (e.g., the UE). This can be understood as replacing steps 1002-1005, directly merging the MCG and SCG reconfiguration messages, and only determining whether the combined MCG+SCG reconfiguration message exceeds the PDCP SDU size limit.

[0290] 2.4 Example 9

[0291] In a variant of Example 8, the SN can segment the SCG reconfiguration message into smaller segments so that each segment may not exceed the PDCP limit for the MN node. This can be understood as segmenting based on the size limit of the MN, rather than based on the size limit of the SN.

[0292] 2.5 Example 10

[0293] In another variation of Example 8, the MN can, for example, provide the SN with an estimate of the MCG reconfiguration message size or the size that the SN can use for the SCG reconfiguration message via the Xn / X2 interface in the initial configuration message (e.g., CG-config / CG-configinfo), according to action 802. Regarding the estimate, two possibilities exist. The MN can provide an estimate of the MCG reconfiguration content in each segment along with the estimate, or it can provide the total size of the RRC reconfiguration message. Based on these two options, the SN can then create segments of the SCG reconfiguration message based on the following example. According to the first option, if the MN provides an estimate of the MCG reconfiguration content in each segment, the SN can segment the SCG reconfiguration message such that, taking into account the MN PDCP limitations, all SCG reconfiguration message segments can collectively match the MCG reconfiguration information. According to the second option, if MN provides an estimate of the total MCG reconfiguration content, SN can segment the SCG reconfiguration message so that the first SCG reconfiguration message segment can be matched with the MCG reconfiguration message, and the remainder of the SCG reconfiguration segment can be constructed with the consideration that the complete MCG segment can be used for the SCG reconfiguration segment.

[0294] Switch

[0295] The above example describes how, in a dual / multi-connection scenario, the primary node (MN) and secondary node (SN) can act to ensure that configuration messages (which may contain both components generated by the MN and components generated by the SN) can be sent to a third node 113 (e.g., the UE).

[0296] It's understandable that the two-connection scenario is just one example of where these methods can be applied. Another scenario where these methods can be applied is switching.

[0297] When a handover is performed, for example in NR or LTE, the network may send an RRCReconfiguration message or RRCConnectionReconfiguration (the name of this message in LTE) to a third node 113 (e.g., the UE). This reconfiguration message may be generated by the target node (i.e., the node that the third node 113 may move toward).

[0298] In addition, during the switching scenario, the following situation may occur: the configuration required by the target may cause the reconfiguration message to be too large, and thus exceed the size limit in the PDCP layer.

[0299] Similarly, based on some of the embodiments and / or examples described above, it is described how the SN can obtain an indication from the MN indicating whether the MN supports DL RRC message segmentation. In a handover scenario, a corresponding embodiment could be that the source can indicate to the target whether the source supports RRC segmentation. The target node can then take this information into account when determining the size constraints to consider when generating reconfiguration messages (e.g., handover messages).

[0300] Those skilled in the art will understand that the other embodiments described above can be applied to switching scenarios in a manner similar to a dual-connectivity scenario.

[0301] The embodiments described herein, or specific examples relating to the embodiments described herein, may be as follows:

[0302] In these specific examples, in the case of dual connectivity, the first node is SN and the second node is MN, while in the case of switching, the first node is the target node and the second node is the source node.

[0303] Specific Example 1: A method in a first node for providing configuration information to a UE via a second node includes:

[0304] - For example, according to action 902, receive an indication from the second node (MN) indicating whether the second node supports DL RRC segmentation.

[0305] - For example, according to action 901 or action 902, receive an indication indicating whether the UE supports DL RRC segmentation.

[0306] - If the second node and the UE support DL RRC segmentation, then, for example, according to Action 905, a first restriction (e.g., a large restriction) is applied to the reconfiguration information used for the UE.

[0307] - If neither the second node nor the UE supports DL RRC segmentation, then, for example, according to Action 905, a second restriction (e.g., a minor restriction) is applied to the reconfiguration information used for the UE.

[0308] Specific Example 2: A method in a second node for sending a reconfiguration, at least partially constructed by a first node, to the UE includes:

[0309] - For example, according to action 802, provide the second node with an indication of whether or not the reconfiguration message is supported or not.

[0310] For example, based on action 804, reconfiguration information is received from the first node.

[0311] - If the size exceeds the limit for the lower layer, then, for example, according to action 808, the obtained reconfiguration message is segmented, and

[0312] - For example, according to action 809, a reconfiguration message is sent to the device.

[0313] The specific embodiments disclosed herein can provide one or more of the following technical advantages, which can be summarized as follows. The embodiments herein can be understood as defining MN and SN behavior to handle RRC messages that may exceed PDCP limitations for, for example, LTE and NR. The embodiments herein can also provide methods for exchanging information between the MN and SN regarding support for segmentation to ensure a consistent segmentation solution in dual-connectivity scenarios.

[0314] Figure 14 Two different examples of arrangements that the first node 111 may include are shown in panels a) and b), respectively. In some embodiments, the first node 111 may include... Figure 14 The following arrangement is shown in diagram a. First node 111 can be understood as being used to process messages destined for third node 113. The messages are configured to include content from at least a first second node 114 of one or more second nodes 112. First node 111 is configured to coordinate with one or more second nodes 112 to process radio communications with third node 113. First node 111 is configured to operate within wireless communication network 100.

[0315] This document includes multiple embodiments. Components from one embodiment may be assumed to exist in another embodiment, and how these components can be used in other exemplary embodiments will be apparent to those skilled in the art. The detailed description in the following sections corresponds to the same reference provided above regarding the actions described for the first node 111, and therefore will not be repeated here. For example, in some embodiments, at least one of the following may be applied: i) the first node 111 may be configured to serve the third node 113 with one or more second nodes 112 using multiple connections; ii) the first node 111 may want to switch its connection with the third node 113 to a first second node 114 or to switch its connection with the third node 113 from the first second node 114; iii) in multiple connections, the first node 111 may be configured to be the MN of the third node 113, and one or more second nodes 112 may be configured to be the SN of the third node 113; iv) in multiple connections, the first second node 114 may be configured to be the MN of the third node 113, and the first node 111 and one or more other second nodes 112 may be configured to be the third node 113. SN 113, v) First node 111 can be configured as the source node of third node 113, and first second node 114 can be configured as the target node of third node 113, vi) First node 111 can be configured as the target node of third node 113, and first second node 114 can be configured as the source node of third node 113, vii) First node 111 can be configured as DU, and first second node 114 can be configured as CU, viiii) First node 111 can be configured as CU, and each of one or more second nodes 112 can be configured as DU, and ix) First node 111 can be configured as the first DU, and any one of one or more second nodes 112 can be configured as another DU.

[0316] The message can be configured as an RRC message.

[0317] exist Figure 14 In the text, optional units are represented by dashed boxes.

[0318] The first node 111 is configured to perform the sending of action 809, for example, by means of a sending unit 1401 within the first node 111, the sending unit 1401 being configured to send a message to the third node 113. The message is configured to be segmented or not segmented. Whether the message is sent segmented or not is configured based on: i) whether the size of the message exceeds a size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first second node 114 of one or more second nodes 112 is configured to support message segmentation.

[0319] The first node 111 can be configured to perform segmentation of action 808, for example by means of segmentation unit 1402, which is configured to segment at least one of the following: a) a first sub-message from the first node 111 to be included in a message to the third node 113; b) at least one corresponding second sub-message configured to be received from one or more second nodes 112 and to be included in a message to the third node 113; and c) a combination of the first sub-message and at least one corresponding second sub-message.

[0320] The message can be configured to be sent based on the first result of the segment.

[0321] The first node 111 can be configured, for example, to perform the determination of action 807 by means of a determining unit 1403, which is configured to determine whether to segment the message based on: i) whether the message size exceeds a size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first second node 114 of one or more second nodes 112 supports message segmentation. The message can be configured to be sent based on the determined second result.

[0322] In some embodiments, determining whether to segment a message based on whether its size exceeds a size limit can be configured to further determine at least one of the following: a) whether a first sub-message from a first node 111 to be included in a message destined for a third node 113 exceeds a first size limit; b) whether one or more second sub-messages, configured to be received from one or more second nodes 112 respectively and to be included in a message destined for the third node 113, exceed a corresponding second size limit; and c) whether a combination of the first sub-message and one or more second sub-messages exceeds a combination size limit. The message can be configured to be sent based on a further determined third result.

[0323] In some embodiments, the combination of a first sub-message and one or more second sub-messages may exceed the combination size limit, and the first node 111 may also be configured to segment the combination.

[0324] In some embodiments, the first node 111 may also be configured as at least one of the following.

[0325] The first node 111 can be configured to perform the acquisition of action 801, for example, by means of acquisition unit 1404, which is configured to acquire a first indication, the first indication being configured to indicate whether the third node 113 supports message segmentation.

[0326] The first node 111 can be configured to perform the transmission of action 802, for example, by means of a sending unit 1401, which is configured to send one or more second indications to at least one of one or more second nodes 112. The one or more second indications can be configured to indicate at least one of the following: i) whether the third node 113 supports message segmentation, ii) whether the first node 111 supports message segmentation, iii) a first version of segmentation supported by the first node 111, and iv) a first size limit, combined size limit, or both for message segmentation supported by the first node 111.

[0327] The first node 111 can be configured to perform this reception of action 803, for example, by means of a receiving unit 1405, which is configured to receive one or more corresponding third indications from one or more second nodes 112. The one or more corresponding third indications can be configured to indicate at least one of the following: i) whether one or more second nodes 112 support message segmentation, ii) a corresponding second version of the segmentation supported by one or more second nodes 112, and iii) a corresponding second size limit, combined size limit, or both for message segmentation supported by one or more second nodes 112.

[0328] The first node 111 can be configured to perform the reception of action 804, for example, by means of a receiving unit 1405, which is configured to receive a third indication from the first and second nodes 114. The third indication can be configured to indicate at least one of the following: i) whether the first and second nodes 114 support message segmentation, ii) a second version of segmentation supported by the first and second nodes 114, and iii) a second size limit, a combined size limit, or both supported by the first and second nodes 114 for segmenting messages.

[0329] The first node 111 can be configured to perform the determination of action 805, for example by means of a determination unit 1403, which is configured to determine at least one of the following: i) a corresponding second version of a segment supported by one or more second nodes 112, ii) a corresponding second size limit, combined size limit, or both for segmenting a message supported by one or more second nodes 112, iii) a second version of a segment supported by the first second node 114, and iv) a second size limit, combined size limit, or both for segmenting a message supported by the first second node 114.

[0330] In some embodiments where the first node 111 can be configured to send a second indication indicating that the first node 111 does not support segmentation to at least the first and second nodes 114, the first node 111 can also be configured, for example, to perform the reception of action 803 by means of a receiving unit 1405, which is configured to receive from at least the first and second nodes 114 a second sub-message to be included in the message destined for the third node 113. The second sub-message can be configured to be smaller than a first size limit configured not to require segmentation.

[0331] In some embodiments where the first node 111 can be configured to serve the third node 113 via multiple connections with one or more second nodes 112, at least one of the first node 111 and the first and second nodes 114 can be configured as MN, and the other can be configured as SN. Only MN and the third node 113 can be configured to support segmentation.

[0332] In some embodiments where the first node 111 can be configured to serve the third node 113 via multiple connections with one or more second nodes 112, at least one of the first node 111 and the first and second nodes 114 can be configured as MN, and the other can be configured as SN. MN, SN, and the third node 113 can all be configured to support segmentation, and the messages sent can be configured to be segmented based on whether at least one of one or more second sub-messages from one or more second nodes 112 to be included in the message destined for the third node 113 is segmented.

[0333] In some embodiments where the first node 111 can be configured as SN, the first and second nodes can be configured as MN, and the segmentation can be configured to be performed according to a third size limit of MN.

[0334] The first node 111 may include other units 1406.

[0335] It can be done through one or more processors (e.g. Figure 14 The embodiments of the present invention are implemented in the first node 111 by a processor 1407 in the first node 111 shown herein and by computer program code for performing the functions and actions of the embodiments herein. As used herein, a processor can be understood as a hardware component. The program code described above can also be provided as a computer program product, for example in the form of a data carrier carrying computer program code, which, when loaded into the first node 111, is used to perform the embodiments herein. One such carrier can be in the form of a CD-ROM. However, other data carriers such as memory sticks are feasible. Furthermore, the computer program code can be provided as plain program code on a server and downloaded to the first node 111.

[0336] The first node 111 may also include a memory 1408, which includes one or more storage units. The memory 1408 is arranged to store acquired information, such as data, configurations, schedules, and applications, which execute the methods described herein when executed in the first node 111.

[0337] In some embodiments, the first node 111 may receive information via the receive port 1409, for example, from the third node 113, one or more second nodes 112, and / or the first and second nodes 114. In some embodiments, the receive port 1409 may be connected, for example, to one or more antennas in the first node 111. In other embodiments, the first node 111 may receive information via the receive port 1409 from another structure in the wireless communication network 100. Because the receive port 1409 can communicate with the processor 1407, the receive port 1409 can then send the received information to the processor 1407. The receive port 1409 may also be configured to receive other information.

[0338] The processor 1407 in the first node 111 can also be configured to send information, for example, to a third node 113, one or more second nodes 112, a first second node 114 and / or another structure in the wireless communication network 100 via a transmit port 1410, which can communicate with the processor 1407 and the memory 1408.

[0339] Those skilled in the art will also understand that the aforementioned units 1401-1406 may involve a combination of analog and digital circuitry and / or one or more processors configured with software and / or firmware stored, for example, in memory, which, when executed by one or more processors (e.g., processor 1407), execute as described above. One or more of these processors, along with other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed among multiple individual components (whether individually packaged or assembled into a system-on-a-chip (SoC)).

[0340] Furthermore, in some embodiments, the different units 1401-1406 described above can be implemented as one or more applications running on one or more processors (e.g., processor 1407).

[0341] Therefore, the method for the first node 111 according to the embodiments described herein can be implemented accordingly by means of a computer program 1411 product including instructions (i.e., software code portions) that, when executed on at least one processor 1407, cause at least one processor 1407 to perform the actions performed by the first node 111 as described herein. The computer program 1411 product can be stored on a computer-readable storage medium 1412. The computer-readable storage medium 1412 on which the computer program 1411 is stored can include instructions that, when executed on at least one processor 1407, cause at least one processor 1407 to perform the actions performed by the first node 111 as described herein. In some embodiments, the computer-readable storage medium 1412 can be a non-transitory computer-readable storage medium, such as a CD-ROM and a memory stick. In other embodiments, the computer program 1411 product can be stored on a carrier containing the computer program 1411 just described, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 1412 as described above.

[0342] The first node 111 may include a communication interface configured to facilitate communication between the first node 111 and other nodes or devices (e.g., a third node 113, one or more second nodes 112, a first second node 114, and / or another structure in the wireless communication network 100). This interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface according to appropriate standards.

[0343] In other embodiments, the first node 111 may include Figure 14 The following arrangement is shown in b. The first node 111 may include processing circuitry 1407 (e.g., one or more processors, such as processor 1407 in the first node 111) and memory 1408. The first node 111 may also include radio circuitry 1413, which may include, for example, a receive port 1409 and a transmit port 1410. The processing circuitry 1407 may be configured or operable to be adapted to... Figure 14 The method described above is used to execute according to... Figure 8 , Figure 10-13 and / or Figure 17-21 The method of operation. Radio circuit 1413 can be configured to establish and maintain a wireless connection with at least a third node 113, one or more second nodes 112, a first second node 114, and / or another structure in the wireless communication network 100. In this document, the circuit can be understood as a hardware component.

[0344] Therefore, embodiments herein also relate to a first node 111 operable in a wireless communication network 100. The first node 111 may include processing circuitry 1407 and a memory 1408 containing instructions executable by the processing circuitry 1407, thereby also enabling the first node 111 to perform, for example, the operations described herein. Figure 8 , Figure 10-13 and / or Figure 17-21 The action described for the first node 111.

[0345] Figure 15 Two different examples of arrangements that the first and second nodes 114 may include are shown in panels a) and b), respectively. In some embodiments, the first and second nodes 114 may include Figure 15 The following arrangement is shown in diagram a. First and second nodes 114 can be understood as being used to process messages destined for third node 113. The messages are configured to include content from at least the first and second nodes 114 of one or more second nodes 112. The first and second nodes 114 are configured to at least cooperate with the first node 111 in processing radio communications with the third node 113. The first and second nodes 114 are configured to operate within the wireless communication network 100.

[0346] This document includes multiple embodiments. Components from one embodiment may be assumed to exist in another embodiment, and how these components can be used in other exemplary embodiments will be apparent to those skilled in the art. The detailed description in the following sections corresponds to the same reference provided above regarding the actions described for first node 111 and first second node 114, and therefore will not be repeated here. For example, in some embodiments, at least one of the following may be applied: i) first second node 114 may be configured to serve third node 113 with first node 111, one or more second nodes 112, or both using multiple connections; ii) first second node 114 may want to switch its connection with third node 113 to first node 111 or to switch its connection with third node 113 from first node 111; iii) in multiple connections, first node 111 may be configured as the MN of third node 113, and one or more second nodes 112 may be configured as the SN of third node 113; iv) in multiple connections, first second node 114 may be configured as the MN of third node 113, and first node 111 and one or more other second nodes 112 may be configured... v) The first node 111 can be configured as the source node of the third node 113, and the first and second nodes 114 can be configured as the target node of the third node 113. vi) The first node 111 can be configured as the target node of the third node 113, and the first and second nodes 114 can be configured as the source node of the third node 113. vii) The first node 111 can be configured as a DU, and the first and second nodes 114 can be configured as a CU. viiii) The first node 111 can be configured as a CU, and each of one or more second nodes 112 can be configured as a DU. ix) The first node 111 can be configured as the first DU, and any one of one or more second nodes 112 can be configured as another DU.

[0347] This message can be configured to be an RRC message.

[0348] exist Figure 15 In the text, optional units are represented by dashed boxes.

[0349] The first and second nodes 114 can be configured to perform the determination of action 907, for example, by means of a determination unit 1501, which is configured to determine whether to segment the message based on: i) whether the size of the message exceeds a size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first and second nodes 114 of one or more second nodes 112 support message segmentation.

[0350] The first and second nodes 114 can be configured, for example, to perform the startup process of action 907 by means of the startup unit 1502 within the first and second nodes 114, the startup unit 1502 being configured to start the message processing based on a determined fourth result.

[0351] In some embodiments, the initiation processing message may be configured to include: the first second node 114 may be configured to perform segmentation of action 908, for example by means of segmentation unit 1503, which is configured to segment at least one of the following: a) a second sub-message from the first second node 114 to be included in a message to the third node 113, b) a first sub-message from the first node 111 to be included in a message to the third node 113, c) at least one corresponding second sub-message received from one or more second nodes 112 and to be included in a message to the third node 113, and d) a combination of the following: the first sub-message, and at least one of the second sub-message and at least one corresponding second sub-message.

[0352] Segmentation can be configured to be based on a determined fourth result.

[0353] In some embodiments, the initiation processing message can be configured to include: the first and second nodes 114 can be configured, for example, by means of a sending unit 1504 within the first and second nodes 114, the sending unit 1504 being configured to send a message to the third node 113. The message can be configured to be segmented or not segmented. Whether the message is sent in segments or not can be configured based on: i) whether the size of the message exceeds a size limit, ii) whether the third node 113 supports message segmentation, iii) whether the first node 111 supports message segmentation, and iv) whether at least the first and second nodes 114 of one or more second nodes 112 are configured to support message segmentation.

[0354] In some embodiments, determining whether to segment a message based on whether its size exceeds a size limit can be configured to further determine at least one of the following: a) whether a first sub-message from a first node 111 to be included in a message destined for a third node 113 exceeds a first size limit; b) whether a second sub-message from a first or second node 114 to be included in a message destined for a third node 113 exceeds a second size limit; c) whether one or more corresponding second sub-messages, configured to be received from one or more second nodes 112 and to be included in a message destined for a third node 113, exceed their respective second size limits; and d) whether a combination of the first and second sub-messages and / or one or more corresponding second sub-messages exceeds a combination size limit. The message can be configured to be sent based on a further determined fifth result.

[0355] In some embodiments, the combination exceeds the combination size limit, and the first and second nodes 114 may also be configured to segment the combination.

[0356] In some embodiments, the first and second nodes 114 may also be configured as at least one of the following.

[0357] The first and second nodes 114 can be configured, for example, to perform the acquisition of action 901 by means of acquisition unit 1505, which is configured to acquire a first indication that indicates whether the third node 113 supports message segmentation.

[0358] The first and second nodes 114 can be configured, for example, to perform the reception of action 902 by means of a receiving unit 1506, which is configured to receive one or more second indications from the first node 111. The one or more second indications can be configured to indicate at least one of the following: i) whether the third node 113 supports message segmentation, ii) whether the first node 111 supports message segmentation, iii) a first version of segmentation supported by the first node 111, and iv) a first size limit, combined size limit, or both for message segmentation supported by the first node 111.

[0359] The first and second nodes 114 can be configured to perform the reception of action 903, for example, by means of a receiving unit 1506, which is configured to receive one or more corresponding third indications from one or more second nodes 112. The one or more corresponding third indications can be configured to indicate at least one of the following: i) whether one or more second nodes 112 support message segmentation, ii) a corresponding second version of the segmentation supported by one or more second nodes 112, and iii) a corresponding second size limit, combined size limit, or both for message segmentation supported by one or more second nodes 112.

[0360] The first and second nodes 114 can be configured to perform the transmission of action 904, for example, by means of a sending unit 1504, which is configured to send a third indication to at least one of the other nodes in the first node 111 and one or more second nodes 112. The third indication can be configured to indicate at least one of the following: i) whether the first and second nodes 114 support message segmentation, ii) a second version of the segmentation supported by the first and second nodes 114, and iii) a second size limit, a combined size limit, or both supported by the first and second nodes 114 for segmenting the message.

[0361] The first and second nodes 114 can be configured to perform the determination of action 905, for example by means of a determination unit 1501, which is configured to determine at least one of the following: i) a corresponding second version of a segment supported by one or more second nodes 112, ii) a corresponding second size limit, combined size limit, or both for segmenting a message supported by one or more second nodes 112, iii) a second version of a segment supported by the first node 111, and iv) a first size limit, combined size limit, or both for segmenting a message supported by the first node 111.

[0362] In some embodiments where the first and second nodes 114 can be configured to receive a second indication that the first node 111 does not support segmentation, the initiation processing message can be configured to include: the first and second nodes 114 can also be configured, for example, by means of a sending unit 1504, which is configured to send a second sub-message to be included in the message destined for the third node 113 to the first node 111. The size of the second sub-message is lower than a first size limit configured not to require segmentation.

[0363] In some embodiments where the first and second nodes 114 can be configured to serve the third node 113 via multiple connections with one or more second nodes 112 and the first node 111, at least one of the first node 111 and the first and second nodes 114 can be configured as MN, and the other can be configured as SN. Only MN and the third node 113 can be configured to support segmentation.

[0364] In some embodiments where the first second node 114 can be configured to serve the third node 113 via multiple connections with one or more second nodes 112 and the first node 111, at least one of the first node 111 and the first second node 114 can be configured as MN, and the other can be configured as SN. MN, SN, and the third node 113 can all be configured to support segmentation, and the determination can be based on whether at least one second sub-message from one or more second nodes 112, to be included in a message destined for the third node 113, is segmented.

[0365] In some embodiments where the first node 111 can be configured as SN, the first and second nodes can be configured as MN, and the segmentation can be configured to be performed according to a third size limit of MN.

[0366] The first and second nodes 114 may include other units 1507.

[0367] It can be done through one or more processors (e.g. Figure 15The embodiments in the first and second nodes 114 shown herein are implemented by a processor 1508 and computer program code for performing the functions and actions of the embodiments herein. As used herein, a processor can be understood as a hardware component. The program code described above can also be provided as a computer program product, for example in the form of a data carrier carrying computer program code, which, when loaded into the first and second nodes 114, is used to perform the embodiments herein. One such carrier can be in the form of a CD-ROM. However, other data carriers such as memory sticks are feasible. Furthermore, the computer program code can be provided as plain program code on a server and downloaded to the first and second nodes 114.

[0368] The first and second nodes 114 may also include a memory 1509, which includes one or more storage units. The memory 1509 is arranged to store acquired information, such as data, configurations, schedules, and applications, which execute the methods described herein when executed in the first and second nodes 114.

[0369] In some embodiments, the first and second nodes 114 may receive information via the receiving port 1510, for example, from a third node 113, one or more other second nodes 112, and / or a first node 111. In some embodiments, the receiving port 1510 may be connected, for example, to one or more antennas in the first and second nodes 114. In other embodiments, the first and second nodes 114 may receive information via the receiving port 1510 from another structure in the wireless communication network 100. Because the receiving port 1510 can communicate with the processor 1508, the receiving port 1510 can then send the received information to the processor 1508. The receiving port 1510 may also be configured to receive other information.

[0370] The processor 1508 in the first and second nodes 114 can also be configured to send information, for example, to a third node 113, one or more other second nodes 112, the first node 111, and / or another structure in the wireless communication network 100 via a transmit port 1511, which can communicate with the processor 1508 and the memory 1509.

[0371] Those skilled in the art will also understand that the aforementioned units 1501-1507 may involve a combination of analog and digital circuitry and / or one or more processors configured with software and / or firmware stored, for example, in memory, which, when executed by one or more processors (e.g., processor 1508), execute as described above. One or more of these processors, along with other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed among multiple individual components (whether individually packaged or assembled into a system-on-a-chip (SoC)).

[0372] Furthermore, in some embodiments, the different units 1501-1507 described above can be implemented as one or more applications running on one or more processors (e.g., processor 1508).

[0373] Therefore, the methods for the first and second nodes 114 according to the embodiments described herein can be implemented by means of a computer program 1512 product including instructions (i.e., software code portions) that, when executed on at least one processor 1508, cause at least one processor 1508 to perform the actions described herein performed by the first and second nodes 114. The computer program 1512 product can be stored on a computer-readable storage medium 1513. The computer-readable storage medium 1513 on which the computer program 1512 is stored can include instructions that, when executed on at least one processor 1508, cause at least one processor 1508 to perform the actions described herein performed by the first and second nodes 114. In some embodiments, the computer-readable storage medium 1513 can be a non-transitory computer-readable storage medium, such as a CD-ROM disk and a memory stick. In other embodiments, the computer program 1512 product can be stored on a carrier containing the computer program 1512 just described, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 1513 as described above.

[0374] The first and second nodes 114 may include a communication interface configured to facilitate communication between the first and second nodes 114 and other nodes or devices (e.g., a third node 113, one or more other second nodes 112, a first node 111, and / or another structure in the wireless communication network 100). This interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface according to appropriate standards.

[0375] In other embodiments, the first and second nodes 114 may include Figure 15The following arrangement is shown in b. The first and second nodes 114 may include processing circuitry 1508 (e.g., one or more processors, such as processor 1508 in the first and second nodes 114) and memory 1509. The first and second nodes 114 may also include radio circuitry 1514, which may include, for example, a receive port 1510 and a transmit port 1511. The processing circuitry 1508 may be configured or operable to be adapted to... Figure 15 The method described above can be used to execute according to... Figure 9 , Figure 10-13 and / or Figure 17-21 The method of operation. Radio circuit 1514 can be configured to establish and maintain at least a wireless connection with a third node 113, one or more other second nodes 112, a first node 111, and / or another structure in the wireless communication network 100. In this document, circuitry can be understood as hardware components.

[0376] Therefore, embodiments herein also relate to a first and second node 114 operable in a wireless communication network 100. The first and second node 114 may include processing circuitry 1508 and a memory 1509 containing instructions executable by the processing circuitry 1508, thereby also enabling the first and second node 114 to perform, for example, the operations described herein. Figure 9 , Figure 10-13 and / or Figure 17-21 The actions described in the first and second nodes 114.

[0377] As used herein, the expression "at least one:" followed by a comma-separated list of alternatives, with the last alternative preceding the term "and," can be understood to mean that only one of the alternatives in the list can be applied, multiple alternatives in the list can be applied, or all alternatives in the list can be applied. This expression can be understood as equivalent to the expression "at least one:" followed by a comma-separated list of alternatives, with the last alternative preceding the term "or."

[0378] When the words “include” or “contain” are used, they will be interpreted as non-restrictive, meaning “consisting of at least…”.

[0379] In this article, the processor can be understood as a hardware component.

[0380] The embodiments described herein are not limited to the preferred embodiments described above. Various alternatives, modifications, and equivalents may be used. Therefore, the above embodiments should not be considered as limiting the scope of the invention.

[0381] Other extensions and variations

[0382] Figure 16Telecommunications networks connected to host computers via an intermediate network according to some embodiments

[0383] refer to Figure 16 According to an embodiment, a communication system includes a telecommunications network 1610, such as a wireless communication network 100, for example a 3GPP-type cellular network, which includes an access network 1611, such as a radio access network, and a core network 1614. The access network 1611 includes any one or two of a plurality of network nodes, such as a first node 111 and one or more second nodes 112 (e.g., the first and second nodes 114). For example, base stations 1612a, 1612b, 1612c, such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 1613a, 1613b, 1613c. Each base station 1612a, 1612b, 1612c can be connected to the core network 1614 via a wired or wireless connection 1615. The wireless communication network 100 includes a plurality of wireless devices, such as wireless device 130. Figure 16 In this example, a first UE 1691 located in coverage area 1613c is configured to wirelessly connect to or be paged by a corresponding base station 1612c. A second UE 1692 in coverage area 1613a may wirelessly connect to a corresponding base station 1612a. Although multiple UEs 1691 and 1692 are shown in this example, the disclosed embodiments are equally applicable to cases where only one UE is in the coverage area or only one UE is connected to the corresponding base station 1612. Either UE 1691 or 1692 is an example of wireless device 130.

[0384] Telecommunications network 1610 is itself connected to host computer 1630, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. Host computer 1630 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 1621 and 422 between telecommunications network 1610 and host computer 1630 may extend directly from core network 1614 to host computer 1630, or via optional intermediate network 1620. Intermediate network 1620 may be one of public, private, or hosted networks, or a combination of several of them; intermediate network 1620 (if any) may be a backbone network or the Internet; in particular, intermediate network 1620 may include two or more subnetworks (not shown).

[0385] Overall, Figure 16The communication system establishes a connection between the connected UEs 1691 and 1692 and the host computer 1630. This connection can be described as an over-the-top (OTT) connection 1650. The host computer 1630 and the connected UEs 1691 and 1692 are configured to transmit data and / or signaling via the OTT connection 1650 using access network 1611, core network 1614, any intermediate network 1620, and possibly other infrastructure (not shown) as intermediaries. Because the participating communication devices through which the OTT connection 1650 passes are unaware of the routes for uplink and downlink communications, the OTT connection 1650 can be transparent. For example, it may not be necessary to inform the base station 1612 of the past routes for incoming downlink communications containing data originating from the host computer 1630 that will be forwarded (e.g., handed over) to the connected UE 1691. Similarly, base station 1612 does not need to know the future route of outgoing uplink communication originating from UE 1691 toward host computer 1630.

[0386] Regarding the following description Figure 17 , 18 19, 20, and 21, it is understood that the UE is an example of the wireless device 130, and any description provided for the UE also applies to the wireless device 130. It is also understood that the base station is an example of any one or both of the first node 111 and one or more second nodes 112 (e.g., first or second node 114), and any description provided for the base station also applies to any one or both of the first node 111 and one or more second nodes 112 (e.g., first or second node 114).

[0387] Figure 17 A host computer that communicates with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0388] According to the embodiments, reference will now be made to Figure 17Example implementations of the wireless device 130 (e.g., UE), first node 111 (e.g., base station), and host computer discussed in the preceding paragraphs are described. In the communication system 1700 (e.g., wireless communication network 100), the host computer 1710 includes hardware 1715, which includes a communication interface 1716 configured to establish and maintain wired or wireless connections with different communication devices of the communication system 1700. The host computer 1710 also includes processing circuitry 1718, which may have storage and / or processing capabilities. Specifically, the processing circuitry 1718 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The host computer 1710 also includes software 1711, which is stored in or accessible by the host computer 1710 and executable by the processing circuitry 1718. The software 1711 includes a host application 1712. Host application 1712 is operable to provide services to remote users (such as UE 1730) connected via OTT connection 1750 terminated between UE 1730 and host computer 1710. In providing services to remote users, host application 1712 can provide user data sent using OTT connection 1750.

[0389] The communication system 1700 also includes a first node 111, which is in Figure 17 The example is exemplified as base station 1720, which is installed in a telecommunications system and includes hardware 1725 enabling it to communicate with host computer 1710 and UE 1730. Hardware 1725 may include a communication interface 1726 for establishing and maintaining wired or wireless connections with different communication devices of communication system 1700, and for establishing and maintaining connections with the coverage area served by base station 1720. Figure 17 Wireless device 130 (not shown in the image) Figure 17 The radio interface 1727 of at least wireless connection 1770 (exemplified as UE 1730) is configured to facilitate connection 1760 with host computer 1710. Connection 1760 can be direct or can be via the core network of a telecommunications system (UE 1730). Figure 17 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1725 of base station 1720 also includes processing circuitry 1728, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 1720 also has software 1721 that is internally stored or accessible via an external connection.

[0390] The communication system 1700 also includes the previously mentioned UE 1730. The hardware 1735 of UE 1730 may include a radio interface 1737 configured to establish and maintain a wireless connection 1770 with a base station serving the coverage area where UE 1730 is currently located. The hardware 1735 of UE 1730 also includes processing circuitry 1738, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. UE 1730 also includes software 1731 stored in or accessible by UE 1730 and executable by processing circuitry 1738. The software 1731 includes a client application 1732. The client application 1732 is operable to provide services to human or non-human users via UE 1730 with the support of host computer 1710. In host computer 1710, the executing host application 1712 can communicate with the executing client application 1732 via OTT connection 1750 terminated between UE 1730 and host computer 1710. In providing services to the user, client application 1732 can receive request data from host application 1712 and provide user data in response to the request data. OTT connection 1750 can transmit both request data and user data. Client application 1732 can interact with the user to generate user data provided by the user.

[0391] Notice, Figure 17 The host computer 1710, base station 1720, and UE 1730 shown can be respectively connected to... Figure 16 The host computer 1630, base stations 1612a, 1612b, and 1612c are similar to or identical to one of the UEs 1691 and 1692. That is to say, the internal working principles of these entities can be as follows: Figure 17 As shown, and independently, the surrounding network topology can be Figure 16 The surrounding network topology.

[0392] exist Figure 17 The OTT connection 1750 has been abstractly depicted to illustrate communication between host computer 1710 and UE 1730 via base station 1720, without explicitly referencing any intermediate devices or the precise routing of messages via those devices. The network infrastructure can determine the route, and can be configured to hide that route from UE 1730 or the service provider operating host computer 1710, or both. When OTT connection 1750 is active, the network infrastructure can further make decisions, dynamically altering the route (e.g., based on load balancing considerations or network reconfiguration).

[0393] The wireless connection 1770 between UE 1730 and base station 1720 is based on the teachings of embodiments described throughout this disclosure. One or more embodiments in various embodiments improve the performance of OTT services provided to UE 1730 using OTT connection 1750 (where wireless connection 1770 forms the final segment). More precisely, the teachings of these embodiments can improve latency, signaling overhead, and service interruption, thereby providing benefits such as reduced user wait time, better responsiveness, and extended battery life.

[0394] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved thereon in one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection 1750 between host computer 1710 and UE 1730 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 1750 may be implemented in software 1711 and hardware 1715 of host computer 1710, or in software 1731 and hardware 1735 of UE 1730, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication equipment traversed by the OTT connection 1750. Sensors may participate in the measurement procedures by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which software 1711, 1731 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1750 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not necessarily affect base station 1720, and it may be unknown or imperceptible to base station 1720. Such processes and functions are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 1710 in measuring throughput, propagation time, latency, etc. Measurements can be made because software 1711 and 1731 cause the use of OTT connection 1750 to send messages, particularly empty or "dummy" messages, while they are monitoring message propagation time, errors, etc.

[0395] The first node embodiment involves Figure 8 , Figure 10-13 , Figure 14 and Figure 17-21 .

[0396] The first node 111 can also be configured to transmit user data to the host application unit in the host computer 1710, for example, via another link (e.g., 1750).

[0397] The first node 111 may include, for example: Figure 14 or Figure 17 The layout shown.

[0398] The first and second node embodiments involve Figure 9 , Figure 10-13 , Figure 15 and Figure 17-21 .

[0399] The first and second nodes 114 can also be configured to transmit user data to the host application unit in the host computer 1710, for example, via another link (e.g., 1750).

[0400] The first and second nodes 114 may include, for example, Figure 15 or Figure 17 The layout shown.

[0401] Figure 18 Methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0402] Figure 18 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 16 and Figure 17 The host computer, base station, and UE are described. For the sake of simplicity in this disclosure, this section only includes descriptions of... Figure 18 Referring to the accompanying drawings. In step 1810, the host computer provides user data. In sub-step 1811 of step 1810 (which may be optional), the host computer provides user data by executing a host application. In step 1820, the host computer initiates a transmission carrying user data to the UE. In step 1830 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1840 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0403] Figure 19 Methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0404] Figure 19 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 16 and Figure 17 The host computer, base station, and UE are described. For the sake of simplicity in this disclosure, this section only includes descriptions of... Figure 19Referring to the accompanying drawings. In step 1910, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1920, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission can be performed via a base station. In step 1930 (which may be optional), the UE receives the user data carried in the transmission.

[0405] Figure 20 Methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0406] Figure 20 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 16 and Figure 17 The host computer, base station, and UE are described. For the sake of simplicity in this disclosure, this section only includes descriptions of... Figure 20 Referring to the accompanying drawings. In step 2010 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2020, the UE provides user data. In sub-step 2021 of step 2020 (which may be optional), the UE provides user data by executing a client application. In sub-step 2011 of step 2010 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 2030 (which may be optional). In step 2040 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0407] Figure 21 Methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0408] Figure 21 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 16 and Figure 17 The host computer, base station, and UE are described. For the sake of simplicity in this disclosure, this section only includes descriptions of... Figure 21Refer to the accompanying drawings. In step 2110 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 2120 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 2130 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0409] Any suitable steps, methods, features, functions, or benefits disclosed herein can be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry that may include one or more microprocessors or microcontrollers and other digital hardware that may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0410] The term “unit” may have its conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing the corresponding tasks, processes, calculations, outputs and / or display functions as described herein.

[0411] Other numbered examples

[0412] 1. A base station configured to communicate with a user equipment (UE), the base station including a radio interface and processing circuitry configured to perform one or more actions as described herein, performed by a first node 111 or a first second node 114.

[0413] 5. A communication system including a host computer, the host computer comprising:

[0414] Processing circuitry, configured to provide user data; and

[0415] The communication interface is configured to forward user data to the cellular network for transmission to the user equipment (UE).

[0416] The cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of which is configured to perform one or more actions as described herein, performed by a first node 111 or a first or second node 114.

[0417] 6. The communication system according to Embodiment 5 further includes a base station.

[0418] 7. The communication system according to Embodiment 6 further includes a UE, wherein the UE is configured to communicate with a base station.

[0419] 8. The communication system according to Embodiment 7, wherein:

[0420] The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0421] The UE includes processing circuitry configured to execute client applications associated with the host application.

[0422] 11. A method implemented in a base station, comprising one or more actions described herein as being performed by a first node 111 or a first second node 114.

[0423] 15. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0424] At the host computer, user data is provided; and

[0425] At the host computer, a transmission carrying user data to the UE is initiated via a cellular network including a base station, wherein the base station performs one or more actions as described herein, performed by a first node 111 or a first second node 114.

[0426] 16. The method according to embodiment 15 further includes:

[0427] At the base station, user data is transmitted.

[0428] 17. The method according to embodiment 16, wherein providing user data at a host computer by executing a host application, the method further includes:

[0429] At the UE, the client application associated with the host application is executed.

[0430] 21. A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform one or more actions as described herein, performed by a wireless device 130.

[0431] 25. A communication system including a host computer, the host computer comprising:

[0432] Processing circuitry, configured to provide user data; and

[0433] The communication interface is configured to forward user data to the cellular network for transmission to the user equipment (UE).

[0434] The UE includes a radio interface and processing circuitry, the processing circuitry of which is configured to perform one or more actions as described herein, performed by the wireless device 130.

[0435] 26. The communication system according to embodiment 25 further includes a UE.

[0436] 27. The communication system according to embodiment 26, wherein the cellular network further includes a base station configured to communicate with the UE.

[0437] 28. The communication system according to embodiment 26 or 27, wherein:

[0438] The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0439] The UE's processing circuitry is configured to execute client applications associated with the host application.

[0440] 31. A method implemented in a user equipment (UE), including one or more actions described herein as being performed by a wireless device 130.

[0441] 35. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0442] At the host computer, user data is provided; and

[0443] At the host computer, a transmission carrying user data is initiated to the UE via a cellular network including a base station, wherein the UE performs one or more actions described herein as being performed by the wireless device 130.

[0444] 36. The method according to embodiment 35 further includes:

[0445] At the UE, user data is received from the base station.

[0446] 41. A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform one or more actions as described herein, performed by a wireless device 130.

[0447] 45. A communication system including a host computer, the host computer comprising:

[0448] The communication interface is configured to receive user data originating from transmissions from the user equipment (UE) to the base station.

[0449] The UE includes a radio interface and processing circuitry, the processing circuitry of which is configured to perform one or more actions as described herein, performed by the wireless device 130.

[0450] 46. ​​The communication system according to embodiment 45 further includes a UE.

[0451] 47. The communication system according to embodiment 46 further includes a base station, wherein the base station includes a radio interface configured to communicate with a UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.

[0452] 48. The communication system according to embodiment 46 or 47, wherein:

[0453] The host computer's processing circuitry is configured to execute host applications; and

[0454] The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data.

[0455] 49. The communication system according to embodiment 46 or 47, wherein:

[0456] The host computer's processing circuitry is configured to execute host applications, thereby providing requested data; and

[0457] The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data in response to data requests.

[0458] 51. A method implemented in a user equipment (UE), including one or more actions described herein as being performed by a wireless device 130.

[0459] 52. The method according to embodiment 51 further includes:

[0460] Provide user data; and

[0461] User data is forwarded to the host computer via transmission to the base station.

[0462] 55. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0463] At the host computer, user data sent to the base station is received from the UE, wherein the UE performs one or more actions as described herein, performed by the wireless device 130.

[0464] 56. The method according to embodiment 55 further includes:

[0465] At the UE, user data is provided to the base station.

[0466] 57. The method according to embodiment 56 further includes:

[0467] At the UE, the client application is executed, thereby providing the user data to be sent; and

[0468] At the host computer, the host application associated with the client application is executed.

[0469] 58. The method according to embodiment 56 further includes:

[0470] At the UE (User Equipment) level, execute the client application; and

[0471] At the UE, input data is received from the client application, and the input data is provided at the host computer by executing the host application associated with the client application.

[0472] In this context, the client application responds to the input data by providing the user data to be sent.

[0473] 61. A base station configured to communicate with a user equipment (UE), the base station including a radio interface and processing circuitry configured to perform one or more actions as described herein, performed by a first node 111 or a first second node 114.

[0474] 65. A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from transmissions from a user equipment (UE) to a base station, wherein the base station includes a radio interface and processing circuitry configured to perform one or more actions as described herein, performed by a first node 111 or a first second node 114.

[0475] 66. The communication system according to embodiment 65 further includes a base station.

[0476] 67. The communication system according to embodiment 66 further includes a UE, wherein the UE is configured to communicate with a base station.

[0477] 68. The communication system according to embodiment 67, wherein:

[0478] The host computer's processing circuitry is configured to execute host applications;

[0479] The UE is configured to execute a client application associated with a host application, thereby providing user data to be received by the host computer.

[0480] 71. A method implemented in a base station, comprising one or more actions described herein as being performed by a first node 111 or a first second node 114.

[0481] 75. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0482] At the host computer, user data originating from a transmission already received by the base station from the UE is received from the base station, wherein the UE performs one or more actions as described herein by the wireless device 130.

[0483] 76. The method according to embodiment 75 further includes:

[0484] At the base station, user data is received from the UE.

[0485] 77. The method according to embodiment 76 further includes:

[0486] At the base station, the transmission of received user data to the host computer is initiated.

[0487] References:

[0488] 1.R2-2000009,(ftp: / / ftp.3gpp.org / tsg_ran / WG2_RL2 / TSGR2_108 / Report / R2-2000009.zip)

[0489] 2.3GPP TS 37.340v16.1.0,

[0490] (http: / / www.3gpp.org / ftp / / Specs / archive / 37_series / 37.340 / 37340-g10.zip)

[0491] 3.3GPP TR 37.873v16.0.0,

[0492] (http: / / www.3gpp.org / ftp / / Specs / archive / 37_series / 37.873 / 37873-g00.zip)

[0493] 4. R2-1915763, CR to 38.331, “Introduction of RRC Segmentation–Downlink”, (ftp: / / ftp.3gpp.org / tsg_ran / WG2_RL2 / TSGR2_108 / Docs / R2-1915763.zip)

Claims

1. A method executed by a first node (111), the method being used to process a message destined for a third node (113), the message including content from at least a first second node (114) of one or more second nodes (112), wherein, The first node (111) coordinates with one or more second nodes (112) to process radio communication with the third node (113), the first node (111) operating in a wireless communication network (100), the method comprising: - Send (809) the message to the third node (113), wherein the message is segmented or not segmented, and wherein whether the message is sent in segments or not is based on: i. Does the size of the message exceed the size limit? ii. Does the third node (113) support message segmentation? iii. Whether the first node (111) supports message segmentation, and iv. Whether at least the first second node (114) of the one or more second nodes (112) supports message segmentation, The first node (111) ensures that a consistent segmentation method is applied in dual-connection scenarios and / or switching scenarios.

2. The method according to claim 1, wherein: i. The first node (111) serves the third node (113) via multiple connections with the one or more second nodes (112), and / or ii. The first node (111) wants to switch its connection with the third node (113) to the first second node (114) or wants to switch its connection with the third node (113) from the first second node (114), and / or iii. In the multiple connections, the first node (111) is the master node MN of the third node (113), and the one or more second nodes (112) are the auxiliary nodes SN of the third node (113), and / or iv. In the multiple connections, the first second node (114) is the master node MN of the third node (113), and the first node (111) and one or more other second nodes (112) are the auxiliary nodes SN of the third node (113). and / or v. The first node (111) is the source node of the third node (113), and the first and second nodes (114) are the target nodes of the third node (113). and / or vi. The first node (111) is the target node of the third node (113). The first and second nodes (114) are the source nodes of the third node (113). and / or vii. The first node (111) is a distributed unit DU, the first and second nodes (114) are centralized units CU, and / or viii. The first node (111) is a CU, each of the one or more second nodes (112) is a DU, and / or ix. The first node (111) is the first DU, and any one of the one or more second nodes (112) is another DU.

3. The method according to claim 1, further comprising: - Segment (808) of at least one of the following: a) a first sub-message from the first node (111) to be included in the message to the third node (113); b) at least one corresponding second sub-message received from the one or more second nodes (112) and to be included in the message to the third node (113); and c) a combination of the first sub-message and the at least one corresponding second sub-message. The message is sent based on the first result of the segment.

4. The method according to claim 1, further comprising: - Determine (807) whether to segment the message based on the following: i. Does the size of the message exceed the size limit? ii. Does the third node (113) support message segmentation? iii. Whether the first node (111) supports message segmentation, and iv. Whether at least the first second node (114) of the one or more second nodes (112) supports message segmentation, and The message is sent based on the determined second result.

5. The method according to claim 4, wherein, Determining (807) whether to segment the message based on whether the message size exceeds the size limit includes further determining at least one of the following: -Does the first sub-message from the first node (111) to be included in the message destined for the third node (113) exceed the first size limit? - Whether one or more second sub-messages received from the one or more second nodes (112) and to be included in the message destined for the third node (113) exceed the corresponding second size limit, and - Whether the combination of the first sub-message and the one or more second sub-messages exceeds the combination size limit, and The message is sent based on the further determined third result.

6. The method according to claim 3 or 5, wherein, The combination of the first sub-message and the one or more second sub-messages exceeds the combination size limit, and the method further includes segmenting the combination (808).

7. The method according to claim 1, wherein, The method further includes at least one of the following: - Obtain (801) a first indication indicating whether the third node (113) supports segmentation of the message. - Send (802) one or more second instructions to at least one of the one or more second nodes (112), the one or more second instructions indicating at least one of the following: i. Does the third node (113) support message segmentation? ii. Whether the first node (111) supports message segmentation, iii. The first version of the segment supported by the first node (111), and iv. A first size limit, a combined size limit, or both, supported by the first node (111) for segmenting the message. - Receive (803) one or more corresponding third instructions from the one or more second nodes (112), the one or more corresponding third instructions respectively indicating at least one of the following: i. Whether the one or more second nodes (112) support message segmentation, ii. The corresponding second version of the segment supported by the one or more second nodes (112), and iii. A corresponding second size limit, combined size limit, or both, supported by the one or more second nodes (112) for segmenting the message. - Receive (804) a third instruction from the first and second nodes (114), the third instruction indicating at least one of the following: i. Whether the first and second nodes (114) support message segmentation, ii. A second version of the segment supported by the first and second nodes (114), and iii. A second size limit, a combined size limit, or both, supported by the first and second nodes (114) for segmenting the message. - Determine at least one of the following (805): i. The corresponding second version of the segment supported by the one or more second nodes (112), ii. The corresponding second size limit, the combined size limit, or both, supported by the one or more second nodes (112) for segmenting the message. iii. The second version of the segment supported by the first and second nodes (114), and iv. The second size limit, the combined size limit, or both, supported by the first and second nodes (114) for segmenting the message.

8. The method according to claim 7, wherein, The first node (111) sends a second indication to at least the first and second nodes (114) indicating that the first node (111) does not support segmentation, and wherein the method further includes: - Receive (806) a second sub-message to be included in the message to the third node (113) from at least the first and second nodes (114), wherein the size of the second sub-message is less than the first size limit which does not require segmentation.

9. The method according to any one of claims 1-5 and 7-8, wherein, The first node (111) and the one or more second nodes (112) serve the third node (113) using multiple connections, wherein at least one of the first node (111) and the first second node (114) is MN and the other is SN, and wherein only the MN and the third node (113) support segmentation.

10. The method according to any one of claims 1-5 and 7-8, wherein, The first node (111) and the one or more second nodes (112) serve the third node (113) using multiple connections, wherein at least one of the first node (111) and the first second node (114) is an MN and the other is an SN, wherein the MN, the SN and the third node (113) all support segmentation, and wherein the sent message is based on whether at least one second sub-message from the one or more second nodes (112) to be included in the message to the third node (113) is segmented.

11. The method according to any one of claims 3 and 7, wherein, The first node (111) is SN, wherein the first second node (114) is MN, and wherein the segmentation (808) is performed according to a third size limit of the MN.

12. The method according to any one of claims 1-5 and 7-8, wherein, The message is a Radio Resource Control (RRC) message.

13. A method executed by a first second node (114), the method being used to process a message destined for a third node (113), the message including content from at least the first second node (114) of one or more second nodes (112), wherein, The first and second nodes (114) coordinate with at least the first node (111) to process radio communications with the third node (113), the first and second nodes (114) operating in a wireless communication network (100), the method comprising: - Determine (906) whether to segment the message based on the following: i. Does the size of the message exceed the size limit? ii. Does the third node (113) support message segmentation? iii. Whether the first node (111) supports message segmentation, and iv. Whether at least the first second node (114) of the one or more second nodes (112) supports message segmentation, and - Based on the determined fourth result, initiate processing (907) of the message. The first and second nodes (114) ensure that a consistent segmentation method is applied in dual-connection scenarios and / or switching scenarios.

14. The method of claim 13, wherein: i. Among them, The first second node (114) serves the third node (113) via multiple connections with the first node (111), the one or more second nodes (112), or both. ii. The first second node (114) wants to switch its connection with the third node (113) to the first node (111) or wants to switch its connection with the third node (113) from the first node (111), and / or iii. In the multiple connections, the first node (111) is the master node MN of the third node (113), and the one or more second nodes (112) are the auxiliary nodes SN of the third node (113), and / or iv. In the multiple connections, the first second node (114) is the master node MN of the third node (113), the first node (111) and one or more other second nodes (112) are auxiliary nodes SN of the third node (113), and / or v. The first node (111) is the source node of the third node (113), and the first and second nodes (114) are the target nodes of the third node (113). and / or vi. The first node (111) is the target node of the third node (113). The first and second nodes (114) are the source nodes of the third node (113). and / or vii. The first node (111) is a distributed unit DU, the first and second nodes (114) are centralized units CU, and / or viii. The first node (111) is a CU, each of the one or more second nodes (112) is a DU, and / or ix. The first node (111) is the first DU, and any one of the one or more second nodes (112) is another DU.

15. The method according to claim 13, wherein, The message in the startup process (907) includes: - Segment (908) at least one of the following: a) a second sub-message from the first second node (114) to be included in the message to the third node (113), b) a first sub-message from the first node (111) to be included in the message to the third node (113), c) at least one corresponding second sub-message received from the one or more second nodes (112) and to be included in the message to the third node (113), and d) a combination of the following: The first sub-message, and the second sub-message and at least one of the at least one corresponding second sub-message, and The segmentation (908) is based on the determined fourth result.

16. The method according to claim 13, wherein, The message in the startup process (907) includes: - Send the message (910) to the third node (113), wherein the message is segmented or not segmented.

17. The method according to claim 13, wherein, Determining (906) whether to segment the message based on whether the message size exceeds the size limit includes further determining at least one of the following: -Does the first sub-message from the first node (111) to be included in the message destined for the third node (113) exceed the first size limit? -Whether the second sub-message from the first and second nodes (114) to be included in the message going to the third node (113) exceeds the second size limit. - Whether one or more corresponding second sub-messages received from the one or more second nodes (112) and to be included in the message destined for the third node (113) exceed the corresponding second size limit, and - Whether the combination of the first sub-message and the second sub-message and / or one or more corresponding second sub-messages exceeds the combination size limit, and The message is sent based on the further determined fifth result.

18. The method according to claim 15 or 17, wherein, The combination exceeds the combination size limit, and the method further includes segmenting the combination (908).

19. The method according to claim 13, wherein, The method further includes at least one of the following: - Obtain (901) a first indication indicating whether the third node (113) supports segmentation of the message. - Receive (902) one or more second instructions from the first node (111), the one or more second instructions indicating at least one of the following: i. Does the third node (113) support message segmentation? ii. Whether the first node (111) supports message segmentation, iii. The first version of the segment supported by the first node (111), and iv. A first size limit, a combined size limit, or both, supported by the first node (111) for segmenting the message. - Receive (903) one or more corresponding third instructions from the one or more second nodes (112), the one or more corresponding third instructions respectively indicating at least one of the following: i. Whether the one or more second nodes (112) support message segmentation, ii. The corresponding second version of the segment supported by the one or more second nodes (112), and iii. A corresponding second size limit, combined size limit, or both, supported by the one or more second nodes (112) for segmenting the message. - Send a third instruction (904) to at least one of the following: the first node (111), And the other nodes in the one or more second nodes (112), the third indication indicates at least one of the following: i. Whether the first and second nodes (114) support message segmentation, ii. A second version of the segment supported by the first and second nodes (114), and iii. A second size limit, a combined size limit, or both, supported by the first and second nodes (114) for segmenting the message. - Determine at least one of the following (905): i. The corresponding second version of the segment supported by the one or more second nodes (112), respectively ii. The corresponding second size limit, the combined size limit, or both, supported by the one or more second nodes (112) for segmenting the message. iii. The first version of the segment supported by the first node (111), and iv. The first size limit, the combined size limit, or both, supported by the first node (111) for segmenting the message.

20. The method according to claim 19, wherein, The first and second nodes (114) receive a second indication that the first node (111) does not support segmentation, and wherein the message initiating the process (907) includes: - Send (909) a second sub-message to the first node (111) to be included in the message to the third node (113), wherein the size of the second sub-message is less than the first size limit which does not require segmentation.

21. The method according to any one of claims 13-17 and 19-20, wherein, The first second node (114) serves the third node (113) with multiple connections to the one or more second nodes (112) and the first node (111), wherein at least one of the first node (111) and the first second node (114) is MN and the other is SN, and wherein only the MN and the third node (113) support segmentation.

22. The method according to any one of claims 13-17 and 19-20, wherein, The first second node (114) serves the third node (113) with multiple connections to the one or more second nodes (112) and the first node (111), wherein at least one of the first node (111) and the first second node (114) is an MN and the other is an SN, wherein the MN, the SN and the third node (113) all support segmentation, and wherein the determination (906) is based on whether at least one second sub-message from the one or more second nodes (112) to be included in the message to the third node (113) is segmented.

23. The method according to any one of claims 15 and 19, wherein, The first node (111) is SN, wherein the first second node (114) is MN, and wherein the segmentation (908) is performed according to a third size limit of the MN.

24. The method according to any one of claims 13-17 and 19-20, wherein, The message is a Radio Resource Control (RRC) message.

25. A first node (111) for processing messages destined for a third node (113), said messages being configured to include content from at least a first second node (114) of one or more second nodes (112), wherein, The first node (111) is configured to coordinate with the one or more second nodes (112) to process radio communications with the third node (113), the first node (111) is configured to operate in a wireless communication network (100), and the first node (111) is further configured to: - Send the message to the third node (113), wherein the message is configured to be segmented or not segmented, and wherein whether the message is sent in segments or not is configured to be based on: i. Does the size of the message exceed the size limit? ii. Does the third node (113) support message segmentation? iii. Whether the first node (111) supports message segmentation, and iv. Whether at least the first second node (114) of the one or more second nodes (112) is configured to support message segmentation, The first node (111) ensures that a consistent segmentation method is applied in dual-connection scenarios and / or switching scenarios.

26. The first node (111) according to claim 25, wherein: i. The first node (111) is configured to serve the third node (113) with multiple connections to the one or more second nodes (112), and / or ii. The first node (111) wants to switch its connection with the third node (113) to the first second node (114) or wants to switch its connection with the third node (113) from the first second node (114), and / or iii. In the multiple connections, the first node (111) is configured as the master node MN of the third node (113), and the one or more second nodes (112) are configured as auxiliary nodes SN of the third node (113), and / or iv. In the multiple connections, the first second node (114) is configured as the master node MN of the third node (113), the first node (111) and one or more other second nodes (112) are configured as auxiliary nodes SN of the third node (113), and / or v. The first node (111) is configured as the source node of the third node (113). The first and second nodes (114) are configured as the target nodes of the third node (113), and / or vi. The first node (111) is configured as the target node of the third node (113), and the first second node (114) is configured as the source node of the third node (113), and / or vii. The first node (111) is configured as a distributed unit (DU), and the first and second nodes (114) are configured as centralized units (CU), and / or viii. The first node (111) is configured as CU, each of the one or more second nodes (112) is configured as DU, and / or ix. The first node (111) is configured as a first DU, and any one of the one or more second nodes (112) is configured as another DU.

27. The first node (111) according to claim 25 is further configured as follows: - Segmenting at least one of the following: a) a first sub-message from the first node (111) to be included in the message destined for the third node (113); b) at least one corresponding second sub-message configured to be received from the one or more second nodes (112) and to be included in the message destined for the third node (113); and c) a combination of the first sub-message and the at least one corresponding second sub-message. in, The message is configured to be sent based on the first result of the segment.

28. The first node (111) according to claim 25 is further configured as follows: - Determine whether to segment the message based on the following: i. Does the size of the message exceed the size limit? ii. Does the third node (113) support message segmentation? iii. Whether the first node (111) supports message segmentation, and iv. Whether at least the first second node (114) of the one or more second nodes (112) supports message segmentation, and in, The message is configured to be sent based on the determined second result.

29. The first node (111) according to claim 28, wherein, Determining whether to segment the message based on whether the message size exceeds the size limit is configured to include further determining at least one of the following: -Does the first sub-message from the first node (111) to be included in the message destined for the third node (113) exceed the first size limit? - Whether one or more second sub-messages, configured to be received from the one or more second nodes (112) and to be included in the message destined for the third node (113), exceed a corresponding second size limit, and - Whether the combination of the first sub-message and the one or more second sub-messages exceeds the combination size limit, and The message is configured to be sent based on the further determined third result.

30. The first node (111) according to claim 27 or 29, wherein, The combination of the first sub-message and the one or more second sub-messages exceeds the combination size limit, and wherein the first node (111) is also configured to segment the combination.

31. The first node (111) according to claim 25, wherein, The first node (111) is also configured to be at least one of the following: - Obtain a first indication configured to indicate whether the third node (113) supports segmentation of the message. - Send one or more second indications to at least one of the one or more second nodes (112), the one or more second indications being configured to indicate at least one of the following: i. Does the third node (113) support message segmentation? ii. Whether the first node (111) supports message segmentation, iii. The first version of the segment configured to be supported by the first node (111), and iv. A first size limit, a combined size limit, or both, configured to be supported by the first node (111) for segmenting the message. - Receive one or more corresponding third indications from the one or more second nodes (112), the one or more corresponding third indications being configured to indicate at least one of the following: i. Whether the one or more second nodes (112) support message segmentation, ii. The corresponding second version of the segment supported by the one or more second nodes (112), and iii. A corresponding second size limit, combined size limit, or both, supported by the one or more second nodes (112) for segmenting the message, - receiving a third indication from the first second node (114), the third indication being configured to indicate at least one of the following: i. Whether the first and second nodes (114) support message segmentation, ii. A second version of the segment supported by the first and second nodes (114), and iii. A second size limit, a combined size limit, or both, supported by the first and second nodes (114) for segmenting the message. - Determine at least one of the following: i. The corresponding second version of the segment supported by the one or more second nodes (112), ii. The corresponding second size limit, the combined size limit, or both, supported by the one or more second nodes (112) for segmenting the message. iii. The second version of the segment supported by the first and second nodes (114), and iv. The second size limit, the combined size limit, or both, supported by the first and second nodes (114) for segmenting the message.

32. The first node (111) according to claim 31, wherein, The first node (111) is configured to send a second indication to at least the first and second nodes (114) indicating that the first node (111) does not support segmentation, and wherein the first node (111) is further configured to: - Receive a second sub-message from at least the first and second nodes (114) to be included in the message to the third node (113), wherein the second sub-message is configured to be smaller than the first size limit configured not to require segmentation.

33. The first node (111) according to any one of claims 25-29 and 31-32, wherein, The first node (111) is configured to serve the third node (113) with multiple connections to the one or more second nodes (112), wherein at least one of the first node (111) and the first second node (114) is configured as MN and the other is configured as SN, and wherein only the MN and the third node (113) are configured to support segmentation.

34. The first node (111) according to any one of claims 25-29 and 31-32, wherein, The first node (111) is configured to serve the third node (113) with multiple connections to the one or more second nodes (112), wherein at least one of the first node (111) and the first second node (114) is configured as MN and the other is configured as SN, wherein the MN, the SN and the third node (113) are all configured to support segmentation, and wherein the sent message is configured to be segmented based on whether at least one second sub-message from the one or more second nodes (112) to be included in the message to the third node (113) is segmented.

35. The first node (111) according to any one of claims 27 or 31, wherein, The first node (111) is configured as SN, wherein the first second node (114) is configured as MN, and wherein the segmentation is configured to be performed according to a third size limit of the MN.

36. The first node (111) according to any one of claims 25-29 and 31-32, wherein, The message is configured as a Radio Resource Control (RRC) message.

37. A first and second node (114) for processing messages destined for a third node (113), the messages being configured to include content from at least the first and second node (114) of one or more second nodes (112), wherein, The first and second nodes (114) are configured to coordinate with at least the first node (111) to process radio communications with the third node (113), the first and second nodes (114) are configured to operate in a wireless communication network (100), and the first and second nodes (114) are further configured to: - Determine whether to segment the message based on the following: i. Does the size of the message exceed the size limit? ii. Does the third node (113) support message segmentation? iii. Whether the first node (111) supports message segmentation, and iv. Whether at least the first second node (114) of the one or more second nodes (112) supports message segmentation, and - Based on the determined fourth result, initiate the processing of the message. The first and second nodes (114) ensure that a consistent segmentation method is applied in dual-connection scenarios and / or switching scenarios.

38. The first and second nodes (114) according to claim 37, wherein: i. Among them, The first second node (114) is configured to serve the third node (113) via multiple connections with the first node (111), the one or more second nodes (112), or both. ii. The first second node (114) wants to switch its connection with the third node (113) to the first node (111) or wants to switch its connection with the third node (113) from the first node (111), and / or iii. In the multiple connections, the first node (111) is configured as the master node MN of the third node (113), and the one or more second nodes (112) are configured as auxiliary nodes SN of the third node (113), and / or iv. In the multiple connections, the first second node (114) is configured as the master node MN of the third node (113), the first node (111) and one or more other second nodes (112) are configured as auxiliary nodes SN of the third node (113), and / or v. The first node (111) is configured as the source node of the third node (113). The first and second nodes (114) are configured as the target nodes of the third node (113), and / or vi. The first node (111) is configured as the target node of the third node (113), and the first second node (114) is configured as the source node of the third node (113), and / or vii. The first node (111) is configured as a distributed unit (DU), and the first and second nodes (114) are configured as centralized units (CU), and / or viii. The first node (111) is configured as CU, each of the one or more second nodes (112) is configured as DU, and / or ix. The first node (111) is configured as a first DU, and any one of the one or more second nodes (112) is configured as another DU.

39. The first and second nodes (114) according to claim 37, wherein, Initiating the processing of the message is configured to include: - Segment at least one of the following: a) a second sub-message from the first and second nodes (114) to be included in the message destined for the third node (113), b) a first sub-message from the first node (111) to be included in the message destined for the third node (113), c) at least one corresponding second sub-message received from the one or more second nodes (112) and to be included in the message destined for the third node (113), and d) a combination of the following: the first sub-message, and at least one of the second sub-message and the at least one corresponding second sub-message, and The segmentation is configured to be based on the determined fourth result.

40. The first and second nodes (114) according to claim 37, wherein, Initiating the processing of the message is configured to include: - Send the message to the third node (113), wherein the message is segmented or not segmented.

41. The first and second nodes (114) according to claim 37, wherein, Determining whether to segment the message based on whether its size exceeds the size limit is further configured to include determining at least one of the following: -Does the first sub-message from the first node (111) to be included in the message destined for the third node (113) exceed the first size limit? -Whether the second sub-message from the first and second nodes (114) to be included in the message going to the third node (113) exceeds the second size limit. - Whether one or more corresponding second sub-messages, respectively configured to be received from the one or more second nodes (112) and to be included in the message destined for the third node (113), exceed the corresponding second size limit, and - Whether the combination of the first sub-message and the second sub-message and / or one or more corresponding second sub-messages exceeds the combination size limit, and The message is configured to be sent based on the further determined fifth result.

42. The first or second node (114) according to claim 39 or 41, wherein, The combination exceeds the combination size limit, and the first and second nodes (114) are further configured to segment the combination.

43. The first and second nodes (114) according to claim 37, wherein, The first and second nodes (114) are also configured to be at least one of the following: - Obtain a first indication configured to indicate whether the third node (113) supports segmentation of the message. - Receive one or more second indications from the first node (111), the one or more second indications being configured to indicate at least one of the following: i. Does the third node (113) support message segmentation? ii. Whether the first node (111) supports message segmentation, iii. The first version of the segment supported by the first node (111), and iv. A first size limit, a combined size limit, or both, supported by the first node (111) for segmenting the message. - Receive one or more corresponding third indications from the one or more second nodes (112), the one or more corresponding third indications being configured to indicate at least one of the following: i. Whether the one or more second nodes (112) support message segmentation, ii. The corresponding second version of the segment supported by the one or more second nodes (112), and iii. A corresponding second size limit, combined size limit, or both supported by the one or more second nodes (112) for segmenting the message, - send a third indication to at least one of the following: the first node (111), and the other nodes in the one or more second nodes (112), the third indication being configured to indicate at least one of the following: i. Whether the first and second nodes (114) support message segmentation, ii. A second version of the segment supported by the first and second nodes (114), and iii. A second size limit, a combined size limit, or both, supported by the first and second nodes (114) for segmenting the message. - Determine at least one of the following: i. The corresponding second version of the segment configured to be supported by the one or more second nodes (112), respectively. ii. The corresponding second size limit, the combined size limit, or both, configured to be supported by the one or more second nodes (112) for segmenting the message. iii. The first version of the segment configured to be supported by the first node (111), and iv. The first size limit, the combined size limit, or both, configured to be supported by the first node (111) for segmenting the message.

44. The first and second nodes (114) according to claim 43, wherein, The first and second nodes (114) are configured to receive a second indication that the first node (111) does not support segmentation, and wherein initiating processing of the message is further configured to include: - Send a second sub-message to the first node (111) to be included in the message to the third node (113), wherein the size of the second sub-message is lower than the first size limit configured not to require segmentation.

45. The first second node (114) according to any one of claims 37-41 and 43-44, wherein, The first second node (114) is configured to serve the third node (113) with multiple connections to the one or more second nodes (112) and the first node (111), wherein at least one of the first node (111) and the first second node (114) is configured as MN and the other is configured as SN, and wherein only the MN and the third node (113) are configured to support segmentation.

46. ​​The first second node (114) according to any one of claims 37-41 and 43-44, wherein, The first second node (114) is configured to serve the third node (113) with multiple connections to the one or more second nodes (112) and the first node (111), wherein at least one of the first node (111) and the first second node (114) is configured as MN and the other is configured as SN, wherein the MN, the SN and the third node (113) are all configured to support segmentation, and wherein the determination is configured to be based on whether at least one second sub-message in one or more corresponding second sub-messages from the one or more second nodes (112) to be included in the message to the third node (113) is segmented.

47. The first and second node (114) according to any one of claims 39 and 43, wherein, The first node (111) is configured as SN, wherein the first second node (114) is configured as MN, and wherein the segmentation is configured to be performed according to a third size limit of the MN.

48. The first second node (114) according to any one of claims 37-41 and 43-44, wherein, The message is configured as a Radio Resource Control (RRC) message.

Images