Spare Extension Field Management in 3GPP Frame Protocols
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The lack of clear specification in 3GPP frame protocols for using Spare Extension (SE) fields in data frames makes it difficult to add new Information Elements (IEs) across different releases, leading to compatibility issues and restricted data capacity due to a small SE field size.
Innovation Solution
Incorporating a New IE Flags IE to indicate valid data in the SE section, with a Spare Extension Flag and SE Length IE to manage the order and length of IEs, allowing backward compatible additions and increasing the SE field size to match control frames.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If the SE field size is increased to match control frames (32 octets), then data capacity is expanded, but the frame structure complexity increases
Solution Approach 1:
The SE field size is made dynamic rather than fixed. The SE Length IE dynamically specifies the actual length of the SE field (0-32 octets), allowing the frame structure to adapt to different data requirements. This resolves the contradiction by providing large capacity when needed while maintaining simplicity when the SE field is not used or uses minimal space.
2Adaptability or versatility
If new IEs are added in later releases without clear SE usage specification, then adaptability improves, but compatibility with earlier releases deteriorates
Solution Approach 1:
The New IE Flags IE is introduced in advance to mark the presence and positions of new IEs before they are actually added to the frame. This preliminary action allows receiving nodes to prepare for and correctly interpret new IEs when they appear, ensuring backward compatibility while enabling future adaptability.
Solution Approach 2:
The New IE Flags IE acts as an intermediary between old and new frame formats. It provides a transition mechanism that allows nodes implementing earlier releases to correctly identify and handle frames with new IEs added in later releases, maintaining compatibility while enabling evolution.
3Adaptability or versatility
If the SE field is used to add new IEs, then adaptability improves, but the difficulty of detecting and measuring SE usage increases
Solution Approach 1:
The New IE Flags IE provides visual (binary) indicators that clearly mark which portions of the SE field contain valid new IEs. Each flag bit acts like a color marker, making it immediately detectable whether new IEs are present and where they are located, eliminating the difficulty of detecting SE usage.
4Device complexity
If the SE field size is restricted to 2 octets in data frames, then frame structure simplicity is maintained, but data capacity is overly restricted
Solution Approach 1:
The SE field size is changed from a fixed 2 octets to a dynamic size (0-32 octets) controlled by the SE Length IE. This allows the frame structure to remain simple when the SE field is small or not used, while providing expanded capacity when larger SE fields are required, resolving the contradiction between simplicity and capacity.
Data Source
AI summary
A protocol (and corresponding equipment) for use in communicating between a sending node (11) and a receiving node (12) a frame (10) including a Spare Extension (SE) section conveying values for one or more information element (IE) fields, and also including a New IE Flags IE or other device for indicating to the receiving node (12) whether the SE section includes valid data for each IE in the SE section. A flag indicating whether valid data is provided in the SE section can be used, and also an IE indicating the length of the SE section. The protocol is such that the receiving node (12) treats an IE field value occurring in the SE section as spare bits if the IE field was introduced for a version of a later release of a specification than that according to which the receiving node (12) was implemented.