MSGin5G Authentication Using TLS-PSK Across Mixed UE Types
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods do not provide a unified solution for authentication and authorization between User Equipment (UE) and the MSGin5G server that is compatible with all UE types, including 5GMSGS, legacy 3GPP, and non-3GPP UEs, without reliance on the Service Enabler Architecture Layer for Verticals (SEAL) support.
Innovation Solution
A method and system using Transport Layer Security pre-shared key (TLS-PSK) and token-based mechanisms for authentication and authorization between MSGin5G User Equipment (UE) and the MSGin5G server, with the Authentication Server Function (AUSF) acting as the key management function, enabling compatibility across different UE types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SEAL enabler is used for authentication and authorization in MSGin5G service, then security and compatibility for 5GMSGS UE is improved, but device complexity increases and legacy UEs cannot communicate
Solution Approach 1:
The patent segments the authentication and authorization process into two independent paths: one for 5GMSGS UEs using SEAL enabler and another for legacy UEs using traditional 3GPP mechanisms. This segmentation allows each UE type to use its appropriate authentication method without requiring all UEs to support SEAL, thereby reducing device complexity requirements while maintaining security for supported devices
Solution Approach 2:
The patent creates a universal authentication framework that supports multiple authentication methods (SEAL-based and traditional 3GPP methods) within the same MSGin5G service architecture. This multi-functionality enables the system to accommodate both 5GMSGS UEs with SEAL enabler and legacy UEs without SEAL, ensuring broad compatibility while maintaining security through the appropriate method for each device type
2Adaptability or versatility
If a unified authentication method is implemented for all UE types, then compatibility is improved, but security requirements cannot be met for legacy UEs without SEAL support
Solution Approach 1:
The patent implements a dynamic authentication mechanism where the system automatically selects the appropriate authentication method based on the UE type. 5GMSGS UEs are directed to use the secure SEAL-based authentication path, while legacy UEs use the traditional 3GPP authentication path. This dynamic adaptation ensures both compatibility across different UE types and appropriate security levels for each device category
3Device complexity
If traditional 3GPP authentication is used for all UEs, then device complexity is reduced, but MSGin5G specific security requirements cannot be satisfied
Solution Approach 1:
The patent applies preliminary action by establishing SEAL-based authentication capabilities in advance for 5GMSGS UEs before they access MSGin5G services. This preliminary setup ensures that when these UEs connect to MSGin5G services, they already have the necessary security credentials and mechanisms in place, satisfying MSGin5G-specific security requirements without adding complexity during the actual service access phase
Data Source
AI summary
The present disclosure relates to a pre-5th generation (5G) or 5G communication system to be provided for supporting higher data rates beyond 4th generation (4G) communication system such as long term evolution (LTE). Embodiments herein provide a method of authentication and authorization between a MSGin5G server and a MSGin5G client, the method comprising: receiving, by a MSGin5G interworking function, a pre-shared key request from one of a SEAL server and a MSGin5G Server; deriving, by the MSGin5G interworking function a pre-shared key KMSG-PSK in response to the pre-shared key request; sending, by the MSGin5G interworking function, the pre-shared key KMSG-PSK to one of the SEAL server and the MSGin5G Server; deriving, by a MSGin5G client, the pre-shared key upon receiving either before or after service provisioning procedure; and establishing a TLS session using the pre-shared key KMSG-PSK derived by the MSGin5 interworking function and the MSGin5G client.