SCEF NEF PLMN Location Mapping Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no mechanism specified for automatically provisioning a database of PLMN location mappings in the SCEF or NEF for responding to monitoring request messages from IoT application servers and service capability servers, leading to labor-intensive and error-prone manual provisioning processes.
Innovation Solution
A dynamically provisioned PLMN location mapping database is implemented in the SCEF or NEF, using location mappings obtained from messaging during eNB attachment or reconnection, and updated through existing 3GPP messaging and self-organizing network (SON) interfaces, allowing automatic configuration and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual provisioning of PLMN location mappings is used, then the database can be configured, but the process is labor-intensive and error-prone
Solution Approach 1:
The system automatically provisions PLMN location mappings by having network elements (eNB, MME, HSS) self-report their location information to the SCEF/NEF through existing signaling interfaces. The SCEF/NEF extracts location data from these self-reported messages and populates the mapping database without manual intervention, eliminating labor-intensive provisioning while maintaining system simplicity through reuse of existing protocols
Solution Approach 2:
The system performs preliminary provisioning of PLMN location mappings by pre-establishing the mapping database before monitoring requests arrive. Network elements report their location information in advance during attachment and configuration phases, so that when monitoring requests are received, the mappings are already available, eliminating the need for manual real-time provisioning
2Reliability
If manual provisioning of PLMN location mappings is used, then the database can be configured, but it is error-prone
Solution Approach 1:
Network elements automatically report their own location information to the SCEF/NEF through standardized signaling messages, eliminating manual data entry errors. The self-reported nature of the data ensures accuracy as each network element provides its own verified location parameters (eNB ID, cell ID, geographic coordinates) without human intervention
Solution Approach 2:
The system implements feedback mechanisms where network elements confirm their location information reporting to the SCEF/NEF, and the SCEF/NEF validates received mappings before storing them in the database. This feedback loop ensures data integrity and reliability by verifying that location mappings are correctly formed and consistent with network topology
3Adaptability or versatility
If a PLMN location mapping database is implemented, then monitoring requests can be resolved, but the system requires additional components
Solution Approach 1:
The SCEF/NEF system performs multiple functions: it acts as both the monitoring request receiver and the PLMN location mapping database manager. The same interface that receives monitoring requests also provisions and queries the location mapping database, eliminating the need for separate dedicated components and reducing overall system complexity while maintaining versatility in handling different monitoring scenarios
Solution Approach 2:
The patent combines the PLMN location mapping database functionality within the existing SCEF/NEF architecture rather than implementing it as a separate external system. The database is integrated into the same network element that processes monitoring requests, merging data storage and processing functions into a single unified component, which reduces system complexity while enabling comprehensive monitoring capabilities
4Reliability
If dynamic updates of PLMN location mappings are implemented, then the database remains current, but more messaging is required
Solution Approach 1:
The system establishes continuous location information reporting from network elements to the SCEF/NEF through existing periodic signaling messages. Rather than implementing separate update mechanisms, the system leverages ongoing network operational messages (attachment, configuration updates, mobility events) to continuously refresh location mappings, ensuring currency without additional messaging overhead
Solution Approach 2:
Existing signaling messages between network elements serve dual purposes: they perform their primary network management functions while simultaneously carrying location information for database updates. For example, eNB attachment messages both establish the radio connection and provide location data for the mapping database, eliminating the need for separate update messaging and reducing overall communication overhead
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for dynamically provisioning and using PLMN location mappings includes, in an SCEF or NEF, receiving, from a PLMN network node, a message containing a PLMN location identifier and a non-PLMN location identifier, extracting the PLMN location identifier and the non-PLMN location identifier from the message and storing, in a PLMN location mapping database in the SCEF or NEF, a mapping between the PLMN location identifier and the non-PLMN location identifier. The method further includes receiving, via a monitoring interface of the SCEF or NEF, a monitoring request message requesting IoT device information and including a non-PLMN location identifier. The method further includes locating an entry in the PLMN location mapping database corresponding to the non-PLMN location identifier, extracting a PLMN location identifier from the database, using the PLMN location identifier extracted from the database to obtain IoT device information, and responding to the monitoring request message with the IoT device information.