5G Network Function Validation Using Blockchain Profile Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Network Repository Function (NRF) in 5G Service Based Architecture faces challenges in validating the profiles of Network Functions (NFs) that do not register their profiles, leading to authorization issues, especially for pure Network Function Consumers (NFcs), and insufficient information in Transport Layer Security (TLS) certificates for complete validation.
Innovation Solution
Utilizing a blockchain ledger to store and manage static profile information of NFs, allowing network devices to validate profile information and authorize NFs based on registered data, providing a mechanism to address authorization issues and validate NFs without OAuth tokens.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If Network Functions do not register their profiles with the NRF, then the network can maintain simpler registration processes, but the NRF cannot validate or authorize these NFs properly
Solution Approach 1:
The patent introduces a blockchain ledger as an intermediary system between NFs and the NRF. The blockchain stores profile information of NFs in a decentralized manner, allowing the NRF to access and validate profiles without requiring traditional registration. This mediator resolves the contradiction by enabling NF validation without mandatory registration while maintaining security and reliability.
Solution Approach 2:
The blockchain ledger serves multiple functions: it stores profile information, enables NF validation, provides authorization capabilities, and maintains a decentralized record of NF identities. This multi-functional system allows the network to handle both registered and unregistered NFs uniformly, resolving the contradiction between ease of access and validation reliability.
2Ease of operation
If the NRF uses traditional registration methods to validate NF profiles, then the validation process is straightforward, but pure Network Function Consumers cannot be authorized due to insufficient information
Solution Approach 1:
The blockchain acts as an intermediary that stores comprehensive profile information about NFs, including pure consumers. The NRF can query this decentralized ledger to obtain the necessary information for authorizing pure NF Consumers, enabling the validation and authorization process to work for all NF types without complicating the overall operation.
Solution Approach 2:
The system performs preliminary action by pre-storing profile information of NFs in the blockchain ledger before authorization is needed. This allows the NRF to quickly retrieve and use the required information for validating and authorizing NFs, including pure consumers, without requiring complex real-time validation processes.
3Device complexity
If the network relies on TLS certificates for NF validation, then the validation process is simple, but the information in TLS certificates is insufficient for complete validation
Solution Approach 1:
The patent merges the TLS certificate validation mechanism with a blockchain-based profile storage system. TLS certificates continue to provide basic security and identification, while the blockchain ledger stores additional comprehensive profile information. This combination ensures complete validation information is available while maintaining the simplicity of the overall validation process.
Solution Approach 2:
The blockchain ledger serves as an intermediary that supplements TLS certificate information with additional profile data. This mediator provides the missing information needed for complete NF validation without replacing the TLS mechanism, thus maintaining simplicity while preventing information loss.
Data Source
AI summary
Embodiments of the present disclosure relate to network function validation. The first network device receives, from a second network device, a request including profile information of the second network device to be validated, obtain registered profile information of the second network device from a third network device maintaining a blockchain ledger storing the registered profile information, and validate the profile information of the second network device based on the registered profile information. The validation can be implemented via blockchain, and OAuth is not need, and for pure consumer can be authorized, in addition information for validation is sufficient.


