USER EQUIPMENT CAPABILITIES COORDINATION FOR EVOLVED UNIVERSAL MOBILE TELECOMMUNICATIONS SYSTEM TERRESTRIAL RADIO ACCESS (E-UTRAN) AND NEW RADIO (NR) MIXED DEPLOYMENTS

CROSS REFERENCE TO RELATED APPLICATIONS:

This application claims priority from United States Provisional Application No. 62/540,674, filed on August 3, 2017. The entire contents of this earlier filed application are hereby incorporated by reference in their entirety.

BACKGROUND:

Field:

Embodiments of the invention generally relate to wireless or cellular communications networks, such as, but not limited to, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, and/or 5G radio access technology or new radio access technology (NR). Some embodiments may generally relate to User Equipment (UE) capabilities for mixed network deployments, such as E-UTRAN-NR or LTE-NR deployment, for example.

Description of the Related Art:

Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) refers to a communications network including base stations, or Node Bs, and for example radio network controllers (RNC). UTRAN allows for connectivity between the user equipment (UE) and the core network. The RNC provides control functionalities for one or more Node Bs. The RNC and its corresponding Node Bs are called the Radio Network Subsystem (RNS). In case of E- UTRAN (Evolved-UTRAN), the air interface design, protocol architecture and multiple-access principles are new compared to that of UTRAN, and no RNC exists and radio access functionality is provided by an evolved Node B (eNodeB or eNB) or many eNBs. Multiple eNBs are involved for a single UE connection, for example, in case of Coordinated Multipoint Transmission (CoMP) and in dual connectivity.

Long Term Evolution (LTE) or E-UTRAN improved efficiency and services, offers lower costs, and provides new spectrum opportunities, compared to the earlier generations. In particular, LTE is a 3GPP standard that provides for uplink peak rates of at least, for example, 75 megabits per second (Mbps) per carrier and downlink peak rates of at least, for example, 300 Mbps per carrier. LTE supports scalable carrier bandwidths from 20 MHz down to 1.4 MHz and supports both Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD). Carrier aggregation or said dual connectivity further allows operating on multiple component carriers at the same time hence multiplying the performance such as data rates per user.

As mentioned above, LTE may also improve spectral efficiency in networks, allowing carriers to provide more data and voice services over a given bandwidth. Therefore, LTE is designed to fulfill the needs for high-speed data and media transport in addition to high capacity voice support. Advantages of LTE include, for example, high throughput, low latency, FDD and TDD support in the same platform, an improved end-user experience, and a simple architecture resulting in low operating costs.

Certain further releases of 3GPP LTE (e.g., LTE Rel-10, LTE Rel-1 1) are targeted towards international mobile telecommunications advanced (IMT-A) systems, referred to herein for convenience simply as LTE- Advanced (LTE- A).

LTE-A is directed toward extending and optimizing the 3GPP LTE radio access technologies. A goal of LTE-A is to provide significantly enhanced services by means of higher data rates and lower latency with reduced cost. LTE-A is a more optimized radio system fulfilling the international telecommunication union-radio (ITU-R) requirements for IMT-Advanced while maintaining backward compatibility. One of the key features of LTE-A, introduced in LTE Rel-10, is carrier aggregation, which allows for increasing the data rates through aggregation of two or more LTE carriers. The next releases of 3GPP LTE (e.g. LTE Rel-12, LTE Rel-13, LTE Rel-14, LTE Rel- 15) are targeted for further improvements of specialized services, shorter latency and meeting requirements approaching the 5G.

5 ^th generation (5G) or new radio (NR) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G is also known to appear as the IMT- 2020 system. It is estimated that 5G will provide bitrates on the order of 10-20 Gbit/s or higher. 5G will support at least enhanced mobile broadband (eMBB) and ultra- reliable low-latency-communication (URLLC). 5G is also expected to increase network expandability up to hundreds of thousands of connections. The signal technology of 5G is anticipated for greater coverage as well as spectral and signaling efficiency. 5G is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. In 5G or NR, the Node B or eNB may be referred to as a next generation Node B (gNB).

SUMMARY:

One embodiment is directed to a method that may include a network node requesting LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities. The method may also include receiving or fetching the LTE-NR DC Capabilities. According to an embodiment, the network node is able to comprehend the LTE-NR DC Capabilities. The method may include using the UE capability information to determine at least the UE configuration, bearers configuration and SN configuration. In one embodiment, the request for the LTE-NR DC Capabilities may be separated from a generic UE-EUTRA-Capability enquiry and dedicated to UE Capabilities enquiry specific for NSA operations. In another embodiment, the request for the LTE-NR DC Capabilities may be separated from a UE-NR-Capability enquiry.

Another embodiment is directed to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to request LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities. The at least one memory and the computer program code may be further configured, with the at least one processor, to cause the apparatus at least to receive or fetch the LTE-NR DC Capabilities. According to an embodiment, the apparatus is able to comprehend the LTE-NR DC Capabilities. The at least one memory and the computer program code may be further configured, with the at least one processor, to cause the apparatus at least to use the UE capability information to determine at least the UE configuration, bearers configuration and SN configuration. In one embodiment, the request for the LTE-NR DC Capabilities may be separated from a generic UE- EUTRA-Capability enquiry and dedicated to UE Capabilties enquiry specific for NSA operations. In another embodiment, the request for the LTE-NR DC Capabilities may be separated from a UE-NR-Capability enquiry.

Another embodiment is directed to an apparatus that may include requesting means for requesting LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category. The apparatus may also include receiving means for receiving or fetching the LTE-NR DC Capabilities. According to an embodiment, the apparatus is able to comprehend the LTE-NR DC Capabilities. The apparatus may include using means for using the UE capability information to determine at least the UE configuration, bearers configuration and SN configuration. In one embodiment, the request for the LTE-NR DC Capabilities may be separated from a generic UE-EUTRA-Capability enquiry and dedicated to UE Capabilties enquiry specific for NSA operations. In another embodiment, the request for the LTE-NR DC Capabilities may be separated from a UE-NR-Capability enquiry. Another embodiment is directed to a method that may include a network node requesting LTE-NR DC Capabilities, and, receiving or fetching the LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities. The network node is then able to comprehend the LTE-NR DC Capabilities, and the method may include using the UE capability information to determine at least UE and/or bearers configuration. According to an embodiment, the network node may use the LTE-NR DC UE Category as a fallback NR UE Category or UE's supported frequency bands in a single radio technology as fallback frequency bands for DC frequency bands. In one embodiment, the method may also include triggering subsequent fetch of the complete UE NR Capabilities.

Another embodiment is directed to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to request LTE-NR DC Capabilities, and, receive or fetch the LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities. The apparatus is then able to comprehend the LTE-NR DC Capabilities, and at least one memory and the computer program code may be further configured, with the at least one processor, to cause the apparatus at least to use the UE capability information to determine at least UE and/or bearers configuration. According to an embodiment, the apparatus may use the LTE- NR DC UE Category as a fallback NR UE Category or UE's supported frequency bands in a single radio technology as fallback frequency bands for DC frequency bands. In one embodiment, the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to trigger subsequent fetch of the complete UE NR Capabilities.

Another embodiment is directed to an apparatus that may include requesting means for requesting LTE-NR DC Capabilities, and, receiving means for receiving or fetching the LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities. The apparatus is then able to comprehend the LTE- NR DC Capabilities, and the apparatus may further include using means for using the UE capability information to determine at least UE and/or bearers configuration. According to an embodiment, the apparatus may use the LTE-NR DC UE Category as a fallback NR UE Category or UE's supported frequency bands in a single radio technology as fallback frequency bands for DC frequency bands. In one embodiment, the apparatus may also include triggering means for triggering subsequent fetch of the complete UE NR Capabilities.

Another embodiment is directed to a method that may include a UE generating a common part of LTE-NR capabilities. The UE may be capable of operations in non- standalone (e.g., LTE and NR) deployments and may implement a LTE-NR capability component. The common part of LTE-NR capabilities may include at least LTE-NR DC UE Category and/or LTE-NR common band combinations. Based on a master node enquiry, the method may include signaling a LTE-NR DC Capability. According to some embodiments, the LTE-NR DC Capability may be provided separately from UE-EUTRA-Capability as a NSA specific UE capabilities and/or may be provided separately from UE-NR-Capability. In an embodiment, the separation of the LTE-NR DC Capability may be realized by using a separate capability block or a separate reply message.

Another embodiment is directed to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to generate a common part of LTE-NR capabilities. The apparatus may be capable of operations in non- standalone (e.g., LTE and NR) deployments and may implement a LTE-NR capability component. The common part of LTE-NR capabilities may include at least LTE-NR DC UE Category and/or LTE-NR common band combinations. Based on a master node enquiry, the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to signal a LTE-NR DC Capability. According to some embodiments, the LTE-NR DC Capability may be provided separately from UE-EUTRA-Capability as a NSA specific UE capabilities and/or may be provided separately from UE-NR-Capability. In an embodiment, the separation of the LTE-NR DC Capability may be realized by using a separate capability block or a separate reply message.

Another embodiment is directed to an apparatus that may include generating means for generating a common part of LTE-NR capabilities. The apparatus may be capable of operations in non- standalone (e.g., LTE and NR) deployments and may implement a LTE-NR capability component. The common part of LTE-NR capabilities may include at least LTE-NR DC UE Category and/or LTE-NR common band combinations. Based on a master node enquiry, the apparatus may include signaling means for signaling a LTE-NR DC Capability. According to some embodiments, the LTE-NR DC Capability may be provided separately from UE-EUTRA-Capability as a NSA specific UE capabilities and/or may be provided separately from UE-NR- Capability. In an embodiment, the separation of the LTE-NR DC Capability may be realized by using a separate capability block or a separate reply message.

Another embodiment is directed to an apparatus configured for provision of a common part of LTE-NR capabilities. The common part of LTE-NR capabilities may include at least LTE-NR DC UE Category and/or LTE-NR common band combinations. Based on the apparatus provision of the LTE NR capabilities, the master node may include signaling means for signaling the LTE-NR DC Capability further to a secondary node along secondary cell configuration message. The NR DC Capability may be provided separately from UE-EUTRA-Capability as a NSA specific UE capability and/or may be provided separately from UE-NR-Capability. In an embodiment, the separation of the LTE-NR DC Capability may be realized by using a separate capability block or a separate reply message.

BRIEF DESCRIPTION OF THE DRAWINGS:

For proper understanding of the invention, reference should be made to the accompanying drawings, wherein: Fig. 1 illustrates a signaling diagram depicting an example of capability coordination during a SgNB addition procedure, according to an embodiment;

Fig. 2 illustrates possible duplicated signalling for UE-ENDC-Capability based on E- UTRA-NR (EN)-DC UE category as the component;

Fig. 3 illustrates an example signaling diagram, according to an embodiment;

Fig. 4 illustrates an example signaling diagram depicting UE capability coordination with UE capabilities enquiry specific for NSA operations, according to an embodiment;

Fig. 5 illustrates an example signaling diagram depicting UE capability coordination with UE Capabilities enquiry split for NR component fetch, according to an embodiment;

Fig. 6 illustrates an example signaling diagram for UE Capability coordination with UE Capabilities enquiry split for each capability component (E-UTRA, ENDC, NR), according to an embodiment;

Fig. 7a illustrates an example block diagram of an apparatus, according to one embodiment;

Fig. 7b illustrates an example block diagram of an apparatus, according to another embodiment;

Fig. 8a illustrates an example flow diagram of a method, according to one embodiment;

Fig. 8b illustrates an example flow diagram of a method, according to another embodiment; and

Fig. 8c illustrates an example flow diagram of a method, according to another embodiment.

DETAILED DESCRIPTION:

It will be readily understood that the components of the invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of systems, methods, apparatuses, and computer program products relating to UE capabilities for mixed network deployment, as represented in the attached figures and described below, is not intended to limit the scope of the invention but is representative of selected embodiments of the invention.

The features, structures, or characteristics of the invention described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases "certain embodiments," "some embodiments," or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. Thus, appearances of the phrases "in certain embodiments," "in some embodiments," "in other embodiments," or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Additionally, if desired, the different functions discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles, teachings and embodiments of this invention, and not in limitation thereof.

The aimed 3 GPP solution is where the master node and secondary node are not required to comprehend each other's UE configuration. The eNB should be able to retrieve NR Capability or LTE/NR Capability. Coordination aspects between eNB and gNB, remain determined by inter-node signaling and related procedures, such as SgNB addition or Cell Group configuration.

However, there is a need for a common piece of UE capabilities among LTE and NR. In particular, the need of LTE-NR dual connectivity (DC) UE categories indicating the combined LTE and NR capabilities, as opposed to defining LTE UE categories and NR UE categories separately, is desirable for all LTE-NR DC deployment options. This implies that, apart from separated LTE and NR UE capabilities, there will be a common part of E-UTRA-NR DC UE capabilities that will have to be comprehended by each RAT.

One embodiment is directed to allowing independent LTE and NR capabilities indication, where the master node and secondary node are not required to comprehend each other's UE configuration. This condition resulted in assumptions that the eNB as a master node will receive NR UE capabilities in a form of a transparent container that will not be used by the eNB, but will be signalled by the UE for the purposes of forwarding it to the gNB during a secondary gNB (SgNB) addition procedure. Fig. 1 illustrates a signaling diagram depicting an example of capability coordination during a SgNB addition procedure, according to an embodiment. As illustrated in Fig. 1 , the UE 100 may provide its capability information including UE-NR capability to the master node, MeNB 1 10. Then, during or upon an SgNB addition procedure, the MeNB 1 10 may provide the UE capability information to the SgNB 120.

Further evaluation of use cases and more mature analysis on common deployments resulted in an exception to the above. The independency should not apply at least to the LTE-NR DC UE category and/or to common baseband capabilities. In addition the following UE capabilities might be subject to be coordinated across the master node and the secondary node: band combinations across RATs; supported frequencies, Layer-2 buffer, any RAT specific features,.

While initially, it has been aimed at a unified signalling procedure of the UE capabilities to eNB, regardless of its partially transparent content (NR relevant) the exception, i.e., combined LTE-NR DC UE capability should indicate device common capabilities that let the eNB and gNB interpret and determine expected configuration and device's performance. This should be sufficient for the initial SgNB addition. The question arises then on the usefulness of duplicated content of the assumed common LTE-NR DC UE Capability compared to independent components of the LTE and NR Capabilities (i.e., NR container). If the eNB received common LTE-NR DC UE capability to configure DC operation, is there a purpose for passing the NR specific content along with UECapabilitylnformation.

As the LTE-NR DC UE Capabilities should be implemented as a common coordinated UE capability, one possible approach is that it would double the content from both separated capability components, as illustrated in Fig. 2. In particular, Fig. 2 illustrates possible duplicated signalling for UE-ENDC-Capability based on E-UTRA-NR (EN)- DC UE category as the component. For UE Capabilities coordinated among LTE and NR signalling procedures as such does not yet exist, certain embodiments take an approach to mitigate the duplication and redundant involvement of the master node (MN).

In an embodiment, a master node (MN) may control the UE capabilities retrieval in non-standalone/LTE-NR deployments. According to some embodiments, the procedure may be split into steps, in which UE Capabilities transfer is distinguished per isolated radio technology relevant part of capabilities and common LTE-NR Capability part. In one embodiment, the control allows to fetch UE Capabilities according to needs (i.e., according to coordination with secondary node). A UE Capabilities component, which an eNB can understand and comprehend (including common LTE-NR Capabilities), may be retrieved separately from NR specific UE capabilities, thereby making UE Capabilities coordination less exposed to duplication of signalling.

Certain embodiments include a method of handling UE capabilities coordination in LTE-NR mixed deployments. In an embodiment, as illustrated in the example signaling diagram of Fig. 3, the method may include the UE 100 (capable of operations in non- standalone (LTE and NR) deployments) implementing LTE-NR Capability component. For example, the UE 100 may generate a common part of LTE- NR capabilities (EN-DC Capabilities in Fig. 3). According to one embodiment, the common part of LTE-NR capabilities may contain at least LTE-NR DC UE Category and LTE-NR common band combinations.

In an embodiment, based on master node (i.e., eNB 1 10) enquiry, the UE 100 may signal LTE-NR DC Capability. According to certain embodiments, the LTE-NR DC Capability can be provided separately from UE-EUTRA-Capability, as non- standalone (NSA) specific UE capabilities (e.g., as shown in Fig. 4 discussed in more detail below), can be provided separately from UE-NR-Capability (e.g., as shown in Fig. 5 discussed in more detail below), and/or separation can be realized by a separate capability block or a separate reply message.

Fig. 4 illustrates an example signaling diagram depicting UE capability coordination with UE capabilities enquiry specific for NSA operations, according to an embodiment. As illustrated in Fig. 4, the UE 100 may receive a NSA Capability Enquiry and provide the UE Capability Information as UE-NR Capability and UE- ENDC Capability to the MeNB 1 10.

Fig. 5 illustrates an example signaling diagram depicting UE capability coordination with UE Capabilities enquiry split for NR component fetch, according to an embodiment. As illustrated in Fig. 5, the UE 100 may receive a Capability Enquiry and provide the UE Capability Information as UE-EUTRA Capability and UE-ENDC Capability to the MeNB 1 10. Upon a SgNB addition procedure, MeNB 1 10 may perform a UE Capability Transfer to the SgNB 120. In an embodiment, for example after RRC reconfiguration, the UE 100 may receive a UE-NR Capability Enquiry and provide the UE-NR Capability Information to the MeNB 1 10. The MeNB 1 10 may then perform a UE Capability Transfer to provide the UE-NR Capability information to the SgNB 120.

In an embodiment, the eNB 1 10 may request and fetch LTE-NR DC Capabilities, containing at least LTE-NR DC UE Category. The eNB 1 10 is able to comprehend them and may use the UE capability information to determine, for example, UE, bearers and secondary node (SN) configuration. According to certain embodiments, the request from the eNB 1 10 may be separated from a generic UE-EUTRA- Capability enquiry and dedicated to UE Capabilties enquiry specific for NSA operations, as shown in Fig. 4. In another embodiment, the request from the eNB 1 10 may be separated from UE-NR-Capability enquiry, as shown in Fig. 5. In some embodiments, the eNB 1 10 may signal the LTE-NR DC Capabilities to the CN and gNB 120. According to one embodiment, successful transfer of LTE-NR DC Capabilities to gNB 120 and actual configuration of the SgNB may trigger a subsequent step: NR-UE Capabilities transfer.

According to an embodiment, the gNB 120 may fetch LTE-NR DC Capabilities, containing at least LTE-NR DC UE Category. The gNB 120 is able to comprehend the LTE-NR DC Capabilities and use the UE capability information to determine, for example, UE and bearers configuration. In one embodiment, the gNB 120 may request the LTE-NR DC Capabilities and is able to use the LTE-NR DC UE Category as a fallback NR UE Category or UE's supported frequency bands in a single radio technology as fallback frequency bands for DC frequency bands. According to some embodiments, the gNB 120 may trigger (by successful addition of SCG Configuration based on LTE-NR DC UE Capability) subsequent fetch of the complete UE NR Capabilities, as shown in Fig. 5.

It is noted that the processes described herein may be implemented in several alternatives that are able to distinguish UE capabilities blocks per deployment scenario. One implementation would allow an eNB to rely on partial and necessary content of UE capabilities (usable LTE and ENDC components) and NR specific component transfer only when the actual need for their use in a gNB is acknowledged (after SgNB addition, e.g., in Fig 5).

Implementation of an additional procedural separation between LTE and ENDC UE Capabilities components fetch (as indicated in Fig. 6) may be an additional optimisation that would allow embodiments to address UE-EUTRA-Capability parameter size issue. More specifically, Fig. 6 illustrates an example signaling diagram for UE Capability coordination with UE Capabilities enquiry split for each capability component (E-UT A, ENDC, NR), according to an embodiment.

Fig. 7a illustrates an example of an apparatus 10 according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be a base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), WLAN access point, mobility management entity (MME), or subscription server associated with a radio access network, such as a GSM network, LTE network, 5G or NR.

It should be understood that apparatus 10 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be standalone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in Fig. 7a.

As illustrated in Fig. 7a, apparatus 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 is shown in Fig. 7a, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (i.e., in this case processor 12 represents a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

Processor 12 may perform functions associated with the operation of apparatus 10 which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.

Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor- based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.

In an embodiment, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10. In some embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink). As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly.

In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

In certain embodiments, apparatus 10 may be a network node or RAN node, such as a base station, access point, Node B, eNB, 5G or new radio Node B (gNB) or access point, WLAN access point, or the like. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein. In one embodiment, apparatus 10 may be a master node, such as a MeNB. In this embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to request LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category or UE's supported frequency bands in Dual Connectivity. Apparatus 10 may then be controlled by memory 14 and processor 12 to receive or fetch the LTE-NR DC Capabilities. According to an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to comprehend the LTE-NR DC Capabilities and to use the UE capability information to determine at least the UE configuration, bearers configuration and SN configuration. In one embodiment, the request for the LTE-NR DC Capabilities may be separated from a generic UE-EUTRA-Capability enquiry and dedicated to UE Capabilties enquiry specific for NSA operations. In another embodiment, the request for the LTE-NR DC Capabilities may be separated from a UE-NR-Capability enquiry.

According to an embodiment, apparatus 10 may also be controlled by memory 14 and processor 12 to signal the LTE-NR DC Capabilities to the core network (CN) and/or gNB. In certain embodiments, successful transfer of LTE-NR DC Capabilities to a gNB and actual configuration of the SgNB may trigger a subsequent step of NR-UE Capabilities transfer.

In another embodiment, apparatus 10 may be a secondary node, such as a SgNB. In this embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to receive or fetch LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities (e.g., supported frequency bands in Dual Connectivity). Apparatus 10 is then able to comprehend the LTE-NR DC Capabilities and may be controlled by memory 14 and processor 12 to use the UE capability information to determine at least UE and/or bearers configuration. According to an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to request the LTE-NR DC Capabilities, and is able to use the LTE-NR DC UE Category as a fallback NR UE Category or UE's supported frequency bands in a single radio technology as fallback frequency bands for DC frequency bands. In one embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to trigger (e.g., by successful addition of SCG Configuration based on LTE-N DC UE Capability) subsequent fetch of the complete UE NR Capabilities.

Fig. 7b illustrates an example of an apparatus 20 according to another embodiment. In an embodiment, apparatus 20 may be a node or element in a communications network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device. As described herein, UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, IoT device or NB-IoT device, or the like. As one example, apparatus 20 may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like.

In some example embodiments, apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, and the like), one or more radio access components (for example, a modem, a transceiver, and the like), and/or a user interface. In some embodiments, apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, and any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 7b.

As illustrated in Fig. 7b, apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in Fig. 7b, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system (i.e., in this case processor 22 represents a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

Processor 22 may perform functions associated with the operation of apparatus 20 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor- based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non-transitory machine or computer readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.

In an embodiment, apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20.

In some embodiments, apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20. Apparatus 20 may further include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

For instance, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly. Apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.

In an embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to one embodiment, apparatus 20 may be a UE, mobile device, mobile station, ME, IoT device and/or NB-IoT device, for example. According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with embodiments described herein. For example, in some embodiments, apparatus 20 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein.

In certain embodiments, apparatus 20 is capable of operations in non- standalone (e.g., LTE and NR) deployments and may implement a LTE-NR capability component. According to one embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to generate a common part of LTE-NR capabilities (e.g., EN-DC Capabilities in Fig. 3). The common part of LTE-NR capabilities may include at least LTE-NR DC UE Category and/or LTE-NR common band combinations. Based on a master node (e.g., eNB) enquiry, apparatus 20 may be controlled by memory 24 and processor 22 to signal a LTE-NR DC Capability. According to some embodiments, the LTE-NR DC Capability may be provided separately from UE-EUTRA-Capability as a NSA specific UE capabilities and/or may be provided separately from UE-NR- Capability. In an embodiment, the separation of the LTE-NR DC Capability may be realized by using a separate capability block or a separate reply message.

Fig. 8a illustrates an example flow diagram of a method, according to one embodiment. The method may be performed by a network node, such as a base station, eNB, or access node, for example. The method of Fig. 8a may include, at 800, requesting LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities (e.g., supported frequency bands in Dual Connectivity). The method may also include, at 810, receiving or fetching the LTE- NR DC Capabilities. According to an embodiment, the network node is able to comprehend the LTE-NR DC Capabilities and the method may include, at 820, using the UE capability information to determine at least the UE configuration, bearers configuration and/or SN configuration. In one embodiment, the request for the LTE- NR DC Capabilities may be separated from a generic UE-EUTRA-Capability enquiry and dedicated to UE Capabilties enquiry specific for NSA operations. In another embodiment, the request for the LTE-NR DC Capabilities may be separated from a UE-NR-Capability enquiry.

Fig. 8b illustrates an example flow diagram of a method, according to one embodiment. The method may be performed by a network node, such as a base station, gNB, or access node, for example. The method of Fig. 8b may include, at 830, requesting LTE-NR DC Capabilities, and, at 840, receiving or fetching the LTE-NR DC Capabilities that may include at least LTE-NR DC UE Category and/or UE's baseband capabilities (e.g., supported frequency bands in Dual Connectivity). The network node is then able to comprehend the LTE-NR DC Capabilities, and the method may include, at 850, using the UE capability information to determine at least UE and/or bearers configuration. According to an embodiment, the network node may use the LTE-NR DC UE Category as a fallback NR UE Category or UE's supported frequency bands in a single radio technology as fallback frequency bands for DC frequency bands. In one embodiment, the method may also include, at 860, triggering (e.g., by successful addition of SCG Configuration based on LTE-NR DC UE Capability) subsequent fetch of the complete UE NR Capabilities.

Fig. 8c illustrates an example flow diagram of a method, according to one embodiment. The method may be performed by a UE or mobile station, for example. In an embodiment, the UE may be capable of operations in non- standalone (e.g., LTE and NR) deployments and may implement a LTE-NR capability component. The method of Fig. 8c may include, at 870, generating a common part of LTE-NR capabilities (e.g., EN-DC Capabilities in Fig. 3). The common part of LTE-NR capabilities may include at least LTE-NR DC UE Category and/or LTE-NR common band combinations. Based on a master node (e.g., eNB) enquiry, the method may include, at 880, signaling a LTE-NR DC Capability. According to some embodiments, the LTE-NR DC Capability may be provided separately from UE-EUTRA-Capability as a NSA specific UE capabilities and/or may be provided separately from UE-NR- Capability. In an embodiment, the separation of the LTE-N DC Capability may be realized by using a separate capability block or a separate reply message.

In view of the above, embodiments of the invention provide several technical effects and/or improvements and/or advantages. For example, certain embodiments can achieve at least improved UE capability coordination that is able to mitigate the duplication and redundant involvement of the master node. As a result, certain embodiments can improve performance and throughput of network nodes including, for example, base stations, eNBs, gNBs and/or UEs. Accordingly, the use of embodiments of the invention result in improved functioning of communications networks and their nodes.

In some embodiments, the functionality of any of the methods, processes, signaling diagrams, or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.

In certain embodiments, an apparatus may be included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor. Programs, also called computer program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and include program instructions to perform particular tasks.

A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments described herein. The one or more computer-executable components may include at least one software code or portions of code. Modifications and configurations required for implementing the functionality of an embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In some embodiments, software routine(s) may be downloaded into the apparatus.

Software or a computer program code or portions of code may be in a source code form, object code form, or in some intermediate form, and may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital device or it may be distributed amongst a number of devices or computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

In other embodiments, the functionality may be performed by hardware, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

According to an embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation(s) and an operation processor for executing the arithmetic operation.

One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention.

Partial Glossary:

CG Cell Group

DC Dual Connectivity

EN-DC E-UTRA - NR DC

E-UTRAN Evolved UTRA

eNB Evolved Node-B

LTE Long Term Evolution

MCG Master Cell Group

MeNB Master eNB

MgNB Master gNB

MME Mobility Management Entity

MN Master Node

NSA Non-StandAlone

NR New Radio

RAT Radio Access Technology

RAN Radio Access Network

RRC Radio Resource Control

SA StandAlone

SCG Secondary Cell Group

SeNB Secondary eNB

SgNB Secondary gNB

SN Secondary Node

UE User Equipment.