Related Applications

[0001] This application claims the benefit of provisional patent application serial number 63/315,398, filed March 1, 2022, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

[0002] The present disclosure relates to a cellular communications system and more specifically to measurements reports related to dual connectivity in a cellular communications system.

Background

[0003] In Evolved Universal Terrestrial Radio Access (E-UTRA) - New Radio (NR) Dual Connectivity (ENDC) and NR Dual Connectivity (NRDC), there are Bl and A4 measurements, respectively. The Bl and A4 measurements are performed by a User Equipment (UE), helping in relocation of the UE to a stronger neighboring cell. The Bl and A4 measurements are used for NR leg setup on a secondary node (i.e., a secondary gNodeB (sgNB)) in ENDC and NRDC, respectively. In ENDC, a Long Term Evolution (LTE) eNodeB acts as a master node (i.e., a Master eNodeB (MeNB)) and a NR (5 ^th Generation (5G)) gNodeB (gNB) acts as a secondary node (i.e., a sgNB). The Bl measurements for ENDC are triggered when the secondary node (sgNB, NR gNB) has a better signal strength than a threshold. In NRDC, both a master node (Master gNB (MgNB)) and a secondary node (sgNB) are NR gNBs. The A4 measurements for NRDC are triggered when the secondary node (sgNB, NR gNB) becomes better than a given threshold.

[0004] The Bl and A4 measurements are performed based on an indication given to the UE by the master node, via a Radio Resource Control (RRC) Reconfiguration Signal containing a measurement configuration: “MeasConfig” Information Element (IE). The “MeasConfig” IE contains details of a Synchronization Signal Block (SSB) for all secondary cells created by the secondary node (sgNB), and the “MeasConfig” IE comprises “MeasObjectToAddModList.” [0005] Figure 1 illustrates an RRC signal flow for sgNB addition in ENDC and NRDC. As illustrated in steps 102 to 106 of Figure 1, the UE and the master node (MeNB/MgNB) establish an RRC connection. In step 108 of Figure 1, the UE and the master node (MeNB/MgNB) exchange UE capability information. As illustrated in the bold and underlined step 110 of Figure 1, the RRC reconfiguration signal (containing the “MeasConfig” IE) is sent after the UE capability information is exchanged between the master node (MeNB/MgNB) and the UE in step 108 of Figure 1.

[0006] As illustrated in step 112 of Figure 1, after the UE receives the RRC reconfiguration signal from the master node (MeNB/MgNB), the UE transmits B1/A4 measurement reports to the master node (MeNB/MgNB). When the B 1 measurements and the A4 measurements are successful, the master node (which is an Anchor eNB in ENDC or a gNB in NRDC) dispatches

(a) a secondary gNB addition request over X2 towards the secondary node (sgNB) (step 114) and

(b) a new RRC reconfiguration signal with Secondary Cell Group (SCG) reconfiguration with Sync to the UE (step 116). Using the parameters present in the new RRC reconfiguration signal (with SCG reconfiguration with Sync), the UE may perform a random access procedure towards the secondary node (sgNB) (step 122) and eventually starts data traffic on a secondary primary cell (sPCell) of the secondary node (sgNB) (step 124).

Summary

[0007] Systems and methods are disclosed for measurement reporting in accordance with carrier bandwidth information about one or more secondary cells. In one embodiment, a method performed by a User Equipment (UE) communicating with a master node and a secondary node comprises receiving, from the master node, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells and performing one or more measurements in accordance with the measurement configuration information. In this manner, unnecessary measurements and reporting on secondary cells that use a bandwidth that is not supported by the UE can be avoided.

[0008] In one embodiment, the one or more secondary cells are secondary cells in a secondary cell group (SCG) established on the secondary node.

[0009] In one embodiment, the one or more measurements comprise one or more measurements related to dual connectivity. In one embodiment, the one or more measurements comprise Bl measurements and/or A4 measurements.

[0010] In one embodiment, the method further comprises transmitting, to the master node, capability information about one or more capabilities of the UE, the capability information comprising one or more carrier bandwidths supported by the UE.

[0011] In one embodiment, performing the one or more measurements comprises performing one or more measurements on the one or more secondary cells if the carrier bandwidth that is used by the one or more secondary cells is supported by the UE. In one embodiment, performing the measurements comprises refraining from performing measurements on the one or more secondary cells if the carrier bandwidth that is used by the one or more secondary cells is not supported by the UE.

[0012] In one embodiment, performing the one or more measurements comprises performing one or more measurements on one of the one or more secondary cells for which the carrier bandwidth is supported by the UE and refraining from performing one or more measurements on another one of the one or more secondary cells for which the carrier bandwidth is not supported by the UE.

[0013] In one embodiment, the method further comprises transmitting, to the master node, a measurement report based on the one or more measurements.

[0014] In one embodiment, the method further comprises receiving, from the master node, a SCG reconfiguration with Sync. In one embodiment, the method further comprises transmitting, to the master node, a signal indicating that SCG reconfiguration is completed. In one embodiment, the method further comprises transmitting, to the secondary node, a random access request and receiving, from the secondary node, a random access grant. In one embodiment, the method further comprises exchanging data traffic with the secondary node.

[0015] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE is adapted to receive, from a master node, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells and perform one or more measurements in accordance with the measurement configuration information.

[0016] In one embodiment, a UE comprises a communication interface comprising a transmitter and a receiver, and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to receive, from a master node, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells and perform one or more measurements in accordance with the measurement configuration information.

[0017] Embodiments of a method performed by a master node are also disclosed. In one embodiment, a method performed by a master node comprises transmitting, to a UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells and receiving, from the UE, a measurement report based on the measurement configuration information.

[0018] In one embodiment, the one or more secondary cells are secondary cells in a SCG established on a secondary node. [0019] In one embodiment, the method further comprises receiving, from the UE, capability information about one or more capabilities of the UE, the capability information comprising one or more carrier bandwidths supported by the UE.

[0020] In one embodiment, the method further comprises transmitting, to the UE (300), a SCG reconfiguration with Sync. In one embodiment, the method further comprises receiving, from the UE, a signal indicating that SCG reconfiguration is completed.

[0021] Corresponding embodiments of a master node are also disclosed. In one embodiment, a master node is adapted to transmit, to a UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells and receive, from the UE, a measurement report based on the measurement configuration information.

[0022] In one embodiment, a master node comprises processing circuitry configured to cause the master node to transmit, to a UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells and receive, from the UE, a measurement report based on the measurement configuration information.

[0023] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0024] Figure 1 illustrates a Radio Resource Control (RRC) signal flow for secondary gNodeB (sgNB) addition in Evolved Universal Terrestrial Radio Access (EUTRA) New Radio (NR) Dual Connectivity (ENDC) and NR Dual Connectivity (NRDC);

[0025] Figure 2 illustrates an example embodiment of a carrier bandwidth Information Element (IE), in accordance with an embodiment of the present disclosure;

[0026] Figure 3 illustrates the operation of a User Equipment (UE), a master node, and a secondary node, in accordance with an embodiment of the present disclosure;

[0027] Figure 4 shows an example of a communication system in accordance with some embodiments;

[0028] Figure 5 shows a UE in accordance with some embodiments;

[0029] Figure 6 shows a network node in accordance with some embodiments;

[0030] Figure 7 is a block diagram of a host, which may be an embodiment of the host of

Figure 4, in accordance with various aspects described herein; [0031] Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

[0032] Figure 9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

Detailed Description

[0033] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0034] There currently exist certain challenge(s). When performing the B1/A4 measurements, User Equipments (UEs) do not have any idea about a bandwidth supported by secondary cells in the Secondary Cell Group (SCG). All UEs with different power classes do not support all bandwidths or bandwidth combinations. Considering the above two criteria (i.e., the bandwidth supported by the secondary cells in SCG and all bandwidths/bandwidth combinations), there are multiple occasions where the UE performs scanning and a measurement on Synchronization Signal Blocks (SSBs) of the secondary cells in SCG, even though there is a mismatch of bandwidths (or bandwidth combinations) between the UE and the secondary cells. Due to the mismatch, the UE may spend power and perform the scanning of these SSBs for the B1/A4 measurements. This scenario results in unnecessary measurements and extra signaling over Radio Resource Control (RRC) between the UE and the network node (e.g., the master node (e.g., the Master evolved NodeB (MeNB) / Master gNodeB (MgNB)) and/or the secondary node (e.g., Secondary gNodeB (sgNB))).

[0035] Once the measurement report is received at the master node (MeNB/MgNB) (step 112 of Figure 1), a X2 signal is dispatched towards the secondary node (sgNB) for sgNB addition request (step 114). As there is a mismatch of the bandwidth support described above, there will be a rejection of the sgNB addition request. If there is a mechanism to screen the UE at the master node (MeNB/MgNB) for the supported bandwidth, there will be no rejection of the sgNB addition request, which is desirable. But the UE may keep measuring the SSBs on the secondary cell and send out the B1/A4 measurement reports to the master node (MeNB/MgNB), which may unnecessarily waste the UE’s battery power. [0036] The UE may stop sending out the B1/A4 measurement reports only when a signal of “RRC reconfiguration with SCGreconfiguration with sync” is sent from the master node (MeNB/MgNB) to the UE, as illustrated in step 116 of Figure 1, after there is successful sgNB addition request acknowledgement (step 114 of Figure 1). This problem can be overwhelming in the future when all the UEs (or devices) of different power classes coexist in networks with different bandwidth supports.

[0037] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein in which carrier bandwidth information for one or more secondary cells is included with measurement configuration information provided to and received by a UE. The UE may then utilize this carrier bandwidth information such that measurements are performed by the UE and reported by the UE for only those secondary cells having bandwidths that are supported by the UE.

[0038] In one embodiment, a new Information Element (IE), referred to herein by the nonlimiting name carrier bandwidth information (“carrierBandwidth”), for all the secondary cells within the Secondary Cell Group (SCG) (established by the secondary node (sgNB)) are added to “measObjectToAddModList” under “measConfig” IE carried in an RRC signal, such as the RRC reconfiguration signal in step 110 of Figure 1, as shown in Figure 2. The new IE (carrier bandwidth information) may be a part of the RRC reconfiguration signal, which is sent out from the master node (MeNB/MgNB) (step 110 of Figure 1) after the UE capability information is exchanged (step 108 of Figure 1).

[0039] It is redundant to include the carrier bandwidth information (“carrierBandwidth”) in any of the previous signals (for example, the signals in steps 100 to 108 of Figure 1) because the network (e.g., the master node (MeNB/MgNB)) is unaware of UE Radio Access Technology (RAT) capability until the network receives UE capability information from the UE.

[0040] Bandwidths for Frequency Range 1 (FR1) and Frequency Range 2 (FR2) in 5 ^th Generation (5G) can vary from 5 Megahertz (MHz) to 400 MHz. So, as shown in Figure 2, the present disclosure proposes to have, for example, 12 bits long (as 400 MHz requires 9 bits) for the carrier bandwidth information (“carrierBandwidth”), which is a new field under “measConfig” IE. The carrier bandwidth information (“carrierBandwidth”) in bits or any form (e.g., representation in decimals and so on) may be included under “measConfig” IE.

[0041] Certain embodiments may provide one or more of the following technical advantage(s). First, solutions proposed by the present disclosure reduce unnecessary scanning and measurements of SSB signals for the B1/A4 measurement reports for bandwidths that are not supported by the UE. Also, such reduction of the scanning and the measurements of SSB signals reduces unnecessary processing on the UE. Second, solutions proposed by the present disclosure reduce unnecessary measurement report signaling, which, in-tum, results in unnecessary X2 signaling. Third, in accordance with solutions of the present disclosure, as the carrier bandwidth information is included in common parts of the RRC reconfiguration signal, which are found in release 15 and later releases of 3 ^rd Generation Partnership Project (3GPP), many of legacy UEs in those releases of 3 GPP should be able to read out the carrier bandwidth information included in the common parts of RRC IE.

[0042] Figure 3 illustrates steps of the embodiments disclosed in the present disclosure. Optional steps are represented by dashed lines. As illustrated, the process involves a UE 300, a master node 302, and a secondary node 304. The master node 302 is, e.g., a MeNB or MgNB, and the secondary node 304 is a sgNB, in this example.

[0043] In step 306, optionally, the UE 300 transmits the UE’s capability information including a bandwidth(s) that the UE can support.

[0044] In step 308, the UE receives, from the master node 302, a RRC reconfiguration signal with measurement configuration information including information (“carrier bandwidth information”) on a carrier bandwidth that is used by a secondary cell(s) within a SCG established on the secondary node 304. In one embodiment, the carrier bandwidth information indicates a carrier bandwidth used for all secondary cells established on the secondary node 304. For example, the RRC reconfiguration signal comprises “measConfig” Information Element (IE) that includes information on a carrier bandwidth. Figure 2 shows that a field “carrierBandwidth” (in the “measConfig” IE) carries the carrier bandwidth information on a carrier bandwidth that is used by all secondary cells in a SCG established on the secondary node 304. For example, if the secondary cell(s) in the SCG established on the secondary node 304 uses a bandwidth of 400 MHz, which requires 9 bits to present the bandwidth, the field “carrierBandwidth” can be 9 bit or longer, such as 12 bits as shown in Figure 2. In one embodiment, the field “carrierBandwidth” can be any decimal number or any form.

[0045] In step 310A, the UE 300 performs B1/A4 measurements based on the measurement configuration information and transmits B 1/A4 measurement reports to the master node 302. In one embodiment, the UE 300 performs B1/A4 measurements on secondary cell(s) having a carrier bandwidth that is supported by the UE 300 and refrains from performing B1/A4 measurements on secondary cell(s) having a carrier bandwidth that is not supported by the UE 300. Thus, in step 310B, the UE 300 reports B 1/A4 measurements only for those secondary cell(s) having a carrier bandwidth that is supported by the UE 300. [0046] In step 312, optionally, the UE 300 receives, from the master node 302, an RRC reconfiguration signal with SCG reconfiguration with Sync.

[0047] In step 314, optionally, the UE 300 transmits, to the master node 302, a signal indicating that RRC reconfiguration is completed.

[0048] In step 316, optionally, the UE 300 transmits, to the secondary node 304, a random access request and receives, from the secondary node 304, a random access grant.

[0049] In step 318, optionally, the UE 300 exchanges data traffic with the secondary node 304.

[0050] Because the information on the particular carrier bandwidth used by the secondary cell(s) is transmitted to the UE 300 (as shown in step 308 of Figure 3), the UE 300 does not waste its power in screening and performing the B1/A4 measurements in bandwidths not used by the secondary node 304.

[0051] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.

[0052] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a Radio Access Network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410A and 410B (one or more of which may be generally referred to as network nodes 410), or any other similar Third Generation Partnership Project (3 GPP) access node or non-3GPP Access Point (AP). The network nodes 410 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections. The UEs in Figure 1 and Figure 3 may correspond to the UEs 412. The master nodes (MeNB/MgNB) and the secondary nodes (SgNB) may correspond to the network nodes 410.

[0053] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 400 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0054] The UEs 412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 410 and other communication devices. Similarly, the network nodes 410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 412 and/or with other network nodes or equipment in the telecommunication network 402 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 402.

[0055] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 406 includes one more core network nodes (e.g., core network node 408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

[0056] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and/or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0057] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 400 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0058] In some examples, the telecommunication network 402 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunication network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunication network 402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and/or massive Machine Type Communication (mMTC)/massive Internet of Things (loT) services to yet further UEs.

[0059] In some examples, the UEs 412 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi -standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. be configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0060] In the example, a hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and/or 412D) and network nodes (e.g., network node 410B). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 410, or by executable code, script, process, or other instructions in the hub 414. As another example, the hub 414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 414 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0061] The hub 414 may have a constant/persistent or intermittent connection to the network node 410B. The hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412C and/or 412D), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 404 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 410B. In other embodiments, the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 410B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0062] Figure 5 shows a UE 500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0063] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).

Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0064] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input/output interface 506, a power source 508, memory 510, a communication interface 512, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 5. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0065] The processing circuitry 502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 510. The processing circuitry 502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 502 may include multiple Central Processing Units (CPUs).

[0066] In the example, the input/output interface 506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 500. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0067] In some embodiments, the power source 508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 508 may further include power circuitry for delivering power from the power source 508 itself, and/or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.

[0068] The memory 510 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.

[0069] The memory 510 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 510 may allow the UE 500 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 510, which may be or comprise a device-readable storage medium. [0070] The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 518 and/or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., the antenna 522) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0071] In the illustrated embodiment, communication functions of the communication interface 512 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0072] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 512, or via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0073] As another example, a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0074] A UE, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 500 shown in Figure 5.

[0075] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

[0076] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators. [0077] Figure 6 shows a network node 600 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0078] BSs may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto BSs, pico BSs, micro BSs, or macro BSs. A BS may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio BS may also be referred to as nodes in a Distributed Antenna System (DAS).

[0079] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi -Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

[0080] The network node 600 includes processing circuitry 602, memory 604, a communication interface 606, and a power source 608. The network node 600 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, each unique Node B and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 600 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., an antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 600.

[0081] The processing circuitry 602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node 600 components, such as the memory 604, to provide network node 600 functionality.

[0082] In some embodiments, the processing circuitry 602 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of Radio Frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the RF transceiver circuitry 612 and the baseband processing circuitry 614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 612 and the baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0083] The memory 604 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 602. The memory 604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and/or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and the memory 604 are integrated.

[0084] The communication interface 606 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 606 comprises port(s)/terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. The radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 may be configured to condition signals communicated between the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 620 and/or the amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface 606 may comprise different components and/or different combinations of components.

[0085] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618; instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes the one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612 as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

[0086] The antenna 610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 610 may be coupled to the radio front-end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 610 is separate from the network node 600 and connectable to the network node 600 through an interface or port.

[0087] The antenna 610, the communication interface 606, and/or the processing circuitry 602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 600. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 610, the communication interface 606, and/or the processing circuitry 602 may be configured to perform any transmitting operations described herein as being performed by the network node 600. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment. [0088] The power source 608 provides power to the various components of the network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 608. As a further example, the power source 608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0089] Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.

[0090] Figure 7 is a block diagram of a host 700, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein. As used herein, the host 700 may be or comprise various combinations of hardware and/or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 700 may provide one or more services to one or more UEs.

[0091] The host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a network interface 708, a power source 710, and memory 712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of the host 700.

[0092] The memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g., data generated by a UE for the host 700 or data generated by the host 700 for a UE. Embodiments of the host 700 may utilize only a subset or all of the components shown. The host application programs 714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 700 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.

[0093] Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0094] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

[0095] Hardware 804 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 808A and 808B (one or more of which may be generally referred to as VMs 808), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808.

[0096] The VMs 808 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of the VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.

[0097] In the context of NFV, a VM 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of the hardware 804 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 808, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802.

[0098] The hardware 804 may be implemented in a standalone network node with generic or specific components. The hardware 804 may implement some functions via virtualization.

Alternatively, the hardware 804 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of the applications 802. In some embodiments, the hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a BS. In some embodiments, some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.

[0099] Figure 9 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 412A of Figure 4 and/or the UE 500 of Figure 5), the network node (such as the network node 410A of Figure 4 and/or the network node 600 of Figure 6), and the host (such as the host 416 of Figure 4 and/or the host 700 of Figure 7) discussed in the preceding paragraphs will now be described with reference to Figure 9.

[0100] Like the host 700, embodiments of the host 902 include hardware, such as a communication interface, processing circuitry, and memory. The host 902 also includes software, which is stored in or is accessible by the host 902 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 906 connecting via an OTT connection 950 extending between the UE 906 and the host 902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 950.

[0101] The network node 904 includes hardware enabling it to communicate with the host 902 and the UE 906 via a connection 960. The connection 960 may be direct or pass through a core network (like the core network 406 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0102] The UE 906 includes hardware and software, which is stored in or accessible by the UE 906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 906 with the support of the host 902. In the host 902, an executing host application may communicate with the executing client application via the OTT connection 950 terminating at the UE 906 and the host 902. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 950 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 950. [0103] The OTT connection 950 may extend via the connection 960 between the host 902 and the network node 904 and via a wireless connection 970 between the network node 904 and the UE 906 to provide the connection between the host 902 and the UE 906. The connection 960 and the wireless connection 970, over which the OTT connection 950 may be provided, have been drawn abstractly to illustrate the communication between the host 902 and the UE 906 via the network node 904, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0104] As an example of transmitting data via the OTT connection 950, in step 908, the host 902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 906. In other embodiments, the user data is associated with a UE 906 that shares data with the host 902 without explicit human interaction. In step 910, the host 902 initiates a transmission carrying the user data towards the UE 906. The host 902 may initiate the transmission responsive to a request transmitted by the UE 906. The request may be caused by human interaction with the UE 906 or by operation of the client application executing on the UE 906. The transmission may pass via the network node 904 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 912, the network node 904 transmits to the UE 906 the user data that was carried in the transmission that the host 902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 914, the UE 906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 906 associated with the host application executed by the host 902.

[0105] In some examples, the UE 906 executes a client application which provides user data to the host 902. The user data may be provided in reaction or response to the data received from the host 902. Accordingly, in step 916, the UE 906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 906. Regardless of the specific manner in which the user data was provided, the UE 906 initiates, in step 918, transmission of the user data towards the host 902 via the network node 904. In step 920, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 904 receives user data from the UE 906 and initiates transmission of the received user data towards the host 902. In step 922, the host 902 receives the user data carried in the transmission initiated by the UE 906.

[0106] One or more of the various embodiments improve the performance of OTT services provided to the UE 906 using the OTT connection 950, in which the wireless connection 970 forms the last segment.

[0107] In an example scenario, factory status information may be collected and analyzed by the host 902. As another example, the host 902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 902 may store surveillance video uploaded by a UE. As another example, the host 902 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs. As other examples, the host 902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and/or transmitting data.

[0108] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 950 between the host 902 and the UE 906 in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 950 may be implemented in software and hardware of the host 902 and/or the UE 906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 950 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 902. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 950 while monitoring propagation times, errors, etc.

[0109] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0110] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionalities may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.

[oni] Some example embodiments of the present disclosure are as follows:

[0112] Embodiment 1 : A method performed by a User Equipment, UE, communicating with a master node and a secondary node, the method comprising: receiving (308), from the master node, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells; and performing (310A), measurements in accordance with the measurement configuration information.

[0113] Embodiment 2: The method of embodiment 1, wherein the one or more secondary cells are all secondary cells in a secondary cell group, SCG, established on a secondary node. [0114] Embodiment 3 : The method of embodiment 1 or 2, wherein the measurements comprise Bl measurements and/or A4 measurements.

[0115] Embodiment 4: The method of any of embodiments 1 to 3 further comprising transmitting (306), to the master node, capability information about one or more capabilities of the UE, the capability information comprising one or more carrier bandwidths supported by the UE. [0116] Embodiment 5: The method of any of embodiments 1 to 4, wherein performing (310A) the measurements comprises performing (310A) measurements on the one or more secondary cells if the carrier bandwidth that is used by the one or more secondary cells is supported by the UE.

[0117] Embodiment 6: The method of embodiment 5, wherein performing (310A) the measurements comprises refraining from performing (310A) measurements on the one or more secondary cells if the carrier bandwidth that is used by the one or more secondary cells is not supported by the UE.

[0118] Embodiment 7: The method of any of embodiments 1 to 6 further comprising transmitting (310B), to the master node, a measurement report based on the measurements.

[0119] Embodiment 8: The method of any of embodiments 1 to 7 further comprising receiving (312), from the master node, a Secondary Cell Group, SCG, reconfiguration with Sync. [0120] Embodiment 9: The method of embodiment 8 further comprising transmitting (314), to the master node, a signal indicating that SCG reconfiguration is completed.

[0121] Embodiment 10: The method of embodiment 9 further comprising transmitting (316), to the secondary node, a random access request and receiving, from the secondary node, a random access grant.

[0122] Embodiment 11 : The method of embodiment 10 further comprising exchanging (318) data traffic with the secondary node.

[0123] Embodiment 12: A User Equipment, UE, adapted to: receive (308), from the master node, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells; and perform (310A), measurements in accordance with the measurement configuration information.

[0124] Embodiment 13 : The UE of embodiment 12, wherein the UE is further adapted to perform the method of any of embodiments 2 to 11.

[0125] Embodiment 14: A User Equipment, UE comprising: one or more transmitters; one or more receivers; and processing circuitry associated with the one or more transmitters and the one or more receivers, the processing circuitry configured to cause the UE to receive (308), from the master node, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells and perform (310A), measurements in accordance with the measurement configuration information.

[0126] Embodiment 15: The UE of embodiment 14, wherein the processing circuitry is further configured to cause the UE to perform the method of any of embodiments 2 to 11. [0127] Embodiment 16: A method performed by a master node, communicating with a User Equipment, UE, and a secondary node, the method comprising: transmitting (308), to the UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells; and receiving (310B), from the UE, a measurement report based on the measurement configuration information.

[0128] Embodiment 17: The method of embodiment 16, wherein the one or more secondary cells are all secondary cells in a secondary cell group, SCG, established on a secondary node.

[0129] Embodiment 18: The method of embodiment 16 or 17 further comprising receiving (306), from the UE, capability information about one or more capabilities of the UE, the capability information comprising one or more carrier bandwidths supported by the UE.

[0130] Embodiment 19: The method of any of embodiments 16 to 18 further comprising transmitting (312), to the UE, a Secondary Cell Group, SCG, reconfiguration with Sync.

[0131] Embodiment 20: The method of embodiment 19 further comprising receiving (314), from the UE, a signal indicating that SCG reconfiguration is completed.

[0132] Embodiment 21 : A master node adapted to: transmit (308), to a User Equipment, UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells; and receive (310B), from the UE, a measurement report based on the measurement configuration information.

[0133] Embodiment 22: The master node of embodiment 21, wherein the master node is further adapted to perform the method of any of embodiments 17 to 20.

[0134] Embodiment 23 : A master node comprising processing circuitry configured to cause the master node to: transmit (308), to a User Equipment, UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells; and receive (310B), from the UE, a measurement report based on the measurement configuration information.

[0135] Embodiment 24: The master node of embodiment 23, wherein the processing circuitry is further configured to cause the master node to perform the method of any of embodiments 17 to 20.

[0136] Embodiment 25: A method implemented in a host configured to operate in a communication system that further includes a master node and a User Equipment, UE, the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the master node, wherein the master node performs the steps of transmitting (308), to a UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells, receiving (310B), from the UE, a measurement report based on the measurement configuration information, and transmitting, to the UE, the user data based on the receiving measurement information.

[0137] Embodiment 26: The method of embodiment 25, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0138] Embodiment 27: A host configured to operate in a communication system to provide an over-the-top, OTT, service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a master node in a cellular network for transmission to a User Equipment, UE, the master node having a communication interface and processing circuitry, the processing circuitry of the master node configured to transmit (308), to a UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells, receive (310B), from the UE, a measurement report based on the measurement configuration information, and transmit, to the UE, user data based on the receiving measurement information.

[0139] Embodiment 28: The host of embodiment 27, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0140] Embodiment 29: A communication system configured to provide an over-the-top, OTT, service, the communication system comprising a host comprising: processing circuitry configured to provide user data for a User Equipment, UE, the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular master node for transmission to the UE, the master node having a communication interface and processing circuitry, the processing circuitry of the master node configured to transmit (308), to a UE, measurement configuration information comprising information on a carrier bandwidth that is used by one or more secondary cells, receive (310B), from the UE, a measurement report based on the measurement configuration information, and transmit, to the UE, user data based on the receiving measurement information.

[0141] Embodiment 30: The communication system of the previous embodiment, further comprising: the master node; and/or the user equipment.

[0142] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.