Patent Description:
The telecommunications industry has experienced significant advancement and has been an enabler of new and improved technologies. Among these advancements is the pursuit of expanding mobility bandwidths to accommodate more Internet of Things (IoT) devices and the provision of greater and faster functionality to mobile user devices, often referred to generically as user equipment (UE). The <NUM> technology is expected to serve as an enabler of the telecommunication advancements and may lead to artificial intelligence (Al) functions such as observing local surroundings, reasoning, inferring, and decision making.

In a <NUM> telecom network, a Medium Access Control (MAC) layer of new radio (NR) provides services to the Radio Link Control (RLC) layer, in which controls are provided in the form of logical channels. These logical channels are virtualized communication network interfaces that are used to transfer IO commands (network data packets) and control instructions over a radio interface and a <NUM> fixed access network. A logical channel is defined by the type of information it carries and is generally differentiated as a control channel, used for transmission of control and configuration information; or as a traffic channel used for the user data. <NUM> new radio technology allows for the creation of multiple logical channels over a single radio bearer network using the <NUM> network slicing models. These logical channels are used to carry a specialized traffic between the UE device and the <NUM> network.

The <NUM> broadband utilizes millimeter waves for transmission which require additional power consumption for devices connecting to the <NUM> network.

<CIT> discloses a method of wireless communication includes receiving, by a first communication node, a signaling message from a second communication node. The signaling message includes information associated with a first mapping and a second mapping. The method includes performing, by the first communication node, a first transmission using the first mapping. The first mapping is established between a first radio bearer and a first radio link control channel, or between a second radio link control channel and a logical channel. The method also includes performing, by the first communication node, a second transmission using the second mapping. The second mapping is established between multiple radio bearers and a third radio link control channel, or multiple radio link control channels and the logical channel.

According to an embodiment of the present invention, a computer-implemented method, a computer program product, and a system for battery power savings of user equipment operating within a <NUM> network. The method provides for one or more processors initiating collection of transmission requirement data of logical channels for application-level data from a Service Data Adaptation Protocol (SDAP), and collection of logical channel identification (ID), application ID, and quality of service class identifier (QCI) indexing information. The one or more processors create a list of logical channels having acceptable QCI indexing for permissible transmission delay of packets, based on logical channel identification (ID), application ID and QCI indexing information. The one or more processors map the logical channels of the list to related radio link control (RLC) channels. The one or more processors, responsive to receipt of a packet by a RLC multiplexing layer, compare the RLC channel ID from a segmented automatic repeat request (ARQ) packet to the list of logical channels with permissible delay of transmission of packets. The one or more processors, responsive to a match between the RLC channel ID and the logical channels of the list, save the packet to an RLC data structure in allocated memory, and the one or more processors, responsive to receipt of a time-critical packet, submit the time-critical packet and the saved packet to a medium access control (MAC) carrier controller for transmission processing.

A preferred embodiment of the invention will now be described, by way of example only, and with reference to the following drawings:.

Embodiments of the present invention recognize that current mechanisms of radio access network (RAN) moderation do not include energy optimization features at the user equipment (UE) level. A <NUM> telecom network programming stack provides control and user plane separation (CUPS) architecture flexibility that offers differentiation between control and user plane selection enablement of faster data and instruction transition between the fixed accessed network (<NUM> core) and RAN. RAN optimizations are considered at the evolved node B (eNodeB) and fixed accessed network levels, such as the serving gateway (S-GW) and packet data network gateway (P-GW), however, embodiments of the present invention recognize an absence of energy consumption optimization and power savings at the UE level.

The current RAN moderation multiplexing and the dedicated traffic channel (DTCH) multiplexing at the UE level is unable to provide power-saving optimization, which is one of the current major limitations of transitioning to <NUM> networks. Further, it has been observed during initial research that <NUM> mobiles are consuming more power and frequently switching back to <NUM> network because of increased device temperature and overheating. Embodiments recognize that there is a need to operate <NUM>-UE devices that include improved operational capabilities with lower power consumption to reduce heat generation. Further, the <NUM> massive broadband operates on millimeter waves lengths, which requires more power consumption by user devices.

Embodiments of the present invention provide a method, computer program product, and system for an efficient mechanism of energy optimization for non-time-critical data transmission over a radio interface of a medium access control (MAC) based data exchange, which will work with existing UE multiplexing of <NUM> RLC. Embodiments perform at the multiplexing layer of the <NUM> User Plane (UP) stack of the UE by collecting the packet traffic information from various layered systems and determining which RLC packets are not delivery time-critical. Embodiments collect application-level data transmission requirements and the quality-of-service characteristic index (QCI), which are used to determine the processing of packets to a radio interface. Embodiments collect and form a list of DTCHs having acceptable QCI indexing for permissible delayed transmission and maps the traffic channels with related RLC channels. The decision point of including a permissible transmission delay is mapped using existing pre-defined configuration policies that coordinate with the dynamic sleep time of RLC multiplexing controllers.

When a packet is received at the RLC multiplexing layer for translation and radio allocation, embodiments of the present invention extract the RLC channel identification (ID) from the segmented automatic repeat request (SEG_ARQ) packet and map the ID to the list of permissible delayed data transmission enabled channels. If the RLC channel ID is matched to a data transmission enabled channel of the list, power consumption savings at the UE can be realized by reducing or delaying invocation of transport multiplexing at the MAC and carrier-based multiplexing of the packets. Embodiments of the present invention save the packets in additionally allocated memory accessible by the RLC controller, and the multiplexer polls for the priority delivery packet from other channels. The priority delivery packet is saved and waits in local memory for the hybrid automatic repeat request (HARQ) to awake and for the carrier controller to process the packet. The RLC controller and MAC based device connector functions are kept in a sleep mode while not in use.

In response to the RLC controller receiving a subsequent packet, the RLC extracts the application channel ID and examines related asynchronous field parameters. If the packet is initiated from an application serving a time-critical operation, demanding immediate delivery over a radio bearer, the carrier controllers are switched to an active state, and the time-critical packet and the asynchronous saved packet are submitted to the MAC carrier controller together for further processing. No latency is experienced by concurrently processing the packets due to carrier controller capabilities.

Because the physical carrier and MAC-based transport handling are battery power-intensive tasks, embodiments of the present invention save battery power by reducing active time for the RLC controller during receipt of non-time-critical packets and processing of the packets simultaneously by the MAC carrier controller. In some embodiments, embodiments can be engaged based on the available battery power of the UE device or automatically applied when the device power level is lower than a pre-defined threshold value. Embodiments manipulate logical channels of the network and apply application and channel delivery requirement information in determining the delay of packet transmission decisions for certain logical channels of the <NUM> network. The resulting delay of non-time-critical packet transmission reduces invocation of the physical radio interface that has high energy requirements. Embodiments minimize the active state of the RLC carrier controller, which increases the sleep mode, and delivery of asynchronous delayed packets occurs along with subsequently received time-critical DTCH packets.

Embodiments utilize available transportation bandwidth in a single carrier processing slot which improves optimization of resources. Embodiments perform an intelligent selection of packets by generating a list of application IDs, logical channels, and QCI characteristics and avoid impacts to application performance due to RLC processing. Embodiments apply to <NUM> networks as the third generation, the fourth generation, and LTE networks lack mechanisms by which packet information can be mapped to generated listings of applications and channels with permissible levels of transmission delay of packets. Some embodiments integrate the provided power management efficiencies of embodiments of the present invention as part of an energy-saving mode of a user equipment (UE) device.

The terminology used in the present application includes acronyms which are used for brevity and defined as follows for clarity:.

The present invention will now be described with reference to the Figures. <FIG> is a functional block diagram illustrating a distributed data processing environment, generally designated <NUM>, in accordance with an embodiment of the present invention. <FIG> provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. The descriptions of the various embodiments of the present invention have been presented for purposes of illustration but are not intended to be exhaustive or limited to the embodiments disclosed. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

In embodiments of the present invention, distributed data processing environment <NUM> is at least a <NUM> network that includes RLC <NUM>, SDAP <NUM>, PDCP layer <NUM>, MM-Wave Multiplexing layer140, and allocated memory160a, 160b, 160c, and 160d, all interconnected as components of a <NUM> network. <FIG> also depicts asynchronous packets <NUM> transferring from PDCP layer <NUM> to RLC <NUM>. To illustrate aspects of embodiments of the present invention, <FIG> depicts asynchronous packets <NUM>, which are asynchronous packets <NUM> that have been saved to allocated memory 160c and 160d as an example. Additionally, <FIG> illustrates synchronous packet <NUM>, which represents a time-critical packet that does not include permission for transmission delay.

Radio link control (RLC) <NUM> performs as a protocol used in <NUM> New Radio, located on top of the MAC layer and below the PDCP-layer. Radio link control <NUM> includes packet extractor <NUM>, memory allocator <NUM>, location mapper <NUM>, packet hold manager <NUM>, power-saving program <NUM>, and packet retriever logic <NUM>.

Packet extractor <NUM> identifies received packets and determines whether the packet has a time-critical delivery requirement. Packet extractor <NUM> extracts packets that have been confirmed with a non-time-critical delivery requirement by comparison with the list of DTCHs having acceptable QCI indexing for permissible delayed transmission and have mapped the traffic channels to related RLC channels. Memory allocator <NUM> designates memory pages to the RLC daemon, using existing memory allocation logic, for non-time-critical packets to be stored instead of submitting over radio network channels. The storage of the packet enables the initiation of a sleep state for the RLC carrier controller for transmission multiplexing at the medium access controller and carrier-based multiplexing.

Location mapper <NUM> provides pointers to the memory locations allocated by memory allocator <NUM> in which the non-time-critical packets are stored, to power-saving program <NUM>.

Packet hold manager <NUM> provides an incremental counter of packets held in additionally allocated memory and includes a validation function of a threshold value for holding of packets, which, if exceeded, initiates a wake-up state and processing of the number of stored packets that have met or exceeded the threshold holding value.

Packet retrieve logic <NUM> provides functions to locate and retrieve the packets stored in allocated memory, enabling a sleep state and power savings for the UE. In some embodiments, packet retrieve logic <NUM> is initiated by receipt and identification of a time-critical packet by the RLC. In other embodiments, packet retrieve logic <NUM> is initiated as a result of a packet holding count exceeding a threshold value, or detection of the RLC daemon as active for carrier transformer.

Power-saving program <NUM> operates with RLC <NUM>. In some embodiments, packet extractor <NUM>, memory allocator <NUM>, Location mapper <NUM>, packet hold manager <NUM>, and packet retrieve logic <NUM> are module components under the operational control of power-saving program <NUM>, providing functions enabling the saving of non-time-critical packets to memory storage and enabling a sleep state that saves battery power for UE. Discussion of power-saving program <NUM> includes functions that may be performed by the modules but, for simplicity and clarity, will be presented under the umbrella operation of power-saving program <NUM>.

Power-saving program <NUM> collects data from SDAP for logical channels for application-level data transmission requirements. The collected data includes radio channel (DTCH) identification from the upper layer of <NUM> UE user plane protocol and collects the quality-of-service class identifier (QCI), which are used to perform synchronous and asynchronous data transmission decisions. Power-saving program <NUM> stores the channel and QCI characteristics collected to metadata mapper classes. Power-saving program <NUM> initiates polling thread at RLC <NUM> for transport channel fetching and radio resource allocation for the UE. The polling includes DWDM or similar MM-Wave physical transmission technologies in which each transport channel is being allocated for a SLOT for data transmission.

Power-saving program <NUM> creates a list of logical channels having acceptable QCI indexing for permissible delayed transmission and maps the logical channels with related RLC channels. The determination of permissible transmission delay includes a mapping in which existing pre-defined configuration policies are used in coordination with the dynamic sleep time of RLC multiplexing controllers.

Power-saving program <NUM>, upon receipt of a packet by the RLC multiplexing layer, extracts the RLC channel ID from the segmented automatic repeat request (Seg-ARQ) packet and maps the extracted channel ID to the list indicating permissible delayed packet delivery per channel. Power-saving program <NUM> determines whether the RLC channel ID matches with the asynchronous data transmission enabled channel list and, if so, saves the packet in the allocated memory and does not immediately transmit the packet. The multiplexer polls other transport channels for non-critical priority packets with permissible delay. The saving of non-time-critical packets in memory removes output from the RLC multiplexer and enables a sleep state to initiate or be maintained. The sleep state saves battery power at the UE by avoiding constant radio resource allocation and allocation of a SLOT for data transmission, as well as activities placing data packets over the transport radio carrier, which are energy demanding.

Power-saving program <NUM> determines the receipt of a priority packet at the RLC controller. The determination of whether the received packet has a priority status as a time-critical for delivery packet includes extracting the RLC channel ID and related asynchronous field parameters and examining the RLC channel ID and parameters by comparison to the list of permissible delayed delivery logical channels-to-RLC channels mapping. Subsequent to confirmation that the RLC channel ID of the received packet does not match the list mapping related RLC channels to logical channels (synchronous priority packet), power-saving program <NUM> activates the RLC carrier modulator and multiplexer. The RLC carrier controller is activated for the case in which many packets are stored in memory and in the queue for delayed delivery. In the case in which the high bandwidth input/output (I/O) workload is on hold, the memory allocation manager (memory allocator <NUM>) module activates the RLC carrier controller. In some cases, the RLC carrier controller is activated when the return trip time (RTT) and the time to leave (TTL) attributes of packets are beyond permissible limits of transmission delay values. In some embodiments, the RLC carrier controller is activated at the UE-user plane stack in case the driver detects possible overhead by queue element manipulation of the UE Radio carrier slots.

Power-saving program <NUM> initiates retrieval of the saved packets from the allocated memory and submits the packets for processing by the MAC multiplexer layer, along with the synchronous priority packet received. The packets are processed in the same awake slot of the RLC carrier multiplexer, further reducing battery power consumed.

Power-saving program <NUM> continues polling for the SDAP or RLC for triggers that initiate a wake-up state.

SDAP <NUM>, known as the Service Data Adaptation Protocol layer, has responsibility for mapping between a quality-of-service flow from the <NUM> core network and a data radio bearer, as well as marking the quality-of-service flow identifier (QFI) in uplink and downlink packets. The SDAP also marks transmitted packets with the correct quality-of-service flow identification (QFI) then indicates the correct forwarding treatment of the packet as it traverses the <NUM> system.

PDCP Layer <NUM> provides services to user plane upper layers and radio resource control (RRC) acting as a protocol between UE and network base station, establishing the connection and release functions with a radio bearer. PDCP layer <NUM> has responsibility for the transfer of user plane data and control plane data, implementing ciphering and integrity checking of packet transmission.

MM-wave multiplexing layer <NUM> is a carrier signal generator of millimeter-wavelength waves (MM-waves) and provides multiplexing of packets for transmission. In some embodiments of the present invention, MM-wave multiplexing layer <NUM> includes medium access control (MAC) and logical link control (LLC) sublayers that.

Allocated memory 160a, b, c, and d represent memory pages allocated from RLC <NUM> by power-saving program <NUM> in which non-time-critical asynchronous packets are stored enabling a sleep mode in which UE power is saved until a time-critical packet is received and processed. Asynchronous packets saved in allocated memory enable a "sleep" state for transport channels working below RLC, which normally are continuously fetching radio resource allocation for the UE. <FIG> depicts asynchronous packets <NUM> as saved in allocated memory 160c, and 160d.

Asynchronous packets <NUM> are user plane data packets that are determined to be non-time-critical for delivery, based on the channel and application IDs and the QCI information included in the packet or packet header. Embodiments of the present invention determine whether received packets have a time-critical requirement, based on the application, logical channel, or QCI associated with the packet.

Synchronous packet <NUM> has a time-critical delivery requirement associated with the packet. Receipt of synchronous packet <NUM> initiates a wake-up response to sleep states and synchronous packet <NUM> is processed for transmission. In embodiments of the present invention, asynchronous packets <NUM> that are saved in allocated memory, such as 160c, and 160d, are retrieved and processed simultaneously along with synchronous packet <NUM>.

<FIG> illustrates operational steps of power-saving program <NUM>, operating in conjunction with RLC <NUM>, within distributed data processing environment <NUM> of <FIG>, in accordance with an embodiment of the present invention. Power-saving program <NUM> reduces the invocation of physical radio interface with user equipment (UE) connected to a <NUM> network. Power-saving program <NUM> determines whether received packets allow a delay in transmission and stores the non-time-critical packets in allocated memory, thus eliminating RLC flow over a radio network component, which allows the carrier controller to enter a sleep mode. Power-saving program <NUM> responds to receipt of a time-critical packet by initiating a wakeup state for the RLC carrier controller and submits the synchronous packet and asynchronous packets retrieved from memory, for transmission processing.

The transport channel layer, working below the RLC carrier controller, continuously fetches radio resource allocation for the UE. This typically works on DWDM or similar MM-Wave physical transmission technologies in which each transport channel is being allocated for a SLOT for data transmission. Based on the slots allocated, the data packets are being placed over the transport radio carrier, and the operation of placement of a data packet over the carrier radio wave consumes large amounts of energy and requires more battery power as the transport channel needs to be prepared for transmission. The preparation includes the transport channel being subscribed and decoded, and the packet needs to be formulated into the physical radio interface format. The transport channel operation of data packet placement requires MM-Wave transcription (millimeter), which is energy-hungry. Embodiments of the present invention collect channel and packet delivery information and create a list of DTCH (logical channels) having acceptable QCI indexing for permissible delayed transmission and, accordingly, maps the logical channels to related RLC channels. The permissible transportation delay feature will be mapped using existing pre-defined configuration policies in coordination with the dynamic sleep time of RLC multiplexing controllers.

Power-saving program <NUM> collects transmission requirement data of logical channels for application-level data (step <NUM>). Power-saving program <NUM> collects data from SDAP that includes logical channels for application-level data transmission requirements. Power-saving program <NUM> collects logical channel (DTCH) ID and QCI mapping characteristics indicating whether packet transmission is time-critical. In some embodiments, power-saving program <NUM> collects logical channel information from various layered systems and detects which RLC packets are not time-critical and collects QCI and application characteristics.

Power-saving program <NUM> creates a list of logical channels with permissible QCI indexing for transmission delay (step <NUM>). Power-saving program <NUM> determines the characteristics associated with non-time-critical packets from the collected logical channel information. Power-saving program <NUM> uses logical channel ID, QCI values, and application ID to determine the characteristics indicating packets with acceptable transmission delay permissions. Power-saving program <NUM> creates a listing of the logical channels that include the asynchronous non-time-critical packets that include permissible transmission delay.

Power-saving program <NUM> maps logical channels of the list to related radio link control (RLC) channels (step <NUM>). Power-saving program <NUM> maps the list of logical channels having characteristics of permissible delay of packet transmission to the related RLC channels. In some embodiments, the decision of permissible transmission delay channels will be mapped using existing pre-defined configuration policies in coordination with the dynamic sleep time of the RLC multiplexing controllers. In some embodiments, mapping of logical channels to RLC tables of channels is based on application-derived APIs or QCI characteristics and allowed tolerance and transmission delay values.

Power-saving program <NUM> compares the RLC channel ID to the list of logical channels in response to receiving a packet (step <NUM>). Power-saving program <NUM> determines a packet is received at the RLC multiplexing layer for translation and radio allocation. Power-saving program <NUM> extracts the RLC channel ID from a segmented automatic repeat request packet (Seg-ARQ) and performs a mapping of the RLC channel ID to the asynchronous data transmission enabled channel list. Comparison of the RLC channel ID of the received packet to the list of logical channels identified as having characteristics accepting delay of packet transmission determines whether the received packet is a non-time-critical asynchronous packet.

Power-saving program <NUM> saves the packet to an RLC data structure in allocated memory in response to determining a match between the RLC channel ID of the packet and the logical channels identified in the list (step <NUM>). Having determined that the received packet RLC channel ID is matched in the list of logical channels having acceptable transmission delay permissions (i.e., non-time-critical packets), power-saving program <NUM> saves the packet in the allocated memory. Power-saving program <NUM> determines the pointers to the memory address at which the packet is saved. In some embodiments, the holding packet counter is incremented, reflecting the quantity of packets saved to the allocated memory.

For example, a packet of asynchronous packets <NUM> is received and transported to RCL <NUM>. Power-saving program <NUM> extracts the RLC channel ID from an ARQ packet and compares the RLC channel ID to the list of logical channels identified as having characteristics accepting delayed transmission of packets. Power-saving program <NUM> determines that the RLC channel ID of the received packet of asynchronous packets <NUM> maps to the list of logical channels and initiates saving of the received packet to a location address in allocated memory 160c. Power-saving program <NUM> determines the pointers to the memory location at which the packet is saved.

Power-saving program <NUM> submits time-critical packet and saved packet(s) to a medium access control (MAC) carrier for transmission, in response to receipt of a time-critical packet (step <NUM>). Power-saving program <NUM> continues to poll the RLC carrier for receipt of packets and compares the RCL channel ID and packet transmission requirement information to the list of logical channels that accept delayed packet transmission. In response to determining the received packet is a time-critical priority packet power-saving program <NUM> initiates a wakeup state for the hybrid automatic repeat request (HARQ) and RCL carrier controller, activating the RLC carrier modulator and multiplexer. Power-saving program <NUM> retrieves the saved packet(s) from the allocated memory (i.e., via memory address pointers) and submits the time-critical packet and the retrieved saved packet(s) to the MAC carrier (i.e., MM-Wave multiplexing) for processing and transmission.

For example, power-saving program <NUM> determines that the RLC carrier controller receives a packet and determines that the RLC channel ID does not match the RLC channel IDs of the list mapping to logical channels accepting delayed packet transmission. The received packet has a time-critical characteristic and power-saving program <NUM> ends a sleep state and initiates a wakeup state for the RLC carrier control and HARQ. Power-saving program <NUM> retrieves the saved packets in allocated memory and submits the saved packets and the time-critical packet to the MAC carrier for processing and transmission.

In some embodiments, the RLC carrier control is activated due to exceeding a holding count threshold of packets stored in allocated memory. In other embodiments, power-saving program <NUM> activates the RLC carrier controller from a sleep state due to RTT and TTL values that exceed permissible limits of transmission delay. In yet other embodiments, power-saving program <NUM> activates the RLC carrier controller in the case that the high bandwidth I/O workload is on hold.

<FIG> depicts a block diagram of components of system <NUM>, which includes computing device <NUM>. Computing device <NUM> includes components and functional capability similar to RCL <NUM>, (<FIG>), in accordance with an illustrative embodiment of the present invention. It should be appreciated that <FIG> provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environment may be made.

Computing device <NUM> includes communications fabric <NUM>, which provides communications between computer processor(s) <NUM>, memory <NUM>, persistent storage <NUM>, communications unit <NUM>, and input/output (I/O) interface(s) <NUM>. Communications fabric <NUM> can be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system. For example, communications fabric <NUM> can be implemented with one or more buses.

Memory <NUM>, cache memory <NUM>, and persistent storage <NUM> are computer readable storage media. In this embodiment, memory <NUM> includes random access memory (RAM) <NUM>. In general, memory <NUM> can include any suitable volatile or non-volatile computer readable storage media.

Power-saving program <NUM> is stored in persistent storage <NUM> for execution by one or more of the respective computer processors <NUM> via one or more memories of memory <NUM>. In this embodiment, persistent storage <NUM> includes a magnetic hard disk drive. Alternatively, or in addition to a magnetic hard disk drive, persistent storage <NUM> can include a solid-state hard drive, a semiconductor storage device, read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, or any other computer readable storage media that is capable of storing program instructions or digital information.

Communications unit <NUM>, in these examples, provides for communications with other data processing systems or devices, including resources of distributed data processing environment <NUM>, such as PDCP layer <NUM>, and MM-wave multiplexing layer <NUM>. In these examples, communications unit <NUM> includes one or more network interface cards. Communications unit <NUM> may provide communications through the use of either or both physical and wireless communications links. Power-saving program <NUM> may be downloaded to persistent storage <NUM> through communications unit <NUM>.

I/O interface(s) <NUM> allows for input and output of data with other devices that may be connected to computing system <NUM>. For example, I/O interface <NUM> may provide a connection to external devices <NUM> such as a keyboard, keypad, a touch screen, and/or some other suitable input device. External devices <NUM> can also include portable computer readable storage media such as, for example, thumb drives, portable optical or magnetic disks, and memory cards. Software and data used to practice embodiments of the present invention, e.g., power-saving program <NUM>, can be stored on such portable computer readable storage media and can be loaded onto persistent storage <NUM> via I/O interface(s) <NUM>. I/O interface(s) <NUM> also connect to a display <NUM>.

Display <NUM> provides a mechanism to display data to a user and may be, for example, a computer monitor.

The programs described herein are identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature herein is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.

Claim 1:
A computer-implemented method for battery power-savings of user equipment operating within a <NUM> network, the method comprising:
Initiating (<NUM>), by one or more processors, a collection of transmission requirement data of logical channels for application-level data from a Service Data Adaptation Protocol, wherein logical channel identification, ID, application ID, and quality of service class identifier, QCI, indexing information is collected;
creating (<NUM>), by the one or more processors, a list of the logical channels having acceptable QCI indexing for permissible transmission delay of packets, based on the logical channel identification, ID, application ID, and QCI indexing information;
mapping (<NUM>), by the one or more processors, the list of the logical channels to related radio link control, RLC, channels;
responsive to receipt of a packet by an RLC multiplexing layer, comparing (<NUM>), by the one or more processors, an RLC channel ID from a segmented automatic repeat request, ARQ, packet to the list of the logical channels with a permissible delay of transmission of packets;
responsive to a match between the RLC channel ID and the list of the logical channels, saving (<NUM>), by the one or more processors, the packet to allocated memory in an RLC data structure; and
responsive to receipt of a time-critical packet, submitting (<NUM>), by the one or more processors, the time-critical packet and the saved packet to a medium access control, MAC, carrier controller for transmission processing.