Location updating method and device, chip system and storage medium

Abstract

The embodiment of the invention provides a position updating method and device, a chip system and a storage medium. According to the method, the third timer is actively closed and the position updating process is re-initiated when the condition that the preset condition is met is identified in the scene that the position updating process fails due to the fact that the RRC connection is not established, so that the situation that the service of the user equipment is abnormal due to long-time waiting of the user equipment can be avoided. Therefore, the user equipment with the abnormal position updating process is quickly recovered to be normal under the condition that the burden is not increased on the network side basically, so that the user equipment can normally receive paging.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method, device, chip system, and storage medium for location update. Background Art

[0002] In mobile communication, the network side needs to identify and track the location information of the user equipment (UE), and then implement mobility management of the UE based on the location information. Therefore, when the location of the UE changes, a corresponding process is required to notify the network side for location update. Otherwise, the network side will not be able to obtain the correct location of the UE, resulting in paging failure.

[0003] However, currently, during the location update process, due to some exceptions, the location update request initiated by the UE may not reach the network side, that is, the location update request fails to be sent. Or, the location update request initiated by the UE is not responded to by the network side. Based on the current communication standard protocol, in this case, the UE will start a timer and can only initiate a location update request again after the timer times out. This causes the UE to be unable to perform services during the timing period corresponding to the timer, affecting user experience. Summary of the Invention

[0004] To solve the above technical problems, embodiments of this application provide a method, device, chip system, and storage medium for location update, aiming to enable a user equipment with an abnormal location update process to quickly return to normal so that the user equipment can normally receive paging.

[0005] In a first aspect, an embodiment of this application provides a method for location update. The method is applied to a user equipment and includes: when the user equipment changes from a first cell it is camped on to a second cell, triggering a location update process and starting a first timer and a second timer; where the current radio resource control (RRC) state of the user equipment is the idle state, the duration corresponding to the second timer is greater than the duration corresponding to the first timer, the duration corresponding to the first timer is the duration for establishing an RRC connection between the user equipment and the core network through random access, the duration corresponding to the second timer is the duration for performing the location update process, and the location update process is implemented based on the RRC connection; within the duration corresponding to the first timer, if the RRC connection is not successfully established, when the first timer times out, closing the second timer and starting a third timer; where the duration corresponding to the third timer is the duration during which the user equipment cannot perform the location update process since the second timer is closed; within the duration corresponding to the third timer, when it is recognized that a preset condition is met, closing the third timer in advance, re-triggering the location update process, and starting the first timer and the second timer.

[0006] Among them, the user equipment includes, for example, mobile phones, smart watches, etc.

[0007] Among them, the network modes corresponding to the first cell and the second cell may be the same or different.

[0008] Among them, the network mode may be one or more of 2G, 3G, 4G, 5G, and future network modes.

[0009] Among them, the first timer is the timer corresponding to the RRC establishment process, such as T300.

[0010] Among them, the second timer and the third timer are related to the network mode of the second cell.

[0011] Exemplarily, when the second cell is a 4G network cell, the second timer is, for example, T3430, and the third timer is, for example, T3411.

[0012] Exemplarily, when the second cell is a 5G network cell, the second timer is, for example, T3510, and the third timer is, for example, T3511.

[0013] According to the standard protocol, the original intention of starting the third timer is to prevent the user equipment from frequently initiating a location update process (including sending a location update request to the network side) to the network side (i.e., the network side device), thereby increasing the burden on the network side. Moreover, the network side may even think that the network is under attack. However, in the case where the RRC connection is not established and thus the location update request is not sent to the network side at all, resulting in an abnormal location update process, the network side actually does not know that the location update action has occurred. Therefore, it is not necessary for the user equipment to wait for the third timer to time out and then re-initiate the location update process. Therefore, in this aspect, within the duration corresponding to the third timer, when the user equipment recognizes that the preset conditions are met, it can actively close the third timer in advance and re-initiate the location update process, thereby avoiding the user equipment waiting for a long time and causing abnormal services of the user equipment.

[0014] Thus, without adding a burden to the network side basically, the user equipment with an abnormal location update process can be quickly restored to normal so that the user equipment can normally receive paging.

[0015] According to the first aspect, within the duration corresponding to the third timer, when it is recognized that the preset conditions are met, closing the third timer in advance includes: within the duration corresponding to the third timer, when it is recognized that the signal quality of the second cell becomes better or the user equipment camps on the third cell, closing the third timer in advance.

[0016] When the RRC connection is not established and the location update request fails to reach the network side, there is no need for the user equipment to wait for the third timer to time out before initiating the location update process. Therefore, in this scenario, when it is recognized that the signal quality of the currently camped cell improves or a new cell is accessed, the user equipment can directly re-trigger the location update process, thus avoiding long waiting times that may cause abnormal services on the user equipment.

[0017] According to the first aspect, or any implementation manner of the above first aspect, the method further includes: when the RRC connection is not successfully established, resulting in the failure of the location update process, the currently triggered location update process is not accumulated into the total number of trigger times corresponding to the location update process.

[0018] Thus, in a scenario where the RRC connection is not established, resulting in the failure of the location update process, such as when the corresponding location update request is not sent to the network side, the user equipment does not accumulate the currently triggered location update process into the total number of trigger times corresponding to the location update process, thereby avoiding the total number of trigger times quickly reaching the preset trigger times specified in the standard protocol, and then starting the fourth timer, which causes the user equipment to be unable to perform the location update process within the duration corresponding to the fourth timer, resulting in the user equipment being unable to return to normal for a long time and thus unable to receive paging normally.

[0019] That is, based on the implementation manner provided in this aspect, it is possible to achieve not imposing a burden on the network and not being rejected by the network.

[0020] According to the first aspect, or any implementation manner of the above first aspect, the method further includes: within the duration corresponding to the third timer, when no preset condition is recognized, after the third timer times out, re-trigger the location update process and start the first timer and the second timer.

[0021] Thus, when no preset condition is recognized within the duration corresponding to the third timer, the location update process can be re-triggered after the third timer times out according to the current standard protocol, ensuring that the location update process can proceed normally.

[0022] According to the first aspect, or any implementation manner of the above first aspect, during the process of re-triggering the location update process, the method further includes: when the RRC connection is successfully established and the re-triggered location update process fails, the currently triggered location update process is accumulated into the total number of trigger times corresponding to the location update process; when the total number of trigger times is greater than the preset trigger times, start the fourth timer, and the duration corresponding to the fourth timer is greater than the durations corresponding to the first timer, the second timer, and the third timer respectively; wherein, within the duration corresponding to the fourth timer, the user equipment cannot perform the location update process.

[0023] Thus, when the RRC connection is not established, resulting in the failure of the location update process, such as in a scenario where the corresponding request for location update is not sent to the network side, the user equipment does not accumulate the currently triggered location update process into the total number of triggered times corresponding to the location update process. For the case where the RRC connection is successfully established but the location update process still fails, that is, when the corresponding request is actually sent out, the number of times is accumulated, so as to avoid the total number of triggers quickly reaching the preset trigger times specified by the standard protocol, and then starting the fourth timer, which causes the user equipment to be unable to perform the location update process within the duration corresponding to the fourth timer, making the user equipment unable to return to normal for a long time, and then resulting in the user equipment being unable to receive paging normally.

[0024] According to the first aspect, or any one of the implementation manners of the above first aspect, the network systems corresponding to the first cell and the second cell are different; or, the network systems corresponding to the first cell and the second cell are the same.

[0025] Exemplarily, the network systems of the first cell and the second cell can be any one of 2G, 3G, 4G, 5G, and future network systems.

[0026] Exemplarily, the first cell can be any one of 2G, 3G, 4G, 5G, and future network systems, and the network system of the second cell can be any one of the network systems other than the first cell.

[0027] According to the first aspect, or any one of the implementation manners of the above first aspect, when the network system corresponding to the second cell is a 4G network, the location update process is implemented through a Tracking Area Update (TAU), the first timer is a T300 timer, the second timer is a T3430 timer, and the third timer is a T3411 timer.

[0028] According to the first aspect, or any one of the implementation manners of the above first aspect, when the network system corresponding to the second cell is a 5G network, the location update process is implemented through a registration process of type Mobile Registration Update (MRU), the first timer is a T300 timer, the second timer is a T3510 timer, and the third timer is a T3511 timer.

[0029] According to the first aspect, or any one of the implementation manners of the above first aspect, when the network system corresponding to the second cell is a 4G network, the fourth timer is a T3402 timer; or, when the network system corresponding to the second cell is a 5G network, the fourth timer is a T3502 timer.

[0030] According to the first aspect, or any implementation manner of the above first aspect, it is recognized that the preset conditions are met, including: when the user equipment is moving rapidly, it is recognized that the preset conditions are met.

[0031] Among them, scenarios of rapid movement are, for example, scenarios that occur when taking transportation means such as high-speed trains and airplanes.

[0032] Since when the user equipment is in a scenario of rapid movement, the cell where the user equipment is located is changing rapidly. Therefore, when there is a problem in the original cell, resulting in the failure of the location update process, the new cell may not have this problem. Thus, for such a scenario, instead of waiting for the third timer to time out and then re-initiate the location update process according to the protocol, when it is recognized that the cell has changed, the third timer is directly turned off, and the location update process is triggered, so that the user equipment can quickly return to normal, and thus ensure normal paging.

[0033] According to the first aspect, or any implementation manner of the above first aspect, when the user equipment changes from the first cell where it is camped to the second cell where it is camped, triggering the location update process includes: when the user equipment camps on the second cell in a redirected manner from the first cell where it is camped, triggering the location update process; or when the user equipment camps on the second cell in a reselection manner from the first cell where it is camped, triggering the location update process.

[0034] In a second aspect, an embodiment of the present application provides a user equipment. The user equipment includes: a memory and a processor, the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the user equipment is caused to execute the instructions of the method in the first aspect or any possible implementation manner of the first aspect.

[0035] In a third aspect, an embodiment of the present application provides a computer-readable medium for storing a computer program, and the computer program includes instructions for executing the method in the first aspect or any possible implementation manner of the first aspect.

[0036] In a fourth aspect, an embodiment of the present application provides a computer program, and the computer program includes instructions for executing the method in the first aspect or any possible implementation manner of the first aspect.

[0037] In a fifth aspect, an embodiment of the present application provides a chip system, and the chip system includes a processor. The processor is used to support the terminal device to implement the instructions of the method in the above first aspect or any possible implementation manner of the first aspect.

[0038] According to the fifth aspect, the processor includes a modem.

[0039] Accordingly, the processor is used to support the user equipment to implement the instructions of the method in the above-mentioned first aspect or any possible implementation manner of the first aspect, specifically including:

[0040] The modem is used to support the user equipment to implement the instructions of the method in the above-mentioned first aspect or any possible implementation manner of the first aspect.

[0041] The fifth aspect and any implementation manner of the fifth aspect respectively correspond to the first aspect and any implementation manner of the first aspect. For the technical effects corresponding to the fifth aspect and any implementation manner of the fifth aspect, reference can be made to the technical effects corresponding to the first aspect and any implementation manner of the first aspect, which will not be elaborated here. Description of the Drawings

[0042] Figure 1 It is a schematic diagram of a scenario where the position change of the UE occurs and triggers the location update process shown exemplarily;

[0043] Figure 2A and Figure 2B It is a schematic diagram of the process of the user equipment performing a location update with the network side under the 4G network shown exemplarily;

[0044] Figure 3 It is a schematic diagram of the process where the location update fails and causes service interruption under the 4G network shown exemplarily;

[0045] Figure 4 It is a schematic diagram of the process of a location update method for the 4G network provided by the embodiment of the present application shown exemplarily;

[0046] Figure 5 It is a schematic diagram of the process of another location update method for the 4G network provided by the embodiment of the present application shown exemplarily;

[0047] Figure 6A and Figure 6B It is a schematic diagram of the process of the user equipment performing a location update with the network side under the 5G network shown exemplarily;

[0048] Figure 7 It is a schematic diagram of the process where the location update fails and causes service interruption under the 5G network shown exemplarily;

[0049] Figure 8 It is a schematic diagram of the process of a location update method for the 5G network provided by the embodiment of the present application shown exemplarily;

[0050] Figure 9 It is a schematic diagram of the process of the location update method provided by the embodiment of the present application shown exemplarily;

[0051] Figure 10Schematic diagram of the hardware structure of an electronic device applicable to the location update method provided in the embodiments of the present application, shown exemplarily. Detailed implementation manners

[0052] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Apparently, the described embodiments are some but not all of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0053] The term "and / or" in this document is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0054] The terms "first", "second", etc. in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of the objects. For example, the first target object and the second target object are used to distinguish different target objects, rather than to describe the specific order of the target objects.

[0055] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific manner.

[0056] In the description of the embodiments of the present application, unless otherwise specified, the meaning of "a plurality of" refers to two or more. For example, a plurality of processing units refers to two or more processing units; a plurality of systems refers to two or more systems.

[0057] Based on the above premise, the technical solutions provided in the embodiments of the present application will be described below.

[0058] Specifically, the technical solution provided in the embodiments of the present application is directed to the problems existing in the scenario of notifying the network side for location update through the location update process after the location of the UE changes.

[0059] Exemplarily, regarding the scenario where the UE triggers the location update process, it can be as Figure 1 shown. Exemplarily, when the initial location of the UE is Figure 1 the first location shown in, the base station corresponding to the cell where it camps can be base station A. As the UE moves, its location moves from the first location to Figure 1The second position shown in [description]. When the base station of the cell corresponding to the second position is Base Station B, the UE needs to perform a location update procedure to notify the corresponding core network through Base Station B for location update, so that when the UE camps on the cell corresponding to Base Station B, the core network can send paging information or invite requests to the UE through Base Station B.

[0060] It should be understood that the above description is only an example listed for better understanding the technical solution of this embodiment and does not serve as the sole limitation of this embodiment.

[0061] It should be noted that due to different network modes, the location update procedures adopted by the UE are different. Among them, for 2G and 3G networks, the UE can notify the corresponding core networks of 2G and 3G networks for location update through Location Area Update (LAU); for Long Term Evolution (LTE) networks (4G networks), the UE can notify the corresponding core network of the LTE network for location update through tracking area update (TAU); for New Radio (NR) networks (5G networks), the UE can implement it through the registration procedure with Type as mobility registration update (MRU).

[0062] According to the existing standard protocols, after the UE under these network modes reselects a cell due to movement, the location update process may include several steps such as cell reselection, random access, location update, and resource release.

[0063] To better illustrate the technical solution provided by the embodiments of this application, the location update procedures performed by the UE and the network side are described below by taking the LTE network and the NR network as examples respectively.

[0064] It can be understood that the Mobility Management Entity (MME) is a key control node in the 3GPP protocol LTE network, and it is responsible for the positioning and paging processes of the UE in the idle mode / status (RRC_IDLE). Therefore, in the scenario of the LTE network mode, the UE performs the location update procedure with the MME.

[0065] In addition, it can also be understood that the Access and Mobility Management Function (AMF), as a 5G network unit, has a function similar to that of the MME in the LTE network and is mainly responsible for functions including registration management, connection management, access management, mobility management, etc. Therefore, in the scenario of the NR network mode, the UE performs a location update process with the AMF.

[0066] See Figure 2A and Figure 2B , which exemplarily shows a schematic diagram of the location update process between the UE and the MME in the LTE network mode.

[0067] As Figure 2A and Figure 2B shown, when the UE notifies the MME to perform a location update through a TAU, it can initiate a TRACKING AREA UPDATE REQUEST (TAU request) to the MME and start the T3430 timer when initiating the TAU request.

[0068] And the MME will, after receiving the TAU request sent by the UE, feedback a TRACKING AREA UPDATE ACCEPT message (TAU accept message) to the UE, as Figure 2A shown. Or feedback a TRACKING AREA UPDATE REJECT message (TAU reject message) to the UE, as Figure 2B shown.

[0069] Correspondingly, when the UE receives the TAU accept message or the TAU reject message sent by the MME, it will turn off the T3430 timer, as Figure 2A and Figure 2B shown.

[0070] It should be noted that in some possible implementation manners, turning off the timer can also be described as stopping the timer. Each embodiment of the present application takes turning off as an example.

[0071] In addition, it should also be noted that for the case where the MME makes a TAU accept message, generally the MME will allocate a Globally Unique Temporary UE Identity (GUTI) for the UE. For the case where the MME allocates a GUTI for the UE, when the MME sends the TAU accept message to the UE, it will add the GUTI to the TAU accept message and start the T3450 timer when sending the TAU accept message to the UE, as Figure 2A shown.

[0072] Accordingly, when the UE receives a TAU acceptance message carrying the GUTI within the duration corresponding to the T3430 timer, in addition to stopping the T3430 timer, it will also send a TRACKING AREA UPDATE COMPLETE to the MME, as Figure 2A shown.

[0073] Accordingly, when the MME receives the TRACKING AREA UPDATE COMPLETE sent by the UE within the duration corresponding to the T3450 timer, it will stop the T3450 timer. In this way, a location update is completed. Conversely, if the UE does not receive the TAU acceptance message sent by the MME within the duration corresponding to the T3430 timer, and / or the MME does not receive the TRACKING AREA UPDATE COMPLETE sent by the UE within the duration corresponding to the T3450 timer, the current location update procedure will be considered a failure.

[0074] Continue to refer to Figure 2B , for example, in the case where the MME sends a TAU rejection message, since the MME does not process the TAU request sent by the UE and thus does not allocate a GUTI to the UE, when sending the TAU rejection message to the UE, it is not necessary to start the T3450 timer.

[0075] Accordingly, when the UE receives the TAU rejection message sent by the MME within the duration corresponding to the T3430 timer, it does not need to send a TRACKING AREA UPDATE COMPLETE to the MME and can directly stop the T3430 timer. In this way, a location update is completed. Conversely, if the UE does not receive the TAU rejection message sent by the MME within the duration corresponding to the T3430 timer, the current location update procedure will be considered a failure.

[0076] For the case where the UE has not received a response from the MME to the TAU request within the duration corresponding to the T3430 timer (such as Figure 2A the TAU acceptance message shown in, or Figure 2B the TAU rejection message shown in), or for the case where the UE fails to send the TAU request at all within the duration corresponding to the T3430 timer due to other reasons (i.e., the TAU fails), according to the regulations of the standard protocol corresponding to the LTE network, the T3411 timer will be started, and after the T3411 timer expires, the TAU procedure can be triggered again, that is, the UE can send a TAU request to the MME again.

[0077] However, according to the regulations of the T3411 timer in the standard protocol, the corresponding duration of the T3411 timer is 10 seconds (second, s). Therefore, after the TAU fails and the T3411 timer is started, it will cause at least 10 seconds of service interruption for the UE. For the sake of easy understanding, the following will be described in conjunction with Figure 3 for illustration.

[0078] See Figure 3 , for example, take the UE initially camping on a cell in the NR network, such as Cell D. In some possible cases, when the signal quality of Cell D deteriorates (e.g., the UE moves away from Cell D), Cell D can notify the UE to perform cell handover, reselection, or redirection. Among them, which cell to handover or redirect to is guided by the network, that is, the network side can send an instruction to the UE to handover or redirect to a certain cell. Which cell to reselect to is decided by the UE itself according to many factors such as the currently detected cell signal distribution and the configuration of the priority between neighboring cells.

[0079] The following will specifically introduce handover, reselection, and redirection.

[0080] (1) Handover

[0081] It means that when the RRC is in the connected state (RRC_CONNECTED), the bearer service changes from one cell to another cell.

[0082] Handover can generally be divided into intra-frequency handover, inter-frequency handover, and inter-system handover.

[0083] Among them, intra-frequency handover means that the target cell (the cell to be handed over to) and the current serving cell (the currently camped cell) use the same radio frequency carrier frequency. Inter-frequency handover means that the target cell and the current serving cell use different radio frequency carrier frequencies. In these two handover scenarios, the target cell and the current serving cell belong to the same communication system. For example, when the UE is currently camping on Cell D of the NR system, the cell to be handed over to also needs to be the NR system. Conversely, if the UE is currently camping on Cell D of the LTE system, the cell to be handed over to needs to be the LTE system.

[0084] Among them, inter-system handover means handover between different systems, such as handover from the NR system to the LTE system, or from the LTE system to the NR system.

[0085] (2) Reselection (can also be described as random access)

[0086] It means that when the RRC is in the idle state (RRC_IDLE), the UE reselects from one cell to another cell.

[0087] Understandably, when the RRC is in the idle state, there is no data service or voice service between the UE and the network side. That is, reselection does not involve service handover.

[0088] (3) Redirection

[0089] Similar to handover, redirection is also based on the RRC being in the connected state. However, redirection cannot carry the previously conducted services.

[0090] Continue to refer to Figure 3 , for example, in this embodiment, after the signal quality of Cell D deteriorates, the UE switches from Cell D to Cell A in the LTE network by means of redirection or reselection.

[0091] Continue to refer to Figure 3 , for example, after the UE successfully camps on Cell A, the TAU procedure will be triggered, that is, notify the network side of the current location so that the network side can page the UE in the correct area or initiate an invite request to the UE.

[0092] Understandably, the TAU request sent by the UE to the network side needs to be based on the RRC connection between the UE and the network side. Therefore, when the TAU procedure is triggered after the UE camps on Cell A, the RRC establishment procedure will be triggered, and the RRC establishment procedure needs to be implemented through the random access procedure.

[0093] In addition, it should be noted that according to the provisions of the standard protocol, when the UE sends an RRC Connection Request (RRC connection request) to the currently camped cell, such as Cell A, the T300 timer needs to be started. And according to the provisions of the standard coordination, when the UE sends a TAU request to the network side, the T3430 timer needs to be started.

[0094] Based on this, when the TAU procedure is triggered after the UE successfully camps on Cell A, the RRC establishment procedure will be triggered together, and then the random access procedure will be triggered. Since both the TAU procedure and the RRC establishment procedure are triggered, the UE will start the T300 timer and the T3430 timer simultaneously, as Figure 3 shown.

[0095] Among them, the duration corresponding to the T300 timer is 1 s, and the duration corresponding to the T3430 timer is 15 s.

[0096] It should be noted that the random access procedure mentioned in this embodiment can also be referred to as the random access process.

[0097] Among them, the random access process refers to the process from when the UE sends a random access preamble and starts to attempt to access the network until a basic signaling connection is established between the UE and the network. There are two types of random access processes in the LTE network: contention-based random access and non-contention-based random access.

[0098] Under normal circumstances, when triggering the random access procedure, the UE will first initialize a contention-based random access process. In this process, the UE randomly selects a random access prefix flag (preamble signature, preamble code) to prepare for the subsequent contention resolution process.

[0099] In addition, it should also be noted that for the contention-based random access process, it usually includes 4 steps. These 4 steps can be implemented through 4 messages, namely msg1, msg2, msg3, and msg4. Among them, the UE randomly selects a preamble code to initiate msg1; after the base station receives msg1 sent by the UE, the Medium Access Control (MAC) layer of the base station organizes and generates a random access response (i.e., msg2); after the UE receives msg2, it performs the first scheduling transmission (i.e., msg3); after the base station receives msg3, it sends a contention resolution message to the UE (i.e., msg4).

[0100] For other implementation details of the random access procedure, please refer to the standard protocol and will not be elaborated here.

[0101] Thus, through the above msg1 to msg4, random access can be completed, that is, the RRC connection between the UE and Cell A is established. In this way, based on the RRC connection, the TAU procedure can be carried out, such as Figure 2A and Figure 2B the procedures shown.

[0102] Exemplarily, in another possible implementation, the messages sent during the interaction between the UE and the network side in the TAU procedure can also be considered as part of the random access procedure. That is, in this implementation, the random access procedure can also include msg5 and msg6.

[0103] Among them, msg5 is the location update request sent by the UE to the base station after receiving msg4 sent by the base station. Msg5 can include the location information of the UE and an identifier indicating the system type.

[0104] Specifically in the LTE network, msg5 is, for example, the TAU request sent by the UE as shown in Figure 2A and Figure 2B shown. Specifically in the NR network, msg5 is, for example, the TAU request sent by the UE as shown inFigure 6A and Figure 6B the REGISTRATION REQUEST of Type MRU shown in Figure 6B . For the specific implementation in the NR network, refer to the following embodiments, which will not be elaborated here for the time being.

[0105] Among them, msg6 is the location update confirmation message sent by the base station to the UE. msg6 may include the identity information of the base station and an identifier for indicating the system type.

[0106] Specifically in the LTE network, msg6 is, for example, the TAU acceptance message sent by the base station as shown in Figure 2A . Specifically in the NR network, msg6 is, for example, the REGISTRATION ACCEPT sent by the base station as shown in Figure 6A . For the specific implementation in the NR network, refer to the following embodiments, which will not be elaborated here for the time being.

[0107] It should be understood that the above description is only an example listed for better understanding the technical solution of this embodiment and does not serve as the sole limitation of this embodiment. In actual applications, msg7 may also be included in the random access procedure. Among them, msg7 is the random access rejection message sent by the base station to the UE. msg7 may include the reason for rejection and an identifier for indicating the system type.

[0108] Continue to refer to Figure 3 . Exemplarily, when the UE sends msg1 to the base station corresponding to Cell A, if msg2 made by the base station for msg1 is not received within the specified time, msg1 will be resent to the base station. Figure 3 When the UE sends msg1 to the base station corresponding to Cell A, if msg2 made by the base station for msg1 is not received within the specified time, msg1 will be resent to the base station.

[0109] According to the provisions of the standard protocol, for the case where the random access step fails, the T3430 timer will be processed in an overtime manner, that is, the T3411 timer will be started. Therefore, if the UE does not complete the random access and establish an RRC connection within the duration (1 s) corresponding to the T300 timer, although the T3430 timer has not timed out, the UE will actively close the T3430 timer and start the T3411 timer, as shown in Figure 3 . Figure 3 shown.

[0110] According to the provisions of the standard protocol, after the UE starts the T3411 timer, within the time corresponding to the T3411 timer, that is, within 10 s, the TAU procedure cannot be initiated. Therefore, even if the UE undergoes cell reselection as it moves, such as successfully camping on CellB, and undergoes cell reselection again as it moves and camps on Cell C. Before the T3411 timer times out, the TAU procedure will not be re-initiated. After the T3411 timer times out, the UE will re-initiate the TAU procedure, as shown in Figure 3 . Figure 3 shown.​​​​

[0111] Understandably, since the UE has not yet established an RRC connection with Cell C. Therefore, when the UE reinitiates the TAU procedure after the T3411 timer expires, it will also trigger the RRC procedure and start the T300 timer and the T3430 timer ( Figure 3 not shown).

[0112] Since the RRC connection needs to be implemented through the random access procedure, after the UE reinitiates the TAU procedure, it will perform the random access procedure with Cell C.

[0113] Correspondingly, after the UE and Cell C complete the random access, the RRC connection between them will be established and the RRC establishment procedure will be completed.

[0114] Figure 3 Taking the case where the random access procedure triggered when the UE reinitiates the TAU procedure after T3411 expires is successful and the UE establishes an RRC connection with Cell C as an example.

[0115] Continue to refer to Figure 3 , exemplarily, after the UE establishes an RRC connection with Cell C, the UE can process the TAU procedure with the core network of LTE through the base station corresponding to Cell C, that is, execute Figure 2A or Figure 2B the interaction shown, which will not be elaborated here.

[0116] Figure 3 Taking the case where the reinitiated TAU procedure is successful as an example, in this case, if the core network initiates an operation to locate this UE, when the RRC state of this UE is not the connected state, the core network can, based on the location information reported by this UE, initiate paging to Cell C where this UE camps on, and thus can achieve interaction with this UE.

[0117] Exemplarily, if the RRC state of this UE is the connected state, the core network can directly initiate an invite request.

[0118] Correspondingly, after the UE receives the paging message from the core network, it can make a response to the paging. After the UE receives the invite request from the core network, it can make a response to the invite.

[0119] However, after the UE starts the T3411 timer, the core network may initiate paging to the UE within these 10 seconds. However, since the TAU process fails after the UE camps on Cell A, the network side does not know that the UE is currently camping on Cell A and still believes that the UE is camping on Cell D. Therefore, the core network of NR will send paging to all the base stations corresponding to the Tracking Area Codes (TACs) recorded in the Tracking Area Code List (TACList), as well as to the UEs accessing these base stations, as Figure 3 shown. However, at this time, the UE has already left Cell D, so the paging message cannot reach the UE. This results in a service interruption problem for the UE within these 10 seconds.

[0120] According to the provisions of the standard protocol, if the number of TAU process failures exceeds 5 times, the UE needs to start the T3402 timer, and it is stipulated that the UE cannot initiate the TAU process again before the T3402 timer expires. In this way, although it can prevent the UE from frequently sending TAU requests to the network side, avoid causing a signaling storm, and reduce the pressure on the network side, the UE cannot initiate the TAU process within the 12 - minute duration of the T3402 timer, which will seriously affect the UE's services.

[0121] However, for the scenario where the UE is in fast movement, such as when it is on a moving high - speed train, airplane, or other means of transportation, the cell where the UE camps is changing rapidly. If there is a problem in the original cell, there may not be a problem in the new cell, and most likely there is no problem.

[0122] Therefore, the current location update processing logic is obviously not well - suited for UEs in fast - moving scenarios. In view of this, the embodiments of the present application provide a method for location update suitable for fast - moving UEs in an LTE network.

[0123] See Figure 4 , for example, still taking the case where the UE initially camps on Cell D of the NR network and, after the signal quality of Cell D deteriorates, the UE switches from Cell D to Cell A of the LTE network by means of redirection or reselection.

[0124] Continue to refer to Figure 4 , for example, after the UE successfully camps on Cell A and triggers the TAU process, it will trigger the RRC establishment process, then trigger the random access process, and start the T300 timer and the T3430 timer simultaneously.

[0125] Continue to refer to Figure 4, exemplarily, in this embodiment, it is still taken as an example that within the timing period corresponding to the T300 timer, random access fails, resulting in no RRC connection being established between the UE and Cell A. For this scenario, the T3430 timer will be actively closed by the UE, and the T3411 timer will be started according to the processing rules for the timeout of the T3430 timer.

[0126] Continue to refer to Figure 4 , exemplarily, specifically in the location update method provided in the embodiment of the present application, when the T3411 timer is started due to random access failure resulting in RRC connection establishment failure, within the timing period corresponding to the T3411 timer, the UE will detect whether the current conditions for re-initiating the TAU procedure are met.

[0127] It should be noted that since the location update method provided in the embodiment of the present application is for the scenario where the UE moves rapidly, in this scenario, as the location moves, the cell where the UE camps may change rapidly, and the original cell where the UE camps may also have better signal quality due to rapid location movement. Therefore, in a possible implementation manner, the conditions for re-initiating the TAU procedure described in the embodiment of the present application may, for example, be a change in the signal quality of the original cell where the UE currently camps, such as the signal quality exceeding a certain threshold, such as increasing by 100 dbm. Another example may be that the cell where the UE camps has changed, such as changing from the currently camped Cell A to Cell B or Cell C.

[0128] It should be understood that the above description is only an example listed for better understanding the technical solution of this embodiment and does not serve as the sole limitation of this embodiment.

[0129] Continue to refer to Figure 4 , exemplarily, in the location update method provided in the embodiment of the present application, when the UE determines that the current conditions for re-initiating the TAU procedure are met, it can actively close the T3411 timer and immediately re-initiate the TAU procedure (currently, according to the 4G standard protocol regulations, the UE cannot actively close the T3411 timer and can only re-initiate the TAU procedure after the T3411 timer times out. The same applies to 5G networks or other networks).

[0130] For the sake of convenience of description, this embodiment takes the example that the cell where the UE camps changes from Cell A to Cell C.

[0131] Regarding the situation where the UE re-initiates the TAU procedure and still fails, the T3411 timer can be restarted. Regarding whether to wait for the T3411 timer to expire before re-initiating the TAU procedure again after starting the T3411 timer, or to immediately stop the T3411 timer and re-initiate the TAU procedure after recognizing that the signal quality of the currently camped cell improves or the camped cell changes, it can be determined according to the reason for starting the T3411 timer.

[0132] Exemplarily, in a possible implementation, if the re-initiated TAU procedure still fails due to random access failure and no RRC connection is established, that is, the TAU request is not sent to the network side at all, the T3411 timer can be immediately stopped and the TAU procedure can be re-initiated after recognizing that the signal quality of the currently camped cell improves or the camped cell changes. Conversely, if the TAU procedure has reached the network side but fails for other reasons, it can be initiated after waiting for the T3411 timer to expire, avoiding frequent TAU requests to the network side and causing pressure on the network.

[0133] Since the UE moves a large distance in a short time in scenarios of fast movement, such as on high-speed trains, airplanes and other means of transportation, the time for the UE to camp on the cell to change from Cell A to Cell C may be very short and may not reach 10 s at all. Therefore, by setting the UE to immediately stop the T3411 timer (stop the T3411 timer in advance before it expires) and re-initiate the TAU procedure after recognizing that the signal quality of the currently camped cell improves or the camped cell changes. In this way, the UE does not need to wait for the T3411 timer to expire, that is, wait for 10 s before re-initiating the TAU procedure, thereby shortening the time when the UE's service is interrupted and ensuring that paging and invite requests can reach the UE normally.

[0134] In addition, in the scenario where random access failure causes no RRC connection to be established at all, since the TAU request does not reach the network side at all (the TAU request fails to be sent out through the RRC connection), immediately stopping the T3411 timer and re-initiating the TAU procedure when the above conditions for re-initiating the TAU procedure are met will not impose an additional burden on the network side.

[0135] As described above, according to the provisions of the standard protocol, when the number of TAU procedure failures exceeds 5 times, the UE needs to start the T3402 timer, and it is stipulated that the UE cannot initiate the TAU procedure again before the T3402 timer expires (12 minutes). However, based on the location update method provided in the embodiments of the present application, in a possible implementation manner, for the case where the reason for the TAU procedure failure is a random access failure, resulting in the unsuccessful establishment of the RRC, the TAU times may not be accumulated, and when the conditions for re-initiating the TAU procedure described above are met, the TAU procedure is initiated again, as Figure 5 shown.

[0136] Continue to refer to Figure 5 , for example, in the case where the RRC connection is successfully established, if the TAU procedure still fails, for this situation, the TAU times can be accumulated according to the provisions of the standard protocol, and when the accumulated TAU times do not exceed the preset number, the TAU procedure is re-initiated. On the contrary, when the accumulated TAU times exceed the preset number, the T3402 timer is started, and the TAU procedure is initiated again only after the T3402 timer expires, as Figure 5 shown.

[0137] Therefore, for the scenario where the RRC connection is not established, resulting in the TAU request not being sent to the network side at all, by not accumulating the TAU procedure times for this reason, the 5 - time opportunity stipulated by the standard protocol can be prevented from being wasted, and the T3402 timer can be avoided from being started. In the scenario where the RRC connection is successfully established, the number of failed TAU procedures is accumulated, that is, the number of TAU requests actually sent out is accumulated. Thus, without substantially increasing the burden on the network side, the location update can be carried out in a timely manner, avoiding the service from being interrupted for a long time, enabling the user equipment to return to normal in a timely manner and receive paging.

[0138] In addition, it should be noted that the TAU procedure described in the embodiments of the present application can be understood as Figure 2A and Figure 2B show the complete interaction between the UE and the MME. The TAU request is the request sent by the UE to the MME when triggering the TAU procedure.

[0139] Refer to Figure 6A and Figure 6B , which exemplarily shows a schematic diagram of the location update process between the UE and the AMF in an NR network system.

[0140] As Figure 6A and Figure 6BAs shown, when the UE notifies the AMF to perform a location update through a registration process of type MRU (subsequently referred to as: MRU process), it can initiate a REGISTRATION REQUEST of type MRU (subsequently referred to as: MRU request. The MRU request is a step in the MRU process) to the AMF, and start the T3510 timer when initiating the MRU request.

[0141] And the AMF will, after receiving the MRU request sent by the UE, feedback a REGISTRATION ACCEPT message (registration acceptance message) to the UE, as Figure 6A shown. Or feedback a REGISTRATION REJECT message (registration rejection message) to the UE, as Figure 6B shown.

[0142] Correspondingly, when the UE receives the registration acceptance message or the registration rejection message sent by the AMF, it will stop the T3510 timer, as Figure 6A and Figure 6B shown.

[0143] It should be noted that for the case where the AMF issues a registration acceptance message, the AMF will also allocate a GUTI for the UE. For the case where the AMF allocates a GUTI for the UE, when the AMF sends the registration acceptance message to the UE, it will add this GUTI to the registration acceptance message and start the T3550 timer when sending the registration acceptance message to the UE, as Figure 6A shown.

[0144] Correspondingly, within the duration corresponding to the T3510 timer, when the UE receives the registration acceptance message carrying the GUTI, in addition to stopping the T3510 timer, it will also send a REGISTRATION COMPLETE to the AMF, as Figure 6A shown.

[0145] Correspondingly, within the duration corresponding to the T3550 timer, when the AMF receives the REGISTRATION COMPLETE sent by the UE, it will stop the T3550 timer. In this way, a location update is completed. On the contrary, if the UE does not receive the registration acceptance message sent by the AMF within the duration corresponding to the T3510 timer, and / or the AMF does not receive the REGISTRATION COMPLETE sent by the UE within the duration corresponding to the T3550 timer, it will be considered that the current location update process fails.

[0146] Continue to refer to Figure 6B, Exemplarily, for the case where the AMF sends a registration rejection message, since the AMF does not process the MRU request sent by the UE and thus does not allocate a GUTI to the UE, when sending a registration rejection message to the UE, it is not necessary to start the T3550 timer.

[0147] Correspondingly, when the UE receives the registration rejection message sent by the AMF within the duration corresponding to the T3510 timer, it does not need to send REGISTRATION COMPLETE to the AMF and can directly close the T3510 timer. In this way, a location update is completed. Conversely, if the UE does not receive the registration rejection message sent by the AMF within the duration corresponding to the T3510 timer, it will be considered that the current location update process fails.

[0148] For the case where the UE has not received a response from the AMF to the MRU request (such as Figure 6A the registration acceptance message shown in Figure 6B or the registration rejection message shown in

[0149] within the duration corresponding to the T3510 timer, or for the case where the UE fails to send the MRU request at all within the duration corresponding to the T3510 timer due to other reasons (i.e., the case of MRU failure), according to the provisions of the standard protocol corresponding to the NR network, the T3511 timer will be started, and after the T3511 timer times out, the MRU process can be triggered again, that is, the UE can send an MRU request to the AMF again. Figure 7 For ease of understanding, the following is described in conjunction with

[0150] Refer to Figure 7 , Exemplarily, take the case where the UE initially camps on a cell in the LTE network, such as Cell H. In some possible situations, when the signal quality of Cell H deteriorates (such as the UE moving away from Cell H), Cell H can notify the UE to perform cell handover, reselection, or redirection.

[0151] For the descriptions of handover, reselection, and redirection, reference can be made to the above embodiment part and will not be elaborated here.

[0152] Continue to refer to Figure 7 , Exemplarily, in this embodiment, take the case where after the signal quality of Cell H deteriorates, the UE switches from Cell H to Cell E in the NR network by means of redirection or reselection as an example.

[0153] Continue to refer toFigure 7 Exemplarily, after the UE successfully camps on Cell E, the MRU process will be triggered, that is, notifying the network side of the current location so that the network side can page the UE in the correct area or initiate an invite request to the UE.

[0154] Understandably, the MRU request sent by the UE to the network side, similar to the TAU request type in the LTE network, also needs to be based on the RRC connection between the UE and the network side. Therefore, when the MRU process is triggered after the UE camps on Cell E, the RRC establishment process will be triggered, and the RRC establishment process needs to be implemented through the random access process.

[0155] Based on this, when the MRU process is triggered after the UE successfully camps on Cell E, the RRC establishment process will be triggered together, and then the random access process will be triggered. Since both the MRU process and the RRC establishment process are triggered, the UE will start the T300 timer and the T3510 timer simultaneously, as Figure 7 shown.

[0156] Among them, the duration corresponding to the T300 timer is 1 s, and the duration corresponding to the T3510 timer is 15 s.

[0157] Regarding the random access process performed by the UE with the base station corresponding to the currently camped Cell E in the NR network, the steps are the same as those in the LTE network. For the specific implementation details, reference can be made to Figure 4 the description part of the random access process in the embodiment shown here, which will not be elaborated further.

[0158] Continue to refer to Figure 7 Exemplarily, when the UE sends msg1 to the base station corresponding to Cell E, if msg2 from the base station in response to msg1 is not received within the specified time, msg1 will be resent to the base station.

[0159] According to the regulations of the standard protocol, for the case where the random access step fails, the T3510 timer will be processed in an overtime manner, that is, the T3511 timer will be started. Therefore, if the UE fails to complete the random access and establish the RRC connection within the duration (1 s) corresponding to the T300 timer, although the T3510 timer has not timed out, the UE will actively close the T3510 timer and start the T3511 timer, as Figure 7 shown.

[0160] According to the provisions of the standard protocol, after the UE starts the T3511 timer, within the time corresponding to the T3511 timer, that is, within 10 s, the UE cannot initiate the MRU process. Therefore, even if the UE performs cell reselection as it moves, such as successfully camping on CellF, and then performs cell reselection again as it moves and camps on Cell G. Before the T3511 timer expires, the MRU process will not be restarted. After the T3511 timer expires, the UE will restart the MRU process, as Figure 7 shown.

[0161] Understandably, since the UE has not yet established an RRC connection with Cell G. Therefore, when the UE restarts the MRU process after the T3511 timer expires, it will also trigger the RRC process and start the T300 timer and the T3510 timer ( Figure 7 not shown).

[0162] Since the RRC connection needs to be implemented through the random access process, after the UE restarts the MRU process, it will perform the random access process with Cell G.

[0163] Correspondingly, after the UE completes the random access with Cell G, the RRC connection between the two will be established, and the RRC establishment process will also be completed.

[0164] Figure 7 Taking the example that the random access process triggered when the UE restarts the MRU process after the T3511 timer expires is successful and the UE establishes an RRC connection with Cell G.

[0165] Continue to refer to Figure 7 , for example, after the UE establishes an RRC connection with Cell G, the UE can process the MRU process with the core network of NR through the base station corresponding to Cell G, that is, execute Figure 6A or Figure 6B the interaction shown, which will not be elaborated here.

[0166] Figure 7 Taking the successful restart of the MRU process as an example, in this case, if the core network initiates an operation to locate this UE, when the RRC state of this UE is not the connected state, the core network can, based on the location information reported by this UE, initiate paging to Cell G where this UE camps, and thus achieve interaction with this UE.

[0167] For example, if the RRC state of this UE is the connected state, the core network can directly initiate an invite request.

[0168] Accordingly, after the UE receives the paging message from the core network, it can make a response to the paging. After the UE receives the invite request from the core network, it can make a response to the invite.

[0169] Then, after the UE starts the T3511 timer, within these 10 seconds, the core network may initiate paging to the UE. However, since the MRU process fails after the UE camps on Cell E, the network side does not know that the UE is currently camping on Cell E and still believes that the UE is camping on Cell H. Therefore, the LTE core network sends paging to all the base stations corresponding to the Tracking Area Codes (TACs) recorded in the Tracking Area Code List (TACList), and to the UEs accessing these base stations, as Figure 7 shown. However, at this time, the UE is no longer camping on Cell H, so the paging message cannot reach this UE. This results in a service interruption problem for this UE within these 10 seconds.

[0170] According to the provisions of the standard protocol, when the number of failures of the MRU process exceeds 5 times, the UE needs to start the T3502 timer, and it is stipulated that the UE cannot initiate the MRU process again before the T3502 timer expires. In this way, although it can prevent the UE from frequently sending MRU requests to the network side, avoid causing a signaling storm, and reduce the pressure on the network side, the 12-minute duration of the T3502 timer will seriously affect the services of the UE.

[0171] However, for the scenario where the UE is moving rapidly, such as when it is on a moving high-speed train, airplane or other means of transportation, the cell where the UE camps is changing rapidly. If there is a problem in the original cell, there may not be a problem in the new cell, and most likely there is no problem.

[0172] Therefore, the current location update processing logic obviously cannot be well applied to the UE in the rapid movement scenario. In view of this, the embodiments of the present application provide a method for location update applicable to rapidly moving UEs in the NR network.

[0173] See Figure 8 , for example, still taking the UE initially camping on Cell H of the LTE network and, after the signal quality of Cell H deteriorates, the UE reselecting or redirecting from Cell H to Cell E of the NR network as an example.

[0174] Continue to see Figure 8 , for example, after the UE successfully camps on Cell E and triggers the MRU process, it will trigger the RRC establishment process, and then trigger the random access process, while starting the T300 timer and the T3510 timer.

[0175] Continue to refer to Figure 8 , for example, in this embodiment, it is still assumed that within the timing period corresponding to the T300 timer, a random access failure occurs, resulting in no RRC connection being established between the UE and Cell E. For this scenario, the T3510 timer will be actively closed by the UE, and according to the processing rules for the timeout of the T3510 timer, the T3511 timer will be started.

[0176] Continue to refer to Figure 8 , for example, specifically in the location update method provided in the embodiments of the present application, when the T3511 timer is started due to a random access failure resulting in a failed RRC connection establishment, within the timing period corresponding to the T3511 timer, the UE will detect whether the current conditions for reinitiating the MRU process are met.

[0177] It should be noted that since the location update method provided in the embodiments of the present application is for the scenario where the UE moves rapidly, in this scenario, as the location moves, the cell where the UE camps may change rapidly, and the original cell where the UE camps may also have better signal quality due to the rapid movement of the location. Therefore, in one possible implementation, the conditions for meeting the reinitiation of the MRU process described in the embodiments of the present application may be, for example, a change in the signal quality of the original cell where the UE currently camps, such as the signal quality exceeding a certain threshold, such as increasing by 100 dbm. Another example may be that the cell where the UE camps has changed, such as changing from the currently camped Cell E to Cell F or Cell G.

[0178] It should be understood that the above description is only an example listed for better understanding the technical solution of this embodiment and does not serve as the sole limitation of this embodiment.

[0179] Continue to refer to Figure 8 , for example, in the location update method provided in the embodiments of the present application, when the UE determines that the current conditions for reinitiating the MRU process are met, it can actively close the T3511 timer and immediately reinitiate the MRU process (currently, according to the 5G standard protocol regulations, the UE cannot actively close the T3511 timer and can only reinitiate the MRU process after the T3511 timer times out. The same is true for 4G networks or other networks).

[0180] For ease of explanation, this embodiment takes the example where the cell where the UE camps changes from Cell E to Cell G.

[0181] Regarding the case where the UE re - initiates the MRU process and still fails, the T3511 timer can be restarted. Regarding whether to wait for the T3511 timer to time out before re - initiating the MRU process again after starting the T3511 timer, or to immediately close the T3511 timer and re - initiate the MRU process after recognizing that the signal quality of the currently camped cell has improved or the camped cell has changed, it can be determined according to the reason for starting the T3511 timer.

[0182] Exemplarily, in a possible implementation, if the re - initiated MRU process still fails due to random access failure and the reason for not establishing an RRC connection, that is, the MRU request is not sent to the network side at all, the T3511 timer can be immediately closed and the MRU process can be re - initiated after recognizing that the signal quality of the currently camped cell has improved or the camped cell has changed. Conversely, if the MRU process has reached the network side but fails for other reasons, it can be initiated after waiting for the T3511 timer to time out, avoiding frequent MRU requests to the network side and causing pressure on the network.

[0183] Since the UE moves a large distance in a short time in scenarios of fast movement, such as on high - speed trains, airplanes and other means of transportation, the time taken for the UE to camp on a cell to change from Cell E to Cell G may be very short, far from reaching 10 s. Therefore, by this setting, when the UE recognizes that the signal quality of the currently camped cell has improved or the camped cell has changed, the T3511 timer is immediately closed (before the T3511 timer times out, the T3511 timer is closed in advance), and the MRU process is re - initiated. In this way, the UE does not need to wait for the T3511 timer to time out, that is, wait for 10 s to re - initiate the MRU process, thereby shortening the time when the UE's service is interrupted and ensuring that paging and invite requests can reach the UE normally.

[0184] In addition, in the scenario of random access failure and no RRC connection established at all, since the MRU request does not reach the network side at all (the MRU request fails to be sent out through the RRC connection), when the conditions for re - initiating the MRU process are met, the T3511 timer is immediately closed and the MRU process is re - initiated, which will not increase the burden on the network side.

[0185] As described above, according to the provisions of the standard protocol, when the number of failures in the MRU process exceeds 5 times, the UE needs to start the T3502 timer, and it is stipulated that the UE cannot initiate the MRU process again before the T3502 timer expires (12 minutes). However, based on the location update method provided in the embodiments of the present application, in a possible implementation, for the case where the reason for the failure of the MRU process is a random access failure, resulting in the unsuccessful establishment of the RRC, the MRU count may not be accumulated, and when the conditions for re-initiating the MRU process as described above are met, the MRU process is initiated again.

[0186] In addition, it should be noted that in order not to add pressure to the network side, when the RRC connection is successfully established, if the MRU process still fails, in this case, according to the provisions of the standard protocol, the MRU count can be accumulated, and when the accumulated MRU count does not exceed the preset number, the MRU process is re-initiated. Conversely, when the accumulated MRU count exceeds the preset number, the T3502 timer is started, and the MRU process is initiated again only after the T3502 timer expires.

[0187] Thus, for the scenario where the RRC connection is not established, resulting in the MRU request not being sent to the network side at all, by not accumulating the MRU process count for this reason, the 5 opportunities stipulated by the standard protocol can be prevented from being wasted, and the T3502 timer can be avoided from being started. In the scenario where the RRC connection is successfully established, the number of failed MRU processes is accumulated, that is, the count is only accumulated for the actually sent MRU requests, so that the location update can be performed in a timely manner without basically increasing the burden on the network side, avoiding the service from being interrupted for a long time, and enabling the user equipment to return to normal in a timely manner and receive paging.

[0188] It should be understood that in the above description of the location update method provided in the embodiments of the present application, only the LTE (4G) network and the NR (5G) network are taken as examples. In practical applications, this method is also applicable to the second-generation wireless telephone technology (2G) network and the third-generation wireless telephone technology (3G) network. Among them, when the location update occurs in the 2G network or the 3G network, it can be implemented through the Location Area Update (LAU) process.

[0189] In addition, it should be understood that in actual applications, the method can be applied not only between different communication networks, such as switching from a cell of an NR network to a cell of an LTE network, or from a cell of an LTE network to a cell of an NR network, but also between the same communication networks. For example, reselecting from a cell of an LTE network to a cell of an LTE network, or reselecting from a cell of an NR network to a cell of an NR network.

[0190] It should be noted that, in the process of reselecting a cell in the same communication network, it is necessary to perform location update based on the location update method provided in the embodiment of the present application under certain circumstances.

[0191] For example, in the scenario of reselecting a cell in the LTE network (residing in a cell in the LTE network before reselection and residing in another cell in the LTE network after reselection), the TAU process needs to be triggered only when the tracking area code (Tracking Area Code, TAC) of the reselected cell is not in the original TAC list (TAC List), and then the location update is performed based on the location update method provided in the embodiment of the present application.

[0192] For example, in the scenario of reselecting a cell in the NR network (residing in a cell in the NR network before reselection and residing in another cell in the NR network after reselection), the MRU process needs to be triggered only when the tracking area code (Tracking Area Code, TAC) of the reselected cell is not in the original TAC list (TAC List), and then the location update is performed based on the location update method provided in the embodiment of the present application.

[0193] In addition, it should be understood that with the subsequent development of communication technology, in the future next-generation communication technology, such as 6G, if based on standard protocols, the location update process performed by user equipment in these networks also includes cell reselection, random access, location update, resource release and other steps, then the location update method provided in the embodiment of the present application is also applicable.

[0194] Specifically, for a method for updating the location of a fast-moving UE in different networks, the following method can be used: Figure 9 As shown, specifically including:

[0195] S101, a user equipment triggers a location update procedure by redirecting or reselecting from a first cell where it resides, and starts a first timer and a second timer.

[0196] Among them, user devices, such as mobile phones, smart watches, tablet computers, etc., are not listed here one by one, and this application does not impose any restrictions on this.

[0197] Among them, the network modes corresponding to the first cell and the second cell may be the same or different.

[0198] Among them, the network mode may include, for example, 2G, 3G, 4G, 5G, and future next-generation communication networks, such as 6G.

[0199] Exemplarily, for the scenario where the network modes corresponding to the first cell and the second cell are the same, the first cell and the second cell can be any one of the above-listed network modes.

[0200] Exemplarily, for the scenario where the network modes corresponding to the first cell and the second cell are different, the first cell can be any one of the above-listed network modes, and the second cell can be a network other than the network mode corresponding to the first cell among the above-listed network modes.

[0201] It should be understood that the above description is only an example listed for better understanding the technical solution of this embodiment and does not serve as the only limitation to this embodiment.

[0202] Among them, the first timer is the T300 timer that needs to be started when establishing an RRC connection.

[0203] Exemplarily, when the second cell where the user equipment currently camps is a cell in the LTE network, such as Cell A, or Cell B, or Cell C in the above embodiment, the second timer is the T3430 timer. When the second cell is a cell in the NR network, such as Cell E, or Cell F, or Cell G mentioned in the above embodiment, the second timer is the T3510 timer.

[0204] S102, within the duration corresponding to the first timer, when the RRC connection fails to be established successfully, after the first timer times out, turn off the second timer and start the third timer.

[0205] Among them, when the second cell where the user equipment currently camps is a cell in the LTE network, such as Cell A, or Cell B, or Cell C in the above embodiment, the third timer is the T3411 timer. When the second cell is a cell in the NR network, such as Cell E, or Cell F, or Cell G mentioned in the above embodiment, the second timer is the T3511 timer.

[0206] S103, within the duration corresponding to the third timer, when it is recognized that a preset condition is met, turn off the third timer in advance, re-trigger the location update process, and start the first timer and the second timer.

[0207] Among them, for the cases that meet the preset conditions, such as the signal quality of the original cell getting better as described in the above embodiments, or the cell changing.

[0208] From the descriptions of the above embodiments applicable to LTE networks and NR networks, it can be seen that for different network modes, the location update processes are different.

[0209] Exemplarily, when the network mode corresponding to the second cell is an LTE network, the location update process is implemented through a Tracking Area Update (TAU).

[0210] Exemplarily, taking the first cell as Cell D described in the above embodiments, the second cell can be Cell A, or Cell B, or Cell C described in the above embodiments. In this scenario, the location update process, for example Figure 4 or Figure 5 In the shown embodiment, when the UE first initiates a TAU process while camping on Cell A, if the re-triggered location update process meets the re-initiation condition, the TAU process initiated after actively closing the T3411 timer.

[0211] Exemplarily, when the network mode corresponding to the second cell is an NR network, the location update process is implemented through a registration process with the Type of MRU.

[0212] Exemplarily, taking the first cell as Cell H described in the above embodiments, the second cell can be Cell E, or Cell F, or Cell G described in the above embodiments. In this scenario, the location update process, for example Figure 8 In the shown embodiment, when the UE first initiates an MRU process while camping on Cell A, if the re-triggered location update process meets the re-initiation condition, the MRU process initiated after actively closing the T3511 timer.

[0213] S104, within the duration corresponding to the third timer, when no situation satisfying the preset condition is recognized, after the third timer times out, re-trigger the location update process, and start the first timer and the second timer.

[0214] Exemplarily, taking the first cell as Cell D described in the above embodiments, the second cell can be Cell A, or Cell B, or Cell C described in the above embodiments. In this scenario, the third location process is a TAU process initiated after T3411 times out.

[0215] Thus, by setting that when the location update process fails due to the RRC connection not being established and a preset condition is recognized, the third timer is actively closed and the location update process is restarted, it is possible to prevent the user equipment from waiting for a long time and causing abnormal services of the user equipment. In this way, without basically increasing the burden on the network side, the user equipment with abnormal location update process can quickly return to normal so that the user equipment can normally receive paging.

[0216] In addition, in some possible implementation manners, it can be set that when the RRC connection is not successfully established and the location update process fails, the location update process triggered this time is not accumulated into the total number of triggers corresponding to the location update process. When the RRC connection is successfully established and the re-triggered location update process fails, the location update process triggered this time is accumulated into the total number of triggers corresponding to the location update process; when the total number of triggers is greater than the preset number of triggers, the fourth timer is started, and the duration corresponding to the fourth timer is greater than the durations corresponding to the first timer, the second timer, and the third timer respectively.

[0217] Among them, in the LTE network, the fourth timer is T3402; in the NR network, the fourth timer is T3502.

[0218] Thus, in a scenario where the RRC connection is not established and the location update process fails, such as when the corresponding request for location update is not sent to the network side, the user equipment does not accumulate the location update process triggered this time into the total number of triggers corresponding to the location update process. For the case where the RRC connection is successfully established but the location update process still fails, that is, when the corresponding request is actually sent out, the number of times is accumulated, so as to avoid the total number of triggers quickly reaching the preset number of triggers specified by the standard protocol, and then starting the fourth timer, resulting in the user equipment being unable to perform the location update process within the duration corresponding to the fourth timer, making the user equipment unable to return to normal for a long time, and then causing the user equipment to be unable to normally receive paging.

[0219] That is, based on the implementation manner provided in this aspect, it is possible to basically not burden the network and not be rejected by the network.

[0220] Regarding the details not elaborated in this embodiment, reference can be made to the description part of the above embodiments for the LTE network and the NR network, which will not be repeated here.

[0221] In addition, it should be noted that in some possible implementation manners, the location update method provided in the embodiments of the present application is also applicable to cell handover, that is, the scenario of switching from one cell to another when the RRC state is in the connected state.

[0222] Understandably, since handover refers to the change from one cell to another when RRC is in the connected state (RRC_CONNECTED). Therefore, during the process of the UE camping on the target serving cell (such as the second cell) in a handover manner from the currently camped cell (such as the first cell), due to the existence of the RRC connection, when triggering a location update procedure, such as the TAU procedure in the LTE network or the MRU procedure in the NR network, there is no need to execute the RRC establishment procedure, and only the random access procedure and the location update procedure are performed.

[0223] Taking the handover of a cell in the LTE network as an example, after the UE changes the camped cell and triggers the random access procedure and the TAU procedure, the first timer started is specifically the T304 timer, and the second timer remains the T3430 timer.

[0224] In addition, it should also be noted that if the random access fails, the cell handover will also fail. At this time, the UE will trigger a Radio Link Failure (RLF) procedure. In the RLF procedure, the cell will be reselected first, and then the RRC reestablishment procedure will be initiated. If the RRC reestablishment procedure fails due to reasons such as random access, the UE will start the T3411 timer. This will face the problem that when camping on the second cell in the redirection or reselection manner in the above embodiment, the RRC connection fails due to reasons such as random access, and then the T3411 timer is started, resulting in the UE being unable to perform services for at least 10 s.

[0225] Therefore, in a possible implementation manner, when the UE changes the camped cell in a handover manner and the RRC reestablishment procedure fails due to reasons such as random access and the T3411 timer is started, the UE that meets the conditions for reinitiating the TAU procedure can also actively close the T3411 timer based on the location update method provided in the above embodiment and immediately initiate the TAU procedure to quickly resume the services of the UE.

[0226] In addition, it should be understood that the above describes the location update in the manner of cell handover taking the scenario of the LET network as an example. The same is true for the NR network. According to the existing standard, the corresponding timer of the NR network is started during the handover process. After the RRC reestablishment procedure fails due to reasons such as random access, the T3511 timer is started. The specific implementation details can refer to the above embodiment and will not be elaborated here.

[0227] To better understand the technical solution provided by the embodiments of the present application, taking the user equipment as a mobile phone as an example, based on the hardware structure of the mobile phone, the hardware involved in implementing the location update method provided by the embodiments of the present application is described.

[0228] See Figure 10, an exemplary hardware structure of a mobile phone 100 is shown.

[0229] As Figure 10 shown, the mobile phone 100 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 button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0230] Among them, the antenna 1 and the antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the mobile phone 100 can be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example: the antenna 1 can be multiplexed as the diversity antenna of the wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0231] Specifically in the embodiments of the present application, the interaction between the network side (such as the MME of the 4G network, or the AMF of the 5G network, or the core network under other network systems) and the mobile phone 100 as the UE, such as the TRACKING AREAUPDATE REQUEST sent by the UE to the network side, the REGISTRATION REQUEST of Type MRU, the TRACKING AREA UPDATE COMPLETE, the REGISTRATION COMPLETE, the messages / instructions in the RRC process, the messages / instructions in the random access process, and the TRACKING AREA UPDATE ACCEPT, the TRACKING AREA UPDATE REJECT, the REGISTRATION ACCEPT, the REGISTRATION REJECT, etc. sent by the network side to the UE, can be implemented through the antenna 1 or the antenna 2.

[0232] Among them, the mobile communication module 150 can provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to the mobile phone 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The wireless communication module 160 can provide solutions for wireless communications applied to the mobile phone 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc.

[0233] Exemplarily, in some implementation manners, the antenna 1 of the mobile phone 100 can be coupled to the mobile communication module 150, and the antenna 2 can be coupled to the wireless communication module 160. Thus, the mobile phone 100 can communicate with the network and other devices through mobile communication technologies or wireless communication technologies.

[0234] In addition, it should be noted that, in some implementation manners, the processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor (Modem, also known as a baseband processor), a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a neural-network processing unit (NPU), etc.

[0235] Understandably, in specific implementations, different processing units may be independent devices or integrated in one or more processors.

[0236] It should be noted that, in specific practical applications, the mobile phone 100 can implement the technical solutions provided in the embodiments of the present application through two processing units, namely the AP 110A and the Modem 110B. For example, the AP 110A determines the location change of the user equipment, and then calls the corresponding driver in the kernel layer of the user equipment to hand over the location update process to the Modem. The Modem can then interact with the network side according to the processing logic involved in the location update method provided in the embodiments of the present application. For the specific implementation details, reference can be made to the above embodiments and will not be elaborated here.

[0237] In addition, it can also be understood that the controller, which is a processing unit included in the processor 110, can be the nerve center and command center of the mobile phone 100. In practical applications, the controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching instructions and executing instructions.

[0238] The wireless communication function of the mobile phone 100 can be implemented through the antenna 1, antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, etc.

[0239] This concludes the introduction to the hardware structure of the mobile phone 100. It should be understood that Figure 10 the mobile phone 100 shown is only an example. In specific implementations, the mobile phone 100 can have more or fewer components than those shown in the figure, can combine two or more components, or can have different component configurations. Figure 10 The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0240] In addition, it should be understood that in order for the user equipment to implement the above functions, it includes the corresponding hardware and / or software modules for executing each function. Combining the algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to exceed the scope of the present application.

[0241] In addition, it should be noted that in actual application scenarios, the location update method provided by the above-mentioned embodiments implemented by the user equipment can also be executed by a chip system included in the user equipment. Based on this, an embodiment of the present application further provides a chip system, which may include a processor. The chip system can be coupled to a memory, so that when the chip system runs, it calls the computer program stored in the memory to implement the steps executed by the above-mentioned user equipment. Among them, the processor in the chip system can be an application processor (such as Figure 10 AP 110A in Figure 10 ), or a non-application processor (such as Modem 110B in

[0242] ).

[0243] In addition, an embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions run on the user equipment, the user equipment is enabled to execute the above-mentioned related method steps to implement the location update method in the above-mentioned embodiments.

[0244] In addition, an embodiment of the present application further provides a computer program product. When the computer program product runs on the user equipment, the user equipment is enabled to execute the above-mentioned related steps to implement the location update method in the above-mentioned embodiments.

[0244] In addition, from the above description, it can be seen that the user equipment, computer-readable storage medium, computer program product or chip provided by the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be elaborated here.

[0245] The above is the case. The above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for location update, characterized in that, Applied to a user equipment, the method includes: When the user equipment changes from a resident first cell to a resident second cell, triggering a location update process, and starting a first timer and a second timer; wherein, the current radio resource control (RRC) state of the user equipment is the idle state, the duration corresponding to the second timer is greater than the duration corresponding to the first timer, the duration corresponding to the first timer is the duration for establishing an RRC connection between the user equipment and the core network through random access, and the duration corresponding to the second timer is the duration for performing the location update process, and the location update process is implemented based on the RRC connection; Within the duration corresponding to the first timer, if the RRC connection is not successfully established, when the first timer times out, turning off the second timer and starting a third timer; wherein, the duration corresponding to the third timer is the duration during which the user equipment cannot perform the location update process since the second timer is turned off; Within the duration corresponding to the third timer, when it is recognized that a preset condition is met, turning off the third timer in advance, re-triggering the location update process, and starting the first timer and the second timer.

2. The method according to claim 1, wherein The turning off the third timer in advance when it is recognized that a preset condition is met within the duration corresponding to the third timer includes: Within the duration corresponding to the third timer, when it is recognized that the signal quality of the second cell becomes better or the user equipment resides in a third cell, turning off the third timer in advance.

3. The method according to claim 1 or 2, characterized in that, The method further includes: When the location update process fails due to the unsuccessful establishment of the RRC connection, not accumulating the triggered location update process into the total number of triggered times corresponding to the location update process.

4. The method according to any one of claims 1 to 3, characterized in that The method further includes: Within the duration corresponding to the third timer, if it is not recognized that the preset condition is met, when the third timer times out, re-triggering the location update process and starting the first timer and the second timer.

5. The method according to any one of claims 1 to 4, characterized in that During the re-triggering of the location update process, the method further includes: When the RRC connection is successfully established and the re-triggered location update process fails, accumulating the triggered location update process into the total number of triggered times corresponding to the location update process; When the total number of triggered times is greater than a preset number of triggered times, starting a fourth timer, and the duration corresponding to the fourth timer is greater than the durations corresponding to the first timer, the second timer, and the third timer respectively; Wherein, within the duration corresponding to the fourth timer, the user equipment cannot perform the location update process.

6. The method according to any one of claims 1 to 5, characterized in that The network modes corresponding to the first cell and the second cell are different; Or, The network modes corresponding to the first cell and the second cell are the same.

7. The method according to any one of claims 1 to 6, characterized in that, When the network mode corresponding to the second cell is the 4G network, the location update process is implemented through a Tracking Area Update (TAU). The first timer is the T300 timer, the second timer is the T3430 timer, and the third timer is the T3411 timer.

8. The method according to any one of claims 1 to 6, characterized in that, When the network mode corresponding to the second cell is the 5G network, the location update process is implemented through a registration process of type Mobility Registration Update (MRU). The first timer is the T300 timer, the second timer is the T3510 timer, and the third timer is the T3511 timer.

9. The method according to any one of claims 5 to 8, characterized in that when the network mode corresponding to the second cell is the 4G network, the fourth timer is the T3402 timer; or when the network mode corresponding to the second cell is the 5G network, the fourth timer is the T3502 timer.

10. The method according to any one of claims 1 to 9, characterized in that, The recognition of meeting the preset conditions includes: when the user equipment is moving fast, it is recognized that the preset conditions are met.

11. A user equipment, characterized in that, The user equipment includes a memory and a processor, and the memory is coupled to the processor; the memory stores program instructions, and when the program instructions are executed by the processor, the user equipment executes the location update method according to any one of claims 1 to 10.

12. A chip system, characterized in that, The chip system includes a processor, and the processor is used to support the user equipment to implement the location update method according to any one of claims 1 to 10.

Images