Service Capability Server MTC Connectivity Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating Machine Type Communications (MTC) traffic into conventional wireless telephony networks is challenging due to differences in data type, frequency, and volume, as well as the sheer number of MTC devices, which requires efficient management of device connectivity to optimize network operations.
Innovation Solution
A Service Capability Server manages MTC device connectivity by activating packet data protocol contexts using SMS or MMS messages, allowing MTC devices to establish connections only when necessary, and employing state information from the E-UTRAN network to create an always-connected illusion, enabling seamless communication without constant active PDP contexts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MTC devices maintain constant active packet data protocol contexts for continuous connectivity, then communication reliability is improved, but network operational costs and energy consumption increase
Solution Approach 1:
The patent implements dynamic PDP context management where the network transitions devices between active and inactive states based on actual communication needs. The network determines when to activate or deactivate PDP contexts by monitoring device status and communication requirements, allowing flexible adaptation rather than static constant connectivity.
Solution Approach 2:
The patent employs periodic status queries where the network sends SMS messages to MTC devices at scheduled intervals to check if they are awake and ready for communication. This periodic checking mechanism allows the network to determine whether to establish active PDP contexts without requiring devices to maintain continuous active connections, thereby reducing energy consumption while ensuring availability when needed.
2Loss of energy
If MTC devices use SMS-based status checking to determine connectivity needs, then energy consumption is reduced, but communication response time increases
Solution Approach 1:
The network performs preliminary actions by sending SMS status query messages to devices before actual data communication is needed. This allows the network to advance knowledge of device availability status in advance, enabling better planning and preparation for when actual communication occurs, thus managing the time delay inherent in SMS-based checking.
Solution Approach 2:
The patent implements a feedback mechanism where MTC devices respond to SMS status queries with their current state information (awake/not awake, PDP context status). This feedback loop allows the network to adjust its behavior based on actual device conditions, optimizing the balance between energy saving and communication speed by adapting to real-time device states.
3Manufacturing precision
If the network manages PDP contexts for each MTC device individually, then connectivity control precision is improved, but network management complexity increases
Solution Approach 1:
The patent segments the network management function by introducing a dedicated Service Capability Server that handles PDP context management separately from the core network functions. This segmentation allows specialized, precise control of MTC device connectivity while isolating the complexity of individual device management from the broader network infrastructure, making the system more manageable.
Solution Approach 2:
The Service Capability Server acts as an intermediary between the MTC devices and the core network elements. It receives status queries from the network, determines appropriate PDP context actions, and coordinates with other network functions. This intermediary role simplifies network management complexity by centralizing the decision-making logic and providing a unified interface for managing diverse MTC device connectivity requirements.
Data Source
AI summary
Methods for managing device connectivity of machine type communications devices include receiving a packet data protocol based command addressed to a Machine Type Communication (MTC) device, determining if the MTC device has an active packet data protocol context, in response to determining that the MTC device does not have an active packet data protocol context, activating a packet data protocol context for the MTC device, and forwarding the packet data protocol based command to the MTC device.