Non-IP EPS Bearer Protocol for MTC Device Complexity Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing demand for spectrum in cellular networks, driven by both data-intensive devices and low-bandwidth Machine Type Communication (MTC) devices, poses challenges in reducing communication complexity and maintaining user experience while managing network resources efficiently.

Innovation Solution

The implementation of a Non-Internet Protocol (Non-IP) Evolved Packet switched System (EPS) bearer protocol that eliminates the need for TCP/IP encapsulation and header compression, using a lightweight protocol to encapsulate non-IP traffic over S1, S5/S8, or S12 interfaces, thereby reducing UE complexity and overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If TCP/IP encapsulation and header compression are used for data transmission, then network compatibility and data routing are improved, but UE complexity and processing overhead increase

Engineering Contradiction:
Improvenetwork compatibilityVSAvoidUE complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts and removes the TCP/IP encapsulation layer from the data transmission path by implementing a Non-IP EPS bearer. This eliminates the need for UE to maintain TCP/IP stacks, directly reducing device complexity while preserving network compatibility through alternative routing mechanisms at the network layer.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary non-IP data format with its own header structure that mediates between the UE and the network. This intermediary format allows direct transmission without TCP/IP encapsulation, reducing UE processing complexity while maintaining network compatibility through the standardized non-IP bearer protocol.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If TCP/IP stacks and header compression are implemented in UE, then data transmission compatibility is improved, but battery consumption and processing power increase

Engineering Contradiction:
Improvedata transmission compatibilityVSAvoidbattery life
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent removes the energy-consuming TCP/IP stack implementation from the UE by using a non-IP bearer. This extraction eliminates the continuous processing overhead of TCP/IP encapsulation and decompression, directly reducing battery consumption while maintaining data transmission compatibility through the alternative non-IP protocol path.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If dedicated bearers are established for each UE, then network resource allocation and QoS are improved, but signaling overhead and network complexity increase

Engineering Contradiction:
Improvenetwork resource allocationVSAvoidnetwork complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple UE data streams into a single non-IP bearer by using unique non-IP data formats and identifiers for each UE. This consolidation reduces the number of separate dedicated bearers needed, lowering network complexity and signaling overhead while maintaining reliable resource allocation through the unified non-IP transmission path.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3329714B1Device and method using non IP-based EPS bearer
Publication Date: 2020.08.12 INTEL CORP
  • EP3329714B1 patent drawingFigure 1~2
  • EP3329714B1 patent drawingFigure 3~4B
  • EP3329714B1 patent drawingFigure 5~6

AI summary

Devices and methods of using a reduced complexity network protocol are generally described. An evolved NodeB (eNB) transmits an Attach Request to a mobility management entity (MME), which transmits a Create Session Request for transmission of non-IP (NIP) data of user equipment (UE) to a Packet Data Network (P-GW). The P-GW in response transmits a Create Session Response, with the UE ID if originating at the P-GW and free from a UE IP address and an Up Link Traffic Flow Template, to the MME, which transmits an Attach Accept to the eNB and UE. A UE identifier (UE ID) either originates at the UE and is transmitted in the Attach Request, or is generated by the eNB, MME or P-GW. The NIP data has a tunneling NIP data packet with a NIP header with the UE ID and a NIP user data packet free from TCP/IP encapsulation and header compression.