Dynamic Packet Bearer Mapping via Routing Level Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 3GPP standards lack a flexible and dynamic method for associating data packets with bearers in user equipment, leading to inflexible configurations and vendor-specific application development, which complicates the mapping of data packets to appropriate quality of service (QoS) and increases development costs due to access and vendor specificity.

Innovation Solution

A method that allows user equipment to establish multiple packet bearers with different QoS, where a control entity determines the appropriate bearer for data packet flows using operator policy rules, and a packet filter associates data packets with the determined bearer based on routing level identification, enabling flexible mapping and access-agnostic application development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current 3GPP standards are used for mapping data packets to bearers, then the system maintains standard compliance, but the configuration becomes inflexible and vendor-specific

Engineering Contradiction:
Improveflexibility in bearer configurationVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic bearer configuration where packet filters and QoS parameters can be modified in real-time based on traffic flow requirements. The system transitions from static, vendor-specific configurations to dynamic, policy-driven configurations that adapt to changing network conditions and service requirements.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The invention changes the configuration parameters from fixed, vendor-specific values to flexible, policy-based parameters. The system allows modification of QoS parameters, bearer characteristics, and packet filter rules through operator policies and network control, enabling adaptable service differentiation without increasing device complexity.

Inventive Principle:
Principle #35Parameter changes

2Ease of manufacture

If vendor-specific application development is required, then the system supports current implementation standards, but development costs increase

Engineering Contradiction:
Improveapplication development easeVSAvoidaccess-agnostic capability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal bearer configuration mechanism that works across different access networks and vendor implementations. By using standardized packet filters and QoS parameters that can be dynamically configured through operator policies, the system enables single applications to operate across multiple access types without vendor-specific customization.

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

Solution Approach 2:

The invention introduces an intermediary layer of operator policies and network-controlled configuration between the application and the underlying access network. This intermediary abstracts the complexity of vendor-specific implementations, allowing applications to develop once and deploy anywhere while the network handles the vendor-specific mapping and configuration details.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If prior configuration is required for packet-bearer mapping, then the system maintains control over QoS, but the configuration process becomes complex

Engineering Contradiction:
ImproveQoS controlVSAvoidconfiguration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent enables the system to automatically configure packet filters and bearer mappings based on pre-defined operator policies. Instead of requiring manual, complex configuration procedures, the network self-configures the appropriate QoS parameters and packet filter rules when traffic flows are detected, maintaining reliable QoS control while eliminating configuration complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The invention implements preliminary configuration of operator policies and QoS rules before actual traffic flows occur. The system pre-establishes the mapping between packet filter characteristics and bearer QoS parameters, so that when traffic flows are detected, the configuration is automatically applied without requiring complex real-time configuration processes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8817610B2Method and devices for installing packet filters in a data transmission
Publication Date: 2014.08.26 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US8817610B2 patent drawing
  • US8817610B2 patent drawing
  • US8817610B2 patent drawing

AI summary

A method is described for associating a data packet (DP) with a packet bearer (PB) in a user equipment (UE1) of a communication network. The data packet is sent in a data flow from an application function of the user equipment, the packet bearer (PB) is established with the user equipment to transmit the data packet (DP) over the communication network towards a further entity, and the user equipment is adapted to establish different packet bearers. The method comprises the steps of identifying the flow with the data packet in a control entity of the communication network, determining the packet bearer for association with said flow from the different packet bearers in a policy function of the control entity, determining a routing level identification of the further entity, instructing the user equipment to install a packet filter based on the routing level identification, wherein the packet filter associates data packets comprising the routing level identification of the further entity with the determined packet bearer, providing the routing level identification to the application function, including the routing level identification into the data packet, and forwarding the data packet (DP) on the determined packet bearer (PB). A corresponding network, control entity, monitoring entity and computer program are also described.