UMTS RRC Message Encapsulation for Fast Call Setup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current UMTS systems experience long call setup delays due to extensive signaling procedures, which negatively impact Quality of Service for services sensitive to such delays, such as interactive games and Push to talk Over Cellular services.

Innovation Solution

A method that encapsulates a Service Request in a RRC CONNECTION REQUEST, allowing earlier transmission to the CN, simplifies NAS signaling by omitting authentication and security procedures, and combines RRC Connection Setup with RB Setup to reduce delays, utilizing pre-configured semi-static channel parameters for faster channel establishment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If extensive signaling procedures are used for call setup in UMTS systems, then connection reliability is improved, but call setup delay increases

Engineering Contradiction:
Improveconnection reliabilityVSAvoidcall setup delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and removes unnecessary signaling steps from the call setup procedure. Specifically, it omits authentication and security procedures that are not required for the particular service being established, thereby reducing call setup delay while maintaining sufficient connection reliability for the service at hand.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary actions by pre-configuring semi-static channel parameters before the actual call setup is needed. This allows the system to skip certain configuration steps during the call setup process, reducing delay while ensuring reliable connections are established with pre-prepared parameters.

Inventive Principle:
Principle #10Preliminary action

2Stability of the object's composition

If multiple separate setup procedures (RRC connection, NAS signaling, RAB establishment) are executed sequentially, then connection stability is improved, but call setup delay increases

Engineering Contradiction:
Improveconnection stabilityVSAvoidcall setup delay
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent merges multiple separate setup procedures into a more integrated process. By combining RRC connection setup with NAS signaling and RAB establishment steps, the system reduces the number of sequential operations while maintaining the stability and reliability of each individual connection layer through coordinated execution.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If complete authentication and security procedures are performed during call setup, then security reliability is improved, but call setup delay increases

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidcall setup delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent selectively removes authentication and security procedures from the call setup process when they are not required for the specific service being established. This extraction of unnecessary security steps significantly reduces call setup delay while maintaining security reliability through service-appropriate authentication mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS7853259B2Methods for air interface message transfer in fast call setup processes
Publication Date: 2010.12.14 SPREADTRUM
  • US7853259B2 patent drawing
  • US7853259B2 patent drawing
  • US7853259B2 patent drawing

AI summary

A method of UU message transfer for fast call setup. The method includes encapsulating a Service Request into a RRC Connection Request. When a UE starts the service sensitive to call setup delay, the RRC layer encapsulates the Service Request into IDT. If this encapsulation is successful, the RRC connection request message undergoes non-critical extension, and the encapsulated IDT is disposed into the extended portion. The RNC, after receiving the extended RRC connection request, extracts the IDT message from the extended RRC CONNECTION REQUEST and sends it to the CN.