Methods and apparatuses for UE-assisted carrier activation and deactivation

Abstract

A method, system and apparatus are disclosed. A method in a network node configured to communicate with a wireless device (WD) is described. The method includes receiving a user assisted session information element and / or a user assisted traffic information control element and performing one or more actions based on the user assisted session information element and / or the user assisted traffic information control element.

Description

[0001] METHODS AND APPARATUSES FOR UE-ASSISTED CARRIER ACTIVATION AND DEACTIVATION

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to wireless device assisted carrier activation and deactivation.

[0004] INTRODUCTION

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes (NNs) and between WDs. The 3 GPP is also developing standards for Sixth Generation (6G) wireless communication networks. In some cases, the term user equipment (UE) is used and may refer to WD.

[0006] Most WD Radio Resource Control (RRC) sessions have a short data transfer of limited volume, e.g., typically, a few Hypertext Transfer Protocol (HTTP) requests. Only a very small fraction (e.g., 1%) of the sessions contribute to most of the volume. Even for sessions with large volume transfers, it may not be a continuous full buffer data transfer and often comes in bursts interspersed with periods of very little activity.

[0007] While carrier aggregation can enable higher throughput, nevertheless, it comes at a larger WD power consumption considering that the WD has to perform regular radio operations, e.g., Physical Downlink Control Channel (PDCCH) monitoring, Channel State Information (CSI) measurement and reporting, Sounding Reference Signal (SRS) transmission and so on over one or more additional carriers instead of just one primary carrier. Hence, WDs are typically configured to maximize battery charge, the number of activated secondary cells (SCells) in a carrier aggregation configuration is minimized, and S-cells are only activated as needed. Conventional User-Assistance-Information (UAI) RRC messages (e.g., as described in 3GPP TS 38.311) allow the WD to indicate its preference for maximum bandwidth, maximum number of SCells, Multiple Input Multiple Output (MIMO), etc., in an effort to limit impact on WD battery drain. However, the WD informs the network node of its preference on the maximum aggregated bandwidth for power saving, or its preference on the maximum number of secondary component carriers for power saving. This is mostly to set an upper limit from which the WD can signal to the network to reduce the carrying capacity.

[0008] FIG. 1 shows an example process where assistance information (e.g., UAI) is provided by the WD, e.g., UE. The purpose of this procedure is for the WD to inform the network of:

[0009] • its delay budget report carrying desired increm ent / decrem ent in the connected mode Discontinuous Reception (DRX) cycle length, or;

[0010] • its overheating assistance information, or;

[0011] • its IDC assistance information, or;

[0012] • its preference on DRX parameters for power saving, or;

[0013] • its preference on the maximum aggregated bandwidth for power saving, or;

[0014] • its preference on the maximum number of secondary component carriers for power saving, or;

[0015] • its preference on the maximum number of MIMO layers for power saving, or;

[0016] • its preference on the minimum scheduling offset for cross-slot scheduling for power saving, or;

[0017] • assistance information to transition out of RRC CONNECTED state when the UE does not expect to send or receive data in the near future;

[0018] The WD may provide the network node with the following granularity of the information elements.

[0019] MaxBW-Preference-rl6 ::= SEQUENCE { reducedMaxB W -FR 1 -r 16 SEQUENCE { reducedBW-FRl-DL-rl6 ReducedAggregatedBandwidth reducedBW-FRl-UL-rl6 ReducedAggregatedBandwidth } OPTIONAL, reducedMaxB W -FR2-r 16 SEQUENCE { reducedBW-FR2-DL-r 16 ReducedAggregatedBandwidth reducedBW-FR2-UL-r 16 ReducedAggregatedBandwidth } OPTIONAL

[0020] }

[0021] MaxCC-Preference-rl6 ::= SEQUENCE { reducedCC sDL-r 16 INTEGER (0 .31), reducedCC sUL-r 16 INTEGER (0 .31) }

[0022] ReducedAggregatedBandwidth ::= ENUMERATED {mhzO, mhzlO, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhzlOO, mhz200, mhz300, mhz400} MaxBW-PreferenceConfig-rl6 ::= SEQUENCE { maxBW-PreferenceProhibitTimer-rl6 ENUMERATED { sO, sOdot5, si, s2, s3, s4, s5, s6, s7, s8, s9, slO, s20, s30, spare2, sparel } }

[0023] MaxCC-PreferenceConfig-rl6 : := SEQUENCE { maxCC-PreferenceProhibitTimer-rl6 ENUMERATED { sO, sOdot5, si, s2, s3, s4, s5, s6, s7, s8, s9, slO, s20, s30, spare2, sparel }

[0024] Detection of an increase in traffic pattern followed by the SCell activation procedure can take some appreciable time as the network node first detects the increase in traffic, informs the WD to activate SCells, then starts channel quality measurements on the SCell, and report these to the network before the network can send data to the WD on the SCells. Often, by the time SCells are activated, much of the data burst may have already been served by the other active carriers (including the Primary Cell (PCell)).

[0025] Additionally, the signaling overhead associated with UAI is too large (e.g., exceeds a predetermined threshold), and the associated procedure is slow to allow for adjusting of network carrying capacity, e.g., in relation to the frequency of traffic pattern change.

[0026] Attempts have been made (e.g., such as in 3GPP in TS 38.321) to define a new Medium Access Control (MAC) Control Element (CE), i.e., “Recommended bit rate MAC CE” for signaling intelligence between the WD and the NN for fast decisions related to throughput needs.

[0027] However, in most cases, when in idle mode, WDs initiate an air interface connection (RACH) because of a need to communicate (transfer data). There is currently no mechanism to indicate to the NN (upon RRC ConnectionSetup / Reconfiguration) any information about the characteristics of an impending data transfer, even though the WD might have knowledge that would be useful to the network node in assigning the right resources. A similar problem exists in connected mode as well, during the lifetime of a session. Due to the need to save WD power, the network node attempts to keep active only as many carriers as needed. Even though UAI message could, in one option, be extended to allow UE to indicate that it anticipates higher data rate and would like more SCells activated, it would still not be efficient enough. RRC messaging is a rather slow process. Especially in a Centralized Unit (CU) Distributed Unit (DU) split architecture, the RRC messages need to be decoded by CU-CP layer before information can be conveyed to the DU-CP and lower MAC scheduler layers. This may add an additional time (e.g., milliseconds) before the information is known at the MAC layers.

[0028] Even if the UAI messages are extended, the granularity of the existing information elements provided by the WD is too poor as the WD cannot specify which of the carriers are preferable to (de-)activate.

[0029] In contrast to LTE, where SCell activation is in the order of 20 ms, in NR the SCell activation time is significantly longer (60+ ms) and depends on multiple variables, e.g., as described in 3GPP TS 38.133 (V17.11.0), section 8.3.

[0030] Further, given the short nature of many data bursts, early SCell activation becomes very important in being able to utilize more carriers when needed. However, these carriers are deactivated when not needed to save WD battery charge. Without a method to activate SCells early, deploying NR carrier aggregation becomes a compromise between throughput (keeping SCells active) and WD power savings (deactivating SCells to save UE power). In addition, the recommended bit rate MAC CE is too limiting as defined, as it was meant mostly for one use case (codecs)

[0031] SUMMARY

[0032] Some embodiments advantageously provide methods, systems, and apparatuses for WD assisted carrier activation and deactivation such as UE-assisted carrier activation and deactivation.

[0033] Depending on the WD implementation (Radio Frequency (RF) architecture), from energy consumption point of view, it may be important to know which of the secondary carriers are activated by the network node rather than only how many. These secondary carriers may be implemented in different transceivers independently power managed. The WD could potentially switch off transceivers / processing chains associated to the carriers when not in use. Hence, for the very same number of component carriers, different power consumption levels may be used at the WDs, depending on which component carriers the network node activates. However, there is currently no mechanism for the WD to inform the network node about such characteristics (which carrier), rather only the amount. Furthermore, different carriers may potentially be deployed with different bandwidths and depending on the traffic needs, the WD may prefer one secondary cell over another rather than just indicating a number of carriers.

[0034] In some embodiments, the WD may be in a better position than the network node to know what end-user applications are running on the WD and potentially what data transfer requirements are associated with such applications. In some other embodiments, the WD determines ( e.g., can judge and anticipate) any desired transfer rate and make decisions on tradeoff between saving battery life or expressing interest to network of activating more or other SCells for faster and quicker data transfer, as well as better utilization of WD hardware and energy resources.

[0035] In some embodiments, for the initial connection, a new optional RRC Information Element (IE) is introduced, e.g., in the RRCConnectionReconfiguration signal to provide to the network key knowledge that the WD has about the characteristics of an impending data transfer, change in location since the last RRC Connected mode as well as known / unknown status of air interface resources (e.g.., SCells).

[0036] In some other embodiments, it is also proposed to introduce a new uplink (UL) MAC Control Element (UL MAC CE) to allow for the WD to refine / update information about data transfer needs. If the WD is aware of the application demands at WD level, as well as hardware resources and has intimate knowledge about the RF configuration of various configured cells in a serving set, the WD may indicate a preference to network node to allocate resources such as the right and the appropriate amount of air interface resources (e.g. choose appropriate carriers) in a timely fashion.

[0037] One or more embodiments are beneficial at last because the network scheduler may react faster (than conventional schedulers) in activating additional carriers for anticipated data burst and deactivating when the extra capacity is not needed. Faster time-to-data (faster traffic down- / uploads), WD battery power savings, and better network resource utilization may be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0039] FIG. 1 shows an example of assistance information provided by the WD;

[0040] FIG. 2 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0041] FIG. 3 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

[0042] FIG. 4 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

[0043] FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

[0044] FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

[0045] FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

[0046] FIG. 8 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure; and

[0047] FIG. 9 is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0048] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to WD assisted carrier activation and deactivation. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0049] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0050] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0051] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0052] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0053] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and / or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0054] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0055] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0056] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0057] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0058] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0059] Also, it is contemplated that a WD 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN. The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0060] The communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and / or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0061] A network node 16 is configured to include a NN management unit 32 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., NN functions. A wireless device 22 is configured to include a WD management unit 34 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., WD functions.

[0062] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0063] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

[0064] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54 configured to enable the service provider to observe / monitor / control / transmit to / receive from the network node 16 and or the wireless device 22.

[0065] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0066] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0067] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include a NN management unit 32 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., NN functions.

[0068] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0069] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0070] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0071] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a WD management unit 34 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., WD functions.

[0072] In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.

[0073] In FIG. 4, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0074] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0075] In some embodiments, 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 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0076] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the WD 22.

[0077] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and / or comprises a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the network node 16.

[0078] Although FIGS. 2 and 3 show various “units” such as NN management unit 32, and WD management unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0079] FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 3. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

[0080] FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

[0081] FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0082] FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

[0083] FIG. 8 is a flowchart of an exemplary process in a network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the NN management unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60 is configured to receive (Block SI 34) a user assisted session information element and / or a user assisted traffic information control element and perform (Block S136) one or more actions based on the user assisted session information element and / or the user assisted traffic information control element.

[0084] In some embodiments, one or more of: (A) the method further includes receiving a connection reconfiguration message including the user assisted session information element; (B) the user assisted session information element includes description of an initial burst, an indication of whether a location is stationary since a last connected state, and / or information about each serving cell configured; and (C) the one or more actions include network node preparing an amount of network resources ahead of time for an upcoming burst, transitioning through an activation procedure, and / or making assumptions about a radio frequency link.

[0085] In some other embodiments, the user assisted traffic information control element includes and / or indicates one or more of: (A) an imminent change in burst intensity; (B) information about which secondary cells the WD 22 is to activate and / or deactivate; (C) the WD 22 prefers a different bandwidth on a same or another carrier; and (D) the WD 22 prefers a more or less stringent time-domain configuration.

[0086] FIG. 9 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the WD management unit 34), processor 86, radio interface 82 and / or communication interface 60. Wireless device 22 such as via processing circuitry 84 and / or processor 86 and / or radio interface 82 is configured to transmit (Block S138) a user assisted session information element and / or a user assisted traffic information control element and perform (Block S140) ne or more actions based on the user assisted session information element and / or the user assisted traffic information control element.

[0087] In some embodiments, one or more of: (A) the method further includes transmitting a connection reconfiguration message including the user assisted session information element; (B) the user assisted session information element includes description of an initial burst, an indication of whether a location is stationary since a last connected state, and / or information about each serving cell configured; and (C) at least the user assisted session information element triggers the network node to prepare an amount of network resources ahead of time for an upcoming burst, transition through an activation procedure, and / or make assumptions about a radio frequency link.

[0088] In some other embodiments, the user assisted traffic information control element includes and / or indicates one or more of: (A) an imminent change in burst intensity; (B) information about which secondary cells the WD 22 is to activate and / or deactivate; (C) the WD 22 prefers a different bandwidth on a same or another carrier; and (D) the WD 22 prefers a more or less stringent time-domain configuration.

[0089] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for WD, e.g., UE, assisted carrier activation and deactivation.

[0090] Typically, data transfers are initiated by WD 22. The WD 22 may have information about the characteristics of an impending data transfer as well as other knowledge that would be useful to the NN 16 in assigning resources, e.g., whether the WD 22 was stationary since the last RRC Connected state, whether cells in the serving set have known RF characteristics, etc. Further, information about serving cells (e.g. recently synchronized signal block (SSB)) may be useful to NN 16 to allow for faster time-to-data and potentially higher transfer rate.

[0091] Some embodiments provide the creation of an RRC IE, i.e., “ User-Assisted Session Information IE” included in a RRCConnectionReconfiguration message (between WD 22 and NN 16)

[0092] List of fields of the RRC IE may include one or more of (but not limited to):

[0093] • Description of the Initial Burst: o Estimated Data burst size in Kbytes; o Expected data direction (UL / DL);

[0094] • “Location Stationary since last RRCConnected state”: Boolean; and / or

[0095] • Known Information about each serving cell configured (RRC known / unknown), if location was stationary, include last reported CSI Report.

[0096] The description of the initial burst allows the NN 16 to prepare an amount of network resources ahead of time for the upcoming burst, e.g., allowing for more efficient communication as compared to conventional system in which the WD 22. In conventional system, the WD 22 first establishes its connection, the NN 16 realizes the demands after some time, and (re-)configures the WD 22 with additional resources. In some other embodiments, RRC known / unknown allows NN 16 to transition through the activation procedure faster and shorten the time-to-data. Knowing that a WD 22 was stationary allows the NN 16 to make educated assumptions about the RF Link, thus allowing for a shorter time-to-data and a faster convergence of link adaptation.

[0097] In some embodiments, a MAC-CE, i.e., “User-Assisted Traffic Information MAC CA ”, is created. The MAC-CE may, without being limited to, include and / or indicate one or more of the following:

[0098] • Imminent change in burst intensity including fields describing the magnitude and duration of the change. Examples may include an indicator (e.g., a Boolean) that indicates high traffic is imminent, granular traffic details about expected data size in uplink and / or downlink, data burst length, etc.

[0099] • Which of the RRC-configured SCells the WD 22 would like to (de-)activate. For example, the RF characteristics of various SCells are considered in combination with potentially already active carriers in the WD 22. If such combination is more power beneficial (considering potential WD RF architecture) than delayed scheduling, the WD 22 indicates it to the NN 16. In another example, the WD 22 may, based on current / anticipated traffic needs, provide preference considering band (e.g., frequency range 1 (FR1) vs FR2) and / or bandwidth (BW) (e.g., 100MHz carrier Vs 20 MHz carrier). For example, if the anticipated data rate is higher than that which can be timely served by a 20MHz carrier, the WD 22 may then provide preference for an SCell of 100MHz.

[0100] • The WD 22 prefers a higher / lower BW on the same or another carrier. As such, the NN 16 could for example potentially switch the WD 22 to a bandwidth part (BWP) according to the WD preference.

[0101] • The WD 22 prefers a more / less stringent time-domain configuration. For example, the WD 22 may for a certain traffic time prefer a search space configuration which is denser (e.g. every slot scheduling) in time than another search space configuration which is sparser (e.g., every 4thslot scheduling).

[0102] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0103] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0104] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0105] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0106] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0107] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0108] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0109] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

Claims

What is claim:Claim 1. A method in a network node configured to communicate with a wireless device (WD), the method comprising: receiving a user assisted session information element and / or a user assisted traffic information control element; and performing one or more actions based on the user assisted session information element and / or the user assisted traffic information control element.Claim 2. The method of Claim 1, wherein one or more of: the method further includes receiving a connection reconfiguration message including the user assisted session information element; the user assisted session information element includes description of an initial burst, an indication of whether a location is stationary since a last connected state, and / or information about each serving cell configured; and the one or more actions include network node preparing an amount of network resources ahead of time for an upcoming burst, transitioning through an activation procedure, and / or making assumptions about a radio frequency link.Claim 3. The method of any one of Claims 1 and 2, wherein the user assisted traffic information control element includes and / or indicates one or more of: an imminent change in burst intensity; information about which secondary cells the WD is to activate and / or deactivate; the WD prefers a different bandwidth on a same or another carrier; and the WD prefers a more or less stringent time-domain configuration.Claim 4. A network node configured to communicate with a wireless device (WD), the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: receive a user assisted session information element and / or a user assisted traffic information control element; and perform one or more actions based on the user assisted session information element and / or the user assisted traffic information control element.Claim 5. The network node of Claim 4, wherein one or more of: the network node is further configured to receive a connection reconfiguration message including the user assisted session information element; the user assisted session information element includes description of an initial burst, an indication of whether a location is stationary since a last connected state, and / or information about each serving cell configured; and the one or more actions include network node preparing an amount of network resources ahead of time for an upcoming burst, transitioning through an activation procedure, and / or making assumptions about a radio frequency link.Claim 6. The network node of any one of Claims 4 and 5, wherein the user assisted traffic information control element includes and / or indicates one or more of: an imminent change in burst intensity; information about which secondary cells the WD is to activate and / or deactivate; the WD prefers a different bandwidth on a same or another carrier; and the WD prefers a more or less stringent time-domain configuration.Claim 7. A method in a wireless device (WD) configured to communicate with a network node, the method comprising: transmitting a user assisted session information element and / or a user assisted traffic information control element; and performing one or more actions based on the user assisted session information element and / or the user assisted traffic information control element.Claim 8. The method of Claim 7, wherein one or more of: the method further includes transmitting a connection reconfiguration message including the user assisted session information element; the user assisted session information element includes description of an initial burst, an indication of whether a location is stationary since a last connected state, and / or information about each serving cell configured; and at least the user assisted session information element triggers the network node to prepare an amount of network resources ahead of time for an upcoming burst, transition through an activation procedure, and / or make assumptions about a radio frequency link.Claim 9. The method of any one of Claims 7 and 8, wherein the user assisted traffic information control element includes and / or indicates one or more of: an imminent change in burst intensity; information about which secondary cells the WD is to activate and / or deactivate; the WD prefers a different bandwidth on a same or another carrier; and the WD prefers a more or less stringent time-domain configuration.Claim 10. A wireless device (WD) configured to communicate with a network node, the WD configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: transmit a user assisted session information element and / or a user assisted traffic information control element; and perform one or more actions based on the user assisted session information element and / or the user assisted traffic information control element.Claim 11. The WD of Claim 10, wherein one or more of: the WD is further configured to transmit a connection reconfiguration message including the user assisted session information element; the user assisted session information element includes description of an initial burst, an indication of whether a location is stationary since a last connected state, and / or information about each serving cell configured; and at least the user assisted session information element triggers the network node to prepare an amount of network resources ahead of time for an upcoming burst, transition through an activation procedure, and / or make assumptions about a radio frequency link.Claim 12. The WD of any one of Claims 10 and 11, wherein the user assisted traffic information control element includes and / or indicates one or more of: an imminent change in burst intensity; information about which secondary cells the WD is to activate and / or deactivate; the WD prefers a different bandwidth on a same or another carrier; and the WD prefers a more or less stringent time-domain configuration.

Images