Network Resource Allocation for Reduced Capability Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network resource schedulers fail to recognize reduced capability devices (RedCap devices), leading to inefficient resource allocation and potential over-allocation, which frustrates network operators and service providers by not distinguishing between service classes effectively.

Innovation Solution

A system that identifies RedCap devices and allocates network resources based on device type, quality of service requirements, and network availability, using a processing system to determine appropriate resource allocation, including bandwidth, MIMO layers, and modulation order.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If network resource schedulers allocate resources without recognizing RedCap devices, then resource allocation is simplified, but resource allocation efficiency deteriorates due to over-allocation

Engineering Contradiction:
Improvescheduler complexityVSAvoidresource allocation efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments network devices into different capability categories (full-capability devices and RedCap devices) and applies different resource allocation strategies to each segment. The scheduler identifies RedCap devices and allocates resources specifically suited to their reduced capabilities, preventing over-allocation while maintaining efficiency for full-capability devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic resource allocation where the scheduler adjusts resource allocation based on real-time device capability identification. The system dynamically determines whether a device is a RedCap device and modifies allocation parameters accordingly, allowing resource allocation to adapt to device capabilities rather than using a static approach.

Inventive Principle:
Principle #15Dynamics

2Reliability

If network resources are over-allocated to RedCap devices, then service quality is maintained, but network resource utilization deteriorates

Engineering Contradiction:
Improveservice qualityVSAvoidnetwork resource utilization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by providing different service quality levels to different device types. RedCap devices receive resource allocations optimized for their specific capabilities, while full-capability devices receive allocations suited to their higher performance requirements. This ensures each device type receives appropriate service quality without wasting resources on over-provisioning.

Inventive Principle:
Principle #3Local quality

3Ease of operation

If network schedulers do not distinguish between device types, then scheduling operations are simplified, but service class differentiation deteriorates

Engineering Contradiction:
Improvescheduling operation simplicityVSAvoidservice class differentiation
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements preliminary action by having devices indicate their capability type (RedCap or full-capability) before resource allocation occurs. The scheduler receives and processes this capability information in advance, allowing service class differentiation to be established before the actual scheduling decision is made, thus maintaining both simplicity and adaptability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240291770A1Apparatuses and methods for faciliating an identification and scheduling of resources for reduced capability devices
Publication Date: 2024.08.29 AT&T INTELLECTUAL PROPERTY I L P
  • US20240291770A1 patent drawing
  • US20240291770A1 patent drawing
  • US20240291770A1 patent drawing

AI summary

Aspects of the subject disclosure may include, for example, obtaining data pertaining to a plurality of user equipment and a plurality of network resources, analyzing the data to identify that a first user equipment included in the plurality of user equipment is a reduced capability device, based on the analyzing, allocating first network resources included in the plurality of network resources to the first user equipment, resulting in a first allocation, and based on the analyzing, allocating second network resources included in the plurality of network resources to a second user equipment included in the plurality of user equipment, resulting in a second allocation. Other embodiments are disclosed.