APARELHO E MÉTODOS PARA EVITAR INTERFERÊNCIA PARA COEXISTÊNCIA EM DISPOSITIVO

Abstract

In some examples, master node, MN, in a telecommunication network, wherein the telecommunication network further comprises a secondary node, SN and a user equipment, UE, and wherein the user equipment, UE, is operable in dual connectivity, DC, with the master node, MN, and with the secondary node, SN, such that the user equipment, UE, can transmit and receive data on multiple carriers of the master node, MN, and the secondary node, SN, is configured to receive, from the user equipment, UE, data representing an indication of a set of carrier frequencies and / or a set of carrier frequency ranges or a combination of candidate serving frequencies or frequency ranges of the master node, MN, and / or of the secondary node, SN, affected by in-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, wherein the master node, MN is further configured to use a configuration, determined on the basis of the data received from the user equipment, UE, by the master node, MN, and / or the secondary node, SN, of the telecommunications network, for time division multiplexing, TDM, or frequency division multiplexing, FDM, whereby to mitigate the effects of the in-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE.

Description

[0001] This disclosure relates generally to data transmission over a communications network, and in particular to the prevention of interference between signals from one or more different radio techniques used in user equipment, such as smartphones. BACKGROUND

[0002] The increasing demand for multiple applications or services in user equipment (UE) has resulted in the coexistence of multiple co-located radio technologies in UE devices. That is, UE can be equipped with multiple radio transceivers to enable communication using various radio protocols such as Long Term Evolution (LTE), New Radio (NR), Global Positioning System (GPS), WiFi, and Bluetooth. As a result, and due to the introduction of more frequency bands for NR and LTE, in-device coexistence (IDC) has become a serious problem due to the proximity of multiple radio transceivers in the same device. IDC, as a result of multiple co-located radio technologies, can cause interference, known as in-device interference, between transceivers due to physical proximity, spectral proximity, and / or imperfect radio frequency (RF) filtering.

[0003] In situations where an UE is operating in a dual connectivity mode, in which it may be in simultaneous communication using multiple radio access technologies (RATs), known as multi-RAT dual connectivity (MR-DC), the UE may be connected to two network nodes simultaneously, one of which may be provided as part of a 3GPP (3GPP) 5G network (e.g., NR) and one of which may be provided as part of a 3GPP 4G network (e.g., Petition 870250098665, dated 10 / 28 / 2025, page 8 / 78 2 / 55 EUTRA) or between two NR nodes. As such, 3GPP signals can be affected by non-3GPP signals and vice versa.

[0004] To mitigate device interference, previously defined solutions, for example using frequency division multiplexing (FDM), generally aim to switch all LTE or NR frequencies away from, for example, the industrial, scientific and medical (ISM) radio frequency (RF) band (such as WiFi). FDM solutions are applicable to all scenarios, provided an alternative carrier frequency is available. In some network deployments, however, using FDM-based solutions to address IDC interference issues is neither feasible nor desirable. Furthermore, a time division multiplexing (TDM) solution is not currently available in the context of MR-DC, where one of the RATs comprises, for example, 5G NR. SUMMARY

[0005] One objective of this disclosure is to provide devices and methods for mitigating device interference in MR-DC scenarios, such as where a UE is connected to two network nodes simultaneously, both belonging to NR or one belonging to NR and the other belonging to E-UTRA.

[0006] The above objectives and others are achieved by the characteristics of independent claims.

[0007] Other forms of implementation are evident in the dependent claims, in the descriptive report and in the Figures.

[0008] A first aspect of the present disclosure provides a master node, MN, in a telecommunications network, wherein the telecommunications network further comprises a secondary node, SN, and a user equipment, UE, and wherein the user equipment, UE, is operable in dual connectivity, DC, with the master node, MN, and with the secondary node, SN, so that the user equipment, UE, can transmit and receive data in multiple Petition 870250098665, dated 10 / 28 / 2025, p. 9 / 78 3 / 55 carrier frequencies of the master node, MN, and the secondary node, SN, the master node, MN, being configured to receive, from the user equipment, UE, data representing an indication of a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies or frequency bands of the master node, MN, and / or the secondary node, SN, affected by coexistence in device, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, wherein the master node, MN, is additionally configured to use a configuration, determined based on the data received from the user equipment, UE, by the master node, MN, and / or the secondary node, SN, of the telecommunications network, for time-division multiplexing, TDM, or frequency-division multiplexing, FDM, to mitigate the effects of coexistence in device, IDC,for uplink and / or downlink communications between the master node (MN) and / or the secondary node (SN) and the user equipment (UE).

[0009] Therefore, there is coordination between nodes in an MR-DC scenario that allows device interference to be mitigated or removed. For example, coordination between a master node and a secondary node can allow the generation of a configuration that can be used by one or more of the master node, the secondary node, and a user device to implement FDM or TDM with the goal of (at least) reducing device interference in the UE. In this way, an IDC problem in MR-DC scenarios can be solved in terms of which nodes provide a configuration and how the FDM and TDM solution can be applied with coordination between nodes, which will efficiently solve the IDC problems for the UE operating in an MR-DC configuration.

[0010] In an implementation of the first aspect, the set of component carrier frequencies and / or the set of bands Petition 870250098665, dated 10 / 28 / 2025, p. 10 / 78 4 / 55 of the carrier frequency component of the master node, MN, and / or the secondary node, SN, affected by coexistence in device, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, can be configured by the master node, MN.The master node can transmit to the secondary node, SN, data representing the indication of the set of component carrier frequencies and / or the set of component carrier frequency bands or a combination of candidate service frequencies or frequency bands of the master node, MN, and / or the secondary node, SN, affected by coexistence in device, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, wherein the set of component carrier frequencies and / or the set of component carrier frequency bands or a combination of candidate service frequencies or frequency bands of the master node, MN, and / or the secondary node, SN, affected by coexistence in device, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE is configured by the secondary node, SN.

[0011] In one example, the master node may disable a Secondary Cell, SCell, of the telecommunications network; and / or, switch to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restrict a physical resource block, PRB, allocation in an unaffected frequency band, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. The master node may receive data from the secondary node, SN, that Petition 870250098665, dated 10 / 28 / 2025, page 11 / 78 5 / 55 represents an indication to enable time-division multiplexing, TDM, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, and to transmit, to the secondary node, SN, time-division multiplexing, TDM assistance information, comprising at least one time-division multiplexing, TDM, pattern for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE.

[0012] The master node may receive, from the secondary node, SN, data representing a time-division multiplexing (TDM) pattern from the secondary node, SN, the time-division multiplexing (TDM) pattern of the secondary node, SN, configured by the secondary node, SN, based on at least one time-division multiplexing (TDM) pattern received as part of the time-division multiplexing (TDM) assistance information for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, and transmit, to the user equipment, UE, the data representing the time-division multiplexing (TDM) pattern of the secondary node, SN. The master node may transmit, to the secondary node, SN, a time-division multiplexing (TDM) pattern for a master cell group, MCG.The master node receives, from the secondary node, SN, data representing a time-division multiplexing (TDM) pattern from the secondary node, SN, the time-division multiplexing (TDM) pattern of the secondary node, SN, configured by the secondary node, SN, based on at least one time-division multiplexing (TDM) pattern received as part of the time-division multiplexing (TDM) assistance information for uplink and / or downlink communications between the master node, MN, and / or the node. Petition 870250098665, dated 10 / 28 / 2025, page 12 / 78 6 / 55 secondary node, SN, and user equipment, UE, and the time-division multiplexing standard, TDM, to the master cell group, MCG, and transmit, to the user equipment, UE, the data representing the time-division multiplexing standard, TDM, from the secondary node, SN.

[0013] In one example, the master node receives, from the secondary node, SN, data representing a time-division multiplexing, TDM, pattern of the secondary node, SN, the time-division multiplexing, TDM, pattern of the secondary node, SN, configured by the secondary node, SN, based on at least one time-division multiplexing, TDM, pattern received as part of the time-division multiplexing, TDM, assistance information for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, and configures a time-division multiplexing, TDM, pattern for a master cell group, MCG, based on the time-division multiplexing, TDM, pattern of the secondary node, SN.

[0014] A second aspect of this disclosure provides a user equipment, UE, configured to operate in dual connectivity, DC, with a master node, MN, and a secondary node, SN, of a telecommunications network such that the user equipment, UE, can transmit and receive data using multiple carrier components of the master node, MN, and the secondary node, SN, wherein the user equipment, UE, is configured to receive, from the master node, MN, a first set of data representing a first set of candidate carrier frequencies and / or a first list of candidate service frequency bands for uplink and / or downlink communications between the user equipment, UE, and the master node, MN, and to receive, from the secondary node, SN, a second set of data representing a second set of candidate carrier frequencies and / or a Petition 870250098665, dated 10 / 28 / 2025, page 13 / 78 7 / 55 second list of candidate service frequency bands for uplink and / or downlink communications between the user equipment, UE, and the secondary node, SN, and detect coexistence on device, IDC, based on the first data set and / or the second data set, and transmit data to the master node, MN, or to the secondary node, SN, representing an indication of coexistence on device, IDC.

[0015] In an implementation of the second aspect, the UE may receive, from the master node, MN, data that represents an indication for the user equipment, UE, to report to the master node, MN, a combination of candidate service frequencies or frequency bands for uplink and / or downlink communications between the user equipment, UE, and the master node, MN, and the secondary node, SN, resulting in device coexistence, IDC. The UE may receive, from the master node, MN, data that represents an indication for the user equipment, UE, to report to the secondary node, SN, a combination of candidate service frequencies or frequency bands for uplink and / or downlink communications between the user equipment, UE, and the master node, MN, and the secondary node, SN, resulting in device coexistence, IDC.

[0016] A third aspect of the present disclosure provides a secondary node, SN, in a telecommunications network, wherein the telecommunications network further comprises a master node, MN, and a user device, UE, and wherein the user device, UE, is operable in dual connectivity, DC, with the master node, MN, and with the secondary node, SN, such that the user device, UE, can transmit and receive data on multiple carriers from the master node, MN, and the secondary node, SN, the secondary node, SN, being configured to receive, from the master node, MN, data representing a list comprising a set of carrier frequencies and / or frequency bands affected by coexistence in the device or a combination of Petition 870250098665, dated 10 / 28 / 2025, page 14 / 78 8 / 55 candidate service frequencies or frequency bands, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE, wherein the carrier frequencies and / or frequency bands affected by coexistence in device, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE is configured by the secondary node, SN, and transmits, to the master node, MN, a confirmation message to confirm receipt of the data representing a list comprising a set of carrier frequencies and / or frequency bands affected by coexistence in device, IDC.

[0017] In an implementation of the third aspect, the secondary node may disable a secondary cell, SCell, of the telecommunications network; and / or, switch to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the secondary node, SN, and the user equipment, UE; and / or restrict a physical resource block allocation, PRB, in an unaffected frequency band, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. The secondary node may transmit, to the master node, MN, a time-division multiplexing pattern, TDM, to a group of secondary cells, SCG.

[0018] These and other aspects of the invention will become apparent from the embodiment(s) described below. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] To make this disclosure easier to understand, examples of modalities will now be described, with reference to the attached drawings, in which: Petition 870250098665, dated 10 / 28 / 2025, page 15 / 78 9 / 55 Figure 1 is a schematic representation of the coexistence in user equipment comprising transceivers for multiple radio frequency techniques, including WiFi, Bluetooth, New Radio and Global Positioning System; Figure 2 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN generates an FDM configuration when individual candidate frequencies are affected by IDC; Figure 3 shows a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN generates an FDM configuration when a frequency combination is affected by IDC; Figure 4 shows a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN generates a TDM configuration when individual frequencies are affected by IDC; Figure 5 shows a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN generates a TDM configuration when a frequency combination is affected by IDC; Figure 6 shows a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the SN generates a TDM configuration when a frequency combination is affected by IDC; Figure 7 shows a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN uses a resource coordination procedure when a frequency combination is affected by IDC; Figure 8 shows a communication flow according to an example between a UE, a MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a set of individual frequencies is affected by IDC; Petition 870250098665, dated 10 / 28 / 2025, page 16 / 78 10 / 55 Figure 9 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN and the SN can configure the UE for FDM when a frequency combination is affected by IDC; Figure 10 shows a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a frequency combination is affected by IDC; Figure 11 shows a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a frequency combination is affected by IDC; Figure 12 is a combined communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN and the SN can configure the UE for FDM when a set of individual frequencies or a combination of frequencies are affected by IDC; Figure 13 is a combined communication flow according to an example between a UE, a MN and an SN in an MR-DC scheme where the MN and the SN can configure the UE for FDM when a set of individual frequencies or a combination of frequencies are affected by IDC and the UE reports individual frequency components of the combinations to the MN or SN; and Figure 14 is a schematic representation of a machine according to an example; Figure 15 is a combined communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM and TDM when a set of individual frequencies or a combination of frequencies are affected by IDC and MN and SN apply the TDM solution to solve the IDC problem; Figure 16 shows a generalized communication flow based on an example between a UE, an MN, and an SN in an MR-DC scheme. Petition 870250098665, dated 10 / 28 / 2025, page 17 / 78 11 / 55 where MN and SN can configure UE for FDM and TDM when a set of individual frequencies or a combination of frequencies are affected by IDC and MN and SN apply the enhanced FDM or TDM solution to resolve the IDC problem. DETAILED DESCRIPTION

[0020] Examples of embodiments are described below in sufficient detail to enable subject matter experts to incorporate and implement the systems and processes described herein. It is important to understand that embodiments can be provided in many alternative forms and should not be interpreted as limited to the examples set forth herein.

[0021] Consequently, although embodiments may be modified in various ways and assume various alternative forms, their specific embodiments are shown in the drawings and described in detail below as examples. There is no intention to limit the specific forms disclosed. On the contrary, all modifications, equivalents and alternatives that fall within the scope of the appended claims are to be included. The elements of the embodiment examples are consistently indicated by the same reference numerals in all drawings and detailed descriptions where appropriate.

[0022] The terminology used here to describe modalities is not intended to limit the scope. The articles "a," "an," and "the" are singular because they have a single referent, however, the use of the singular in this document should not preclude the presence of more than one referent. In other words, the elements mentioned in the singular may be one or more, unless the context clearly indicates otherwise. It should be further understood that the terms "comprises," "comprising," "includes," and / or "including," when used here, specify the presence of declared features, items, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, items, steps, operations, Petition 870250098665, dated 10 / 28 / 2025, p. 18 / 78 12 / 55 elements, components and / or groups thereof. The term and / or is simply an association relation to describe associated objects and represents that three relations can exist such that A and / or B can indicate that A exists alone, A and B exist at the same time, or B exists alone. The character / usually represents that the associated objects are in an OR relationship.

[0023] Unless otherwise defined, all terms (including technical and scientific terms) used herein shall be interpreted as customary in the art. It shall be further understood that terms in common usage shall also be interpreted as customary in the state of the art and not in an idealized or overly formal sense, unless expressly so defined herein.

[0024] The following contains specific information relating to implementations of this disclosure. The drawings and the accompanying detailed disclosure are directed only to implementations. However, this disclosure is not limited to these implementations. Other variations and implementations of this disclosure will be obvious to those skilled in the art.

[0025] The phrases in one implementation or in some implementations may refer to one or more identical or different implementations. The term coupled is defined as connected directly or indirectly through intervening components and is not necessarily limited to physical connections. The expression at least one of A, B and C or at least one of the following: A, B and C means only A, or only B, or only C, or any combination of A, B and C.

[0026] The terms system and network can be used interchangeably.

[0027] For explanatory purposes and not limitation, specific details such as functional entities, techniques, protocols and Petition 870250098665, dated 10 / 28 / 2025, page 19 / 78 13 / 55 patterns are presented to provide an understanding of this disclosure. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures is omitted so as not to obscure this disclosure with unnecessary details.

[0028] Skilled individuals will immediately recognize that any disclosed network function or algorithm can be implemented by hardware, software, or a combination of software and hardware. The disclosed functions may correspond to modules that may be software, hardware, firmware, or any combination thereof.

[0029] A software implementation may include machine-readable and / or computer-readable and / or executable instructions stored on a machine-readable and / or computer-readable medium, such as memory or other types of storage devices. One or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and perform the disclosed network function(s) or algorithm(s).

[0030] Microprocessors or general-purpose computers may include application-specific integrated circuits (ASICs), programmable logic arrays, and / or use one or more digital signal processors (DSPs). Although some of the disclosed implementations are oriented towards software installed and running on computer hardware, alternative implementations implemented as firmware or as hardware or as a combination of hardware and software are within the scope of this disclosure. Computer-readable media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), cassettes Petition 870250098665, dated 10 / 28 / 2025, page 20 / 78 14 / 55 magnetic, magnetic tape, magnetic disk storage, or any other equivalent means capable of storing computer-readable instructions.

[0031] A radio communication network architecture, such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN), typically includes at least one base station (BS), at least one user equipment (UE), and one or more optional network elements that provide connectivity within a network. The UE communicates with the network, such as a Core Network (CN), an Evolved Packet Core Network (EPC), an Evolved Universal Terrestrial RAN (E-UTRAN), a 5G Core (5GC), or the internet via a RAN established by one or more BSs.

[0032] A UE may include, but is not limited to, a mobile station, a terminal, or a mobile device or user communication radio terminal. The UE may be portable radio equipment which includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA) with wireless communication capability. The UE is configured to receive and transmit signals using one or more signaling radio carriers via an air interface to one or more cells in a RAN using one or more multiple component carriers.

[0033] A BS may provide communication services in accordance with at least one Radio Access Technology (RAT), such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM), which is often called 2G, GSM Enhanced Data Rates for GSM Evolution RAN (EDGE) (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), which is often called 3G based on Petition 870250098665, dated 10 / 28 / 2025, page 21 / 78 15 / 55 Basic Broadband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, evolved LTE (eLTE), which is LTE connected to 5GC, NR (generally referred to as 5G) and / or LTE-A Pro. However, the scope of this disclosure is not limited to these protocols.

[0034] A BS may include, but is not limited to, a B node (NB) in UMTS, an evolved B node (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in GSM / GERAN, a next-generation eNB (ng) in an Evolved Terrestrial Universal Access Radio BS (E-UTRA) in connection with 5GC, a next-generation B node (gNB) in 5G-RAN, or any other device capable of controlling radio communication and managing radio resources within a cell. A BS may serve one or more UEs through a radio interface.

[0035] A BS can provide radio coverage for a specific geographic area using a plurality of cells forming the RAN. The BS supports the operations of the cells. Each cell is operable to provide services to at least one UE within its radio coverage.

[0036] Each cell (often called a service cell) can provide services to serve one or more UEs within its radio coverage, such that each cell schedules downlink (DL) and optionally uplink (UL) resources for at least one UE within its radio coverage for DL ​​and optionally UL packet transmissions. The BS can communicate with one or more UEs in the radio communication system through cell plurality. A cell can allocate sidelink (SL) resources to support proximity service (ProSe) or vehicle-to-everything (V2X) service. Each cell can have coverage areas that overlap with other cells.

[0037] Examples of some terms used in this publication are: Petition 870250098665, dated 10 / 28 / 2025, page 22 / 78 16 / 55 Primary Cell (PCell): A PCell is the master cell group (MCG) cell, operating at the primary frequency, on which a UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. A PCell is the special cell (SpCell) of the MCG.

[0038] Primary SCG Cell (PSCell): For dual connectivity (DC) operation, PSCell is the secondary cell group (SCG) cell in which the UE performs random access when performing the Synchronization Reconfiguration procedure. PSCell is the SpCell of the SCG. In some implementations, the term PSCell may refer to a primary secondary cell. The terms “Primary SCG Cell” and “Primary Secondary Cell” may be used interchangeably in this disclosure.

[0039] Special Cell (SpCell): For DC operation, the term Special Cell (SpCell) refers to the PCell of the MCG or the PSCell of the SCG, otherwise, the term Special Cell refers to the PCell.

[0040] Secondary Cell (SCell): For a UE configured with carrier aggregation (CA), the SCell is a cell that provides additional radio capabilities beyond the special cell.

[0041] Service Cell: For an RRC_CONNECTED UE not configured with CA / DC, there is only one service cell comprising the primary cell. For an RRC_CONNECTED UE configured with CA / DC, the term “service cells” is used to denote the set of cells comprising the Special Cell(s) and all secondary cells.

[0042] Master Cell Group (MCG): In MR-DC, MCG is a group of service cells associated with the master node, comprising the SpCell (PCell) and, optionally, one or more SCells.

[0043] Master Node (MN): In MR-DC, an MN or primary node is the radio access node that provides the control plane connection to the core network. It can be an eNB Master (in EN-DC), an ng-eNB Master (in NGEN-DC), or a gNB Master (in NR-DC and NE-DC). In Petition 870250098665, dated 10 / 28 / 2025, p. 23 / 78 17 / 55 In some implementations, an MN or primary node may comprise a source or target node for a UE.

[0044] Secondary Cell Group (SCG): In MR-DC, SCG is a group of service cells associated with the secondary node, composed of SpCell (PSCell) and, optionally, one or more SCells.

[0045] Secondary Node (SN): In MR-DC, the SN is the radio access node, without a control plane connection to the core network, providing additional resources to the UE. It can be an en-gNB (in ENDC), a secondary ng-eNB (in NE-DC), or a secondary gNB (in NR-DC and NGEN-DC). In some implementations, an SN or secondary node may comprise a source or target node for a UE.

[0046] Frequency Division Multiplexing (FDM) is a multiplexing technique that involves combining more than one signal on a shared medium. In FDM, signals of different frequencies are combined for simultaneous transmission. A total bandwidth can be divided into a set of non-overlapping frequency bands. Each of these bands comprises a carrier of a different signal that is generated and modulated by one of the multiple sending devices. Modulated signals can be combined using a multiplexer (MUX), and the combined signal can be transmitted over a communication channel, allowing multiple independent data streams to be transmitted simultaneously. In a receiving device, the individual signals are extracted from the combined signal by demultiplexing (DEMUX).

[0047] Time Division Multiplexing (TDM) is a multiplexing technique in which users utilize an available bandwidth on a time-sharing basis. The time domain is divided into multiple recurring slots of fixed length, and each signal receives a time slot, for example, in a round-robin system.

[0048] A UE can communicate with a gNB in ​​a range of Petition 870250098665, dated 10 / 28 / 2025, page 24 / 78 18 / 55 frequencies using one or more radio access technologies implementing multiple radio techniques. The frequency range may comprise frequencies in the radio frequency portion of the electromagnetic spectrum, corresponding to frequencies from approximately 3 Hz to 3.000 GHz. The frequency range may comprise frequencies in the 5G spectrum, from approximately 700 MHz to 80 GHz. One or more different radio techniques may each use at least part of this frequency range to send signals between the UE and gNB. The portions of the frequency range used by each technique may not be adjacent and / or contiguous frequency ranges and, in some cases, may not be the same for each time slot (e.g., when the technique uses frequency hopping).There may be interference between signals from one or more of the multiple radio techniques implemented by the UE in one or more frequency bands within the frequency range in which the UE is configured to operate generally, leading to device interference. The interference may be due to respective signals sent or received using two or more of the multiple radio techniques implemented by the user device, or it may be due to interference between different frequencies for a single technique, such as different frequencies used by 5G NR, for example.

[0049] As noted above, the resulting IDC interference becomes even more complex when different NR / LTE / WiFi / Bluetooth frequencies are intermodulated. For example, signals from an NR transmitter operating on FR1 (e.g., n41 band) can interfere with signals from a WiFi receiver operating on 2.5G and vice versa.

[0050] Figure 1 is a schematic representation of various radio chains for use in a user equipment (UE) according to an example. In the example in Figure 1, UE 100 accommodates transceivers 101-106 for multiple RATs implementing Petition 870250098665, dated 10 / 28 / 2025, page 25 / 78 19 / 55 multiple radio techniques. For example, transceivers 101 and 102 transmit and receive signals for NR using antenna 107, transceivers 103 and 104 transmit and receive signals for GPS using antenna 108, and transceivers 105 and 106 transmit and receive signals for WiFi and Bluetooth using antenna 109. For some frequency bands, the simultaneous operation of these multiple radio techniques working at adjacent or sub-harmonic frequencies can result in significant IDC interference that cannot be eliminated by filtering. Therefore, signaling mechanisms and procedures have been introduced to address this IDC problem.

[0051] According to an example, mechanisms are provided to allow a network device, such as a network node, particularly a Master Node (MN) or a Secondary Node (SN), to determine whether coordination is required between the two network nodes (MN and SN) when involved in a dual connectivity procedure, to resolve an IDC problem. Coordination may involve determining a configuration to resolve an IDC problem, such as using an FDM or TDM solution. Thus, in the present context, resolving an IDC problem involves using a configuration for TDM, or frequency division multiplexing, FDM, to mitigate the effects of on-device coexistence, IDC, for uplink and / or downlink communications between a master node, MN, and / or a secondary node, SN, and a user device, UE.

[0052] Figure 2 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN generates an FDM configuration when individual candidate frequencies are affected by IDC. In the example in Figure 2, SN 205 sends (1) a list of candidate SN service frequencies (which may include the candidate bandwidth) on which it is interested in receiving IDC reports regarding MN 203 as part of a configuration message (CG-Config). MN 203 Petition 870250098665, dated 10 / 28 / 2025, page 26 / 78 20 / 55 generates (2a) a combined (or consolidated) candidate service frequency band list using a list of candidate MN service frequencies representing a set of candidate frequencies or frequency bands that the MN is interested in using together with the list of candidate SN service frequencies (which may comprise a list of frequency bands). MN 203 transmits (2b) the Combined Candidate Service Frequency Band List to UE 201 as part of a configuration message.

[0053] UE 201 now has a list of combined candidate service frequency bands which is a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and SN frequency bands. UE 201 uses this to determine if any of the frequencies will cause an IDC problem. That is, whether the use of any of the sets of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and / or SN frequency bands will cause device interference between UE transceivers as a result of their physical proximity, spectral proximity and / or imperfect radio frequency (RF) filtering. If UE 201 detects such a problem, representing an IDC problem, UE 201 may report (3a) this to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC).In one example, the information reported by UE 201 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) may comprise data representing an indication of a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies or frequency bands of the master node, MN, and / or secondary node, SN, affected by coexistence in device, IDC, for uplink communications and / or. Petition 870250098665, dated 10 / 28 / 2025, p. 27 / 78 21 / 55 downlink between the master node, MN, and / or the secondary node, SN, and the user equipment, UE.

[0054] According to an example, if the individual candidate service frequency is configured by MN 203, MN 203 can take action (3b) to resolve the IDC problem. For example, MN 203 can apply scheduling restrictions on current or future service frequencies. In this case, no information is provided to SN 205 by MN 203.

[0055] If the individual candidate service frequency is configured by SN 205 (including any common MN and SN frequencies, for example), MN 203 may transmit (3c) data comprising a list of affected service frequencies (e.g., a frequency that is configured by SN 205 and included in the set of affected carrier frequencies reported by UE 201 in the UAI or IDC message) to SN 205 as part of a configuration message. SN 205 may take action to resolve the IDC problem. In one example, there may also be an explicit indication that any IDC problem is due to an individual SN frequency. A confirmation message may be transmitted (3d) from SN 205 to MN 203 after action is taken by SN 205 to resolve the IDC problem.In one example, in general, an action to resolve an IDC problem by SN 205 might involve disabling a secondary cell, SCell, of the telecommunications network; and / or switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the secondary node, SN, and the user equipment, UE; and / or restricting a physical resource block, PRB, allocation in an unaffected frequency band, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node. Petition 870250098665, dated 10 / 28 / 2025, page 28 / 78 22 / 55 SN, and the user equipment, UE. In one example, in general, an action to resolve an IDC problem by MN 203 may comprise disabling a Secondary Cell, SCell, of the telecommunications network; and / or, switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restricting a physical resource block, PRB, allocation in an unaffected frequency band, to resolve device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. [005 6] Figure 3 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN generates an FDM configuration when a frequency combination is affected by IDC. In the example in Figure 3, SN 205 transmits (1) a list of candidate SN service frequencies or frequency bands (which may include the candidate bandwidth) from which it is interested in receiving IDC reports regarding MN 203 as part of a configuration message (CG-Config). MN 203 generates (2a) a combined (or consolidated) list of candidate service frequency bands using a list of candidate MN service frequencies representing a set of candidate frequencies or frequency bands that the MN is interested in using along with the list of candidate SN service frequencies (which may comprise a list of frequency bands).MN 203 transmits (2b) the Combined Candidate service frequency band list for UE 201 as part of a configuration message.

[0057] The UE 201 now has a list of combined candidate service frequency bands which is a set of frequencies Petition 870250098665, dated 10 / 28 / 2025, p. 29 / 78 23 / 55 carriers and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and SN frequency bands. UE 201 uses this to determine if any of the frequencies will cause an IDC problem. That is, whether the use of any of the sets of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and / or SN frequency bands will cause device interference between UE transceivers as a result of their physical proximity, spectral proximity and / or imperfect radio frequency (RF) filtering. If UE 201 detects such a problem, representing an IDC problem, UE 201 may report (3a) this to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC).In one example, the information reported by UE 201 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) may comprise data representing an indication of a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies or frequency bands of the master node, MN, and / or secondary node, SN, affected by coexistence in device, IDC, for uplink and / or downlink communications between the master node, MN, and / or secondary node, SN, and the user equipment, UE.

[0058] According to an example, if the individual candidate service frequency band is configured by MN 203, MN 203 can take action (3b) to resolve the IDC problem. For example, MN 203 can apply scheduling restrictions on current or future service frequency bands. In this case, no information is provided to SN 205 by MN 203.

[0059] If the individual candidate service frequency band is configured by SN 205 (including any common MN and SN frequency bands, for example), MN 203 Petition 870250098665, dated 10 / 28 / 2025, p. 30 / 78 24 / 55 can transmit (3c) data comprising a list of affected service frequency bands (e.g., a frequency band that is configured by SN 205 and included in the set of affected carrier frequency bands reported by UE 201 in the IDC or UAI message) to SN 205 as part of a configuration message. SN 205 can take action to resolve the IDC problem. In one example, there may also be an explicit indication that any IDC problem is due to an individual SN frequency. A confirmation message can be transmitted (3d) from SN 205 to MN 203 after action is taken by SN 205 to resolve the IDC problem.In one example, in general, an action to resolve an IDC problem by SN 205 might involve implementing an FDM solution, for example, by disabling a Secondary Cell, SCell, of the telecommunications network; and / or switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the secondary node, SN, and the user equipment, UE; and / or restricting a physical resource block, PRB, allocation in an unaffected frequency band, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE.In one example, in general, an action to resolve an IDC problem by MN 203 might involve implementing an FDM solution, for example, disabling a Secondary Cell, SCell, of the telecommunications network; and / or switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restricting a physical resource block, PRB, allocation within a range of... Petition 870250098665, dated 10 / 28 / 2025, page 31 / 78 25 / 55 frequency unaffected, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. In one example, there may be an explicit indication that an IDC problem is due to a frequency combination and only one frequency of SN 205 from that combination is transmitted to SN 205.

[0060] Figure 4 is a communication flow according to an example between a UE, a MN and an SN in an MR-DC scheme where the MN generates a TDM configuration when individual frequencies are affected by IDC. In the example in Figure 4, SN 205 transmits (1) a list of candidate SN service frequencies or frequency bands (which may include the candidate bandwidth) from which it is interested in receiving IDC reports regarding MN 203 as part of a configuration message (CG-Config). As part of this message, SN 205 may include an indication to MN 203 to enable the use of TDM for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE.

[0061] MN 203 generates (2a) a combined (or consolidated) list of candidate service frequencies using a list of MN candidate services frequencies representing a set of candidate frequencies or frequency bands that the MN is interested in using together with the list of SN candidate service frequencies (which may comprise a list of frequency bands). MN 203 transmits (2b) the combined list of candidate service frequencies to UE 201 as part of a configuration message, which also includes an indication that TDM is enabled for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. Petition 870250098665, dated 10 / 28 / 2025, p. 32 / 78 26 / 55

[0062] UE 201 now has a list of combined candidate service frequency bands which is a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and SN frequency bands. UE 201 uses this to determine if any of the frequencies will cause an IDC problem. That is, whether the use of any of the sets of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and / or SN frequency bands will cause device interference between UE transceivers as a result of their physical proximity, spectral proximity and / or imperfect radio frequency (RF) filtering.If UE 201 detects such a problem, representing an IDC problem, UE 201 may report (3a) this to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) which may include TDM assistance information for UE 201, in which UE 201 may inform MN 203 of an internal status of UE 201 so that resources can be allocated appropriately. For example, one or more UE configuration parameters may be provided, comprising at least one preferred parameter for a UE 201 TDM configuration.

[0063] In one example, the information reported by UE 201 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) may comprise data representing an indication of a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies or frequency bands of the master node, MN, and / or secondary node, SN, affected by coexistence in device, IDC, for uplink and / or downlink communications between the master node, MN, and / or secondary node, SN, and the user equipment, UE. Petition 870250098665, dated 10 / 28 / 2025, p. 33 / 78 27 / 55

[0064] According to an example, if the individual candidate service frequency or frequencies are configured by MN 205, then MN can take action (3b) to resolve the IDC problem (e.g., generating a configuration for a TDM pattern). Nothing is forwarded to SN.

[0065] If individual candidate service frequencies are configured by SN 205, MN 203 may transmit (3c) the list of such affected service frequencies (i.e., a frequency or frequencies configured by SN 205 and included in the affected carrier frequency reported by UE 101 in the IDC or UAI message) along with TDM assistance information to SN 205. SN 205 may then take steps to resolve the IDC problem using a configuration for TDM, to mitigate the effects of coexistence on device, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE.

[0066] SN 205 can transmit (3d) an SCG TDM configuration to MN 203, wherein the SCG TDM configuration is generated based on the TDM pattern reported by UE. MN can transmit (4) information representing an SCG TDM or MCG configuration to UE 201.

[0067] Figure 5 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN generates a TDM configuration when a frequency combination is affected by IDC. In the example in Figure 5, SN 205 transmits (1) a list of candidate SN service frequency bands (which may include candidate bandwidth) on which it is interested in receiving IDC reports regarding MN 203 as part of a configuration message (CG-Config). As part of this message, SN 205 may include an indication to MN 203 to allow the use of TDM for uplink and / or downlink communications between MN 203 and / or SN 205. Petition 870250098665, dated 10 / 28 / 2025, page 34 / 78 28 / 55 and EU 101.

[0068] MN 203 generates (2a) a combined (or consolidated) candidate service frequency band list using a candidate MN service frequency band list representing a set of candidate frequencies or frequency bands that the MN is interested in using together with the candidate SN service frequency band list. MN 203 transmits (2b) the combined candidate service frequency band list to UE 201 as part of a configuration message, which also includes an indication that TDM is enabled for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0069] UE 201 now has a list of combined candidate service frequency bands which is a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and SN frequency bands. UE 201 uses this to determine if any of the frequencies or frequency bands will cause an IDC problem. That is, whether the use of any of the sets of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and / or SN frequency bands will cause device interference between UE transceivers as a result of their physical proximity, spectral proximity and / or imperfect radio frequency (RF) filtering.If UE 201 detects such a problem, representing an IDC problem, UE 201 may report (3a) this to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) which may include TDM assistance information for UE 201, in which UE 201 may inform MN 203 of an internal status of UE 201 so that resources can be allocated appropriately. For example, one or more UE configuration parameters may be provided. Petition 870250098665, dated 10 / 28 / 2025, page 35 / 78 29 / 55 comprising at least one preferred parameter for a UE 201 TDM configuration.

[0070] In one example, the information reported by UE 201 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) may comprise data representing an indication of a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies or frequency bands of MN203 and / or SN 205 affected by coexistence in device, IDC, for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0071] According to an example, if the individual candidate service frequency band is configured by MN 205, then MN can take action (3b) to resolve the IDC problem (e.g., generating a configuration for a TDM pattern). MN 203 transmits (3b) data representing the list of affected frequency bands, a configuration representing an MCG TDM pattern, and UE assistance information to SN 205. SN 205 can use this data to generate a configuration representing an SCG TDM pattern based on the MCG TDM pattern and the TDM pattern reported by UE from the UE assistance information. The generated SCG TDM pattern is transmitted (3c) to MN 203. The information representing the MCG and / or SCG TDM pattern can be transmitted (4) to UE 101 from MN 203 to thus resolve the IDC problem.In other words, the configurations implemented by the UE, MN, and / or SN using the generated TDM standards can mitigate the effects of any device interference in UE 101.

[0072] Figure 6 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the SN generates a TDM configuration when a frequency combination is affected by IDC. In the example in Figure 6, the SN is 205 Petition 870250098665, dated 10 / 28 / 2025, page 36 / 78 30 / 55 transmits (1) a list of candidate SN service frequency bands (which may include candidate bandwidth) on which it is interested in receiving IDC reports regarding MN 203 as part of a configuration message (CG-Config). As part of this message, SN 205 may include an indication to MN 203 to allow the use of TDM for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0073] MN 203 generates (2a) a combined (or consolidated) list of candidate service frequencies or a list of frequency bands using a list of candidate MN service frequency bands representing a set of candidate frequencies or frequency bands that the MN is interested in using together with the list of candidate SN service frequency bands. MN 203 transmits (2b) the combined list of candidate service frequency bands to UE 201 as part of a configuration message, which also includes an indication that TDM is enabled for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0074] UE 201 now has a list of combined candidate service frequency bands which is a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and SN frequency bands. UE 201 uses this to determine if any of the frequencies or frequency bands will cause an IDC problem. That is, whether the use of any of the sets of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and / or SN frequency bands will cause device interference between UE transceivers as a result of their physical proximity, spectral proximity and / or imperfect radio frequency (RF) filtering. If UE 201 Petition 870250098665, dated 10 / 28 / 2025, p. 37 / 78 31 / 55 detecting such a problem, representing an IDC problem, UE 201 may report (3a) this to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) which may include TDM assistance information for UE 201, in which UE 201 may inform MN 203 of an internal status of UE 201 so that resources can be allocated appropriately. For example, one or more UE configuration parameters may be provided, comprising at least one preferred parameter for a UE 201 TDM configuration.

[0075] In one example, the information reported by UE 201 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) may comprise data representing an indication of a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies or frequency bands of MN203 and / or SN 205 affected by coexistence in device, IDC, for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0076] According to one example, MN 203 can be configured to forward TDM assistance information from UE 101 to SN 205. That is, MN 203 does not (3b) take active measures to resolve an IDC problem reported by UE 101. Thus, MN 203 can transmit (3c) data representing the list of affected frequencies and UE assistance information to SN 205. SN 205 can use this information to resolve the IDC problem by generating a configuration for a TDM standard to be used. In one example, SN 205 generates a configuration representing an SCG TDM standard based on the TDM standard reported by the UEs (provided as part of the UE assistance information, for example) and forwards (3d) this to MN 203. MN 203 generates (3e) a configuration that Petition 870250098665, dated 10 / 28 / 2025, page 38 / 78 32 / 55 represents an MCG TDM pattern based on received SCG pattern information and the TDM pattern reported by the UEs. MN 203 can transmit (4) information representing the SCG TDM and MCG settings to UE 101, thus enabling resolution of the IDC problem.

[0077] Figure 7 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN uses a resource coordination procedure when a frequency combination is affected by IDC. In the example in Figure 7, SN 205 transmits (1) a list of candidate SN service frequency bands (which may include candidate bandwidth) on which it is interested in receiving IDC reports regarding MN 203 as part of a configuration message (CG-Config). As part of this message, SN 205 may include an indication to MN 203 to allow the use of TDM for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0078] MN 203 generates (2a) a combined (or consolidated) list of candidate service frequencies or a list of frequency bands using a list of candidate MN service frequency bands representing a set of candidate frequencies or frequency bands that the MN is interested in using together with the list of candidate SN service frequency bands. MN 203 transmits (2b) the combined list of candidate service frequency bands to UE 201 as part of a configuration message, which also includes an indication that TDM is enabled for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0079] UE 201 now has a list of combined candidate service frequency bands which is a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / bands. Petition 870250098665, dated 10 / 28 / 2025, p. 39 / 78 33 / 55 frequency of the MN and SN. UE 201 uses this to determine if any of the frequencies or frequency bands will cause an IDC problem. That is, whether the use of any of the sets of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies / MN and / or SN frequency bands will cause device interference between UE transceivers as a result of their physical proximity, spectral proximity and / or imperfect radio frequency (RF) filtering. If UE 201 detects such a problem, representing an IDC problem, UE 201 may report (3a) this to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) which may include TDM assistance information for UE 201, in which UE 201 may inform MN 203 of an internal status of UE 201 so that resources can be allocated appropriately.For example, one or more UE configuration parameters may be provided, comprising at least one preferred parameter for a UE 201 TDM configuration.

[0080] In one example, the information reported by UE 201 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC) may comprise data representing an indication of a set of carrier frequencies and / or a set of carrier frequency bands or a combination of candidate service frequencies or frequency bands of MN203 and / or SN 205 affected by coexistence in device, IDC, for uplink and / or downlink communications between MN 203 and / or SN 205 and UE 101.

[0081] In the example in Figure 7, MN 203 can resolve the IDC problem alerted by UE 101 by applying / using a configuration that represents TDM transmissions between an MCG and an SCG. That is, according to the example, MN 203 can Petition 870250098665, dated 10 / 28 / 2025, page 40 / 78 34 / 55 negotiate (3b) a UL TDM standard with SN 205 using existing MR-DC resource coordination information or MeNB resource coordination information.

[0082] Figure 8 is a communication flow according to an example between a UE, a MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a set of individual frequencies is affected by IDC. In the example in Figure 8, MN 203 and SN 205 exchange information representing the candidate frequencies. However, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies) for the UE (without any coordination). That is, MN 203 configures (1a) the candidate service frequency band list for UE 101 for IDC reporting to MN 205. SN 205 configures the candidate service frequency band list for IDC reporting to SN 205 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier Container (SRB 3)).

[0083] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether any of the frequencies will cause an IDC problem. That is, whether the use of any of the carrier frequency sets and / or a set of carrier frequency bands or a combination of candidate service frequencies / frequency bands from MN and / or SN will cause device interference between UE transceivers as a result of their physical proximity, spectral proximity and / or imperfect radio frequency (RF) filtering. If UE 201 detects such a problem, representing an IDC problem, UE checks (2a) whether the IDC problem is due to individual candidate service frequencies configured by MN 203. UE 101 may report (2b) such affected individual carrier frequencies in an IDC or UAI message to MN 205, in order to allow MN 205 to resolve the IDC problem.

[0084] The EU can check (2c) if the IDC problem is Petition 870250098665, dated 10 / 28 / 2025, page 41 / 78 35 / 55 due to individual candidate service frequencies configured by SN 205. UE 101 can report (2d) such affected individual carrier frequencies in an IDC or UAI message to SN 205 using a container on SRB1 or using SRB 3 to enable SN 205 to resolve the IDC issue. Thus, as appropriate, MN 203 or SN 205 can resolve the IDC issue as described above, for example.

[0085] Figure 9 is a communication flow according to an example between a UE, a MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a frequency combination is affected by IDC. In the example in Figure 9, MN 203 and SN 205 exchange information representing the candidate frequencies. However, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies) for the UE (without any coordination). In one example, MN 203 and SN 205 can exchange candidate frequency information during node addition or during an Xn / X2 configuration procedure.

[0086] MN 203 configures (1a) the candidate service frequency band list for UE 101 for IDC reporting to MN 205. SN 205 configures the candidate service frequency band list for IDC reporting to SN 205 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier (SRB 3)).

[0087] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether the frequency combination will cause an IDC problem. That is, whether an IDC problem is generated due to the combination of frequencies configured by MN 203 and SN 205. If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report (2b) the affected frequency combination to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC). Petition 870250098665, dated 10 / 28 / 2025, page 42 / 78 36 / 55

[0088] If MN 203 decides to resolve the IDC problem on its own, for example, by disabling a secondary cell, SCell, of the telecommunications network; and / or, switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restricting a physical resource block allocation, PRB, in an unaffected frequency band, then MN 203 does not forward any information to SN 205.

[0089] However, if MN 203 decides that SN resolves the IDC problem caused by the MR-DC frequency combination, MN 203 can forward (2d) information about the MR-DC frequency combination to SN 205. This means that there is an implicit indication for SN 205 to act.The SN 205 can then apply an FDM solution to resolve the IDC problem, such as by disabling a secondary cell, SCell, of the telecommunications network; and / or switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the SN and the UE; and / or restricting a physical resource block allocation, PRB, in an unaffected frequency band, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. There may also be an explicit indication that an IDC problem is due to a frequency mix-up and only one SN frequency from the mix-up is forwarded. SN 205 can resolve the IDC problem and transmit an acknowledgment (2e) to MN 203.

[0090] Figure 10 is a communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where Petition 870250098665, dated 10 / 28 / 2025, page 43 / 78 37 / 55 The MN and SN can configure the UE for FDM when a frequency combination is affected by IDC. In the example in Figure 10, MN 203 and SN 205 exchange information representing the candidate frequencies. However, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies) for the UE (without any coordination). In one example, MN 203 and SN 205 can exchange candidate frequency information during node addition or during an Xn / X2 configuration procedure.

[0091] MN 203 configures (1a) the candidate service frequency band list for UE 101 for IDC reporting to MN 205. MN 203 also provides an indication for UE 101 to report the affected frequency combination to MN 203. SN 205 configures the candidate service frequency band list for IDC reporting to SN 205 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier Container (SRB 3)).

[0092] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether the frequency combination will cause an IDC problem. That is, whether an IDC problem is generated due to the combination of frequencies configured by MN 203 and SN 205. If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report (2b) the affected frequency combination to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC). The entity to report (2b) the affected frequency combination (i.e., MN 205 in this example) is determined based on the indication from MN 203.

[0093] If MN 203 decides to solve the IDC problem on its own (2c), for example, by disabling a secondary cell, SCell, of the telecommunications network; and / or, switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs Petition 870250098665, dated 10 / 28 / 2025, page 44 / 78 38 / 55 available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restrict a physical resource block allocation, PRB, in an unaffected frequency band, then MN 203 does not forward any information to SN 205.

[0094] However, if MN 203 decides that SN resolves the IDC problem caused by the MR-DC frequency combination, MN 203 can forward (2d) information about the MR-DC frequency combination to SN 205. This means that there is an implicit indication for SN 205 to act.The SN 205 can then apply an FDM solution to resolve the IDC problem, such as by disabling a secondary cell, SCell, of the telecommunications network; and / or switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the SN and the UE; and / or restricting a physical resource block allocation, PRB, in an unaffected frequency band, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. There may also be an explicit indication that an IDC problem is due to a frequency mix-up and only one SN frequency from the mix-up is forwarded. SN 205 can resolve the IDC problem and transmit an acknowledgment (2e) to MN 203.

[0095] Figure 11 is a communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a frequency combination is affected by IDC. In the example in Figure 11, MN 203 and SN 205 exchange information representing the candidate frequencies. However, MN 203 and SN 205 separately configure the IDC settings (i.e., frequencies of Petition 870250098665, dated 10 / 28 / 2025, page 45 / 78 39 / 55 candidate services) for the EU (without any coordination). In one example, MN 203 and SN 205 can exchange candidate frequency information during node addition or during an Xn / X2 configuration procedure.

[0096] MN 203 configures (1a) the candidate service frequency band list for UE 101 for IDC reporting to MN 205 and forwards this to UE 101. MN 203 also provides an indication for UE 101 to report the affected frequency combination to SN 205. SN 205 configures the candidate service frequency band list for IDC reporting to SN 205 and transmits (1b) this to UE 101 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier Container (SRB 3)).

[0097] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether the frequency combination will cause an IDC problem. That is, whether an IDC problem is generated due to the combination of frequencies configured by MN 203 and SN 205. If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report (2b) the affected frequency combination to SN 205 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC). The entity to report (2b) the affected frequency combination (i.e., SN 205 in this example) is determined based on the indication from MN 203.

[0098] SN 205 can then apply an FDM solution to resolve the IDC problem, such as by disabling a secondary cell, SCell, of the telecommunications network; and / or switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the SN and the UE; and / or restricting a physical resource block allocation, PRB, in an unaffected frequency band, to resolve coexistence. Petition 870250098665, dated 10 / 28 / 2025, page 46 / 78 40 / 55 on device, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. There may also be an explicit indication that an IDC problem is due to a frequency mix-up and only one SN frequency from the mix-up is being forwarded. SN 205 can resolve the IDC problem.

[0099] In another example, MN 203 and SN 205 exchange information representing candidate frequencies. However, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies) for the UE (without any coordination). In one example, MN 203 and SN 205 may exchange candidate frequency information during node addition or during an Xn / X2 configuration procedure.

[0100] MN 203 can configure the list of candidate service frequency bands for UE 101 for IDC reporting to MN 205 and forward it to UE 101. SN 205 configures the list of candidate service frequency bands for IDC reporting to SN 205 and transmits this to UE 101 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier Container (SRB 3)).

[0101] UE 201 uses information from MN 203 and SN 205 to determine if the frequency combination will cause an IDC problem. That is, if an IDC problem is generated due to the combination of frequencies configured by MN 203 and SN 205. If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report the affected frequency combination to MN 203 or SN 205 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC). The entity to which the affected frequency combination should be reported (i.e., MN 203 or SN 205 in this example) is determined by UE. Petition 870250098665, dated 10 / 28 / 2025, p. 47 / 78 41 / 55 101. Based on the node to which UE 101 reports, that node may take appropriate action as described above with reference to Figures 10 and 11.

[0102] Figure 12 is a combined communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a set of individual frequencies or a combination of frequencies are affected by IDC. In the example in Figure 12, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies) for the UE.

[0103] SN 205 sets up the list of candidate service frequency bands for IDC reporting to SN 205 and transmits (1a) this to UE 101 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier (SRB 3)).

[0104] In one example, SN 205 may additionally send candidate service frequencies to MN 203 (1b).

[0105] MN 203 configures (1c) the candidate service frequency band list, including a candidate service frequency decided by MN 203. The candidate service frequency band list configured by MN 203 may include candidate service frequencies forwarded to it by SN 205. MN 203 forwards the configured candidate service frequency band list to UE 101.

[0106] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether the individual frequency or the combination of frequencies will cause an IDC problem. That is, whether an IDC problem is generated due to the individual frequencies or the combination of frequencies configured by MN 203 and SN 205.

[0107] If UE 201 detects such a problem, representing an IDC problem, UE checks (2a) whether the IDC problem is due to configured individual candidate service frequencies Petition 870250098665, dated 10 / 28 / 2025, p. 48 / 78 42 / 55 by MN 203. UE 101 may report (2b) such affected individual carrier frequencies in an IDC or UAI message to MN 205 in order to enable MN 205 to resolve the IDC problem.

[0108] UE can check (2c) whether the IDC problem is due to the individual candidate service frequencies configured by SN 205. UE 101 can report (2d) such affected individual carrier frequencies in an IDC or UAI message to SN 205 using a container on SRB1 or using SRB 3 to enable SN 205 to resolve the IDC problem. Therefore, as appropriate, MN 203 or SN 205 can resolve the IDC problem as described above, for example.

[0109] If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report the affected frequency combination to MN or to the node configured by NW, or decide on its own to which node to send the report (2e).

[0110] If the UE decides to report (2f) the affected frequency combination to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC), you may include the affected frequency combination in the report to the MN. If MN 203 decides to resolve the IDC problem itself, for example, by disabling a secondary cell, SCell, of the telecommunications network; and / or, switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restricting a physical resource block, PRB, allocation in an unaffected frequency band, then MN 203 does not forward any information to SN 205.

[0111] However, if MN 203 decides that SN resolves the IDC problem caused by the MR-DC frequency combination, Petition 870250098665, dated 10 / 28 / 2025, p. 49 / 78 43 / 55 MN 203 can forward (2d) information about the MR-DC frequency combination to SN 205. This means there is an implicit indication for SN 205 to act. SN 205 can then apply an FDM solution to resolve the IDC problem, such as by disabling a secondary cell, SCell, of the telecommunications network; and / or switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the SN and the UE; and / or restricting a physical resource block allocation, PRB, in an unaffected frequency band, to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE.There may also be an explicit indication that an IDC problem is due to a frequency combination and only one SN frequency from the combination is forwarded. SN 205 can resolve the IDC problem and transmit an acknowledgment (2e) to MN 203.

[0112] Figure 13 is a combined communication flow according to an example between a UE, an MN and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM when a set of individual frequencies or a combination of frequencies are affected by IDC and the UE reports individual frequency components of the combinations to the MN or SN; In the example in Figure 13, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies) for the UE.

[0113] SN 205 sets up the list of candidate service frequency bands for IDC reporting to SN 205 and transmits (1a) this to UE 101 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier (SRB 3)). Petition 870250098665, dated 10 / 28 / 2025, p. 50 / 78 44 / 55

[0114] In one example, SN 205 may also send the candidate service frequencies on which it is interested in receiving IDC reports to MN 203 (1b).

[0115] MN 203 sets (1c) the candidate service frequency band list, including the candidate service frequency decided by MN and may include those forwarded by SN 205 to UE 101 for IDC reporting to MN 203 and forwards this to UE 101.

[0116] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether the individual frequency or the combination of frequencies will cause an IDC problem. That is, whether an IDC problem is generated due to the individual frequencies or the combination of frequencies configured by MN 203 and SN 205.

[0117] If UE 201 detects such a problem, representing an IDC problem, UE checks (2a) whether the IDC problem is due to individual candidate service frequencies configured by MN 203. UE 101 may report (2b) such affected individual carrier frequencies in an IDC or UAI message to MN 205 in order to allow MN 205 to resolve the IDC problem.

[0118] UE can verify (2c) whether the IDC problem is due to the individual candidate service frequencies configured by SN 205. UE 101 can report (2d) such affected individual carrier frequencies in an IDC or UAI message to SN 205 using a container on SRB1 or using SRB 3 to enable SN 205 to resolve the IDC problem. Thus, as appropriate, MN 203 or SN 205 can resolve the IDC problem as described above, for example.

[0119] If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report the individual affected frequency range configured by the MN of the combination to the MN or report the Petition 870250098665, dated 10 / 28 / 2025, page 51 / 78 45 / 55 IDC assistance information, including the individual affected frequency range configured by the SN in combination for the SN, along with an explicit indication that the IDC problem is due to the frequency combination.

[0120] Furthermore, the node, MN 203 or SN 205, to which UE 101 can report such IDC problems arising from frequency combination, can be set by NW or decided on its own by UE (2e).

[0121] If the UE decides to report (2f) the affected frequency combination to MN 203 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC), it may include the individual affected frequency of the combination configured by the MN in the report to the MN, along with an explicit indication that this IDC problem is due to the frequency combination. MN 203 may decide to resolve the IDC problem, for example, by disabling a secondary cell, SCell, of the telecommunications network; and / or, switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restricting a physical resource block, PRB, allocation in an unaffected frequency band.

[0122] If the UE decides to report (2g) the affected frequency combination to SN 205 as part of an IDC message (for EN-DC) or a UE Assistance Information (UAI) message (for NR-DC), it may include the individual affected frequency of the combination configured by the SN in the report to the SN, along with an explicit indication that this IDC problem is due to the frequency combination. SN 205 may decide to resolve the IDC problem, for example, by disabling a secondary cell, SCell, of the telecommunications network; and / or, switching to a bandwidth portion, BWP, of the carrier Petition 870250098665, dated 10 / 28 / 2025, p. 52 / 78 46 / 55 different from a set of multiple bandwidth parts, BWPs, of carrier available for uplink and / or downlink communications between the secondary node, SN, and the user equipment, UE; and / or restrict a physical resource block allocation, PRB, in an unaffected frequency band.

[0123] Figure 15 is a combined communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM and TDM when a set of individual frequencies or a combination of frequencies are affected by IDC. In the example in Figure 15, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies and enable TDM reporting) for the UE.

[0124] SN 205 configures the candidate service frequency band list and enables TDM reporting for IDC reporting to SN 205 and transmits (1a) this to UE 101 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier (SRB 3)).

[0125] In one example, SN 205 also sends candidate service frequencies and indication to enable TDM reporting to MN 203 (1b).

[0126] MN 203 configures (1c) the candidate service frequency band list, including a candidate service frequency decided by MN 203 and also enables TDM reporting. The candidate service frequency band list configured by MN 203 may include candidate service frequencies forwarded to it by SN 205. MN 203 forwards the configured candidate service frequency band list to UE 101 and also enables TDM reporting.

[0127] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether the individual frequency or combination of frequencies will cause an IDC problem. That is, whether a Petition 870250098665, dated 10 / 28 / 2025, page 53 / 78 The 47 / 55 IDC problem is generated due to the individual frequencies or the combination of frequencies configured by MN 203 and SN 205.

[0128] If UE 201 detects such a problem, representing an IDC problem, the UE verifies (2a) whether the IDC problem is due to individual candidate service frequencies configured by MN 203. UE 101 may report (2b) such affected individual carrier frequencies in a UAI or IDC message to MN 205 along with TDM assistance information to enable MN 205 to resolve the IDC problem. MN may then resolve the IDC using the TDM solution and configure the appropriate DRX for the UE based on the TDM assistance information received from the UE.

[0129] The UE can verify (2c) whether the IDC problem is due to the individual candidate service frequencies configured by SN 205. UE 101 can report (2d) such affected individual carrier frequencies in a UAI or IDC message along with the TDM assistance information to SN 205 using a container on SRB1 or using SRB 3 to enable SN 205 to resolve the IDC problem. The SN can then resolve the IDC using the TDM solution and configure the appropriate DRX for the UE based on the TDM assistance information received from the UE. Thus, as appropriate, MN 203 or SN 205 can resolve the IDC problem as described above, for example.

[0130] If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report the affected frequency combination to MN or to the node configured by NW, or decide on its own which node to send the report to (2e).

[0131] If the UE decides to report (2f) the affected frequency combination to MN 203 as part of an IDC message (for EN-DC) or an UE assistance information message Petition 870250098665, dated 10 / 28 / 2025, p. 54 / 78 48 / 55 (UAI) (for NR-DC), may include the affected frequency combination in the report to the MN along with the TDM assistance information. If MN 203 decides to resolve the IDC issue on its own using the TDM solution and configures the appropriate XRD for the UE, then MN 203 will not forward any information to SN 205.

[0132] If MN 203 knows that SN 205 supports the TDM solution for IDC and decides that the SN should resolve the IDC problem caused by the MR-DC frequency combination, MN 203 can forward (2d) information about the MR-DC frequency combination and TDM assistance information to SN 205. This means there is an implicit indication for SN 205 to act. SN 205 can then apply a TDM solution to resolve the IDC problem, such as configuring the appropriate DRX for the UE, to resolve the on-device coexistence, IDC. There may also be an explicit indication that an IDC problem is due to a frequency combination and only one SN frequency of the combination is forwarded along with TDM assistance information. SN 205 can resolve the IDC problem and transmit an acknowledgment (2e) to MN 203.

[0133] Figure 16 is a generalized communication flow according to an example between a UE, an MN, and an SN in an MR-DC scheme where the MN and SN can configure the UE for FDM and TDM when a set of individual frequencies or a combination of frequencies are affected by IDC. In the example in Figure 16, MN 203 and SN 205 separately configure the IDC settings (i.e., candidate service frequencies and enable TDM reporting) for the UE.

[0134] SN 205 configures the candidate service frequency band list and enables TDM reporting for IDC reporting to SN 205 and transmits (1a) this to UE 101 (via a Signal 1 Radio Carrier Container (SRB 1) or a Signal 3 Radio Carrier (SRB 3)). Petition 870250098665, dated 10 / 28 / 2025, page 55 / 78 49 / 55

[0135] In one example, SN 205 also sends candidate service frequencies and indication to enable TDM reporting to MN 203 (1b).

[0136] MN 203 configures (1c) the candidate service frequency band list, including a candidate service frequency decided by MN 203 and also enables TDM reports. The candidate service frequency band list configured by MN 203 may include candidate service frequencies forwarded to it by SN 205. MN 203 forwards the configured candidate service frequency band list to UE 101 and also enables TDM reports.

[0137] UE 201 uses information from MN 203 and SN 205 to determine (2a) whether the individual frequency or the combination of frequencies will cause an IDC problem. That is, whether an IDC problem is generated due to the individual frequencies or the combination of frequencies configured by MN 203 and SN 205.

[0138] If UE 201 detects such a problem, representing an IDC problem, UE verifies (2a) whether the IDC problem is due to individual candidate service frequencies configured by MN 203. UE 101 may report (2b) such affected individual carrier frequencies in a UAI or IDC message to MN 205 along with TDM assistance information to enable MN 205 to resolve the IDC problem. MN may then resolve the IDC using an FDM or TDM solution.

[0139] The UE can verify (2c) whether the IDC problem is due to the individual candidate service frequencies configured by SN 205. UE 101 can report (2d) such affected individual carrier frequencies in a UAI or IDC message along with TDM assistance information to SN 205 using a container on SRB1 or using SRB 3 to enable SN 205 to resolve the IDC problem. SN can then resolve the IDC using an FDM or TDM solution. Thus, as Petition 870250098665, dated 10 / 28 / 2025, pp. 56 / 78 If the 50 / 55 voltage is appropriate, the MN 203 or SN 205 can resolve the IDC problem as described above, for example.

[0140] If there is a problem due to the combination of frequencies configured by MN 203 and SN 205, UE 101 can report the affected frequency combination to MN or to the node configured by NW, or decide on its own which node to send the report to (2e).

[0141] If the UE decides to report (2f) the affected frequency combination to MN 203 as part of an IDC message (for EN-DC) or a UE assistance information (UAI) message (for NR-DC), it may include the affected frequency combination and TDM assistance information in the report to the MN. If MN 203 decides to resolve the IDC problem itself using the FDM solution, for example, by disabling a secondary cell, SCell, of the telecommunications network; and / or, switching to a different carrier bandwidth portion, BWP, from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the master node, MN, and the user equipment, UE; and / or restricting a physical resource block, PRB, allocation in an unaffected frequency band; Or by using the TDM solution itself, configuring the appropriate DRX for the UE, then MN 203 does not forward any information to SN 205.

[0142] If MN 203 knows that SN 205 supports the TDM solution for IDC and decides that SN should resolve the IDC problem caused by the MR-DC frequency combination, MN 203 can forward (2d) information about the MR-DC frequency combination and TDM assistance information to SN 205. This means there is an implicit indication for SN 205 to act. SN 205 can then apply an FDM solution to resolve the IDC problem, such as by disabling a secondary cell, SCell, of the telecommunications network; and / or, switching to a Petition 870250098665, dated 10 / 28 / 2025, pp. 57 / 78 51 / 55 carrier bandwidth portion, BWP, different from a set of multiple carrier bandwidth portions, BWPs, available for uplink and / or downlink communications between the SN and the UE; and / or restricting a physical resource block allocation, PRB, in an unaffected frequency band; or applying the TDM solution by configuring the appropriate DRX for the UE to resolve on-device coexistence, IDC, for uplink and / or downlink communications between the master node, MN, and / or the secondary node, SN, and the user equipment, UE. There may also be an explicit indication that an IDC problem is due to a frequency mix-up and only one SN frequency from the mix-up is forwarded along with TDM assistance information. SN 205 may resolve the IDC problem and transmit an acknowledgment (2e) to MN 203.

[0143] Thus, several solutions are presented to address an IDC problem in MR-DC scenarios, along with configuration and solution aspects in terms of which nodes provide a configuration and how an FDM or TDM solution can be applied with coordination between nodes.

[0144] Examples in this disclosure may be provided as machine-readable procedures, methods, systems, or instructions, such as any combination of software, hardware, firmware, or the like. Such machine-readable instructions may be included in a computer-readable storage medium (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-readable program code.

[0145] This disclosure is described with reference to flowcharts and / or block diagrams of the method, devices, and systems according to examples in this disclosure. Although the flowcharts described above show a specific order of execution, the order of execution may be different. Petition 870250098665, dated 10 / 28 / 2025, pp. 58 / 78 52 / 55 of that described. Blocks described in relation to one flowchart may be combined with those of another flowchart. In some examples, some blocks from the flowcharts may not be necessary and / or additional blocks may be added. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as combinations of flows and / or diagrams in the flowcharts and / or block diagrams, may be implemented by machine-readable instructions.

[0146] Machine-readable instructions can, for example, be executed by a machine, such as a general-purpose computer, a platform comprising user equipment, such as a smart device, for example, a smartphone, a special-purpose computer, an embedded processor, or processors of other programmable data processing devices to perform the functions described in the description and diagrams. In particular, a processor or processing appliance can execute machine-readable instructions. Thus, appliance modules can be implemented by a processor executing machine-readable instructions stored in memory, or a processor operating according to instructions embedded in logic circuits. The term processor should be interpreted broadly to include a CPU, processing unit, ASIC, logic unit, or set of programmable gates, etc.The methods and modules can be implemented by a single processor or divided among multiple processors.

[0147] These machine-readable instructions can also be stored in a computer-readable storage that can direct the computer or other programmable data processing devices to operate in a specific mode. For example, instructions can be provided in a non-transient, instruction-encoded, computer-readable storage medium executable by a processor. Petition 870250098665, dated 10 / 28 / 2025, pp. 59 / 78 53 / 55

[0148] Figure 14 is a schematic representation of a machine according to an example. The machine 1200 may be, for example, a system or apparatus, user equipment or part thereof (for example, the UE of Figure 1, a MN 203 or an SN 205). The machine 1200 comprises a processor 1203 and a memory 1205 for storing instructions 1207, executable by the processor 1203. The machine comprises a storage 1209 which may be used to store data representing settings for FDM and / or TDM patterns, as described above with reference to Figures 1 to 11, for example.

[0149] The 1200 machine can implement a method to mitigate on-device coexistence between multiple radio transceivers that implement multiple radio communication protocols for a UE configured to operate in dual connectivity, DC, with a master node, MN, and a secondary node, SN, of a telecommunications network so that the UE can transmit and receive data on multiple component carriers of the MN and SN.

[0150] These machine-readable instructions can also be loaded into a computer or other programmable data processing devices, so that the computer or other programmable data processing devices perform a series of operations to produce computer-implemented processing; thus, the instructions executed on the computer or other programmable devices provide an operation to perform functions specified by flow(s) in flowcharts and / or block(s) in block diagrams.

[0151] Furthermore, the teachings contained herein may be implemented in the form of a computer product or software, such as a non-transient machine-readable storage medium, the software or computer product being stored on a storage medium and comprising a plurality of instructions, for example, machine-readable instructions, for Petition 870250098665, dated 10 / 28 / 2025, pp. 60 / 78 54 / 55 to make a computer device implement the methods described in the examples in this disclosure.

[0152] In some examples, some methods can be performed in a cloud computing or network-based environment. Cloud computing environments can provide various services and applications via the Internet. These cloud-based services (e.g., software as a service, platform as a service, infrastructure as a service, etc.) can be accessed through a web browser or other remote interface from the user's equipment, for example. Several functions described here can be provided through a remote desktop environment or any other cloud computing environment.

[0153] Although several embodiments have been described and / or illustrated here in the context of fully functional computing systems, one or more of these exemplary embodiments may be distributed as a program product in a variety of forms, regardless of the specific type of computer-readable storage medium used to actually perform the distribution. The embodiments disclosed here may also be implemented using software modules that perform certain tasks. These software modules may include scripts, batches, or other executable files that may be stored on a computer-readable storage medium or on a computing system. In some embodiments, these software modules may configure a computing system to perform one or more of the exemplary embodiments disclosed here.Furthermore, one or more of the modules described here can transform data, physical devices, and / or representations of physical devices from one form to another.

[0154] The preceding description was provided to enable other skilled individuals in the field to better utilize various aspects of the exemplary modalities disclosed herein. This exemplary description Petition 870250098665, dated 10 / 28 / 2025, pp. 61 / 78 55 / 55 is not intended to be exhaustive or limited to any precise form disclosed. Many modifications and variations are possible without departing from the spirit and scope of the instant disclosure. The embodiments disclosed herein should be considered in all respects illustrative and not restrictive. Reference should be made to the appended claims and their equivalents to determine the scope of the instant disclosure.

Claims

1. Master node, MN, in a telecommunications network, characterized in that the telecommunications network additionally comprises a secondary node, SN, and a user equipment, UE, and in that the UE is operable in dual connectivity, DC, with the MN and with the SN such that the UE can transmit and receive data on multiple carriers from the MN and the SN, the MN being configured to: receive, from the UE, data representing an indication of a set of carrier frequencies or a set of carrier frequency bands or a combination of a set of carrier frequencies and a set of carrier frequency bands, or a combination of candidate service frequencies or frequency bands affected by device coexistence, IDC, in which the MN is additionally configured to: use a data-matched configuration for time-division multiplexing, TDM, or frequency-division multiplexing, FDM, to mitigate the effects of IDC.

2. Master node, according to claim 1, characterized in that the configuration is determined based on data received from the UE, by the SN.

3. Master node, according to claim 1 or 2, characterized in that the set of carrier frequencies or the set of carrier frequency bands or the combination of the set of carrier frequencies and the set of carrier frequency bands is configured by the MN.

4. Master node, according to claim 1 or 2, characterized in that the master node is additionally configured to: transmit to the SN the data representing the indication of the set of carrier frequencies or the set of carrier frequency bands or the combination of the set of carrier frequencies and the set of carrier frequency bands, or a combination of candidate service frequencies or frequency bands, wherein the set of carrier frequencies or the set of carrier frequency bands or the combination of the set of carrier frequencies and the set of carrier frequency bands or a combination of candidate service frequencies or frequency bands is configured by the SN.

5. Master node, according to any one of claims 1 to 4, characterized in that the master node is additionally configured to: disable a Secondary Cell, SCell; or, switch to a different carrier bandwidth portion, BWP, from a set of multiple available BWPs; or, restrict a physical resource block allocation, PRB, in an unaffected frequency band; or, disable a Secondary Cell, SCell, and switch to a different carrier bandwidth portion, BWP, from a set of multiple available BWPs; or, disable a Secondary Cell, SCell, and restrict a physical resource block allocation, PRB, in an unaffected frequency band; or, switch to a different carrier bandwidth portion, BWP, from a set of multiple available BWPs and restrict a physical resource block allocation, PRB, in an unaffected frequency band;or, deactivate a Secondary Cell, SCell, and switch to a different carrier bandwidth portion, BWP, from a set of multiple available BWPs and restrict a physical resource block allocation, PRB, in an unaffected frequency band. Petition 870260043387, dated 08 / 05 / 2026, page 9 / 25 3 / 9; 6. Master node, according to any one of claims 1 to 5, characterized in that the master node is additionally configured to: receive, from the SN, data representing an indication to enable TDM; and transmit, to the SN, TDM assistance information comprising at least one TDM pattern.

7. Master node, according to claim 6, characterized in that the master node is additionally configured to: receive, from the SN, data representing a TDM pattern of the SN, the TDM pattern of the SN, configured by the SN, based on at least one TDM pattern received as part of the TDM assistance information; and transmit, to the UE, the data representing the TDM pattern of the SN.

8. Master node, according to claim 6, characterized in that the master node is additionally configured to: transmit, to the SN, a TDM pattern for a group of master cells, MCG.

9. Master node, according to claim 8, characterized in that the master node is additionally configured to: receive, from the SN, data representing a TDM pattern of the SN, the TDM pattern of the SN, configured by the SN, based on at least one TDM pattern received as part of the TDM assistance information, and the TDM pattern for the MCG; and transmit, to the UE, the data representing the TDM pattern of the SN.

10. Master node, according to claim 6, characterized in that the master node is additionally configured to: receive, from the SN, data representing a TDM pattern of the SN, the TDM pattern of the SN, configured by the SN, based on at least one TDM pattern received as part of the TDM assistance information; and configure a TDM pattern for an MCG based on the TDM pattern of the SN.

11. Method, characterized in that it comprises: receiving, from a user device (UE), data representing an indication of a set of carrier frequencies or a set of carrier frequency bands or a combination of a set of carrier frequencies and a set of carrier frequency bands, or a combination of candidate service frequencies or frequency bands affected by coexistence in a device (IDC); using a configuration corresponding to the data, for time-division multiplexing (TDM) or frequency-division multiplexing (FDM), to mitigate the effects of IDC.

12. Method, according to claim 11, characterized in that the configuration is determined based on data received from the UE, by a secondary node, SN.

13. Method, according to claim 11 or 12, characterized in that the set of carrier frequencies or the set of carrier frequency bands or the combination of the set of carrier frequencies and the set of carrier frequency bands is configured by the MN.

14. Method, according to claim 11 or 12, characterized in that it further comprises: transmitting to the SN the data representing the indication of the set of carrier frequencies or the set of carrier frequency bands or the combination of the set of carrier frequencies and the set of carrier frequency bands, or a combination of candidate service frequencies or frequency bands, wherein the set of carrier frequencies or the set of carrier frequency bands or the combination of the set of carrier frequencies and the set of carrier frequency bands or a combination of candidate service frequencies or frequency bands is configured by the SN.

15. A method, according to any one of claims 11 to 14, characterized in that it further comprises: receiving, from the SN, data representing an indication to enable TDM; and transmitting, to the SN, TDM assistance information comprising at least one TDM pattern.

16. User equipment, UE, characterized in that it is configured to operate in dual connectivity, DC, with a master node, MN, and a secondary node, SN, of a telecommunications network, such that the UE can transmit and receive data using multiple carriers from the MN and the SN, wherein the UE is configured to: receive, from the MN, a first set of data representing a first set of candidate carrier frequencies or a first list of candidate service frequency bands or the combination of a first set of candidate carrier frequencies and a first list of candidate service frequency bands for uplink or downlink or the combination of uplink and downlink communications between the UE and the MN;to receive, from the SN, a second set of data representing a second set of candidate carrier frequencies or a second list of candidate service frequency bands or the combination of a second set of candidate carrier frequencies and a second list of candidate service frequency bands for uplink or downlink or the combination of uplink and downlink communications between the UE and the SN; and to detect coexistence in device, IDC, based on Petition 870260043387, dated 08 / 05 / 2026, page 12 / 25 6 / 9 first set of data or in the second set of data or in the combination of the first set of data and the second set of data; and to transmit data to the MN or to the SN, representing an indication from the IDC.

17. UE, according to claim 16, characterized in that the UE is additionally configured to: receive, from the MN, data that represent an indication for the UE to report, to the MN, a combination of candidate service frequencies or frequency bands.

18. UE, according to claim 16, characterized in that the UE is additionally configured to: receive, from the MN, data that represent an indication for the UE to report, to the SN, a combination of candidate service frequencies or frequency bands.

19. Method, characterized in that it comprises: receiving, from a master node, MN, a first set of data representing a first set of candidate carrier frequencies or a first list of candidate service frequency bands or the combination of a first set of candidate carrier frequencies and a first list of candidate service frequency bands; receiving, from a secondary node, SN, a second set of data representing a second set of candidate carrier frequencies or a second list of candidate service frequency bands or the combination of a second set of candidate carrier frequencies and a second list of candidate service frequency bands; and detecting device coexistence, IDC, based on the first set of data or the second set of data or the combination of the first set of data and the second set of data;and transmit data to the MN, or to the SN, representing a Petition 870260043387, dated 08 / 05 / 2026, page 13 / 25 7 / 9 indication of the IDC.; 20. Secondary node, SN, in a telecommunications network, characterized in that the telecommunications network additionally comprises a master node, MN, and a user equipment, UE, and in that the UE is operable in dual connectivity, DC, with the MN and with the SN such that the UE can transmit and receive data on multiple carriers from the MN and the SN, the SN being configured to: receive, from the MN, data representing a list comprising a set of carrier frequencies or a set of frequency bands or a combination of a set of carrier frequencies and a set of frequency bands affected by device coexistence, IDC, or a combination of candidate service frequencies or frequency bands affected by IDC, in which the carrier frequencies or frequency bands or the combination of carrier frequencies and frequency bands are configured by the SN and transmit, to the MN,A confirmation message to acknowledge receipt of data representing a list comprising a set of carrier frequencies or a set of frequency bands or a combination of a set of carrier frequencies and a set of frequency bands.

21. Secondary node, according to claim 20, characterized in that the secondary node is configured to: disable a Secondary Cell, SCell; or, switch to a different carrier bandwidth portion, BWP, from a set of multiple available BWPs; or restrict a physical resource block allocation, PRB, in an unaffected frequency band; or disable a Secondary Cell, SCell and switch to a Petition 870260043387, dated 08 / 05 / 2026, p.14 / 25 8 / 9 portion of bandwidth, BWP, of a carrier different from a set of multiple available BWPs; or disable a Secondary Cell, SCell, and restrict a physical resource block, PRB, allocation in an unaffected frequency band; or switch to a portion of bandwidth, BWP, of a carrier different from a set of multiple available BWPs and restrict a physical resource block, PRB, allocation in an unaffected frequency band; or disable a Secondary Cell, SCell, and switch to a portion of bandwidth, BWP, of a carrier different from a set of multiple available BWPs and restrict a physical resource block, PRB, allocation in an unaffected frequency band.

22. Secondary node, according to claim 20 or 21, characterized in that the secondary node is configured to: transmit, the MN, a time-division multiplexing pattern, TDM, to a group of secondary cells, SCG.

23. Method, characterized in that the method is applied by a secondary node, SN, comprising: receiving, from a master node, MN, data representing a list comprising a set of carrier frequencies or a set of frequency bands or the combination of a set of carrier frequencies and a set of frequency bands affected by device coexistence, IDC, or a combination of candidate service frequencies or frequency bands affected by IDC, wherein the carrier frequencies or frequency bands or the combination of carrier frequencies and frequency bands are configured by the SN; transmitting, to the MN, a confirmation message to confirm Petition 870260043387, dated 08 / 05 / 2026, page 1.15 / 25 9 / 9 the receipt of data representing a list comprising a set of carrier frequencies or a set of frequency bands or a combination of a set of carrier frequencies and a set of frequency bands.

24. Communication apparatus, comprising a processor, characterized in that the processor is coupled to a memory, and the processor is configured to execute instructions stored in the memory, such that the communication apparatus is enabled to implement the method as defined in any one of claims 11 to 15, or 19, or 23.

25. Computer-readable storage medium, characterized in that the computer-readable storage medium stores instructions and, when the instructions are run on a communication device, the communication device is enabled to perform the method as defined in any one of claims 11 to 15, or 19, or 23.

Images