Methods and apparatus for UE secondary carrier activation and deactivation

Abstract

A method, system, and apparatus are disclosed. This document describes a method in a network node configured to communicate with a wireless device (WD). The method includes: receiving user-assisted session information elements and / or user-assisted service information control elements, and performing one or more actions based on the user-assisted session information elements and / or user-assisted service information control elements.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to auxiliary carrier activation and deactivation of wireless devices. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for fourth-generation (4G) (also known as Long Term Evolution (LTE)) and fifth-generation (5G) (also known as New Radio (NR)) wireless communication systems. Among other features, such systems provide broadband communication between network nodes (e.g., base stations) and mobile wireless devices (WDs), as well as communication between network nodes (NNs) and between WDs. 3GPP is also developing standards for sixth-generation (6G) wireless communication networks. In some cases, the term User Equipment (UE) is used, and it can refer to WDs.

[0003] Most WD Radio Resource Control (RRC) sessions have limited, short data transfer volumes, typically consisting of a few Hypertext Transfer Protocol (HTTP) requests. Only a very small fraction of the session (e.g., 1%) contributes the majority of the data transfer volume. Even for high-volume sessions, data transfer may not be continuous and fully buffered, and is often bursty, interspersed with periods of very low activity.

[0004] While carrier aggregation can achieve higher throughput, the power consumption of the WD (Driver Controller) is significantly higher because it must perform routine radio operations (e.g., Physical Downlink Control Channel (PDCCH) monitoring, Channel State Information (CSI) measurement and reporting, Sounding Reference Signal (SRS) transmission, etc.) via one or more additional carriers (rather than just one primary carrier). Therefore, WDs are typically configured to maximize battery power, minimize the number of active secondary cells (SCells) in the carrier aggregation configuration, and activate S-cells only as needed. Regular User Assistance Information (UAI) RRC messages (e.g., as described in 3GPP TS 38.311) allow the WD to indicate its preferences for maximum bandwidth, maximum number of SCells, Multiple-Input Multiple-Output (MIMO), etc., to minimize the impact on WD battery consumption. However, the WD informs network nodes of its preferences for the maximum aggregated bandwidth used for power saving or its preferences for the maximum number of secondary component carriers used for power saving. This is primarily to set an upper limit on the WD's ability to signal to the network to reduce its capacity.

[0005] Figure 1 An example procedure is shown where auxiliary information (e.g., UAI) is provided by the WD (e.g., the UE). The purpose of this procedure is to allow the UE to inform the network:

[0006] Its delay budget report carries the expected increment / decrement of the connection mode discontinuous reception (DRX) cycle length, or;

[0007] • Its overheating auxiliary information, or;

[0008] • Its IDC assistance information, or;

[0009] • Their preference for DRX parameters used for energy saving, or;

[0010] • Its preference for the maximum aggregate bandwidth used for energy saving, or;

[0011] • Its preference for the maximum number of auxiliary component carriers used for energy saving, or;

[0012] • Its preference for the maximum number of MIMO layers used for energy saving, or;

[0013] • Its preference for the minimum scheduling offset for cross-time slot scheduling used for energy saving, or;

[0014] • Auxiliary information for transitioning out of the RRC_CONNECTED state when the UE anticipates not sending or receiving data in the near future;

[0015] WD can provide information elements at the following granularities to network nodes.

[0016]

[0017] Detecting traffic increase patterns before the SCell activation process can take a considerable amount of time because network nodes first detect the traffic increase, inform the WD to activate the SCell, then begin channel quality measurements on the SCell, and report these channel quality measurements to the network before the network can send data to the WD on the SCell. Typically, when the SCell is activated, most data bursts may have already been processed by other active carriers (including the primary cell (PCell)).

[0018] In addition, the signaling overhead associated with UAI is too high (e.g., exceeding a predetermined threshold), and the associated process is too slow to adjust network capacity, for example, according to the frequency of changes in business patterns.

[0019] (For example, in 3GPP TS38.321) an attempt has been made to define a new Media Access Control (MAC) Control Element (CE) (i.e., “Recommended Bit Rate MAC CE”) for signaling intelligence between the WD and NN to make rapid decisions related to throughput requirements.

[0020] However, in most cases, when in idle mode, the WD initiates an air interface connection (RACH) because it needs to communicate (transfer data). Currently, there is no mechanism (during RRC connection establishment / reconfiguration) to indicate to the NN the characteristics of the upcoming data transfer, even though the WD may have knowledge that the correct resources will be available for network nodes when allocated correctly.

[0021] A similar issue exists in connected mode throughout the session. Due to the need to conserve WD power, network nodes attempt to keep only the required number of carriers active. While, in one option, the UAI message could be extended to allow the UE to indicate its anticipated higher data rate and desire to activate more SCells, this would still be insufficiently efficient. RRC message delivery is a rather slow process. Specifically, in a centralized cell (CU) distributed cell (DU) split architecture, RRC messages need to be decoded by the CU-CP layer before being transmitted to the DU-CP and the lower MAC scheduler layer. This can add additional time (e.g., in milliseconds) before the MAC layer is aware of this information.

[0022] Even with the extension of UAI messages, the granularity of existing information elements provided by WD is still too poor, because WD cannot specify which carrier is preferred to be (deactivated) activated.

[0023] Compared to LTE (where the SCell activation time is on the order of 20ms), the SCell activation time in NR is significantly longer (60+ms) and depends on several variables, such as those described in section 8.3 of 3GPP TS 38.133 (V17.11.0).

[0024] Furthermore, given the short duration of many data bursts, early SCell activation becomes crucial to leverage more carriers when needed. However, these carriers are deactivated when not needed to conserve WD battery power. Without a method for early SCell activation, deploying NR carrier aggregation becomes a trade-off between throughput (keeping SCells active) and WD power saving (deactivating SCells to conserve UE power). Additionally, the recommended bit rate MAC CE definition is overly restrictive, as it primarily targets a single use case (codec). Summary of the Invention

[0025] Some embodiments advantageously provide methods, systems, and apparatus for WD auxiliary carrier activation and deactivation (e.g., UE auxiliary carrier activation and deactivation).

[0026] Depending on the WD implementation (radio frequency (RF) architecture), from an energy consumption perspective, knowing which secondary carriers a network node activates may be more important than simply knowing how many secondary carriers are activated. These secondary carriers can be implemented in separate transceivers that are independently power-managed.

[0027] The WD (Diverter-Driven Controller) may shut down the transceiver / processing chain associated with a carrier when it is not in use. Therefore, for the same number of component carriers, different power levels can be used at the WD, depending on which component carriers the network node activates. However, there is currently no mechanism for the WD to inform the network node of this characteristic (which carrier), only the quantity. Furthermore, different carriers may be deployed with different bandwidths, and depending on service requirements, the WD may prefer one secondary cell over another, rather than simply indicating the number of carriers.

[0028] In some embodiments, the WD may know more about what end-user applications are running on the WD and the potential data transfer needs associated with such applications than network nodes. In some other embodiments, the WD determines (e.g., can judge and predict) any desired transfer rate and makes decisions on the trade-offs between saving battery life or expressing an intention to the network to activate more or other SCells for faster data transfer and better utilizing WD hardware and energy.

[0029] In some embodiments, for initial connections, a new optional RRC Information Element (IE) is introduced in, for example, the RRCConnectionReconfiguration signal, to provide the network with key knowledge of the characteristics of the upcoming data transmission, location changes since the last RRC connection mode, and the known / unknown state of air interface resources (e.g., SCells).

[0030] In some other embodiments, it is also suggested to introduce a new uplink (UL) MAC control element (UL MAC CE) to allow the WD to refine / update information about data transmission requirements. If the WD understands the application requirements and hardware resources at the WD level and has in-depth knowledge of the RF configurations of various configured cells in the service set, the WD can indicate preferences to network nodes to allow for timely allocation of resources, such as the correct and appropriate amount of air interface resources (e.g., selection of appropriate carriers).

[0031] One or more embodiments are ultimately beneficial because the network scheduler can respond more quickly (compared to a conventional scheduler) when activating additional carriers for anticipated data bursts and deactivating them when no additional capacity is needed. This can provide faster data acquisition (faster download / upload speeds), WD battery savings, and better network resource utilization. Attached Figure Description

[0032] A more complete understanding of this embodiment and its accompanying advantages and features will be more readily understood when considered in conjunction with the accompanying drawings, by referring to the following detailed description, in which:

[0033] Figure 1 An example of auxiliary information provided by WD is shown;

[0034] Figure 2 This is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host computer via an intermediate network according to the principles of this disclosure;

[0035] Figure 3 This is a block diagram illustrating how a host computer communicates with a wireless device via a network node through at least a partial wireless connection, according to some embodiments of the present disclosure.

[0036] Figure 4 This is a flowchart illustrating an exemplary method for executing a client application at a wireless device, implemented in a communication system including a host computer, a network node, and a wireless device, according to some embodiments of the present disclosure;

[0037] Figure 5 This is a flowchart illustrating an exemplary method for receiving user data at a wireless device, implemented in a communication system including a host computer, a network node, and a wireless device, according to some embodiments of the present disclosure;

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

[0039] Figure 7 This is a flowchart illustrating an exemplary method for receiving user data at a host computer, implemented in a communication system including a host computer, network nodes, and wireless devices, according to some embodiments of the present disclosure.

[0040] Figure 8 This is a flowchart of an exemplary process in a network node according to some embodiments of this disclosure; and

[0041] Figure 9 This is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure. Detailed Implementation

[0042] Before describing the exemplary embodiments in detail, it should be noted that the embodiments primarily consist of a combination of apparatus components and processing steps related to WD auxiliary carrier activation and deactivation. Therefore, components are appropriately indicated in the drawings by conventional symbols, and only those specific details relevant to understanding the embodiments are shown so as not to obscure this disclosure with details that would be obvious to those of ordinary skill in the art who benefit from the description herein. Throughout this specification, similar reference numerals denote similar elements.

[0043] As used herein, relational terms (e.g., “first” and “second”, “top” and “bottom”, etc.) may be used only to distinguish one entity or element from another, and do not necessarily require or imply any physical or logical relationship or order between these entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the concept described herein. Unless the context explicitly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are intended to also include the plural forms. It should also be understood that the terms “comprising,” “having,” and / or “including” as used herein indicate the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0044] In the embodiments described herein, connection terms such as "communicating with" can be used to indicate electrical or data communication, which can be achieved, for example, through physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will understand that multiple components can interoperate, and modifications and variations can be made to electrical and data communication.

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

[0046] As used herein, the term "network node" can refer to any type of network node included in a radio network, including base stations (BS), radio base stations, basic transceiver stations (BTS), base station controllers (BSC), radio network controllers (RNC), g node Bs (gNB), evolved Node Bs (eNB or eNodeB), node Bs, multi-standard radio (MSR) radio nodes (such as MSR BS), multi-cell / multicast coordination entities (MCE), integrated access and backhaul (IAB) nodes, relay nodes, donor node control relays, radio access points (AP), transmission points, transmission nodes, remote radio units (RRU), remote radio heads (RRH), core network nodes (e.g., mobility management entities (MME), self-organizing network (SON) nodes, coordination nodes, location nodes, MDT nodes, etc.), external nodes (e.g., third-party nodes, nodes outside the current network), nodes in distributed antenna systems (DAS), spectrum access systems (SAS) nodes, element management systems (EMS), etc. Network nodes can also include test equipment. The term “radio node” as used in this article can also be used to refer to a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0047] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) may be used interchangeably. A WD as used herein can be any type of wireless device capable of communicating with a network node or another WD via radio signals, such as a wireless device (WD). A WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD or a WD capable of machine-to-machine (M2M) communication, a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter or client terminal device (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0048] Additionally, in some embodiments, the generic term "radio network node" is used. It can be any type of radio network node, including any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved NodeB (eNB), NodeB, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), remote radio headend (RRH), etc.

[0049] Please note that although terms from a particular wireless system (e.g., 3GPP LTE and / or New Radio (NR)) may be used in this disclosure, this should not be construed as limiting the scope of this disclosure to the aforementioned systems only. Other wireless systems (including, but not limited to, Wideband Code Division Multiple Access (WCDMA), Global Microwave Access Interoperability (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM)) may also benefit from utilizing the ideas covered in this disclosure.

[0050] It should also be noted that the functions performed by wireless devices or network nodes as described herein can be distributed across multiple wireless devices and / or network nodes. In other words, it is expected that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device, and can actually be distributed across several physical devices.

[0051] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that the terms used herein should be interpreted in accordance with their meaning in the context of this specification and related art, and not in an ideal or overly formal sense, unless so explicitly defined herein.

[0052] Referring again to the accompanying drawings, in which similar elements are indicated by similar reference numerals, Figure 2 The diagram illustrates a communication system 10 according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), comprising an access network (e.g., a radio access network) 12 and a core network 14. The access network 12 includes multiple network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via 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 can wirelessly connect to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where a single WD is located in the coverage area or a single WD is connected 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 more WDs 22 and network nodes 16.

[0053] Additionally, it is conceivable that WD 22 can communicate simultaneously and / or be configured to communicate individually with more than one network node 16 and more than one type of network node 16. For example, WD 22 can have dual connectivity with LTE-enabled network nodes 16 and the same or different NR-enabled network nodes 16. For example, WD 22 can communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0054] The communication system 10 itself can be connected to a host computer 24, which can 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 cluster. The host computer 24 can be owned by or under the control of a service provider, or can be operated by or on behalf of a service provider. Connections 26, 28 between the telecommunications network 10 and the host computer 24 can extend directly from the core network 14 to the host computer 24, or can extend via an optional intermediate network 30. The intermediate network 30 can be one or more of a public network, a private network, or a server network. The intermediate network 30 (if any) can be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0055] Figure 2 The communication system as a whole establishes a connection between one of the connected WDs 22a and 22b and the host computer 24. This connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a and 22b are configured to send data and / or signaling via the OTT connection using the access network 12, core network 14, any intermediate network 30, and other possible intermediate infrastructure (not shown). At least some of the participating communication devices through which the OTT connection passes are unaware of the routes of the uplink and downlink communications; in this sense, the OTT connection can be transparent. For example, network node 16 may not be informed or need not be informed of the past routes of incoming downlink communications that have data originating from host computer 24 and to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, network node 16 does not need to know the future routes of uplink communications originating from WD 22a and heading towards the host computer 24.

[0056] Network node 16 is configured to include an NN management unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features, such as NN functions, described in this disclosure. Wireless device 22 is configured to include a WD management unit 34, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or functions, such as WD functions, described in this disclosure.

[0057] Now refer to Figure 2 This section describes an example implementation of the WD 22, network node 16, and host computer 24 discussed in the preceding paragraphs, according to an embodiment. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40 configured to establish and maintain wired or wireless connections with different communication devices of the communication system 10. The host computer 24 also includes processing circuitry 42, which may have storage and / or processing capabilities. Processing circuitry 42 may include a processor 44 and memory 46. Specifically, as a complement or alternative to the processor (e.g., a central processing unit) and memory, processing circuitry 42 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) adapted to execute instructions. The processor 44 can be configured to access memory 46 (e.g., write to or read from memory 46), which can include any type of volatile and / or non-volatile memory, such as 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).

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

[0059] Software 48 can be executed by processing circuitry 42. Software 48 includes a host application 50. Host application 50 can be operated to provide services to a remote user, such as a WD 22 connected via an OTT connection 52 terminating between the WD 22 and the host computer 24. In providing services to the remote user, host application 50 can provide user data transmitted using the OTT connection 52. "User data" can be data and information described herein for implementing the described functionality. In embodiments, host computer 24 can be configured to provide control and functionality to a service provider and can be operated by or on behalf of the service provider. Processing circuitry 42 of host computer 24 enables host computer 24 to observe, monitor, control, transmit to network node 16 and / or wireless device 22 and / or receive from network node 16 and / or wireless device 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54, which is configured to enable the service provider to observe / monitor / control network node 16 and / or wireless device 22, send to network node 16 and / or wireless device 22, and / or receive from network node 16 and / or wireless device 22, etc.

[0060] The communication system 10 also includes a network node 16 configured within the communication system 10, which includes hardware 58 enabling it to communicate with the host computer 24 and the WD 22. Hardware 58 may include: a communication interface 60 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 10; and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with the WD 22 located within the coverage area 18 served by the network node 16. The radio interface 62 may be configured 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 with the host computer 24. The connection 66 may be direct, or it may be via the core network 14 of the communication system 10 and / or via one or more intermediate networks 30 outside the communication system 10.

[0061] In the illustrated embodiment, the hardware 58 of network node 16 also includes processing circuitry 68. Processing circuitry 68 may include a processor 70 and memory 72. Specifically, as a complement or alternative to the processor (e.g., a central processing unit) and memory, processing circuitry 68 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) adapted to execute instructions. Processor 70 may be configured to access (e.g., write to or read from) memory 72, which may include any type of volatile and / or non-volatile memory, such as 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).

[0062] Therefore, network node 16 also has software 74 internally stored, for example in memory 72, or stored in external memory (e.g., a database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 can be executed by processing circuitry 68. Processing circuitry 68 can be configured to control any methods and / or processes described herein, and / or cause such methods and / or processes to be executed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for performing the functions of network node 16 described herein. Memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause 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 network node 16 may include NN management unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features, such as NN functions, described in this disclosure.

[0063] The communication system 10 also includes the previously mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 where the WD 22 is currently located. The radio interface 82 may be configured as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0064] The hardware 80 of the WD 22 also includes processing circuitry 84. Processing circuitry 84 may include a processor 86 and memory 88. Specifically, as a complement or alternative to the processor (e.g., a central processing unit) and memory, processing circuitry 84 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) adapted to execute instructions. Processor 86 may be configured to access memory 88 (e.g., write to or read from memory 46), which may include any type of volatile and / or non-volatile memory, such as 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).

[0065] Therefore, WD 22 may also include software 90, which is stored, for example, in memory 88 at WD 22, or in external memory accessible by WD 22 (e.g., a database, storage array, network storage device, etc.). Software 90 may be executed by processing circuitry 84. Software 90 may include a client application 92. Client application 92 may be operated to provide services to human or non-human users via WD 22 with the support of host computer 24. In host computer 24, a host application 50 is executing and can communicate with the executing client application 92 via an OTT connection 52, which terminates between WD 22 and host computer 24. When providing services to a user, client application 92 may receive request data from host application 50 and provide user data in response to the request data. OTT connection 52 can transmit both request data and user data. Client application 92 may interact with the user to generate the user data it provides.

[0066] Processing circuitry 84 may be configured to control any methods and / or processes described herein, and / or cause such methods and / or processes to be performed, for example, by WD 22. Processor 86 corresponds to one or more processors 86 for performing the functions of WD 22 described herein. WD 22 includes memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92 may include instructions that, when executed by processor 86 and / or processing circuitry 84, cause processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, processing circuitry 84 of wireless device 22 may include WD management unit 34 configured to perform any steps and / or tasks and / or processes and / or methods and / or functions, such as WD functions, described in this disclosure.

[0067] In some embodiments, the internal operations of network node 16, WD 22, and host computer 24 can be as follows: Figure 3 As shown, and independently, the surrounding network topology can be Figure 2 The network topology.

[0068] exist Figure 4 The OTT connection 52 is abstractly depicted to illustrate communication between host computer 24 and wireless device 22 via network node 16, without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the service provider operating host computer 24 or both. The network infrastructure can also dynamically change the routing determination while OTT connection 52 is active (e.g., based on load balancing considerations or network reconfiguration).

[0069] The wireless connection 64 between WD 22 and network node 16 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT services provided to WD 22 using OTT connection 52, in which wireless connection 64 may form the final part. More specifically, the teachings of some of these embodiments can improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user wait times, relaxed file size limits, better responsiveness, extended battery life, etc.

[0070] In some embodiments, a measurement process may be provided for monitoring data rate, latency, and other factors that are the object of improvement in one or more embodiments. Optional network functionality may also be present for reconfiguring the OTT connection 52 between host computer 24 and WD 22 in response to changes in measurement results. The measurement process and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in software 48 of host computer 24 or software 90 of WD 22, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices traversed by the OTT connection 52; the sensors may participate in the measurement process by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities from which software 48, 90 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 52 may include message formatting, retransmission settings, preferred routing, etc.; the reconfiguration does not need to affect network node 16, and the reconfiguration may be unknown or imperceptible to network node 16. Some of such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary WD signaling, which facilitates the host computer 24 in measuring throughput, propagation time, latency, etc. In some embodiments, the measurement may be achieved by software 48, 90 using OTT connection 52 to send messages (especially empty messages or "virtual" messages) while monitoring propagation time, errors, etc.

[0071] Therefore, in some embodiments, host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 configured to forward user data to the cellular network for transmission to WD 22. In some embodiments, the cellular network also includes network node 16 having a radio interface 62. In some embodiments, network node 16 and / or processing circuitry 68 of network node 16 are configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to WD 22, and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from WD 22.

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

[0073] although Figure 2 and Figure 3 Various “units” such as NN management unit 32 and WD management unit 34 are shown as being within their respective processors, but it is conceivable that these units could be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, these units could be implemented within the processing circuitry in hardware or a combination of hardware and software.

[0074] Figure 4 This illustrates a communication system (e.g., according to one embodiment) Figure 2 and Figure 3 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be referenced... Figure 3 The method describes a host computer 24, a network node 16, and a WD 22. In a first step, the host computer 24 provides user data (block S100). In an optional sub-step of the first step, the host computer 24 provides the user data by executing a host application (e.g., host application 50) (block S102). In a second step, the host computer 24 initiates a transmission to the WD 22 carrying the user data (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the WD 22 (block S106). In an optional fourth step, the WD 22 executes a client application (e.g., client application 92) associated with the host application 50 executed by the host computer 24 (block S108).

[0075] Figure 5 This illustrates a communication system (e.g., according to one embodiment) Figure 2 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be referenced... Figure 2 and Figure 3 The description includes a host computer 24, a network node 16, and a WD 22. In a first step of the method, the host computer 24 provides user data (block S110). In an optional sub-step (not shown), the host computer 24 provides the user data by executing a host application (e.g., host application 50). In a second step, the host computer 24 initiates a transmission to the WD 22 carrying the user data (block S112). This transmission may be carried via the network node 16, according to 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 S114).

[0076] Figure 6This illustrates a communication system (e.g., according to one embodiment) Figure 2 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be referenced... Figure 2 and Figure 3 The method describes a host computer 24, a network node 16, and a WD 22. In an optional first step, WD 22 receives input data provided by the host computer 24 (box S116). In an optional sub-step of the first step, WD 22 executes a client application 92 that provides user data in response to the received input data provided by the host computer 24 (box S118). Additionally or alternatively, in an optional second step, WD 22 provides user data (box S120). In an optional sub-step of the second step, WD provides user data by executing a client application (e.g., client application 92) (box S122). When providing user data, the executed client application 92 may also consider user input received from the user. Regardless of the specific manner in which user data is provided, WD 22 may initiate the transmission of user data to the host computer 24 in an optional third sub-step (box S124). In the fourth step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, host computer 24 receives user data sent from WD 22 (block S126).

[0077] Figure 7 This illustrates a communication system (e.g., according to one embodiment) Figure 2 A flowchart illustrating an exemplary method implemented in a communication system. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be referenced... Figure 2 and Figure 3 The description includes a host computer 24, a network node 16, and a WD 22. In an optional first step of the method, network node 16 receives user data from WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S128). In an optional second step, network node 16 initiates a transmission of the received user data to host computer 24 (block S130). In a third step, host computer 24 receives the user data carried in the transmission initiated by network node 16 (block S132).

[0078] Figure 8This is a flowchart of an exemplary process in network node 16. One or more blocks described herein can be performed by one or more elements of network node 16, such as one or more of processing circuitry 68 (including NN management unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 (e.g., via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60) is configured to: receive (block S134) user-assisted session information elements and / or user-assisted service information control elements, and perform (block S136) one or more actions based on the user-assisted session information elements and / or user-assisted service information control elements.

[0079] In some embodiments, the method further includes one or more of the following actions: (A) receiving a connection reconfiguration message including user-assisted session information elements; (B) the user-assisted session information elements including a description of the initial burst, an indication of whether the location has been stationary since the last connection state, and / or information about each configured serving cell; and (C) one or more actions including the network node preparing a certain amount of network resources in advance for the upcoming burst, performing a transition through an activation process, and / or making assumptions about the radio frequency link.

[0080] In some other embodiments, the user auxiliary service information control element includes and / or indicates one or more of the following: (A) an impending burst intensity change; (B) information about which secondary cells WD 22 should activate and / or deactivate; (C) WD 22 preferably uses different bandwidths on the same carrier or another carrier; and (D) WD 22 preferably uses a more stringent or more lenient time-domain configuration.

[0081] Figure 9 This 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 the wireless device 22, such as one or more of processing circuitry 84 (including WD management unit 34), processor 86, radio interface 82, and / or communication interface 60. The wireless device 22 (e.g., via processing circuitry 84 and / or processor 86 and / or radio interface 82) is configured to: transmit (block S138) user-assisted session information elements and / or user-assisted service information control elements, and perform (block S140) one or more actions based on the user-assisted session information elements and / or user-assisted service information control elements.

[0082] In some embodiments, one or more of the following applies: (A) the method further includes sending a connection reconfiguration message including a user-assisted session information element; (B) the user-assisted session information element includes a description of the initial burst, an indication of whether the location has been stationary since the last connection state, and / or information about each configured serving cell; and (C) at least the user-assisted session information element triggers a network node to prepare a certain amount of network resources in advance for the upcoming burst signal, to perform a transition through an activation process, and / or to make assumptions about the radio frequency link.

[0083] In some other embodiments, the user auxiliary service information control element includes and / or indicates one or more of the following: (A) an impending burst intensity change; (B) information about which secondary cells WD 22 should activate and / or deactivate; (C) WD 22 preferably uses different bandwidths on the same carrier or another carrier; and (D) WD 22 preferably uses a more stringent or more lenient time-domain configuration.

[0084] The general process flow of the arrangements of this disclosure has been described and examples of hardware and software arrangements for implementing the processes and functions of this disclosure have been provided. The following sections provide details and examples of arrangements for WD (e.g., UE) secondary carrier activation and deactivation.

[0085] Typically, data transmission is initiated by WD 22. WD 22 may possess information about the characteristics of the upcoming data transmission, as well as other knowledge that will be used by NN 16 when allocating resources, such as whether WD 22 has been inactive since the last RRC connection state, and whether the cells in the serving set have known RF characteristics. Furthermore, information about the serving cell (e.g., the most recently synchronized signal block (SSB)) can be used by NN 16 to allow for faster data acquisition and potentially higher transmission rates.

[0086] Some implementations provide the creation of an RRC IE (i.e., the "User Assistive Session Information IE" included in the RRCConnectionReconfiguration message (between WD 22 and NN 16)).

[0087] The field list of the RRC IE may include (but is not limited to) one or more of the following:

[0088] • Description of the initial outbreak:

[0089] o Estimated data burst size (in kilobytes);

[0090] o Expected data direction (UL / DL);

[0091] • "Position has been stationary since the last RRCConnected state": Boolean; and / or

[0092] • Known information (RRC known / unknown) for each configured serving cell, including the last reported CSI report if the location is stationary.

[0093] The description of the initial burst allows the NN 16 to prepare a certain amount of network resources in advance for an upcoming burst, such as enabling more efficient communication compared to a conventional system with a WD 22. In a conventional system, the WD 22 establishes its connection first, and the NN 16 recognizes the need after a certain period of time and (re)configures additional resources for the WD 22.

[0094] In some other embodiments, the known / unknown RRC allows NN 16 to transition through the activation process more quickly and reduce data acquisition time. Knowing that WD 22 is static allows NN 16 to make reasonable assumptions about the RF link, thereby allowing for faster data acquisition and faster link adaptation convergence.

[0095] In some embodiments, a MAC-CE, namely "User Assistance Service Information MAC CA", is created. This MAC-CE may include, but is not limited to, one or more of the following:

[0096] • The impending burst intensity change, including fields describing the magnitude and duration of the change. Examples may include indicators indicating an impending high traffic volume (e.g., Boolean values), detailed business information about the expected data size in the uplink and / or downlink, the length of the data burst, etc.

[0097] • WD 22 decides which SCells in the RRC configuration it wants to activate (deactivate). For example, it considers the RF characteristics of various SCells in conjunction with carriers that may already be activated in WD 22. If this combination (considering possible WD RF architectures) is more energy efficient than delayed scheduling, WD 22 indicates this to NN 16. In another example, WD 22 may provide preferences regarding frequency bands (e.g., frequency range 1 (FR1) vs. FR2) and / or bandwidths (BW) (e.g., 100MHz carrier vs. 20MHz carrier) based on current / expected service demands. For example, if the expected data rate is higher than the data rate that the 20MHz carrier can provide in time, WD 22 may prefer the 100MHz SCell.

[0098] • WD 22 preferably uses a higher / lower BW on the same or different carriers. Therefore, NN 16 can switch WD 22 to the bandwidth portion (BWP) according to WD's preference.

[0099] • WD 22 prefers a more stringent / more lenient time-domain configuration. For example, WD 22 may prefer a more time-intensive search space configuration (e.g., scheduling per time slot) rather than a more time-sparse search space configuration (e.g., scheduling every 3 time slots) during a specific business period.

[0100] As those skilled in the art will recognize, the concepts described herein can be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining hardware and software aspects, all of which are collectively referred to herein as “circuit” or “module.” Any processes, steps, actions, and / or functions described herein can be performed by and / or associated with a corresponding module, which can be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure can take the form of a computer program product on a tangible computer-readable storage medium having computer program code embodied in that medium that is executable by a computer. Any suitable tangible computer-readable medium can be utilized, including hard disks, CD-ROMs, electrical storage devices, optical storage devices, or magnetic storage devices.

[0101] This document describes some embodiments with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It should be understood that each block in 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 can be provided to a general-purpose computer (thus creating a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing apparatus for producing a machine, such that the instructions (executed via the computer's processor or other programmable data processing apparatus) create means for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0102] These computer program instructions may also be stored in a computer-readable storage medium or storage medium that directs a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce implementation flowcharts and / or blocks. Figure 1 The article of an instruction device for a function / action specified in one or more boxes.

[0103] Computer program instructions may also be loaded into a computer or other programmable data processing apparatus to cause a series of operable steps to be executed 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 for implementing flowcharts and / or blocks. Figure 1 The steps of the function / action specified in one or more boxes.

[0104] It should be understood that the functions and / or actions marked in the boxes may occur in a different order than those indicated in the operating instructions. For example, depending on the function / action involved, two boxes shown consecutively may actually be executed simultaneously, or the boxes may sometimes be executed in reverse order. Although some diagrams include arrows on the communication path to indicate the main direction of communication, it should be understood that communication may occur in the opposite direction to the indicated arrow.

[0105] Computer program code used to perform the operations of the concepts described herein can be written in an object-oriented programming language such as Python, Java®, or C++. However, computer program code used to perform the operations of this disclosure can also be written in a conventional procedural programming language such as the "C" programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter case, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0106] In conjunction with the foregoing description and accompanying drawings, numerous different embodiments have been disclosed herein. It should be understood that a verbatim description and illustration of each combination and sub-combination of these embodiments would be excessively repetitive and confusing. Therefore, all embodiments may be combined in any manner and / or combination, and this specification, including the accompanying drawings, is to be interpreted as a complete written description of all combinations and sub-combinations of the embodiments described herein, as well as the ways and processes of making and using them, and will support claims to any such combinations or sub-combinations.

[0107] Those skilled in the art will recognize that the embodiments described herein are not limited to those specifically shown and described above. Furthermore, unless otherwise stated above, it should be noted that all figures are not drawn to scale. Various modifications and variations can be made in light of the foregoing teachings.

Claims

1. A method in a network node configured to communicate with a wireless device, WD, the method comprising: receiving a user assistance session information element and / or a user assistance traffic information control element; and performing one or more actions based on the user assistance session information element and / or the user assistance traffic information control element.

2. The method of claim 1, wherein, One or more of the following apply: the method further comprises receiving a connection reconfiguration message comprising the user assistance session information element; the user assistance session information element comprises a description of an initial burst, an indication about whether the location has been stationary since the last connection state, and / or information about each configured serving cell; and the one or more actions comprise the network node preparing an amount of network resources in advance for an upcoming burst, transitioning through an activation procedure, and / or making assumptions about radio frequency links.

3. The method of any one of claims 1 and 2, wherein, the user assistance traffic information control element comprises and / or indicates one or more of: an upcoming change in burst intensity; information about which secondary cells the WD is to activate and / or deactivate; different bandwidths on the same carrier or another carrier preferred by the WD; and a more stringent or more relaxed time domain configuration preferred by the WD.

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 processing circuitry configured to: receive a user assistance session information element and / or a user assistance traffic information control element; and perform one or more actions based on the user assistance session information element and / or the user assistance traffic information control element.

5. The network node of claim 4, wherein, One or more of the following apply: the network node is further configured to receive a connection reconfiguration message comprising a user assistance session information element; the user assistance session information element comprises a description of an initial burst, an indication about whether the location has been stationary since the last connection state, and / or information about each configured serving cell; and the one or more actions comprise the network node preparing an amount of network resources in advance for an upcoming burst, transitioning through an activation procedure, and / or making assumptions about radio frequency links.

6. The network node of any one of claims 4 and 5, wherein, the user assistance traffic information control element comprises and / or indicates one or more of: an upcoming change in burst intensity; information about which secondary cells the WD is to activate and / or deactivate; different bandwidths on the same carrier or another carrier preferred by the WD; and a more stringent or more relaxed time domain configuration preferred by the WD.

7. A method in a wireless device, WD, configured to communicate with a network node, the method comprising: sending a user assistance session information element and / or a user assistance traffic information control element; and performing one or more actions based on the user assistance session information element and / or the user assistance traffic information control element.

8. The method of claim 7, wherein, One or more of the following apply: the method further comprises sending a connection reconfiguration message comprising the user assistance session information element; The user assistance session information element comprises a description of the initial burst, an indication on whether the location has been stationary since the last connection state, and / or information on each configured serving cell; and At least the user assistance session information element triggers the network node to prepare an amount of network resources in advance for the upcoming burst, to switch through an activation procedure, and / or to make assumptions on the radio frequency link.

9. The method of any one of claims 7 and 8, wherein, The user assistance traffic information control element comprises and / or indicates one or more of: an upcoming change in burst intensity; information on which secondary cells the WD is to activate and / or deactivate; a different bandwidth on the same carrier or another carrier preferred by the WD; and a more stringent or more relaxed time domain configuration preferred by the WD.

10. A wireless device, WD, configured to communicate with a network node, the WD configured to and / or comprising a radio interface and / or processing circuitry configured to: send a user assistance session information element and / or a user assistance traffic information control element; and perform one or more actions based on the user assistance session information element and / or the user assistance traffic information control element.

11. The WD of claim 10, one or more of the following apply: The WD is further configured to send a connection reconfiguration message comprising a user assistance session information element; The user assistance session information element comprises a description of the initial burst, an indication on whether the location has been stationary since the last connection state, and / or information on each configured serving cell; and At least the user assistance session information element triggers the network node to prepare an amount of network resources in advance for the upcoming burst, to switch through an activation procedure, and / or to make assumptions on the radio frequency link.

12. The WD of any one of claims 10 and 11, wherein, The user assistance traffic information control element comprises and / or indicates one or more of: an upcoming change in burst intensity; information on which secondary cells the WD is to activate and / or deactivate; a different bandwidth on the same carrier or another carrier preferred by the WD; and a more stringent or more relaxed time domain configuration preferred by the WD.

Images