Uplink Configured Grant Release Validation via Non-Fallback DCI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques for validating the release of semi-statically configured communications in wireless systems, such as uplink configured grants and semi-persistent scheduling, are limited, particularly in using non-fallback DCI for ensuring invalid resource assignments, which can lead to issues in configuring SPS and Type 2 configured grant configurations across different component carriers.
Innovation Solution
The use of non-fallback DCI scrambled with a configured scheduling radio network temporary identifier (CS-RNTI) for release validation, where the FDRA bit field is set to indicate an invalid resource assignment based on resource allocation types, allowing for efficient release validation of downlink SPS and uplink Type 2 configured grants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing validation techniques are used for release of semi-statically configured communications, then the system maintains basic operational capability, but release validation reliability is limited and cannot properly handle configurations across different component carriers
Solution Approach 1:
The patent changes the validation parameter from checking DCI format type (fallback vs. non-fallback) to checking the validity of resource assignment values within DCI fields. Specifically, it validates whether frequency domain resource assignment (FDRA) and time domain resource assignment (TDRA) bit fields contain valid resource assignments according to configured resource allocation rules. This parameter change enables reliable validation across all DCI formats and different component carrier configurations.
Solution Approach 2:
Instead of validating release by confirming the DCI format type (the conventional approach), the patent inverts the validation logic by checking for invalid resource assignments. The core insight is that a release DCI will intentionally contain invalid resource assignment values, so validation succeeds by detecting these invalid values rather than by confirming format characteristics. This inversion resolves the contradiction by making validation independent of DCI format type and component carrier configuration.
2Adaptability or versatility
If non-fallback DCI is used for release validation, then configuration flexibility across component carriers is improved, but the complexity of ensuring invalid resource assignments increases
Solution Approach 1:
The validation mechanism uses the DCI message's own resource assignment fields to perform self-validation. The DCI contains FDRA and TDRA bit fields that are interpreted according to pre-configured resource allocation rules (resource allocation type 0 or type 1). The validation logic checks whether these fields contain valid resource assignments according to the configured rules, without requiring external validation data or complex format-specific handling. This self-service approach reduces complexity while maintaining flexibility across component carriers.
Solution Approach 2:
The patent creates a universal validation mechanism that works across all DCI formats (fallback and non-fallback) and all component carrier configurations. The validation logic universally checks FDRA and TDRA field validity according to configured resource allocation types, without requiring format-specific or carrier-specific validation rules. This universal approach simplifies the system by replacing multiple format-specific validation paths with a single multi-functional validation process.
3Measurement precision
If resource allocation fields are set to indicate invalid assignments for release validation, then release detection accuracy is improved, but signaling overhead increases
Solution Approach 1:
The patent converts the potential harm of using resource allocation fields for dual purposes (both resource assignment and release indication) into a benefit. By intentionally setting FDRA and TDRA fields to invalid values for release DCIs, the system uses these fields as both data carriers and validation markers. This approach does not increase signaling overhead because the same bit fields are used, but it improves release detection accuracy by providing clear, unambiguous invalid value patterns that distinguish release DCIs from activation DCIs.
Solution Approach 2:
The patent merges the resource assignment indication function and the release validation function into a single mechanism using the same DCI fields (FDRA and TDRA). Instead of requiring separate fields or additional signaling for release validation, the system combines both functions by interpreting the validity of resource assignment values. This merging reduces signaling overhead while maintaining high detection accuracy, as the validation information is embedded within the existing resource allocation fields without requiring additional bits.
Data Source
AI summary
Methods, systems, and devices for wireless communications are described that support techniques for release validation of uplink configured grants and semi-persistent scheduling (SPS). For example, downlink SPS and uplink configured grants may be released using non-fallback downlink control information (DCI). In such cases, a resource allocation field within the DCI may be based on a type of resource allocation configured for the UE, which may enable an invalid assignment to be indicated to the UE for release of the semi-statically configured communications. In other cases, the fields within the DCI may include predefined values that are used for indicating the release. A UE may validate whether the DCI activates or releases the downlink SPS or uplink configured grant based on the value of bit fields within the DCI.