Grouping Session Data Transmission for MMTC Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Mass Machine Type Communication (MMTC) scenarios, the current networking scheme faces inefficiencies in data transmission due to mismatched data and signaling amounts, limited access and processing capacity, high deployment costs, and increased power consumption in terminal devices, which are exacerbated by the need for each device to establish a bearer for data transmission.
Innovation Solution
The method involves establishing grouping sessions based on feature identifiers, allowing terminal devices to send data directly to network devices via physical random-access channels without establishing a bearer, and then routing this data through network devices to server devices for processing, thereby reducing the need for multiple sessions and enhancing processing capacity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a bearer is established for each terminal device for data transmission, then data transmission reliability is improved, but device complexity and deployment cost increase
Solution Approach 1:
The patent merges multiple bearers into a single common bearer that serves all terminal devices. Instead of establishing separate bearers for each device, the system uses a shared bearer structure where data from multiple terminals is multiplexed and transmitted through a common channel, thereby reducing system complexity while maintaining transmission reliability through proper resource allocation and scheduling mechanisms
Solution Approach 2:
The common bearer is designed with universal functionality to handle data from diverse terminal devices. The bearer can accommodate different data types, priorities, and transmission requirements from multiple terminals simultaneously, making it a multi-functional structure that replaces multiple specialized bearers while simplifying the overall system architecture
2Reliability
If a bearer is established for each terminal device, then data transmission reliability is improved, but power consumption increases
Solution Approach 1:
By merging individual device bearers into a common shared bearer, the patent reduces the overhead and resource requirements for each terminal device. Terminal devices consume less power for bearer management and can transmit data more efficiently through the shared channel, reducing overall power consumption while maintaining reliable data transmission through centralized scheduling and resource allocation
3Reliability
If multiple bearers are established for data transmission, then data transmission reliability is improved, but network deployment cost increases
Solution Approach 1:
The patent merges multiple individual bearers into a single common bearer structure, significantly reducing the number of network elements and configurations required. This consolidation lowers network deployment costs by reducing infrastructure requirements, simplifying network management, and decreasing the complexity of provisioning and maintenance, while maintaining data transmission reliability through proper resource allocation mechanisms
4Reliability
If bearers are established for each terminal device, then data transmission reliability is improved, but bandwidth resources consumed increase
Solution Approach 1:
The patent merges multiple device bearers into a single common bearer that efficiently utilizes bandwidth resources. Through multiplexing techniques and centralized resource scheduling, the system optimizes bandwidth allocation across multiple terminal devices, reducing the total bandwidth consumption compared to having separate dedicated bearers for each device while maintaining reliable data transmission through proper resource management
Data Source
AI summary
A method for data transmission, a network device, a terminal device, and a server device are disclosed. The method may include receiving application data sent by a terminal device; where the application data corresponds to a grouping feature identifier; determining a corresponding first grouping session in the network device according to the grouping feature identifier; and sending the application data to the first grouping session, and sending the application data in the first grouping session to a corresponding second grouping session in the server device, such that the server device processes the application data.