SCS Network-Initiated Device Detach for MTC Power Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In machine-type communication (MTC) systems, there is a lack of defined procedures for network-initiated detach and attach operations, particularly when events like theft, disallowed locations, or integrity validation failures occur, which can lead to unnecessary activity on control and user planes due to the inability to efficiently manage device connections.
Innovation Solution
A method and apparatus that allow a services capability server (SCS) to request a network-initiated detach of a device and manage attach notifications, using subscription fields stored in a home subscriber server (HSS) to inform the SCS when a device is attached or needs to detach, thereby reducing unnecessary network activity and power consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the MTC device establishes user plane communication to check with the MTC server, then the device can be informed of task status, but power consumption increases and network resources are wasted when there are no tasks to perform
Solution Approach 1:
The network performs preliminary actions by establishing detach procedures before the device actually needs to communicate. The SCS can proactively detach devices that are not needed, and the network can pre-establish the detach command transmission mechanism so that when a device needs to be detached, the procedure is already in place and can be executed immediately without requiring the device to first establish user plane communication.
2Reliability
If the SCS wants to detach a device for events like theft or disallowed locations, then device security is improved, but there is no defined procedure for network-initiated detach operations
Solution Approach 1:
The patent introduces an intermediary mechanism involving the MME (Mobility Management Entity) as a mediator between the SCS (Services Capability Server) and the WTRU (Wireless Transmit/Receive Unit). The MME receives detach commands from the SCS and facilitates the actual detach procedure with the device, providing a structured intermediary layer that defines clear procedures for network-initiated detach operations for security events.
Solution Approach 2:
The patent establishes feedback mechanisms where the SCS receives information about device attach status from the network, and the network receives detach commands from the SCS. This bidirectional feedback loop enables the SCS to make informed decisions about when to detach devices for security reasons and ensures proper procedure implementation for network-initiated detach operations.
3Productivity
If the network allows device attach without checking with the SCS, then device connectivity is maintained, but unnecessary activity on control and user planes occurs when devices should be detached
Solution Approach 1:
The patent implements feedback mechanisms where the SCS is informed when a device attaches to the network. The SCS can then determine whether the device should be detached based on subscription fields and current network conditions. This feedback loop allows the network to maintain connectivity when appropriate while enabling energy-efficient detach decisions when devices should be removed from the network.
Solution Approach 2:
The patent introduces dynamic control over device attach/detach decisions. Instead of static allow-all or block-all policies, the network can dynamically adjust its behavior based on real-time information from the SCS and subscription fields. The network can adaptively allow attach when needed and initiate detach when resources should be conserved, creating a dynamic balance between connectivity and energy efficiency.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
A method and apparatus are described for processing service layer detach commands and attach notifications. A services capability server (SCS) may request a core network to perform a network initiated detach of a device. This procedure may be used when the SCS knows that the device will not be needed for a long time or when the SCS detects some event that may warrant a detach, (e.g., theft, disallowed location, integrity validation failure). The SCS may be asked if the device may be allowed to attach at this time. If the SCS indicates that the attach may be rejected, the device may not be allowed to attach until a later time, thus avoiding additional activity on control and user planes. The SCS may be informed when a device is attached based on various subscription fields stored in a home subscriber server (HSS).