Communication method, terminal equipment and readable storage medium

Abstract

The invention relates to the technical field of computers, in particular to a communication method, terminal equipment and a readable storage medium. The method comprises the following steps: when the total number of times that the terminal equipment fails to access network connection in a current cell reaches a first number of times threshold value, the terminal equipment can start a retry timer; and when the total number of times of continuous network connection failure of the terminal equipment in the current cell reaches a second number of times threshold value, acquiring the reference signal receiving power (RSRP) of the current cell, and adding a penalty value to the RSRP of the current cell so as to further reduce the wireless signal strength of the current cell. And the terminal equipment can trigger searching and preferably select other cells with larger RSRP for network connection. Therefore, the terminal equipment can quickly access the network again in the cell with better wireless signals, the time for the terminal equipment to access the network is saved, and the network access efficiency of the terminal equipment is improved.

Description

Technical Field

[0001] This application relates to the field of computer technologies, and in particular, to a communication method, a terminal device, and a readable storage medium. Background Art

[0002] In a mobile communication system, a user equipment (UE) can access the network through an attach (ATTACH) or a tracking area update (TAU). During the process of ATTACH or TAU when the UE is located in the network coverage area, a radio resource control (RRC) connection needs to be established to ensure that the UE can access the network normally and perform mobile services. However, due to underlying reasons, RRC connection release before ATTACH or TAU is successful, timeout of timers such as T3410, attach reject (ATTACH REJECT), and other various reasons will cause the UE to continuously initiate ATTACH or TAU failures, that is, the UE continuously fails to access the network. For example, the underlying reason is poor network signal.

[0003] According to the provisions of the TS24.301 protocol: when the number of consecutive network access failures of the UE is less than 5 times, the T3411 timer will be started, and the timeout duration is 10 s. During this period, the UE cannot initiate ATTACH or TAU again; when the number of consecutive network access failures of the UE is greater than 5 times, the T3402 timer will be started, and the timeout duration is 12 min, and during this period, the UE cannot initiate ATTACH or TAU again. Both T3411 and T3402 are a kind of retry timer. Only when the timer T3411 or T3402 times out can the UE initiate ATTACH or TAU again to access the network.

[0004] Based on the above, regardless of the reason for the continuous network access failure of the UE currently, the UE needs to wait for the timers T3411 and T3402 to time out before it can initiate ATTACH or TAU again to access the network, which affects the network access efficiency of the UE. Summary of the Invention

[0005] To solve the above problems, this application provides a communication method, a terminal device, and a readable storage medium.

[0006] In a first aspect, the present application provides a communication method for a terminal device. The method includes: detecting that the number of failures of the terminal device to establish a network connection in a first cell is greater than a first number threshold, where the terminal device currently has a first reference signal receiving power; reducing the first reference signal receiving power of the terminal device to a second reference signal receiving power, and the second reference signal receiving power satisfies the first cell handover condition; establishing a network connection through a second cell, where a third reference signal receiving power of the second cell is greater than the second reference signal receiving power.

[0007] It can be understood that the terminal device may refer to the mobile phone 100 mentioned in the embodiments of the present application, the first number threshold may refer to N, N1, N2, N3, N4 mentioned in the embodiments of the present application, and the number of failures of the terminal device to establish a network connection in the first cell may refer to the number of consecutive failures of the mobile phone 100 to initiate an ATTACH or TAU request in the current cell in the embodiments of the present application; the first reference signal receiving power may refer to the obtained RSRP1 of the current cell mentioned in the embodiments of the present application, for example, -117 dBm, the second reference signal receiving power may refer to -122 dBm mentioned in the embodiments of the present application, and the third reference signal receiving power may refer to -80 dBm mentioned in the embodiments of the present application.

[0008] It can be understood that in the fourth-generation mobile communication network or the fifth-generation mobile communication network, the standard range of the RSRP signal strength is from -140 dBm to -44 dBm. The larger the RSRP, the stronger the signal strength, and the smaller the RSRP, the weaker the signal strength. The first reference signal receiving power of the first cell can be any value within the range of -140 dBm to -44 dBm, which is not limited herein.

[0009] Through the above solution, regardless of the reason for the continuous failure of the terminal device to initiate an ATTACH request or a TAU request, that is, the access network fails, the terminal device can quickly initiate an ATTACH request or a TAU request in a cell with better wireless signals and achieve quick access to the network. That is, the communication solution provided by the present application does not need to wait for the timer T3411 or T3402 to time out before initiating an ATTACH request or a TAU request, which is beneficial to saving the time for the terminal device to access the network and improving the network access efficiency of the terminal device.

[0010] In a possible implementation of the above first aspect, the first cell handover condition includes: there is at least one cell whose reference signal receiving power is greater than the second reference signal receiving power, and the at least one cell does not include the first cell.

[0011] Based on the above solution, by reducing the reference signal receiving power of the current cell, the terminal device can preferably select a neighboring cell with a higher reference signal receiving power. Furthermore, the terminal device can quickly re-initiate an ATTACH request or a TAU request in a cell with a higher reference signal receiving power, that is, a cell with better wireless signals, so as to quickly access the network.

[0012] In a possible implementation of the first aspect above, the method further includes: corresponding to detecting that the number of failures of the terminal device to connect to the network in the first cell is less than a second number threshold, starting a first retry timer, where the second number threshold is less than the first number threshold; corresponding to detecting that the number of failures of the terminal device to connect to the network in the first cell is greater than the second number threshold and less than the first number threshold, starting a second retry timer, where the timeout duration of the second retry timer is greater than the timeout duration of the first retry timer.

[0013] It can be understood that the second number threshold can refer to the short-term retry number threshold mentioned in the embodiments of the present application, including: the first short-term retry number threshold, the second short-term retry number threshold, and the fourth short-term retry number threshold. The first retry timer can refer to the first short-term retry timer, the second short-term retry timer, and the fourth short-term retry timer mentioned in the embodiments of the present application; the second retry timer can refer to the first long-term retry timer, the second long-term retry timer, and the fourth long-term and short-term retry timer mentioned in the embodiments of the present application.

[0014] It can be understood that in some other embodiments, when it is detected that the number of failures of the terminal device to connect to the network in the first cell is less than the first number threshold, the retry timer may not be started either, but instead, an ATTACH or TAU request may be directly re-initiated in the current cell to establish a network connection, which is not limited herein.

[0015] Based on the above solution, the timeout duration of the retry timer started after a failure in the current cell can be custom-set based on different numbers of failures, so as to save the time for the terminal device to re-initiate an ATTACH or TAU request in the current cell, and further improve the network access efficiency of the terminal device.

[0016] In a possible implementation of the first aspect above, it further includes: corresponding to the second reference signal receiving power not meeting the first cell handover condition, obtaining the reason for the failure of the terminal device to connect to the network in the first cell; determining a communication strategy based on the number of failures of the terminal device to connect to the network in the first cell.

[0017] In a possible implementation of the above first aspect, a communication strategy is determined based on the reason for the failure of the terminal device to connect to the network in the first cell, including: detecting that the number of failures of the terminal device to connect to the network in the first cell is less than a third number threshold and greater than a first number threshold, and starting a third retry timer; wherein, the timeout duration of the third retry timer is greater than the timeout duration of the second retry timer.

[0018] It can be understood that the third number threshold may refer to N5 mentioned in the embodiments of the present application, and the third retry timer may refer to the fifth retry timer mentioned in the embodiments of the present application.

[0019] Through the above solution, for the scenario where the terminal device fails to access the network due to multiple reasons, a relatively large failure number threshold and a relatively long timeout duration of the retry timer can be uniformly set, rather than setting different retry timers separately, which can effectively reduce the power consumption generated by the terminal device's excessive re-attempts to access the network.

[0020] In a possible implementation of the above first aspect, a communication strategy is determined based on the reason for the failure of the terminal device to connect to the network in the first cell, further including: detecting that the number of failures of the terminal device to connect to the network in the first cell is greater than the third number threshold, the terminal device stops connecting to the network based on the current first public land mobile network or the first network mode, and the terminal device connects to the network through at least one of the following: connecting to the network through the second public land mobile network or the second network mode of the first cell; connecting to the network through the second network mode of the first cell; connecting to the network through the third cell.

[0021] In a possible implementation of the above first aspect, the failure of the network connection includes the failure of sending an attachment request or the failure of initiating a tracking area update request; the reason for the failure of the terminal device to connect to the network can be at least one of the following reasons: underlying reasons, where the underlying reasons include poor radio signals of the cell, timeout of timer T300; during the process of the terminal device connecting to the network, the terminal device detects the release of the radio resource control connection, wherein the radio resource control connection is the connection between the terminal device and the base station; timeout of timer T3410 or timeout of timer T3430; the attachment request initiated by the terminal device is rejected or the tracking area update request is rejected.

[0022] Based on the above solution, regardless of whether the terminal device continuously initiates an ATTACH request or a TAU request and fails due to one or more of the above reasons, that is, fails to access the network, the terminal device can quickly re-initiate an ATTACH request or a TAU request in a cell with better wireless signal and achieve quick access to the network. That is, the communication solution provided by this application does not need to wait for the timer T3411 or T3402 to time out before initiating an ATTACH request or a TAU request, which is beneficial to saving the time for the terminal device to access the network and improving the network access efficiency of the terminal device.

[0023] In a second aspect, an embodiment of the present application provides a terminal device, including a memory. The memory includes physical memory and external memory, and is used to store instructions executed by one or more processors of the terminal device; and a processor, configured to execute the instructions to enable the terminal device to implement the communication method provided in the first aspect and various possible implementations of the first aspect.

[0024] In a third aspect, an embodiment of the present application provides a readable storage medium, on which instructions are stored. When the instructions are executed on a terminal device, the communication method provided in the first aspect and various possible implementations of the first aspect is implemented.

[0025] In a fourth aspect, an embodiment of the present application further provides a computer program product, including a computer program / instructions. When the computer program / instructions run on a terminal device, the terminal device is enabled to implement the communication method provided in the first aspect and various possible implementations of the first aspect.

[0026] For the beneficial effects of the second to fourth aspects above, reference may be made to the relevant descriptions in the first aspect and various possible implementations of the first aspect, which will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 According to some embodiments provided by the present application, a schematic diagram of a scenario where a mobile phone 100 accesses the network is shown;

[0028] Figure 2 According to some embodiments provided by the present application, a schematic diagram of a radio access protocol architecture is shown;

[0029] Figure 3 According to some embodiments provided by the present application, a schematic diagram of an implementation process of a communication method in a scenario where a UE initiates an ATTACH request or a TAU request and fails is shown;

[0030] Figure 4 According to some embodiments provided by the present application, a schematic diagram of an implementation process of a communication method in a scenario where the mobile phone 100 continuously initiates an ATTACH request or a TAU request and fails due to underlying reasons is shown;

[0031] Figure 5 According to some embodiments provided by the present application, a real-time process schematic diagram of a communication method in a scenario where the continuous access to the network fails due to the failure of RRC connection establishment is shown;

[0032] Figure 6 According to some embodiments provided by the present application, an implementation process schematic diagram of a communication method in a scenario where the mobile phone 100 continuously fails to initiate an ATTACH request or a TAU request due to receiving an RRC Release in advance is shown;

[0033] Figure 7 According to some embodiments provided by the present application, an implementation process schematic diagram of a communication method in a scenario where the mobile phone 10 continuously fails to initiate an ATTACH request or a TAU request due to the timeout of the T3410 timer or the T3430 timer is shown;

[0034] Figure 8 According to some embodiments provided by the present application, an implementation process schematic diagram of a communication method in a scenario where the mobile phone 100 fails to initiate an ATTACH request or a TAU request due to the rejection of the attach request or the tracking area update request is shown;

[0035] Figure 9 According to some embodiments provided by the present application, an implementation flowchart of a communication method in a scenario where the mobile phone 100 fails to initiate an ATTACH request or a TAU request due to multiple reasons is shown;

[0036] Figure 10 According to some embodiments provided by the present application, a schematic diagram of the structure of a terminal device is shown. Specific embodiments

[0037] Illustrative embodiments of the present application include, but are not limited to, a communication method, a terminal device, and a readable storage medium.

[0038] It can be understood that the terminal device in the embodiments of the present application may also be referred to as a terminal, an electronic device, a mobile terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The terminal device may be a mobile phone, a smart TV, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The following will take a mobile phone as an example for illustration. However, it can be understood that the technical solutions described in the present application are applicable to various terminal devices with mobile communication functions as described above, not limited to mobile phones.

[0039] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5G system or New Radio (NR), etc.

[0040] To facilitate the understanding of the embodiments of the present application, some terms used in the embodiments of the present application are explained below to facilitate the understanding of those skilled in the art.

[0041] (1) Attachment (ATTACH)

[0042] In a mobile communication network, the ATTACH process refers to the process in which, after a UE establishes a radio resource control (RRC) connection with a base station, it sends an attachment request (ATTACH REQUEST) to a network node (mobility management entity, MME) to register the UE in the network and obtain corresponding services. That is to say, ATTACH is the process by which the UE establishes a connection with the network through the base station so that the UE can perform mobile services, such as calls.

[0043] (2) Tracking area (TA)

[0044] The network area that a base station can cover can be divided into multiple TAs. The UE is located in a TA. The TA is the basic unit for updating and paging the location of the UE in the LTE system. Each TA can be further divided into one or more cells.

[0045] (3) Tracking area update (TAU)

[0046] TAU refers to the process in which when the UE moves from one TA to another TA, it is necessary to re-register the UE's location in the new TA in the evolved packet core (EPC).

[0047] (4) Radio resource control (RRC)

[0048] The RRC layer can be responsible for radio resource control between the UE and the network. Before the UE and the network carry services, it is necessary to establish an RRC connection first. Based on the successful establishment of the RRC connection, the broadcast of system information, paging, RRC connection management, radio resource control, mobility management, etc. can be achieved.

[0049] The technical solution of the present application is specifically introduced below with reference to the accompanying drawings.

[0050] For example, Figure 1 shows a schematic diagram of a scenario where a mobile phone 100 accesses the network. Refer to Figure 1, the base station 01 can provide mobile communication network coverage to meet the communication needs of the mobile phone 100 to access the mobile communication network at any time and anywhere. For example, the areas covered by the mobile communication network can include TA02, TA03, etc. TA02 can include cell 021, cell 022, etc., and TA03 can include cell 031, cell 032, etc. When the mobile phone 100 is located in cell 021, it can access the network in cell 021 through initiating an ATTACH or TAU procedure to conduct mobile services such as calls. When the mobile phone 100 moves from cell 021 to cell 031 or cell 032, the mobile phone 100 can re-access the network by initiating a TAU procedure.

[0051] As mentioned above, due to underlying reasons and various reasons such as RRC connection release during the ATTACH or TAU process, timeout of timers such as T3410, and ATTACH REJECT, etc., it may cause the UE to continuously initiate ATTACH or TAU failures, and correspondingly the UE will continuously fail to access the network. Among them, the above-mentioned underlying reasons can include that the cell network signal where the mobile phone 100 is currently located is poor, so that the base station 01 does not receive the attachment request "ATTACH REQUEST" sent by the UE, etc. The above-mentioned underlying reasons can also include the timeout of the T300 timer, etc. During the ATTACH process, the timeout of the T300 timer can indicate the failure of RRC connection establishment. The T300 timer is a timer used in the RRC connection establishment process in the TS24.301 protocol. When the T300 timer times out, it means that the RRC connection establishment is not completed within the preset time.

[0052] In addition, based on the provisions of the TS24.301 protocol: when the number of consecutive network access failures of the UE is less than 5 times, the T3411 timer will be started, with a duration of 10 s; when the number of consecutive network access failures of the UE is greater than 5 times, the T3402 timer will be started, with a duration of 12 min.

[0053] Therefore, no matter what reason causes the UE to continuously fail to access the network, the UE needs to wait for the timers T3411 and T3402 to time out before it can re-initiate ATTACH or TAU to access the network, which affects the network access efficiency of the UE.

[0054] It can be understood that the RRC layer corresponding to the radio resource control RRC is the third layer in the radio access protocol architecture applied in mobile communication. For example, refer to Figure 2Schematic diagram of the wireless access protocol architecture shown, which may include three layers. The first layer is the physical layer (PHY); the second layer may include the media access layer (MAC), the radio link control layer (RLC), and the packet data convergence protocol (PDCP); the third layer may include the radio resource control layer RRC layer and the non-access stratum (NAS).

[0055] The communication method provided in the embodiments of this application requires the use of the RRC layer and the NAS layer. It can be understood that the NAS layer, as the non-access layer, is the functional layer between the UE and the network, that is, the NAS layer can be used to handle the signaling interaction between the UE and the MME. The RRC layer, as the access layer, can be used to handle the signaling interaction between the UE and the base station, that is, the RRC layer can be responsible for network selection, cell selection, and radio resource management. Among them, radio resource management may include RRC connection establishment, call release, etc. It can be said that the access layer builds the underlying bearer for the signaling process of the non-access layer.

[0056] In some embodiments, the RRC layer of the UE can configure the UE to measure the reference signal receiving power (RSRP) of the reference signal sent by the base station through the physical layer (or can be called the specific reference signal of the current cell), and then the physical layer can send the RSRP to the RRC layer. That is to say, the RSRP of the current cell where the UE is located can be obtained from the RRC layer through the physical layer as an intermediary. For example, the RSRP can be measured through the physical layer when the UE sends channel state information (CSI) to the base station, and then the RSRP is sent to the RRC layer.

[0057] It can be understood that the RSRP refers to the average value of the signal power received on all resource elements (REs) carrying the reference signal of the current cell within a certain symbol, which can be used to characterize the radio signal quality between the cell where the UE is located and the base station, that is, the intensity of the reference signal sent by the base station received by the current cell. It can be understood that the reference signal is also a kind of radio signal.

[0058] It can be understood that the range of the RSRP can be from -140 dBm to -44 dBm. The higher the RSRP, the higher the quality of the radio signal of the current cell and the higher the communication quality.

[0059] To solve the above problems, an embodiment of the present application provides a communication method. The method includes: when the total number of times that the terminal device fails to initiate an ATTACH request or a TA request in the current cell reaches the first number threshold, the terminal device can start a first timer. When the total number of consecutive ATTACH or TAU failures of the terminal device in the current cell reaches the second number threshold, the reference signal received power of the current cell, that is, the RSRP of the current cell, can be directly obtained based on the RRC layer, where the RSRP can be used to indicate the wireless signal strength in the current cell. For example, if the RSRP of the current cell is -117 dBm, it means that the wireless signal in the current cell is weak, and the UE can display one bar of wireless signal, for example. At this time, a penalty value (cell - offset) can be added to the RSRP of the current cell to further reduce the wireless signal strength of the current cell. For example, if the penalty value is -5 dBm, the RSRP of the current cell can become -122 dBm after adding the penalty value. Based on this, the terminal device can trigger the search for and preferably other cells with a larger RSRP. For example, if the RSRP of a neighboring cell is searched to be -80 dBm, an ATTACH request or a TAU request can be re - initiated in the neighboring cell to access the network.

[0060] It can be understood that if no neighboring cell with an RSRP better than that of the current cell is found for the terminal device to access, the terminal device can continue to re - initiate an ATTACH request or a TAU request in the current cell to access the network.

[0061] In this way, through the above - mentioned solution, regardless of the reason for the continuous failure of the terminal device to initiate an ATTACH request or a TAU request, that is, the failure to access the network, the terminal device can quickly re - initiate an ATTACH request or a TAU request in a cell with better wireless signal and achieve quick access to the network. That is, the communication solution provided by the present application does not need to wait for the timer T3411 or T3402 to time out before initiating an ATTACH request or a TAU request, which is beneficial to saving the time for the terminal device to access the network and improving the network access efficiency of the terminal device.

[0062] Figure 3 According to an embodiment of the present application, a schematic flowchart of an implementation process of a communication method in a scenario where a UE initiates an ATTACH request or a TAU request and fails is shown.

[0063] It can be understood that in some embodiments of the present application, Figure 3 the execution subject of each step in the shown process can be the processor of the above - mentioned mobile phone 100. In other embodiments, Figure 3 the execution subject of each step in the shown process can also be the processor of a terminal device such as a tablet computer, a smart wearable device, a smart home device, a vehicle - mounted device, etc., which is not limited herein.

[0064] Specifically,Figure 3 The process shown may include the following steps:

[0065] S301: Initiate an attach request or a tracking area update request.

[0066] In some embodiments, the mobile phone 100 may establish a connection with the network by initiating an ATTACH request or a TAU request. Before that, the RRC layer of the mobile phone 100 may send an RRC connection establishment request "RRCConnectionRequest" to the base station to establish an RRC connection with the base station. After the RRC connection is established, the NAS layer of the mobile phone 100 may send an attach request (ATTACH REQUEST) to the MME to access the network for mobile services.

[0067] It can be understood that initiating an attach request or a tracking area update request may indicate the start of the attach or tracking area update process.

[0068] It can be understood that the process of establishing an RRC connection may include: the RRC layer of the mobile phone 100 sending "RRCConnectionRequest" to the base station, and "RRCConnectionRequest" may include necessary parameters such as the temporary identity document (ID) of the mobile phone 100 and the cell identity where it is located. After receiving "RRCConnectionRequest", the base station may perform authentication and confirmation. The base station will confirm the identity of the mobile phone 100 by verifying the temporary ID and cell identity of the mobile phone 100. Then, the base station will allocate an RRC connection identifier for the mobile phone 100. Furthermore, an RRC connection is established between the mobile phone 100 and the base station, so that the mobile phone 100 can request network system information from the base station.

[0069] It can be understood that the MME is a key control node for accessing the network in the 3GPP protocol and can be responsible for the positioning, paging, etc. of UEs in the idle mode.

[0070] In some embodiments, when the mobile phone 100 moves from cell 021 to cell 031, it is necessary to re-register the location of the mobile phone 100 entering the new cell in the evolved packet core (EPC). The NAS layer of the mobile phone 100 may send a tracking area update request (TAU REQUEST) to the MME. After receiving the TAU REQUEST, the MME will update the location cell of the mobile phone 100 to 031.

[0071] S302: Detect that the initiation of the attach request or the tracking area update request fails and count the number of failures.

[0072] In some embodiments, when the mobile phone 100 fails to initiate an ATTACH request or a TAU request, the NAS layer of the mobile phone 100 can detect that the mobile phone 100 fails to initiate an ATTACH request or a TAU request, and use a counter to count the number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request.

[0073] It can be understood that the failure to initiate an ATTACH request or a TAU request indicates that the mobile phone 100 fails to access the network. Therefore, counting the number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request, that is, counting the number of failures of the mobile phone 100 to access the network. Based on this, the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request currently, that is, the total number of failures of the mobile phone 100 to access the network currently, can be obtained through the counting result.

[0074] S303: Determine whether the total number of failures is greater than or equal to the short-term retry count threshold.

[0075] If the judgment result is yes, go to S305, start the long-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0076] If the judgment result is no, go to S304, start the short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0077] In some embodiments, when the mobile phone 100 executes the above step S302, the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request can be determined, and it can be determined whether the total number of failures is greater than or equal to the short-term retry count threshold. For example, the short-term retry count threshold can be set to 6 times.

[0078] It can be understood that taking the short-term retry count threshold as 6 times in the embodiments of the present application is only an exemplary illustration, and the short-term retry count threshold can also be set to any other count threshold greater than 6 times, which is not limited herein.

[0079] S304: Start the short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0080] In some embodiments, when it is determined based on S303 that the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request currently is less than the short-term retry count threshold, the short-term retry timer can be started. For example, the duration of the short-term retry timer can be 8s. In addition, the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request, that is, the total number of failures of the mobile phone 100 to access the network, so the number of consecutive access failures of the mobile phone 100 in the current cell can be incremented by 1.

[0081] It can be understood that the timeout duration of the short-term retry timer being 8 s in the embodiments of the present application is only an exemplary illustration. The timeout duration of the short-term retry timer can also be any duration less than or greater than 8 s, which is not limited herein.

[0082] It can be understood that the manner in which the mobile phone 100 accesses the network can be random access. Random access refers to accessing the network through a random access channel (RACH), which is not limited herein. Among them, the RACH is an uplink transmission channel, and random access can enable the mobile phone 100 to establish a connection with the base station.

[0083] S305: Start a long-term retry timer, and increment the number of consecutive access failure times in the current cell by 1.

[0084] In some embodiments, when, based on S303, it is determined that the total number of failure times of the mobile phone 100 initiating an ATTACH request or a TAU request fails is greater than or equal to the short-term retry count threshold, then a long-term retry timer can be started. For example, the duration of the long-term retry timer can be 13 min. In addition, the total number of failure times of the mobile phone 100 initiating an ATTACH request or a TAU request fails, which is also the total number of failure times of accessing the network. Therefore, the number of consecutive access failure times of the mobile phone 100 in the current cell can be incremented by 1.

[0085] It can be understood that the timeout duration of the first long-term retry timer being 13 min in the embodiments of the present application is only an exemplary illustration. The timeout duration of the long-term retry timer can also be any duration less than or greater than 13 min, which is not limited herein.

[0086] It can be understood that the timeout duration of the long-term retry timer is greater than the timeout duration of the short-term retry timer.

[0087] S306: Determine whether the number of consecutive access failure times in the current cell is greater than or equal to the preset count threshold N.

[0088] If the determination result is yes, proceed to S307, obtain the reference signal received power of the current cell, and add a penalty value to the reference signal received power of the current cell to reduce the reference signal received power of the current cell.

[0089] If the determination result is no, proceed to S310. After waiting for the timer to timeout in the current cell, re-initiate an attach request or a tracking area update request.

[0090] In some embodiments, when the mobile phone 100 executes the above step S302, the total number of failures of the mobile phone 100 to continuously initiate an ATTACH request or a TAU request in the current cell can be determined, that is, the number of consecutive access failures of the mobile phone 100 in the current cell. Furthermore, it can be determined whether the number of consecutive access failures of the mobile phone 100 in the current cell is greater than or equal to a preset number threshold N. For example, N = 10, N ≥ 5.

[0091] It can be understood that the preset number threshold can be greater than the above-mentioned short-term retry number threshold.

[0092] It can be understood that the mobile phone 100 can establish a network connection with the base station in the current cell by using random access.

[0093] It can be understood that the above-mentioned short-term retry number can be shortRetry. If shortRetry = M * N, it can be explained that when the mobile phone 100 attempts to initiate an ATTACH or TAU request in M cells, consecutive access failures occur. Based on this, the retry interval can be lengthened, and a long-term retry timer can be started for each retry. For example, the long-term retry timer is longRetryTimer, and the timeout duration of longRetryTimer should be greater than the short-term retry timer shortRetryTimer.

[0094] S307: Obtain the reference signal receiving power of the current cell, and increase a penalty value to the reference signal receiving power of the current cell to reduce the reference signal receiving power.

[0095] In some embodiments, when it is determined based on S306 that the number of consecutive failures of the mobile phone 100 in the current cell is greater than or equal to N times, the reference signal receiving power of the current cell can be directly obtained through the RRC layer as shown above, and a penalty value is added to the reference signal receiving power of the current cell to reduce the reference signal receiving power of the current cell. Figure 2 For example, the reference signal receiving power RSRP1 of the current cell is -117 dBm. A penalty value of -5 dBm is added to RSRP1, and the RSRP1 of the current cell is reduced from -117 dBm to -122 dBm. RSRP1 can be reflected on the interface of the mobile phone 100 as the wireless signal strength decreasing from 1 bar to zero.

[0096] By reducing the reference signal receiving power of the current cell, when there is a cell with a reference signal receiving power higher than -122 dBm nearby, the mobile phone 100 can automatically search for a cell with a higher reference signal receiving power and automatically initiate an ATTACH or TAU request in the cell with a higher reference signal receiving power to access the network.

[0097] ​

[0098] It can be understood that in the fourth-generation or fifth-generation mobile communication network, the range of the RSRP signal strength standard is from -140 dBm to -44 dBm. The larger the RSRP, the stronger the signal strength, and the smaller the RSRP, the weaker the signal strength. Among them, -140 dBm indicates a weak wireless signal, while -44 dBm indicates a strong wireless signal.

[0099] It can be understood that taking the reference signal received power RSRP1 of the current cell as -117 dBm in the embodiments of the present application is only an illustrative example. In some other embodiments, the reference signal received power RSRP1 of the current cell can also be any value from -140 dBm to -44 dBm.

[0100] It can be understood that taking the penalty value as -5 dBm in the embodiments of the present application is only an illustrative example. In some other embodiments, the penalty value can also be set to any value from -5 dBm to -15 dBm, which is not limited herein. In addition, the reference signal received power after increasing the penalty value still needs to satisfy the range from -140 dBm to -44 dBm.

[0101] For example, the reference signal received power RSRP1 of the current cell is -117 dBm. By increasing the penalty value of -5 dBm, -117 dBm is reduced to -122 dBm, and neighboring cells with a reference signal received power greater than -122 dBm are automatically searched. If no such cells are found, the penalty value can be further increased. For example, by increasing the penalty value of -5 dBm again, -122 dBm is reduced to -127 dBm, and neighboring cells with a reference signal received power greater than -127 dBm are automatically searched for network connection. If no neighboring cells with a reference signal received power greater than -127 dBm are found within the preset time, the reference signal received power of the current cell can be restored to -117 dBm, and a new attempt to connect to the network can be made in the current cell.

[0102] S308: Search for other cells with a reference signal received power greater than that of the current cell, and clear the count of consecutive access failure times.

[0103] In some embodiments, when the RSRP1 of the current cell has been reduced to -122 dBm, the RRC layer of the mobile phone 100 searches for neighboring cells in real time to check if there are any cells with a reference signal received power higher than -122 dBm nearby. If any exist, an ATTACH or TAU request is re-initiated in the cell with the highest reference signal received power. For example, the RSRP of neighboring cell A1 is -80 dBm, the RSRP of neighboring cell A2 is -110 dBm, the RSRP of neighboring cell A3 is -105 dBm, etc. In addition, the count of the consecutive access failure times of the mobile phone 100 in the current cell is cleared.

[0104] S309: Initiate an attach request or a tracking area update request in other cells.

[0105] In some embodiments, if a neighboring cell with a relatively high reference signal received power is detected, an attach or a tracking area update request may be initiated in the neighboring cell with the highest reference signal received power. For example, if the RSRP of neighboring cell A1 is -80 dBm, the RSRP of neighboring cell A2 is -110 dBm, and the RSRP of neighboring cell A3 is -105 dBm, then based on -80 dBm > -105 dBm > -110 dBm > -122 dBm, an ATTACH or TAU request is selected to be initiated in neighboring cell A1. If no neighboring cell with a reference signal received power higher than -122 dBm is detected, the mobile phone 100 continues to wait in the current cell until the short-term retry timer or the long-term retry timer expires, and then re-initiates an ATTACH request or a TAU request.

[0106] S310: After the timer in the current cell expires, re-initiate an attach request or a tracking area update request.

[0107] In some embodiments, when it is determined based on S306 that the number of consecutive failures of the mobile phone 100 in the current cell is less than N times, for example, N = 10 (N ≥ 5), then continue to wait in the current cell until the timer expires, and then re-initiate an ATTACH request or a TAU request in the current cell.

[0108] For example, when the number of consecutive failures of the mobile phone 100 in the current cell is 5, which is less than the short-term retry count threshold of 6 and less than 10, then it can wait for the short-term retry timer to expire, that is, wait for 8 s. During this period, the mobile phone 100 cannot re-initiate an ATTACH request or a TAU request in the current cell. After waiting for 8 s, the mobile phone 100 can re-initiate an ATTACH request or a TAU request in the current cell.

[0109] For another example, when the number of consecutive failures of the mobile phone 100 in the current cell is 8, which is greater than the short-term retry count threshold of 6 and less than 10, then it can wait for the long-term retry timer to expire, that is, wait for 13 min. During this period, the mobile phone 100 cannot re-initiate an ATTACH request or a TAU request in the current cell. After waiting for 13 min, the mobile phone 100 can re-initiate an ATTACH request or a TAU request in the current cell.

[0110] Through the above communication method, when the mobile phone 100 continuously initiates an ATTACH request or a TAU request and fails, that is, in the case of continuous network access failure, the mobile phone 100 can quickly re-initiate an ATTACH request or a TAU request in a cell with better wireless signal and access the network. Instead of waiting for the timer T3411 or T3402 to time out before re-initiating an ATTACH or TAU, the time for the mobile phone 100 to access the network is saved, and the network access efficiency of the mobile phone 100 is improved.

[0111] In some embodiments, underlying reasons may cause the mobile phone 100 to continuously initiate an ATTACH request or a TAU request and fail.

[0112] Next, in combination with scenarios where different reasons cause the UE such as the mobile phone 100 to continuously initiate an ATTACH request or a TAU request and fail, the specific implementation process of the communication method provided in this application in the corresponding scenarios will be described in detail.

[0113] First, the specific implementation process of the communication method provided in this application applied to the scenario where the mobile phone 100 continuously initiates an ATTACH request or a TAU request and fails due to underlying reasons will be introduced in combination with Embodiment 1.

[0114] Embodiment 1

[0115] Figure 4 According to the embodiment of the present application, a schematic diagram of the implementation process of a communication method in a scenario where the mobile phone 100 continuously initiates an ATTACH request or a TAU request and fails due to underlying reasons is shown.

[0116] Specifically, Figure 4 The shown process may include the following steps:

[0117] S401: Initiate an attach request or a tracking area update request.

[0118] Exemplarily, this step S401 may refer to the relevant description in the above step S301 and will not be elaborated here.

[0119] S402: Detect that the initiation of the attach request or the tracking area update request fails due to underlying reasons, and count the number of failures.

[0120] In some embodiments, the underlying reason may be that the wireless signal of the cell where the mobile phone 100 is located is poor. Due to the poor wireless signal, the base station 01 may not receive the "RRCConnectionRequest" sent by the mobile phone 100. As a result, the base station 01 cannot send the message "RRCConnectionSetup" for establishing an RRC connection to the RRC layer, and the RRC connection cannot be successfully established. Then, the RRC layer reports this situation to the NAS layer, and the NAS layer terminates the initiation of the ATTACH request or TAU request. In this way, the mobile phone 100 fails to initiate an attach request or a tracking area update request, and a counter is used to count the number of failures of the mobile phone 100 to initiate an ATTACH request or TAU request due to the underlying reason.

[0121] It can be understood that the failure to initiate an ATTACH request or TAU request due to the underlying reason indicates that the mobile phone 100 fails to access the network. Therefore, counting the number of failures to initiate an ATTACH request or TAU request due to the underlying reason is also counting the number of failures to access the network. Based on this, the total number of failures of the mobile phone 100 to currently initiate an ATTACH request or TAU request can be obtained through the counting result, that is, the total number of failures of the mobile phone 100 to currently access the network.

[0122] S403: Determine whether the total number of failures is greater than or equal to the first short-term retry count threshold.

[0123] If the judgment result is yes, go to S405, start the first long-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0124] If the judgment result is no, go to S404, start the first short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0125] In some embodiments, when the mobile phone 100 executes the above step S402, the total number of failures of the mobile phone 100 to initiate an ATTACH request or TAU request due to the underlying reason can be determined, and then it can be judged whether the total number of failures is greater than or equal to the first short-term retry count threshold. For example, the first short-term retry count threshold can be set to 7 times.

[0126] It can be understood that taking the first short-term retry count threshold as 7 times in the embodiments of the present application is only an exemplary illustration, and the first short-term retry count threshold can also be set to any other count threshold less than or greater than 7, which is not limited herein.

[0127] S404: Start the first short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0128] In some embodiments, when, based on S403, it is determined that the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request due to underlying reasons is less than the first short-term retry count threshold, the first short-term retry timer may be started, and the number of consecutive access failures of the mobile phone 100 in the current cell is incremented by 1. For example, the duration of the first short-term retry timer may be 9 s. It can be understood that the failure to initiate an ATTACH request or a TAU request also indicates that the mobile phone 100 fails to access the network.

[0129] It can be understood that using a duration of 9 s for the first short-term retry timer in the embodiments of the present application is only an exemplary illustration, and the first short-term retry count threshold may also be any duration less than or greater than 9 s, which is not limited herein.

[0130] S405: Start the first long-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0131] In some embodiments, when, based on S403, it is determined that the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request due to underlying reasons is greater than or equal to the first short-term retry count threshold, the first long-term retry timer may be started, and the number of consecutive access failures of the mobile phone 100 in the current cell is incremented by 1. For example, the duration of the first long-term retry timer may be 14 min.

[0132] It can be understood that using a duration of 14 min for the first long-term retry timer in the embodiments of the present application is only an exemplary illustration, and the timeout duration of the first long-term retry timer may also be any duration less than or greater than 14 min, which is not limited herein.

[0133] It can be understood that the timeout duration of the first long-term retry timer is greater than the timeout duration of the first short-term retry timer.

[0134] S406: Determine whether the number of consecutive access failures in the current cell is greater than or equal to the first preset count threshold N1.

[0135] If the determination result is yes, proceed to S407 to obtain the reference signal received power of the current cell, and add a penalty value to the reference signal received power of the current cell to reduce the reference signal received power of the current cell.

[0136] If the determination result is no, proceed to S410. After waiting for the timer to time out in the current cell, re-initiate an attach request or a tracking area update request.

[0137] In some embodiments, when the mobile phone 100 executes the above-mentioned step S402, the total number of failures of the mobile phone 100 to continuously initiate ATTACH requests or TAU requests due to underlying reasons in the current cell can be determined, that is, the number of consecutive access failures of the mobile phone 100 in the current cell. Furthermore, it can be determined whether the number of consecutive access failures of the mobile phone 100 in the current cell is greater than or equal to the first preset number threshold N1. For example, N1 = 10, N1 ≥ 5.

[0138] It can be understood that the first preset number threshold N1 can be greater than the above-mentioned first short-term retry number threshold.

[0139] It can be understood that the above-mentioned first short-term retry number can be shortRetry1. If shortRetry1 = M * N, it can be explained that the mobile phone 100 attempts to initiate ATTACH requests or TAU requests in M cells and all result in consecutive access failures. Then, the retry interval can be lengthened, and each retry can start the first long-term retry timer. For example, the first long-term retry timer is longRetryTimer1, and the timeout duration of longRetryTimer1 should be greater than the timeout duration of the first short-term retry timer shortRetryTimer1.

[0140] S407: Obtain the reference signal received power of the current cell, and add a penalty value to the reference signal received power of the current cell to reduce the reference signal received power.

[0141] Exemplarily, the specific execution process of this step S407 can refer to the relevant description in the above step S307, and will not be elaborated here.

[0142] S408: Search for other cells with a reference signal received power greater than that of the current cell, and clear the number of consecutive access failures.

[0143] Exemplarily, the specific execution process of this step S408 can refer to the relevant description in the above step S308, and will not be elaborated here.

[0144] S409: Initiate an attach request or a tracking area update request in other cells.

[0145] Exemplarily, the specific execution process of this step S409 can refer to the relevant description in the above step S309, and will not be elaborated here.

[0146] S410: After waiting for the timer to timeout in the current cell, re-initiate an attach request or a tracking area update request.

[0147] Exemplarily, the specific execution process of this step S410 can refer to the relevant description in the above step S310, and will not be elaborated here.

[0148] Through the above communication method, for the case where the consecutive initiation of ATTACH requests or TAU requests fails due to underlying reasons, that is, the case of consecutive network access failures, the mobile phone 100 can quickly re-initiate an ATTACH request or a TAU request in a cell with better radio signals and access the network. Instead of waiting for the timer T3411 or T3402 to time out before re-initiating an ATTACH request or a TAU request, the time for the mobile phone 100 to access the network is saved, and the network access efficiency of the mobile phone 100 is improved.

[0149] In some other embodiments, the underlying reason may be the failure of RRC connection establishment caused by the timeout of the T300 timer.

[0150] Figure 5 According to the embodiments of the present application, a schematic diagram of the real-time process of another communication method in the scenario where consecutive network access failures are caused by the failure of RRC connection establishment as the underlying reason is shown.

[0151] The specific process may include:

[0152] S501: Initiate an attach request or a tracking area update request.

[0153] Exemplarily, the specific execution process of this step S501 may refer to the relevant description in the above step S301 and will not be elaborated here.

[0154] S502: Detect that the T300 timer times out, the radio resource control connection establishment fails, and count the number of failures.

[0155] In some embodiments, successfully establishing an RRC connection is a prerequisite for the mobile phone 100 to initiate an ATTACH request or a TAU request. When the NAS layer of the mobile phone 100 detects that the RRC connection establishment fails due to the timeout of the T300 timer, the NAS layer terminates the initiation of the ATTACH request or the TAU request, that is, the initiation of the ATTACH request or the TAU request fails. It can be understood that the T300 timer is a timer used in the RRC connection establishment process in the TS24.301 protocol, and the timeout duration of the T300 timer can be 1000 ms. The T300 timer starts when the mobile phone 100 sends "RRCConnectionRequest" to the base station. When the T300 timer times out and the RRC layer has not received "RRCConnectionSetup" sent by the base station 01, it can indicate that the RRC connection establishment fails, and a counter is used to count the number of failures of the mobile phone 100 due to the failure of the RRC connection establishment after the T300 timer times out, resulting in the failure of initiating an ATTACH request or a TAU request. It can be understood that the failure of initiating an ATTACH request or a TAU request can indicate that the mobile phone 100 fails to access the network. Therefore, counting the number of failures of initiating an ATTACH request or a TAU request, that is, counting the number of failures of accessing the network. Based on this, the total number of failures of the mobile phone 100 currently initiating an ATTACH request or a TAU request can be obtained through the counting result, that is, the total number of failures of the mobile phone 100 currently accessing the network fails.

[0156] It can be understood that taking the timeout duration of the T300 timer as 1000 ms as an example in the embodiments of the present application is only an exemplary illustration. In some other embodiments, the timeout duration of the T300 timer can also be any duration from 100 ms to 2000 ms, which is not limited herein.

[0157] S503: Determine whether the total number of failures is greater than or equal to the first short-term retry count threshold.

[0158] Exemplarily, the specific execution process of this step S503 can refer to the relevant descriptions in the above steps S303 or S403, and will not be elaborated herein.

[0159] S504: Start the first short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0160] Exemplarily, the specific execution process of this step S504 can refer to the relevant descriptions in the above steps S304 or S404, and will not be elaborated herein.

[0161] S505: Start the first long-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0162] Exemplarily, the specific execution process of this step S505 can refer to the relevant descriptions in the above steps S305 or S405, and will not be elaborated here.

[0163] S506: Determine whether the number of consecutive access failures in the current cell is greater than or equal to the first preset number threshold N1.

[0164] Exemplarily, the specific execution process of this step S506 can refer to the relevant descriptions in the above steps S306 or S406, and will not be elaborated here.

[0165] S507: Obtain the reference signal receiving power of the current cell, and increase a penalty value to the reference signal receiving power of the current cell to reduce the reference signal receiving power.

[0166] S508: Search for other cells with a reference signal receiving power greater than that of the current cell, and clear the number of consecutive access failures.

[0167] S509: Initiate an attach request or a tracking area update request in other cells.

[0168] S510: After the timer expires in the current cell, re-initiate an attach request or a tracking area update request.

[0169] Exemplarily, S507 to S510 can refer to the relevant descriptions in the above S307 to S310 or S407 to S410, and will not be elaborated here.

[0170] In some other embodiments, when it is determined based on S506 that the number of consecutive access failures of the mobile phone 100 in the current cell is greater than or equal to N times, it is also possible to set a prohibition on initiating an ATTACH request or a TAU request in the current cell within a preset duration. For example, the preset duration can be any duration, such as 24 minutes, 15 minutes, etc., which is not limited here.

[0171] Through the above communication method, for the case where the RRC connection establishment fails due to the timeout of the T300 timer, and further causes the mobile phone 100 to continuously initiate an attach request or a TAU request to fail, that is, the case of continuous network access failure, the mobile phone 100 can quickly re-initiate an attach request or a TAU request in a cell with better wireless signal and access the network. Instead of waiting for the timers T3411 or T3402 to timeout before re-initiating an attach request or a TAU request, it saves the time for the mobile phone 100 to access the network and improves the network access efficiency of the mobile phone 100.

[0172] In some other embodiments, when the mobile phone 100 is in the ATTACH or TAU state, due to situations such as RRC configuration failure or handover failure between the mobile phone 100 and the base station, the base station 01 sends an RRC connection release message "RRCRelease" to the mobile phone 100 in advance, causing the mobile phone 100 to fail to initiate an ATTACH request or a TAU request.

[0173] Next, the communication method provided by the present application will be introduced in combination with Embodiment 2, and the specific implementation process in the scenario where the mobile phone 100 continuously fails to initiate an ATTACH request or a TAU request due to receiving an RRCRelease in advance will be described.

[0174] Embodiment 2

[0175] Figure 6 According to the embodiments of the present application, a schematic flowchart of an implementation process of a communication method in a scenario where the mobile phone 100 continuously fails to initiate an ATTACH request or a TAU request due to receiving an RRC Release in advance is shown.

[0176] The specific process includes:

[0177] S601: Initiate an attach request or a tracking area update request.

[0178] Exemplarily, this step S501 can refer to the relevant description of step S301 above, and will not be elaborated here.

[0179] S602: Detect that the initiation of the attach request or the tracking area update request fails due to the early release of the radio resource control connection, and count the number of failures.

[0180] In some embodiments, after the mobile phone 100 and the base station establish an RRC connection, the NAS layer of the mobile phone 100 can send an attach request (ATTACH REQUEST) or a tracking area update request (TAU REQUEST) to the MME. However, if the mobile phone 100 is in the ATTACH or TAU state and there are situations such as RRC configuration failure or handover failure between the mobile phone 100 and the base station 01, the base station 01 sends an "RRC Release", that is, a radio resource control connection release message, to the RRC layer of the mobile phone 100 in advance before the ATTACH or TAU is completed. When the RRC layer receives the "RRC Release", it reports the situation to the NAS layer, and then the NAS layer interrupts the initiation of the ATTACH request or the TAU request, that is, the mobile phone 100 fails to initiate the ATTACH request or the TAU request, and a counter is used to count the number of failures of the mobile phone 100 to initiate the ATTACH request or the TAU request due to the RRC Release.

[0181] It can be understood that if the ATTACH request or TAU request fails due to the RRC Release, it indicates that the mobile phone 100 fails to access the network. Therefore, the number of failures of the ATTACH request or TAU request that fails due to receiving the RRC Release in advance is counted, that is, the number of failures of accessing the network is counted. Based on this, the total number of failures of the current ATTACH request or TAU request initiated by the mobile phone 100 can be obtained through the counting result, that is, the total number of failures of the mobile phone 100 to access the network currently, which can also be referred to as the number of consecutive access failures.

[0182] S603: Determine whether the total number of failures is greater than or equal to the second short-term retry count threshold.

[0183] If the judgment result is yes, go to S505, start the second long-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0184] If the judgment result is no, go to S504, start the second short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0185] In some embodiments, when the mobile phone 100 executes the above step S602, it can be determined that during the process of the NAS layer of the mobile phone 100 initiating an ATTACH request or a TAU request, the RRC layer receives an RRC Release, resulting in the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request, and then it can be determined whether the total number of failures is greater than or equal to the second short-term retry count threshold. For example, the second short-term retry count threshold can be set to 8 times.

[0186] It can be understood that taking the second short-term retry count threshold as 8 times in the embodiments of the present application is only an exemplary illustration, and the second short-term retry count threshold can also be set to any other count threshold less than or greater than 8, which is not limited herein.

[0187] S604: Start the second short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0188] In some embodiments, when it is determined based on S603 that during the process of the NAS layer of the mobile phone 100 initiating an ATTACH request or a TAU request, the RRC layer receives an RRC Release, resulting in the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request being less than the second short-term retry count threshold, the second short-term retry timer can be started, and the number of consecutive failures of the mobile phone 100 in the current cell is incremented by 1. For example, the duration of the second short-term retry timer can be 10s.

[0189] It can be understood that taking the duration of the second short - term retry timer as 10 s in the embodiments of the present application is only an exemplary illustration. The second short - term retry count threshold can also be any duration less than or greater than 10 s, which is not limited herein.

[0190] S605: Start the second long - term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0191] In some embodiments, when, based on S603, it is determined that during the process of the NAS layer of the mobile phone 100 initiating an ATTACH request or a TAU request, the RRC layer receives an RRC Release, and the total number of failures causing the mobile phone 100 to initiate an ATTACH request or a TAU request to fail is greater than or equal to the second short - term retry count threshold, then the second long - term retry timer can be started, and the number of consecutive failures of the mobile phone 100 in the current cell is incremented by 1. For example, the duration of the second long - term retry timer can be 15 min.

[0192] It can be understood that taking the duration of the second long - term retry timer as 15 min in the embodiments of the present application is only an exemplary illustration. The second long - term retry count threshold can also be any duration less than or greater than 15 min, which is not limited herein.

[0193] It can be understood that the duration of the second long - term retry timer is greater than the duration of the second short - term retry timer.

[0194] It can be understood that in some other embodiments, the duration of the second short - term retry timer can be the same as the duration of the first short - term retry timer, and the timeout duration of the second long - term retry timer can be the same as the timeout duration of the first long - term retry timer, which is not limited herein.

[0195] S606: Determine whether the number of consecutive access failures in the current cell is greater than or equal to the second preset count threshold N2.

[0196] If the judgment result is yes, go to S607, obtain the reference signal received power of the current cell, and add a penalty value to the reference signal received power of the current cell to reduce the reference signal received power.

[0197] If the judgment result is no, go to S610, and after waiting for the timer to timeout in the current cell, re - initiate an attach request or a tracking area update request.

[0198] In some embodiments, when, based on S602, it is determined that the mobile phone 100 receives an RRCRelease in advance during ATTACH or TAU, and further, the total number of failures in continuously initiating an ATTACH request or a TAU request fails in the current cell, that is, the number of consecutive access failures of the mobile phone 100 in the current cell, it can be further determined whether the number of consecutive access failures of the mobile phone 100 in the current cell is greater than or equal to, for example, N2 = 10, N2 ≥ 5.

[0199] It can be understood that the second preset number threshold N2 can be greater than the above-mentioned second short-term retry number threshold.

[0200] It can be understood that the above-mentioned second short-term retry number can be shortRetry2. If shortRetry2 = M * N, it can be explained that the mobile phone 100 attempts to initiate an ATTACH request or a TAU request in M cells and continuously receives an RRC Release during the attachment or tracking area update process. Then, the retry interval can be extended, and a second long-term retry timer can be started for each retry. For example, the second long-term retry timer is longRetryTimer2, and the timeout duration of longRetryTimer2 should be greater than the timeout duration of the second short-term retry timer shortRetryTimer2.

[0201] S607: Obtain the reference signal received power of the current cell, and increase a penalty value to the reference signal received power of the current cell to reduce the reference signal received power.

[0202] S608: Search for other cells whose reference signal received power is greater than that of the current cell, and clear the number of consecutive access failures.

[0203] S609: Initiate an attachment request or a tracking area update request in other cells.

[0204] Exemplarily, S607 to S609 can refer to the above S307 to S309 or S407 to S409, which will not be elaborated here.

[0205] S610: After waiting for the timer to time out in the current cell, re-initiate an attachment request or a tracking area update request.

[0206] In some embodiments, when, based on S606, it is determined that the number of consecutive access failures of the mobile phone 100 in the current cell is less than N2, continue to wait for the timer to time out in the current cell, and then re-initiate an ATTACH request or a TAU request in the current cell.

[0207] For example, when the number of consecutive access failures of the mobile phone 100 in the current cell is 7, which is less than the second short retry count threshold of 8 and less than 10, it can wait for the second short retry timer to expire, that is, wait for 10 s. During this period, the mobile phone 100 cannot initiate an ATTACH request or a TAU request again in the current cell. After waiting for 10 s, the mobile phone 100 can initiate an ATTACH request or a TAU request again in the current cell.

[0208] For another example, when the number of consecutive access failures of the mobile phone 100 in the current cell is 9, which is greater than the second short retry count threshold of 8 and less than 10, it can wait for the second long retry timer to expire, that is, wait for 15 min. During this period, the mobile phone 100 cannot initiate an ATTACH request or a TAU request again in the current cell. After waiting for 15 min, the mobile phone 100 can initiate an ATTACH request or a TAU request again in the current cell.

[0209] It can be understood that N2 is greater than the second short retry count threshold mentioned above.

[0210] Through the above communication method, for the situation where the mobile phone 100 fails to continuously initiate an ATTACH request or a TAU request during the process of initiating an ATTACH request or a TAU request and receiving an RRCRelease, that is, the situation of continuous network access failure, the mobile phone 100 can quickly initiate an ATTACH request or a TAU request again in a cell with better wireless signal and access the network. Instead of waiting for the timer T3411 or T3402 to expire before being able to initiate an ATTACH or TAU again, it saves the time for the mobile phone 100 to access the network and improves the network access efficiency of the mobile phone 100.

[0211] In some other embodiments, when the mobile phone 100 initiates an ATTACH request or a TAU request and the network has no response, that is, the T3410 timer expires or the T3430 timer expires, resulting in the failure of the mobile phone 100 to initiate an ATTACH request or a TAU request.

[0212] The following describes the communication method provided by the present application in combination with Embodiment 3, and the specific implementation process in the scenario where the mobile phone 100 fails to continuously initiate an ATTACH request or a TAU request due to the expiration of the T3410 timer or the T3430 timer.

[0213] Embodiment 3

[0214] Figure 7 According to the embodiment of the present application, a schematic flowchart of the implementation process of a communication method in a scenario where the mobile phone 10 continuously fails to initiate an ATTACH request or a TAU request due to the expiration of the T3410 timer or the T3430 timer is shown.

[0215] The specific process includes:

[0216] S701: Initiate an attach request or a tracking area update request.

[0217] Exemplarily, this step S701 can refer to the relevant descriptions in the above step S301 and will not be elaborated here.

[0218] S702: Detect that the initiation of the attach request or the tracking area update request fails due to the timeout of the T3410 timer or the T3430 timer, and count the number of failures.

[0219] In some embodiments, the T3410 timer can be used to monitor the activities of the mobile phone 100 in the Radio Resource Control Connected (RRC_CONNECTED) state. The timeout duration of the T3430 timer can be 15s. If the mobile phone 100 does not perform any activities in the RRC_CONNECTED state, for example, the mobile phone 100 does not send or receive data continuously for 15s in the RRC_CONNECTED state, does not perform any control signaling interaction, etc., then the T3410 timer times out. The mobile communication system will determine that the mobile phone 100 is in the idle state and release all resources allocated to the mobile phone 100. The base station 01 sends an "RRCRelease", that is, a radio resource control connection release message, to the RRC layer. When the RRC layer receives the "RRC Release", it reports the situation to the NAS layer. Then the NAS layer interrupts the initiation of the ATTACH request, that is, the mobile phone 100 fails to initiate the ATTACH request, and a counter is used to count the number of failures of the mobile phone 100 to initiate the ATTACH request due to the timer timeout.

[0220] In some other embodiments, when the mobile phone 100 is in the TAU process, the T3430 timer can be used to monitor the activities of the mobile phone 100 in the RRC_CONNECTED state. The timeout duration of the T3410 timer can be 15s. If the mobile phone 100 does not perform any activities in the RRC_CONNECTED state, for example, the mobile phone 100 does not send or receive data continuously for 15s in the RRC_CONNECTED state, does not perform any control signaling interaction, etc., then the T3430 timer times out. The system will determine that the mobile phone 100 is in the idle state, and then release all resources allocated to the mobile phone 100. The base station 01 sends an "RRCRelease", that is, a radio resource control connection release message, to the RRC layer. When the RRC layer receives the "RRC Release", it reports the situation to the NAS layer. Then the NAS layer interrupts the initiation of the TAU request, that is, the mobile phone 100 fails to initiate the TAU request, and a counter is used to count the number of failures of the mobile phone 100 to initiate the TAU request due to the timer timeout.

[0221] It can be understood that the failure to initiate an ATTACH request or a TAU request due to the timeout of the timer indicates that the mobile phone 100 fails to access the network. Therefore, the number of failures caused by the timeout of the timer when initiating an ATTACH request or a TAU request is counted, that is, the number of failures of the mobile phone 100 to access the network is counted. Based on this, the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request currently due to the timeout of the timer can be obtained through the counting result, that is, the total number of failures of the mobile phone 100 to access the network currently.

[0222] It can be understood that in the embodiments of the present application, taking the timeout duration of the T3410 timer and the T3430 timer as 15s is only an exemplary illustration. In some other embodiments, the timeout duration of the T3410 timer and the T3430 timer can also be 20s, etc., which is not limited herein.

[0223] S703: Determine whether the total number of failures caused by the timeout of the timer is less than the third preset number threshold N3.

[0224] If the judgment result is yes, go to S705 and do not start the retry timer.

[0225] If the judgment result is no, go to S706, start the third retry timer, and clear the total number of failures caused by the timeout of the timer.

[0226] In some embodiments, when the mobile phone 100 executes the above step S702, it can determine the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request due to the timeout of T3410 during ATTACH and the timeout of T3430 during TAU, and then can judge whether the total number of failures is less than the third preset number threshold N3. For example, N3 = 10, N3 ≥ 5.

[0227] S704: Do not start the retry timer.

[0228] In some embodiments, when it is determined based on S704 that the number of consecutive failures is less than the third preset number threshold N3, for example, N3 = 10, then the retry timer is not started. The mobile phone 100 can directly re-initiate an ATTACH request or a TAU request.

[0229] S705: Start the third retry timer, and clear the total number of failures caused by the timeout of the timer.

[0230] In some embodiments, when it is determined based on S703 that the number of consecutive access failures is greater than or equal to the third preset number threshold N3, for example, N3 = 10, the third retry timer can be started based on S705. For example, the timeout duration of the third retry timer can be 16 minutes. In addition, the total number of failures caused by timer timeout is cleared.

[0231] It can be understood that in the embodiments of the present application, taking the duration of the third retry timer as 16 minutes is only an exemplary illustration. The third long - time retry number threshold can also be any duration less than or greater than 16 minutes, which is not limited herein.

[0232] It can be understood that in some other embodiments, the duration of the third retry timer can be the same as the timeout duration of the first short - time retry timer and the second short - time retry timer, or the same as the timeout duration of the first long - time retry timer and the second long - time retry timer, which is not limited herein.

[0233] S706: Wait for the third retry timer to timeout.

[0234] In some embodiments, after starting the third retry timer based on S705, it is possible to wait for the third retry timer to timeout. For example, if the timeout duration of the third retry timer is 16 minutes, then the mobile phone 100 needs to wait for 16 minutes before it can re - initiate an ATTACH request or a TAU request.

[0235] S707: Re - initiate an attach request or a tracking area update request.

[0236] In some embodiments, when it is determined based on S704 that the total number of consecutive failures is less than the third preset number threshold N3, for example, N3 = 10, the retry timer may not be started, and the mobile phone 100 directly re - initiates an ATTACH request or a TAU request.

[0237] In some other embodiments, when waiting for the third retry timer to timeout based on S707, the mobile phone 100 can re - initiate an ATTACH request or a TAU request.

[0238] Through the above - mentioned communication method, for the case where the initiation of an ATTACH request or a TAU request fails due to the timeout of the T3410 timer or the T3430 timer, that is, the case of network access failure, the mobile phone 100 can quickly re - initiate an ATTACH request or a TAU request in a cell with better wireless signal and access the network. Instead of waiting for the timeout of the timer T3411 or T3402 before re - initiating an ATTACH request or a TAU request, the time for the mobile phone 100 to access the network is saved, and the network access efficiency of the mobile phone 100 is improved.

[0239] In some other embodiments, when the NAS layer of the mobile phone 100 receives the "ATTACH REJECT" message of attachment rejection sent by the MME or the "TAU REJECT" message of tracking area update rejection, the mobile phone 100 fails to initiate an ATTACH request or a TAU request. Based on this, the embodiments of the present application provide a communication method in the scenario where the ATTACH request or the TAU request fails due to attachment rejection or tracking area update rejection.

[0240] The following describes the communication method provided by the present application in combination with Embodiment 4, and specifically describes the implementation process in the scenario where the mobile phone 100 continuously fails to initiate an ATTACH request or a TAU request due to attachment request rejection or tracking area update request rejection.

[0241] Embodiment 4

[0242] Figure 8 Fig. shows a schematic flowchart of an implementation process of a communication method in the scenario where the mobile phone 100 fails to initiate an ATTACH request or a TAU request due to attachment request rejection or tracking area update request rejection.

[0243] The specific process includes:

[0244] S801: Initiate an attachment request or a tracking area update request.

[0245] Exemplarily, the specific execution process of this step S801 may refer to the above S301 and will not be elaborated here.

[0246] S802: Detect that the attachment or the tracking area update fails due to attachment request rejection or tracking area update request rejection, and count the number of failures.

[0247] In some embodiments, when the NAS layer of the mobile phone 100 receives the "ATTACH REJECT" message of attachment rejection sent by the MME or the "TAU REJECT" message of tracking area update rejection during the process of initiating an ATTACH request or a TAU request, it may indicate that the mobile phone 100 fails to initiate an ATTACH request or a TAU request, and a counter is used to count the number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request due to underlying reasons.

[0248] It can be understood that the failure to initiate an ATTACH request or a TAU request due to a rejected attach request or a rejected tracking area update request indicates that the mobile phone 100 fails to access the network. Therefore, the number of failures resulting from a rejected attach request or a rejected tracking area update request that causes the failure to initiate an ATTACH request or a TAU request is counted, that is, the number of failures in accessing the network is counted. Based on this, the total number of failures in the current ATTACH request or TAU request initiated by the mobile phone 100 can be obtained from the counting result, that is, the total number of failures in the current access of the mobile phone 100 to the network, which can also be referred to as the number of consecutive access failures.

[0249] It can be understood that when the network cannot accept an attach request "ATTACH REQUEST" or a tracking area update request "TAU REQUEST", the MME should send "ATTACH REJECT" or "TAU REJECT" to the NAS layer of the UE. Among them, "ATTACH REJECT" or "TAU REJECT" may include appropriate mobility management (eps mobile management, EMM) cause values. For example, the EMM cause value may be abnormal situations such as #19 "ESM failure", #22, #25, #31, etc. specified in clause 5.5.1.2.6 of the communication terms, which are not limited herein.

[0250] S803: Determine whether the total number of failures is greater than or equal to the fourth short-term retry count threshold.

[0251] If the judgment result is yes, go to S805, start the fourth long-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0252] If the judgment result is no, go to S804, start the fourth short-term retry timer, and increment the number of consecutive access failures in the current cell by 1.

[0253] In some embodiments, when the mobile phone 100 executes the above step S802, the total number of failures in the mobile phone 100 resulting from a rejected ATTACH request or a rejected TAU request that causes the failure to initiate an ATTACH request or a TAU request can be determined. Furthermore, it can be determined whether the total number of failures in the mobile phone 100 to initiate an ATTACH request or a TAU request is greater than or equal to the fourth short-term retry count threshold. For example, the fourth short-term retry count threshold can be set to 9 times.

[0254] It can be understood that taking the fourth short-term retry count threshold as 9 times in the embodiments of the present application is only an exemplary illustration, and the fourth short-term retry count threshold can also be any other count threshold less than or greater than 9, which is not limited herein.

[0255] S804: Start the fourth short-term retry timer, and increment the consecutive access failure count in the current cell by 1.

[0256] In some embodiments, when, based on S803, it is determined that the total number of failures of the mobile phone 100 to initiate an ATTACH request or a TAU request due to the ATTACH request being rejected or the TAU request being rejected is less than the fourth short-term retry count threshold, the fourth short-term retry timer can be started, and the consecutive access failure count in the current cell of the mobile phone 100 due to the ATTACH being rejected or the TAU being rejected is incremented by 1. For example, the duration of the fourth short-term retry timer can be 11 s.

[0257] It can be understood that taking the duration of the fourth short-term retry timer as 11 s in the embodiments of the present application is only an exemplary illustration, and the fourth short-term retry count threshold can also be any other duration less than or greater than 1 h, which is not limited herein.

[0258] S805: Start the fourth long-term retry timer, and increment the consecutive access failure count in the current cell by 1.

[0259] In some embodiments, when, based on S803, it is determined that the total number of failures of the mobile phone 100 to ATTACH or TAU due to the ATTACH request being rejected or the TAU request being rejected is greater than or equal to the fourth short-term retry count threshold, the fourth long-term retry timer can be started, and the consecutive access failure count in the current cell of the mobile phone 100 due to the ATTACH being rejected or the TAU being rejected is incremented by 1. For example, the duration of the fourth long-term retry timer can be 17 min.

[0260] It can be understood that taking the duration of the fourth long-term retry timer as 17 min in the embodiments of the present application is only an exemplary illustration, and the fourth long-term retry count threshold can also be any duration less than or greater than 17 min, which is not limited herein.

[0261] It can be understood that the duration of the fourth long-term retry timer is greater than the duration of the fourth short-term retry timer.

[0262] It can be understood that in some other embodiments, the duration of the fourth short-term retry timer can be the same as the duration of the first short-term retry timer and the second short-term retry timer, and the duration of the fourth long-term retry timer can be the same as the duration of the first long-term retry timer and the second long-term retry timer, which is not limited herein.

[0263] S806: Determine whether the consecutive access failure count in the current cell is greater than or equal to the fourth preset count threshold N4.

[0264] If the judgment result is yes, go to S807, obtain the reference signal receiving power of the current cell, and increase a penalty value to the reference signal receiving power of the current cell to reduce the reference signal receiving power of the current cell.

[0265] If the judgment result is no, go to S810. After the timer in the current cell times out, initiate an attach request or a tracking area update request again.

[0266] In some embodiments, when the mobile phone 100 executes the above-mentioned step S802, the total number of failures of the mobile phone 100 to continuously initiate an attach request or a tau request due to attach rejection or tau rejection can be determined, that is, the number of consecutive access failures of the mobile phone 100 in the current cell. Furthermore, it can be determined whether the number of consecutive access failures of the mobile phone 100 in the current cell is greater than or equal to a fourth preset number threshold N4. For example, N4 = 10, N4 ≥ 5.

[0267] It can be understood that the fourth preset number threshold N4 can be greater than the above-mentioned fourth retry number threshold.

[0268] It can be understood that the above-mentioned fourth short retry number can be shortRetry4. If shortRetry4 = M * N, it can be stated that the mobile phone 100 attempts to initiate an attach request or a tau request in M cells and all result in consecutive attach rejections or tau rejections. Then, the retry interval can be lengthened, and a fourth long retry timer can be started for each retry. For example, the fourth long retry timer is longRetryTimer4, and the timeout duration of longRetryTimer4 should be greater than the timeout duration of the fourth short retry timer shortRetryTimer4.

[0269] S807: Obtain the reference signal receiving power of the current cell, and increase a penalty value to the reference signal receiving power of the current cell to reduce the reference signal receiving power.

[0270] S808: Search for other cells whose reference signal receiving power is greater than that of the current cell, and clear the number of consecutive access failures.

[0271] S809: Initiate an attach request or a tracking area update request in other cells.

[0272] Exemplarily, S807 to S809 can refer to the above-mentioned S307 to S309, S407 to S409, and will not be elaborated here.

[0273] S810: After the timer in the current cell times out, initiate an attach request or a tracking area update request again.

[0274] In some embodiments, when it is determined based on S806 that the number of consecutive access failures of the mobile phone 100 in the current cell is less than the fourth preset number threshold N4, for example, N4 = 10 and N4 ≥ 5, then continue to wait in the current cell until the timer times out, and then re-initiate an ATTACH request or a TAU request in the current cell.

[0275] For example, when the number of consecutive failures of the mobile phone 100 in the current cell is 8, which is less than the fourth short-term retry number threshold 9 and less than 11, it is possible to wait for the fourth short-term retry timer to time out, that is, wait for 11 s. During this period, the mobile phone 100 cannot re-initiate an ATTACH request or a TAU request in the current cell. After waiting for 11 s, the mobile phone 100 can re-initiate an ATTACH request or a TAU request in the current cell.

[0276] Another example is when the number of consecutive failures of the mobile phone 100 in the current cell is 10, which is greater than the fourth short-term retry number threshold 9 and less than 11. It is possible to wait for the fourth long-term retry timer to time out, that is, wait for 17 min. During this period, the mobile phone 100 cannot re-initiate an ATTACH request or a TAU request in the current cell. After waiting for 17 min, the mobile phone 100 can re-initiate an ATTACH request or a TAU request in the current cell.

[0277] Through the above communication method, for the situation where the continuous initiation of an ATTACH request or a TAU request fails due to the rejection of the ATTACH request or the TAU request, that is, the continuous access to the network fails, the mobile phone 100 can quickly re-initiate an ATTACH request or a TAU request in a cell with better wireless signal and access the network. Instead of waiting for the timer T3411 or T3402 to time out before re-initiating an ATTACH request or a TAU request, it saves the time for the mobile phone 100 to access the network and improves the network access efficiency of the mobile phone 100.

[0278] In some other embodiments, when the mobile phone 100 fails in an ATTACH or TAU during the process of initiating an ATTACH request or a TAU request due to various reasons, such as including the reasons Figures 3 to 8 that cause the mobile phone 100 to fail in initiating an ATTACH request or a TAU request as described above, based on this, the embodiments of the present application provide a communication method in the scenario where the mobile phone 100 fails in initiating an ATTACH request or a TAU request due to multiple reasons.

[0279] The following describes the communication method provided by the present application in combination with Embodiment 5, and the specific implementation process in the scenario where the mobile phone 100 continuously fails in initiating an ATTACH request or a TAU request due to multiple reasons.

[0280] Embodiment 5

[0281] Figure 9 The figure shows a flowchart of an implementation of a communication method in a scenario where a mobile phone 100 fails to initiate an ATTACH request or a TAU request due to various reasons.

[0282] The specific process includes:

[0283] S901: Initiate an attach request or a tracking area update request.

[0284] Exemplarily, this step S901 can refer to the relevant description of step S301 above and will not be elaborated here.

[0285] S902: Detect that the initiation of the attach request or the tracking area update request fails due to underlying reasons.

[0286] Exemplarily, this step S902 can refer to the relevant description of step S402 above and will not be elaborated here.

[0287] S903: Detect that the initiation of the attach request or the tracking area update request fails due to the early release of the radio resource control connection.

[0288] Exemplarily, this step S903 can refer to the relevant description of step S602 above and will not be elaborated here.

[0289] S904: Detect that the initiation of the attach request or the tracking area update request fails due to the timeout of the T3410 timer or the T3430 timer.

[0290] Exemplarily, this step S904 can refer to the relevant description of step S702 above and will not be elaborated here.

[0291] S905: Detect that the attach rejection request or the tracking area update rejection request causes the initiation of the attach request or the tracking area update request to fail.

[0292] Exemplarily, this step S905 can refer to the relevant description of step S802 above and will not be elaborated here.

[0293] S906: Count the number of failures in initiating the attach request or the tracking area update request.

[0294] In some embodiments, count the number of times the reasons in S902 to S905 cause the mobile phone 100 to fail to initiate an ATTACH request or a TAU request. For each failure, the count value is incremented by 1, that is, the number of failures + 1.

[0295] It can be understood that the failure to initiate an ATTACH request or a TAU request for various reasons indicates that the mobile phone 100 fails to access the network. Therefore, the number of failures in initiating an ATTACH request or a TAU request for various reasons is counted, that is, the number of failures in accessing the network is counted. Based on this, the total number of failures in the current ATTACH request or TAU request initiated by the mobile phone 100 can be obtained through the counting result, that is, the total number of failures in the current network access failure of the mobile phone 100.

[0296] S907: Determine whether the total number of failures is greater than or equal to the fifth preset number threshold N5.

[0297] If the judgment result is yes, go to S908 to disable the current mobile network.

[0298] If the judgment result is no, go to S909 to start the fifth retry timer and clear the total number of failures.

[0299] In some embodiments, the number of failures in the mobile phone 100 initiating an ATTACH request or a TAU request due to the reasons in S902 to S905 is counted, and it is determined whether the total number of failures is less than the fifth preset number threshold N5. For example, N5 = 20, any value where N5 ≥ 5.

[0300] It can be understood that the fifth preset number threshold N5 in S907 is greater than the preset number thresholds in S306, S406, S506, S604, S706, and S806 above.

[0301] S908: Disable the current mobile network.

[0302] In some embodiments, when it is determined based on S907 that the total number of failures is greater than or equal to N5 times, the public land mobile network (PLMN) and long term evolution (LTE), that is, the 4G network, etc., currently used by the mobile phone 100 can be disabled.

[0303] It can be understood that the PLMN is a network established and operated by an approved operator for the purpose of providing land mobile communication services to users. This network must be interconnected with the public switched telephone network (PSTN) to form a communication network in the entire region or on a larger scale. For example, the PLMN of China Mobile can be 46000, the PLMN of China Unicom can be 46001, and the PLMN of China Telecom can be 46011.

[0304] It can be understood that when the current mobile network is disabled, the terminal device can still connect to the network through at least one of the following: connect to the network through the second public land mobile network or the second network mode of the current cell, which is not limited herein.

[0305] S909: Start the fifth retry timer and clear the total number of failures.

[0306] In some embodiments, when it is determined based on S907 that the total number of failures is less than N5 times, for example, N5 = 20 and the total number of failures is less than 20, the mobile phone 100 can start the fifth retry timer. For example, the timeout duration of the fifth retry timer can be 30 minutes. In addition, clear the total number of failures.

[0307] It can be understood that in the embodiments of the present application, taking the duration of the fifth retry timer as 30 minutes is only an exemplary illustration, and the fifth long retry duration threshold can also be any duration less than or greater than 30 minutes, which is not limited herein.

[0308] It can be understood that based on Figure 9 The shown communication method is applied to the scenario where the mobile phone 100 fails to initiate an ATTACH request or a TAU request due to multiple reasons. Therefore, the duration of the fifth retry timer can be greater than the timeout durations of the first long retry timer, the second long retry timer, the third retry timer, and the fourth long timer, which is not limited herein.

[0309] S910: After waiting for the fifth retry timer to time out, re-initiate an attach request or a tracking area update request.

[0310] In some embodiments, after starting the fifth retry timer in S909, wait for the fifth retry timer to time out. For example, if the timeout duration of the fifth retry timer is 30 minutes, the mobile phone 100 needs to wait for 30 minutes before it can re-initiate an ATTACH request or a TAU request in the current cell.

[0311] Through the above communication method, for the scenario where the mobile phone 100 fails to initiate an ATTACH request or a TAU request due to various reasons, a unified failure counting mechanism can be set. When the total number of times of failing to initiate an ATTACH request or a TAU request due to various reasons reaches the preset number Nfail, the current PLMN and LTE are disabled. And based on this, the mobile phone 100 can quickly re-initiate an ATTACH request or a TAU request and access the network, without having to wait for the timer T3411 or T3402 to time out before re-initiating an ATTACH request or a TAU request, saving the time for the mobile phone 100 to access the network and improving the network access efficiency of the mobile phone 100.

[0312] Based on the communication method provided in the embodiments of the present application, by flexibly customizing the timer duration and retry count limit adopted for all ATTACH or TAU failure scenarios that require starting timers T3411 and T3402, it is ensured that the UE can promptly resume mobile services on available cells.

[0313] In addition, for different reasons leading to ATTACH or TAU failures, on the basis of flexibly customizing the retry count and retry duration, by means such as setting penalty values, the UE can exit the retry of invalid cells earlier, increasing the chance of successful retry. Moreover, for unified retry failure counting in various mixed scenarios causing ATTACH or TAU failures, it can be ensured that the UE can be promptly suppressed under multiple failure scenarios and prevent excessive attempts from affecting the power consumption of the UE.

[0314] It can be understood that the communication method provided in the embodiments of the present application can also be applied in 4G networks or 5G networks, which is not limited herein.

[0315] Figure 10 According to the embodiments of the present application, a schematic structural diagram of a terminal device is shown. It can be understood that the terminal device may include the aforementioned mobile phone 100.

[0316] As Figure 10 shown, the terminal device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. Among them, the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, etc.

[0317] It can be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the terminal device. In other embodiments of the present application, the terminal device may include more or fewer components than shown in the figures, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0318] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors. The controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

[0319] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store the instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be directly called from the above memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system. In some embodiments, the processor 110 may be used to implement the communication method provided in the embodiments of the present application.

[0320] The wireless communication function of the terminal device can be implemented by antenna 1, antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor, etc.

[0321] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the terminal device can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0322] The mobile communication module 150 can provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to terminal devices. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through antenna 1, and perform processing such as filtering and amplification on the received electromagnetic waves, and then transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves through antenna 1 and radiate it out. In some embodiments, at least some functional modules of the mobile communication module 150 can be disposed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 can be disposed in the same device.

[0323] The modulation and demodulation processor can include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Subsequently, the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to speaker 170A, receiver 170B, etc.), or displays an image or video through the display screen 194. In some embodiments, the modulation and demodulation processor can be an independent device. In other embodiments, the modulation and demodulation processor can be independent of the processor 110 and disposed in the same device as the mobile communication module 150 or other functional modules.

[0324] The wireless communication module 160 may provide solutions for wireless communications applied to a terminal device, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSSs), frequency modulation (FM), near field communication (NFC), infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 may also receive signals to be sent from the processor 110, perform frequency modulation and amplification on them, and convert them into electromagnetic waves through the antenna 2 for radiation.

[0325] In some embodiments, antenna 1 of the terminal device is coupled to the mobile communication module 150, and antenna 2 is coupled to the wireless communication module 160, enabling the terminal device to communicate with the network and other devices through wireless communication technologies. The above wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The above GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Beidou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0326] The terminal device realizes the display function through the GPU, the display screen 194, and the application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering.

[0327] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device. The external memory card communicates with the processor 110 through the external memory interface 120 to achieve the data storage function. For example, files such as music and videos are saved in the external memory card.

[0328] The internal memory 121 can be used to store computer-executable program code, which includes instructions. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.). The data storage area can store data created during the use of the terminal device (such as audio data, phone book, etc.). In addition, the internal memory 121 can include a high-speed random access memory and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the terminal device by running the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor.

[0329] The SIM card interface 195 is used to connect to a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation from the terminal device. The terminal device can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the above multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The terminal device interacts with the network through the SIM card to implement functions such as calls and data communication. In some embodiments, the terminal device uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the terminal device and cannot be separated from the terminal device.

[0330] The embodiments of the present application also provide a computer program product for implementing the communication methods provided in the above embodiments.

[0331] The embodiments of the mechanism disclosed in the present application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as computer program modules or module codes executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memories and / or storage elements), at least one input device, and at least one output device.

[0332] A computer program module or module code can be applied to input instructions to perform the various functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0333] The module code can be implemented in a high-level modular language or an object-oriented programming language to communicate with the processing system. When needed, the module code can also be implemented in assembly language or machine language. In fact, the mechanisms described in this application are not limited to the scope of any particular programming language. In any case, the language can be a compiled language or an interpreted language.

[0334] In some cases, the disclosed embodiments can be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments can also be implemented as instructions carried or stored on one or more transient or non-transient machine-readable (e.g., computer-readable) storage media, which can be read and executed by one or more processors. For example, the instructions can be distributed via a network or via other computer-readable media. Thus, a machine-readable medium can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to, a floppy disk, a compact disc, a CD-ROM, a magneto-optical disk, a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic or optical card, a flash memory, or a tangible machine-readable memory for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) in electrical, optical, acoustic, or other forms via the Internet. Thus, a machine-readable medium includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0335] References in the specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one exemplary implementation or technique disclosed in embodiments of the present application. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment.

[0336] The disclosure of embodiments of the present application also relates to an apparatus for performing operations in the text. The apparatus may be specifically constructed for the required purpose or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer-readable medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of medium suitable for storing electronic instructions, and each may be coupled to a computer system bus. Further, the computers referred to in the specification may include a single processor or may be architectures involving multiple processors for increased computing power.

[0337] In addition, the language used in this specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the disclosed subject matter. Accordingly, the disclosure of embodiments of the present application is intended to illustrate rather than limit the scope of the concepts discussed herein.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: Detecting that the number of failures of the terminal device to establish a network connection in a first cell is greater than a first number threshold, where the terminal device currently has a first reference signal receiving power; Reducing the first reference signal receiving power of the terminal device to a second reference signal receiving power, and the second reference signal receiving power satisfies the first cell handover condition; Establishing a network connection through a second cell, where a third reference signal receiving power of the second cell is greater than the second reference signal receiving power.

2. The method according to claim 1, wherein The first cell handover condition includes: There is at least one cell whose reference signal receiving power is greater than the second reference signal receiving power, and the at least one cell does not include the first cell.

3. The method according to claim 2, characterized in that It further includes: Corresponding to detecting that the number of failures of the terminal device to establish a network connection in the first cell is less than a second number threshold, starting a first retry timer, where the second number threshold is less than the first number threshold; Corresponding to detecting that the number of failures of the terminal device to establish a network connection in the first cell is greater than the second number threshold and less than the first number threshold, starting a second retry timer, where the timeout duration of the second retry timer is greater than the timeout duration of the first retry timer.

4. The method according to claim 3, characterized in that, It further includes: Corresponding to the second reference signal receiving power not satisfying the first cell handover condition, obtaining the reason for the failure of the terminal device to establish a network connection in the first cell; Determining a communication strategy based on the number of failures of the terminal device to establish a network connection in the first cell.

5. The method according to claim 4, characterized in that, The determining a communication strategy based on the reason for the failure of the terminal device to establish a network connection in the first cell includes: Detecting that the number of failures of the terminal device to establish a network connection in the first cell is less than a third number threshold and greater than the first number threshold, starting a third retry timer; Wherein, the timeout duration of the third retry timer is greater than the timeout duration of the second retry timer.

6. The method according to claim 4, wherein The determining a communication strategy based on the reason for the failure of the terminal device to establish a network connection in the first cell further includes: Detecting that the number of failures of the terminal device to establish a network connection in the first cell is greater than the third number threshold, the terminal device stops establishing a network connection based on the current first public land mobile network or the first network mode, and The terminal device establishes a network connection through at least one of the following: Establishing a network connection through a second public land mobile network or a second network mode of the first cell; Establishing a network connection through a second network mode of the first cell; Establishing a network connection through a third cell.

7. The method according to claim 1, wherein The failure of the network connection includes a failure to send an attachment request or a failure to initiate a tracking area update request; The reason for the failure of the terminal device to establish a network connection can be at least one of the following reasons: Underlying reasons, where the underlying reasons include poor radio signals of the cell and timeout of timer T300; During the process of the terminal device establishing a network connection, the terminal device detects the release of a radio resource control connection, where the radio resource control connection is the connection between the terminal device and the base station; Timer T3410 times out or timer T3430 times out; The attachment request initiated by the terminal device is rejected or the tracking area update request is rejected.

8. A terminal device, characterized in that, Comprising: A processor and a memory, the memory including physical memory and external memory, for storing instructions executed by one or more processors of the terminal device; And, A processor, for executing the instructions to enable the terminal device to implement the communication method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when run by the terminal device, enables the terminal device to implement the communication method according to any one of claims 1 to 7.

10. A computer program product, characterized in that, Comprising a computer program / instructions, which, when the computer program product runs on the terminal device, enables the terminal device to implement the communication method according to any one of claims 1 to 7.

Images