Capillary Network Device Identifier for 3GPP Gateway Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Capillary network devices, lacking 3GPP compliant radios, cannot be registered with or recognized by 3GPP networks, making it difficult for MTC servers to identify, address, and trigger these devices for communication and charging purposes.
Innovation Solution
Assigning a capillary network device identifier (CNDID) to devices connected behind 3GPP compliant gateways, allowing MTC servers to recognize and communicate with these devices without requiring direct registration with the 3GPP core network, and using this identifier to facilitate group communication and reduce signaling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If capillary network devices connect to 3GPP networks via gateways using short range wireless technology, then device connectivity and network access are enabled, but device identification and registration with the core network become difficult
Solution Approach 1:
The patent introduces a capillary network device identifier (CNDID) as an intermediary element that bridges the gap between capillary devices and the 3GPP core network. The CNDID is assigned to capillary devices and registered with the core network, enabling the network to identify and communicate with devices that otherwise lack direct 3GPP radio capabilities. This mediator identifier allows the core network to detect and manage capillary devices through the gateway infrastructure.
2Device complexity
If capillary network devices lack 3GPP compliant radios, then device complexity and cost are reduced, but direct registration with the core network is impossible
Solution Approach 1:
The patent extracts the registration and identification functions from the capillary device itself and places them at the gateway level. Instead of requiring each capillary device to have 3GPP radio capabilities for direct registration, the gateway performs the registration on behalf of capillary devices using their CNDIDs. This separation allows simple capillary devices to gain core network access without complex radio hardware.
3Ease of operation
If MTC servers need to trigger capillary network devices behind gateways, then device control and communication are enabled, but signaling overhead and network complexity increase
Solution Approach 1:
The CNDID serves multiple functions simultaneously: it identifies capillary devices to the core network, enables MTC servers to trigger devices, and facilitates charging mechanisms. This universal identifier eliminates the need for separate signaling mechanisms for different operations, reducing overall network complexity while maintaining full device control capabilities.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
A method for use in a wireless transmit/receive unit (WTRU), the method comprising: receiving a first registration message comprising a capillary network device identifier (CNDID) from an application running on a capillary network device; transmitting a second registration message including the CNDID to a core network; establishing a packet data connection, comprising receiving an assigned identifier for the capillary network device, with the core network; receiving a data message from the capillary network device; and transmitting the data message, using the assigned identifier, to the core network.