Terminal Card Registration Using Stored Network Identity Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a pseudo-card-replacement scenario of dual-card or multi-card terminals, the registration process of new cards requests the network to allocate all identifiers, increasing network burden and registration time.
Innovation Solution
A method and device that detect an inserted identity card, read its identifier, acquire a corresponding network identity from a database, and register the card based on the acquired identity, reducing unnecessary signaling interactions by storing network identities of registered cards.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the terminal adopts the registration process of new cards to request network allocation of all identifiers in pseudo-card-replacement scenarios, then the terminal can ensure proper registration, but the network burden increases and registration time is extended
Solution Approach 1:
The terminal performs preliminary actions by storing card identifier information (IMSI, ICCID) and network identity information (GUTI, TMSI, M-TMSI) locally in a database before actual card replacement occurs. When card replacement is detected, the terminal checks whether the inserted card's identifier exists in the database. If found, it retrieves the corresponding network identity information and uses it directly for registration, avoiding the need to request new identifier allocation from the network. This preliminary storage and reuse of identifier information resolves the contradiction by enabling fast re-registration without network burden while ensuring proper registration through validated identifier pairs.
2Reliability
If the terminal requests network allocation of all identifiers in pseudo-card-replacement scenarios, then the terminal can ensure proper network registration, but the signaling interactions increase
Solution Approach 1:
The patent extracts the identifier allocation function from the network side and implements it locally in the terminal through a database. The terminal stores pairs of card identifiers (IMSI, ICCID) and network identities (GUTI, TMSI, M-TMSI) locally. When a card is inserted, the terminal extracts and checks the card identifier against the database, and if found, directly retrieves the corresponding network identity without involving the network in the identifier allocation process. This extraction of the identifier management function from the network reduces signaling interactions while maintaining registration reliability through local validation.
3Adaptability or versatility
If the terminal deletes stored identifier information when detecting card changes, then the terminal can adapt to new cards, but unnecessary network resource allocation is triggered in pseudo-card-replacement cases
Solution Approach 1:
The terminal performs preliminary action by building and maintaining a local database that stores card identifier information (IMSI, ICCID) and corresponding network identity information (GUTI, TMSI, M-TMSI) before actual card replacement occurs. When card replacement is detected, the terminal checks whether the inserted card's identifier exists in the database. If found, it retrieves the corresponding network identity information and uses it directly for registration, avoiding the need to request new identifier allocation from the network. This preliminary storage and reuse of identifier information resolves the contradiction by enabling fast re-registration without network burden while ensuring proper registration through validated identifier pairs.
Solution Approach 2:
The patent implements a feedback mechanism where the terminal continuously monitors card insertion events, checks the card identifier against the stored database, and adjusts its registration approach based on whether the card is new or previously used. When the card identifier is found in the database, the terminal feeds back that this is a pseudo-card-replacement scenario and uses the stored network identity. When not found, it feeds back that this is a true card replacement and requests new identifier allocation. This feedback loop enables the terminal to adapt to different scenarios appropriately, maintaining card adaptability while avoiding unnecessary network resource allocation.
Data Source
AI summary
A terminal registration processing method and device are provided. The method includes: detecting that an identity card is inserted into at least one card slot; reading an identifier of the identity card; acquiring, from a database, a network identity corresponding to the identifier, wherein the database stores a correspondence between a network identity and an identifier of a registered card; and registering the identity card according to a result of acquiring the network identity.