RLC Protocol Activation Bits for Radio Network Functionality

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for activating or deactivating radio network (RN) functionality in WCDMA systems rely on 3GPP standardized signaling, which is inadequate for proprietary or non-standard RN functionality, lacking an efficient method to manage these functionalities without altering existing standards.

Innovation Solution

The introduction of new functionality in the Radio Link Control (RLC) protocol that allows for the activation and deactivation of RN and User Equipment (UE) functionality using standardized messages within the RRC protocol, specifically utilizing reserved bits in the PDU Type, Super Field, Header Extension, and Length Indicator fields, enabling proprietary or standardized implementation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If 3GPP standardized signaling is used to activate or deactivate RN functionality, then standardization and interoperability are improved, but the ability to support proprietary or non-standard RN functionality deteriorates

Engineering Contradiction:
ImprovestandardizationVSAvoidproprietary functionality support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary mechanism by embedding functionality indication bits within existing standardized RLC protocol fields (PDU Type, Super Field, Header Extension, Length Indicator). This intermediary approach allows proprietary functionality to be signaled through standardized channels, maintaining interoperability while enabling vendor-specific features without requiring changes to 3GPP standards.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If existing 3GPP RRC protocol signaling is used, then protocol compatibility is improved, but the efficiency of activating proprietary RN functionality deteriorates

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidfunctionality activation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent extracts the functionality activation mechanism from the higher-layer RRC protocol and implements it directly at the RLC layer using reserved bits in existing fields. This extraction eliminates the need for lengthy RRC signaling exchanges, enabling faster and more efficient activation of proprietary functionality while maintaining protocol compatibility through standardized RLC message structures.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If new RLC protocol functionality is introduced, then the ability to support proprietary RN functionality is improved, but protocol complexity deteriorates

Engineering Contradiction:
Improveproprietary functionality supportVSAvoidprotocol structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a single RLC layer mechanism that serves multiple purposes: it supports both standardized and proprietary RN functionality, works with existing RLC message types, and maintains backward compatibility. The functionality indication bits can represent various functions (activation, deactivation, configuration) using the same protocol structure, avoiding the need for separate signaling mechanisms for different scenarios.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10009212B2Method and apparatus for activation and deactivation of radio network functionality
Publication Date: 2018.06.26 GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
  • US10009212B2 patent drawing
  • US10009212B2 patent drawing
  • US10009212B2 patent drawing

AI summary

A method implemented in a first peer entity communicating with a second peer entity using a predetermined protocol includes receiving a first packet from the second peer entity. The method further includes identifying an instruction field included within the first packet, the instruction field indicating a predetermined function to be performed by the first peer entity. The method further includes determining whether the predetermined function can be performed by the first entity. The method also includes transmitting a second packet to the second peer entity indicating whether the first entity performs the predetermined function.