Privacy-preserving and UE-assisted CDRX configuration

Abstract

Some embodiments described herein provide systems, methods, and apparatuses for a user equipment (UE) centric Connected Discontinuous Reception (CDRX) optimization. In some embodiments, a UE may receive a set of inputs including Quality of Service (QoS) requirements, UE contextual information, and traffic information. The UE may determine one or more CDRX configurations based on the set of inputs, and send the one or more CDRX configurations to a network node.

Description

PRIVACY-PRESERVING AND UE-ASSISTED CDRX CONFIGURATION TECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including protocols for link budget limited devices and privacy-preserving and UE assisted CDRX configuration. BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE).3GPP RANs can include, for example, Global System for Mobile communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.1 4916-1830-2277\1 P67185WO1

[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E- UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0006] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC). BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0008] FIG.1 illustrates a diagram for discontinuous reception (DRX), according to one or more embodiments of the present disclosure.

[0009] FIG.2 illustrates a diagram for DRX with an inactivity timer, according to one or more embodiments of the present disclosure.

[0010] FIG.3 illustrates a diagram of DRX with short cycles and long cycles, in accordance with one or more embodiments of the present disclosure.

[0011] FIG.4 illustrates an example block diagram of a joint UE and network CDRX configuration, according to one or more embodiments of the present disclosure.

[0012] FIG.5 illustrates a signal flow diagram of an example joint UE and network CDRX configuration, in accordance with one or more embodiments of the present disclosure.

[0013] FIG.6 illustrates an example block diagram of a UE-centric CDRX configuration, in accordance with one or more embodiments of the present disclosure.

[0014] FIG.7 illustrates a signal flow diagram of UE-centric CDRX configuration, in accordance with one or more embodiments of the present disclosure.

[0015] FIG.8 illustrates a diagram of a UE-centric dynamic adjustment of CDRX parameters, according to one or more embodiments of the present disclosure.

[0016] FIG.9 illustrates an example of traditional compression of a digital image, according to one or more embodiments of the present disclosure.2 4916-1830-2277\1 P67185WO1

[0017] FIG.10 illustrates an example of semantic compression of a digital image, according to one or more embodiments of the present disclosure.

[0018] FIG.11 illustrates an example of relay-based data reconstruction, according to one or more embodiments of the present disclosure.

[0019] FIG.12 illustrates an example of an interface for image verification, according to one or more embodiments of the present disclosure.

[0020] FIG.13 illustrates an example of a protocol of image verification, according to one or more embodiments of the present disclosure.

[0021] FIG.14 illustrates a diagram of offloading of image reconstruction from a satellite, according to one or more embodiments of the present disclosure.

[0022] FIG.15 illustrates an example of an interface for video verification, according to one or more embodiments of the present disclosure.

[0023] FIG.16 illustrates an example of a protocol of explicit video verification, according to one or more embodiments of the present disclosure.

[0024] FIG.17 illustrates an example of a protocol of implicit video verification, according to one or more embodiments of the present disclosure.

[0025] FIG.18 illustrates a diagram of offloading of video reconstruction with a satellite, according to one or more embodiments of the present disclosure.

[0026] FIG.19 illustrates a diagram of offloading of video reconstruction with uplink relaying, according to one or more embodiments of the present disclosure.

[0027] FIG.20 illustrates a diagram for a proposed compression procedure at the transmitter, according to one or more embodiments of the present disclosure.

[0028] FIG.21 illustrates a diagram for stable diffusion, according to one or more embodiments of the present disclosure.

[0029] FIG.22 illustrates a method performed by a UE, according to one or more embodiments of the present disclosure.

[0030] FIG.23 illustrates a method performed by a network node, according to one or more embodiments of the present disclosure.

[0031] FIG.24 illustrates an example architecture of a wireless communication system, according to one or more embodiments of the present disclosure.3 4916-1830-2277\1 P67185WO1

[0032] FIG.25 illustrates a system for performing signaling between a wireless device and a network device, according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0033] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.

[0034] Some embodiments herein include systems, methods, and apparatuses for privacy-preserving and UE-assisted Connected Discontinuous Reception (CDRX) Configuration. Embodiments that use CDRX may provide power saving, low latency, optimized radio resource allocation, coverage and capacity optimization. Additionally, embodiments consider solutions for privacy concerns related to a UE sharing details about traffic with the network for the CDRX configuration.

[0035] FIG.1 illustrates a diagram for discontinuous reception (DRX) 102, in accordance with one or more embodiments of the present disclosure. In some embodiments, a long DRX cycle is configured. Each long DRX cycle may include an ON period (e.g., on period 108) and an OFF period (e.g., off period 110). The ON period may also be referred to as an “ON Duration,” and may be defined in terms of milliseconds. The ON Duration may refer to the period in which the UE stays awake and decodes the PDCCH. The ON and OFF durations together form a Long DRX duration and repeat once every Long DRX Cycle period (e.g., long DRX cycle 106) which is configured by RRC.

[0036] In one or more embodiments, once a Long DRX Cycle 106 starts, the UE stays active for a duration of drx-onDurationTimer 104. If there is no PDCCH received during this time, the UE would go to DRX sleep state, until the start of the next ‘ON duration’.

[0037] For example, in the illustrated embodiment, during the long DRX cycle 106, the UE stays awake during the on period 108, and since there is no PDCCH received during the drx-onDurationTimer 104, the UE enters a DRX sleep state, until the start of the next On duration.4 4916-1830-2277\1 P67185WO1

[0038] FIG.2 illustrates a diagram of DRX 202 in which a PDCCH is received, in accordance with one or more embodiments of the present disclosure. As shown, during the On period 204, PDCCH reception 206 occurs in the illustrated example. In some embodiments, in case there is PDCCH activity during the On Duration period (e.g., On period 204), it is highly likely that the device might be scheduled again.

[0039] In some embodiments, a parameter may be defined to keep the UE in active state after being scheduled. For example, in the illustrated example, drx-inactivityTimer 208 starts after PDCCH reception 206 keeping the UE in an active state for a period of time. After the drx-inactivityTimer 208 runs out, the UE may DRX sleep state. In at least one embodiment, the UE may start or restart this timer every time PDCCH indicates a new uplink or downlink transmission.

[0040] FIG.3 illustrates a diagram of DRX 302 with short cycles (e.g., short DRX cycle 306) and long cycles (e.g., long DRX cycle 304), in accordance with one or more embodiments of the present disclosure. In some embodiments, discontinuous reception can include a long DRX cycle (e.g., long DRX cycle 304) and a short DRX cycle (e.g., short DRX cycle 306). In the illustrated embodiment, in case there is no data activity during the ‘ON duration’ of a long cycle, the device simply follows long DRX cycle as if short DRX cycle is not configured. If there is any data activity (e.g., PDCCH reception 308), the UE may switch to short DRX cycle and follows short cycle for a certain amount of time. If there is no data activity during this time, the UE may then switch to long DRX cycle and so on.

[0041] In some embodiments, if there is no data activity during the period defined by drx-ShortCycleTimer x drx-ShortCycle, the UE may enter a long cycle. In other words, the UE may enter a long DRX cycle upon the drx-ShortCycleTimer number of short cycles.

[0042] In some embodiments, connected DRX configurations can be optimized according to one or more examples of the present disclosure. In at least one embodiment, various parameters can be included that impact the performance of the CDRX configuration. In at least some embodiments, these parameters can include parameters related to applications running on the devices (e.g., load, traffic type and pattern, device model, application Quality of Service (QoS) requirements, signal quality). Additionally, the parameters can include the importance of the blocks / representations, interdependence5 4916-1830-2277\1 P67185WO1between the blocks and / or representations, tolerable packet error or total minimum required weight, and delay budget.

[0043] The CDRX configurations can include a DRX cycle length (long and short cycles), the on-duration length, and the inactivity timer length. It may be beneficial to define an optimal CDRX configuration for a given set of parameters. Some solutions assume that all information above about traffic characteristics and requirements are shared with the network node which then picks the configuration to be used by the device. Furthermore, in some embodiments the UE may be assumed to share all the information about the traffic and application characteristics with the base station.

[0044] However, for privacy concerns, it may be desirable to minimize the information that the UE shares. Accordingly, some embodiments herein provide ways to optimize CDRX configurations while limiting the amount of information shared with the base station.

[0045] In some embodiments, the CDRX configurations can include an optional dynamic adjustment. For example, the base station might dynamically adjust the CDRX configuration based on changing parameters. A CDRX reconfiguration message may be sent for such adjustments. In some embodiments, the UE can report its capabilities related to CDRX to the base station during initial connection set up or when requested by the network. Such information can include supported DRX parameters.

[0046] One of the goals of network design is power savings. For example, power savings for extended reality (XR) may be important especially in cases where a device is battery powered. In some embodiments, to better optimize CDRX for XR traffic, 3GPP identified the information described below from core network to RAN that may be helpful for the enhancement of XR-specific UE power management. Such information may be assumed to be shared by the UE and / or application server with the network.

[0047] The information shared with the network can include the protocol data unit (PDU) set periodicity and start time of the first PDU of a PDU set. This can be helpful for configuring the periodicity and start time of CDRX or PDCCH monitoring to match with traffic period.

[0048] The information shared with the network can include a PDU set end indication or indication of the last PDU in a PDU set. This can be helpful for the network node, for example, to indicate the UE to dynamically skip PDCCH monitoring once the last PDU of the PDU set is delivered.6 4916-1830-2277\1 P67185WO1

[0049] The information shared with the network can include PDU set level QoS parameters including priority and [air interface] delay budget of a PDU set. This can help the network node to select suitable CDRX parameters (e.g., periodicities) that enable fulfilling the delay requirements for a given flow. It also helps with UE power saving, for example by reducing retransmission or by early dropping of a PDU that exceeds the delay deadline.

[0050] The information shared with the network can include PDU set size (number of bits) or number of PDUs in a PDU set. When considered in comparison to the statistical information, real-time or dynamic information provided to network node, if possible, this information can help scheduler make more efficient scheduling decision to enable UE power saving.

[0051] The information shared with the network can include PDU set identity and relationship information among PDUs within the same PDU set. The network node can use this information for early PDU dropping.

[0052] The information shared with the network can include information such as Jitter information such as the range of the jitter (minimum and maximum value). In some embodiments, jitter refers to packet arrival time variation at network node for download direction. The network node could use this information to configure parameters of UE power saving schemes, for example CDRX OnDuration and Active Time or PDCCH monitoring duration for handling of the jitter.

[0053] However, excessive disclosure of the identified information to the network may pose privacy risks to the UE and the application. Embodiments herein describe ways to minimize the information provided to the network while still allowing for CDRX optimization.

[0054] The UE may have different concurrent objectives. Such objectives may include power saving, low latency, optimized radio resource allocation, coverage and capacity optimization. These objectives may be in opposition to one another, and sometimes one or more of the objectives may be more important than the others. For example, while power saving is an objective, at the same time latency is an objective important to an XR application cares also about the latency, about optimized resource allocation, about coverage and the and capacity.7 4916-1830-2277\1 P67185WO1

[0055] Accordingly, to achieve optimization of the objectives, the UE may account for different contextual information. For example, the UE may account for mobility, radio conditions and channel quality, as well as traffic load and UE capability.

[0056] The UE may be involved in CDRX configuration. For example, a UE can report its capabilities related to CDRX to the network node during initial connection set up or when requested by the network. The CDRX UE capabilities may include supported longDRX-Cycle and shortDRX-Cycle. Further, for optional dynamic adjustment, the network node might dynamically adjust the CDRX parameters based on changing parameters. A CRDX reconfiguration message may be sent for optional dynamic adjustments.

[0057] One of the challenges of network-centric CDRX is privacy concerns. Some solutions assume that the UE shares detailed information about the traffic with the network. In case the information about traffic are not shared with the network, the CDRX configuration determined by the network might not be the best for the UEs. However, the information may be revealing about the application or about the capabilities of the UE.

[0058] Accordingly, embodiments herein reduce the amount of information shared with the network. In some embodiments, a UE-Centric CDRX Optimization may be implemented. Two options can be considered for more optimized configuration of CDRX parameters with involvement of the UE. In some embodiments, joint UE and network CDRX configuration may be implemented. In some embodiments, UE-centric CDRX configuration may be implemented. For both options, the CDRX parameters may be adjusted optionally (e.g., UE-centric dynamic adjustment of CDRX parameters).

[0059] Such approaches can help take advantage of two types of data: application specific information, and environment specific information. Application specific information may include traffic type and pattern, jitter and size information of media unit, etc. Environment specific information may include load in the network, available resources, channel state information, downlink buffer status. Application specific information is available at the UE and for privacy reasons, it might not be desirable to share such information with the network. Environment specific information is available at the network given that the network is in charge of allocating resources and controls the buffers for downlink transmissions.8 4916-1830-2277\1 P67185WO1

[0060] FIG.4 illustrates an example block diagram 402 of a joint UE and network CDRX configuration, according to one or more embodiments of the present disclosure. In some embodiments, based on the information about the application requirements and traffic details, the UE 406 can locally optimize the CDRX configuration and identify a number of configurations that better fit the UE requirements and constraints.

[0061] For example, the optimization problem can be formulated as a multi-objective optimization problem where the goal of the UE 406 is to optimize multiple targets simultaneously whenever possible. The goals can include latency, power saving, throughput, etc.

[0062] The UE 406 may generate one or more UE optimized CDRX configurations 410 based on inputs 408. The information of the inputs 408 that can be taken into account by the UE 406 may include QoS requirements, UE contextual information, and traffic details. The UE contextual information may include one or more of the device model, or the number of applications running simultaneously and their requirements. Traffic details can include one or more of traffic type and pattern, periodicity, range of jitter, start time of the first PDU of a PDU set, PDU set level QoS parameters (priority and delay budget of a PDU set), PDU sets sizes, or number of PDUs within a PDU set. The UE 406 can share a number of desirable CDRX configurations (e.g., UE optimized CDRX configurations 410) with the network node 404.

[0063] The network node 404 can also optimize the CDRX configuration by leveraging the locally available information 412. The locally available information 412 at the network node 404 may include one or more of Channel State Information (CSI) information, buffer status, or allocated resources. The objective function at the network node 404 might be different than the UE’s as it might account for multiple UEs simultaneously and optimize network capacity. By taking into account the preferences of the UE 406, the network node 404 can identify the best CDRX configuration to be used by the UE 406.

[0064] For example, in the illustrated embodiment, the network node 404 receives the UE optimized CDRX configurations 410. The network node 404 also uses locally available information 412 as an input including: one or more of network node QoS target, network load, radio link quantity, UE's buffer status, or available resources. Based on this locally available information 412, the network node 404 selects a CDRX configuration 414 (e.g., one of the configurations from the UE optimized CDRX9 4916-1830-2277\1 P67185WO1configurations 410), and sends the selected CDRX configuration 414 to the UE 406. The UE 406 may use the selected CDRX configuration 414.

[0065] FIG.5 illustrates a signal flow diagram 502 of an example joint UE and network CDRX configuration, in accordance with one or more embodiments of the present disclosure. As shown, the Application Server 506 may send the network node 508 metadata 510 with details about the traffic to be transmitted. The network node 508 may then send to the UE 504 metadata 512 with details about the traffic to be transmitted.

[0066] The UE 504 may perform CDRX Configuration optimization 514 based on the received metadata and local contextual information. The UE 504 may generate multiple optimized CDRX configurations. The UE 504 may share 516 with the network node 508 a number of potential CDRX configurations to be used by UE 504.

[0067] The network node 508 may perform CDRX Configuration optimization 518 based on local parameters while accounting for CDRX configuration options shared by the UE 504. The network node 508 may share 520 a single CDRX configuration to be used by the UE 504.

[0068] FIG.6 illustrates an example block diagram 602 of a UE-centric CDRX configuration, in accordance with one or more embodiments of the present disclosure. In some embodiments, based on the information about the application requirements, traffic details, and information received from the network node about network conditions, the UE 608 can locally optimize the CDRX configuration and identify a number of configurations that better fit the UE requirements and constraints.

[0069] For example, the optimization problem can be formulated as a multi-objective optimization problem where the goal of the UE 608 is to optimize multiple targets simultaneously whenever possible. The goals can include latency, power saving, throughput, etc.

[0070] The UE 608 may generate a 606 based on a number of inputs 604. The information of the inputs 604 that can be taken into account by the UE 608 may include QoS requirements, UE contextual information, traffic details, and network specific information. The UE contextual information may include one or more of the device model, or the number of applications running simultaneously and their requirements. Traffic details can include one or more of traffic type and pattern, periodicity, range of jitter, start time of the first PDU of a PDU set, PDU set level QoS parameters (priority and delay budget of a PDU set), PDU sets sizes, or number of PDUs within a PDU set.10 4916-1830-2277\1 P67185WO1The network specific information may include one or more of CSI information, buffer status, or allocated resources.

[0071] The UE 608 can share a single or multiple CDRX configurations to be used with the network node. Optionally, the network node can pick one of the multiple options and recommend it to the UE 608.

[0072] FIG.7 illustrates a signal flow diagram 722 of a UE-centric CDRX configuration, in accordance with one or more embodiments of the present disclosure. As shown, the Application Server 706 may send the network node 704 metadata 708 with details about the traffic to be transmitted. The network node 704 may then send to the UE 702 the metadata 710 with details about the traffic to be transmitted.

[0073] The UE 702 may request 712 periodic information about UE's downlink buffer status, CSI, and allocated resources from the network node 704. The network node 704 may share 714 buffer status, CSI, and allocated resources for UE 702. The UE 702 may perform CDRX Configuration optimization 718 based on QoS requirements, UE contextual information, traffic information, and network information.

[0074] The UE 702 may share, with the network node 704, one or more CDRX configurations 716 to be used by UE 702. Optionally, if multiple CDRX configurations are sent to the network node 704, the network node 704 can pick one of the multiple options and recommend 710 it to the UE 702.

[0075] FIG.8 illustrates a signal flow diagram 802 of a UE-centric dynamic adjustment of CDRX parameters, in accordance with one or more embodiments of the present disclosure. In some embodiments, the UE 806 can adjust the CDRX configuration based on the data it receives, its local requirements as well as potential additional information updates it might receive from the network. In some embodiments, the UE 806 can dynamically and locally update the CDRX configuration and then share the parameters with the network. For instance, in case online learning is used to optimize the CDRX parameters, the updated parameters can be part of the CDRX configuration optimization process.

[0076] In the illustrated embodiment, the network node 804 sends a traffic transmission 808 to the UE 806. The UE 806 may send the network node 804 a request 810 for one time or period parameters status such as buffer status. The network node 804 may send the UE 806 the requested information (e.g., buffer status). The UE 806 may perform 814 CDRX Configuration optimization based on received data and updated network11 4916-1830-2277\1 P67185WO1parameters. The UE 806 may share the CDRX configuration 816 to be used by UE 806 with the network node 804.

[0077] The following provides an example of CDRX configuration optimization for XR traffic. In at least some embodiments, QoS requirements of XR services can be characterized by a delay budget and an error rate and / or minimum total weight wth. In some embodiments, the satisfaction of a UE can be defined as the number of representations that are received within the delay budget with at least the minimum total weight wth.

[0078] In the following equation, let x(t) be the variable accounting for the user’s active time of the tthDRX cycle, namely the value of the drx-OnDuration parameter of the DRX configuration. The user may be satisfied if the activity time of the current DRX cycle expires after the frame arrival. The instantaneous user’s satisfaction may be modeled at tthDRX cycle by the following equation 1.equation 1

[0079] The above function counts how many times the user has been satisfied by the decision throughout the time.

[0080] The optimization of the CDRX configuration while accounting for the UE's KPIs and constraints can be formulated by the equation below.equation 2 where, f is the objective function and capture the UE's KPI and can be for example defined by the following limit (equation 3).equation 312 4916-1830-2277\1 P67185WO1

[0081] Further, e(t) corresponds to the energy consumption of the UE. Su corresponds to the constraint for user satisfaction, which is the target percentage of representations received within the delay budget and minimum total weight. Additionally, g represents the UE’s constraints and can for examples be defined by the limit shown below in equation 4.equation 4

[0082] In some embodiments, multiple protocols can be included to enable privacy preserving and UE-centric CDRX configuration mechanisms. For example, the present disclosure describes some embodiments comprising a protocol to enable a joint UE and network node CDRX configuration optimization mechanism that does not require any sharing of traffic and application related information with the network. Some embodiments comprise a protocol to enable UE-centric CDRX configuration with inputs from the network node to be shared with the UE. Furthermore, some embodiments of the present invention can include a protocol to enable dynamic adjustment of the CDRX reconfiguration locally at the UE with inputs from the network node about the changes in the environment.

[0083] Depending on the radio technology (cellular, WiFi and satellite), different metrics can make it hard to support the QoS requirements for some specific services. For instance, dynamic radio conditions. These conditions can impact the instantaneous achievable latency due to interference, blockage and fading. Congestion which occurs when devices transmit at a higher bitrate than the network can sustain. Services with strict latency requirements. In satellite communication, the limited uplink data rate makes it challenging to support application with heavy traffic such as video calls. The present disclosure includes embodiments that may overcome the above complications.

[0084] Additionally, the present disclosure describes methods that enable multimedia transmission (images and video) over satellite using generative AI. Additionally, the present disclosure describes a method that enhances QoS for devices with limited power and compute resources through relaying and generative AI. The disclosure herein includes descriptions of traditional versus semantic compression, relay-based data13 4916-1830-2277\1 P67185WO1reconstruction, multimedia transmission in satellite, offloading of image reconstruction, offloading of video reconstruction, offloading of video reconstruction (uplink relaying), and offloading of video reconstruction (downlink relaying).

[0085] FIG.9 illustrates an example block diagram 902 of traditional compression of a digital image, in accordance with one or more embodiments of the present disclosure. Traditional compression may result in adding distortion to reduce message size. The poor quality can result if the target size is small.

[0086] FIG.10 illustrates an example block diagram 1002 of semantic compression of a digital image, in accordance with one or more embodiments of the present disclosure. With semantic compression, the resulting reconstructed semantic image can include a high perceptual quality. In some embodiments, the reconstructed image can be semantically equivalent to the original image. The reconstructed image may not the same as the original image. Accordingly, verification can be required when reconstructing the original image using semantic compression.

[0087] FIG.11 illustrates an example diagram 1102 of relay-based data reconstruction, in accordance with one or more embodiments of the present disclosure. In some embodiments, relay-based data reconstruction of digital media can be subject to power consumption and compute limitations. In at least some embodiments, devices with limited power and compute resources might not be able to perform advanced coding and decoding techniques.

[0088] In some embodiments, relay-based data reconstruction can also be subject to limitations of local links performance. In at least one embodiment, for application with strict delay budget, local links performance (e.g. WIFI, P2P) might not be the ideal for satisfying such requirements due to channel access techniques that results in high latency. In such scenarios, a sender / receiver might rely on the capabilities of the relay to overcome these limitations.

[0089] The present disclosure proposes developments to help solve the above limitations. In some embodiments, to support services with strict requirements and overcome the compute and power limitations on the transmitting / receiving devices, a more capable relaying hot spot device can be utilized to perform the compression and reconstruction mechanism with the goal of enhancing the perceptual quality of the data and / or satisfying the service requirements of the application of interest, if any.14 4916-1830-2277\1 P67185WO1

[0090] FIG.12 illustrates an example block diagram 1202 of an interface for image verification, in accordance with one or more embodiments of the present disclosure. In some embodiments, a sender can choose an image to send to a recipient side. In at least one embodiment, a semantic image can be generated and provided to the sender for verification. In some embodiments, the semantic image can be slightly different from the original one. In at least one example, the semantic image can be displayed to the sender with a text description. The sender can review the semantic image and the text description. In some embodiments, the sender can choose to send the semantic image or update the text description and retry.

[0091] In some embodiments, the sender side can transmit the text description and a compressed latent representation to the recipient side. In at least one embodiment, the semantic image is generated and provided to the recipient.

[0092] FIG.13 shows an example block diagram 1302 of a protocol of image verification, in accordance with one or more embodiments of the present disclosure. In some embodiments, an original image, (e.g., a photo) of any size can undergo semantic compression. The semantic image can be a compressed latent representation with a size of 200 to 600 bytes. Optionally, a semantic text description with a size of 200 bytes can also be provided.

[0093] In some embodiments, the protocol of image verification can also include semantic reconstruction, where a reconstructed 512 by 512 image can be shown to the Sender for verification. In some embodiments, the sender's decision can be to send the image or to try another attempt. If the sender chooses to send the image, a representation and / or text description can be transmitted. In at least some embodiments, a receiver reconstructs exactly the same 512 x 512 image that was verified by the sender.

[0094] In at least one embodiment, if the sender chooses to try another attempt, the text description is provided to the user for verification and correction. Additionally, the size of the compressed latent representation can be increased if it is less than the allowed maximum. In some embodiments, in the case that only the text description is updated, a new reconstructed 512 by 512 image can be shown to the sender for verification. In the case the latent representation size is updated, a new compressed latent representation can be constructed.

[0095] In some embodiments, the size of the compressed latent representation can be selected based on the cooperation opportunities of the UE. For example, a single UE can15 4916-1830-2277\1 P67185WO1include 200 bytes. Two cooperating UEs can include 400 bytes, and 3 or more cooperating UEs can include 600 bytes.

[0096] FIG.14 illustrates an example signaling diagram 1402 of offloading of image reconstruction from a satellite, in accordance with one or more embodiments of the present disclosure. In some embodiments, Satellite-to-device link is much faster (10-100) than device-to-satellite link. In at least one embodiment, the semantically represented image can be reconstructed at the network or a server to preserve device power.

[0097] In some embodiments, the reconstructed image and semantic text description is sent back to the sender to verify the quality. In one or more embodiments, the sender can approve sending it, decide to send just text, or not send. The proposed verification mechanism on the server / satellite is optional and can be performed on the device when the loss over the link is not considered.

[0098] FIG.15 illustrates an example block diagram 1502 of an interface for video verification, in accordance with one or more embodiments of the present disclosure. In some embodiments, a sender can choose a video to send to a recipient side. In at least one embodiment, a semantic video can be generated and provided to the sender for verification. In some embodiments, the semantic video can be slightly different from the original one. In at least one example, the semantic video can be displayed to the sender with a text description. The sender can review the semantic video and the text description. In some embodiments, the sender can choose to send the semantic video or update the text description and retry.

[0099] In some embodiments, the sender side can transmit the text description and a compressed video to the recipient side. In at least one embodiment, the semantic video is generated and provided to the recipient.

[0100] FIG.16 shows an example block diagram 1602 of a protocol of explicit video verification, in accordance with one or more embodiments of the present disclosure. In some embodiments, an original high resolution video of any size can undergo semantic compression. The semantic video can be a frame-level compressed latent representation with a size of 200 to 600 bytes per frame. Optionally, a semantic text description with a size of 200 bytes can also be provided.

[0101] In some embodiments, the protocol of explicit video verification can also include semantic reconstruction, where a reconstructed video can be shown to the Sender for verification. In some embodiments, the sender's decision can be to send the video or16 4916-1830-2277\1 P67185WO1to try another attempt. If the sender chooses to send the video, a compressed video and / or a text description can be transmitted. In at least some embodiments, a receiver reconstructs exactly the video that was verified by the sender.

[0102] In at least one embodiment, if the sender chooses to try another attempt, the text the compression rate can be decreased as long as the compressed video size is lower than the allowed maximum size. In some embodiments, the size of the compressed latent representation can be selected based on the cooperation opportunities of the UE. For example, a single UE can include 200 bytes. Two cooperating UEs can include 400 bytes, and 3 or more cooperating UEs can include 600 bytes.

[0103] FIG.17 shows an example block diagram 1702 of a protocol of implicit video verification, in accordance with one or more embodiments of the present disclosure. In some embodiments, an original high resolution video of any size can undergo semantic compression. The semantic video can be a frame-level compressed latent representation with a size of 200 to 600 bytes per frame. Optionally, a semantic text description with a size of 200 bytes can also be provided.

[0104] In some embodiments, the protocol of implicit video verification can also include semantic reconstruction, where an implicit comparison of reconstructed video with original one at the sender. In at least one embodiment, an implicit rendering quality comparison can be performed with respect to a threshold. If the threshold is met, the video can be sent. In such embodiments, the compressed video and optional text description are transmitted. Furthermore, the receiver reconstructs exactly the video that was verified by the sender.

[0105] In some embodiments, if the threshold is not met, the compression rate can be decreased as long as the compressed video size is lower than the allowed maximum size. In some embodiments, the size of the compressed latent representation can be selected based on the cooperation opportunities of the UE. For example, a single UE can include 200 bytes. Two cooperating UEs can include 400 bytes, and 3 or more cooperating UEs can include 600 bytes.

[0106] FIG.18 illustrates an example signaling diagram 1802 of offloading of video reconstruction with a satellite, in accordance with one or more embodiments of the present disclosure. In some embodiments, the semantically represented video can be reconstructed at the network or a server to preserve the device power. In at least one embodiment, the reconstructed video and semantic text description is sent back to the17 4916-1830-2277\1 P67185WO1sender to verify the quality. Additionally, the sender can approve either explicitly or implicitly sending it, decide to send just text, or not send.

[0107] FIG.19 illustrates an example block diagram 1902 of offloading of video reconstruction with uplink relaying, in accordance with one or more embodiments of the present disclosure. In some embodiments, offloading of video reconstruction can include various assumptions. In some embodiments, these assumptions can include assumptions such as relaying-to-recipient device link is capacity limited. Another assumption can be in the relaying scenario, the sender is assumed to have limited power and compute capabilities.

[0108] In some embodiments, the original video is either semantically compressed or reconstructed at the relay which could be a phone, customer premise equipment (CPE), or any other capable device. In at least one embodiment, the quality of the reconstructed video against the original video is verified implicitly at the replay device and when it reaches a predefined threshold, the semantically compressed video is shared with the receiver. In some embodiments, the reconstructed video and optional semantic text description are sent to the receiver.

[0109] FIG.20 shows an example block diagram 2002 for a proposed compression procedure at the transmitter, in accordance with one or more embodiments of the present disclosure.

[0110] FIG.21 shows an example block diagram 2102 for stable diffusion, in accordance with one or more embodiments of the present disclosure. In some embodiments, stable diffusion can include components such as VAE: mapping to and from latent representation, conditional denoising U-Net model, and / or a CLIPText encoder. In some embodiments, all stable diffusion components can be optimized.

[0111] FIG.22 illustrates a method 2200 performed by a UE, according to one or more embodiments of the present disclosure. The illustrated method 2200 includes receiving 2202 a set of inputs, the inputs comprising: QoS requirements, UE contextual information, and traffic information. The method 2200 further includes determining 2204 one or more CDRX configurations based on the set of inputs. The method 2200 further includes sending 2206 the one or more CDRX configurations to a network node.

[0112] In some embodiments, the method 2200 further comprises receiving, from the network node, a selected CDRX configuration, wherein the selected CDRX18 4916-1830-2277\1 P67185WO1configuration is based on network information at the network node, and using the selected CDRX configuration.

[0113] In some embodiments, the method 2200 further comprises receiving network information from the network node, and wherein the inputs further comprise the network information. In some such embodiments, the network information comprises CSI information, buffer status, and allocated resources.

[0114] In some embodiments of the method 2200, the UE contextual information comprises a device model, a number of applications running simultaneously, and requirements of the applications.

[0115] In some embodiments of the method 2200, the traffic information comprises periodicity, range of jitter, start time of a first PDU of a PDU set, PDU set level QoS parameters, PDU sets sizes, number of PDUs within the PDU set.

[0116] In some embodiments, the method 2200 further comprises adjusting the CDRX configuration based on updated information, and dynamically and locally updating the CDRX configuration.

[0117] In some embodiments of the method 2200, determining the one or more CDRX configurations includes solving a multi-objective optimization problem for multiple targets including one or more of latency, power saving, or throughput.

[0118] FIG.23 illustrates a method 2300 performed by a network node, according to one or more embodiments of the present disclosure. The illustrated method 2300 includes receiving 2302, from a UE, one or more CDRX configurations based on the set of inputs that include QoS requirements, UE contextual information, and traffic information. The method 2300 further includes selecting 2304 a CDRX configuration from the one of the one or more CDRX configurations for the UE to apply. The method 2300 further includes sending 2306 the selected CDRX configuration to the UE.

[0119] In some embodiments of the method 2300, the selected CDRX configuration is based on network information at the network node. In some such embodiments, the network information comprises CSI information, buffer status, and allocated resources.

[0120] In some embodiments, the method 2300 further comprises sending network information to the UE.19 4916-1830-2277\1 P67185WO1

[0121] In some embodiments of the method 2300, the UE contextual information comprises a device model, a number of applications running simultaneously, and requirements of the applications.

[0122] In some embodiments of the method 2300, the traffic information comprises periodicity, range of jitter, start time of a first PDU of a PDU set, PDU set level QoS parameters, PDU sets sizes, number of PDUs within the PDU set.

[0123] In some embodiments, the method 2300 further comprises receiving, from the UE, an updated CDRX configuration based on updated information.

[0124] FIG.24 illustrates an example architecture of a wireless communication system 2400, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 2400 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.

[0125] As shown by FIG. 24, the wireless communication system 2400 includes UE 2402 and UE 2404 (although any number of UEs may be used). In this example, the UE 2402 and the UE 2404 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0126] The UE 2402 and UE 2404 may be configured to communicatively couple with a RAN 2406. In embodiments, the RAN 2406 may be NG-RAN, E-UTRAN, etc. The UE 2402 and UE 2404 utilize connections (or channels) (shown as connection 2408 and connection 2410, respectively) with the RAN 2406, each of which comprises a physical communications interface. The RAN 2406 can include one or more base stations (such as base station 2412 and base station 2414) that enable the connection 2408 and connection 2410.

[0127] In this example, the connection 2408 and connection 2410 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 2406, such as, for example, an LTE and / or NR.

[0128] In some embodiments, the UE 2402 and UE 2404 may also directly exchange communication data via a sidelink interface 2416. The UE 2404 is shown to be configured to access an access point (shown as AP 2418) via connection 2420. By way of example, the connection 2420 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 2418 may20 4916-1830-2277\1 P67185WO1comprise a Wi-Fi®router. In this example, the AP 2418 may be connected to another network (for example, the Internet) without going through a CN 2424.

[0129] In embodiments, the UE 2402 and UE 2404 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 2412 and / or the base station 2414 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0130] In some embodiments, all or parts of the base station 2412 or base station 2414 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 2412 or base station 2414 may be configured to communicate with one another via interface 2422. In embodiments where the wireless communication system 2400 is an LTE system (e.g., when the CN 2424 is an EPC), the interface 2422 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 2400 is an NR system (e.g., when CN 2424 is a 5GC), the interface 2422 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 2412 (e.g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g., CN 2424).

[0131] The RAN 2406 is shown to be communicatively coupled to the CN 2424. The CN 2424 may comprise one or more network elements 2426, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 2402 and UE 2404) who are connected to the CN 2424 via the RAN 2406. The components of the CN 2424 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine- readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).21 4916-1830-2277\1 P67185WO1

[0132] In embodiments, the CN 2424 may be an EPC, and the RAN 2406 may be connected with the CN 2424 via an S1 interface 2428. In embodiments, the S1 interface 2428 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 2412 or base station 2414 and a serving gateway (S-GW), and the S1-MME interface, which is a signaling interface between the base station 2412 or base station 2414 and mobility management entities (MMEs).

[0133] In embodiments, the CN 2424 may be a 5GC, and the RAN 2406 may be connected with the CN 2424 via an NG interface 2428. In embodiments, the NG interface 2428 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 2412 or base station 2414 and a user plane function (UPF), and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 2412 or base station 2414 and access and mobility management functions (AMFs).

[0134] Generally, an application server 2430 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 2424 (e.g., packet switched data services). The application server 2430 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 2402 and UE 2404 via the CN 2424. The application server 2430 may communicate with the CN 2424 through an IP communications interface 2432.

[0135] FIG.25 illustrates a system 2500 for performing signaling 2534 between a wireless device 2502 and a network device 2518, according to embodiments disclosed herein. The system 2500 may be a portion of a wireless communications system as herein described. The wireless device 2502 may be, for example, a UE of a wireless communication system. The network device 2518 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0136] The wireless device 2502 may include one or more processor(s) 2504. The processor(s) 2504 may execute instructions such that various operations of the wireless device 2502 are performed, as described herein. The processor(s) 2504 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.22 4916-1830-2277\1 P67185WO1

[0137] The wireless device 2502 may include a memory 2506. The memory 2506 may be a non-transitory computer-readable storage medium that stores instructions 2508 (which may include, for example, the instructions being executed by the processor(s) 2504). The instructions 2508 may also be referred to as program code or a computer program. The memory 2506 may also store data used by, and results computed by, the processor(s) 2504.

[0138] The wireless device 2502 may include one or more transceiver(s) 2510 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna(s) 2512 of the wireless device 2502 to facilitate signaling (e.g., the signaling 2534) to and / or from the wireless device 2502 with other devices (e.g., the network device 2518) according to corresponding RATs.

[0139] The wireless device 2502 may include one or more antenna(s) 2512 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 2512, the wireless device 2502 may leverage the spatial diversity of such multiple antenna(s) 2512 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 2502 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 2502 that multiplexes the data streams across the antenna(s) 2512 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0140] In certain embodiments having multiple antennas, the wireless device 2502 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 2512 are relatively adjusted such that the (joint) transmission of the antenna(s) 2512 can be directed (this is sometimes referred to as beam steering).

[0141] The wireless device 2502 may include one or more interface(s) 2514. The interface(s) 2514 may be used to provide input to or output from the wireless device23 4916-1830-2277\1 P67185WO12502. For example, a wireless device 2502 that is a UE may include interface(s) 2514 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 2510 / antenna(s) 2512 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0142] The wireless device 2502 may include a UE module 2516. The UE module 2516 may be implemented via hardware, software, or combinations thereof. For example, the UE module 2516 may be implemented as a processor, circuit, and / or instructions 2508 stored in the memory 2506 and executed by the processor(s) 2504. In some examples, the UE module 2516 may be integrated within the processor(s) 2504 and / or the transceiver(s) 2510. For example, the UE module 2516 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 2504 or the transceiver(s) 2510.

[0143] The UE module 2516 may be used for various aspects of the present disclosure, for example, aspects of FIG.1 - FIG. 22. The UE module 2516 is configured to cause the wireless device 2502 to receive a set of inputs, the inputs comprising QoS requirements, UE contextual information, and traffic information. The UE module 2516 is configured to further cause the wireless device 2502 to determine one or more CDRX configurations based on the set of inputs. The UE module 2516 is configured to further cause the wireless device 2502 to send the one or more CDRX configurations to a network device 2518.

[0144] The network device 2518 may include one or more processor(s) 2520. The processor(s) 2520 may execute instructions such that various operations of the network device 2518 are performed, as described herein. The processor(s) 2520 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0145] The network device 2518 may include a memory 2522. The memory 2522 may be a non-transitory computer-readable storage medium that stores instructions 2524 (which may include, for example, the instructions being executed by the processor(s)24 4916-1830-2277\1 P67185WO12520). The instructions 2524 may also be referred to as program code or a computer program. The memory 2522 may also store data used by, and results computed by, the processor(s) 2520.

[0146] The network device 2518 may include one or more transceiver(s) 2526 that may include RF transmitter circuitry and / or receiver circuitry that use the antenna(s) 2528 of the network device 2518 to facilitate signaling (e.g., the signaling 2534) to and / or from the network device 2518 with other devices (e.g., the wireless device 2502) according to corresponding RATs.

[0147] The network device 2518 may include one or more antenna(s) 2528 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 2528, the network device 2518 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0148] The network device 2518 may include one or more interface(s) 2530. The interface(s) 2530 may be used to provide input to or output from the network device 2518. For example, a network device 2518 that is a base station may include interface(s) 2530 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 2526 / antenna(s) 2528 already described) that enables the base station to communicate with other equipment in a core network, and / or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

[0149] The network device 2518 may include a network module 2532. The network module 2532 may be implemented via hardware, software, or combinations thereof. For example, the network module 2532 may be implemented as a processor, circuit, and / or instructions 2524 stored in the memory 2522 and executed by the processor(s) 2520. In some examples, the network module 2532 may be integrated within the processor(s) 2520 and / or the transceiver(s) 2526. For example, the network module 2532 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 2520 or the transceiver(s) 2526.

[0150] The network module 2532 may be used for various aspects of the present disclosure, for example, aspects of FIG.1- FIG.21 and FIG.23. The network module 2532 is configured to cause the network device 2518 to receive, from a wireless device25 4916-1830-2277\1 P67185WO12502, one or more CDRX configurations based on the set of inputs that include QoS requirements, UE contextual information, and traffic information. The network module 2532 is configured to further cause the network device 2518 to select a CDRX configuration from the one of the one or more CDRX configurations for the UE to apply. The network module 2532 is configured to further cause the network device 2518 to send the selected CDRX configuration to the UE.

[0151] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 2200. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 2502 that is a UE, as described herein).

[0152] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 2200. This non-transitory computer- readable media may be, for example, a memory of a UE (such as a memory 2506 of a wireless device 2502 that is a UE, as described herein).

[0153] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 2200. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 2502 that is a UE, as described herein).

[0154] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 2200. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 2502 that is a UE, as described herein).

[0155] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 2200.

[0156] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 2200. The processor may be a processor of a UE (such as a processor(s) 2504 of a wireless device 2502 that is a UE, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 2506 of a wireless device 2502 that is a UE, as described herein).26 4916-1830-2277\1 P67185WO1

[0157] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 2300. This apparatus may be, for example, an apparatus of a base station (such as a network device 2518 that is a base station, as described herein).

[0158] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 2300. This non-transitory computer- readable media may be, for example, a memory of a base station (such as a memory 2522 of a network device 2518 that is a base station, as described herein).

[0159] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 2300. This apparatus may be, for example, an apparatus of a base station (such as a network device 2518 that is a base station, as described herein).

[0160] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 2300. This apparatus may be, for example, an apparatus of a base station (such as a network device 2518 that is a base station, as described herein).

[0161] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 2300.

[0162] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of the method 2300. The processor may be a processor of a base station (such as a processor(s) 2520 of a network device 2518 that is a base station, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the base station (such as a memory 2522 of a network device 2518 that is a base station, as described herein).

[0163] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband27 4916-1830-2277\1 P67185WO1processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0164] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0165] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0166] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0167] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as28 4916-1830-2277\1 P67185WO1to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0168] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.29 4916-1830-2277\1 P67185WO1

Claims

CLAIMS 1. A method performed by a user equipment (UE), the method comprising: receiving a set of inputs, the inputs comprising: Quality of Service (QoS) requirements, UE contextual information, and traffic information; determining one or more Connected Discontinuous Reception (CDRX) configurations based on the set of inputs; and sending the one or more CDRX configurations to a network node.

2. The method of claim 1, further comprising, receiving, from the network node, a selected CDRX configuration, wherein the selected CDRX configuration is based on network information at the network node; and using the selected CDRX configuration.

3. The method of claim 1, further comprising, receiving network information from the network node, and wherein the inputs further comprise the network information.

4. The method of claim 3, wherein the network information comprises Channel State Information (CSI) information, buffer status, and allocated resources.

5. The method of claim 1, wherein the UE contextual information comprises a device model, a number of applications running simultaneously, and requirements of the applications.

6. The method of claim 1, wherein the traffic information comprises periodicity, range of jitter, start time of a first protocol data unit (PDU) of a PDU set, PDU set level QoS parameters, PDU sets sizes, number of PDUs within the PDU set.

7. The method of claim 1, further comprising: adjusting the CDRX configuration based on updated information; and dynamically and locally updating the CDRX configuration.

8. The method of claim 1, wherein determining the one or more CDRX configurations includes solving a multi-objective optimization problem for multiple targets including one or more of latency, power saving, or throughput.30 4916-1830-2277\1 P67185WO19. An apparatus comprising means to perform one or more elements of a method or process described herein.

10. A non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to a method or process described herein.

11. A method performed by a network node, the method comprising: receiving, from a user equipment (UE), one or more Connected Discontinuous Reception (CDRX) configurations based on the set of inputs that include Quality of Service (QoS) requirements, UE contextual information, and traffic information; selecting a CDRX configuration from the one of the one or more CDRX configurations for the UE to apply; and sending the selected CDRX configuration to the UE.

12. The method of claim 11, wherein the selected CDRX configuration is based on network information at the network node.

13. The method of claim 12, wherein the network information comprises Channel State Information (CSI) information, buffer status, and allocated resources.

14. The method of claim 11, further comprising, sending network information to the UE.

15. The method of claim 11, wherein the UE contextual information comprises a device model, a number of applications running simultaneously, and requirements of the applications.

16. The method of claim 11, wherein the traffic information comprises periodicity, range of jitter, start time of a first protocol data unit (PDU) of a PDU set, PDU set level QoS parameters, PDU sets sizes, number of PDUs within the PDU set.

17. The method of claim 11, further comprising, receiving, from the UE, an updated CDRX configuration based on updated information.

18. A computing apparatus comprising: a processor; and31 4916-1830-2277\1 P67185WO1a memory storing instructions that, when executed by the processor, configure the apparatus to: receive a set of inputs, the inputs comprising: Quality of Service (QoS) requirements, UE contextual information, and traffic information; determine one or more Connected Discontinuous Reception (CDRX) configurations based on the set of inputs; and send the one or more CDRX configurations to a network node.

19. The computing apparatus of claim 18, wherein the instructions further configure the apparatus to, receive, from the network node, a selected CDRX configuration, wherein the selected CDRX configuration is based on network information at the network node; and using the selected CDRX configuration.

20. The computing apparatus of claim 18, wherein the instructions further configure the apparatus to, receive network information from the network node, and wherein the inputs further comprise the network information.

21. An apparatus comprising means to perform the method of any of claim 1 to claim 16.

22. A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 16.

23. An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 16.

24. A baseband processor for a user equipment (UE) configured to perform the method of any of claim 1 to claim 8.32 4916-1830-2277\1 P67185WO1

Images