IMS Security Protocol Selection Using Slice ID Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless communication networks inefficiently select security protocols for registering wireless user devices with the Internet Protocol Multimedia Subsystem (IMS) and fail to effectively associate different security protocols with different classes of user devices.
Innovation Solution
Implementing slice-based security protocol selection by generating an authorization request with an Address Value Pair (AVP) to request a slice Identifier (ID) for the user device, receiving an authorization response with the slice ID, and selecting a security protocol like IPsec or SRTP based on the slice ID to establish a secure communication channel.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional security protocol selection is used for IMS registration, then the registration process can be completed, but the security protocol selection is inefficient and does not effectively associate different security protocols with different classes of user devices
Solution Approach 1:
The patent segments user devices into different classes based on slice identifiers (e.g., slice ID 1 for IoT devices, slice ID 2 for mobile devices). Each slice class is associated with specific security protocols, allowing differentiated security handling. The CSCF segments the authentication process by retrieving slice-specific security protocol information from the UDM based on the user's slice identifier.
Solution Approach 2:
The patent changes the parameter of security protocol selection from a generic one-size-fits-all approach to a dynamic parameter-based approach where the security protocol is selected based on the slice identifier parameter. The system retrieves and applies different security protocols (e.g., IPsec, SRTP, or no security) depending on the slice class, making the security parameter adaptive to device type.
2Adaptability or versatility
If slice-based security protocol selection is implemented, then different security protocols can be associated with different user device classes, but the registration process complexity increases
Solution Approach 1:
The system implements self-service by automatically retrieving slice identifier information from the UDM and autonomously selecting the appropriate security protocol without manual configuration. The CSCF automatically queries the UDM for slice-specific security information and applies the correct protocol, eliminating the need for manual security protocol configuration for each device class.
Solution Approach 2:
The UDM acts as an intermediary between the CSCF and the security protocol selection process. The UDM stores and provides slice-specific security protocol information to the CSCF, which then uses this information to select the appropriate security protocol. This intermediary approach centralizes security policy management and simplifies the overall system architecture.
Data Source
AI summary
Various embodiments comprise a wireless communication network to perform slice-based security protocol selection for Internet Protocol Multimedia Subsystem (IMS). In some examples, the wireless communication network comprises a Call Session Control Function (CSCF). The CSCF receives an IMS registration request transferred by a wireless user device, generates an authorization request that includes an Address Value Pair (AVP) requesting a slice Identifier (ID) for the wireless user device, and transfers the authorization request to a network data system. The CSCF receives an authorization response from the network data system that includes the slice ID for the wireless user device. The CSCF selects a security protocol for authenticating the wireless user device based on the slice ID. The CSCF transfers an authentication challenge for delivery to the wireless user device and establishes a secure communication channel with the wireless user device using the selected security protocol.