A tracking area update method and a tracking area update apparatus

Abstract

The application provides a tracking area updating method and device, which is applied to a terminal device and shortens the time length of losing step between the terminal device and a network device. The method comprises the following steps: sending a first updating request to the network device; in the case that no updating acceptance information of the network device is received within a first initial time and the sending number of the first updating request is less than a sending number threshold, determining a first updating time based on the first initial time; resending the first updating request to the network device, and judging whether the tracking area updating is realized according to whether the updating acceptance information of the network device is received within the first updating time; wherein the first updating time is less than the first initial time, and the sending number threshold is an upper limit of the sending number of the first updating request.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and particularly relates to a tracking area updating method and a tracking area updating device. BACKGROUND

[0002] Tracking area updating is a common signaling interaction mode in long term evolution. When a terminal device moves from one tracking area to another tracking area, location registration is re-performed on the new tracking area, that is, a tracking area updating process is initiated to notify a network device to change the location information of the terminal device stored by the network device. This process is tracking area updating.

[0003] However, the above tracking area updating process may cause a long time out-of-sync between the terminal device and the network device. SUMMARY

[0004] The present application provides a tracking area updating method and a tracking area updating device, which shortens the out-of-sync time length between the terminal device and the network device.

[0005] In a first aspect, a tracking area updating method is provided, and the method is applied to a terminal device. The method comprises the following steps: sending a first updating request to a network device; in the case that no updating acceptance information of the network device is received within a first initial time and the sending number of the first updating request is less than a sending number threshold, determining a first updating time based on the first initial time; resending the first updating request to the network device, and judging whether tracking area updating is implemented according to whether the updating acceptance information of the network device is received within the first updating time; wherein the first updating time is less than the first initial time, and the sending number threshold is an upper limit of the sending number of the updating request.

[0006] In the present application, the terminal device sends a first updating request to a network device, and in the case that no updating acceptance information of the network device is received within a first initial time and the sending number of the first updating request is less than a sending number threshold, the terminal device can resend the first updating request to the network device, and judge whether tracking area updating is implemented according to whether the updating acceptance information of the network device is received within a first updating time. The sending number threshold is an upper limit of the sending number of the first updating request, the first updating time is determined based on the first initial time, and the first updating time is less than the first initial time. In other words, the terminal device in the present application can continuously obtain the updated time within the sending number threshold through the sending number of the updating request, so as to shorten the out-of-sync time length between the terminal device and the network device with the increase of the sending number of the updating request.

[0007] Secondly, a terminal device is provided, comprising: a sending module and a processing module, wherein the sending module is configured to send a first update request to a network device; the processing module is configured to, if no update acceptance information is received from the network device within a first initial time and the number of times the first update request is sent is less than a sending count threshold, determine a first update time based on the first initial time; and resend the first update request to the network device, and determine whether to implement a tracking area update based on whether update acceptance information is received from the network device within the first update time; wherein the first update time is less than the first initial time, and the sending count threshold is an upper limit on the number of times the first update request is sent.

[0008] Thirdly, a tracking region update apparatus is provided, including a processor coupled to a memory for executing instructions in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the apparatus further includes a memory. Optionally, the apparatus further includes a communication interface, to which the processor is coupled.

[0009] Fourthly, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method in any possible implementation of the first aspect described above.

[0010] In specific implementation, the processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, gate circuit, flip-flop, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0011] Fifthly, a processing apparatus is provided, including a processor and a memory. The processor is used to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the method in any of the possible implementations of the first aspect described above.

[0012] Optionally, there may be one or more processors and one or more memories.

[0013] Alternatively, the memory can be integrated with the processor, or the memory can be set up separately from the processor.

[0014] In specific implementation, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0015] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0016] The processing device in the fifth aspect above can be a chip. The processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0017] In a sixth aspect, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform the method in any possible implementation of the first aspect.

[0018] In a seventh aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods in any of the possible implementations of the first aspect described above. Attached Figure Description

[0019] Figure 1 This is a schematic diagram illustrating the application scenario provided in the embodiments of this application;

[0020] Figure 2 This is a flowchart of the tracking region update method provided in the embodiments of this application;

[0021] Figure 3 This is a schematic diagram of the system architecture of the terminal device provided in the embodiments of this application;

[0022] Figure 4 This is a flowchart of a tracking region update method provided in an embodiment of this application;

[0023] Figure 5This is a flowchart of a first specific example of a tracking region update method provided in the embodiments of this application;

[0024] Figure 6 This is a flowchart of a second specific example of a tracking region update method provided in the embodiments of this application;

[0025] Figure 7 This is a flowchart of a third specific example of a tracking region update method provided in the embodiments of this application;

[0026] Figure 8 This is a structural block diagram of an example of the tracking region updating device provided in the embodiments of this application;

[0027] Figure 9 This is a schematic diagram of another example of the tracking area update device provided in the embodiments of this application. Detailed Implementation

[0028] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0029] Figure 1 This is a schematic diagram illustrating application scenario 100 provided in an embodiment of this application. For example... Figure 1 As shown, application scenario 100 includes terminal device 101 and network device 102. Tracking area update is a commonly used signaling interaction mode in Long Term Evolution (LTE). When terminal device 101 moves from one tracking area to another, it re-registers its location in the new tracking area, initiating a tracking area update process to notify network device 102 to change the location information of the terminal device it stores. This process is called tracking area update.

[0030] However, the above-mentioned tracking area update process may cause a prolonged period of synchronization loss between terminal devices and network devices.

[0031] Figure 2 A flowchart of a tracking region update method 200 provided in this application. Figure 2 As shown, the method 200 includes the following steps:

[0032] S201, the terminal device sends an update request to the network device. Correspondingly, the network device receives the update request from the terminal device.

[0033] It should be understood that, according to the 3GPP specification, after the terminal device initiates the first update request, it can set the tracking area update counter to 1 and start the T3430 timer (15s).

[0034] S202, the network device sends an update acceptance message to the terminal device. Correspondingly, the terminal device receives the update acceptance message from the network device.

[0035] S203, the terminal device sends a tracking area update completion message to the network device. Correspondingly, the network device receives the tracking area update completion message from the terminal device.

[0036] Optionally, corresponding to S202 above, when the T3430 timer expires (i.e., more than 15 seconds), the terminal device will increment the tracking area update counter by 1 and send an update request to the network device again.

[0037] It should be understood that if there is a network anomaly and the network device does not respond to the terminal device's update request, the terminal device will attempt to initiate 5 update requests. If the terminal device does not receive the update acceptance information from the network device after the 5th update request (i.e., the tracking area update counter is 5) and the T3430 times out (i.e., more than 15 seconds), there will be a 75-second out-of-sync period between the terminal device and the network device, making it impossible for the terminal to perform normal data services.

[0038] In view of this, embodiments of this application provide a tracking area update method and a tracking area update apparatus. A terminal device sends a first update request to a network device. If it does not receive update acceptance information from the network device within a first initial time period, and the number of times the first update request is sent is less than a sending count threshold, the terminal device can resend the first update request to the network device. Based on whether update acceptance information is received from the network device within the first update time period, it is determined whether a tracking area update has been achieved. The sending count threshold is an upper limit on the number of times the first update request can be sent, and the first update time is determined based on the first initial time, and this first update time is less than the first initial time. In other words, the terminal device in this application can continuously obtain the updated time within the sending count threshold by adjusting the number of update request transmissions, thereby reducing its time out of sync with the network device as the number of update request transmissions increases.

[0039] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, 5th generation (5G) system, or new radio (NR) or other evolved communication systems.

[0040] It should also be understood that the terminal device in the embodiments of this application may also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device involved in the embodiments of this application can be a device that provides voice / data connectivity to users, such as a handheld device with wireless connection function, vehicle-mounted device, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a mobile network (PLMN), etc., are not limited to this in the embodiments of this application.

[0041] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0042] Furthermore, in this application embodiment, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. The terminal device in this application can also be an on-board unit, on-board module, on-board component, on-board chip, or on-board unit built into a vehicle as one or more components or units. The vehicle can implement the method of this application through the built-in on-board unit, on-board module, on-board component, on-board chip, or on-board unit. Therefore, the embodiments of this application can be applied to vehicle networking, such as vehicle-to-everything (V2X), long-term evolution-vehicle (LTE-V) communication technology, and vehicle-to-vehicle (V2V) communication.

[0043] For example, Figure 3 This is a schematic diagram of the system architecture of a terminal device provided in an embodiment of this application.

[0044] like Figure 3 As shown, the terminal device includes a processor 310, a transceiver 320, and a display unit 370. The display unit 370 may include a display screen.

[0045] Optionally, the terminal device may also include a memory 330. The processor 310, transceiver 320 and memory 330 can communicate with each other through an internal connection path to transmit search data. The memory 330 is used to store computer programs, and the processor 310 is used to call and run the computer programs from the memory 330.

[0046] The processor 310 and memory 330 can be combined into a single processing device, but more commonly they are separate components. The processor 310 executes the program code stored in the memory 330 to achieve the aforementioned functions. In specific implementations, the memory 330 can be integrated into the processor 310, or it can be independent of the processor 310.

[0047] In addition, to further enhance the functionality of the terminal device, it may also include one or more of an input unit 360, an audio circuit 380, and a sensor 301.

[0048] Optionally, the terminal device may also include a power supply 350 for providing power to various devices or circuits in the terminal device.

[0049] Understandable Figure 3 The operations and / or functions of each module in the terminal device shown are respectively for implementing the corresponding processes in the following method embodiments. For details, please refer to the descriptions in the following method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0050] Understandable Figure 3 The processor 310 in the terminal device shown may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0051] The processor 310 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. This memory can store instructions or data that the processor 310 has just used or that are used repeatedly. If the processor 310 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 310, and thus improves the efficiency of the system.

[0052] In some embodiments, the processor 310 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0053] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the terminal device. In other embodiments of this application, the terminal device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0054] Understandable Figure 3 The power supply 350 shown is used to supply power to the processor 310, memory 330, display unit 370, input unit 360, and transceiver 320, etc.

[0055] Transceiver 320 can provide solutions for wireless communication applications on terminal devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. Transceiver 320 can be one or more devices integrating at least one communication processing module.

[0056] The terminal device implements display functions through a GPU, a display unit 370, and an application processor. The GPU is a microprocessor for image processing, connecting the display unit 370 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. The processor 310 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0057] Display unit 370 is used to display images, videos, etc. Display unit 370 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc.

[0058] The memory 330 can be used to store computer executable program code, which includes instructions. The memory 330 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the terminal device (such as search data), etc. Furthermore, the memory 330 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 310 executes various functional applications and data processing of the terminal device by running instructions stored in the memory 330 and / or instructions stored in memory disposed in the processor.

[0059] Terminal devices can implement audio functions through audio circuitry 380 and application processors, such as music playback and recording.

[0060] The network devices involved in the embodiments of this application may include access and mobile management function (AMF) devices, transmission reception points (TRPs), evolved NodeBs (eNBs or eNodeBs) in LTE systems, home base stations (e.g., home evolved NodeBs or home Node Bs, HNBs), base band units (BBUs), and radio controllers in cloud radio access network (CRAN) scenarios. Alternatively, the access network device may be a relay station, access point, vehicle-mounted device, wearable device, or access network device in a 5G network or an access network device in a future evolved PLMN network. It may be an access point (AP) in a WLAN, a gNB in ​​a new radio (NR) system, or a satellite base station in a satellite communication system. The embodiments of this application are not limited to these.

[0061] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0062] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0063] It should be noted that, in this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0064] Furthermore, "at least one" refers to one or more, while "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0065] To make the objectives and technical solutions of this application clearer and more intuitive, a tracking region update method and tracking region update apparatus provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0066] Figure 4 This is a schematic flowchart illustrating a tracking region update method 400 provided in an embodiment of this application. Method 400 can be applied to the above... Figure 1 The application scenario 100 shown can be applied to other scenarios as well, and this application does not limit the scope of application. For example... Figure 4 As shown, the method 400 may include the following steps:

[0067] S401, the terminal device sends the first update request to the network device.

[0068] It should be understood that this first update request can also be referred to as the first tracking area update request.

[0069] For example, when a terminal device moves from one tracking area to another, it can send the aforementioned first update request in the new tracking area.

[0070] S402, if the terminal device does not receive update acceptance information from the network device within the first initial time and the number of times the first update request is sent is less than the sending count threshold, a first update time is determined based on the first initial time. Wherein, the first update time is less than the first initial time, and the sending count threshold is the upper limit for the number of times the first update request can be sent.

[0071] It should be understood that the first initial time can also be called the first time out of sync, and the first update time can also be called the first update out of sync.

[0072] For example, after the terminal device sends the first update request to the network device, the terminal device can set the tracking area update counter to 1, start the T3430 timer, and initialize the start T3430 timer to a first initial time, and then determine whether the first initial time has been exceeded based on the T3430.

[0073] It should be understood that the timers shown above are merely exemplary and are not intended to limit the scope of this application.

[0074] S403, the terminal device resends the first update request to the network device, and determines whether to implement the tracking area update based on whether it receives the update acceptance information from the network device within the first update time.

[0075] It should be understood that the terminal device can determine to implement the tracking area update when it receives the update acceptance information from the network device within the aforementioned first update time.

[0076] In this application, a terminal device sends a first update request to a network device. If it does not receive an update acceptance message from the network device within a first initial time period, and the number of times the first update request has been sent is less than a sending count threshold, the terminal device can resend the first update request to the network device. Based on whether it receives an update acceptance message from the network device within the first update time period, it determines whether a tracking area update has been achieved. Here, the sending count threshold is the upper limit on the number of times the first update request can be sent, and the first update time is determined based on the first initial time, and this first update time is less than the first initial time. In other words, the terminal device in this application can continuously obtain the updated time within the sending count threshold by adjusting the number of update request transmissions, thereby reducing its time out of sync with the network device as the number of update request transmissions increases.

[0077] Optionally, following S403 above, if no update acceptance information is received from the network device within the first update time and the number of times the first update request is resent is less than the number of times it is sent, the terminal device may resend the first update request again to implement the tracking area update method provided in this application.

[0078] Figure 5 This is a schematic flowchart of the tracking region update method 500 provided in an embodiment of this application. Figure 5 As shown, the method 500 may include the following steps:

[0079] S501, when the terminal device determines that it has not received the update acceptance information from the network device within the first update time, it determines whether the number of times the first update request is resent is less than the number of times it is sent.

[0080] For example, the aforementioned first update time can be calculated based on the following formula:

[0081] T1′=max(T1-n*3s,3s)

[0082] Where T1′ is the first update time, T1 is the first initial time, n is the number of times the first update request is sent, and s is the time unit in seconds.

[0083] It should be understood that the above formula is merely exemplary and is not intended to limit the scope of this application.

[0084] S502, if it is determined that the number of times the first update request is resent is less than the number of times it is sent, the terminal device obtains a new first update time based on the first initial time.

[0085] It should be understood that this new first update time is less than the aforementioned first update time.

[0086] It should also be understood that the aforementioned threshold for the number of transmissions can be represented by N, and N = 5. In other words, the terminal device can execute the above-mentioned S502 if it determines that the number of times the aforementioned retransmitted update request has been sent is less than 5.

[0087] For example, the new first update time can be calculated using the following formula.

[0088] T1″ = max(T1 - n*3s, 3s)

[0089] Where T1″ is the new first update time, T1 is the first initial time, n can represent the number of times the first update request is sent again, and s is the time unit in seconds.

[0090] It should be understood that, to distinguish it from the number of times the first update request was sent, when the number of times the first update request was sent is n, the number of times the resent first update request was sent can also be represented by n′. Furthermore, when the first update request and the resent first update request are sent consecutively, n′ = n + 1, and n′ <N。

[0091] It should be understood that this formula is merely exemplary and is not intended to limit the scope of this application.

[0092] S503, the terminal device resends the first update request to the network device, and determines whether to implement the tracking area update based on whether it receives the update acceptance information from the network device within the new first update time.

[0093] It should be understood that the terminal device may determine to implement the tracking area update if it receives the update acceptance information from the network device within the aforementioned new first update time. Alternatively, if it does not receive the update acceptance information from the network device within the aforementioned new first update time, and the number of times the first update request is resent is less than the aforementioned number of resentments threshold, it may continue to determine the new time and resend the first update request again to implement the tracking area update method provided in this application.

[0094] Table 1 shows the determined time (also known as the time of loss of synchronization) for the first update request within a range of less than or equal to the number of sends.

[0095] Table 1

[0096]

[0097] As shown in Table 1, when the transmission threshold N=5, the terminal device can continuously send a maximum of 5 first update requests without receiving update acceptance information from the network device. These are the first first update request sent (n=1), the second first update request sent (n=2), the third first update request sent (n=3), the fourth first update request sent (n=4), and the fifth first update request sent (n=5).

[0098] For example, as shown in Table 1, the terminal device can execute a first update request (n=1) and determine to implement the tracking area update when it receives the update acceptance information from the network device within 15 seconds.

[0099] It should be understood that, corresponding to the description in the above embodiments, the 15s is the first initial time mentioned above, which is the initial preset time.

[0100] For example, if the terminal device determines that it has not received an update acceptance message from the network device within 15 seconds, it may continue to execute the first update request (n=2), and if it receives an update acceptance message from the network device within 12 seconds, it determines that the tracking area update is to be implemented.

[0101] It should be understood that, corresponding to the description in the above embodiments, the 12s can also be called the first update time, which is calculated based on the first initial time of 15s and the number of times the first update request (n=1) is sent, such as 12s=max(15s-1*3s, 3s).

[0102] For example, if the terminal device determines that it has not received an update acceptance message from the network device within 12 seconds, it may continue to execute the first update request (n=3), and if it receives an update acceptance message from the network device within 9 seconds, it determines that the tracking area update has been implemented.

[0103] It should be understood that, corresponding to the description in the above embodiments, the 9s can also be called the new first update time, which is calculated based on the first initial time of 15s and the number of times the first update request (n=2) is sent, such as 9s=max(15s-2*3s, 3s).

[0104] For example, if the terminal device determines that it has not received an update acceptance message from the network device within 9 seconds, it may continue to execute the first update request (n=4), and if it receives an update acceptance message from the network device within 6 seconds, it determines that the tracking area update is to be implemented.

[0105] It should be understood that the 6s can be calculated based on the first initial time of 15s and the number of times the first update request (n=3) is sent, such as 6s=max(15s-3*3s, 3s).

[0106] For example, if the terminal device determines that it has not received an update acceptance message from the network device within 6 seconds, it may continue to execute the first update request (n=5), and if it receives an update acceptance message from the network device within 3 seconds, it determines that the tracking area update will be implemented.

[0107] It should be understood that the 3s can be calculated based on the first initial time of 15s and the number of times the first update request (n=4) is sent, such as 3s=max(15s-4*3s, 3s).

[0108] In summary, Table 1 shows that the time of loss of synchronization between the terminal device and the network device in this application can be shortened as the number of times the first update request is sent increases.

[0109] Furthermore, when the terminal device executes the first update request (n=5) and receives the update acceptance information from the network device within 3 seconds, and determines that the tracking area update has been achieved, even if the number of times the first update request is sent reaches the upper limit (5 times), the time of loss of synchronization between the terminal device and the network device can be shortened as the number of times the first update request is sent increases, so that the maximum total time of loss of synchronization is 45 seconds, which is 30 seconds shorter than the 75 seconds of the prior art, and the time overhead of loss of synchronization is reduced by 40%.

[0110] It should be understood that this application can also send more update requests within the existing 75s timeframe, which not only shortens the time the terminal device and network device lose synchronization, but also improves the success rate of tracking area updates. That is, if the first update request (n=5) is executed and no update acceptance information is received from the network device within 3s, the sending of new update requests can continue.

[0111] In one possible implementation, the terminal device can send multiple rounds of update requests, such as three rounds of update requests, even without receiving update acceptance information from the network device.

[0112] It should be understood that the number of times to send and the initial time for each of the three rounds of update requests mentioned above may be different.

[0113] For example, the threshold number of times the update request is sent in the first round of update requests can be 5 times as mentioned in the above embodiments, and the initial time can be the first initial time of 15 seconds as mentioned in the above embodiments. That is, the specific details of the first round of update requests can be found in the above embodiments. Figure 5 The description will not be repeated here to avoid repetition. Next... Figure 5 The corresponding first round of update requests will then be processed through... Figure 6 and Figure 7 In the cases of the second and third update requests, the tracking area update method provided in this application is described in detail.

[0114] For example, in order to distinguish between update requests in different rounds, this application will refer to the update request included in the first round of update requests as the first update request, the update request included in the second round of update requests as the second update request, and the update request included in the third round of update requests as the third update request.

[0115] It should be understood that the above naming is merely exemplary and is not intended to limit the scope of this application.

[0116] Figure 6 This is a schematic flowchart of the tracking region update method 600 provided in an embodiment of this application. Figure 6 As shown, the method 600 may include the following steps:

[0117] S601, if no update acceptance information is received from the network device under the first update request, the terminal device sends a second update request to the network device.

[0118] It should be understood that this second update request can also be referred to as the second tracking area update request.

[0119] For example, if the terminal device does not receive an update acceptance message from the network device within 45 seconds as shown in Table 1 above, it may execute S601 as described above.

[0120] S602, the terminal device determines the second initial time and the second transmission count threshold based on the number of abnormal occurrences in the current cell.

[0121] It should be understood that the second initial time can be the upper limit of the time (i.e., the time of loss of synchronization) to wait for the network device to receive the update information after the second update request is sent once in the second round of update requests.

[0122] It should be understood that the aforementioned second sending threshold is the sending threshold for the second update request included in the second round of update requests.

[0123] For example, the aforementioned second initial time and second transmission number threshold can be calculated using the following formula:

[0124] T2 = T1 - m * 5s, N = 5 - m - 1

[0125] Where T2 is the second initial time, T1 is the first initial time, m is the number of anomalies in the current cell, N is the second transmission threshold, and s is the time unit in seconds.

[0126] For example, in the case of the second round of update requests, the number of exceptions m=1, which means T2=10 and N=3 can be calculated. That is, after the terminal device sends the second update request to the network device, the terminal device can set the tracking area update counter to 1, start the T3430 timer, and initialize the start timer to the second initial time (i.e., 10s). Then, based on the T3430 timer, it can determine whether the second initial time has been exceeded.

[0127] It should be understood that the timers shown above are merely exemplary and are not intended to limit the scope of this application.

[0128] It should also be understood that the above-mentioned abnormal number is used to indicate the number of times that multiple rounds of update requests have been initiated in the current cell without receiving update acceptance information. Each round of update requests includes update requests with a maximum number of transmissions equal to the above-mentioned transmission threshold. The current cell is a cell covered by the above-mentioned network device.

[0129] In one possible implementation, the terminal device can obtain the number of abnormal occurrences of the current cell through a blacklist.

[0130] It should be understood that the current cell may be placed on a blacklist if no update acceptance information is received in the first round of update request transmissions, in order to record the number of anomalies in the current cell. The blacklist also includes the cell information of the current cell, such as the physical cell identifier (PCI) and absolute radio-frequency channel number (Arfcn). Correspondingly, before S602 above, the terminal device can determine whether the current cell is on the blacklist. If it is determined that the current cell is on the blacklist, the terminal device can obtain the number of anomalies in the current cell and execute S602 above.

[0131] S603, if no update acceptance information is received from the network device during the second initial time period and the number of times the second update request is sent is less than the second sending number threshold, the terminal device obtains the second update time based on the second initial time.

[0132] It should be understood that this second update time is shorter than the aforementioned second initial time.

[0133] For example, the second update time mentioned above can be calculated based on the following formula:

[0134] T2′=max(T2-n*3s,3s)

[0135] Where T2′ is the second update time, T2 is the second initial time, n is the number of times the second update request is sent, and s is the time unit in seconds. That is, when the terminal device determines that it has not received update acceptance information from the network device within the second initial time period and the number of times the second update request is sent is less than the second sending threshold, the terminal device can increment the tracking area update counter by 1, i.e., 1+1=2, and start the T3430 timer, updating the start of the T3430 timer to the second update time, and then determine whether the second update time has been exceeded based on the T3430 timer.

[0136] It should be understood that the formulas and timers shown above are merely exemplary and are not intended to limit the scope of this application.

[0137] S604, the terminal device resends the second update request to the network device, and determines whether the tracking area update is achieved based on whether it receives the update acceptance information from the network device within the second update time.

[0138] Table 2 shows the determined time (also known as the time of loss of synchronization) for a second update request that is less than or equal to the second sending number threshold.

[0139] Table 2

[0140]

[0141] As shown in Table 2, when the second sending threshold N=3, the terminal device can send a maximum of 3 second update requests consecutively without receiving update acceptance information from the network device. These are the first second update request sent (n=1 in the table), the second second update request sent (n=2 in the table), and the third second update request sent (n=3 in the table).

[0142] For example, as shown in Table 2, the terminal device can execute a second update request (n=1) and determine to implement the tracking area update when it receives the update acceptance information from the network device within 10 seconds.

[0143] It should be understood that, in accordance with the description in the above embodiments, the 10s is the second initial time mentioned above, which is calculated based on the first initial time and the number of anomalies, i.e., 10s = 15s - 1 * 5s.

[0144] For example, if the terminal device determines that it has not received an update acceptance message from the network device within 10 seconds, it may continue to execute the second update request (n=2), and if it receives an update acceptance message from the network device within 7 seconds, it determines that the tracking area update is to be implemented.

[0145] It should be understood that, corresponding to the description in the above embodiments, the 7s can also be called the second update time, which is calculated based on the second initial time 10s and the number of times the second update request (n=1) is sent, such as 7s=max(10s-1*3s, 3s).

[0146] For example, if the terminal device determines that it has not received an update acceptance message from the network device within 7 seconds, it may continue to execute the second update request (n=3), and if it receives an update acceptance message from the network device within 4 seconds, it determines that the tracking area update is to be implemented.

[0147] It should be understood that, corresponding to the description in the above embodiments, the 9s can also be called the new second update time, which is calculated based on the second initial time 10s and the number of times the second update request (n=2) is sent, such as 4s=max(10s-2*3s, 3s).

[0148] In summary, Table 2 shows that the time of loss of synchronization between the terminal device and the network device in this application can be shortened as the number of times the second update request is sent increases.

[0149] Furthermore, when the terminal device executes the second update request (n=3) and receives the update acceptance information from the network device within 4 seconds, and determines that the tracking area update has been achieved, even if the number of times the second update request is sent reaches the upper limit of the second round of update request sending (3 times), since the time of desynchronization between the terminal device and the network device can be shortened as the number of times the second update request is sent increases, the final total time of desynchronization in the first round of update request and the second round of update request is 66 seconds, which is 9 seconds shorter than the 75 seconds of the prior art, reducing the time loss of desynchronization by 12%, and increasing the number of update request sending by 3 times.

[0150] Figure 7 This is a schematic flowchart of the tracking region update method 700 provided in an embodiment of this application. Figure 7 As shown, the method 700 may include the following steps:

[0151] S701, if no update acceptance information is received from the network device under the second update request, the terminal device sends a third update request to the network device.

[0152] It should be understood that this third update request can also be referred to as the third tracking area update request.

[0153] For example, if the terminal device has not received the update acceptance information from the network device within the 21 seconds shown in Table 2 above, it may execute the above S701.

[0154] S702, the terminal device determines the third initial time third transmission count threshold based on the number of abnormal occurrences in the current cell.

[0155] It should be understood that the third initial time can be the upper limit of the time (i.e., the time of loss of synchronization) to wait for the network device to receive the update information after the third update request is sent once in the third round of update requests.

[0156] For example, the aforementioned third initial time and third transmission count threshold can be calculated using the following formula:

[0157] T3 = T1 - m * 5s, N = 5 - m - 1

[0158] Where T3 is the third initial time, T1 is the first initial time, m is the number of anomalies in the current cell, N is the third transmission threshold, and s is the time unit in seconds.

[0159] For example, in the case of the third round of update requests, the number of exceptions m=2, which means T3=5 and N=2 can be calculated. That is, after the terminal device sends the second update request to the network device, the terminal device can set the tracking area update counter to 1, start the T3430 timer, and initialize the start T3430 timer to the third initial time (i.e., 5s), and then determine whether the above-mentioned third initial time has been exceeded based on the T3430.

[0160] It should be understood that the timers shown above are merely exemplary and are not intended to limit the scope of this application.

[0161] It should also be understood that the above-mentioned abnormal number is used to indicate the number of times that multiple rounds of update requests were initiated in the current cell without receiving update acceptance information. Each round of update requests includes update requests with a maximum number of transmissions equal to the above-mentioned transmission threshold. The current cell is a cell covered by the above-mentioned network device.

[0162] In one possible implementation, the terminal device can obtain the number of abnormal occurrences of the current cell through a blacklist.

[0163] It should be understood that the current cell may be placed on the blacklist if no update acceptance information is received in the first round of update request sending, so as to record the number of anomalies in the current cell. Correspondingly, before S702 above, the terminal device can determine whether the current cell is in the blacklist, so that if it is determined that the current cell is placed on the blacklist, the number of anomalies in the current cell can be obtained, and S702 above can be executed.

[0164] S703, if no update acceptance information is received from the network device during the third initial time period and the number of times the third update request is sent is less than the third sending number threshold, the terminal device obtains the third update time based on the third initial time.

[0165] It should be understood that this third update time is less than the aforementioned third initial time.

[0166] For example, the aforementioned third update time can be calculated based on the following formula:

[0167] T3′=max(T3-n*3s,3s)

[0168] Where T3′ is the aforementioned third update time, T3 is the aforementioned third initial time, n is the number of times the aforementioned third update request is sent, and s is the time unit in seconds. That is, when the terminal device determines that it has not received update acceptance information from the network device within the aforementioned third initial time period, and the number of times the third update request is sent is less than the aforementioned third sending threshold, the terminal device can increment the tracking area update counter by 1, i.e., 1+1=2, and simultaneously start the T3430 timer, updating the start of the T3430 timer to the third update time, and then determine whether the aforementioned third update time has been exceeded based on the T3430.

[0169] It should be understood that the formulas and timers shown above are merely exemplary and are not intended to limit the scope of this application.

[0170] S704, the terminal device resends the aforementioned third update request to the network device, and determines whether the tracking area update is achieved based on whether it receives the update acceptance information from the network device within the third update time.

[0171] Table 3 shows the determined time (also known as the time of loss of synchronization) for the third update request within the third sending number threshold of less than or equal to the third sending number threshold.

[0172] Table 3

[0173]

[0174] As shown in Table 3, when the third sending threshold N=2, the terminal device can send a maximum of 2 third update requests consecutively without receiving update acceptance information from the network device. These are the first third update request sent (i.e., the third update request in the table (n=1)) and the second third update request sent (i.e., the third update request in the table (n=2)).

[0175] For example, as shown in Table 2, the terminal device can execute a third update request (n=1) and determine to implement the tracking area update when it receives the update acceptance information from the network device within 5 seconds.

[0176] It should be understood that, in accordance with the description in the above embodiments, the 5s is the third initial time mentioned above, which is calculated based on the first initial time and the number of anomalies, i.e., 5s = 15s - 2 * 5s.

[0177] For example, if the terminal device determines that it has not received an update acceptance message from the network device within 5 seconds, it may continue to execute the third update request (n=2), and if it receives an update acceptance message from the network device within 3 seconds, it determines to implement the tracking area update.

[0178] It should be understood that, corresponding to the description in the above embodiments, the 3s can also be called the third update time, which is calculated based on the third initial time 5s and the number of times the third update request (n=1) is sent, such as 3s=max(5s-1*3s, 3s).

[0179] In summary, Table 3 shows that the time of out-of-sync between the terminal device and the network device in this application can be shortened as the number of third update requests increases.

[0180] Furthermore, when the terminal device executes the third update request (n=2) and receives the update acceptance information from the network device within 3 seconds, and it is determined that the tracking area update has been achieved, even if the number of times the third update request is sent reaches the upper limit of the third round of update request sending (2 times), since the time of loss of synchronization between the terminal device and the network device can be shortened as the number of times the third update request is sent increases, the final total time of loss of synchronization in the first round of update request, the second round of update request and the third round of update request is up to 74 seconds, which is 1 second shorter than the 75 seconds of the prior art, reducing the time loss of synchronization overhead by 1.3%, and increasing the number of update request sending by 5 times.

[0181] Optionally, after receiving the update acceptance information from the aforementioned network device and determining that the tracking area update has been implemented, the terminal device may also update the number of anomalies for the current cell in the blacklist if it is determined that the current cell has been placed in the blacklist, so as to obtain a new number of anomalies (also known as a second number of anomalies).

[0182] For example, corresponding to the above Figure 6 When a terminal device sends a second update request for any number of times in the second round of update requests and receives an update acceptance message from the network device, it can update the abnormal count m = 1 of the current cell that has been placed in the current blacklist to a new abnormal count m′ = m - 1 = 0.

[0183] For example, corresponding to the above Figure 7 The terminal device can also update the abnormal count m=2 of the current cell that has been placed in the current blacklist to a new abnormal count m′=2-1=1 when it sends the third update request for any number of times in the third round of update requests and receives the update acceptance information from the network device.

[0184] Optionally, the terminal device can also determine whether to remove the abnormal cell from the blacklist based on the number of abnormal occurrences in the current cell.

[0185] For example, if the number of anomalies is determined to be 0, the terminal device can remove the current cell from the blacklist, such as when the new number of anomalies m′ = m-1 = 0 obtained from the update.

[0186] For example, the terminal device may also keep the current cell in the blacklist if it determines that the number of anomalies is not equal to 0, such as when the new number of anomalies m′=2-1=1 obtained by the above update is still greater than 0.

[0187] Optionally, the terminal device can also update the current cell's placement time in the blacklist (also known as the first placement time) and obtain a new placement time (also known as the second placement time).

[0188] In one possible scenario, the terminal device can update the placement time of the current cell in the blacklist after obtaining a new number of anomalies for the current cell, thus obtaining the aforementioned new placement time.

[0189] In another possible scenario, if the terminal device has been in the blacklist for a longer period than the preset placement time, it can update the placement time to obtain the new placement time mentioned above.

[0190] In one possible implementation, if the placement time exceeds the preset placement time, the terminal device can update the new number of anomalies based on the current number of anomalies in the cell, and then update the placement time based on the new number of anomalies (also known as the second number of anomalies) to obtain a new placement time (also known as the second placement time).

[0191] For example, the new placement time mentioned above can be calculated using the following formula:

[0192] t′=m′*t

[0193] Where t′ is the new placement time, m′ is the new number of anomalies in the current cell, m′=m-1 or m′=m-1, where m is the number of anomalies in the current cell and m′≠0, and t is the placement time, which can be preset.

[0194] It should be understood that the various embodiments described above can also be coupled to each other, and this application does not limit this. Furthermore, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0195] The above text combines Figure 1 to Figure 7 The tracking region update method of the embodiments of this application is described in detail below. Figure 8 and Figure 9 This application describes in detail the tracking area update apparatus according to embodiments of the present application.

[0196] Figure 8This application illustrates a tracking area update apparatus 800 according to an embodiment of the present application. The tracking area update apparatus 800 includes a sending module 801 and a processing module 802.

[0197] The sending module 801 is configured to: send a first update request to the network device; the processing module 802 is configured to: determine a first update time based on the first initial time if no update acceptance information is received from the network device within a first initial time and the number of times the first update request is sent is less than a sending number threshold; and resend the first update request to the network device, and determine whether to implement a tracking area update based on whether update acceptance information is received from the network device within the first update time; wherein the first update time is less than the first initial time, and the sending number threshold is the upper limit of the number of times the first update request is sent.

[0198] Optionally, the processing module 802 is configured to: when receiving update acceptance information from the network device during the first update time, determine to implement the tracking area update.

[0199] Optionally, the first update time is calculated based on the following formula: T1′=max(T1-n*3s,3s), where T1′ is the first update time, T1 is the first initial time, n is the number of times the first update request is sent, and s is the time unit in seconds.

[0200] Optionally, the processing module 802 is configured to: place the current cell of the terminal device in a blacklist if no update acceptance information is received from the network device within the first update time and the number of times the first update request is resent is equal to the number of times it is sent; or, when no update acceptance information is received from the network device within the first update time, the number of times the first update request is resent is equal to the number of times it is sent, and the current cell is already placed in the blacklist, update the number of abnormal occurrences of the cell in the blacklist; wherein the blacklist contains cell information and the number of abnormal occurrences of the current cell, the number of abnormal occurrences being used to indicate the number of times multiple rounds of update requests have been initiated without receiving update acceptance information under the current cell, each round of update requests includes an update request with a maximum number of times it is sent equal to the number of times it is sent; the current cell is a cell covered by the network device.

[0201] Optionally, the processing module 802 is configured to: obtain a new first update time based on the first initial time when no update acceptance information is received from the network device within the first update time and the number of times the first update request is resent is less than the number of times it is sent; resend the first update request to the network device again, and determine whether to implement the tracking area update based on whether the update acceptance information is received from the network device within the new first update time; wherein the new first update time is less than the first update time.

[0202] Optionally, the processing module 802 is configured to: send a second update request to the network device; determine a second initial time and a second transmission count threshold based on the number of abnormal occurrences of the current cell in the blacklist; when no update acceptance information is received from the network device within the second initial time period and the number of transmissions of the second update request is less than the second transmission count threshold, obtain the second update time based on the second initial time; resend the second update request to the network device, and determine whether to implement tracking area update based on whether update acceptance information is received from the network device within the second update time; wherein the second update time is less than the second initial time.

[0203] Optionally, the second initial time and the second transmission count threshold are calculated using the following formula: T2 = T1 - m * 5s, N = 5 - m - 1, where T2 is the second initial time, T1 is the first initial time, m is the number of anomalies in the current cell, N is the second transmission count threshold, and s is the time unit in seconds.

[0204] Optionally, the processing module 802 is configured to: when it is determined that the current cell has been placed in the blacklist, update the number of anomalies of the current cell to obtain a second number of anomalies; based on the second number of anomalies, determine whether to remove the current cell from the blacklist; wherein the blacklist carries cell information and anomaly count of the current cell, the number of anomalies being used to indicate the number of times multiple rounds of update requests have been initiated in the current cell without receiving update acceptance information, and each round of update requests includes an update request with a maximum number of transmissions equal to the threshold number of transmissions.

[0205] Optionally, the processing module 802 is configured to: remove the current cell from the blacklist if it is determined that the second abnormal count is equal to 0; or, keep the current cell in the blacklist if it is determined that the second abnormal count is not equal to 0. Optionally, the processing module 802 is configured to: update the placement time of the current cell in the blacklist to obtain the second placement time.

[0206] Optionally, the processing module 802 is configured to: update the placement time of the current cell in the blacklist and obtain the second placement time when the second number of abnormalities of the current cell is obtained; or, update the placement time and obtain the second placement time when the placement time exceeds a preset placement time.

[0207] Optionally, the processing module 802 is configured to: when the placement time exceeds a preset placement time, update the second abnormal number based on the abnormal number of the current cell; update the placement time based on the second abnormal number to obtain the second placement time.

[0208] Optionally, the second placement time is calculated using the following formula: t′=m′*t, where t′ is the second placement time, m′ is the second anomaly count of the current cell, and t is the placement time.

[0209] It should be understood that the tracking area update device 800 here is embodied in the form of a functional module. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors, etc.) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the tracking area update device 800 can be specifically the terminal device in the above embodiments, or the functions of the terminal device in the above embodiments can be integrated into the tracking area update device 800. The tracking area update device 800 can be used to execute the various processes and / or steps corresponding to the terminal device in the above method embodiments; to avoid repetition, these will not be described again here.

[0210] The aforementioned tracking area update device 800 has the function of implementing the corresponding steps performed by the terminal device in the aforementioned method; the aforementioned function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned function. In embodiments of this application, Figure 8 The tracking region update device 800 can also be a chip or a chip system, such as a system on chip (SoC).

[0211] Figure 9Another tracking region update apparatus 900 provided in this application embodiment is illustrated. The tracking region update apparatus 900 includes a processor 901, a memory 902, a communication interface 903, and a bus 904. The memory 902 is used to store instructions, and the processor 901 is used to execute the instructions stored in the memory 902. The processor 901, the memory 902, and the communication interface 903 are interconnected via the bus 904.

[0212] The processor 901 is configured to: send a first update request to a network device; if no update acceptance information is received from the network device within a first initial time and the number of times the first update request is sent is less than a sending count threshold, determine a first update time based on the first initial time; and resend the first update request to the network device, and determine whether to implement a tracking area update based on whether update acceptance information is received from the network device within the first update time; wherein the first update time is less than the first initial time, and the sending count threshold is an upper limit on the number of times the first update request is sent.

[0213] It should be understood that the tracking area update device 900 can be specifically the terminal device in the above embodiments. The functions of the terminal device in the above embodiments can be integrated into the tracking area update device 900. The tracking area update device 900 can be used to execute the various steps and / or processes corresponding to the terminal device in the above method embodiments.

[0214] Optionally, the memory 902 may include read-only memory and random access memory, and provide instructions and data to the processor 901. A portion of the memory 902 may also include non-volatile random access memory. For example, the memory 902 may also store device type information. The processor 901 can be used to execute instructions stored in the memory, and when the processor executes the instructions, the processor 901 can perform the various steps and / or processes corresponding to the terminal device in the above method embodiments.

[0215] It should be understood that, in the embodiments of this application, the processor may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0216] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or as a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor executes the instructions in the memory, combining them with its hardware to complete the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0217] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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, but such implementation should not be considered beyond the scope of this application.

[0218] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0219] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0220] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0221] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0222] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or terminal device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0223] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of protection of the above claims.

Claims

1. A tracking region update method, characterized in that, Applied to a terminal device, the method includes: Send the first update request to the network device; If no update acceptance information is received from the network device within the first initial time period, and the number of times the first update request is sent is less than the number of times it is sent, the first update time is determined based on the first initial time period. The first update request is resent to the network device, and the tracking area update is determined based on whether the update acceptance information from the network device is received within the first update time. Wherein, the first update time is less than the first initial time, and the sending number threshold is the upper limit of the number of times the first update request can be sent.

2. The method according to claim 1, characterized in that, The step of resending the first update request to the network device and determining whether to implement the tracking area update based on whether the update acceptance information from the network device is received within the first update time includes: When the update acceptance information of the network device is received within the first update time, it is determined to implement the tracking area update.

3. The method according to claim 1 or 2, characterized in that, The first update time is calculated based on the following formula: in, For the first update time, For the first initial time, The number of times the first update request was sent, and, The unit of time is seconds.

4. The method according to claim 1, characterized in that, The method further includes: If no update acceptance information is received from the network device within the first update time, and the number of times the first update request is resent is equal to the number of times it is sent, the current cell of the terminal device is placed in the blacklist; or, If no update acceptance information is received from the network device within the first update time, the number of times the first update request is resent is equal to the number of times it is sent, and the current cell is already placed in the blacklist, then update the number of abnormal occurrences of the cell in the blacklist. The blacklist contains cell information and the number of times the cell is abnormal. The number of times the cell is abnormal indicates the number of times multiple rounds of update requests have been initiated in the current cell without receiving update acceptance information. Each round of update requests includes an update request with a maximum number of transmissions equal to the transmission threshold. The current cell is a cell covered by the network device.

5. The method according to claim 1, characterized in that, The method further includes: If no update acceptance information is received from the network device within the first update time, and the number of times the first update request is resent is less than the number of times it is sent, a new first update time is obtained based on the first initial time. The first update request is resent to the network device, and the tracking area update is determined based on whether the update acceptance information from the network device is received within the new first update time. Wherein, the new first update time is less than the first update time.

6. The method according to claim 4, characterized in that, The method further includes: Send a second update request to the network device; The second initial time and the second transmission count threshold are determined based on the number of abnormal occurrences of the current cell in the blacklist; If no update acceptance information is received from the network device within the second initial time period, and the number of times the second update request is sent is less than the second sending number threshold, the second update time is obtained based on the second initial time. The second update request is resent to the network device, and the tracking area update is determined based on whether the update acceptance information from the network device is received within the second update time. The second update time is less than the second initial time.

7. The method according to claim 6, characterized in that, The second initial time and the second transmission count threshold are calculated using the following formula: in, This is the second initial time. For the first initial time, This represents the number of anomalies in the current cell. The second transmission count threshold, and The unit of time is seconds.

8. The method according to claim 2, characterized in that, Upon receiving update acceptance information from the network device within the first update time, after determining that the tracking area update has been implemented, the method further includes: When it is determined that the current cell of the terminal device has been placed in the blacklist, the abnormal count of the current cell is updated to obtain a second abnormal count; Based on the second number of anomalies, determine whether to remove the current cell from the blacklist; The blacklist carries cell information and anomaly count for the current cell. The anomaly count indicates the number of times multiple rounds of update requests have been initiated in the current cell without receiving update acceptance information. Each round of update requests includes an update request with a maximum number of transmissions equal to the transmission threshold.

9. The method according to claim 8, characterized in that, The step of determining whether to remove the current cell from the blacklist based on the second number of anomalies includes: If the second abnormal count is determined to be 0, the current cell is removed from the blacklist; or, If the number of the second anomalies is not equal to 0, the current cell remains in the blacklist.

10. The method according to claim 9, characterized in that, The current cell is placed in the blacklist, and the method further includes: Update the placement time of the current cell in the blacklist to obtain a second placement time.

11. The method according to claim 10, characterized in that, The step of updating the placement time of the current cell in the blacklist to obtain a second placement time includes: If a second abnormality count is obtained by updating the abnormality count of the current cell, the placement time of the current cell in the blacklist is updated to obtain the second placement time; or... If the placement time exceeds the preset placement time, the placement time is updated to obtain the second placement time.

12. The method according to claim 11, characterized in that, The step of updating the placement time to obtain a second placement time when the placement time exceeds a preset placement time includes: If the placement time exceeds the preset placement time, a second anomaly count is obtained based on the current anomaly count of the cell. Based on the second number of anomalies, the placement time is updated to obtain the second placement time.

13. The method according to claim 12, characterized in that, The second placement time is calculated using the following formula: in, For the second placement time, The second anomaly count of the current cell, The placement time is mentioned.

14. A terminal device, characterized in that, include: The sending module is used to send the first update request to the network device; The processing module is configured to determine a first update time based on the first initial time when no update acceptance information is received from the network device within a first initial time and the number of times the first update request is sent is less than a sending number threshold. In addition, the first update request is resent to the network device, and the tracking area update is determined based on whether the update acceptance information of the network device is received within the first update time; wherein the first update time is less than the first initial time, and the sending number threshold is the upper limit of the number of times the update request is sent.

15. A tracking region update device, characterized in that, The device includes a processor, a memory, and a transceiver, wherein the memory is used to store code instructions, the processor is used to execute the code instructions, and the transceiver is used to send and receive information to perform the method as described in any one of claims 1 to 13.

16. A computer-readable storage medium, characterized in that, Used to store a computer program, the computer program including instructions for implementing the method as described in any one of claims 1 to 13.

17. A computer program product, said computer program product comprising computer program code, characterized in that, When the computer program code is run on a computer, it causes the computer to implement the method as described in any one of claims 1 to 13.

Images