Tracking area updating method and tracking area updating device

Abstract

The invention provides a tracking area updating method and a tracking area updating device, which are applied to terminal equipment and shorten the out-of-step duration between the terminal equipment and network equipment. The method comprises the following steps: sending a first update request to network equipment; determining first updating time based on the first initial time under the condition that the updating receiving information of the network equipment is not received within the first initial time and the sending frequency of the first updating request is smaller than a sending frequency threshold value; re-sending the first updating request to the network equipment, and judging whether to realize tracking area updating or not according to whether updating receiving information of the network equipment is received within the first updating time or not; wherein the first updating time is smaller than the first initial time, and the sending frequency threshold value is the sending frequency upper limit of sending the first updating request.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a tracking area updating method and a tracking area updating device. Background Art

[0002] Tracking area update is a common signaling interaction mode in long-term evolution. When a terminal device moves from one tracking area to another, it will re-register its location in the new tracking area, that is, initiate a tracking area update process to notify the network device to change the location information of the terminal device it stores. This process is called tracking area update.

[0003] However, the above tracking area update process may cause a long period of desynchronization between the terminal device and the network device. Summary of the invention

[0004] The present application provides a tracking area update method and a tracking area update device, which shorten the desynchronization time between a terminal device and a network device.

[0005] In a first aspect, a tracking area update method is provided, which is applied to a terminal device, and the method includes: sending a first update request to a network device; determining a first update time based on the first initial time when no update acceptance information from the network device is received within a first initial time and the number of times the first update request is sent is less than a sending number threshold; resending the first update request to the network device, and judging 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; 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.

[0006] In the present application, the terminal device sends a first update request to the network device. If the update acceptance information from the above network device is not received within the first initial time, and the number of times the above first update request is sent is less than the sending number threshold, the terminal device can resend the above first update request to the above network device, and determine whether to implement the tracking area update based on whether the update acceptance information from the above network device is received within the first update time. The sending number threshold is the upper limit of the number of times the first update request is sent, and the first update time is determined based on the first initial time, and the first update 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 above sending number threshold by sending the update request, so as to shorten the out-of-sync time with the network device as the number of times the update request is sent increases.

[0007] In a second aspect, a terminal device is provided, and the terminal device includes: a sending module and a processing module, wherein the sending module is used to send a first update request to the network device; the processing module is used to determine a first update time based on the first initial time when no update acceptance information from the network device is received within the 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 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 is sent.

[0008] In a third aspect, a tracking area update device is provided, comprising a processor, the processor is coupled to a memory, and can be used to execute instructions in the memory to implement the method in any possible implementation of the first aspect. Optionally, the device also includes a memory. Optionally, the device also includes a communication interface, the processor is coupled to the communication interface.

[0009] In a fourth aspect, a processor is provided, comprising: an input circuit, an output circuit and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation of the first aspect.

[0010] In the specific implementation process, 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, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation methods of the processor and various circuits.

[0011] In a fifth aspect, a processing device is provided, comprising a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any possible implementation of the first aspect.

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

[0013] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

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

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

[0016] The processing device in the fifth aspect mentioned above can be a chip. The processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.

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

[0018] In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions) which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0020] Figure 2 is a flowchart of a tracking area update method provided in an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of the system architecture of a terminal device provided in an embodiment of the present application;

[0022] Figure 4 is a flow chart of a tracking area update method provided by an embodiment of the present application;

[0023] Figure 5is a flowchart of a first specific example of a tracking area update method provided in an embodiment of the present application;

[0024] Figure 6 is a flowchart of a second specific example of a tracking area update method provided in an embodiment of the present application;

[0025] Figure 7 is a flowchart of a third specific example of a tracking area update method provided in an embodiment of the present application;

[0026] Figure 8 is a structural block diagram of an example of a tracking area update device provided in an embodiment of the present application;

[0027] Fig. 9 It is a structural diagram of another example of a tracking area update device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0029] Figure 1 Schematic diagram of application scenario 100 provided in an embodiment of the present application. Figure 1 As shown, the application scenario 100 includes a terminal device 101 and a network device 102. Among them, tracking area update is a common signaling interaction mode in long-term evolution. When the terminal device 101 moves from one tracking area to another, it will re-register its location in the new tracking area, that is, initiate a tracking area update process to notify the network device 102 to change the location information of the terminal device stored in it. This process is tracking area update tracking area update.

[0030] However, the above tracking area update process may cause a long period of desynchronization between the terminal device and the network device.

[0031] Figure 2 Flow chart of a tracking area 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 update request for the first time, it can set the tracking area update counter (counter) to 1 and start the T3430 timer (15s).

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

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

[0036] Optionally, corresponding to the above S202, when the above T3430 timer times out (ie, exceeds 15 seconds), the terminal device will increase the tracking area update counter by 1 and will initiate an update request to the network device again.

[0037] It should be understood that there is an anomaly in the network, and the network device never responds to the update request of the terminal device. The terminal device will try to initiate 5 update requests. When the update request is initiated for the 5th time (that is, the tracking area update counter is 5) and T3430 times out (that is, more than 15s) and does not receive the update acceptance information from the network device, it will cause a 75s 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, an embodiment of the present application provides a tracking area update method and a tracking area update device, in which a terminal device sends a first update request to a network device. If the terminal device does not receive update acceptance information from the network device within a first initial time, and the number of times the first update request is sent is less than a threshold number of times, the terminal device can resend the first update request to the network device, and determine 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. The threshold number of times is the upper limit of the number of times the first update request is sent, and the first update time is determined based on the first initial time, and the first update 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 threshold number of times by sending the update request, so as to shorten the out-of-sync time with the network device as the number of times the update request is sent increases.

[0039] It should be understood that the technical solutions of the embodiments of the present 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, fifth 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 the present 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 the present application may be a device that provides voice / data connectivity to a user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, 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 functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (public land mobile communication networks) Mobile network, PLMN) and the like, the embodiments of the present application are not limited to this.

[0041] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

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

[0043] For example, Figure 3 A schematic diagram of the system architecture of a terminal device provided in an embodiment of the present 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 further include a memory 330. The processor 310, the transceiver 320 and the memory 330 may communicate with each other through an internal connection path to transfer search data. The memory 330 is used to store computer programs, and the processor 310 is used to call and run the computer program from the memory 330.

[0046] The processor 310 and the memory 330 may be combined into a processing device, or more commonly, they are independent components, and the processor 310 is used to execute the program code stored in the memory 330 to implement the above functions. In specific implementation, the memory 330 may also be integrated into the processor 310, or may be independent of the processor 310.

[0047] In addition, in order to make the functions of the terminal device more complete, the terminal device may further include one or more of an input unit 360 , an audio circuit 380 , and a sensor 301 .

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

[0049] Understandably, 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 description in the following method embodiments. To avoid repetition, detailed description is appropriately omitted here.

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

[0051] The processor 310 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. The memory may store instructions or data that the processor 310 has just used or cyclically used. If the processor 310 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, 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. The interface 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 understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the terminal device. In other embodiments of the present application, the terminal device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

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

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

[0056] The terminal device implements the display function 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 is used to perform mathematical and geometric calculations for graphics rendering. The processor 310 may include one or more GPUs that execute program instructions to generate or change display information.

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

[0058] The memory 330 can be used to store computer executable program codes, which include instructions. The memory 330 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal device (such as search data), etc. In addition, the memory 330 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 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 a memory provided in the processor.

[0059] The terminal device can realize audio functions such as music playing and recording through the audio circuit 380 and the application processor.

[0060] The embodiments of the present application involve network devices, which may include access and mobile management function (AMF) devices, transmission reception points (TRPs), and may also be evolved NodeBs (eNBs or eNodeBs) in LTE systems, or may also be home base stations (for example, home evolved NodeBs, or home Node Bs, HNBs), base band units (BBUs), or may be wireless controllers in cloud radio access networks (CRAN) scenarios, or the access network devices may be relay stations, access points, vehicle-mounted devices, wearable devices, and access network devices in 5G networks or access network devices in future evolved PLMN networks, etc., may be access points (APs) in WLANs, may be gNBs in new radio (NR) systems, may be satellite base stations in satellite communication systems, etc., and the embodiments of the present application are not limited.

[0061] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0062] In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

[0063] It should be noted that, in this application, words such as "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 interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.

[0064] In addition, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers 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, c can be single or multiple.

[0065] In order to make the purpose and technical solution of the present application clearer and more intuitive, a tracking area update method and tracking area update device provided by the embodiment of the present application will be described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0066] Figure 4 is a schematic flow chart of a tracking area update method 400 provided in an embodiment of the present application. The method 400 can be applied to the above Figure 1 The application scenario 100 shown in the figure can also be applied to other scenarios, which are not limited in the present embodiment. Figure 4 As shown, the method 400 may include the following steps:

[0067] S401: The terminal device sends a first update request to the network device.

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

[0069] Exemplarily, when the terminal device moves from one tracking area to another tracking area, the terminal device sends the 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 number threshold, the terminal device determines the first update time based on the first initial time. 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.

[0071] It should be understood that the first initial time may also be referred to as a first out-of-step time, and the first update time may also be referred to as a first update out-of-step time.

[0072] Exemplarily, after the terminal device sends the first update request to the network device, the terminal device can set the tracking area update counter (counter) to 1, start the T3430 timer, and initialize the started T3430 timer to the first initial time, and then determine whether it exceeds the above-mentioned first initial time based on the T3430.

[0073] It should be understood that the timer shown above is merely exemplary and the present application does not limit this.

[0074] S403, the terminal device resends the first update request to the network device, and determines whether to implement the tracking area update according to whether the update acceptance information of the network device is received within the first update time.

[0075] It should be understood that the terminal device may determine to implement the tracking area update when receiving the update acceptance information from the network device within the above-mentioned first update time.

[0076] In the present application, the terminal device sends a first update request to the network device. If the update acceptance information from the above network device is not received within the first initial time, and the number of times the above first update request is sent is less than the sending number threshold, the terminal device can resend the above first update request to the above network device, and determine whether to implement the tracking area update based on whether the update acceptance information from the above network device is received within the first update time. The sending number threshold is the upper limit of the number of times the first update request is sent, and the first update time is determined based on the first initial time, and the first update 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 above sending number threshold by sending the update request, so as to shorten the out-of-sync time with the network device as the number of times the update request is sent increases.

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

[0078] Figure 5 is a schematic flow chart of a tracking area update method 500 provided in an embodiment of the present 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 update acceptance information from the network device within the first update time, it determines whether the number of times the resent first update request is sent is less than a sending number threshold.

[0080] Exemplarily, the first update time may be calculated based on the following formula:

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

[0082] Wherein, 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 limited in this application.

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

[0085] It should be understood that the new first update time is smaller than the above first update time.

[0086] It should also be understood that the above-mentioned transmission times threshold can be represented by N, and N=5. In other words, the terminal device can execute the above-mentioned S502 when it is determined that the transmission times of the above-mentioned resent update request is less than 5.

[0087] Exemplarily, the new first update time may be calculated using the following formula.

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

[0089] Wherein, T1″ is the new first update time, T1 is the first initial time, n here can represent the number of times the resent first update request is sent, and s is the time unit second.

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

[0091] It should be understood that this formula is merely exemplary and is not limited in this application.

[0092] S503, the terminal device resends the first update request to the network device again, and determines whether to implement the tracking area update according to whether the update acceptance information of the network device is received within the new first update time.

[0093] It should be understood that the terminal device can determine to implement the tracking area update when it receives the update acceptance information of the network device within the above-mentioned new first update time. Alternatively, it can also continue to determine the new time and continue to resend the above-mentioned first update request when it does not receive the update acceptance information of the network device within the above-mentioned new first update time, and the number of times the above-mentioned first update request is resent is less than the above-mentioned number of times threshold, so as to implement the tracking area update method provided by the present application.

[0094] Table 1 shows the determined time (also referred to as out-of-sync time) for the first update request that is less than or equal to the sending number threshold.

[0095] Table 1

[0096]

[0097] As shown in Table 1, when the sending number threshold N=5, the terminal device can send the first update request continuously for up to 5 times without receiving the update acceptance information of the network device, which are the first update request sent for the first time, i.e., the first update request in the table (n=1), the first update request sent for the second time, i.e., the first update request in the table (n=2), the first update request sent for the third time, i.e., the first update request in the table (n=3), the first update request sent for the fourth time, i.e., the first update request in the table (n=4), and the first update request sent for the fifth time, i.e., the first update request in the table (n=5).

[0098] Exemplarily, as shown in Table 1, the terminal device may execute the first update request (n=1), and upon receiving the update acceptance information from the network device within 15 seconds, determine to implement the tracking area update.

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

[0100] Exemplarily, when it is determined that the update acceptance information of the network device is not received within 15 seconds, the terminal device can continue to execute the first update request (n=2), and when the update acceptance information of the network device is received within 12 seconds, it is determined to implement the tracking area update.

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

[0102] Exemplarily, when it is determined that the update acceptance information of the network device is not received within 12 seconds, the terminal device can continue to execute the first update request (n=3), and when the update acceptance information of the network device is received within 9 seconds, it is determined to implement the tracking area update.

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

[0104] Exemplarily, when it is determined that the update acceptance information of the network device is not received within 9 seconds, the terminal device can continue to execute the first update request (n=4), and when the update acceptance information of the network device is received within 6 seconds, it is determined to implement the tracking area update.

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

[0106] Exemplarily, when it is determined that the update acceptance information of the network device is not received within 6 seconds, the terminal device can continue to execute the first update request (n=5), and when the update acceptance information of the network device is received within 3 seconds, it is determined to implement the tracking area update.

[0107] It should be understood that the 3s can be calculated based on the first initial time 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, from Table 1, it can be learned that the out-of-sync duration 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 3s, it is determined that the tracking area update is implemented. Even if the number of times the first update request is sent reaches the upper limit (5 times), the out-of-sync duration between the terminal device and the network device in the present application can be shortened as the number of times the first update request is sent increases, so that the final maximum total out-of-sync duration is 45s, which is 30s shorter than 75s in the prior art, thereby reducing the out-of-sync time overhead by 40%.

[0110] It should be understood that the present application can also send more update requests within 75 seconds of the prior art, which can not only shorten the desynchronization time between the terminal device and the network device, but also improve the success rate of the tracking area update. That is, when the first update request (n=5) is executed above and the update acceptance information of the network device is not received within 3 seconds, the sending operation of the new update request can be continued.

[0111] In a possible implementation, the terminal device may execute multiple rounds of sending operations of update requests, such as three rounds of sending operations of update requests, without receiving update acceptance information from the network device.

[0112] It should be understood that the sending number threshold and initial time corresponding to each of the three rounds of update requests may be different.

[0113] For example, the threshold of the number of times the update request is sent included in the first round of update requests may be 5 times as mentioned in the above embodiment, and the initial time may be the first initial time 15s as mentioned in the above embodiment. That is, the specific details of the first round of update requests can be referred to in the above description. Figure 5 The description of is not repeated here to avoid repetition. Figure 5 The corresponding first round of update requests are then passed through Figure 6 and Figure 7 In the case of the second round of update request and the third round of update request, the tracking area update method provided in the present application is respectively described in detail.

[0114] Exemplarily, to distinguish different rounds of update requests, the present application hereinafter refers to the update requests included in the first round of update requests as first update requests, the update requests included in the second round of update requests as second update requests, and the update requests included in the third round of update requests as third update requests.

[0115] It should be understood that the above naming is merely exemplary and this application does not limit it.

[0116] Figure 6 6 is a schematic flow chart of a tracking area update method 600 provided in an embodiment of the present application. Figure 6 As shown, the method 600 may include the following steps:

[0117] S601: When the terminal device does not receive update acceptance information 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 the second update request may also be referred to as a second tracking area update request.

[0119] Exemplarily, the terminal device may execute S601 above when the update acceptance information of the network device is not received within 45 seconds as shown in Table 1 above.

[0120] S602, the terminal device determines a second initial time and a second sending number threshold based on the number of abnormalities in the current cell.

[0121] It should be understood that the second initial time may be the upper limit of the time for waiting for update acceptance information of the network device after sending the second update request with the number of times being 1 in the second round of update requests (ie, the desynchronization time).

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

[0123] Exemplarily, the second initial time and the second sending times threshold may be calculated by the following formula:

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

[0125] Among them, T2 is the above-mentioned second initial time, T1 is the first initial time, m is the number of abnormal times of the current cell, N is the above-mentioned second sending number threshold, and s is the time unit second.

[0126] For example, in the case of the second round of update request, the number of exceptions m = 1, that is, it can be calculated that T2 = 10, N = 3. 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 (counter) to 1, start the T3430 timer at the same time, and initialize the started T3430 timer to the second initial time (i.e. 10s), and then determine whether it exceeds the above second initial time based on the T3430.

[0127] It should be understood that the timer shown above is merely exemplary and the present application does not limit this.

[0128] It should also be understood that the above-mentioned number of abnormal times is used to indicate the number of times that multiple rounds of update requests are continuously initiated in the current cell without receiving update acceptance information, and each round of update requests in the multiple rounds of update requests includes an update request with an upper limit of the number of sending times equal to the above-mentioned sending number threshold; the current cell is the cell covered by the above-mentioned network device.

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

[0130] It should be understood that the current cell may be placed on the blacklist when no update acceptance information is received in the first round of update request sending, so as to record the number of abnormalities 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) information of the current cell. Correspondingly, before the above S602, the terminal device can determine whether the current cell is in the blacklist, so as to obtain the number of abnormalities of the current cell and execute the above S602 when it is determined that the current cell has been placed on the blacklist.

[0131] S603, when 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 terminal device obtains the second update time based on the second initial time.

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

[0133] Exemplarily, the second update time may be calculated based on the following formula:

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

[0135] Wherein, 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 the 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 number threshold, the terminal device can add 1 to the tracking area update counter (counter) on the original basis, that is, 1+1=2, and start the T3430 timer at the same time, and update the started T3430 timer to the second update time, and then judge whether the second update time is exceeded based on the T3430.

[0136] It should be understood that the formula and timer shown above are merely exemplary and are not limited to this application.

[0137] S604: The terminal device resends the second update request to the network device, and determines whether to implement the tracking area update according to whether the update acceptance information of the network device is received within the second update time.

[0138] Table 2 shows the determined time (also referred to as out-of-sync time) for the 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 number threshold N=3, the terminal device can send the second update request up to 3 times in succession without receiving the update acceptance information from the network device, which are the second update request sent for the first time, i.e., the second update request in the table (n=1), the second update request sent for the second time, i.e., the second update request in the table (n=2), and the second update request sent for the third time, i.e., the second update request in the table (n=3).

[0142] Exemplarily, as shown in Table 2, the terminal device may execute the second update request (n=1), and upon receiving the update acceptance information from the network device within 10 seconds, determine to implement the tracking area update.

[0143] It should be understood that, corresponding to the description in the above embodiment, the 10s is the above second initial time, which is calculated based on the first initial time and the number of abnormalities, that is, 10s=15s-1*5s.

[0144] Exemplarily, when it is determined that the update acceptance information of the network device is not received within 10s, the terminal device can continue to execute the second update request (n=2), and when the update acceptance information of the network device is received within 7s, it is determined to implement the tracking area update.

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

[0146] Exemplarily, when it is determined that no update acceptance information from the network device is received within 7 seconds, the terminal device may continue to execute the second update request (n=3), and when update acceptance information from the network device is received within 4 seconds, it is determined to implement tracking area update.

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

[0148] In summary, from Table 2, it can be learned that the out-of-sync duration 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 4s, it is determined that the tracking area update is implemented. 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), the out-of-sync duration between the terminal device and the network device in the present application can be shortened as the number of times the second update request is sent increases. The final out-of-sync duration during the first round of update requests and the second round of update requests is a maximum total of 66s, which is 9s shorter than 75s in the prior art, thereby reducing the out-of-sync time overhead by 12%, and the number of update requests sent is increased by 3 times.

[0150] Figure 7 is a schematic flow chart of a tracking area update method 700 provided in an embodiment of the present application. Figure 7 As shown, the method 700 may include the following steps:

[0151] S701: When the terminal device does not receive update acceptance information 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 the third update request may also be referred to as a third tracking area update request.

[0153] Exemplarily, the terminal device may execute S701 above when the update acceptance information of the network device has not been received within 21 seconds as shown in Table 2 above.

[0154] S702, the terminal device determines a third sending number threshold at a third initial time based on the number of abnormalities in the current cell.

[0155] It should be understood that the third initial time may be the upper limit of the time for waiting for update acceptance information of the network device after sending the third update request with the number of times being 1 in the third round of update requests (ie, the desynchronization time).

[0156] Exemplarily, the third initial time and the third sending times threshold may be calculated by the following formula:

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

[0158] Among them, T3 is the above-mentioned third initial time, T1 is the first initial time, m is the number of abnormal times of the current cell, N is the above-mentioned third sending number threshold, and s is the time unit second.

[0159] For example, in the case of the third round of update request, the number of exceptions m = 2, that is, T3 = 5, 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 (counter) to 1, start the T3430 timer at the same time, and initialize the started T3430 timer to the third initial time (i.e. 5s), and then determine whether it exceeds the above third initial time based on T3430.

[0160] It should be understood that the timer shown above is merely exemplary and the present application does not limit this.

[0161] It should also be understood that the above-mentioned number of abnormal times is used to indicate the number of times that multiple rounds of update requests are continuously initiated in the current cell without receiving update acceptance information, and each round of update requests in the multiple rounds of update requests includes an update request with an upper limit of the number of sending times equal to the above-mentioned sending number threshold; the current cell is the cell covered by the above-mentioned network device.

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

[0163] It should be understood that the current cell may be placed in the blacklist when no update acceptance information is received in the first round of update request transmission, so as to record the number of abnormalities in the current cell. Correspondingly, before the above S702, the terminal device may determine whether the current cell is in the blacklist, so as to obtain the number of abnormalities of the current cell when it is determined that the current cell has been placed in the blacklist, and execute the above S702.

[0164] S703, when no update acceptance information is received from the network device within 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 the third update time is less than the third initial time mentioned above.

[0166] Exemplarily, the third update time may be calculated based on the following formula:

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

[0168] Wherein, T3′ is the third update time, T3 is the third initial time, n is the number of times the 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 the update acceptance information from the network device within 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 can add 1 to the tracking area update counter (counter) on the original basis, that is, 1+1=2, and start the T3430 timer at the same time, and update the started T3430 timer to the third update time, and then judge whether the third update time is exceeded based on the T3430.

[0169] It should be understood that the formula and timer shown above are merely exemplary and are not limited to this application.

[0170] S704, the terminal device resends the third update request to the network device, and determines whether to implement the tracking area update according to whether the update acceptance information of the network device is received within the third update time.

[0171] Table 3 shows the determined time (also referred to as out-of-sync time) under the third update request that is less than or equal to the third sending number threshold.

[0172] Table 3

[0173]

[0174] As shown in Table 3, when the third sending times threshold N=2, the terminal device can send the third update request consecutively up to 2 times without receiving the update acceptance information from the network device, which are the third update request sent for the first time, i.e., the third update request in the table (n=1) and the third update request sent for the second time, i.e., the third update request in the table (n=2).

[0175] Exemplarily, as shown in Table 2, the terminal device may execute the third update request (n=1), and upon receiving the update acceptance information from the network device within 5 seconds, determine to implement the tracking area update.

[0176] It should be understood that, corresponding to the description in the above embodiment, the 5s is the above third initial time, which is calculated based on the first initial time and the number of abnormalities, that is, 5s=15s-2*5s.

[0177] Exemplarily, when it is determined that the update acceptance information of the network device is not received within 5 seconds, the terminal device can continue to execute the third update request (n=2), and when the update acceptance information of the network device is received within 3 seconds, it is determined to implement the tracking area update.

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

[0179] In summary, from Table 3, it can be learned that the out-of-sync duration between the terminal device and the network device in this application can be shortened as the number of times the third update request is sent 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 3s, it is determined that the tracking area update is implemented. 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), the out-of-sync duration between the terminal device and the network device in the present application can be shortened as the number of times the third update request is sent increases. The final out-of-sync duration in the first round of update requests, the second round of update requests and the third round of update requests is a maximum of 74s in total, which is 1s shorter than 75s in the prior art, thereby reducing the out-of-sync time overhead by 1.3% and increasing the number of update requests sent by 5 times.

[0181] Optionally, after receiving the update acceptance information from the above-mentioned network device and determining that the tracking area update has been implemented, the terminal device can also update the number of abnormalities of the current cell in the blacklist if it is determined that the current cell has been placed on the blacklist to obtain a new number of abnormalities (also referred to as the second number of abnormalities).

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

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

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

[0185] Exemplarily, when it is determined that the number of exceptions is equal to 0, the terminal device may remove the current cell from the blacklist, such as when the new number of exceptions m′=m-1=0 obtained by the above update.

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

[0187] Optionally, the terminal device may also update the placement time of the current cell in the blacklist (also referred to as the first placement time) and obtain a new placement time (also referred to as the second placement time).

[0188] In one possible case, the terminal device may update the placement time of the current cell in the blacklist when obtaining a new number of abnormalities of the current cell, and obtain the new placement time.

[0189] In another possible case, the terminal device may also update the placement time when the placement time of the current cell in the blacklist exceeds the preset placement time to obtain the above-mentioned new placement time.

[0190] In one possible implementation, when the above-mentioned placement time exceeds the preset placement time, the terminal device can obtain a new number of abnormalities based on the number of abnormalities of the current cell, and then update the above-mentioned placement time based on the new number of abnormalities (also referred to as the second number of abnormalities) to obtain a new placement time (also referred to as the second placement time).

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

[0192] t′=m′*t

[0193] Among them, t′ is the above-mentioned new placement time, m′ is the new number of abnormalities in the current cell, m′=m-1 or m′=m-1, wherein m is the number of abnormalities in the current cell, and m′≠0, and t is the placement time, which can be preset.

[0194] It should be understood that the above embodiments may be coupled to each other, and this application does not limit this. Moreover, the size of the sequence number of each process does not mean 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] Combined with the above Figures 1 to 7 , describes in detail the tracking area update method of the embodiment of the present application, and will be combined with Figure 8 and Fig. 9 , describes in detail the tracking area update device of an embodiment of the present application.

[0196] Figure 8A tracking area update device 800 provided in an embodiment of the present application is shown. The tracking area update device 800 includes: a sending module 801 and a processing module 802.

[0197] Among them, the sending module 801 is used to: send a first update request to the network device; the processing module 802 is used to: determine the first update time based on the above-mentioned first initial time when the update acceptance information of the above-mentioned network device is not received within the first initial time and the number of times the above-mentioned first update request is sent is less than the sending number threshold; and resend the above-mentioned first update request to the above-mentioned network device, and determine whether to realize the tracking area update according to whether the update acceptance information of the above-mentioned network device is received within the above-mentioned first update time; wherein the above-mentioned first update time is less than the above-mentioned first initial time, and the above-mentioned 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 used to: upon receiving update acceptance information from the network device within 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), wherein 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 used to: place the current cell of the terminal device in the blacklist when the update acceptance information of the network device is not received within the first update time and the number of times the resent first update request is sent is equal to the sending number threshold; or, when the update acceptance information of the network device is not received within the first update time, the number of times the resent first update request is sent is equal to the sending number threshold, and the current cell has been placed in the blacklist, update the abnormal number of the cell in the blacklist; wherein the blacklist contains the cell information and the cell abnormal number of the current cell, the abnormal number is used to indicate the number of times that multiple rounds of update requests are continuously initiated in the current cell without receiving update acceptance information, and each round of update requests in the multiple rounds of update requests includes an update request with an upper limit of the number of sending times equal to the sending number threshold; the current cell is the cell covered by the network device.

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

[0202] Optionally, the processing module 802 is used to: send a second update request to the above-mentioned network device; determine a second initial time and a second sending number threshold based on the number of abnormalities of the above-mentioned current cell in the above-mentioned blacklist; when no update acceptance information is received from the above-mentioned network device within the above-mentioned second initial time period and the number of sending times of the above-mentioned second update request is less than the above-mentioned second sending number threshold, obtain the above-mentioned second update time based on the above-mentioned second initial time; resend the above-mentioned second update request to the above-mentioned network device, and determine whether to realize the tracking area update based on whether the update acceptance information of the above-mentioned network device is received within the above-mentioned second update time; wherein the above-mentioned second update time is less than the above-mentioned second initial time.

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

[0204] Optionally, the processing module 802 is used to: when it is determined that the current cell has been placed on the blacklist, update the number of abnormalities of the current cell to obtain a second number of abnormalities; based on the second number of abnormalities, determine whether to remove the current cell from the blacklist; wherein the blacklist carries the cell information and the number of abnormalities of the current cell, and the number of abnormalities is used to indicate the number of times that multiple rounds of update requests are continuously initiated in the current cell without receiving update acceptance information, and each round of update requests in the multiple rounds of update requests includes an update request with an upper limit of the number of sending times equal to the above-mentioned sending number threshold.

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

[0206] Optionally, the processing module 802 is used to: when the second abnormal number of the current cell is updated, update the above-mentioned placement time of the above-mentioned current cell in the above-mentioned blacklist to obtain the above-mentioned second placement time; or, when the above-mentioned placement time exceeds the preset placement time, update the above-mentioned placement time to obtain the above-mentioned second placement time.

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

[0208] Optionally, the second placement time is calculated by the following formula: t′=m′*t, wherein t′ is the second placement time, m′ is the second abnormal number 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 may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art may understand that the tracking area update device 800 may be specifically a terminal device in the above-mentioned embodiment, or the functions of the terminal device in the above-mentioned embodiment may be integrated in the tracking area update device 800, and the tracking area update device 800 may be used to execute the various processes and / or steps corresponding to the terminal device in the above-mentioned method embodiment. To avoid repetition, it will not be repeated here.

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

[0211] Fig. 9Another tracking area update device 900 provided in an embodiment of the present application is shown. The tracking area update device 900 includes: a processor 901 and 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 connected to each other through the bus 904.

[0212] Among them, processor 901 is used to: send a first update request to the network device; if the update acceptance information of the above-mentioned network device is not received within the first initial time and the number of sending times of the above-mentioned first update request is less than the sending number threshold, determine the first update time based on the above-mentioned first initial time; and resend the above-mentioned first update request to the above-mentioned network device, and determine whether to realize the tracking area update according to whether the update acceptance information of the above-mentioned network device is received within the above-mentioned first update time; wherein the above-mentioned first update time is less than the above-mentioned first initial time, and the above-mentioned sending number threshold is the upper limit of the number of sending times of sending the first update request.

[0213] It should be understood that the tracking area update device 900 can be specifically the terminal device in the above-mentioned embodiment, the functions of the terminal device in the above-mentioned embodiment can be integrated into the tracking area update device 900, and 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-mentioned method embodiment.

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

[0215] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0216] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor executes the instructions in the memory, and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0217] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

[0219] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0221] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0222] If the above functions are implemented in the form of 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 the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or terminal device, etc.) to perform all or part of the steps of the above methods in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0223] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the above claims.

Claims

1. A tracking area update method, characterized in that: Applied to a terminal device, the method comprises: Sending a first update request to the network device; If update acceptance information of the network device is not received within the first initial time and the number of times the first update request is sent is less than a sending number threshold, determining a first update time based on the first initial time; resending the first update request to the network device, and determining whether to implement tracking area update according to whether update acceptance information of the network device is received within the first update time; The first update time is less than the first initial time, and the sending times threshold is an upper limit of the number of times the first update request is 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 according to whether update acceptance information of 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: T1′=max(T1-n*3s,3s) Wherein, 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.

4. The method according to claim 1, characterized in that The method further comprises: If the update acceptance information of the network device is not received within the first update time and the number of times the first update request is resent is equal to the number of times threshold, the current cell of the terminal device is placed in a blacklist; or, When the update acceptance information of the network device is not received within the first update time, the number of times the first update request is resent is equal to the number of times of transmission threshold, and the current cell has been placed in the blacklist, updating the number of abnormalities of the cell in the blacklist; Among them, the blacklist contains the cell information of the current cell and the number of cell abnormalities, the number of abnormalities is used to indicate the number of times that multiple rounds of update requests are continuously initiated in the current cell and no update acceptance information is received, each round of update requests in the multiple rounds of update requests includes an update request with an upper limit of the number of sending times equal to the sending number threshold; the current cell is the cell covered by the network device.

5. The method according to claim 1, characterized in that The method further comprises: When no update acceptance information of the network device is received within the first update time and the number of times the first update request is resent is less than the number of times threshold, obtaining a new first update time based on the first initial time; resending the first update request to the network device again, and determining whether to implement the tracking area update according to whether the update acceptance information of the network device is received within the new first update time; The new first update time is smaller than the first update time.

6. The method according to claim 4, characterized in that The method further comprises: Sending a second update request to the network device; Determine a second initial time and a second sending number threshold based on the number of abnormalities 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 times the second update request is sent is less than the second sending number threshold, obtaining the second update time based on the second initial time; resending the second update request to the network device, and determining whether to implement tracking area update according to whether update acceptance information of 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 sending number threshold are calculated by the following formula: T2=T1-m*5s,N=5-m-1 Among them, T2 is the second initial time, T1 is the first initial time, m is the number of abnormal times of the current cell, N is the second sending times threshold, and s is the time unit second.

8. The method according to claim 2, characterized in that: When receiving update acceptance information from the network device within the first update time, after determining that the tracking area update is implemented, the method further includes: When it is determined that the current cell has been placed in the blacklist, updating the number of abnormalities of the current cell to obtain a second number of abnormalities; Based on the second abnormal number, determining whether to remove the current cell from the blacklist; Among them, the blacklist carries the cell information and abnormal number of the current cell, and the abnormal number is used to indicate the number of times that multiple rounds of update requests are continuously initiated in the current cell without receiving update acceptance information, and each round of update requests in the multiple rounds of update requests includes an update request with an upper limit of the number of sending requests equal to the sending number threshold.

9. The method according to claim 8, characterized in that The determining, based on the second abnormal number of times, whether to remove the current cell from the blacklist includes: If it is determined that the second abnormal number is equal to 0, removing the current cell from the blacklist; or, When it is determined that the second abnormal number is not equal to 0, the current cell is kept 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: The placement time of the current cell in the blacklist is updated to obtain a second placement time.

11. The method according to claim 10, characterized in that The updating of the placement time of the current cell in the blacklist to obtain a second placement time includes: In the case where the number of abnormalities of the current cell is updated to obtain a second number of abnormalities, updating the placement time of the current cell in the blacklist to obtain the second placement time; or, When 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 When the placement time exceeds the preset placement time, updating the placement time to obtain the second placement time includes: In the case where the placement time exceeds the preset placement time, updating and obtaining a second abnormal number based on the abnormal number of the current cell; Based on the second abnormal number, 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 by the following formula: t′=m′*t Among them, t' is the second placement time, m' is the second abnormal number of the current cell, and t is the placement time.

14. A terminal device, characterized in that: include: A sending module, used for sending a first update request to the network device; A processing module, configured to determine a first update time based on the first initial time if no update acceptance information of the network device is received within the 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 the tracking area update 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 sending update requests.

15. A tracking area updating device, characterized in that: The system comprises 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, so as to execute the method according to 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 comprising instructions for implementing the method according to any one of claims 1 to 13.

17. A computer program product, comprising computer program code, characterized in that: When the computer program code is executed on a computer, the computer is caused to implement the method according to any one of claims 1 to 13.

Images