Radio network node, user equipment and methods performed therein
By enabling User Equipment (UE) to apply priority rules for uplink resource allocation in wireless communication networks, the method addresses the challenge of managing CSI reporting and ensures efficient data transmission, prioritizing time-sensitive data over non-time-critical CSI feedback.
Patent Information
- Application Number
- PCT/SE2023/050907
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-09-15
- Publication Date
- 2025-03-20
AI Technical Summary
Current wireless communication networks face challenges in efficiently handling communication, particularly in managing Channel State Information (CSI) reporting, which can lead to conflicts between prioritizing CSI feedback and transmitting time-sensitive uplink data.
A method where User Equipment (UE) transmits a capability indication to a radio network node, allowing the UE to apply priority rules for allocating uplink resources. These priority rules prioritize certain uplink data transmissions over non-time-critical CSI feedback, ensuring efficient resource allocation and minimizing network performance impact.
The proposed solution enables UEs to prioritize time-sensitive uplink data over non-time-critical CSI feedback, thereby improving network efficiency and reducing latency in data transmission, while still allowing for effective CSI data collection when necessary.
Smart Images

Figure SE2023050907_20032025_PF_FP_ABST
Abstract
Description
[0001] RADIO NETWORK NODE, USER EQUIPMENT AND METHODS PERFORMED
[0002] THEREIN
[0003] TECHNICAL FIELD
[0004] Embodiments herein relate to a radio network node, a user equipment (UE) and methods performed therein regarding communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication, such as managing Channel State Information (CSI) reporting, in a wireless communication network.
[0005] BACKGROUND
[0006] In a typical wireless communication network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, servers, computers, communicate via an Access Network (AN), such as a radio access network (RAN) or a wired access network, with one or more core networks (CNs). The AN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the access node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the access node.
[0007] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate, e.g., enhanced data rate and radio capacity. In some RANs, e.g., as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises, and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.
[0008] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and present and coming 3GPP releases, such as New Radio (NR) and extensions, are being worked on. The EPS comprises of the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.
[0009] With the emerging 5G technologies such as new radio (NR), the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.
[0010] Artificial Intelligence (Al), Machine Learning (ML) have been investigated as promising tools to optimize the design of air-interface in wireless communication networks in both academia and industry. Example use cases include using autoencoders for CSI compression to reduce the feedback overhead and improve channel prediction accuracy; using deep neural networks for classifying Line of Sight (LOS) and Non-Line of Sight (NLOS) conditions to enhance the positioning accuracy; and using reinforcement learning for beam selection at the network side and / or the UE side to reduce the signaling overhead and beam alignment latency; using deep reinforcement learning to learn an optimal precoding policy for complex Multiple Input Multiple Output (MIMO) precoding problems.
[0011] In 3GPP NR standardization work, a new release 18 study item on AI / ML for NR air interface has started since May 2022 RP-213599, “Study on Artificial Intelligence (Al) / Machine Learning (ML) for NR Air Interface”, Dec. 2021. This study item will explore the benefits of augmenting the air-interface with features enabling improved support of AI / ML based algorithms for enhanced performance and / or reduced complexity / overhead. Through studying a few selected use cases, such as CSI feedback, beam management and positioning, this study aims at laying the foundation for future air-interface use cases leveraging AI / ML techniques.
[0012] A possible high-level description of model Life Cycle Management (LCM) for Al on physical layer (PHY) can include the stages and data / signal flows depicted in Fig. 1. A detailed description of different LCM stages can be found in R1-2208908, “Discussion on general aspects of AI / ML framework”, Oct. 2022, Ericsson.
[0013] Data Collection is a stage that collects and provides input data, such as raw data or pre-processed data, for Model Training, Model Inference and Model Monitoring.
[0014] If an Al model only requires uplink gNB radio measurements, then the networkside can collect and label data via existing 3GPP signaling shown in R1 -2208908, such as data collection of CSI feedback, i.e., information on the downlink wireless channel reported back by the UE, for AI / ML training purposes. Training data may be acquired in three distinct manners for those use cases where layer 1 (L1) information is required for AI / ML training purposes: i) L1-CSI reporting framework: this framework relies on utilizing existing signaling to collect training data, e.g., CSI feedback. This alternative allows the network to collect data potentially minimizing overheads for some use cases — since they already form part of the normal network operation — and without introducing new features to the standard. ii) Minimization of Drive Test (MDT) framework: a mechanism to configure normal UEs in an interested area to perform higher-layer radio measurements, store the measurement results and then report them to Operations, Administration, and Maintenance (OAM). MDT based data collection is controlled by the OAM and the data collection procedure is subject to user consent. A detailed description of radio measurement collection mechanisms for MDT can be found in TS 37.320 v.17.0.0, Radio measurement collection for Minimization of Drive Tests (MDT). iii) Radio Resource Control (RRC)-message based framework: This framework is expected to support L1 UE measurement configuration and UE logging, storing, and reporting of collected data via RRC message(s) to the gNB, and the training data collection procedure terminates at the gNB. While more flexible than the L1-CSI reporting framework, e.g., can support data collection with large payload size or under different RRC states, this framework requires standardization and may introduce additional overheads with regards to the L1-CSI reporting framework.
[0015] If the network cannot accurately estimate the full downlink channel from uplink transmissions, then active UEs need to report channel information to the network over the uplink. In LTE and NR, this feedback is achieved by the following signaling L1-CSI reporting framework:
[0016] • The network periodically / semi-persistently / aperiodically transmits DL Reference Signal (RS) resources, e.g., CSI-RSs, each comprising of a number of ports.
[0017] • The UE estimates the downlink channel by measuring each of the configured DL RS resources.
[0018] • The UE calculates and reports CSI, e.g., CSI Reference Signal Resource Indicator (CRI), Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (Rl) where PMI is the precoder and Rl is the rank of the precoder, to the network over uplink, for example, control or data, channel.
[0019] • The network uses the UE’s feedback to select suitable precoders for downlink multi-user (MU)-MIMO transmissions.
[0020] In NR, both Type I and Type II codebooks are configurable for reporting PMI, where the Type II PMI reporting typically has a substantially larger overhead than Type I PMI, few tens of bits vs. several hundred bits, because it has been specifically designed to enable the UE feeding back rich channel information to facilitate MU-MI MO operation. Due to the potential large size of the reports and the difficulty of predicting the amount of information to be fed back by the UE at a given time, which is dependent on the instantaneous characteristics of the wireless channel, the existing process to obtain CSI feedback via Uplink Control Information (UCI), where CSI report resides in, on Physical Uplink Shared Channel (PUSCH) via DL Control Information (DCI) can be summarized as follows:
[0021] • The gNB allocates PUSCH resources to the UE, together with some Modulation Coding Scheme (MCS).
[0022] • The gNB triggers CSI feedback to be carried on PUSCH, this is achieved by configuring the CSI request bits contained in the DCI scheduling the PUSCH.
[0023] • The gNB configures if data, such as Uplink Shared Channel (UL-SCH), is transmitted on PUSCH. o The UE determines the number of resource elements for carrying the CSI report, and other UCI, based on the MCS and beta-offset parameters configured in the DCI. If LIL-SCH is triggered, and if there are unused resources by CSI report, and other UCI, these unused resources can be used for transmitting data. The unused resources for CSI reporting may occur when the UE decides to report fewer bits in CSI Part 2 due to a channel condition when a Type II PMI is configured.
[0024] As an example shown in Fig. 2, a UE maps UCI on PUSCH according to a certain rules defined in the standard. In practice, the current standard defines the following priority rules when multiplexing UCI with data on PUSCH :
[0025] • All UCI types have higher priority compared to data. UL data is only transmitted on PUSCH if there are spare resource elements after mapping all UCI types to be transmitted on the PUSCH.
[0026] • Different types of UCI have different priority levels. For instance, Hybrid Automatic Repeat Request (HARQ)-acknowledgement (ACK) has higher priority compared to CSI report. CSI part 1 has higher priority than CSI part 2.
[0027] SUMMARY
[0028] As part of developing embodiments herein one or more problems have first been identified.
[0029] Consider the situation where the network is interested in gathering downlink CSI, e.g., CSI Type II, also referred to as Type II PMI, or a newly type tailored for data acquisition, for training purposes. An example use case where Type II CSI feedback may be utilized for AI / ML training purposes includes the utilization of such information as a ground truth when performing an AI / ML-based CSI estimation in downlink bands only using Sounding Reference Signals (SRS) from distinct uplink bands, see M. Arnold et al., “Towards Practical FDD Massive MIMO: CSI Extrapolation Driven by Deep Learning and Actual Channel Measurements,” in 53rd Asilomar Conference on Signals, Systems and Computers, 2019.
[0030] Given that the radio network node does not always have access to the most recent uplink buffer status at the UE, the UE may have time-sensitive data to transmit when requested to convey the CSI feedback. Also for offline model training cases, the latency requirement for radio network node to obtain the training data, e.g., CSI Type II or a newly type tailored CSI type, is much relaxed compared to the UE’s normal uplink data transmission. As per the current priority rules, the CSI feedback has always priority over uplink data and will have to be transmitted back. However, in the context of data collection for model training or monitoring, the acquisition of the downlink CSI may not be essential, because it may not be used by the radio network node for MU -Ml MO precoding purposes, or time-sensitive, since AI / ML models can be retrained / monitored in a non-real-time manner.
[0031] Overall, the current specification may cause situations where the UE may be ready but unable to transmit important uplink data when being scheduled to perform a non-time- critical data collection for model training or model monitoring.
[0032] An object herein is to provide a mechanism to handle communication efficiently in the wireless communication network.
[0033] According to an aspect the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling communication of the UE in a wireless communication network. The UE transmits a capability indication to a radio network node, wherein the capability indication indicates a capability to apply one or more priority rules, wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions. The one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions. The UE further applies a priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions.
[0034] According to another aspect the object is achieved, according to embodiments herein, by providing a method performed by a radio network node for handling communication of a UE in a wireless communication network. The radio network node receives a capability indication from the UE, wherein the capability indication indicates a capability to apply one or more priority rules, and wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions. The one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions. The radio network node schedules uplink data transmissions for the UE. The radio network node further receives from the UE the first type of uplink data transmissions and / or the second type of uplink data transmissions; and decodes the first type of uplink data transmissions and / or the second type of uplink data transmissions taking the capability indication into account.
[0035] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the radio network node and the UE, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the radio network node and the UE, respectively.
[0036] According to yet another aspect the object is achieved, according to embodiments herein, by providing a UE for handling communication of the UE in a wireless communication network. The UE is configured to transmit a capability indication to a radio network node, wherein the capability indication indicates a capability to apply one or more priority rules, wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions. The one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions. The UE is further configured to apply a priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions.
[0037] According to still another aspect the object is achieved, according to embodiments herein, by providing a radio network node for handling communication of a UE in a wireless communication network. The radio network node is configured to receive a capability indication from the UE, wherein the capability indication indicates a capability to apply one or more priority rules, and wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions. The one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions. The radio network node is configured to schedule uplink data transmissions for the UE. The radio network node is further configured to receive from the UE the first type of uplink data transmissions and / or the second type of uplink data transmissions; and to decode the first type of uplink data transmissions and / or the second type of uplink data transmissions taking the capability indication into account.
[0038] It is herein disclosed a method that enables UEs to apply a priority rule when allocating UCI resources on PLISCH. The objective is to enable UEs to prioritize certain uplink data transmissions over non-time-sensitive UCI-based data for collection processes, therefore minimizing the impact of the latter on the network performance. Embodiments herein may, for example, allow UEs to sacrifice CSI feedback quality when UEs have uplink data with certain characteristics to be transmitted to the network, e.g., time-sensitive data. The one or more priority rules allow UEs to prioritize uplink data transmissions with certain characteristics over non-time-sensitive UCI-based data collection processes on PUSCH. Thus, embodiments herein handle communication efficiently for UEs in the wireless communication network.
[0039] BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:
[0041] Fig. 1 shows a flowchart of a Model LCM according to prior art;
[0042] Fig. 2 shows a schematic overview depicting mapping of UCI on PUSCH according to prior art;
[0043] Fig. 3 shows a wireless communication network according to embodiments herein;
[0044] Fig. 4 shows a combined signaling scheme and flowchart according to some embodiments herein;
[0045] Fig. 5 shows a flowchart depicting a method performed by a UE according to embodiments herein;
[0046] Fig. 6 shows a flowchart depicting a method performed by a radio network node according to embodiments herein;
[0047] Fig. 7 shows a combined signaling scheme and flowchart according to some embodiments herein;
[0048] Fig. 8 shows a flowchart depicting a method performed by a UE according to some embodiments herein;
[0049] Fig. 9 shows a flowchart depicting a method performed by a UE according to some embodiments herein;
[0050] Fig. 10 shows a flowchart depicting a method performed by a UE according to some embodiments herein; Fig. 11 shows a schematic overview depicting a UE according to embodiments herein:
[0051] Fig. 12 shows a schematic overview depicting a radio network node according to embodiments herein:
[0052] Fig. 13 shows an example of a communication system QQ100 in accordance with some embodiments;
[0053] Fig. 14 shows a UE QQ200 in accordance with some embodiments;
[0054] Fig. 15 shows a network node QQ300 in accordance with some embodiments;
[0055] Fig. 16 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 13, in accordance with various aspects described herein;
[0056] Fig. 17 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized; and
[0057] Fig. 18 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.
[0058] DETAILED DESCRIPTION
[0059] Embodiments herein relate to wireless communication networks in general. Fig. 3 is a schematic overview depicting a wireless communication network 1 . The wireless communication network 1 comprises one or more ANs, such as RANs or wired ANs, and one or more CNs. The communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent wired and wireless networks such as Wi-Fi, new radio (NR), 6G, other existing wired or wireless networks, and further developments of existing wireless communications systems such as e.g., LTE or WCDMA.
[0060] In the wireless communication network 1, a UE 10, for example, a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and / or a wireless terminal, is comprised communicating via the one or more AN to other UEs or one or more CNs. It should be understood by the skilled in the art that “UE” is a nonlimiting term which means any terminal, wireless communications terminal, Internet of Things (loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.
[0061] The wireless communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a first service area 11 or first cell, of a first Radio Access Technology (RAT), such as WiFi, NR, LTE, or similar. The radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the radio network node depending e.g. on the first radio access technology and terminology used. The radio network node 12 may be an access node such as a WiFi-modern or a radio network node and may be referred to as a serving radio network node, master node, or serving secondary network node, wherein the service area may be referred to as a source cell. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.
[0062] According to embodiments herein the UE 10 transmits a capability indication to the radio network node 12, wherein the capability indication indicates a capability to apply one or more priority rules. The one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for the computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions. The one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions. Thus, allocation of resources for uplink data transmissions of the second type of uplink data transmissions is prioritized over allocation of resources for uplink data transmissions of the first type of uplink data transmissions. As an example, uplink data transmissions may be handled before CSI type data transmissions for training the computational model. The computational model may be a ML model or similar for gathering data for CSI feedback, beam management and / or positioning.
[0063] The UE 10 further applies the priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions. Embodiments herein disclose the messaging or signaling from the UE to the network, the capability of the UE to apply the new priority rule or rules for allocating UCI resources. Some embodiments herein disclose the messaging from the radio network node 12 to the UE 10 indicating the priority rule or rules that should be applied by the UE 10 when determining the information to be included in the scheduled UCI resources. It is also disclosed herein a definition of a logic to be executed at the UE 10 to determine the information to be included in the scheduled UCI resources based on the newly defined priority rule or rules. In addition, the messaging, from the UE 10 to the radio network node 12, indicating the information included in scheduled UCI resources, i.e. , the priority rule applied, is also herein disclosed.
[0064] The one or more priority rules allow UEs to prioritize uplink data transmissions with certain characteristics over non-time-sensitive UCI-based data collection processes on PUSCH, therefore minimizing the impact of the latter on the network performance.
[0065] Fig. 4 is a combined signaling scheme and flowchart according to some embodiments herein.
[0066] Action 401. The UE 10 transmits the capability indication to the radio network node 12. That is, the UE 10 may signal in a message that the UE 10 is capable of applying a priority rule prioritizing the second type of uplink data transmissions, such as payload data or Type I CSI (having a smaller overhead than Type II CSI), over the first type of uplink data transmissions, such as data for data collection for training a ML model for CSI feedback, beam management and / or positioning.
[0067] Action 402. The radio network node 12 may determine priority rule to use for the UE and may transmit to the UE 10, the indication of a determined priority rule.
[0068] Action 403. The radio network node 12 schedules uplink data transmissions for the UE 10. For example, the radio network node 12 may schedule PUSCH and trigger CSI-feedback reporting. For example, schedule PUSCH for subsequent downlink scheduling and CSI-feedback for data collection, e.g., when the entity controlling AI / ML model LCM decides that data acquisition is required for, e.g., training, retraining, or performance monitoring.
[0069] Action 404. The UE 10 applies the priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions when using UCI resources. Since the priority rule indicates that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions, the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions.
[0070] Action 405. The UE 10 may thus transmit UL data wherein the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions. The UE 10 may further indicate, with an apply indication, what priority rule the UE 10 used.
[0071] Fig. 5 illustrates an example of a method performed by the UE 10 for handling communication of the UE 10 in the wireless communication network 1 in accordance with embodiments herein. Optional actions are shown using a dashed line. The acts in Fig. 5 may be performed in any suitable order.
[0072] Action 501. The UE 10 transmits the capability indication to the radio network node 12, wherein the capability indication indicates the capability to apply one or more priority rules, wherein the one or more priority rules indicate the allocation of uplink resources for the first type of uplink data transmissions related to data collection for the computational model, relative to the allocation of uplink resources for the second type of uplink data transmissions, wherein the one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions.
[0073] Action 502. The UE 10 may obtain an indication of the priority rule to apply. The indication may be received from the radio network node 12 or it may be retrieved internally. The UE 10 may obtain the indication by receiving, from the radio network node 12, a specific RS configuration for the UE and / or by receiving a specific set of RSs to the UE 10. Thus, the specific RS configuration or the specific set of RSs may indicate the priority rule to apply. The indication may be received: in a message that allocates PUSCH resources to the UE; in a message that triggers CSI feedback to be carried on PUSCH; in a message that configures RS measurement configuration and / or CSI reporting configuration; in a message that configures a data collection process; and / or in a dedicated configuration message. The obtained indication may indicate an order to apply the one or more priority rules, such as a list or similar. The obtained indication may indicate to autonomously adjust one or more parameters pertaining to a configuration of CSI feedback, and / or apply a default priority rule.
[0074] Action 503. The UE 10 may receive a rule indication indicating one or more of the following: the one or more priority rules to be applied for a subsequent CSI feedback report, or • the one or more priority rules to be applied until indicated otherwise,
[0075] • the one or more priority rules to be applied until implicitly indicated via a configuration message,
[0076] • the one or more priority rules to be applied for a duration of a data collection process, and / or
[0077] • the one or more priority rules to be applied for a given duration.
[0078] Action 504. The UE 10 further applies the priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions. The second type of uplink data transmissions may comprise payload data and / or a CSI type not related to data collection for the computational model, and the first type of uplink data transmissions may comprise a CSI type related to data collection for the computational model. Thus, the UE 10 may perform the second type of uplink data transmissions before the first type of uplink data transmissions.
[0079] The one or more priority rules may indicate that the UE 10 is to reduce a quality of, or omit, CSI feedback in order to allocate a larger amount of a type of uplink data within available PUSCH resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model. Thus, UEs may be allowed not to transmit CSI feedback in spite of it being requested. The radio network node 12 may indicate this possibility when, e.g., it is only interested in gathering CSI for data collection purposes."
[0080] Action 505. The UE 10 may further transmit to the radio network node an apply indication indicating the applied priority rule. The apply indication may comprise UCI content for indicating the selected priority rule, which may have higher priority than data and CSI report. The UE 10 may also indicate the size of each of the uplink data transmissions. The apply indication may comprise a certain type of data transmission indicating the applied priority rule.
[0081] Fig. 6 illustrates an example of a method performed by the radio network node 12 for handling communication of the UE 10 in the wireless communication network 1 in accordance with embodiments herein. Optional actions are shown using a dashed line. The acts in Fig. 6 may be performed in any suitable order. Action 601. The radio network node 12 receives the capability indication from the UE 10, wherein the capability indication indicates the capability to apply the one or more priority rules, wherein the one or more priority rules indicate the allocation of uplink resources for the first type of uplink data transmissions related to data collection for the computational model, relative to the allocation of uplink resources for the second type of uplink data transmissions. The one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions. The one or more priority rules may indicate that the UE 10 is to reduce a quality of, or omit, CSI feedback in order to allocate a larger amount of a type of uplink data within available PUSCH resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model.
[0082] Action 602. The radio network node 12 may transmit to the UE 10, the indication of a determined one or more priority rules out of the one or more priority rules to apply. The radio network node 12 may indicate the indication by signaling the specific RS configuration to the UE and / or by transmitting the specific set of RSs to the UE 10. The indication may indicate an order to apply the one or more priority rules, such as a list of priority rules. The list of priority rules may comprise a first priority rule allowing the UE to reduce quantity of CSI related data for data collection and a second priority rule allowing the UE 10 to omit transmission of CSI related to data collection for the computational model. The indication may be transmitted: in a message that allocates PUSCH resources to the UE 10; in a message that triggers CSI feedback to be carried on PUSCH; in a message that configures RS measurement configuration and / or CSI reporting configuration; in a message that configures a data collection process; and / or in a dedicated configuration message. If the radio network node 12 is only interested in gathering CSI for data collection purposes, e.g., for training / retraining / evaluating the performance of an ML model that uses such CSI, but may still prioritize not harming the performance of certain, or all, types of data communication, based on, e.g., service level agreements,! the radio network node 12 may determine set of priority rules where the UE is allowed not to transmit the triggered CSI feedback when the UE has uplink data (UL- SCH) with certain characteristics in the buffer. In another example, the radio network node 12 may be interested in gathering CSI both for subsequent single-user (SU)-MIMO downlink scheduling purposes, i.e. , Type I CSI, and data collection purposes, e.g., Type II CSI or a new type of CSI, e.g., for training / retraining / evaluating the performance of an ML model that uses such CSI, but may still prioritize not harming the performance of certain, or all, types of data communication, based on, e.g., service level agreements, the radio network node 12 may indicate to the UE to prioritize the CSI feedback of Type I CSI over the CSI feedback of Type II CSI if there are not enough resources to transmit both the CSI feedback of Type II CSI and the communication data.
[0083] Action 603. The radio network node 12 may transmit the rule indication indicating one or more of the following:
[0084] • the one or more priority rules to be applied for a subsequent CSI feedback report, or
[0085] • the one or more priority rules to be applied until indicated otherwise,
[0086] • the one or more priority rules to be applied until implicitly indicated via a configuration message,
[0087] • the one or more priority rules to be applied for a duration of a data collection process, and / or
[0088] • the one or more priority rules to be applied for a given duration.
[0089] This rule indication may be transmitted together with the indication of the determined one or more priority rules or transmitted separately.
[0090] Action 604. The radio network node 12 schedules uplink data transmissions for the UE 10.
[0091] Action 605. The radio network node 12 may receive from the UE 10 the apply indication indicating the applied priority rule. The UE can also indicate the size of each of the uplink data transmissions. The apply indication of the applied priority rule may be derived by the radio network node 12 based on the indication of what type of information each of the uplink data transmission types contains. Thus, the apply indication may comprise a certain type of data transmission indicating the applied priority rule.
[0092] Action 606. The radio network node 12 further receives from the UE the first type of uplink data transmissions and / or the second type of uplink data transmissions.
[0093] Action 607. The radio network node 12 decodes the first type of uplink data transmissions and / or the second type of uplink data transmissions taking the capability indication into account. The radio network node 12 may decode the first type of uplink data transmissions and / or the second type of uplink data transmissions based on the apply indication. Thus, the radio network node 12 decodes the first type of uplink data transmissions and / or the second type of uplink data transmissions taking the capability indication and / or the apply indication into account. The second type of uplink data transmissions may comprise payload data and / or a CSI type not related to data collection for the computational model, and the first type of uplink data transmissions comprises a CSI type related to data collection for the computational model.
[0094] In embodiments herein, upon triggering CSI feedback to be carried on PLISCH for at least data collection purposes, the radio network node 12 may indicate to the UE 10 whether it is allowed to
[0095] • Utilize the allocated PUSCH resources to transmit uplink data, e.g., UL-SCH data, instead of the triggered CSI feedback. In other words, UEs may be allowed not to transmit CSI feedback in spite of it being requested. o The network may indicate this possibility when, e.g., it is only interested in gathering CSI for data collection purposes.
[0096] • Reduce the quality of the CSI feedback, e.g., feeding back Type I CSI, also referred to as Type I PM I, instead of Type II CSI, or Type II CSI or a new type tailored for data acquisition with lower resolution, in order to allocate a larger amount of uplink data (UL-SCH) within the available PUSCH resources. In other words, UEs may be allowed to prioritize the transmission of certain types of uplink data (UL-SCH) over the transmission of certain types of CSI feedback. o The network may indicate this possibility when, e.g., it is interested in gathering CSI both for subsequent SU-MIMO downlink scheduling purposes and data collection purposes. In these cases, even if the network triggers a high-quality CSI feedback report (e.g., resembling Type II CSI), the UE may be allowed to transmit back a lower-quality CSI report (e.g., Type I CSI) when it has uplink data in its buffer.
[0097] The determination of parameters that configure the CSI feedback sent by the UE may be i) indicated by the network, or ii) autonomously adjusted by the UE based on their proprietary implementation and / or specification rules.
[0098] The one or more priority rules to be applied by the UE may consider the characteristics of the data in the uplink buffer. For instance, different priorities may be applied depending on the Quality of Service (QoS) identifiers or size of the data.
[0099] Throughout the description, the concept ‘network’ may refer to one of a generic network node, a gNB (or the corresponding node in a 6G network), a base station, a unit within the base station to handle at least some ML operation, a relay node, a core network node, a core network node that handle at least some ML operations, or a device supporting device to device (D2D) communication.
[0100] Fig. 7 shows actions of a proposed method according to an example.
[0101] Action 70: The UE 10 signals capability of applying new priority rules when using UCI resources.
[0102] In some embodiments, the network, i.e. , radio network node 12, may request an explicit UE capability message. Such a request message may request a complete or partial list of the set of priority rules that may be applied by the UE 10. The UE 10 would then respond with a UE capability information according to the request.
[0103] In some embodiments, the UE’s capability of applying new priority rules may be bundled with one or more AI / ML based features. As an example, the standard specification may require that a UE supporting an AI / ML-based CSI prediction feature shall also support the new priority rules when multiplexing UCI with UL data on PUSCH. Hence, the network can infer whether the UE 10 supports the new priority rule based on whether it supports the AI / ML-based CSI prediction feature in its UE capability reporting.
[0104] In other embodiments, the network may infer whether the UE 10 supports the application of certain priority rules depending on, e.g., their support of a specific specification version, e.g., 3GPP Release 20, or the UE chipset model, e.g., a certain type of chipset.
[0105] Action 71 : The radio network node 12 indicates to the UE 10 the priority rules to be applied when using UCI resources.
[0106] Configuration of the priority rules applied by the UE 10:
[0107] • In some embodiments, the network will indicate to the UE 10 to apply a specific set of priority rules supported by the standard specification. o For instance, the network may indicate the order in which a subset of rules available in the standard specification should be applied. o As another example, a subset of priority rules may be defined for a specific RS configuration. The network may indicate to the UE 10 to apply a specific set of priority rules by signaling a specific RS configuration to the UE 10 and / or by transmitting a specific set of RSs to the UE 10. The RS configuration / transmitting may be associated with data collection for model training, retaining, updating and / or monitoring. o As another example, a subset of priority rules may be defined for a data collection procedure and / or configuration associated to one or more AI / ML- based features. The network may indicate to the UE 10 to apply a specific set of priority rules by data collection related signaling, e.g., signaling to initiate data collection procedure, signaling to trigger UE reporting its collected data.
[0108] • In other embodiments, the UE 10 may be allowed to autonomously — based on their proprietary logic — adjust one or more parameters pertaining the configuration of the CSI feedback. o In this case, the network may not be fully aware of the specific priority rules applied by the UE 10 but may still be able to indicate high-level intents declared in the standard specification, e.g., apply priority rules applicable for a subsequent SU-MIMO transmission.
[0109] • In yet other embodiments, the network may not explicitly indicate the priority rules to be applied by the UE 10. In this case, the UE 10 may apply one or more default priority rules, while the default priority rules can be the legacy priority rules where data has the lowest priority or the newly proposed rules where data has higher priority.
[0110] Duration of the indicated priority rules:
[0111] In some embodiments, the network will indicate to the UE 10 that the indicated set of priority rules should:
[0112] • only be applied for a subsequent CSI feedback report,
[0113] • be applied until indicated otherwise,
[0114] • be applied until implicitly indicated via a (re)configuration message, e.g., the RS configuration is changed from the specific RS configuration to another RS configuration,
[0115] • be applied for the duration of an overarching data collection process, and / or
[0116] • be applied for a given duration. Such duration may be specified in, e.g., seconds, number of slots, or number of CSI feedback reports, or associated with a timer.
[0117] How or location of the indication:
[0118] The network may indicate to the UE 10 the priority rules to be applied
[0119] • in the message that allocates PUSCH resources to the UE, or
[0120] • in the message that triggers CSI feedback to be carried on PUSCH, or
[0121] • in a message(s) that configure(s) RS measurement configuration and / or CSI reporting configuration, or
[0122] • in a message that configures an overarching data collection process, or • in a dedicated configuration message.
[0123] Such messages may be contained, e.g., within RRC messages, within MAC Control Elements (CE), or Downlink Control Information (DCI).
[0124] Action 72. The radio network node 12 may then schedule PLISCH and trigger CSI feedback.
[0125] Action 73: After scheduling PLISCH and triggering CSI feedback, UE applies specified priority rules when using UCI resources.
[0126] The priority rules applied by the UE indicate the order in which the UE should allocate the available UCI resources (i.e. , the priority level in which different information should be assigned).
[0127] Action 74: UE indicates selected priority rules and, as per the application of the indicated priority rules, transmits 1) data and / or CSI feedback within UCI resources.
[0128] In one embodiment, a new UCI content for indicating the selected priority rule or rules can be defined, which may have higher priority than data and CSI report.
[0129] An example of the logic utilized by the UE for a given set of priority rules is illustrated in Fig. 8, and is described in the following:
[0130] Fig. 8 shows some logic executed by the UE 10 to allocate information within the UCI resources.
[0131] First, the UE 10 may first determine the uplink data and / or CSI feedback that may be allocated at a given priority level. The identification may be at least based on one or more of the following parameters:
[0132] • Uplink data or payload data. The presence of uplink data in the buffer. In some embodiments, the data that may be allocated at a given priority level may have specific features. These features may be related to, for example, o a QoS identifier, o a time-related metric, i.e., total time that the data has been in the buffer, remaining time to transmit the data within the deadline,
[0133] • CSI feedback. o Type (e.g., Type I, Type II, or a new CSI type in the specification). o Type-specific parameters (e.g., the number of selected beams for reporting in CSI Type II).
[0134] Priority level k = 1
[0135] Available PLISCH resources. # of priority levels K
[0136] Action 801. The UE 10 may determine uplink data that may be allocated in priority level k based on, e.g., QoS identifier, time-related metric.
[0137] Action 802. The UE 10 may determine CSI feedback that may be allocated in priority level k based on, e.g., type and type-specific parameters.
[0138] Action 803. The UE 10 may determine size (e.g., number of PUSCH resources) required to convey the information (uplink data and / or CSI feedback) in priority level k
[0139] Action 804. The UE 10 may check size required to convey information in priority level k < available PUSCH resources?
[0140] Action 805. That being the case, the UE 10 may allocate information (uplink data and / or CSI feedback) in priority level k
[0141] Action 806. The UE 10 may check k < K?
[0142] Action 807. That being the case, the UE 10 may increase k = k + 1.
[0143] Action 808. The UE 10 may calculate number of remaining PUSCH resources as available PUSCH resources minus allocated resources in priority level k - 1.
[0144] As shown in Fig. 8, once the relevant uplink data and / or CSI feedback to be allocated at a given priority level has been identified, the UE 10 may compute their size, i.e. , the number resource elements required to convey the relevant uplink data or CSI feedback, and may determine whether the relevant uplink data or CSI feedback can be allocated within the remaining number of PUSCH resources available. Subsequently, the UE 10 will execute the next priority level, if existing.
[0145] Two illustrative embodiments of the priority rules that may be applied by the UE 10 are shown in Fig. 9 and Fig. 10. For illustrative purposes, the number of PUSCH resources (REs) for i) data, for ii) Type II CSI reporting, for iii) Type I CSI reporting, and iv) total initially available are i) 40 REs, ii) 90 REs, iii) 20 REs, and 100 REs, respectively.
[0146] Fig. 9 shows a set of priority rules where the UE 10 is allowed not to transmit the triggered CSI feedback when the UE 10 has uplink data with certain characteristics in the buffer, e.g., mission critical delay sensitive signaling data see 3GPP TS 23.501 v.17.7.0, “System architecture for the 5G System (5GS); Stage 2”, Dec. 2022, since the remaining PUSCH resource after transmitting data, i.e., 100 - 90 = 10 REs, is not sufficient to transmit the CSI report with the resolution / quality required for data collection purposes. In other words, UEs may be allowed not to transmit CSI feedback in spite of it being requested. The network may indicate this possibility when, e.g., it is only interested in gathering CSI for data collection purposes.
[0147] Priority level k = 1
[0148] Available PLISCH resources =100
[0149] # of priority levels K=2
[0150] Action 901. The UE 10 may identify uplink data that has QoS identifier with mission critical delay sensitive signaling in the buffer.
[0151] Action 902. The UE 10 may check size (e.g., number of PUSCH resources) required to convey the identified in priority level k = 1 is 40 PUSCH resources.
[0152] Action 903. The UE 10 may check size required to convey information in priority level k < available PUSCH resources.
[0153] Action 904. That being the case, the UE 10 may allocate uplink information in priority level k = 1.
[0154] Action 905. The UE 10 may check k < K (1 < 2).
[0155] Action 906. That being the case, the UE 10 may determine number of remaining PUSCH resources = 100 - 40 = 60.
[0156] Action 907. That being the case, the UE 10 may increase k = k + 1.
[0157] Action 908. The UE 10 may identify CSI feedback to be allocated in priority level k = 2: Type II (size = 90 resources).
[0158] Action 909. The UE 10 may check size (e.g., number of PUSCH resources) required to convey the identified in priority level k = 2 is 90 PUSCH resources.
[0159] Action 910. The UE 10 may check size required to convey information in priority level k < available PUSCH resources?
[0160] Action 911. The UE 10 may check k < K (2 < 2)?
[0161] Thus, Fig. 9 shows some embodiment of the proposed method where the priority rules allow the UE not to transmit the triggered CSI feedback when the UE 10 has mission critical delay sensitive signaling uplink data in the buffer.
[0162] Fig. 10 shows a set of priority rules where the UE 10 is allowed to reduce the quality of the CSI feedback in order to allocate a larger amount of certain types of uplink data within the available PUSCH resources, e.g., mission critical delay sensitive signaling data, see 3GPP TS 23.501 v.17.7.0. In other words, UEs may be allowed to prioritize the transmission of certain types of uplink data (UL-SCH) over the transmission of certain types of CSI feedback. o The network may indicate this possibility when, e.g., it is interested in gathering CSI both for subsequent SU-MIMO downlink scheduling purposes and data collection purposes.
[0163] Priority level k = 1
[0164] Available PLISCH resources =100
[0165] # of priority levels K=2
[0166] Action 1001. The UE 10 may identify uplink data that has QoS identifier with mission critical delay sensitive signaling in the buffer (size = 40 resources).
[0167] Action 1002. The UE 10 may identify CSI feedback to be allocated in priority level k = 1: Type II (size = 90 resources).
[0168] Action 1003. The UE 10 may identify size (e.g., number of PUSCH resources) required to convey the identified in priority level k = 1 is 130 (40+90) PUSCH resources.
[0169] Action 1004. The UE 10 may check k < K (1 < 2)?
[0170] Action 1005. That being the case, the UE 10 may increase k = k + 1.
[0171] Action 1006. The UE 10 may identify uplink data that has QoS identifier, mission critical delay sensitive signaling, in the buffer (size = 40 resources).
[0172] Action 1007. The UE 10 may identify CSI feedback to be allocated in priority level k = 2: Type I (size = 20 resources).
[0173] Action 1008. The UE 10 may determine size (e.g., number of PUSCH resources) required to convey the identified in priority level k = 2 is 60 (40+20) PUSCH resources.
[0174] Action 1009. The UE 10 may check that size required to convey information in priority level k < available PUSCH resources?
[0175] Action 1010. The UE 10 may allocate uplink information in priority level k = 2.
[0176] Action 1011. The UE 10 may check k < K (2 < 2)?
[0177] Thus, Fig. 10 shows some embodiments of the proposed method where the priority rules allow the UE 10 to transmit reduced quality CSI feedback, for example, Type I instead of the network-requested Type II, when the UE 10 has mission critical delay sensitive signaling uplink data in the buffer.
[0178] In other embodiments, the CSI report may be punctured at a given priority level in order to fit within the available PUSCH resources. For example, if a Type II or a new type of CSI report for data collections is configured, in case there is not sufficient PUSCH resources for CSI report after high priority data is transmitted, the CSI report may be omitted in some parts according to a pre-defined omission rule. Fig. 11 depicts embodiment of the UE 10 for handling communication of the UE 10 in the wireless communication network 1 according to embodiments herein.
[0179] The UE 10 may comprise processing circuitry 1101 , e.g. one or more processors, configured to perform the methods herein.
[0180] The UE 10 and / or the processing circuitry 1101 is configured to transmit the capability indication to the radio network node 12, wherein the capability indication indicates the capability to apply one or more priority rules. The one or more priority rules indicate the allocation of uplink resources for the first type of uplink data transmissions related to data collection for the computational model, relative to the allocation of uplink resources for the second type of uplink data transmissions. The one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions.
[0181] The UE 10 and / or the processing circuitry 1101 is configured to apply the priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions.
[0182] The UE 10 and / or the processing circuitry 1101 may be configured to obtain the indication of the priority rule to apply.
[0183] The UE 10 and / or the processing circuitry 1101 may be configured to obtain the indication by receiving the indication from the radio network node 12.
[0184] The UE 10 and / or the processing circuitry 1101 may be configured to obtain the indication by receiving from the radio network node 12 a specific RS configuration for the UE and / or by receiving a specific set of RSs to the UE.
[0185] The obtained indication may indicate an order to apply the one or more priority rules.
[0186] The obtained indication may indicate to autonomously adjust one or more parameters pertaining to a configuration of CSI feedback, and / or apply a default priority rule.
[0187] The indication may be received: in a message that allocates PUSCH resources to the UE; in a message that triggers CSI feedback to be carried on PUSCH; in a message that configures RS measurement configuration and / or CSI reporting configuration; in a message that configures a data collection process; and / or in a dedicated configuration message.
[0188] The UE 10 and / or the processing circuitry 1101 may be configured to receive a rule indication indicating one or more of the following: • the one or more priority rules to be applied for a subsequent CSI feedback report, or
[0189] • the one or more priority rules to be applied until indicated otherwise,
[0190] • the one or more priority rules to be applied until implicitly indicated via a configuration message,
[0191] • the one or more priority rules to be applied for a duration of a data collection process, and / or
[0192] • the one or more priority rules to be applied for a given duration.
[0193] The one or more priority rules may indicate that the UE is to reduce a quality of, or omit, CSI feedback in order to allocate a larger amount of a type of uplink data within available PLISCH resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model.
[0194] The UE 10 and / or the processing circuitry 1101 may be configured to transmit to the radio network node 12 the apply indication indicating the applied priority rule.
[0195] The second type of uplink data transmissions may comprise payload data and / or a CSI type not related to data collection for the computational model, and the first type of uplink data transmissions may comprise a CSI type related to data collection for the computational model.
[0196] The UE 10 further comprises a memory 1105. The memory 1105 comprises one or more units to be used to store data on, such as indications, apply indication, priority rules, feedback indication, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the UE 10 may comprise a communication interface 1106 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.
[0197] The methods according to the embodiments described herein for the UE 10 are respectively implemented using e.g., a computer program product 1107 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. The computer program product 1107 may be stored on a computer-readable storage medium 1108, e g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1108, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a UE 10 for handling communication in a wireless communication network, wherein the UE 10 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the UE 10 is operative to perform any of the methods herein.
[0198] Fig. 12 depicts embodiment of the radio network node 12 for handling communication of the UE 10 in the wireless communication network 1 according to embodiments herein.
[0199] The radio network node 12 may comprise processing circuitry 1201 , e.g. one or more processors, configured to perform the methods herein.
[0200] The radio network node 12 and / or the processing circuitry 1201 is configured to receive the capability indication from the UE 10, wherein the capability indication indicates the capability to apply one or more priority rules. The one or more priority rules indicate the allocation of uplink resources for the first type of uplink data transmissions related to data collection for the computational model, relative to the allocation of uplink resources for the second type of uplink data transmissions, wherein the one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions.
[0201] The radio network node 12 and / or the processing circuitry 1201 is configured to schedule uplink data transmissions for the UE.
[0202] The radio network node 12 and / or the processing circuitry 1201 is configured to receive from the UE the first type of uplink data transmissions and / or the second type of uplink data transmissions.
[0203] The radio network node 12 and / or the processing circuitry 1201 is configured to decode the first type of uplink data transmissions and / or the second type of uplink data transmissions taking the capability indication into account.
[0204] The radio network node 12 and / or the processing circuitry 1201 may be configured to transmit to the UE, the indication of the determined one or more priority rules out of the one or more priority rules to apply.
[0205] The radio network node 12 and / or the processing circuitry 1201 may be configured to transmit the indication by signaling the specific RS configuration to the UE and / or by transmitting the specific set of RSs to the UE.
[0206] The indication may indicate an order to apply the one or more priority rules. The radio network node 12 and / or the processing circuitry 1201 may be configured to transmit the indication: in the message that allocates PLISCH resources to the UE; in the message that triggers CSI feedback to be carried on PLISCH; in the message that configures RS measurement configuration and / or CSI reporting configuration; in the message that configures the data collection process; and / or in the dedicated configuration message.
[0207] The radio network node 12 and / or the processing circuitry 1201 may be configured to transmit the rule indication indicating one or more of the following:
[0208] • the one or more priority rules to be applied for a subsequent channel state information, CSI, feedback report, or
[0209] • the one or more priority rules to be applied until indicated otherwise,
[0210] • the one or more priority rules to be applied until implicitly indicated via a configuration message,
[0211] • the one or more priority rules to be applied for a duration of a data collection process, and / or
[0212] • the one or more priority rules to be applied for a given duration.
[0213] The one or more priority rules may indicate that the UE 10 is to reduce a quality of, or omit, CSI feedback in order to allocate a larger amount of a type of uplink data within available PUSCH resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model.
[0214] The radio network node 12 and / or the processing circuitry 1201 may be configured receive from the UE 10 the apply indication indicating an applied priority rule, and to decode the first type of uplink data transmissions and / or the second type of uplink data transmissions based on the apply indication.
[0215] The second type of uplink data transmissions may comprise payload data and / or a CSI type not related to data collection for the computational model, and the first type of uplink data transmissions may comprise the CSI type related to data collection for the computational model.
[0216] The radio network node 12 further comprises a memory 1205. The memory 1205 comprises one or more units to be used to store data on, such as indications, apply indication, priority rules, feedback indication, collected data, ML model, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the radio network node 12 may comprise a communication interface 1206 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.
[0217] The methods according to the embodiments described herein for the radio network node 12 are respectively implemented using e.g., a computer program product 1207 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12. The computer program product 1207 may be stored on a computer-readable storage medium 1208, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1208, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a radio network node 12 for handling communication in a wireless communication network, wherein the radio network node 12 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the radio network node 12 is operative to perform any of the methods herein.
[0218] In some embodiments a more general term “radio network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a wireless device, wired device and / or with another network node. Examples of network nodes are, router, modem, server, UE, NodeB, master (M)eNB, secondary (S)eNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc.
[0219] In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), internet of things (loT) capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.
[0220] Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
[0221] As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single Application-Specific Integrated Circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.
[0222] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, Digital Signal Processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.
[0223] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read-Only Memory (ROM), Random-Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
[0224] Fig. 13 shows an example of a communication system QQ100 in accordance with some embodiments.
[0225] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110 or network node 12), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node, being examples of the entities herein, is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.
[0226] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near- real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112 or UE 10) to the core network QQ106 over one or more wireless connections.
[0227] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0228] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.
[0229] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0230] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0231] As a whole, the communication system QQ100 of Fig. 13 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
[0232] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0233] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0234] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0235] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0236] Fig. 14 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0237] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0238] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 14. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0239] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).
[0240] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0241] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.
[0242] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.
[0243] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual inline memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.
[0244] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0245] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0246] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0247] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0248] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Nonlimiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Fig. 14.
[0249] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0250] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0251] Fig. 15 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O- DU, O-CU).
[0252] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0253] Other examples of network nodes include multiple transmission point (multi- TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0254] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.
[0255] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.
[0256] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.
[0257] The memory QQ304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.
[0258] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio frontend circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0259] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).
[0260] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.
[0261] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0262] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0263] Embodiments of the network node QQ300 may include additional components beyond those shown in Fig. 15 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.
[0264] Fig. 16 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 13, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.
[0265] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Fig. 14 and 15, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.
[0266] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0267] Fig. 17 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0268] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0269] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.
[0270] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0271] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.
[0272] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.
[0273] Fig. 18 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 13 and / or UE QQ200 of Figure 14), network node (such as network node QQ110a of Figure 13 and / or network node QQ300 of Figure 15), and host (such as host QQ116 of Figure 13 and / or host QQ400 of Figure 16) discussed in the preceding paragraphs will now be described with reference to Figure 18.
[0274] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.
[0275] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 13) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.
[0276] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.
[0277] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0278] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.
[0279] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.
[0280] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve optimize UL transmissions and thereby provide benefits such as reduced user waiting time, better energy savings, better responsiveness or similar.
[0281] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.
[0282] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.
[0283] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0284] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non- transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
[0285] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.
[0286]
Claims
CLAIMS1. A method performed by a User equipment, UE, (10) for handling communication of the UE (10) in a wireless communication network (1), the method comprising: transmitting (501) a capability indication to a radio network node (12), wherein the capability indication indicates a capability to apply one or more priority rules, wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions, wherein the one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions; and applying (504) a priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions.
2. The method according to claim 1 , further comprising obtaining (502) an indication of the priority rule to apply.
3. The method according to claim 2, wherein obtaining (502) the indication comprises receiving the indication from the radio network node (12).
4. The method according to claim 3, wherein obtaining (502) the indication comprises receiving from the radio network node (12) a specific reference signal, RS, configuration for the UE and / or by receiving a specific set of RSs to the UE.
5. The method according to any of the claims 2-4, wherein the obtained indication indicates an order to apply the one or more priority rules.
6. The method according to claim 2, wherein the obtained indication indicates to autonomously adjust one or more parameters pertaining to a configuration of channel state information feedback, and / or apply a default priority rule.
7. The method according to any of the claims 2-6, wherein the indication is received: in a message that allocates physical uplink shared channel, PLISCH, resources to the UE; in a message that triggers channel state information, CSI, feedback to be carried on PLISCH; in a message that configures reference signal, RS, measurement configuration and / or CSI reporting configuration; in a message that configures a data collection process; and / or in a dedicated configuration message.
8. The method according to any of the claims 1-7, further comprising receiving (503) a rule indication indicating one or more of the following:• the one or more priority rules to be applied for a subsequent channel state information, CSI, feedback report, or• the one or more priority rules to be applied until indicated otherwise,• the one or more priority rules to be applied until implicitly indicated via a configuration message,• the one or more priority rules to be applied for a duration of a data collection process, and / or• the one or more priority rules to be applied for a given duration.
9. The method according to any of the claims 1-8, wherein the one or more priority rules indicate that the UE is to reduce a quality of, or omit, channel state information, CSI, feedback in order to allocate a larger amount of a type of uplink data within available physical uplink shared channel, PUSCH, resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model.
10. The method according to any of the claims 1-9, further comprisingtransmitting (505) to the radio network node an apply indication indicating the applied priority rule.
11. The method according to any of the claims 1-10, wherein the second type of uplink data transmissions comprises payload data and / or a channel state information, CSI, type not related to data collection for the computational model, and the first type of uplink data transmissions comprises a CSI type related to data collection for the computational model.
12. A method performed by a radio network node (12) for handling communication of a user equipment, UE, (10) in a wireless communication network (1), the method comprising: receiving (601) a capability indication from the UE (10), wherein the capability indication indicates a capability to apply one or more priority rules, wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions, wherein the one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions; scheduling (604) uplink data transmissions for the UE; receiving (606) from the UE the first type of uplink data transmissions and / or the second type of uplink data transmissions; and decoding (607) the first type of uplink data transmissions and / or the second type of uplink data transmissions taking the capability indication into account.
13. The method according to claim 12, further comprising transmitting (602) to the UE, an indication of a determined one or more priority rules out of the one or more priority rules to apply.
14. The method according to claim 13, wherein the radio network node indicates the indication by signaling a specific reference signal, RS, configuration to the UE and / or by transmitting a specific set of RSs to the UE.
15. The method according to any of the claims 13-14, wherein the indication indicates an order to apply the one or more priority rules.
16. The method according to any of the claims 13-15, wherein the indication is transmitted: in a message that allocates physical uplink shared channel, PLISCH, resources to the UE; in a message that triggers channel state information, CSI, feedback to be carried on PUSCH; in a message that configures reference signal, RS, measurement configuration and / or CSI reporting configuration; in a message that configures a data collection process; and / or in a dedicated configuration message.
17. The method according to any of the claims 12-16, further comprising transmitting (603) a rule indication indicating one or more of the following:• the one or more priority rules to be applied for a subsequent channel state information, CSI, feedback report, or• the one or more priority rules to be applied until indicated otherwise,• the one or more priority rules to be applied until implicitly indicated via a configuration message,• the one or more priority rules to be applied for a duration of a data collection process, and / or• the one or more priority rules to be applied for a given duration.
18. The method according to any of the claims 12-17, wherein the one or more priority rules indicate that the UE is to reduce a quality of, or omit, channel state information, CSI, feedback in order to allocate a larger amount of a type of uplink data within available physical uplink shared channel, PUSCH, resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model.
19. The method according to any of the claims 12-18, further comprising receiving (605) from the UE (10) an apply indication indicating an applied priority rule, and decoding (607) the first type of uplink data transmissions and / or the second type of uplink data transmissions based on the apply indication.
20. The method according to any of the claims 12-19, wherein the second type of uplink data transmissions comprises payload data and / or a channel state information, CSI, type not related to data collection for the computational model, and the first type of uplink data transmissions comprises a CSI type related to data collection for the computational model.
21. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-20, as performed by the radio network node and the UE, respectively.
22. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-20, as performed by the radio network node and the UE, respectively.
23. A User equipment, UE, (10) for handling communication of the UE (10) in a wireless communication network (1), wherein the UE (10) is configured to: transmit a capability indication to a radio network node (12), wherein the capability indication indicates a capability to apply one or more priority rules, wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplink data transmissions, wherein the one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions; andapply a priority rule out of the one or more priority rules for allocating uplink resources for transmitting the first type of uplink data transmissions and / or the second type of uplink data transmissions.
24. The UE (10) according to claim 23, wherein the UE is further configured to obtain an indication of the priority rule to apply.
25. The UE (10) according to claim 24, wherein the UE is further configured to obtain the indication by receiving the indication from the radio network node (12).
26. The UE (10) according to claim 25, wherein the UE is further configured to obtain the indication by receiving from the radio network node (12) a specific reference signal, RS, configuration for the UE and / or by receiving a specific set of RSs to the UE.
27. The UE (10) according to any of the claims 24-26, wherein the obtained indication indicates an order to apply the one or more priority rules.
28. The UE (10) according to claim 24, wherein the obtained indication indicates to autonomously adjust one or more parameters pertaining to a configuration of channel state information feedback, and / or apply a default priority rule.
29. The UE (10) according to any of the claims 24-28, wherein the indication is received: in a message that allocates physical uplink shared channel, PUSCH, resources to the UE; in a message that triggers channel state information, CSI, feedback to be carried on PUSCH; in a message that configures reference signal, RS, measurement configuration and / or CSI reporting configuration; in a message that configures a data collection process; and / or in a dedicated configuration message.
30. The UE (10) according to any of the claims 23-29, wherein the UE (10) is configured to: receive a rule indication indicating one or more of the following:• the one or more priority rules to be applied for a subsequent channel state information, CSI, feedback report, or• the one or more priority rules to be applied until indicated otherwise,• the one or more priority rules to be applied until implicitly indicated via a configuration message,• the one or more priority rules to be applied for a duration of a data collection process, and / or• the one or more priority rules to be applied for a given duration.
31. The UE (10) according to any of the claims 23-30, wherein the one or more priority rules indicate that the UE is to reduce a quality of, or omit, channel state information, CSI, feedback in order to allocate a larger amount of a type of uplink data within available physical uplink shared channel, PUSCH, resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model.
32. The UE (10) according to any of the claims 23-31, wherein the UE (10) is configured to transmit to the radio network node an apply indication indicating the applied priority rule.
33. The UE (10) according to any of the claims 23-32, wherein the second type of uplink data transmissions comprises payload data and / or a channel state information, CSI, type not related to data collection for the computational model, and the first type of uplink data transmissions comprises a CSI type related to data collection for the computational model.
34. A radio network node (12) for handling communication of a user equipment, UE, (10) in a wireless communication network (1), wherein the radio network node (12) is configured to: receive a capability indication from the UE (10), wherein the capability indication indicates a capability to apply one or more priority rules, wherein the one or more priority rules indicate an allocation of uplink resources for a first type of uplink data transmissions related to data collection for a computational model, relative to an allocation of uplink resources for a second type of uplinkdata transmissions, wherein the one or more priority rules indicate that the second type of uplink data transmissions is prioritized over the first type of uplink data transmissions; schedule uplink data transmissions for the UE; receive from the UE the first type of uplink data transmissions and / or the second type of uplink data transmissions; and decode the first type of uplink data transmissions and / or the second type of uplink data transmissions taking the capability indication into account.
35. The radio network node (12) according to claim 34, wherein the radio network node is configured to transmit to the UE, an indication of a determined one or more priority rules out of the one or more priority rules to apply.
36. The radio network node (12) according to claim 35, wherein the radio network node is configured to transmit the indication by signaling a specific reference signal, RS, configuration to the UE and / or by transmitting a specific set of RSs to the UE.
37. The radio network node (12) according to any of the claims 35-36, wherein the indication indicates an order to apply the one or more priority rules.
38. The radio network node (12) according to any of the claims 35-37, wherein the radio network node (12) is configured to transmit the indication: in a message that allocates physical uplink shared channel, PUSCH, resources to the UE; in a message that triggers channel state information, CSI, feedback to be carried on PUSCH; in a message that configures reference signal, RS, measurement configuration and / or CSI reporting configuration; in a message that configures a data collection process; and / or in a dedicated configuration message.
39. The radio network node (12) according to any of the claims 34-38, wherein the radio network node (12) is configured to transmit a rule indication indicating one or more of the following:• the one or more priority rules to be applied for a subsequent channel state information, CSI, feedback report, or• the one or more priority rules to be applied until indicated otherwise,• the one or more priority rules to be applied until implicitly indicated via a configuration message,• the one or more priority rules to be applied for a duration of a data collection process, and / or• the one or more priority rules to be applied for a given duration.
40. The radio network node (12) according to any of the claims 34-39, wherein the one or more priority rules indicate that the UE is to reduce a quality of, or omit, channel state information, CSI, feedback in order to allocate a larger amount of a type of uplink data within available physical uplink shared channel, PLISCH, resources; and / or to transmit payload data and / or a CSI type of a first type before transmitting CSI related to data collection for the computational model.
41. The radio network node (12) according to any of the claims 34-40, wherein the radio network node is configured to receive from the UE (10) an apply indication indicating an applied priority rule, and to decode the first type of uplink data transmissions and / or the second type of uplink data transmissions based on the apply indication.
42. The radio network node (12) according to any of the claims 34-41 , wherein the second type of uplink data transmissions comprises payload data and / or a channel state information, CSI, type not related to data collection for the computational model, and the first type of uplink data transmissions comprises a CSI type related to data collection for the computational model.
Citation Information
Patent Citations
Methods, devices, and medium for communication
WO2023108375A1