Communication method and device, electronic equipment, computer program product and chip

Abstract

The invention provides a communication method and device, electronic equipment, a computer program product and a chip. The technical problem that the communication registration success rate is low is solved. The communication method comprises the following steps: in response to a first registration failure event, adding a first preset value to a registration attempt counter, and starting a first registration interval timer; in response to a first registration target event, a registration attempt counter is reset, and a first registration interval timer is started. In a normal registration failure scene, the count is increased progressively and the first registration interval timer is started, so that accurate accumulation of the number of registration failures of the terminal UE is ensured. In an abnormal scene, the counter is reset and the first registration interval timer is started, so that a vicious cycle of counting accumulation is broken, and the UE can be ensured to obtain a registration attempt opportunity again by resetting and emptying the historical accumulated count. Therefore, starting of other long timing is avoided, insufficient number of attempts in a weak field environment is improved, long-time reconnection failure after multiple registration failures is avoided, and the success rate of communication registration is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods and apparatus, electronic devices, computer program products, and chips. Background Technology

[0002] In 5G networks, user terminals (UEs) often fail to register in weak signal areas or during cross-system reselection due to RRC release, registration request timeout, or TAU failure. To prevent signaling storms caused by endless retries in poor network environments, a registration attempt count is used to limit the number of retries for initial registration or mobility registration. Summary of the Invention

[0003] To overcome the technical problem of low communication registration success rate in related technologies, this application provides a communication method and apparatus, electronic device, computer program product, and chip.

[0004] According to a first aspect of the embodiments of this application, a communication method is provided, the communication method comprising: in response to a first registration failure event, incrementing a registration attempt counter by a first preset value and starting a first registration interval timer; and in response to a first registration target event, resetting the registration attempt counter and starting the first registration interval timer.

[0005] In some possible implementations, the first registration target event includes: a deregistration request; wherein the deregistration request instructs the terminal to perform reregistration.

[0006] In some possible implementations, the first registration target event includes: a network access anomaly recovery event; wherein, the network access anomaly recovery event includes an event in which the terminal initiates a Tracking Area Update (TAU) request after switching from a first network mode to a second network mode, and switches back to the first network mode after the TAU fails.

[0007] In some possible implementations, the first network mode is New Radio, and the second network mode is Evolved Universal Terrestrial Radio Access.

[0008] In some possible implementations, TAU failure includes at least one of the following: after initiating a TAU request, no Tracking Area Update Received TAU ACCEPT message is received from the network device; or the establishment of a Radio Resource Control (RRC) connection with the second network mode fails.

[0009] In some possible implementations, in response to a first registration failure event, the registration attempt counter is incremented by a first preset value, and a first registration interval timer is started, including: when the registration attempt counter is incremented by the first preset value, in response to the count value of the registration attempt counter being less than a count threshold, starting the first registration interval timer; and when the first registration interval timer times out, re-initiating the registration request.

[0010] In some possible implementations, the first registration failure event includes at least one of the following: the registration request failed; the access connection was abnormally released.

[0011] In some possible implementations, starting a first registration interval timer includes: in the event of resetting the registration attempt counter, in response to a second registration failure event, incrementing the registration attempt counter by a second preset value, and starting the first registration interval timer to perform a retry registration operation.

[0012] In some possible implementations, starting a first registration interval timer to perform a retry registration operation includes starting the first registration interval timer if the count value of the registration attempt counter is less than a third preset value.

[0013] In some possible implementations, the second registration failure event includes at least one of the following: in a communication environment, the registration request fails to be sent; the communication environment is an environment where the received network reference signal power (RSRP) of the terminal is lower than a first threshold; the registration request is successfully sent to the network device, and the network device issues a Radio Resource Control (RRC) Release message.

[0014] In some possible implementations, the retry operation includes initiating a registration request if the timing of the first registration interval timer is greater than a first time threshold.

[0015] In some possible implementations, the method further includes: if the count value of the registration attempt counter is greater than or equal to a third preset value, in response to a third registration failure event, starting a second registration interval timer; wherein the second time threshold corresponding to the second registration interval timer is greater than the first time threshold corresponding to the first registration interval timer.

[0016] In some possible implementations, the method further includes: if the count value of the registration attempt counter is less than a third preset value, in response to a second registration target event, resetting the registration attempt counter and starting a first registration interval timer.

[0017] According to a second aspect of the embodiments of this application, a communication device is provided, the communication device comprising: a communication module and a processor; the processor, coupled to the communication module, is configured to: in response to a first registration failure event, control the communication module to increment a registration attempt counter by a first preset value and start a first registration interval timer; in response to a first registration target event, control the communication module to reset the registration attempt counter and start the first registration interval timer.

[0018] In some possible implementations, the processor is also configured to: when the registration attempt counter increments by a first preset value, start a first registration interval timer in response to the count value of the registration attempt counter being less than a count threshold; and re-initiate a registration request when the first registration interval timer times out.

[0019] In some possible implementations, the processor is also configured to: in the event of resetting the registration attempt counter, in response to a second registration failure event, increment the registration attempt counter by a second preset value, and start a first registration interval timer to perform a retry registration operation.

[0020] In some possible implementations, the processor is also configured to start a first registration interval timer if the count value of the registration attempt counter is less than a third preset value.

[0021] In some possible implementations, the processor is also configured to initiate a registration request if the timing of the first registration interval timer is greater than a first time threshold.

[0022] In some possible implementations, the processor is further configured to: in response to a third registration failure event, start a second registration interval timer if the count value of the registration attempt counter is greater than or equal to a third preset value; wherein the second time threshold corresponding to the second registration interval timer is greater than the first time threshold corresponding to the first registration interval timer.

[0023] In some possible implementations, the processor is also configured to: in response to a second registration target event, reset the registration attempt counter and start a first registration interval timer if the count value of the registration attempt counter is less than a third preset value.

[0024] According to a third aspect of the present application, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the communication method of the first aspect.

[0025] According to a fourth aspect of the embodiments of this application, a computer program product is provided, including computer-executable instructions that, when executed by a processor, implement the communication method of the first aspect.

[0026] According to a fifth aspect of the embodiments of this application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the communication method of the first aspect.

[0027] According to a sixth aspect of the embodiments of this application, a chip is provided, including at least one processor and at least one interface circuit; the processor obtains program instructions through the interface circuit; when the program instructions are executed by the processor, they implement the communication method of the first aspect.

[0028] The technical solutions provided by the embodiments of this application can include the following beneficial effects: By responding to a first registration failure event, the registration attempt counter is incremented by a first preset value and a first registration interval timer is started. In a normal registration failure scenario, the incrementing counter and the start of the first registration interval timer ensure the accurate accumulation of the number of registration failures of the terminal UE, strictly meeting the upper limit requirement of attempts, avoiding statistical deviations in the number of attempts caused by counting chaos. At the same time, the first registration interval timer allows the UE to quickly initiate the next registration attempt, reducing waiting time while reserving a reasonable time window for resetting in abnormal scenarios. By responding to a first registration target event, the registration attempt counter is reset and the first registration interval timer is started. In abnormal scenarios, the counter reset and the start of the first registration interval timer break the vicious cycle of count accumulation. By resetting and clearing the historical accumulated count, it ensures that the UE can regain the opportunity to register. For example, in a weak field environment, this design can ensure that the UE can stably complete the registration process, significantly improving the continuity of 5G services. The reset mechanism allows the UE to start the first registration interval timer even after multiple failures, greatly shortening the service interruption time and enabling rapid retry. More importantly, both technical methods start the same first registration interval timer, ensuring the consistency of the process control logic and avoiding process chaos caused by switching timer types. This avoids starting other long timers, improves the insufficient number of attempts in weak field environments, and prevents prolonged inability to reconnect after multiple registration failures, thereby increasing the success rate of communication registration and ensuring the continuity and stability of network services.

[0029] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0030] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0031] Figure 1 A flowchart illustrating a communication method for some embodiments of this application; Figure 2 An interactive schematic diagram illustrating a communication method for some embodiments of this application; Figure 3 An interactive schematic diagram illustrating a communication method for some embodiments of this application; Figure 4 A flowchart illustrating a communication method for some embodiments of this application; Figure 5 A flowchart illustrating a communication method for some embodiments of this application; Figure 6 A flowchart illustrating a communication method for some embodiments of this application; Figure 7 A flowchart illustrating a communication method for some embodiments of this application; Figure 8 A schematic diagram of the structure of a communication device is shown for some embodiments of this application; Figure 9 A schematic diagram of the structure of an electronic device is shown for some embodiments of this application; Figure 10 This is a schematic diagram of the structure of a chip system shown in some embodiments of this application. Detailed Implementation

[0032] Some embodiments of this application will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. Various changes, modifications, and equivalents of the methods, apparatus, and / or systems described herein will become apparent upon understanding this application. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but can be changed as will become apparent upon understanding this application, except for operations that must be performed in a specific order. Furthermore, for clarity and brevity, descriptions of features known in the art may be omitted.

[0033] The embodiments described in the following examples of this application do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0034] Fifth-generation mobile communication technology (5G) is not only applicable to enhanced mobile broadband (eMBB) scenarios, but also widely used in the Internet of Things (IoT), industrial internet, smart cities, autonomous driving, and other fields. With its core characteristics of low latency, high bandwidth, and massive connectivity, 5G effectively promotes the digital transformation of various industries.

[0035] In these diverse application scenarios, the user equipment (UE), as a key node for perception, interaction, and execution, must first complete registration with the wireless mobile network in order to access and use the communication services provided by 5G. The core purpose of network registration is to establish a secure and reliable identity authentication and session channel, ensuring that the UE can legally and stably conduct voice calls, data transmission, and other service functions within the operator's network.

[0036] In current mobile communication systems, to avoid frequent registration processes (LR) initiated by the UE (User Equipment) to the network, different network standards have defined corresponding registration interval timer mechanisms. Specifically, 2G and 3G standards use timers T3211 (Timer T3211, T3211) and T3311 (Timer T3311, T3311). 4G standards use timers T3511 (Timer T3511, T3511). 5G standards use timers T3511 and T3502 (Timer T3502, T3502). 6G standards are tentatively scheduled to use timers T3611 (Timer T3611, T3611) and T3602 (Timer T3602, T3602). It should be noted that the specific manifestation of LR differs across standards. For example, in 2G / 3G scenarios, it manifests as location update requests, attach requests, and routing area update requests. In 4G scenarios, it manifests as attach requests and tracking area update requests. In 5G scenarios, it's a registration request. In 6G scenarios, it's LR.

[0037] According to industry standards, after the UE fails to register (LR) for the first four times, a short-term registration interval timer T3X11 (Timer T3X11, T3X11) will be started. The specific timer models for each network standard are shown above, and their uniform duration is 10 seconds. When the UE fails to register for the first five times consecutively, a long-term registration interval timer T3X02 (Timer T3X02, T3X02) will be started. The specific timer models for each network standard are the same as above, and their uniform duration is 12 minutes. Only after the above registration interval timer expires can the UE initiate another registration attempt. This mechanism achieves a balance between network load and UE registration needs.

[0038] The start and stop logic of timers is basically the same across different network standards. Taking 5G (New Radio, NR) as an example, the 3rd Generation Partnership Project (3GPP) defines a Registration Attempt Counter (RAC) to precisely control the registration process and the start logic of timers. If the registration process triggered by the UE is not an emergency registration and is not initiated to establish an Emergency Protocol Data Unit (PDU), the RAC will increment accordingly when encountering scenarios such as Access Stratum (AS) access failure or Radio Resource Control (RRC) link release after the registration request is sent. Simultaneously, each time the RAC completes its increment or is set to its maximum value, the UE compares it with the preset maximum value of 5. If the RAC value is less than 5, the T3511 timer (duration 10 seconds) is started. If the RAC value equals 5, then timer T3502 (duration 12 minutes) will be started, and the Tracking Area Identity list (TAI list), the Last Visited Registered Tracking Area Identity (Last Visited Registered TAI), and the List of Equivalent Public Land Mobile Networks (Equivalent PLMNs List) will be deleted simultaneously. Furthermore, during the execution of timer T3502, the UE will disable the N1 interface (N1) capability under the current Public Land Mobile Network (PLMN), thereby causing the UE to camp on the 4G network.

[0039] However, in practical applications, the existing RAC control mechanism under the 5G standard has obvious defects. In certain scenarios, it can cause UEs to be unable to register to the 5G network for a long time and unable to obtain normal 5G services, which seriously affects the user experience.

[0040] For example, when a UE moves to a weak signal or temporarily abnormal environment and attempts to register for mobility, it may encounter multiple AS layer access failures or RRC link release issues, causing the RAC to gradually increase to 4. At this point, the UE's Non-Access Stratum (NAS) successfully sends a Registration Request (RR) to the network. However, because the network has not synchronized information with the UE for a long time, the network sends a Deregistration Request (DR) to the UE with a "Re-registration Required" indication, requiring the UE to re-initiate the initial registration. However, the existing mechanism does not have RAC reset logic for this scenario. If the UE subsequently encounters AS layer access failure or RRC link release again, the RAC will directly increase to 5, triggering the T3502 timer (12 minutes). The UE must wait for this timer to expire before it can attempt to register again, ultimately resulting in a prolonged inability to access the 5G network.

[0041] For example, when a UE attempts to register for 5G mobility in a weak signal or temporary abnormal environment, the RAC increments to 4 after multiple failures. Due to the weak 5G signal, the UE reselects to the 4G network and initiates a Tracking Area Update (TAU), but the TAU process fails. The UE then reselects back to the 5G network and initiates mobility registration again. The existing mechanism does not reset the RAC of the original standard (5G) in scenarios where 4G and 5G interoperability fail and the target standard (4G) registration / update fails. If subsequent 5G registration fails again, the RAC will increment to 5 and trigger the T3502 timer, causing the UE to be unable to retry 5G registration for a long time.

[0042] To address the above issues, this application provides a communication method applied to terminal devices. It is applicable to various registration-related scenarios in communication networks where there is a risk of accumulated registration attempt counts, including but not limited to mobile registration in weak signal environments, subsequent registration after historical registration attempt counts have not been cleared, registration after returning to 5G following a failed mode reselection, and registration processes prone to triggering long time intervals due to multiple registration failures. In normal registration failure scenarios, this application increments the counter and activates the first registration interval timer, ensuring accurate accumulation of the number of failed registration attempts for the terminal UE. In abnormal scenarios, the counter is reset and the first registration interval timer is activated, breaking the vicious cycle of count accumulation. By resetting and clearing the historical accumulated count, it ensures that the UE can regain the opportunity to attempt registration. This avoids activating other long time intervals, improves the insufficient number of attempts in weak signal environments, and prevents prolonged inability to reconnect after multiple registration failures, thereby improving the communication registration success rate.

[0043] In some embodiments, the terminal device may be an electronic device. Electronic devices include, but are not limited to, at least one of the following: mobile phone, wearable device, Internet of Things (IoT) device, car with communication capabilities, smart car, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0044] Figure 1 This is a flowchart illustrating a communication method for some embodiments of this application. For example... Figure 1 As shown, in some embodiments, the communication method includes the following steps: S101, in response to the first registration failure event, increment the registration attempt counter by a first preset value and start the first registration interval timer.

[0045] In some embodiments, the first registration failure event includes at least one of the following: Registration request failure; for example, the UE is in a weak signal environment (such as an underground parking garage or remote mountainous area), where the wireless signal strength is insufficient, causing the registration request message to fail to be sent to the network device (also known as the network side). Another example is severe interference in the transmission channel between the UE and the network, causing the registration request message to be lost during transmission and unable to be received by the network.

[0046] The access connection is abnormally released; for example, the registration request is sent successfully, but the network device issues a Radio Resource Control (RRC) release. Another example is that the UE experiences a temporary hardware failure during the access process, causing the access connection to the network to be interrupted.

[0047] It is understandable that the first registration failure event includes, but is not limited to, the three event types mentioned above.

[0048] In some embodiments, in response to a first registration failure event, a registration attempt counter is maintained. Maintaining the registration attempt counter refers to the logical behavior of the terminal automatically and rule-driven recording, incrementing, or resetting a certain state variable (such as the number of registration attempts) according to specifications. It is understood that maintaining the registration attempt counter includes incrementing the registration attempt counter by a first preset value.

[0049] In some embodiments, when the registration attempt counter is incremented by a first preset value, a first registration interval timer may be started in response to the count value of the registration attempt counter being less than a counting threshold. That is, the first registration interval timer may be started after the registration attempt counter is incremented by the first preset value and the count value of the registration attempt counter is less than the counting threshold.

[0050] like Figure 2As shown, for example, the first preset value is configured to 1 (i.e., the increment of the registration attempt counter each time a registration request fails or a network release is received), the counting threshold is configured to 5 (i.e., the maximum number of allowed registration attempts), and the timer duration corresponding to the first registration interval timer is set to 10 seconds. When the UE is in a weak field (e.g., an underground parking lot), it initiates an Initial Registration request. This request is sent to the base station (gNB) via RRC signaling bearer through the communication interface (e.g., the Uu interface). However, due to poor air interface channel quality, the gNB fails to parse the request. After the T300 timer expires, the UE determines that "registration request transmission failed" and immediately increments the local registration attempt count from 0 to 1. After completing the increment operation of the registration attempt counter, the UE immediately reads the current count value as 1 and compares it with the counting threshold of 5. Since 1 is less than 5, the UE immediately starts the first registration interval timer. After the first registration interval timer expires, the UE triggers the RRC connection reconstruction procedure and re-initiates the Initial Registration request. In this way, by following the orderly process of "first increasing the first preset value, then judging the relationship between the count value and the threshold, and finally starting the timer", the logical error of starting the timer before the registration attempt counter is updated is avoided. At the same time, by fixing the first preset value of 1 and the count threshold of 5, the number of registration attempts in weak field conditions is controlled, which not only complies with the timer triggering specification, but also ensures that the UE can retry multiple times stably in weak field conditions.

[0051] like Figure 2As shown, for example, the first preset value is configured to 1 (i.e., the increment of the registration attempt counter each time a registration request fails or a network release is received), the counting threshold is configured to 5 (i.e., the maximum number of allowed registration attempts), and the timer duration corresponding to the first registration interval timer is set to 10 seconds. The UE initiates an Initial Registration request. In the case of temporary recovery of the air interface signal, this registration request is successfully sent to the gNB via the RRC signaling bearer of the communication interface (Uu interface), and forwarded by the gNB to the AMF of the core network. However, at this time, the AMF cannot complete the registration process due to registration queue overflow, and then sends an RRC Release signaling to the gNB. After the gNB forwards the RRC Release signaling to the UE, the UE parses the received signaling. Since no Registration Accept signaling carrying the 5G-GUTI identifier is detected, it determines that this registration is not completed, and then increases the local registration attempt count from 1 to 2 according to the first preset value "1". After completing the increment operation of the registration attempt counter, the UE immediately reads the current count value as 2 and compares it with the counting threshold 5. Since 2 is less than 5, the UE then restarts the first registration interval timer. After the timer expires, the UE will trigger the RRC connection reconstruction process again and re-initiate the Initial Registration request to retry.

[0052] For example, in a weak field scenario, the UE first initiates an Initial Registration request. At this time, the air interface RSRP is at a low level in the weak field range, and the request is not parsed by the gNB. The UE triggers a determination that the registration request transmission has failed, increments the registration attempt count from 0 to 1, and then starts the first registration interval timer. After the first registration interval timer expires, the UE initiates the request again. At this time, the air interface signal temporarily recovers (channel quality meets the standard), and the request is successfully forwarded to the AMF by the gNB. Since the UE does not receive the Registration Accept carrying 5G-GUTI, the UE increments the registration attempt counter from 1 to 2 and starts the first registration interval timer again. After the first registration interval timer expires again, when the UE initiates a new registration request, the air interface signal falls back due to environmental obstruction (channel quality deteriorates), and the request is not successfully received by the gNB. The UE triggers again to increment the registration attempt counter from 2 to 3 and starts the first registration interval timer. After the first registration interval timer expires, the signal temporarily recovers (channel quality meets standards), and the registration request is successfully sent to the AMF. However, at this time, there are still short-term resource-related anomalies in the core network, and the AMF still issues RRC Release signaling. The UE increments the registration attempt counter from 3 to 4. It is understood that this example only exemplifies the alternation process of two incomplete registration scenarios: "registration request air interface transmission failure" and "registration request successfully sent to the network but released." It does not constitute a limitation on the specific reasons for the alternation, the number of alternations, the signal change pattern, or the core network resource status change mode.

[0053] In some embodiments, when the first registration interval timer is started, the registration attempt counter may be incremented by a first preset value in response to the count value of the registration attempt counter being less than the count threshold. That is, after the first registration interval timer is started, and the count value of the registration attempt counter is less than the count threshold, the registration attempt counter may be incremented by a first preset value.

[0054] In some embodiments, "incrementing the registration attempt counter by a first preset value" and "starting the first registration interval timer" can be performed simultaneously.

[0055] S102, in response to the first registration target event, reset the registration attempt counter and start the first registration interval timer.

[0056] In some embodiments, the first registration target event includes a deregistration request. The deregistration request instructs the terminal to perform a re-registration.

[0057] like Figure 2As illustrated, for example, the UE continuously initiates initial registration retries, i.e., it starts a first registration interval timer and re-initiates the request after the timeout. The UE's registration request is successfully sent to the AMF, but due to a synchronization anomaly in the core network User Data Management (UDM) function, the AMF does not return a Registration Accept signaling to the UE. After the first registration interval timer expires, the AMF sends a Deregistration Request signaling to the gNB through the communication interface (N2 interface), and the value of the "deregistration type" information element (IE) in this signaling is explicitly set to "re-registration". "re-registration" instructs the UE to perform re-registration. This deregistration request is the "first registration target event". In response to this first registration target event, the UE parses the fields of the received deregistration request signaling and resets the registration attempt counter.

[0058] In some embodiments, the UE rewrites the registration attempt count value stored in the non-volatile memory to 0 and updates the status flag to "reset" to complete the reset of the registration attempt counter.

[0059] like Figure 2 As shown, for example, after the registration attempt counter is reset, the UE immediately starts the first registration interval timer.

[0060] To adapt to fast-moving weak field scenarios, in some embodiments, the first registration interval timer can be a 5-second short-time timer.

[0061] In some embodiments, the first registration target event includes a network access anomaly recovery event. This network access anomaly recovery event includes an event where the terminal initiates a Tracking Area Update (TAU) request after switching from a first network mode to a second network mode, and switches back to the first network mode after the TAU fails.

[0062] In some embodiments, the first network mode is New Radio (NR) and the second network mode is Evolved Universal Terrestrial Radio Access (UTC). After the terminal reselects from 5G to 4G, it initiates a Tracking Area Update (TAU) request, and after the TAU update fails, it returns to 5G and prepares to re-initiate the registration request.

[0063] In some embodiments, TAU failure includes at least one of the following: after initiating a TAU request, no Tracking Area Update Received TAU ACCEPT message is received from the network device; or the establishment of a Radio Resource Control (RRC) connection with the second network mode fails.

[0064] like Figure 3As shown, for example, the UE continuously initiates initial registration retries, accumulating a registration attempt count of 4. At this point, the UE detects that the reselection condition of "weak 5G signal, available 4G signal" is met, and triggers an inter-system reselection from 5G to 4G, camping on the 4G cell covered by the eNB, completing the handover from the first network mode to the second network mode. After camping on 4G, the UE initiates a TAU request to the eNB, which carries a status flag of "5G mobile registration incomplete," used to inform the 4G core network MME of the current registration context. Subsequently, the UE continuously measures the network signal, detects that the inter-system reselection condition of 4G to 5G is met, triggers a handover, and returns to the 5G network. Thus, the network access anomaly recovery event of "handover from 5G to 4G, initiation of TAU, TAU failure, and return to 5G" is fully triggered, i.e., the first registration target event is established. In response to this first registration target event, the UE resets the locally maintained registration attempt count from 4 to 0 and updates the status bit to "4GTAU reset complete." At the same time, the first registration interval timer (configured duration 10 seconds) is started.

[0065] For example, after the UE resets the registration attempt counter through a network access anomaly recovery event, and returns to the 5G network, its registration attempt counter is reset to 0. It then initiates a mobile registration request in a weak signal environment. At this time, the air interface signal is at a low level in the weak signal range, and the channel quality is poor, causing the request to be unsuccessfully parsed by the gNB. The UE determines that the registration request transmission has failed, increments the counter from 0 to 1, starts the first registration interval timer, and waits for a timeout before retrying. After the first registration interval timer expires, the UE initiates the mobile registration request again. This time, the air interface signal temporarily recovers, the channel quality meets the requirements, and the request is successfully forwarded to the AMF by the gNB. However, the core network session management function (SMF) still has resource limitations (the load has not dropped below the processing threshold), and the AMF cannot establish a complete session for the UE. Therefore, it sends an RRC Release signaling to the gNB. The UE does not receive a response signaling carrying a registration completion identifier, determines that this registration is incomplete, increments the counter from 1 to 2, and starts the first registration interval timer again to retry. After the first registration interval timer expired, the UE initiated a third mobile registration request. However, the air interface signal fell back due to environmental obstruction, resulting in poor channel quality. The request was not parsed by the gNB, and the UE determined the transmission had failed, incrementing the counter from 2 to 3 and starting the first registration interval timer again. After the first registration interval timer expired, a retry was performed. The air interface signal temporarily recovered again, and the request was successfully sent to the AMF. However, although the core network SMF resource load was alleviated, it still did not fully meet the demand. The AMF continued to issue RRRCRelease signaling, and the UE subsequently incremented the counter from 3 to 4. It is evident that the two scenarios of "registration request air interface transmission failure" and "registration request successfully sent to the network but released due to resource limitations" can continuously alternate.

[0066] Based on this, since the counter has been reset to 0 by 4GTAU, even after multiple alternations, the current counter value of 4 is still less than the preset counting threshold of 5, and the remaining number of attempts can still meet the design goal of "at least 5 times", effectively avoiding the problem of counter exhaustion and inability to retry in traditional solutions.

[0067] It is understood that this example only illustrates the alternation process of two scenarios: "registration request air interface transmission failure" and "registration request successfully sent to the network but released due to resource limitations". It does not constitute a limitation on the specific reasons for the alternation, the number of alternations, the signal change pattern, or the core network resource status change mode.

[0068] In some embodiments, the first registration interval timer in step S101 and the first registration interval timer in step S102 may be the same registration interval timer. In one implementation, the first registration interval timer may be T3511, and the time threshold of the registration interval timer may be 10s.

[0069] In some embodiments, the first registration interval timer in step S101 and the first registration interval timer in step S102 may refer to the same type of registration interval timer, whose timeout period is less than a preset time threshold. The preset time threshold may be 10 seconds.

[0070] like Figure 4 As shown, in some embodiments, starting a first registration interval timer includes the following steps: S201, in the case of resetting the registration attempt counter, in response to the second registration failure event, the registration attempt counter is incremented by a second preset value, and the first registration interval timer is started to perform a retry registration operation.

[0071] In some embodiments, when the registration attempt counter is incremented by a second preset value, a first registration interval timer may be started in response to the count value of the registration attempt counter being less than a count threshold. That is, the first registration interval timer may be started after the registration attempt counter is incremented by the second preset value and the count value of the registration attempt counter is less than the count threshold.

[0072] In some embodiments, when the first registration interval timer is started, the registration attempt counter may be incremented by a second preset value in response to the count value of the registration attempt counter being less than the count threshold. That is, after the first registration interval timer is started, and the count value of the registration attempt counter is less than the count threshold, the registration attempt counter may be incremented by a second preset value.

[0073] In some embodiments, "incrementing the registration attempt counter by a second preset value" and "starting the first registration interval timer" can be performed simultaneously.

[0074] In some embodiments, the second registration failure event includes at least one of the following: In a communication environment, the registration request failed to send. The communication environment is one where the received network reference signal power (RSRP) of the terminal is below a first threshold. For example, a communication environment where the RSRP is less than or equal to the first threshold - 110 dBm is also known as a weak network environment.

[0075] The registration request was successfully sent to the network device, and the network device issued a Radio Resource Control Release (RRCRelease) message.

[0076] In some embodiments, a first registration interval timer is started to perform a retry registration operation, including starting the first registration interval timer when the count value of the registration attempt counter is less than a third preset value.

[0077] like Figure 2 or Figure 3 As shown, for example, a registration retry is initiated based on the condition that "the registration attempt counter is less than the third preset value of 5".

[0078] like Figure 5 As shown, in some embodiments, the retry operation includes the following steps: S301, if the timing period of the first registration interval timer is greater than the first time threshold, initiate a registration request.

[0079] like Figure 2 As shown, for example, after the first registration interval timer expires, the UE initiates a Mobility Registration Update request, and can continue to initiate registration retry based on the condition that "the registration attempt counter is less than the third preset value of 5" in a weak field environment.

[0080] For example, the UE initiates initial registration after the first registration interval timer expires.

[0081] like Figure 6 As shown, in some embodiments, the following steps are also included: S401, if the count value of the registration attempt counter is greater than or equal to the third preset value, in response to the third registration failure event, the second registration interval timer is started.

[0082] The second time threshold corresponding to the second registration interval timer is greater than the first time threshold corresponding to the first registration interval timer.

[0083] In some embodiments, the third registration failure event includes at least one of the following: The registration request failed to send in the communication environment. The communication environment is one where the received network reference signal power (RSRP) of the terminal is below a first threshold.

[0084] The registration request was successfully sent to the network device, and the network device issued a Radio Resource Control Release (RRCRelease) message.

[0085] For example, the third preset value is set to 5 (i.e., triggered when the cumulative number of attempts reaches the maximum allowed 5 after the counter is reset). The first time threshold corresponding to the first registration interval timer is 10 seconds, and the second time threshold corresponding to the second registration interval timer is 12 minutes. It can be seen that the second time threshold is significantly larger than the first time threshold, thereby achieving the design intention of "reducing the retry frequency and alleviating network load". The UE has reset the registration attempt count from 4 to 0 through the first registration target event. After the UE returns to the 5G network, random access fails, the registration attempt count is increased from 0 to 1, and the first registration interval timer of 10 seconds is started. After the first registration interval timer expires, a retry is performed. The air interface signal is temporarily restored, but the AMF sends an RRC Release message due to SMF resource limitations. The UE increases the counter to 2 and starts the 10-second timer again. This alternating process continues in a loop, with the UE repeatedly switching between "registration request transmission failure" and "receiving an RRC Release message." Each registration failure increments the counter by a first preset value of 1 until the registration attempt count accumulates from 0 to 5. At this point, the counter value of 5 reaches and satisfies the precondition of "greater than or equal to the third preset value of 5." After the counter value reaches 5, the UE starts the first registration interval timer and it times out, then initiates the mobile registration request again. At this time, the UE is still in a weak signal environment (e.g., RSRP = -125dBm, below the first threshold), the air interface channel quality has not improved, and the request is not successfully parsed by the gNB. The UE determines that "registration request transmission failed in a weak signal environment," formally triggering the third registration failure event. Even if this request is successfully sent to the AMF, because the SMF resources are still not alleviated, the AMF will issue an RRC Release message, which will also trigger the third registration failure event.

[0086] After the UE triggers the third registration failure event, it detects that the current registration attempt count (5) is greater than the third preset value of 5. It then stops starting the original 10-second first registration interval timer and starts the second registration interval timer, with a corresponding second time threshold of 12 minutes. At this point, the UE enters a "low-frequency retry" mode, no longer frequently initiating registration requests at the original short 10-second intervals. It will only attempt to register again after the 12-minute second registration interval timer expires. It is understandable that after starting the 12-minute timer, the registration attempt counter will be synchronously reset to its initial value of 0. After the 12-minute second registration interval timer expires, the next registration attempt initiated by the UE will start counting again from the reset counter value.

[0087] If the registration attempt counter still exhausts 5 allowed attempts after being reset, it indicates that the current weak network environment and network resource status are unlikely to improve in the short term. By starting a second registration interval timer with a longer duration, the air interface signaling overhead caused by frequent retries on the terminal side can be effectively reduced, avoiding adding extra burden to the already heavily loaded core network (such as SMF). At the same time, the 30-second interval still retains the necessary retry opportunities, without completely terminating the registration process, thus balancing "network load reduction" and "registration success rate". It is understood that this example only provides an illustrative demonstration of the implementation process of step S401 and does not constitute a limitation on the specific value of the third preset value, the specific duration of the second time threshold, or the specific triggering scenario of the third registration failure event.

[0088] like Figure 7 As shown, in some embodiments, the following steps are also included: S501, if the count value of the registration attempt counter is less than the third preset value, in response to the second registration target event, reset the registration attempt counter and start the first registration interval timer.

[0089] In some embodiments, the second registration target event includes a deregistration request. The deregistration request instructs the terminal to perform a re-registration.

[0090] In some embodiments, the second registration target event includes a network access anomaly recovery event. Specifically, the network access anomaly recovery event includes an event where the terminal initiates a Tracking Area Update (TAU) request after switching from a first network mode to a second network mode, and switches back to the first network mode after the TAU fails.

[0091] For example, in the case of the first reset of the registration attempt counter, the UE has already reset the registration attempt count from 4 to 0. When the UE returns to 5G and initiates the first mobile registration request, because the air interface signal difference is not resolved by the gNB, the counter is increased from 0 to 1. At this time, the counter value of 1 is less than the third preset value of 5. Then the UE starts the first registration interval timer. After the first registration interval timer expires, the request is initiated again. The air interface signal is temporarily restored, and the request is successfully sent to the AMF. Due to the UDM database synchronization anomaly (interaction delay timeout between the UDM and AMF on the N8 interface), the user subscription data of the UE cannot be obtained, so the registration process is terminated. After the first registration interval timer expires, the AMF sends a DEEGISTRATION REQUEST signaling to the gNB through the N2 interface, and the "deregistration Type" information element (IE) in the signaling is "re-registration", explicitly instructing the UE to perform re-registration. After receiving the deregistration request, the UE reads the current registration attempt count value as 1, confirming that the "count value is less than the third preset value of 5" is met. The UE verifies that "deregistration Type=re-registration" and is currently in the mobile registration process, and determines that the second registration target event is established. Based on the fact that both conditions are met, the registrationattemptcount is reset from 1 to 0 again, the status flag is updated to "secondary reset complete", and the first registration interval timer is restarted in response to the second registration target event.

[0092] It is understood that this example only provides an illustrative description of the implementation process of step S601 and does not constitute a limitation on the specific value of the third preset value, the specific type of the second registered target event, or the upper limit of the number of secondary resets.

[0093] As can be seen from the above embodiments, this application, in response to the first registration failure event, increments the registration attempt counter by a first preset value and starts the first registration interval timer. In normal registration failure scenarios, the incrementing counter and the start of the first registration interval timer ensure accurate accumulation of the number of registration failures for the terminal UE, strictly adhering to the upper limit requirement for attempts and avoiding statistical deviations in the number of attempts caused by counter chaos. Simultaneously, the first registration interval timer allows the UE to quickly initiate the next registration attempt, reducing waiting time and reserving a reasonable time window for resetting in abnormal scenarios. By resetting the registration attempt counter and starting the first registration interval timer in response to the first registration target event, in abnormal scenarios, the counter reset and the first registration interval timer start break the vicious cycle of counter accumulation. The historical accumulated count can be cleared by resetting, ensuring that the UE can regain the opportunity to register. For example, in weak field environments, this design can ensure that the UE can stably complete the mobile update process, significantly improving 5G service continuity. The reset mechanism allows the UE to start the first registration interval timer even after multiple failures, greatly shortening service interruption time and enabling rapid retry. More importantly, both technical methods start the same first registration interval timer, ensuring the consistency of the process control logic and avoiding process chaos caused by switching timer types. This avoids starting other long timers, improves the insufficient number of attempts in weak field environments, and prevents prolonged inability to reconnect after multiple registration failures, thereby increasing the success rate of communication registration and ensuring the continuity and stability of network services.

[0094] This application also provides a communication device for performing the above-described method.

[0095] Figure 8 This is a schematic diagram illustrating the structure of a communication device according to some embodiments of this application. For example... Figure 8 As shown, in some embodiments, the communication device includes a communication module and a processor.

[0096] The processor, coupled to the communication module, is configured to: in response to a first registration failure event, control the communication module to increment the registration attempt counter by a first preset value and start a first registration interval timer; and in response to a first registration target event, control the communication module to reset the registration attempt counter and start the first registration interval timer.

[0097] In some embodiments, the processor is further configured to: upon incrementing the registration attempt counter by a first preset value, and in response to the registration attempt counter value being less than a counting threshold, start a first registration interval timer; and if the first registration interval timer times out, re-initiate the registration request.

[0098] In some embodiments, the processor is further configured to: in the event of resetting the registration attempt counter, in response to a second registration failure event, increment the registration attempt counter by a second preset value and start a first registration interval timer to perform a retry registration operation.

[0099] In some embodiments, the processor is further configured to: start a first registration interval timer if the count value of the registration attempt counter is less than a third preset value.

[0100] In some embodiments, the processor is further configured to initiate a registration request if the duration of a first registration interval timer exceeds a first time threshold. The registration request includes mobility registration and initial registration.

[0101] In some embodiments, the processor is further configured to: in response to a third registration failure event, start a second registration interval timer if the count value of the registration attempt counter is greater than or equal to a third preset value.

[0102] The second time threshold corresponding to the second registration interval timer is greater than the first time threshold corresponding to the first registration interval timer.

[0103] In some embodiments, the processor is further configured to: in response to a second registration target event, reset the registration attempt counter and start a first registration interval timer if the count value of the registration attempt counter is less than a third preset value.

[0104] Figure 9 This is a schematic diagram illustrating the structure of an electronic device for some embodiments of this application. For example, the electronic device 800 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0105] Reference Figure 9 The electronic device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0106] Processing component 802 typically controls the overall operation of electronic device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0107] Memory 804 is configured to store various types of data to support the operation of electronic device 800. Examples of such data include instructions for any application or method operating on electronic device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0108] Power component 806 provides power to various components of electronic device 800. Power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 800.

[0109] Multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the electronic device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0110] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when electronic device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0111] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0112] Sensor assembly 814 includes one or more sensors for providing state assessments of various aspects of electronic device 800. For example, sensor assembly 814 can detect the on / off state of electronic device 800, the relative positioning of components such as the display and keypad of electronic device 800, changes in position of electronic device 800 or a component of electronic device 800, the presence or absence of user contact with electronic device 800, orientation or acceleration / deceleration of electronic device 800, and temperature changes of electronic device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0113] Communication component 816 is configured to facilitate wired or wireless communication between electronic device 800 and other devices. Electronic device 800 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, other communication standards, or combinations thereof. In some embodiments of this application, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In some embodiments of this application, communication component 816 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0114] In some embodiments of this application, the electronic device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0115] In some embodiments of this application, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of an electronic device 800 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0116] This application also provides a computer program product, including computer-executable instructions, which, when executed by a processor, implement the above-described communication method.

[0117] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the above-described communication method.

[0118] Some embodiments of this application also provide a chip system, such as Figure 10 As shown, the chip system includes at least one processor 1301 and at least one interface circuit 1302. The processor 1301 and the interface circuit 1302 are interconnected via lines. For example, the interface circuit 1302 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 1302 can be used to send signals to other devices (e.g., the processor 1301). Exemplarily, the interface circuit 1302 can read instructions stored in memory and send those instructions to the processor 1301. When the instructions are executed by the processor 1301, the steps in the above embodiments can be performed. Of course, the chip system may also include other discrete devices, and some embodiments of this application do not specifically limit this.

[0119] In some embodiments of this application, the interface circuit 1302 can obtain data, program instructions and / or information from the internal storage area of ​​the chip system; it can also obtain data, program instructions and / or information from outside the chip system.

[0120] Optionally, the chip system also includes a memory 1303 for storing necessary computer programs and data.

[0121] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0122] In the above detailed description, reference has been made to the accompanying drawings, which illustrate specific aspects of how this application can be practiced. In this regard, terms indicating direction or positional relationship, such as “center,” “longitudinal,” “lateral,” “length,” “width,” “thickness,” “upper,” “lower,” “front,” “rear,” “left,” “right,” “vertical,” “horizontal,” “top,” “bottom,” “inner,” “outer,” “clockwise,” “counterclockwise,” “axial,” “radial,” and “circumferential,” can be used with reference to the orientation of the described figures. Since components of the described device can be positioned in multiple different orientations, directional terms are used for illustrative purposes and are not restrictive. It should be understood that other aspects can be utilized and structural or logical changes can be made without departing from the concept of this application. Therefore, the following detailed description should not be considered limiting.

[0123] It should be understood that, unless otherwise specifically indicated, features of various embodiments of this application described herein can be combined with each other. As used herein, the term “and / or” includes any one of the relevant listed items and any combination of any two or more; similarly, “at least one of…” includes any one of the relevant listed items and any combination of any two or more.

[0124] It should be understood that, unless otherwise expressly specified and limited, the terms "joining," "attaching," "installing," "connecting," "linking," and "fixing," as used in the embodiments of this application, should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection, an electrical connection, or a connection that allows communication between them; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise expressly limited. Those skilled in the art can understand the specific meaning of the above terms herein based on the specific circumstances.

[0125] Furthermore, the term "above" as used herein with respect to components, elements, or material layers formed or located "above" a surface may be used to indicate that the component, element, or material layer is "indirectly" positioned (e.g., placed, formed, deposited, etc.) on the surface such that one or more additional components, elements, or layers are arranged between the surface and the component, element, or material layer. However, the term "above" as used with respect to components, elements, or material layers formed or located "above" a surface may also optionally have a specific meaning: that the component, element, or material layer is "directly" positioned (e.g., placed, formed, deposited, etc.) on the surface, for example, in direct contact with the surface.

[0126] Although terms such as “first,” “second,” and “third” may be used herein to describe various components, parts, regions, layers, or sections, these components, parts, regions, layers, or sections are not limited to these terms. Rather, these terms are used only to distinguish one component, part, region, layer, or section from another. Therefore, without departing from the teachings of the examples described herein, the first component, part, region, layer, or section mentioned in the examples may also be referred to as the second component, part, region, layer, or section. Furthermore, the terms “first” and “second” are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as “first” or “second” may explicitly or implicitly include at least one of that feature. In the description herein, “a plurality” means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0127] It should be understood that spatial relative terms, such as “above,” “upper,” “below,” and “lower,” are used herein to describe the relationship between one element and another shown in the figures. In addition to the orientation depicted in the figures, these spatial relative terms are also intended to encompass different orientations of the device in use or operation. For example, if the device in the figures is flipped, an element described as “above” or “upper” relative to another element would be “below” or “lower” relative to that other element. Thus, depending on the spatial orientation of the device, the term “above” encompasses both above and below orientations. Devices may have other orientations (e.g., rotated 90 degrees or in other orientations), and the spatial relative terms used herein should be interpreted accordingly.

[0128] Furthermore, the term “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous compared to other aspects or designs. Rather, the use of the term “exemplary” is intended to present the concept in a concrete manner. As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise specified or clear from the context, “X applies A or B” is intended to mean any of the natural inclusive arrangements. That is, “X applies A or B” satisfies any of the foregoing instances if X applies A; X applies B; or both X applies A and B. Additionally, unless otherwise specified or clear from the context to refer to the singular form, the articles “a” and “an” as used in this application and the appended claims are generally understood to mean “one or more.”

[0129] Similarly, although this application has been shown and described with respect to one or more implementations, equivalent variations and modifications will occur to those skilled in the art upon reading and understanding the specification and drawings. This application includes all such modifications and variations and is limited only by the scope of the claims. In particular, with respect to the various functions performed by the components described above (e.g., elements, resources, etc.), unless otherwise indicated, the terminology used to describe such components is intended to correspond to any component (functionally equivalent) that performs the specific function of the described component, even if structurally not equivalent to the disclosed structure. Furthermore, although a particular feature of this application may have been disclosed with respect to only one of several implementations, such features may be combined with one or more other features of other implementations, as may be desired and advantageous to any given or particular application. Moreover, with regard to the terms “comprising,” “owning,” “having,” “having,” or variations thereof as used in the Detailed Description or the claims, such terms are intended to be inclusive in a manner similar to the term “including.”

[0130] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0131] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A communication method, characterized in that, include: In response to the first registration failure event, the registration attempt counter is incremented by a first preset value, and the first registration interval timer is started; In response to the first registration target event, the registration attempt counter is reset and the first registration interval timer is started.

2. The communication method according to claim 1, characterized in that, The first registered target event includes: Send a registration request; The deregistration request instructs the terminal to perform a re-registration.

3. The communication method according to claim 1, characterized in that, The first registered target event includes: Network access anomaly recovery event; The network access anomaly recovery event includes an event in which the terminal initiates a Tracking Area Update (TAU) request after switching from the first network mode to the second network mode, and switches back to the first network mode after the TAU fails.

4. The communication method according to claim 3, characterized in that, The first network mode is New Radio, and the second network mode is Evolved Universal Terrestrial Radio Access.

5. The communication method according to claim 3, characterized in that, The TAU failure includes at least one of the following: After initiating the TAU request, no TAU ACCEPT message was received from the network device to update the tracking area. The establishment of a Radio Resource Control (RRC) connection with the second network mode failed.

6. The communication method according to any one of claims 1-5, characterized in that, In response to the first registration failure event, incrementing the registration attempt counter by a first preset value and starting the first registration interval timer includes: When the registration attempt counter increases by a first preset value, and the count value of the registration attempt counter is less than the count threshold, the first registration interval timer is started. If the first registration interval timer expires, the registration request will be re-initiated.

7. The communication method according to claim 6, characterized in that, The first registration failure event includes at least one of the following: Registration request failed; The access connection was abnormally released.

8. The communication method according to claim 1, characterized in that, Starting the first registration interval timer includes: In the event of resetting the registration attempt counter, in response to the second registration failure event, the registration attempt counter is incremented by a second preset value, and the first registration interval timer is started to perform a retry registration operation.

9. The communication method according to claim 8, characterized in that, The step of starting the first registration interval timer to perform a retry registration operation includes: If the count value of the registration attempt counter is less than a third preset value, the first registration interval timer is started.

10. The communication method according to claim 8, characterized in that, The second registration failure event includes at least one of the following: In a communication environment, the registration request fails to be sent; the communication environment is an environment where the received network reference signal power (RSRP) of the terminal is lower than a first threshold. The registration request was successfully sent to the network device, and the network device issued a Radio Resource Control Release (RRC) message.

11. The method according to claim 8, characterized in that, The retry operation includes: If the timing period of the first registration interval timer is greater than the first time threshold, a registration request is initiated.

12. The method according to claim 8, characterized in that, Also includes: If the count value of the registration attempt counter is greater than or equal to a third preset value, in response to a third registration failure event, a second registration interval timer is started; Wherein, the second time threshold corresponding to the second registration interval timer is greater than the first time threshold corresponding to the first registration interval timer.

13. The method according to claim 8, characterized in that, Also includes: If the count value of the registration attempt counter is less than a third preset value, in response to the second registration target event, the registration attempt counter is reset and the first registration interval timer is started.

14. A communication device, characterized in that, include: Communication module; The processor, coupled to the communication module, is configured to: in response to a first registration failure event, control the communication module to increment the registration attempt counter by a first preset value and start a first registration interval timer; In response to the first registration target event, the communication module is controlled to reset the registration attempt counter and start the first registration interval timer.

15. The communication device according to claim 14, characterized in that, The processor is also configured to: When the registration attempt counter increases by a first preset value, and the count value of the registration attempt counter is less than the count threshold, the first registration interval timer is started. If the first registration interval timer expires, the registration request will be re-initiated.

16. The communication device according to claim 14, characterized in that, The processor is also configured to: In the event of resetting the registration attempt counter, in response to the second registration failure event, the registration attempt counter is incremented by a second preset value, and the first registration interval timer is started to perform a retry registration operation.

17. The communication device according to claim 16, characterized in that, The processor is also configured to: If the count value of the registration attempt counter is less than a third preset value, the first registration interval timer is started.

18. The communication device according to claim 16, characterized in that, The processor is also configured to: If the timing period of the first registration interval timer is greater than the first time threshold, a registration request is initiated.

19. The communication device according to claim 16, characterized in that, The processor is also configured to: If the count value of the registration attempt counter is greater than or equal to a third preset value, in response to a third registration failure event, a second registration interval timer is started; Wherein, the second time threshold corresponding to the second registration interval timer is greater than the first time threshold corresponding to the first registration interval timer.

20. The communication device according to claim 16, characterized in that, The processor is also configured to: If the count value of the registration attempt counter is less than a third preset value, in response to the second registration target event, the registration attempt counter is reset and the first registration interval timer is started.

21. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the communication method according to any one of claims 1-13.

22. A computer program product, characterized in that, It includes computer-executable instructions that, when executed by a processor, implement the communication method according to any one of claims 1-13.

23. A computer-readable storage medium, characterized in that, The device contains a computer program that, when executed by a processor, implements the communication method according to any one of claims 1-13.

24. A chip, characterized in that, It includes at least one processor and at least one interface circuit; the processor obtains program instructions through the interface circuit; when the program instructions are executed by the processor, they implement the communication method according to any one of claims 1-13.

Images