Patent Description:
Accordingly there is provided a system, a computer implemented method, and a computer program as detailed in the appended set of claims that follow.

Described herein are techniques and systems relating to switching between New Radio (NR) Dual Connectivity (DC) and NR Carrier Aggregation (CA) in cellular networks. NR DC refers to a user equipment (UE) connecting to different radio access nodes. For example, <NUM> NR DC can use a first gNodeB (gNb) that is associated with a first frequency band, and a second gNb that is associated with a second frequency band. In this way, the UE could use a first frequency band, such as millimeter waves for downlink, and a second frequency band, such as non-millimeter waves for uplink. NR CA refers to aggregation of multiple carriers that allows UE to simultaneously transmit and receive data using the aggregated carriers. For example, <NUM> NR CA may support aggregation for a number of component carriers (CCs) (e.g., <NUM> CCs (contiguous and non-contiguous), or some other number of CCs) from a single gNb.

Using techniques described herein, a UE is not limited to using the initially configured mode (e.g., either NR CA or NR DC) in a stand-alone (SA) <NUM> cellular network. For example, a UE can be configured to use NR DC during a communication session while the UE is near the cell, and switch to NR CA when the UE moves away from the cell and is closer to mid-cell or the cell edge. According to some examples, network conditions associated with the cellular network (e.g., RF conditions) are monitored and analyzed by node within the cellular network (e.g., gNB) to determine when to switch. In this way, user experience will be improved as the UE is more efficiently using the available radio access technologies.

As an example, a UE can be initially configured to use NR DC or NR CA at registration and/or upon completion of a hand-over procedure. After the initial configuration, the gNB can monitor power headroom reports (PHRs) received from the UE. The gNb may use data from the PHRs to determine when to switch from/to NR DC and/or pass this data to one or more other nodes to determine when to switch from/to NR DC.

Generally, a PHR indicates how much transmission power is left for a UE to use in addition to the power being used by a current transmission. In some configurations, the gNB, or some other device or component, determines if the UE transmission (TX) power indicates that the UE is near the gNB that represents a near cell condition, or if the UE TX power indicates that the UE is farther away from the gNB and the UE is experiencing mid-cell or cell edge conditions. For instance, if the UE is using NR DC, then when the PHR indicates that enough power is left for UE TX power, then the UE stays in NR DC mode. Conversely, when the PHR indicates that the UE is running out of TX power, then the UE can be reconfigured to use NR CA.

By switching to/from NR DC, poor performance of the UE (e.g., when the UE is near/on the cell edge) can be avoided. Further, by switching to NR CA from NR DC, the UE coverage can be extended using different frequency bands. Frequency bands for <NUM> wireless cellular networks are classified into different frequency ranges, such as FR1 and FR2 frequency ranges. FR1 uses the <NUM> to <NUM> band of frequencies, and FR2 uses the <NUM> to <NUM> band of frequencies. Generally, FR1 communications are slower than but have more range compared to FR2.

The systems, devices, and techniques described herein can improve a functioning of a network by providing an architecture to switch between NR DC and NR CA based on one or more network conditions. For example, switching from/to NR DC may result in better performance for the UE. These and other improvements to the functioning of a computer and network are discussed herein. More details are provided below with reference to <FIG>.

<FIG> is a block diagram of an illustrative environment showing switching between new radio dual connectivity and carrier aggregation in cellular networks. The environment <NUM> may include an access network <NUM>, a <NUM> core network <NUM>, a network <NUM>, and a data network <NUM> that is associated with a wireless service provider(s). The environment <NUM> is illustrated in simplified form and may include many more components.

The environment <NUM> may include cells, such as cell <NUM>, that may be wireless or wired that are coupled to <NUM> core network <NUM> and/or some other network. The environment <NUM> may also include one or more access points (not shown), and one or more gateways (not shown). A cell, such as cell <NUM>, may handle traffic and signals between electronic devices, such as the user equipment <NUM>, and <NUM> CN <NUM>. For example, a cell <NUM> may perform the transcoding of speech channels, allocation of radio channels to electronic devices, paging, transmission and reception of voice and data, as well as other functions. A cell <NUM> may include several base transceiver stations (BTS), each BTS may include a transceiver, antenna, and additional network switch and control equipment that provide a network cell for facilitating wireless communication between UE computing devices and the core network <NUM> and/or other networks. In some examples, the cells <NUM> may include one or more gNodeBs and/or one or more eNodeBs.

The UE <NUM> are computing devices that can include, but are not limited to, smart phones, mobile phones, cell phones, tablet computers, portable computers, laptop computers, personal digital assistants (PDAs), electronic book devices, or any other portable electronic devices that can generate, request, receive, transmit, or exchange voice, video, and/or digital data using a cellular access network <NUM>, and/or over a Wi-Fi network, or some other type of network. In some instances, the UE <NUM> computing devices can be configured to send and receive data using any wired or wireless protocols. Additional examples of the UE <NUM> include, but are not limited to, smart devices such as televisions, music players, or any other electronic appliances that can generate, request, receive, transmit, or exchange voice, video, and/or digital data over a network. In some examples, the UE <NUM> is configured to communicate with <NUM> CN <NUM>, and/or other cellular networks. The UE <NUM> can further be configured to establish or receive a communication session, such as a voice call, a video call, or another sort of communication.

In some configurations, one or more nodes, such as nodes <NUM> illustrated in <NUM> CN <NUM> and/or nodes <NUM> illustrated in network <NUM> may be configured as one or more application servers that provide support for one more applications, such as application <NUM> used by one or more computing devices, such as UE <NUM>. Some example applications include, but are not limited to browser applications, messaging applications, voice applications (e.g., Voice over Internet Protocol "VoIP" applications), video applications, and the like.

While the nodes <NUM> are illustrated within the <NUM> CN <NUM> and nodes <NUM> are illustrated in network <NUM>, one or more other computing devices may be located outside of these networks. For example, an application server, or some other server or device, may be connected to a network via one or more external packet switched networks, such as the Internet.

According to some configurations, a telephony client application, such as application <NUM>, on the UE <NUM> may establish data communication with the network <NUM> through a data connection to the cell <NUM>. The cell <NUM> may route a communication wired/wirelessly from the UE <NUM> through the access network <NUM> for communication to the <NUM> CN <NUM>. In general, a cell <NUM> can be implemented as a variety of technologies to provide wired and/or wireless access to the network, as discussed herein. In some instances, the cell <NUM> can include a New Radio (<NUM>) RAN, a 3GPP RAN, such a GSM/EDGE RAN (GERAN), a Universal Terrestrial RAN (UTRAN), an evolved UTRAN (E-UTRAN), or alternatively, a "non-3GPP" RAN, such as a Wi-Fi RAN, or another type of wireless local area network (WLAN) that is based on the IEEE <NUM> standards. Further, the cell <NUM> can include any number and type of transceivers and/or base stations representing any number and type of macrocells, microcells, picocells, or femtocells, for example, with any type or amount of overlapping coverage or mutually exclusive coverage.

When a communication request arrives at the network <NUM>, one or more of the nodes <NUM> may determine the identity of the originating computing device for the communication (e.g., using a telephone number, IMEI, IMSI, IP address) as well as the identity of the computing devices to send the communication. In some configurations, one or more of the nodes <NUM> may be used to determine the identity of the originating computing device for the communication as well as the identity of the computing devices to send the communication. According to some configurations, a UE <NUM> may connect to the service nodes <NUM>, or some other component such as an application server, via the Internet (not illustrated).

As illustrated, the environment <NUM> includes one or more servers, including nodes <NUM> and <NUM>, to facilitate communications by and between the various devices in the environment <NUM> and perform operations relating to using the network <NUM>, the data network <NUM>, and/or other networks. That is, environment <NUM> can include any computing devices implementing various aspects of one or more of second, third, fourth generation, and fifth generation (<NUM>, <NUM>, <NUM>, and <NUM>) cellular-wireless access technologies, which may be cross-compatible and may operate collectively to provide data communication services. Global Systems for Mobile (GSM) is an example of <NUM> telecommunications technologies; Universal Mobile Telecommunications System (UMTS) is an example of <NUM> telecommunications technologies; and Long-Term Evolution (LTE), including LTE Advanced, Evolved High-Speed Packet Access (HSPA+) are examples of <NUM>, and <NUM> NR is an example of <NUM> telecommunications technologies. Thus, the environment <NUM> may implement GSM, UMTS, LTE/LTE Advanced, and/or <NUM> NR telecommunications technologies.

The environment <NUM> may include, but is not limited to, a combination of: base transceiver stations BTSs (e.g., NodeBs, Enhanced-NodeBs, gNodeBs), Radio network Controllers (RNCs), serving GPRS support nodes (SGSNs), gateway GPRS support nodes (GGSNs), proxies, a mobile switching center (MSC), a mobility management entity (MME), a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an evolved packet data gateway (e-PDG), an Internet Protocol (IP) Multimedia Subsystem (IMS), or any other data traffic control entity configured to communicate and/or route data packets between the UE <NUM>, and one or more endpoints within the environment <NUM> (e.g., nodes 112A - <NUM> that provide network functions (NFs) 120A - 120D, Access and Mobility Management Function (AMF) <NUM>, Session Management Function (SMF) <NUM>, user-plane functions (UPFs) <NUM>, nodes 116A - 116Q that provide NFs 120E - 120I, websites, etc.). While <FIG> illustrates an example environment <NUM>, it is understood in the context of this document, that the techniques discussed herein may also be implemented in other networking technologies.

The <NUM> core network <NUM> may expose network Functions (NFs) to nodes within the network <NUM>, and/or nodes within some other network, such as network <NUM> and/or network <NUM>. As illustrated, the <NUM> CN exposes NFs 120A - 120D, AMF <NUM>, SMF <NUM>, and UPFs <NUM>.

In some examples, the UE <NUM> requests a new session that is received by an AMF <NUM>. The AMF <NUM> receives the request from the UE <NUM> and handles connection or mobility management requests while forwarding session management requirements to the SMF <NUM>. The AMF <NUM> may determine which SMF <NUM> to use by querying a Network Repository Function (NRF), such as NRF <NUM> illustrated in <FIG>. According to some configurations, the SMF <NUM> may access and/or store data that identifies the connected cell-IDs associated with UEs and the corresponding connected UPFs.

As briefly discussed above, using techniques described herein, a UE <NUM> is not limited to using an initially configured mode (e.g., either NR CA or NR DC) in a stand-alone (SA) <NUM> cellular network. For example, a UE <NUM> can be configured to use NR DC during a communication session while the UE <NUM> is near the cell <NUM>, and switch to NR CA when the UE <NUM> moves away from the cell <NUM> and is closer to mid-cell or the cell edge.

As an example, a UE <NUM> can be initially configured to use NR DC or NR CA at registration and/or upon completion of a hand-over procedure. After the initial configuration, the cell <NUM> can monitor power headroom reports (PHRs) received from the UE <NUM>. The cell <NUM> may use data from the PHRs to determine when to switch the UE <NUM> from/to NR DC and/or pass this data to one or more other nodes to determine when to switch the UE <NUM> from/to NR DC.

In some examples, the range of values contained in the PHR is from -<NUM> dB to +<NUM> dB in steps of <NUM> dB. Positive dB values indicate the difference between a maximum UE transmit power for the UE <NUM> and a current UE transmit power of the UE <NUM>. Negative values indicate the difference between the maximum UE transmit power and the calculated UE transmit power. The PHRs can be received by the cell <NUM> (e.g., the gNB(s) connected to the UE) periodically, when the downlink path loss changes by a specific amount, and/or received based on some other parameter(s).

In some configurations, cell <NUM>, or some other device or component, determines if the UE transmission (TX) power indicates that the UE is near the cell <NUM> that represents a near cell condition, or if the UE TX power indicates that the UE <NUM> is farther away from the cell <NUM> and the UE <NUM> is experiencing mid-cell or cell edge conditions.

For instance, if the UE <NUM> is using NR DC, then when the PHR indicates that enough power is left for UE TX power, then the UE <NUM> stays in NR DC mode. Conversely, when the PHR indicates that the UE <NUM> is running out of TX power, then the UE <NUM> can be reconfigured to use NR CA. By switching to/from NR DC, poor performance of the UE <NUM> (e.g., when the UE is near/on the cell edge) can be avoided. Further, by switching to NR CA from NR DC, the UE coverage can be extended using different frequency bands. More details are provided below with regard to <FIG>.

<FIG> is a block diagram of an illustrative environment <NUM> including a <NUM> core network showing switching between NR DC and NR CA. The environment <NUM> illustrates the UE <NUM> switching between NR DC and NR CA depending on network conditions.

According to some configurations, different NFs, such as NFs 120A - 120D, are connected together using a common API which may be referred to herein as a service-based interface (SBI). In some examples, a NF service can directly access other NF services without having to pass through another node. Generally, nodes on the user plane handle the processing of packets between radio access network (RAN) and a data network. The UPFs <NUM> provide functionalities such as access control, encapsulation/decapsulation, bearer lookup, service data flow (SDF) mapping, per-flow Quality of Service (QoS), guaranteed bit rate (GBR), maximum bit rate (MBR), forwarding of packets, packet inspection, and the like. In some examples, a control plane node(s) may select user plane nodes based on location information of the UE and the location of the user plane nodes that may provide a requested service.

Subscriber sessions may be anchored on user plane NFs located either on edge locations or centralized data centers. Because of mobility of subscribers from a first location (e.g., x) to a second location (e.g., y), and/or changing network conditions, there may be a benefit to switch the communication mode used by a UE between NR DC and NR CA.

In some cases, a <NUM> CN <NUM> and the network <NUM> can interact seamlessly via internetwork service discovery. The AMF <NUM> connects to UE <NUM> and a cell <NUM>, that may include one or more gNbs, and manages UE <NUM> related functions. In some examples, access and mobility functions are performed by AMF <NUM>.

As illustrated, the UE <NUM> is initially located at location <NUM> within access network <NUM> and then at some point moves to location <NUM> within access network <NUM>. At location <NUM> that is within area 102a, the UE <NUM> is near cell <NUM> and is within range of the FR2 frequency bands.

As discussed above, the UE <NUM> may initially select which mode to use for communication from NR DC and NR CA. When the UE <NUM> is close to the cell <NUM> as indicated by the area <NUM> within the dashed lines, the UE <NUM> can be configured to use NR DC that can use the FR2 bands for download, and the FR1 bands for upload. When the UE <NUM> is not near cell, as indicated when the UE <NUM> is outside of the area 102A, then the UE <NUM>-<NUM> can be configured to use NR CA.

In some examples, when the UE <NUM> moves from near cell (as indicated when within area 102A) and mid-cell or cell edge as indicated when UE <NUM> is outside of area 102A, the UE <NUM> can be configured to switch modes. As illustrated, when UE <NUM> moves from location <NUM> to location <NUM>, the mode used by the UE <NUM> is switched from NR DC to NR CA.

In some examples, the UE <NUM> monitors network conditions that can be used by cell <NUM>, or some other device or component, to determine when the UE <NUM> is near cell and when the UE <NUM> is mid-cell or near a cell edge. According to some configurations, a gNB connected to the UE <NUM> can monitor PHRs received from the UE <NUM>. The gNb may use data from the PHRs to determine when to switch from/to NR DC and/or pass this data to one or more other nodes to determine when to switch from/to NR DC. In some examples, the switch to NR CA is made before the UE <NUM> runs out of transmission power that is used for the signaling used to switch to NR CA. For instance, the switch to NR CA can be made during a time the PHR indicates that there is enough power headroom to make the switch.

As such, when the PHR indicates that the UE <NUM> is running out of TX power, then the UE can be reconfigured to use NR CA. By switching to/from NR DC, poor performance of the UE (e.g., when the UE is near/on the cell edge) can be avoided. Further, by switching to NR CA from NR DC, the UE <NUM> can use the higher bandwidths available from FR2.

<FIG> is a block diagram illustrating a system <NUM> that includes one or more components for switching between NR DC and NR CA in cellular networks. The system <NUM> includes a terminal <NUM>, which can represent a UE <NUM>, or another computing device, coupled to a server <NUM>, via a network <NUM>. The server <NUM> can represent a computing device, such as one or more of the servers within the access network <NUM>, the <NUM> CN <NUM>, network <NUM>, and/or some other computing device. The network <NUM> can represent network <NUM>, <NUM>, <NUM> and/or access network <NUM>, or some other network.

The network <NUM> can include one or more networks, such as a cellular network <NUM> and a data network <NUM>. The network <NUM> can include one or more core network(s) connected to terminal(s) via one or more access network(s). Example access networks include LTE, WIFI, GSM Enhanced Data Rates for GSM Evolution (EDGE) Radio Access network (GERAN), UTRAN, and other cellular access networks. Message transmission, reception, fallback, and deduplication as described herein can be performed, e.g., via <NUM>, <NUM>, <NUM>, WIFI, or other networks.

The cellular network <NUM> can provide wide-area wireless coverage using a technology such as GSM, Code Division Multiple Access (CDMA), UMTS, LTE, NR, or the like. Example networks include Time Division Multiple Access (TDMA), Evolution-Data Optimized (EVDO), Advanced LTE (LTE+), Generic Access network (GAN), Unlicensed Mobile Access (UMA), Orthogonal Frequency Division Multiple Access (OFDM), GPRS, EDGE, Advanced Mobile Phone System (AMPS), High Speed Packet Access (HSPA), evolved HSPA (HSPA+), VoIP, VoLTE, IEEE <NUM>. 1x protocols, wireless microwave access (WIMAX), WIFI, and/or any future IP-based network technology or evolution of an existing IP-based network technology. Communications between the server <NUM> and terminals such as the terminal <NUM> can additionally or alternatively be performed using other technologies, such as wired (Plain Old Telephone Service, POTS, or PSTN lines), optical (e.g., Synchronous Optical NETwork, SONET) technologies, and the like.

The data network <NUM> can include various types of networks for transmitting and receiving data (e.g., data packets), including networks using technologies such as WIFI, IEEE <NUM>. <NUM> ("BLUETOOTH"), Asynchronous Transfer Mode (ATM), WIMAX, and other network technologies, e.g., configured to transport IP packets. In some examples, the server <NUM> includes or is communicatively connected with an IWF or other device bridging networks, e.g., LTE, <NUM>, and POTS networks. In some examples, the server <NUM> can bridge SS7 traffic from the PSTN into the network <NUM>, e.g., permitting PSTN customers to place calls to cellular customers and vice versa.

In some examples, the cellular network <NUM> and the data network <NUM> can carry voice or data. For example, the data network <NUM> can carry voice traffic using VoIP or other technologies as well as data traffic, or the cellular network <NUM> can carry data packets using HSPA, LTE, or other technologies as well as voice traffic. Some cellular networks <NUM> carry both data and voice in a PS format. For example, many LTE networks carry voice traffic in data packets according to the VoLTE standard. Various examples herein provide origination and termination of, e.g., carrier-grade voice calls on, e.g., networks <NUM> using CS transports or mixed VoLTE/<NUM> transports, or on terminals <NUM> including OEM handsets and non-OEM handsets.

The terminal <NUM> can be or include a wireless phone, a wired phone, a tablet computer, a laptop computer, a wristwatch, or other type of terminal. The terminal <NUM> can include one or more processors <NUM>, e.g., one or more processor devices such as microprocessors, microcontrollers, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), programmable logic devices (PLDs), programmable logic arrays (PLAs), programmable array logic devices (PALs), or digital signal processors (DSPs), and one or more computer readable media (CRM) <NUM>, such as memory (e.g., random access memory (RAM), solid state drives (SSDs), or the like), disk drives (e.g., platter-based hard drives), another type of computer-readable media, or any combination thereof. The CRM or other memory of terminal <NUM> can hold a datastore, e.g., an SQL or NoSQL database, a graph database, a BLOB, or another collection of data. The terminal <NUM> can further include a user interface (UI) <NUM>, e.g., including an electronic display device, a speaker, a vibration unit, a touchscreen, or other devices for presenting information to a user and receiving commands from the user. The terminal <NUM> can further include one or more network interface(s) <NUM> configured to selectively communicate (wired or wirelessly) via the network <NUM>, e.g., via an access network <NUM>.

The CRM <NUM> can be used to store data and to store instructions that are executable by the processors <NUM> to perform various functions as described herein. The CRM <NUM> can store various types of instructions and data, such as an operating system, device drivers, etc. The processor-executable instructions can be executed by the processors <NUM> to perform the various functions described herein.

The CRM <NUM> can be or include computer-readable storage media. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible, non-transitory medium which can be used to store the desired information and which can be accessed by the processors <NUM>. Tangible computer-readable media can include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program components, or other data.

The CRM <NUM> can include processor-executable instructions of an application <NUM>. The CRM <NUM> can store information <NUM> identifying the terminal <NUM>. The information <NUM> can include, e.g., an IMEI, an IMSI identifying the subscriber using terminal <NUM>, or other information discussed above. The CRM <NUM> can additionally or alternatively store credentials (omitted for brevity) used for access, e.g., to IMS or RCS services.

The server <NUM> can include one or more processors <NUM> and one or more CRM <NUM>. The CRM <NUM> can be used to store processor-executable instructions of a selection component <NUM> which may be configured to select between NR DC and NR CA based, at least in part, on one or more network conditions (e.g., TX power) detected by UE <NUM>, a switch component <NUM> which may configured to the selected NR DC/NR CA mode, a network component <NUM> that is configured to perform one or more network operations, as well as one or more other components <NUM>. The processor-executable instructions can be executed by the one or more processors <NUM> to perform various functions described herein.

In some examples, server <NUM> can communicate with (e.g., is communicatively connectable with) terminal <NUM> or other devices via one or more communications interface(s) <NUM>, e.g., network transceivers for wired or wireless networks, or memory interfaces. Example communications interface(s) <NUM> can include ETHERNET or FIBRE CHANNEL transceivers, WIFI radios, or DDR memory-bus controllers (e.g., for DMA transfers to a network card installed in a physical server <NUM>).

In some examples, processor <NUM> and, if required, CRM <NUM>, are referred to for brevity herein as a "control unit. " For example, a control unit can include a CPU or DSP and instructions executable by that CPU or DSP to cause that CPU or DSP to perform functions described herein. Additionally, or alternatively, a control unit can include an ASIC, FPGA, or other logic device(s) wired (physically or via blown fuses or logic-cell configuration data) to perform functions described herein. Other examples of control units can include processor <NUM> and, if required, CRM <NUM>.

<FIG> illustrate example processes. The example processes are illustrated as a logical flow graph, each operation of which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the process.

<FIG> is a flow diagram of an example process that includes switching between NR DC and NR CA, in <NUM> cellular networks. The process includes, at <NUM>, initially selecting to use NR DC or NR CA to use by the UE <NUM> during a communication session. As discussed above, when the UE <NUM> is near cell <NUM> and is within area 102A, then the selected mode can be NR DC. When the UE <NUM> is outside of area 102A and is mid-cell or near the cell edge NR CA can be selected.

At <NUM>, the selected mode is used to establish a session with the UE <NUM>. As discussed above, using techniques described herein, the UE <NUM> may later switch to a different mode (e.g., from NR DC to NR CA, or from NR CA to NR DC).

At <NUM>, one or more network conditions are monitored. As discussed above, in some examples, the network conditions indicate whether the UE <NUM> is near cell, mid-cell, or near a cell edge. In some cases, the UE <NUM> monitors specified network conditions and can provide PHRs to one or more nodes, such as a connected gNB associated with cell <NUM>. According to some configurations, other data may also be used to assist in determining what mode to select. For example, the available bandwidth, current usage statistics, forecasted usage statistics, and/or some other data that may indicate capability of the cell <NUM> to provide service at a desired level to the UE <NUM>.

At <NUM>, the mode can be switched from/to NR DC based on the network conditions. Generally, the mode is switched from NR DC to NR CA when the UE <NUM> moves toward mid-cell or cell edge. See <FIG> and related discussion for more details.

<FIG> is a flow diagram of an example process that includes determining when to switch between NR DC and NR CA, based on network conditions.

The process includes, at <NUM>, receiving network conditions. As discussed above, in some configurations, the UE <NUM> provides PHRs to cell <NUM>, and/or some other component or device, that includes data that indicates when the UE <NUM> is near cell, mid-cell, or near a cell edge. In other examples, the network conditions may be estimated by one or more components of the core network. For example, the cell <NUM> may estimate network conditions for the UE <NUM> based on data received/transmitted to the UE <NUM>.

At <NUM>, a determination is made as to whether to switch modes. As discussed above, the switch may be from NR DC to NR CA, or from NR CA to NR DC. When the network conditions indicate that the UE <NUM> is near cell, the cell <NUM> may determine to switch to NR DC if the mode is currently NR CA. When the UE <NUM> is outside of the near cell area 102a, then the cell <NUM> may determine to switch to NR CA if the mode is currently NR DC. When it is determined to switch, the process <NUM> moves to <NUM> where the mode is switched. When it determined that a switch is not to occur, the process <NUM> returns to <NUM>.

Claim 1:
A system comprising a User Equipment, (UE) and a Network Node, the system further comprising: processors;
a memory; and
one or more components stored in the memory and executable by the processors to perform operations comprising:
selecting (<NUM>) by the User Equipment, UE, (<NUM>) a first mode of a communication session for the User Equipment, UE, (<NUM>) within a <NUM> cellular network, wherein the first mode is selected from a New Radio, NR, Dual Connectivity, DC, mode and a NR Carrier Aggregation, CA, mode;
establishing (<NUM>) the communication session between the UE (<NUM>) and one or more nodes within a cellular network that uses the first mode;
accessing one or more network conditions associated with performance of the UE (<NUM>) within the cellular network, wherein the performance is associated with transmission of data within the cellular network, wherein the one or more network conditions include at least a transmission power of the UE (<NUM>);
determining by the network node to switch the first mode to a second mode based, at least in part, on the one or more network conditions and on forecasted usage statistics of the cellular network, wherein the second mode is one of the NR DC mode or the NR CA mode that is different from the first mode, wherein the determining based, at least in part, on the one or more network conditions and on the forecasted usage statistics further comprises determining an availability of transmission power of the UE (<NUM>);
reconfiguring the UE (<NUM>) to use the second mode; and
using the second mode for communications associated with the UE (<NUM>).