Application Service Layer Batch Request Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Machine-to-machine (M2M) communications often require numerous messages to perform services, leading to inefficiencies in data processing and response handling, particularly when handling batched requests that contain similar operations.

Innovation Solution

The implementation of an application service layer (ASL) that processes batched requests by identifying and specifying operations once for multiple requests, allowing for separate or batched responses, based on request names, attributes, or addresses, to enhance efficiency and reduce message overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If batched requests are processed individually with separate operations specified for each, then processing accuracy is maintained, but message overhead and system complexity increase

Engineering Contradiction:
Improveprocessing accuracyVSAvoidmessage overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple individual requests into a single batched request message. Instead of sending separate messages for each request operation, the system merges multiple operations (e.g., multiple data retrieval requests) into one batched request that contains all operations and their parameters in a structured format, reducing message overhead while maintaining processing accuracy through individual operation handling within the batch

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The batched request mechanism serves multiple functions: it consolidates multiple operations into one message transmission, maintains individual operation integrity for accurate processing, and provides a universal framework that can handle different types of requests (data retrieval, device control, etc.) through a standardized batched format with operation identifiers and parameters

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

2Productivity

If batched requests are processed with operations specified once for multiple requests, then message overhead is reduced, but processing complexity increases

Engineering Contradiction:
Improveoperational efficiencyVSAvoidprocessing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary organization of multiple operations into a structured batched request format before transmission. The batched request includes pre-defined operation identifiers, parameters, and structure that enable the receiving system to efficiently parse and process each operation without requiring complex real-time decision-making, thus reducing processing complexity while maintaining high operational efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The batched request is segmented into distinct operations with unique identifiers and parameters. Each operation within the batch is clearly delimited and structured, allowing the processing system to handle each operation independently while benefiting from the consolidated message transmission, thereby managing processing complexity through systematic segmentation

Inventive Principle:
Principle #1Segmentation

3Reliability

If separate responses are sent to each request in batched requests, then response accuracy is improved, but communication overhead increases

Engineering Contradiction:
Improveresponse accuracyVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system merges multiple individual response messages into a single batched response message that contains results for all operations. Instead of transmitting separate response messages for each operation in the batch, the system consolidates all responses into one structured message with operation-result mappings, reducing communication overhead while maintaining response accuracy through explicit association of results with their corresponding operations

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP2954705B1Methods and apparatuses for restful batch services
Publication Date: 2020.01.01 IOT HOLDINGS INC
  • EP2954705B1 patent drawingFigure 1A
  • EP2954705B1 patent drawingFigure 1B
  • EP2954705B1 patent drawingFigure 1C

AI summary

Apparatuses, computer readable media, and methods are disclosed for supporting services at an application service layer (ASL). The method may include responding to receiving batched requests from an entity by processing the batched requests, and sending a response to the batched requests to the entity. The method may include sending a separate response to each request indicated in the batched request to the entity, or sending a batched response. Two or more batched requests may have the same operation and the operation may be only specified once. The operation may be determined based on a name of the batched requests or an attribute of the batched request. The request may be determined to be a batch request based on a name of the batched request, attributes associated with the batched request, or an address to which the batched request is addressed. The ASL may be a service capability layer.