Receipt Status Reporting Flexibility in Communication Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for data unit receipt status reporting in communication networks lack flexibility, as they typically allow only one type of status report to be sent at a fixed periodicity, which can lead to inefficient use of transmission resources and inadequate control over data transmission.

Innovation Solution

Implementing a method that configures communication devices to send two different types of receipt status reports with distinct periodicities, allowing for more flexible and efficient reporting by associating a first status report type with a first reporting periodicity parameter and a second status report type with a second reporting periodicity parameter, enabling simultaneous parallel reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single type of status report is sent at a fixed periodicity, then the system operation is simple, but the reporting flexibility and resource efficiency are poor

Engineering Contradiction:
Improvereporting flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the single status report type into multiple report types (first status report type and second status report type), each with different periodicity parameters. This segmentation allows the system to send different types of status reports at different intervals, improving reporting flexibility while maintaining manageable complexity through structured configuration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic configurability by allowing the network device to configure multiple reporting periodicity parameters (first reporting periodicity parameter and second reporting periodicity parameter) that can be adjusted based on network conditions and requirements. This dynamic approach enables the system to adapt reporting behavior to changing conditions, improving versatility without requiring complete system redesign.

Inventive Principle:
Principle #15Dynamics

2Reliability

If detailed status reports are sent frequently, then transmission control is improved, but resource consumption increases

Engineering Contradiction:
Improvetransmission controlVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by assigning different reporting periodicities to different status report types based on their specific needs. The first status report type can be sent with higher frequency when detailed transmission control is needed, while the second status report type uses lower frequency when resource conservation is prioritized. This localized optimization of reporting frequency for different report types resolves the contradiction between reliability and resource consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes the periodicity parameter dynamically by configuring at least two different reporting periodicity parameters. The network can adjust which periodicity parameter applies to which report type based on current network conditions, traffic patterns, and reliability requirements. This parameter flexibility allows the system to optimize the balance between transmission control quality and resource consumption.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3411977B1Methods and devices for receipt status reporting
Publication Date: 2020.01.01 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3411977B1 patent drawingFigure 1
  • EP3411977B1 patent drawingFigure 2
  • EP3411977B1 patent drawingFigure 3

AI summary

A method of receipt status reporting in a communication device (110), comprising configuring (SI) said communication device for periodic receipt status reporting by associating a first status report type with a value of a first reporting periodicity parameter and associating a second status report type with a value of second reporting periodicity parameter, said first status report type being different from said second status report type and said first reporting periodicity parameter being different from said second reporting periodicity parameter, and periodically (S2) sending receipt status reports of said first type according to said associated value of said first reporting periodicity parameter and receipt status reports of said second type according to said associated value of said second reporting periodicity parameter.