Operation Request Generation for Multi-Protocol Packet Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing devices face complexity in supporting multiple protocols and scenarios due to the need for different data models and entries, making product development and maintenance difficult, especially when sending operation requests across devices with varying protocols.

Innovation Solution

A method and system for generating operation requests that include assignment content and location information using an identifier of a packet header, offset, and length, allowing for generic operation requests independent of specific protocols, reducing the complexity of device deployment and supporting multiple protocols efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a device uses different data models and entries for different protocols, then it can support multiple protocols and scenarios, but the device complexity increases and product development becomes difficult

Engineering Contradiction:
Improveprotocol support capabilityVSAvoiddata model complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal data model that can represent multiple protocols and scenarios through a unified structure. The operation request includes generic fields (assignment content, assignment location information with packet header type identifier, offset, and length) that can accommodate different protocols without requiring separate data models for each protocol type.

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

Solution Approach 2:

The patent uses parameter-based differentiation within a unified data model. By varying parameters such as packet header type identifier, offset, and length, the same data model structure can represent different protocols and scenarios, eliminating the need for multiple specialized data models.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If a device needs to send multiple types of operation requests to support different protocols, then it can handle diverse packet processing requirements, but the deployment complexity increases

Engineering Contradiction:
Improveoperation request typesVSAvoiddeployment difficulty
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent designs a universal operation request structure that can function across multiple protocols. The request contains assignment content and assignment location information (packet header type identifier, offset, length) that can be configured to work with different packet types and protocols, allowing a single device deployment to handle diverse scenarios.

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

Solution Approach 2:

The patent introduces an intermediary layer of generic operation requests that mediate between the sending device and receiving device. This intermediary structure abstracts away protocol-specific details, allowing the sending device to use a unified request format regardless of the specific protocol being used by the receiving device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11337211B2Operation request generating method, device, and system
Publication Date: 2022.05.17 HUAWEI TECH CO LTD
  • US11337211B2 patent drawing
  • US11337211B2 patent drawing
  • US11337211B2 patent drawing

AI summary

An operation request generating method, including a generation device generates a first operation request that requests to perform an operation on a first packet, where the first operation request includes first assignment content and information used to indicate a first assignment location, the first assignment location is a location in the first packet, the first assignment content is data used to assign a value to the first assignment location, and the information used to indicate the first assignment location includes an identifier of a type of a first packet header, a first offset, and a first length, where the first packet header is a packet header in the first packet, and the first offset is an offset relative to a start location of the first packet header, and the generation device sends the first operation request to a description device or a receiving device.