Service-Type Identifier Assignment for Mobile Network Resource Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for assigning Internet Protocol (IP) addresses to mobile devices do not consider the network resources required for their interaction with cloud services, leading to sub-optimal network performance, including dropped connections and uneven bandwidth allocation.

Innovation Solution

A method that associates a service type with each mobile device, mapping it to a specific identifier that determines the frame-forwarding treatment within the network fabric, ensuring optimal resource allocation by assigning IP addresses and other device identifiers based on dynamic policies linked to traffic-management algorithms deployed by network elements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IP addresses are assigned by DHCP server without considering network capabilities, then device connectivity is established, but network performance deteriorates due to sub-optimal resource allocation

Engineering Contradiction:
Improvenetwork performanceVSAvoididentifier assignment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent pre-associates identifiers with service types before actual device connection. The network element maintains a mapping between service types and identifiers, so when a device connects, the appropriate identifier is already predetermined based on the service type, eliminating the need for complex real-time analysis during connection establishment

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter being used for identifier assignment from generic DHCP allocation to service-type-based allocation. By categorizing devices according to their service requirements (e.g., voice, data, video) and assigning identifiers accordingly, the system optimizes network resource allocation to match actual service needs rather than using uniform assignment

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If QoS settings are encoded into data packets, then service differentiation is attempted, but user experience deteriorates due to inconsistent application usage and poor results

Engineering Contradiction:
Improveservice differentiation capabilityVSAvoidapplication consistency
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

Instead of requiring applications to set QoS parameters in packets (bottom-up approach), the patent inverts the approach by having the network element assign identifiers based on service type (top-down approach). This eliminates dependency on application-level QoS configuration and ensures consistent service differentiation at the network level regardless of application behavior

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces service type as an intermediary category between the device and the identifier assignment. Rather than directly mapping devices to identifiers or relying on application QoS settings, the service type acts as a mediator that translates device capabilities into appropriate identifier assignments, ensuring consistent and appropriate resource allocation

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If identifiers are assigned without service type consideration, then assignment simplicity is maintained, but resource allocation efficiency deteriorates leading to dropped connections and high latency

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoididentifier assignment mechanism
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The network element performs preliminary association of identifiers with service types before actual device connection. This pre-mapping allows the system to quickly assign appropriate identifiers based on service type without complex real-time analysis, improving resource allocation efficiency while keeping the assignment mechanism relatively simple

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the assignment criterion from generic device identification to service-type-based identification. By categorizing devices according to their service requirements and assigning identifiers that correspond to appropriate resource allocation profiles, the system improves productivity without significantly increasing complexity

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9197560B2Assigning identifiers to mobile devices according to their data service requirements
Publication Date: 2015.11.24 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH
  • US9197560B2 patent drawing
  • US9197560B2 patent drawing
  • US9197560B2 patent drawing

AI summary

A network fabric includes a mobile device associated with a service type and a server including a processor and memory storing program code for assigning identifiers to mobile devices in accordance with an identifier assignment policy. The processor, in response to executing the program code stored in the memory, associates a service type with the mobile device, maps the service type to an identifier predetermined to cause frames bearing the identifier to receive a particular frame-forwarding treatment within the network fabric, assigns the identifier to the mobile device based on the service type of the mobile device, and sends the identifier to the mobile device for inclusion in frames transmitted by the mobile device.