Underlying Network Entity Cellular Resource Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In machine-to-machine (M2M) communications, there is a lack of defined interface between the common service entity and the underlying network entity, preventing effective communication and data transmission.

Innovation Solution

A data sending method is introduced that provides a common service entity with a communications type supported by the underlying network entity, acquires a service configuration file, allocates cellular network resources, and sends data using these resources, enabling communication between the common service entity and the underlying network entity when the communications type supports a cellular network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If an interface between the common service entity and the underlying network entity is not defined, then the M2M device structure remains simple, but communication between the common service entity and the underlying network entity cannot be achieved

Engineering Contradiction:
Improvecommunication capabilityVSAvoidinterface definition complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a service configuration file as an intermediary element that mediates between the common service entity and the underlying network entity. This file contains communication parameters and configuration information, enabling indirect communication without requiring a directly defined interface between the two entities. The service configuration file acts as a bridge that translates and transmits necessary communication information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by pre-defining communication parameters and configuration information in the service configuration file before actual communication occurs. The underlying network entity acquires this configuration file in advance, allowing it to prepare communication resources and settings beforehand, thus enabling reliable communication without requiring complex real-time interface negotiations.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If a service configuration file is acquired and used to allocate cellular network resources, then data transmission efficiency is improved, but the complexity of resource management increases

Engineering Contradiction:
Improvedata transmission efficiencyVSAvoidresource management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The service configuration file contains pre-defined communication parameters and resource allocation information. The underlying network entity acquires this configuration in advance and uses it to allocate cellular network resources before actual data transmission. This preliminary preparation enables efficient resource utilization without requiring complex real-time resource management decisions during data transmission.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The common service entity autonomously manages its own communication configuration by maintaining and updating the service configuration file. The underlying network entity independently acquires and processes this configuration file for resource allocation. This self-service mechanism reduces the need for complex centralized resource management, allowing each entity to manage its own communication resources efficiently.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10129724B2Data sending method, common service entity, and underlying network entity
Publication Date: 2018.11.13 HUAWEI TECH CO LTD
  • US10129724B2 patent drawing
  • US10129724B2 patent drawing
  • US10129724B2 patent drawing

AI summary

A method in the machine-to-machine communications (M2M) field includes providing, by an underlying network entity, a common service entity with a communications type supported by the underlying network entity; acquiring, by the underlying network entity, a service configuration file of the common service entity when the communications type supports a cellular network; receiving, by the underlying network entity, data that needs to be sent by the common service entity; and carrying and sending, by the underlying network entity, the data by using a cellular network communication resource that is allocated according to a service configuration file.