Registration optimization method and device, electronic equipment and computer readable storage medium
By recording and analyzing the registration failure context information, user devices and the network side determine optimization strategies, which solves the inefficiency problem caused by GUTI registration failure. The adoption of SUCI registration improves registration efficiency and avoids resource waste and delays.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-26
- Publication Date
- 2026-04-03
AI Technical Summary
In wireless communication networks, user equipment lacks the ability to analyze failures and optimize intelligently after GUTI registration fails, resulting in low registration efficiency and wasted resources and delayed registration response due to multiple retries.
User equipment and the network side analyze the reasons for registration failure by recording failure context information, and determine optimization strategies based on the reasons, including using SUCI to initiate registration when the context fails, to avoid multiple GUTI retries.
It improved registration efficiency, avoided resource waste and registration response delays, reduced network operation and maintenance pressure, and significantly improved the intelligent optimization capability of the registration process.
Smart Images
Figure CN121793128A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, specifically to a registration optimization method, apparatus, electronic device, and computer-readable storage medium. Background Technology
[0002] In wireless communication networks, User Equipment (UE) needs to complete a network registration process in order to provide users with continuous and stable communication services. During the registration process, the UE prioritizes using a Globally Unique Temporary Identifier (GUTI) to initiate a registration request.
[0003] After GUTI registration fails, a retry mechanism will be triggered, and registration will be retried multiple times. Only after multiple retry failures will the UE fall back to using the Subscription Concealed Identifier (SUCI) to initiate registration. This registration mechanism lacks failure analysis and intelligent optimization capabilities, resulting in low registration efficiency. Summary of the Invention
[0004] This application provides a registration optimization method, apparatus, electronic device, and computer-readable storage medium, which can analyze the reasons for registration failure and optimize the registration process to avoid multiple GUTI registration retries.
[0005] In a first aspect, embodiments of this application provide a registration optimization method applied to a user equipment (UE), the method comprising: When the UE fails to register with the network using the Globally Unique Temporary Identifier (GUTI), the failure context information is recorded. Based on the failure context information, analyze the reasons for the initial registration failure; Based on the reasons for the initial registration failure, determine the initial registration optimization strategy and execute the initial registration optimization strategy; When the initial registration fails due to context invalidation, the initial registration optimization strategy includes: initiating registration with the network side using the subscription encryption identifier SUCI.
[0006] Secondly, embodiments of this application provide a registration optimization method applied to the network side, the method comprising: Obtain the failure context information uploaded by the UE; the failure context information is: information recorded when the UE fails to register with the network side using GUTI; Obtain network operation status data; Based on the failure context information and the network operation status data, the reason for the target registration failure is determined; Based on the reasons for the target registration failure, a target registration optimization strategy is determined and the target registration optimization strategy is sent to the UE; the target registration optimization strategy is used to guide the UE to perform registration optimization. When the target registration fails due to context invalidation, the target registration optimization strategy includes: initiating registration with the network side using SUCI.
[0007] Thirdly, embodiments of this application provide a registration optimization apparatus applied to a UE, the apparatus comprising: The information recording module is used to record failure context information when the UE fails to register with the network side using GUTI; The cause analysis module is used to analyze the cause of the initial registration failure based on the failure context information; The strategy determination module is used to determine an initial registration optimization strategy based on the initial registration failure reason, and to execute the initial registration optimization strategy. When the initial registration failure is due to context invalidation, the initial registration optimization strategy includes: initiating registration with the network side using SUCI.
[0008] Fourthly, embodiments of this application provide a registration optimization device applied on the network side, the device comprising: The information acquisition module is used to acquire the failure context information uploaded by the UE; the failure context information is: the information recorded when the UE fails to register with the network side using GUTI; The data acquisition module is used to acquire network operation status data; The cause determination module is used to determine the cause of the target registration failure based on the failure context information and the network operation status data; The strategy delivery module is used to determine a target registration optimization strategy based on the reason for the target registration failure, and to deliver the target registration optimization strategy to the UE; the target registration optimization strategy is used to overwrite the UE's initial registration optimization strategy for registration optimization; When the target registration fails due to context invalidation, the target registration optimization strategy includes: initiating registration with the network side using SUCI.
[0009] Fifthly, embodiments of this application also provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps in the registration optimization method described above.
[0010] Sixthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the above-described registration optimization method.
[0011] In a seventh aspect, embodiments of this application also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described in embodiments of this application.
[0012] The embodiments of this application have the following beneficial effects: When a user equipment fails to register with the network using GUTI, the initial registration failure reason can be analyzed based on the failure context information. Based on this reason, an initial registration optimization strategy can be determined and executed to achieve failure analysis and intelligent optimization of the registration process, thereby improving registration efficiency. Specifically, when the initial registration failure reason is context invalidation, the corresponding initial registration optimization strategy includes initiating registration with the network using SUCI. This avoids resource waste and registration response delays caused by multiple registration retries based on GUTI, and also prevents further exacerbation of network operation and maintenance pressure, thus significantly improving registration efficiency. Attached Figure Description
[0013] To more clearly illustrate the technical solutions in this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0014] Figure 1 This is a schematic diagram of the steps of a registration optimization method provided in an embodiment of this application; Figure 2 This is a schematic flowchart of a registration optimization method provided in an embodiment of this application; Figure 3 This is a schematic diagram of the steps of a registration optimization method provided in another embodiment of this application; Figure 4 This is a schematic diagram of the registration optimization device provided in one embodiment of this application; Figure 5 This is a schematic diagram of the registration optimization device provided in another embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0015] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.
[0016] For ease of understanding, the following definitions are provided: GUTI is a temporary identifier used in mobile communication networks to identify UEs, in order to avoid privacy leaks caused by directly exposing permanent identifiers (such as subscribing to permanent identifiers), while improving network registration efficiency.
[0017] The Subscription Permanent Identifier (SUPI) is a permanent identity identifier for users in 5G networks. It is used by the network side to uniquely identify a user's subscription information and is stored in the UE's Universal Subscriber Identity Module (USIM) and the user database of the home network. The SUPI is not transmitted directly over the air interface, but is instead generated and sent after encryption to protect user privacy. It is only used in scenarios such as internal network authentication.
[0018] SUCI is an identifier introduced in 5G to enhance user privacy. It is a variant of SUPI and is mainly used to enhance user privacy protection. When GUTI cannot be used, SUCI is used to complete network registration. In a 5G network, when a terminal attempts to register for the first time, it encapsulates SUPI into SUCI and sends an initial registration request message with SUCI, instead of transmitting SUPI over the air interface, to prevent user identity leakage.
[0019] A Public Land Mobile Network (PLMN) is a network provided by mobile communication operators to offer terrestrial mobile communication services. It includes infrastructure such as base stations and core networks. Different operators have their own unique PLMN identifiers to distinguish them from different operators or network environments. PLMNs support functions such as terminal access, mobility management, and session establishment, and are the basic network architecture for users to achieve voice and data communication.
[0020] A failure context is a collection of detailed information about an operation that fails (such as registration failure). It records the context and key parameters at the time of the failure. This information may include the failure type, timestamp, signal environment, PLMN status, and network-side response parameters. In mobile communications, failure context helps the network or user equipment analyze the root causes of failures during registration, handover, and other processes, aiding in troubleshooting and network optimization.
[0021] In one embodiment, such as Figure 1 As shown, a registration optimization method is provided. Although the logical order is illustrated in the step diagram, in some cases, the steps shown or described can be performed in a different order than that shown in the diagram. Specifically, this registration optimization method can be applied to user equipment. User equipment refers to a terminal device held by a user and capable of initiating communication requests. User equipment can establish a connection with the network side (such as a base station or core network) via wireless signals to complete operations such as registration, authentication, and data transmission and reception, thereby obtaining communication services such as voice calls and internet access. It is the direct interface for users to interact with the communication network. User equipment can include, but is not limited to, one or more of smartphones, tablets, laptops, in-vehicle computers, smartwatches, and industrial IoT sensors.
[0022] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the priority of the embodiments.
[0023] according to Figure 1 The registration optimization method shown includes at least steps S110 to S130, which are described in detail below: In step S110, when the UE fails to register with the network side using the globally unique temporary identifier (GUTI), the failure context information is recorded.
[0024] A UE's registration failure using GUTI to the network side means that after the UE initiates a registration request using GUTI to the network side, it does not receive an acceptance response from the network side. When registration fails, the failure context information can be recorded.
[0025] Failure context information may include, but is not limited to, one or more of the following: timestamp, current PLMN identifier, target PLMN identifier, signal quality, local GUTI context state, key validity flag for the authentication process, and retransmission count. Signal quality may include Received Signal Strength Indicator (RSSI) and / or Signal to Interference plus Noise Ratio (SINR). RSSI measures the total power of all signals received by the receiver (including useful signals, interference, and noise); SINR represents the ratio of useful signal power to the sum of interference and noise power, reflecting signal quality.
[0026] The context of the most recent N failures can be recorded in a file or in a table, where N is a positive integer set according to actual needs.
[0027] In step S120, the reason for the initial registration failure is analyzed based on the failure context information.
[0028] In step S130, an initial registration optimization strategy is determined based on the reason for the initial registration failure, and the initial registration optimization strategy is executed.
[0029] The UE can analyze the reason for the initial registration failure based on the failure context information. The reasons for the initial registration failure may include, but are not limited to: context failure, key error, and authentication logic conflict.
[0030] The initial registration optimization strategies corresponding to different initial registration failure reasons can be predetermined. After determining the initial registration failure reason, the corresponding initial registration optimization strategy can be directly obtained and executed to re-register without repeatedly performing GUTI registration, thereby solving the problem of low registration efficiency caused by repeated retries.
[0031] As an example, analyzing the cause of initial registration failure based on failure context information may include: determining the cause of initial registration failure as context failure when the failure context information indicates that the local GUTI is invalid and a Public Land Mobile Network (PLMN) handover occurs within the target time; determining the cause of initial registration failure as key error when the failure context information indicates that the context is valid but the failure code in the authentication signaling indicates that the key is invalid; and determining the cause of initial registration failure as authentication logic conflict when the failure context information indicates that multiple concurrent requests occur within the authentication period but the network does not respond.
[0032] In one embodiment, the target time period refers to the recent period, which can be set according to actual needs. If the local GUTI is invalid and a PLMN handover occurs within the target time period, it indicates GUTI context asynchrony due to cross-PLMN movement. In this case, the initial registration failure can be determined as a context failure. Whether a PLMN handover occurred within the target time period can be determined by checking if the identifiers of multiple PLMNs recorded in the failure context information are consistent. The validity period of the network context corresponding to the GUTI recorded locally by the UE can also be used to determine if the GUTI is invalid; alternatively, if the UE receives a GUTI invalidity reason code returned by the network side when initiating registration using the GUTI, the invalidity of the GUTI can be confirmed.
[0033] For example, a UE was previously assigned a GUTI in operator A's PLMN, and this GUTI was bound to the core network context of operator A. When the UE recently switched to operator B's PLMN, since the core networks of different PLMNs operate independently, the core network of operator B did not store the user context (including subscription information, security parameters, etc.) corresponding to the GUTI used by the UE in operator A. If the UE still uses the original GUTI to initiate registration with operator B, operator B will not be able to recognize the validity of the GUTI, and therefore the registration failure can be determined to be due to context invalidation.
[0034] Context failure is essentially caused by cross-network identifier incompatibility due to PLMN independence. Therefore, when the initial registration failure is due to context failure, the corresponding initial registration optimization strategy can be to require the UE to re-register using a permanent identifier such as SUPI, ensuring the network correctly identifies the UE and authorizes services to establish a new context association. To enhance user privacy, the corresponding initial registration optimization strategy can be to require the UE to re-initiate registration with the network using SUCI. In this way, repeated GUTI registration is unnecessary, improving registration efficiency.
[0035] In one embodiment, when the UE fails to register with the network using GUTI and the context is determined to be valid based on the failure context information, it can be determined whether the authentication signaling includes a failure code (such as KEY_INVALID) indicating that the key is invalid. If the failure code is received, it can be determined that the registration failure is due to the failure of the key synchronization mechanism in the security authentication stage. Therefore, it can be determined that the initial registration failure is due to a key error.
[0036] When a UE initiates registration based on a GUTI, if the network successfully matches the pre-stored user context (including subscription data, authentication vectors, etc.) through the GUTI, it indicates that the identity verification process is normal. At this point, the network generates an expected response value based on the root key and algorithm generated by its home network and sends an authentication challenge message to the UE. The UE uses the root key stored in its USIM card, combined with the same algorithm, to calculate the response value and sends it back to the network. If the response value calculated by the UE does not match the expected response value generated by the network, a key error is detected, and the network determines that authentication has failed, thus returning an authentication signaling message containing a failure code to the UE.
[0037] As an example, when the initial registration fails due to a key error, the corresponding initial registration optimization strategy may include renegotiation of the key. The UE can restore normal access by renegotiation of the key, thereby preventing unauthorized access and ensuring communication security.
[0038] When a UE fails to register due to a key error, it can first attempt to re-initiate registration using SUPI or SUCI, triggering the network side to request a new authentication vector from the Unified Data Management (UDM) module. The network-side UDM generates an authentication challenge containing a random number and an Authentication Token (AUTN) and sends it to the UE. The random number is an input parameter in the authentication process, used by the UE and the network side to independently calculate the key and response value, ensuring the uniqueness of each authentication. The AUTN contains information such as the network identifier and synchronization parameters; the UE verifies its legitimacy upon receipt to confirm the network identity and prevent replay attacks. The UE calculates the response value using the local root key via the USIM card and verifies the AUTN's legitimacy. The UE feeds back the response value to the network. If it matches the network's expected response value, both parties can update the security context based on newly generated derived keys such as the Security Anchor Function Key (K_SEAF) to complete key synchronization. K_SEAF is the anchor key calculated by the authentication server function of the home network. If authentication still fails, the UE can trigger a USIM card information refresh, or the network side can update the user key stored in the UDM to ensure that the keys of both parties are consistent.
[0039] In one embodiment, when the failure context information indicates that multiple concurrent requests occur within the same authentication period but the network fails to respond, the initial registration failure can be determined to be due to an authentication logic conflict. The authentication period in mobile communication is the complete interaction time from when the UE initiates an authentication request to when the network completes the authentication response and establishes or updates the security context with the UE. Within the same authentication period, the network only supports processing a single authentication request from the same UE. Concurrent requests can easily trigger authentication logic conflicts. In authentication logic conflicts, the network does not reject the request due to incorrect authentication parameters (such as key mismatch), but rather because the logic processing mechanism limits its ability to respond, thus leading to initial registration failure.
[0040] Optionally, based on information such as overlapping timestamps of multiple concurrent requests and the absence of any network response signaling recorded in the failure context information, it can be determined that multiple concurrent requests occurred within the same authentication period but the network side did not respond, thereby determining that the initial registration failure was due to an authentication logic conflict. Optionally, it can be determined that the initial registration failure was due to an authentication logic conflict based on a specific failure code returned by the network side.
[0041] When a UE repeatedly sends multiple authentication requests within the same authentication cycle due to abnormal signaling retransmission mechanism (such as not receiving a confirmation message for the initial request from the network side), it will lead to authentication logic conflicts: the network-side authentication module cannot process multiple authentication tasks of the same UE at the same time, cannot determine the priority of the request to be responded to, and may also block all requests due to context resource locking, ultimately resulting in the network side not returning a response to all concurrent requests.
[0042] As an example, when the initial registration fails due to an authentication logic conflict, the corresponding initial registration optimization strategy may include repairing local logic. By repairing local logic, relevant temporary resources can be reset, the locked authentication context can be released, and authentication capabilities can be quickly restored.
[0043] To fix the local logic, the UE needs to stop other concurrent authentication threads, clear the local conflict context, and then re-initiate authentication to ensure that only one authentication request is sent each time.
[0044] Specifically, fixing local logic may include: the UE freezing the current registration process and clearing the local conflict context; sending a security status synchronization request to the network side and receiving security information returned by the network side; and updating its own security status based on the security information.
[0045] When a UE determines that there is an authentication logic conflict, it can freeze the current registration process, stop other concurrent authentication threads, and terminate the sending and retransmission mechanism of redundant authentication requests. At the same time, the UE also needs to clean up the local conflict context, including resetting the temporary session identifier associated with the local GUTI and clearing the conflicting temporary key cache, to avoid residual data interfering with subsequent interactions and to ensure that the local state returns to the initial clean state pending authentication.
[0046] The UE sends a security state synchronization request to the network side. This request may carry the UE's current identifier (such as GUTI) and conflict event markers, informing the network side that conflict authentication resources related to the UE need to be synchronized and cleared. This security state synchronization request can be a newly defined extended information element (IE) or a reused UE context synchronization message. Extended IEs are functional supplements and field extensions to basic information elements in mobile communication protocols, used to transmit more granular and complex control signaling or data between network elements. Based on this security state synchronization request, the network side can release locked resources and, after releasing the locked resources, return the currently valid security information to the UE; the security information may include the latest authentication vector or security context.
[0047] After receiving the security information returned by the network side, the UE can skip the identity and key allocation steps and directly update its own security status based on the security information, including reinitializing the local security algorithm, synchronizing the authentication cycle start time of the network side, and updating the basic parameters required for key derivation.
[0048] By fixing local logic, it can be ensured that both parties can complete the interaction based on a consistent security state in subsequent single authentication requests, thus fixing the conflict issue locally and preparing for re-initiating registration.
[0049] By adopting the technical solution of this application embodiment, failure analysis and intelligent optimization of UE during the registration process can be realized by collecting failure context information and analyzing the reasons for initial registration failure. Multi-dimensional failure context information can provide a basis for analyzing the reasons for initial registration failure, thereby accurately distinguishing different types of initial registration failure reasons, and then determining the initial registration optimization strategy. Based on the initial registration optimization strategy, the number of repeated failures can be greatly reduced, the registration time can be shortened, and the registration efficiency can be improved.
[0050] Figure 2 This is a schematic flowchart of a registration optimization method provided in an embodiment of this application, referred to... Figure 2As shown, the UE may include a UE failure context acquisition and analysis module, a policy determination module, and a registration optimization execution module. The UE failure context acquisition and analysis module collects failure context information and analyzes the reasons for initial registration failure based on this information, thereby determining the initial registration optimization policy. The policy determination module determines whether the policy to be executed is the initial registration optimization policy or the target registration optimization policy. The registration optimization execution module executes the initial registration optimization policy or the target registration optimization policy determined by the policy determination module. After the registration optimization execution module executes the corresponding policy, registration is completed if the network responds.
[0051] By adopting the technical solution of this application embodiment, when a user equipment fails to register with the network side using GUTI, it can analyze the initial registration failure reason based on the failure context information, determine the initial registration optimization strategy based on the initial registration failure reason, and execute the initial registration optimization strategy to realize failure analysis and intelligent optimization of the registration process, thereby improving registration efficiency. Among them, when the initial registration failure reason is context invalidation, the corresponding initial registration optimization strategy includes initiating registration with the network side using SUCI. This can avoid resource waste and registration response delay caused by multiple registration retries based on GUTI, and can avoid further aggravating the network operation and maintenance pressure, thereby significantly improving registration efficiency.
[0052] Based on the above technical solution, as an example, refer to Figure 2 The registration optimization method may further include: reporting failure context information to the network side; receiving the target registration optimization strategy corresponding to the target registration failure reason issued by the network side; the target registration failure reason is determined by the network side based on the failure context information and network operation status data; using the target registration optimization strategy to override the initial registration optimization strategy, and executing the target registration optimization strategy.
[0053] The failure context information can be reported to the network side in the form shown in Table 1. Table 1 contains the failure context information stored in tabular form. The failure timestamp, current PLMN, and signal strength in Table 1 are the failure context information, and the failure type is the initial registration failure reason analyzed based on the failure context information. The initial registration optimization strategy can be determined based on the initial registration failure reason.
[0054] Table 1
[0055] After the UE packages the failure context information, it can send it to the failure context coordination module on the network side through the Non-Access Stratum (NAS) or Radio Resource Control (RRC) extended information elements.
[0056] The network side can acquire network operation status data and, based on failure context information and this data, determine the cause of target registration failure. Network operation status data refers to a collection of various data points collected in real-time or offline by network elements and monitoring systems during network operation. These data reflect operational characteristics such as network resource utilization, service processing capacity, and fault risk. Network operation status data can be used for fault location, performance optimization, and capacity planning to ensure stable and efficient network operation.
[0057] Network operational status data may include, but is not limited to, one or more of the following: internal network counter data, load monitoring data, and historical statistical data. Internal network counter data is event-triggered data recorded in real time by internal network counters. By statistically analyzing the number or frequency of specific events, it reflects the real-time service processing status and anomalies of network elements; for example, the number of RRC connection establishment requests / successful requests and the number of authentication request processing on the base station side. Internal network counter data is a fundamental indicator for determining whether a network element is processing services normally.
[0058] Load monitoring data is real-time monitoring data of the resource occupancy status of network elements, links, and resource pools. It is used to assess the current network load and prevent service degradation caused by resource overload. Load monitoring data may include, but is not limited to: base station radio resource block (PRB) utilization, number of user connections, number of sessions processed by the core network's Access and Mobility Management Function (AMF), server CPU / memory utilization, and transmission link bandwidth utilization. Load monitoring data can be used for real-time early warning of resource bottlenecks and is a key basis for dynamic network resource scheduling.
[0059] Historical statistical data is data aggregated and summarized from network internal counter data and load monitoring data at fixed periods. It is used to reflect the long-term trends, patterns, and potential problems of network operation; for example, the daily average RRC connection failure rate, the peak distribution of base station load in different time periods within a week, and the monthly trend of authentication failures. Historical statistical data can be used to support long-term network planning, performance baseline establishment (such as determining the normal load fluctuation range of a certain area), and root cause tracing of problems (such as finding that a certain fault occurs periodically by comparing historical data).
[0060] By analyzing network internal counter data, load monitoring data, and historical statistics in a coordinated manner, the network's operational status can be comprehensively and accurately determined from three dimensions: real-time events, real-time load, and long-term trends. For example, if real-time counter data detects a sudden increase in the RRC connection failure rate, and real-time load data confirms that it is caused by excessive base station load, and then historical statistics are used to determine whether the base station has a long-term overload problem, optimization plans for temporary scheduling and long-term capacity expansion can be ultimately formulated.
[0061] After determining the cause of the target registration failure, the network side can determine a target registration optimization strategy. This strategy can be predetermined or intelligently determined by a large model based on the cause of the registration failure, failure context information, and network operation status data. The network side can then distribute the target registration optimization strategy to the UE.
[0062] The UE can receive the target registration optimization policy corresponding to the target registration failure reason sent by the network side, and use the target registration optimization policy to override the initial registration optimization policy, and then execute the target registration optimization policy. After receiving the target registration optimization policy sent by the network side, the UE can determine whether the target registration optimization policy and the initial registration optimization policy are consistent. If they are consistent, the UE can continue to execute the initial registration optimization policy; if they are inconsistent, the UE stops executing the initial registration optimization policy and instead executes the target registration optimization policy.
[0063] like Figure 2 As shown, the network side may include a network failure context coordination module, a network global classification and policy generation module, and a policy coverage and distribution module. The network failure context coordination module receives failure context information reported by the UE and collects network operation status data. The network global classification and policy generation module can analyze the reasons for target registration failure based on the failure context information and network operation status data, and formulate target registration optimization strategies. The policy coverage and distribution module can distribute the target registration optimization strategies to the UE.
[0064] By adopting the technical solution of this application embodiment, the network side can analyze the more accurate reasons for target registration failure based on failure context information and network operation status data, and derive a more accurate target registration optimization strategy. As a result, the UE can optimize the registration process and improve registration efficiency by executing a more accurate target registration optimization strategy.
[0065] Based on the above technical solution, as an embodiment, the registration optimization method may further include: reporting failure context information to the network side; receiving a prediction optimization strategy issued by the network side; the prediction optimization strategy is: a registration optimization strategy corresponding to the upcoming registration failure situation predicted by the network side based on the failure context information and network operation status data; and executing the prediction optimization strategy.
[0066] The network side can acquire network operation status data and, through machine learning or preset rules, predict upcoming registration scenarios and the corresponding failure reasons based on failure context information and network operation status data. It then intelligently determines a prediction optimization strategy based on the failure reason. The network side sends the prediction optimization strategy to the UE, and the UE executes the received strategy.
[0067] In this way, registration strategies can be dynamically adjusted in advance, thereby avoiding registration failures, reducing the impact of registration failures on user experience, lowering troubleshooting costs, and improving registration efficiency.
[0068] In one embodiment, such as Figure 3 As shown, a registration optimization method is provided. Although the logical order is illustrated in the step diagram, in some cases, the steps shown or described can be performed in a different order than that shown in the diagram. Specifically, this registration optimization method can be applied to the network side. The network side is the collective term for all network devices, network elements, and supporting systems that support UE access and communication services. The network side includes the radio access network and the core network, and is the provider of communication services, playing a crucial role in connecting the UE to the Internet and ensuring stable communication. These will be described in detail below. It should be noted that the order of description in the following embodiments is not intended to limit the priority of the embodiments.
[0069] according to Figure 3 The registration optimization method shown includes at least steps S310 to S340, which are described in detail below: In step S310, the failure context information uploaded by the UE is obtained. The failure context information is the information recorded when the UE fails to register with the network side using GUTI.
[0070] In step S320, network operating status data is obtained.
[0071] In step S330, the reason for the target registration failure is determined based on the failure context information and network operation status data.
[0072] In step S340, a target registration optimization strategy is determined based on the reason for the target registration failure, and the target registration optimization strategy is sent to the UE. The target registration optimization strategy is used to overwrite the UE's initial registration optimization strategy for registration optimization.
[0073] A UE's registration failure using GUTI to the network side means that after the UE initiates a registration request using GUTI, it does not receive an acceptance response from the network side. When registration fails, the failure context information can be recorded. The UE can package the failure context information and send it to the network side via the Non-Access Stratum or Radio Resource Control Extended Information element.
[0074] The network side can acquire network operation status data and, based on failure context information and network operation status data, determine the reason for target registration failure. Network operation status data refers to a collection of various data reflecting operational characteristics such as network resource utilization, service processing capacity, and fault risk, collected in real-time or offline by network elements and monitoring systems during the operation of the communication network. Network operation status data may include, but is not limited to, one or more of the following: internal network counter data, load monitoring data, and historical statistical data.
[0075] After determining the cause of the target registration failure, the network side can determine a target registration optimization strategy. This optimization strategy can be predetermined or intelligently determined by the network side's large-scale model based on the cause of the registration failure, failure context information, and network operation status data. The network side can then distribute the target registration optimization strategy to the UE. The UE can receive the target registration optimization strategy corresponding to the cause of the registration failure distributed by the network side, override the initial registration optimization strategy with the target registration optimization strategy, and execute the target registration optimization strategy.
[0076] Reasons for target registration failure may include, but are not limited to: context invalidation, key error, and authentication logic conflict. When the target registration failure is due to context invalidation, target registration optimization strategies may include: initiating registration with the network side using SUCI.
[0077] From the network side's perspective, context failure occurs when the UE cannot find the previous context during PLMN handover; key error occurs when the key expires due to synchronization failure or not being updated for a long time; authentication logic conflict occurs when multiple authentication requests conflict repeatedly due to incorrect context presets by the UE or delayed processing by the network side.
[0078] By adopting the technical solution of this application embodiment, the network side can obtain the failure context information uploaded by the UE and obtain network operation status data. Based on the failure context information and network operation status data, the network side can accurately determine the cause of the target registration failure, and then determine the corresponding target registration optimization strategy. The target registration optimization strategy is then sent to the UE to optimize registration based on a more accurate target registration optimization strategy that covers the UE's initial registration optimization strategy. In this way, failure analysis and intelligent optimization of the registration process can be realized, thereby improving registration efficiency. Among them, when the cause of the target registration failure is context failure, the corresponding target registration optimization strategy includes initiating registration with the network side using SUCI. This can avoid the waste of resources and registration response delay caused by the UE making multiple registration retries based on GUTI, and can also avoid further aggravating the network operation and maintenance pressure, thereby significantly improving registration efficiency.
[0079] Based on the above technical solution, as an embodiment, the registration optimization method may further include: storing the latest PLMN information in the failure context information when the target registration failure is due to context invalidation; when the target registration failure is due to key error and the number of errors is less than the target number, the target registration optimization strategy includes: renegotiation of the key; when the target registration failure is due to key error and the number of errors is not less than the target number, the target registration optimization strategy includes: initiating registration with the network side using SUCI; when the target registration failure is due to authentication logic conflict, the target registration optimization strategy includes: repairing local logic.
[0080] When the network side determines that the target registration failure is due to context invalidation, it can issue the corresponding target registration optimization policy with the highest priority. This policy informs the UE to directly trigger SUCI registration without retrying GUTI registration (the decision code can be marked as CODE_SUCI_NOW). Furthermore, the network side can store the latest PLMN information from the failure context information reported by the UE in the buffer with the second-highest priority, thereby avoiding wasting signaling resources.
[0081] If the network determines that the target registration failure is due to a key error, and the number of errors is less than the target number, the network-side target registration optimization strategy can be a key renegotiation (marked with the decision code CODE_TEMPKEY_REAUTH). Upon receiving this target registration optimization strategy, the UE can trigger temporary key renegotiation. The target number of errors can be set according to actual needs.
[0082] If the network determines that the target registration failure is due to a key error, and the number of errors is not less than the target number, then renegotiation of the key may also fail. Therefore, the target registration optimization strategy issued by the network can be to switch to SUCI registration. After receiving this target registration optimization strategy, the UE can trigger registration with the network using SUCI.
[0083] When the network side determines that the target registration failure is due to an authentication logic conflict, the target registration optimization strategy issued by the network side can be to repair local logic (which can be marked with the decision code CODE_LOCAL_FIX). Repairing local logic can avoid consuming additional resources.
[0084] By adopting the technical solution of this application embodiment, the network side can issue different target registration optimization strategies for different reasons for target registration failure, thereby effectively solving the fault, improving the accuracy and efficiency of fault handling, and avoiding resource consumption caused by excessive operation.
[0085] Based on the above technical solution, as an embodiment, the registration optimization method may further include: receiving a security state synchronization request sent by the UE; the security state synchronization request is sent by the UE based on the repair local logic in the target registration optimization strategy; based on the security state synchronization request, maintaining the original security context and retransmitting security information to the UE; and discarding duplicate authentication requests within the conflict window.
[0086] When the target registration optimization strategy issued by the network side is to repair local logic, the UE can freeze the current registration process, stop other concurrent authentication threads, and terminate the sending and retransmission mechanism of redundant authentication requests based on the target registration optimization strategy. At the same time, the UE also needs to clean up the local conflict context, including resetting the temporary session identifier associated with the local GUTI and clearing the conflicting temporary key cache, to avoid residual data interfering with subsequent interactions and to ensure that the local state returns to the initial clean state pending authentication.
[0087] The UE sends a security state synchronization request to the network side. This request may carry the UE's current identifier (such as GUTI) and conflict event flags, informing the network side that conflict authentication resources related to the UE need to be synchronized and cleared. This security state synchronization request may be a newly defined extended information element or a reused UE context synchronization message.
[0088] Based on this security state synchronization request, the network side can maintain the existing security context, release locked resources, discard duplicate authentication requests within the conflict window, and return the currently valid security information to the UE. Maintaining the existing security context may include updating necessary random numbers and sequence numbers to maintain security consistency. The currently valid security information may include necessary fields such as session identifier and K_AMF, without needing to create a new AMF instance.
[0089] After receiving the security information returned by the network side, the UE can skip the identity and key allocation steps and directly update its own security status based on the security information.
[0090] By adopting the technical solution of this application embodiment, by repairing local logic, it can be ensured that the network side and UE can complete the interaction based on a consistent security state in subsequent single authentication requests, thereby partially repairing the conflict problem and preparing for the UE to re-initiate registration.
[0091] Based on the above technical solution, as an embodiment, the registration optimization method may further include: predicting an impending registration failure based on failure context information and network operation status data; determining a registration optimization strategy corresponding to the impending registration failure; and issuing the prediction.
[0092] The network side can acquire network operation status data and, through machine learning or preset rules, predict upcoming registration scenarios and the corresponding failure reasons based on failure context information and network operation status data. It then intelligently determines a prediction optimization strategy based on the failure reason. The network side sends the prediction optimization strategy to the UE, and the UE executes the received strategy.
[0093] In this way, registration strategies can be dynamically adjusted in advance, thereby avoiding registration failures, reducing the impact of registration failures on user experience, lowering troubleshooting costs, and improving registration efficiency.
[0094] To facilitate better implementation of the registration optimization method of this application, this application also provides a registration optimization apparatus based on the above-described registration optimization method. The meanings of the terms used are the same as in the above-described registration optimization method, and specific implementation details can be found in the descriptions of the method embodiments.
[0095] The technical solution adopted in this application has the following advantages: It can improve registration agility: With the help of failure context analysis and mode switching optimization, UE can quickly decide whether to continue using GUTI or switch directly to SUCI, reducing latency in dynamic scenarios; This can reduce system resource consumption: reduce signaling waste caused by multiple retries of GUTI registration. In high-load networks, registration signaling redundancy is reduced by optimizing triggering conditions.
[0096] It can enhance business continuity: especially in high-speed mobile or high-load scenarios, intelligent switching strategies can quickly complete registration and ensure uninterrupted business operations.
[0097] Please see Figure 4 , Figure 4This is a schematic diagram of the registration optimization device provided in the embodiments of this application, wherein the registration optimization device is applied to a UE, and the registration optimization device includes: Information recording module 401 is used to record failure context information when the UE fails to register with the network side using GUTI; The cause analysis module 402 is used to analyze the cause of the initial registration failure based on the failure context information; The strategy determination module 403 is used to determine an initial registration optimization strategy based on the initial registration failure reason, and execute the initial registration optimization strategy. When the initial registration failure is due to context invalidation, the initial registration optimization strategy includes: initiating registration with the network side using SUCI.
[0098] In one embodiment, the cause analysis module 402 includes: The first cause determination unit is used to determine that the cause of the initial registration failure is context failure when the failure context information indicates that the local GUTI is invalid and a Public Land Mobile Network (PLMN) handover occurs within the target time. The second cause determination unit is used to determine that the cause of the initial registration failure is a key error when the failure context information indicates that the context is valid but the failure code in the authentication signaling indicates that the key is invalid. The third cause determination unit is used to determine that the cause of the initial registration failure is an authentication logic conflict when multiple concurrent requests occur within the authentication period represented by the failure context information but the network side does not respond.
[0099] In one embodiment, when the initial registration failure is due to a key error, the initial registration optimization strategy includes: renegotiation of the key; When the initial registration failure is due to an authentication logic conflict, the initial registration optimization strategy includes: repairing local logic.
[0100] In one embodiment, the repair local logic includes: Freeze the current registration process and clear local conflict contexts; Send a security status synchronization request to the network side and receive security information returned by the network side; Based on the security information, update its own security status.
[0101] In one embodiment, the device further includes: The reporting module is used to report the failure context information to the network side; The policy receiving module is used to receive the target registration optimization policy corresponding to the target registration failure reason issued by the network side; the target registration failure reason is determined by the network side based on the failure context information and network operation status data; The target policy execution module is used to override the initial registration optimization policy with the target registration optimization policy and execute the target registration optimization policy.
[0102] By adopting the technical solution of this application embodiment, when a user equipment fails to register with the network side using GUTI, it can analyze the initial registration failure reason based on the failure context information, determine the initial registration optimization strategy based on the initial registration failure reason, and execute the initial registration optimization strategy to realize failure analysis and intelligent optimization of the registration process, thereby improving registration efficiency. Among them, when the initial registration failure reason is context invalidation, the corresponding initial registration optimization strategy includes initiating registration with the network side using SUCI. This can avoid resource waste and registration response delay caused by multiple registration retries based on GUTI, and can avoid further aggravating the network operation and maintenance pressure, thereby significantly improving registration efficiency.
[0103] Please see Figure 5 , Figure 5 This is a schematic diagram of the registration optimization device provided in an embodiment of this application, wherein the registration optimization device is applied on the network side, and the registration optimization device includes: The information acquisition module 501 is used to acquire the failure context information uploaded by the UE; the failure context information is: the information recorded when the UE fails to register with the network side using GUTI; Data acquisition module 502 is used to acquire network operating status data; The cause determination module 503 is used to determine the cause of the target registration failure based on the failure context information and the network operation status data; The strategy delivery module 504 is used to determine a target registration optimization strategy based on the reason for the target registration failure, and to deliver the target registration optimization strategy to the UE; the target registration optimization strategy is used to overwrite the UE's initial registration optimization strategy for registration optimization; When the target registration fails due to context invalidation, the target registration optimization strategy includes: initiating registration with the network side using SUCI.
[0104] In one embodiment, the device further includes: The information storage module is used to store the latest PLMN information in the failure context information when the reason for the target registration failure is context invalidation; When the target registration fails due to a key error and the number of errors is less than the target number, the target registration optimization strategy includes: renegotiation of the key; When the target registration failure is due to a key error and the number of errors is not less than the target number, the target registration optimization strategy includes: initiating registration with the network side using the SUCI; When the target registration failure is due to an authentication logic conflict, the target registration optimization strategy includes: repairing local logic.
[0105] The device further includes: A request receiving module is used to receive a security state synchronization request sent by the UE; the security state synchronization request is sent by the UE based on the repair local logic in the target registration optimization strategy; The maintenance module is used to maintain the original security context and retransmit security information to the UE based on the security state synchronization request. The discard module is used to discard duplicate authentication requests within the conflict window.
[0106] By adopting the technical solution of this application embodiment, the network side can obtain the failure context information uploaded by the UE and obtain network operation status data. Based on the failure context information and network operation status data, the network side can accurately determine the cause of the target registration failure, and then determine the corresponding target registration optimization strategy. The target registration optimization strategy is then sent to the UE to optimize registration based on a more accurate target registration optimization strategy that covers the UE's initial registration optimization strategy. In this way, failure analysis and intelligent optimization of the registration process can be realized, thereby improving registration efficiency. Among them, when the cause of the target registration failure is context failure, the corresponding target registration optimization strategy includes initiating registration with the network side using SUCI. This can avoid the waste of resources and registration response delay caused by the UE making multiple registration retries based on GUTI, and can also avoid further aggravating the network operation and maintenance pressure, thereby significantly improving registration efficiency.
[0107] Specific limitations regarding the registration optimization device can be found in the limitations of the registration optimization method above, and will not be repeated here. Each module in the aforementioned registration optimization device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.
[0108] In addition, this application also provides an electronic device, such as Figure 6 As shown, it illustrates the structural diagram of the electronic device involved in this application, specifically: The electronic device may include components such as a processor 601 with one or more processing cores and a memory 602 with one or more computer-readable storage media. Those skilled in the art will understand that... Figure 6 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein: The processor 601 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines, and performs various functions and processes data by running or executing software programs and / or modules stored in the memory 602, and by calling data stored in the memory 602, thereby providing overall monitoring of the electronic device. Optionally, the processor 601 may include one or more processing cores; preferably, the processor 601 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 601.
[0109] The memory 602 can be used to store software programs and modules. The processor 601 executes various functional applications and data processing by running the software programs and modules stored in the memory 602. The memory 602 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 602 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 602 may also include a memory controller to provide the processor 601 with access to the memory 602.
[0110] In one embodiment, the electronic device further includes a power supply 603 that supplies power to the various components. Preferably, the power supply 603 can be logically connected to the processor 601 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 603 may also include one or more DC or AC power supplies, recharging systems, power equipment debugging circuits, power converters or inverters, power status indicators, and other arbitrary components.
[0111] In one embodiment, the electronic device may further include an input unit 604, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
[0112] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 601 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 602 according to the following instructions, and the processor 601 runs the applications stored in the memory 602, thereby implementing the steps in any of the registration optimization methods provided in the embodiments of this application.
[0113] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.
[0114] In one embodiment, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the methods described in any embodiment of this application.
[0115] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method described in any embodiment of this application.
[0116] In some embodiments, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the methods described in any embodiment of this application.
[0117] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0118] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.
[0119] To this end, this application provides a computer-readable storage medium storing a computer program that can be loaded by a processor to execute the steps in any of the registration optimization methods provided in this application.
[0120] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0121] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0122] Since the instructions stored in the computer-readable storage medium can execute the steps in any of the registration optimization methods provided in this application, the beneficial effects that any of the registration optimization methods provided in this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.
[0123] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.
[0124] The above provides a detailed description of a registration optimization method, apparatus, electronic device, and computer-readable storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, those skilled in the art will recognize that there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.
Claims
1. A registration optimization method, characterized in that, Applied to a user equipment (UE), the method includes: When the UE fails to register with the network using the Globally Unique Temporary Identifier (GUTI), the failure context information is recorded. Based on the failure context information, analyze the reasons for the initial registration failure; Based on the reasons for the initial registration failure, determine the initial registration optimization strategy and execute the initial registration optimization strategy; When the initial registration fails due to context invalidation, the initial registration optimization strategy includes: initiating registration with the network side using the subscription encryption identifier SUCI.
2. The method according to claim 1, characterized in that, The analysis of the initial registration failure reason based on the failure context information includes: When the failure context information indicates that the local GUTI is invalid and a Public Land Mobile Network (PLMN) handover occurs within the target time, the cause of the initial registration failure is determined to be a context failure. When the failure context information indicates that the context is valid but the failure code in the authentication signaling indicates that the key is invalid, the reason for the initial registration failure is determined to be a key error; When multiple concurrent requests occur within the authentication period as indicated by the failure context information but the network side does not respond, the cause of the initial registration failure is determined to be an authentication logic conflict.
3. The method according to claim 1, characterized in that, When the initial registration failure is due to a key error, the initial registration optimization strategy includes: renegotiation of the key; When the initial registration failure is due to an authentication logic conflict, the initial registration optimization strategy includes: repairing local logic.
4. The method according to claim 3, characterized in that, The repair local logic includes: Freeze the current registration process and clear local conflict contexts; Send a security status synchronization request to the network side and receive security information returned by the network side; Based on the security information, update its own security status.
5. The method according to claim 1, characterized in that, The method further includes: The failure context information is reported to the network side; The system receives a target registration optimization strategy corresponding to the target registration failure reason issued by the network side; the target registration failure reason is determined by the network side based on the failure context information and network operation status data. The target registration optimization strategy is used to override the initial registration optimization strategy, and the target registration optimization strategy is executed.
6. A registration optimization method, characterized in that, Applied to the network side, the method includes: Obtain the failure context information uploaded by the UE; the failure context information is: information recorded when the UE fails to register with the network side using GUTI; Obtain network operation status data; Based on the failure context information and the network operation status data, the reason for the target registration failure is determined; Based on the reasons for the target registration failure, a target registration optimization strategy is determined and the target registration optimization strategy is sent to the UE; the target registration optimization strategy is used to overwrite the UE's initial registration optimization strategy for registration optimization. When the target registration fails due to context invalidation, the target registration optimization strategy includes: initiating registration with the network side using SUCI.
7. The method according to claim 6, characterized in that, The method further includes: When the target registration fails due to context invalidation, the latest PLMN information in the failure context information is stored; When the target registration fails due to a key error and the number of errors is less than the target number, the target registration optimization strategy includes: renegotiation of the key; When the target registration failure is due to a key error and the number of errors is not less than the target number, the target registration optimization strategy includes: initiating registration with the network side using the SUCI; When the target registration failure is due to an authentication logic conflict, the target registration optimization strategy includes: repairing local logic.
8. The method according to claim 7, characterized in that, The method further includes: The system receives a security state synchronization request sent by the UE; the security state synchronization request is sent by the UE based on the repair local logic in the target registration optimization strategy. Based on the security state synchronization request, the original security context is maintained, and the security information is retransmitted to the UE; Discard duplicate authentication requests within the conflict window.
9. A registration optimization device, characterized in that, Applied to a UE, the device includes: The information recording module is used to record failure context information when the UE fails to register with the network side using GUTI; The cause analysis module is used to analyze the cause of the initial registration failure based on the failure context information; The strategy determination module is used to determine an initial registration optimization strategy based on the initial registration failure reason, and to execute the initial registration optimization strategy. When the initial registration failure is due to context invalidation, the initial registration optimization strategy includes: initiating registration with the network side using SUCI.
10. A registration optimization device, characterized in that, Applied to the network side, the device includes: The information acquisition module is used to acquire the failure context information uploaded by the UE; the failure context information is: the information recorded when the UE fails to register with the network side using GUTI; The data acquisition module is used to acquire network operation status data; The cause determination module is used to determine the cause of the target registration failure based on the failure context information and the network operation status data; The strategy delivery module is used to determine a target registration optimization strategy based on the reason for the target registration failure, and to deliver the target registration optimization strategy to the UE; the target registration optimization strategy is used to overwrite the UE's initial registration optimization strategy for registration optimization; When the target registration fails due to context invalidation, the target registration optimization strategy includes: initiating registration with the network side using SUCI.
11. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the registration optimization method as described in any one of claims 1 to 8.
12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the registration optimization method as described in any one of claims 1 to 8.