Terminal Identifier Retrieval via NEF Address Mapping Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The security of obtaining a terminal device identifier via an edge enabler server (EES) is a critical issue that needs to be addressed to enhance the integrity and accuracy of the identification process.
Innovation Solution
The proposed solution involves the edge enabler server receiving a private address from a terminal device, obtaining a public address and port number, and sending this information to a network exposure function network element to verify the accuracy of the private address, thereby ensuring secure identification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the edge enabler server directly obtains the terminal device identifier using the private address provided by the terminal device, then the process is simple and fast, but the security and accuracy of identifier acquisition deteriorates due to potential address spoofing or incorrect information
Solution Approach 1:
The patent introduces a network exposure function network element as an intermediary between the edge enabler server and the terminal device. This intermediary verifies the validity of the private address by querying the network exposure function network element, which maintains a mapping relationship between public addresses and private addresses. This mediator approach ensures security without requiring the edge enabler server to directly trust the terminal device's provided address.
Solution Approach 2:
The patent implements preliminary verification of the private address before using it to obtain the terminal device identifier. The edge enabler server first queries the network exposure function network element to verify whether the private address is valid and corresponds to the correct public address. This preliminary action prevents incorrect or spoofed addresses from being used in subsequent identifier acquisition operations.
2Reliability
If the system adds verification steps to validate the private address, then the security improves, but the time required for identifier acquisition increases
Solution Approach 1:
The verification of the private address is performed as a preliminary action before the main identifier acquisition process. By validating the address mapping relationship in advance through the network exposure function network element, the system ensures that subsequent identifier acquisition operations can proceed with confidence, reducing the need for re-verification or error handling later in the process.
Solution Approach 2:
The patent implements a feedback mechanism where the edge enabler server queries the network exposure function network element to obtain verification information about the private address. The network exposure function network element returns feedback indicating whether the private address is valid and correctly mapped to the public address. This feedback loop enables quick verification without requiring complex verification procedures.
3Ease of operation
If the edge enabler server trusts the private address provided by the terminal device without verification, then the operation is simple, but the system becomes vulnerable to address spoofing attacks
Solution Approach 1:
The patent introduces the network exposure function network element as a trusted intermediary that mediates between the terminal device and the edge enabler server. This intermediary maintains an authoritative mapping relationship between public and private addresses, allowing the system to verify address validity without requiring complex verification logic or directly trusting the terminal device's provided information.
Solution Approach 2:
The system performs preliminary verification of the private address against the network exposure function network element's recorded mapping information before using it for identifier acquisition. This preliminary action prevents address spoofing attacks by ensuring that the private address provided by the terminal device actually corresponds to the correct public address and terminal device.
Data Source
AI summary
A communication method is provided. The method includes: An EES receives, from a terminal device, a first request message for obtaining an identifier of the terminal device, where the first request message includes a private IP address of the terminal device; the EES obtains a public IP address and a port number of the terminal device and sends, to an NEF, a second request message used to request the identifier of the terminal device, where the second request message includes the private IP address, and the public IP address and the port number of the terminal device; and the EES receives a response message from the NEF, where the response message includes the identifier of the terminal device, or the response message indicates that the obtaining fails.