A method, apparatus, terminal, and readable storage medium for de-attachment

Abstract

This application provides a de-attachment method, apparatus, terminal, and readable storage medium. The method includes: the terminal sending a de-attachment request message to a network-side device and starting a wait timer; before the timer expires, if the terminal determines that de-attachment has failed, the terminal sends the de-attachment request message to the network-side device again and restarts the wait timer. This application can reduce the power consumption of the terminal.

Description

Technical Field

[0001] This application relates to the field of narrowband Internet of Things (IoT) technology, and in particular to a method, apparatus, terminal, and readable storage medium for de-attachment. Background Technology

[0002] The terminal cancels its registration with the network by sending a detach request, thus ceasing service from the wireless network and deleting corresponding parameter information. In existing solutions, the terminal sends the detach request and starts a timer. If it receives a detach acceptance message from the wireless network within the timer's duration, the detachment is successful, the timer stops, and both the terminal and the wireless network delete their respective bearer contexts locally. If no detach acceptance message is received within the timer's duration, the terminal sends the detach request message again and restarts the timer after the timer expires. This repeated sending of the detach request message and restarting of the timer results in high power consumption for the terminal. Summary of the Invention

[0003] This application provides a method, apparatus, terminal, and readable storage medium for removing attachments, in order to solve the problem of high power consumption in the terminal.

[0004] In a first aspect, embodiments of this application provide a method for removing adhesion, including:

[0005] The terminal sends a detach request message to the network-side device and starts a waiting timer;

[0006] If the terminal determines that the detachment has failed before the waiting timer expires, the terminal will send the detachment request message to the network-side device again and restart the waiting timer.

[0007] Secondly, embodiments of this application also provide a de-adhesion device, comprising:

[0008] The first sending module is used to send a detach request message to the network-side device and to start a waiting timer;

[0009] The second sending module is used to send the detach request message to the network-side device again and restart the waiting timer before the waiting timer expires, if it is determined that the detach failure has failed.

[0010] Thirdly, embodiments of this application also provide a terminal, including a processor, a memory, and a program or instructions stored in the memory and running on the processor, wherein the program or instructions, when executed by the processor, implement the steps in the method described in the first aspect above.

[0011] Fourthly, embodiments of this application also provide a readable storage medium for storing a program, wherein the program is stored on the readable storage medium, and when the program is executed by a processor, it implements the steps in the method described in the first aspect above.

[0012] In this embodiment, the terminal sends a detach request message to the network-side device and starts a waiting timer. If the terminal determines that detachment has failed before the waiting timer expires, the terminal sends the detach request message to the network-side device again and restarts the waiting timer. That is, if the terminal determines that detachment has failed before the waiting timer expires, the terminal can directly initiate a detach request message again without waiting for the waiting timer to expire, thereby reducing invalid waiting time and reducing the terminal's power consumption. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of this application, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a schematic flowchart of an attachment removal method provided in an embodiment of this application;

[0015] Figure 2 This is a flowchart illustrating a method for shortening the de-attachment waiting time provided in an embodiment of this application;

[0016] Figure 3 This is a schematic diagram of the structure of a de-adhesion device provided in an embodiment of this application;

[0017] Figure 4 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0019] The terms "first," "second," etc., used in the embodiments of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices. Additionally, the use of "and / or" in this application indicates at least one of the connected objects, such as A and / or B and / or C, representing seven possibilities: including A alone, B alone, C alone, and the presence of both A and B, both B and C, both A and C, and the presence of A, B, and C.

[0020] Please see Figure 1 , Figure 1 This is a flowchart illustrating an attachment removal method provided in an embodiment of this application, as shown below. Figure 1 As shown, it includes the following steps:

[0021] Step 101: The terminal sends a detach request message to the network-side device and starts a waiting timer.

[0022] The terminal, also known as a terminal device or user equipment (UE), can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include smartwatches, wristbands, headphones, glasses, etc. It should be noted that the specific type of terminal is not limited in this embodiment.

[0023] It is understood that the aforementioned detach request message is used by the terminal to cancel its registration with the wireless network, no longer accept the services of the wireless network, and delete the corresponding parameter information. The aforementioned network-side device is a component of the aforementioned wireless network, and the terminal achieves detachment by interacting with the aforementioned network-side device.

[0024] In some embodiments, the aforementioned detach request message is used in a normal detach process, i.e., the terminal disconnects all PDN (Public Data Network) links. In a normal detach process, the terminal first sends the aforementioned detach request message and carries the type of the detach request to trigger the detach process, and simultaneously starts the aforementioned waiting timer to control the detach process, and waits for the network-side device to return a detach consent message within the time interval of the aforementioned waiting timer. After the terminal receives the aforementioned detach consent message, it considers the detach process to be successful and stops the aforementioned waiting timer. After the terminal and the aforementioned network-side device delete their respective local bearer contexts, the aforementioned network-side device considers that the terminal no longer needs network services.

[0025] In some embodiments, the aforementioned waiting timer can be a timer T3421. The duration of timer T3421 in NB-IoT (Narrow Band Internet of Things) is 255 seconds, that is, the timing period of the aforementioned waiting timer is 255 seconds.

[0026] Step 102: Before the waiting timer expires, if the terminal determines that the detachment has failed, the terminal sends the detachment request message to the network-side device again and restarts the waiting timer.

[0027] Optionally, the terminal determines that de-attachment has failed, including at least one of the following:

[0028] The terminal receives a release link message sent by the network-side device;

[0029] The terminal disconnects the communication link between itself and the network-side device.

[0030] It is understood that the terminal can send the aforementioned detach request message to the network-side device through the aforementioned communication link, and receive the detach consent message sent by the network-side device in response to the aforementioned detach request message, thereby enabling the terminal and the network-side device to delete their respective local bearer contexts.

[0031] The aforementioned release link message can indicate that the aforementioned network-side device initiates the disconnection of the aforementioned communication link, and the aforementioned terminal disconnecting the communication link between the aforementioned terminal and the aforementioned network-side device can indicate that the aforementioned terminal initiates the disconnection of the communication link.

[0032] During the aforementioned waiting timer period, since the inactive timer of the aforementioned network-side device generally has a short duration, if the duration of the aforementioned inactive timer is 20 seconds, the aforementioned network-side device will initiate the aforementioned release connection message at the 20th second. In this way, the aforementioned terminal will not receive the unattach consent message returned by the aforementioned network-side device in the remaining time, and the aforementioned terminal's waiting in the remaining time becomes meaningless. If the terminal determines that the detachment has failed before the timer expires, the terminal will send the detach request message to the network device again and restart the timer. Taking timer T3421 with a duration of 255 seconds as an example, if the terminal determines that the detachment has failed at the 20th second, the terminal does not need to wait for the remaining 235 seconds of timer T3421. It can directly send the detach request message to the network device again and restart timer T3421. It can attempt up to 5 times. When timer T3421 is started for the 5th time, the terminal can delete the local bearer context without waiting for the detach consent message sent by the network device and complete the detachment process.

[0033] After sending the aforementioned detach request message to the network-side device, if the terminal quickly completes the detach process, it can return to normal operation and enter sleep mode earlier. In some embodiments, the power consumption standard of the terminal in idle state is 5mW, and the power consumption standard in sleep mode is 0.03mW, meaning that during the nearly 20 minutes of the five starts of the aforementioned timer T3421, the terminal can save approximately 99.3% of its power.

[0034] In this embodiment, the terminal sends a detach request message to the network-side device and starts a waiting timer. If the terminal determines that detachment has failed before the waiting timer expires, the terminal sends the detach request message to the network-side device again and restarts the waiting timer. That is, if the terminal determines that detachment has failed before the waiting timer expires, the terminal can directly initiate a detach request message again without waiting for the waiting timer to expire, thereby reducing invalid waiting time and reducing the terminal's power consumption.

[0035] Optionally, before the terminal sends the detach request message to the network-side device again in step 102 and before restarting the waiting timer, the method may further include the following steps:

[0036] If the terminal determines that the detachment has failed, the terminal sends a request message to the network-side device to establish the communication link.

[0037] Since the terminal receives a release link message from the network-side device, or the terminal disconnects the communication link between the terminal and the network-side device, the disconnection of the communication link prevents the terminal from receiving the detach consent message from the network-side device. If the terminal determines that detaching has failed, it sends a request message to the network-side device to re-establish the communication link.

[0038] Optionally, the terminal may send the detach request message to the network-side device again, including:

[0039] The terminal sends the detach request message to the network-side device again through the communication link established by the request message to establish the communication link.

[0040] It is understood that when the terminal sends the aforementioned detach request message to the network-side device again, it can use the rebuilt communication link. If the terminal sends the aforementioned detach request message to the network-side device again and restarts the aforementioned waiting timer, the terminal will wait again for the network-side device to send a response message within the timer's duration. Similarly, if the terminal determines that detachment has failed within this waiting timer's duration, the terminal will send the aforementioned detach request message to the network-side device again and restart the aforementioned waiting timer.

[0041] In this embodiment, the terminal sends the detach request message to the network-side device again through the communication link established by the request message to establish the communication link, thereby increasing the success rate of the terminal completing the detachment by receiving the response of the network-side device to the detach request message.

[0042] Optionally, before the waiting timer expires in step 102, if the terminal determines that the detachment has failed, the terminal sends the detachment request message to the network-side device again and restarts the waiting timer. Specifically, this may include:

[0043] If the terminal determines that the detachment has failed before the waiting timer expires, the terminal closes the waiting timer, sends the detachment request message to the network-side device again, and restarts the waiting timer.

[0044] In this implementation, if the terminal determines that detachment has failed before the waiting timer expires, the terminal shuts down the waiting timer. That is, if detachment failure is determined, the terminal no longer waits for the waiting timer to expire, but directly shuts it down. This avoids the terminal wasting time waiting for the remaining time. By sending the detach request message to the network-side device again and restarting the waiting timer, the terminal can quickly complete the detachment and return to normal service more quickly, thereby reducing the time and power consumption required for detachment and improving the user experience.

[0045] In addition, by quickly detaching from the device, the terminal can enter a normal state and sleep mode earlier, thereby reducing the power consumption of the terminal.

[0046] The various optional implementation methods described in the embodiments of this application can be combined with each other or implemented individually without conflict, and the embodiments of this application do not limit this.

[0047] For ease of understanding, a specific example is as follows:

[0048] This application also provides a method for shortening the de-attachment latency, applicable to narrowband IoT terminals, such as... Figure 2 As shown, the timer used in the narrowband IoT terminal is timer T3421, and the timing duration of timer T3421 is 255 seconds. The above-mentioned method for shortening the de-attachment waiting time can specifically include the following process:

[0049] The terminal initiates a normal type of detach process: The terminal sends a detach request (detach_req) message to the wireless network device and carries the type of normal type detach. At the same time, it starts a timer T3421 with a length of 255 seconds. The terminal waits for the response from the wireless network device for the duration of timer T3421.

[0050] When the wireless network device sends a release link message to the terminal, or when the terminal loses its communication link locally, the terminal believes that it can no longer obtain the detach_acp message from the wireless network device.

[0051] In this situation, the terminal immediately determines that the detach process has failed. Instead of waiting for the remaining time of timer T3421 to expire, it directly stops timer T3421. The terminal will immediately re-initiate the request to establish a communication link, resend the detach_req message to the wireless network device, and restart timer T3421. This attempt can be accumulated up to 5 times.

[0052] In this embodiment, if a communication link is lost during the operation of timer T3421, the terminal can directly close timer T3421 and re-initiate the detach process. In the prior art, the terminal only executes the local detach process and deletes local bearer information when timer T3421 times out for the fifth time. However, each wait time for timer T3421 is 255 seconds. If five consecutive attempts are made, the cumulative wait time reaches 1275 seconds, meaning the terminal cannot resume service for more than 20 minutes. This application avoids the ineffective waiting time after the communication link is lost by closing timer T3421 and restarting the detach process immediately. The terminal can save up to nearly 20 minutes of time. Furthermore, by closing timer T3421 and restarting the detach process immediately upon communication link loss, the detach process can be completed more quickly, allowing for a faster return to normal service. By quickly completing the detach process and returning to normal service, the terminal can shorten the time to enter normal operation and enter sleep mode, reducing power consumption.

[0053] See Figure 3 , Figure 3 This is a schematic diagram of the structure of a de-adhesion device provided in an embodiment of this application. Figure 3 As shown, the de-adhesion device 300 includes:

[0054] The first sending module 301 is used to send a detach request message to the network-side device and start a waiting timer;

[0055] The second sending module 302 is used to send the detach request message to the network-side device again and restart the waiting timer before the timer expires, if the terminal determines that detaching has failed.

[0056] Optionally, the terminal determines that de-attachment has failed, including at least one of the following:

[0057] The terminal receives a release link message sent by the network-side device;

[0058] The terminal disconnects the communication link between itself and the network-side device.

[0059] Optionally, the de-adhesion device may further include:

[0060] The third sending module is used to send a request message to the network-side device to establish the communication link when the terminal determines that the detachment has failed.

[0061] Optionally, the second sending module 302 may specifically include:

[0062] The sending unit is used to send the detach request message to the network-side device again through the communication link established by the request message for establishing the communication link.

[0063] Optionally, the second sending module 302 may specifically include:

[0064] The shutdown unit is used to close the waiting timer if the terminal determines that the detachment has failed before the waiting timer expires, and then send the detachment request message to the network-side device again, and restart the waiting timer.

[0065] The de-attachment device 300 can achieve the functions described in the embodiments of this application. Figure 1 The various processes in the method embodiments, and the ways to achieve the same beneficial effects, will not be repeated here to avoid repetition.

[0066] This application also provides a terminal. Please refer to the embodiments therein. Figure 4 The terminal 400 includes a processor 401, a memory 402, and a program or instructions stored in the memory 402 and executable on the processor 401. When the program or instructions are executed by the processor 401, they implement the above-mentioned functions. Figure 1 The various processes of the de-attachment method embodiments described herein can achieve the same technical effect, and will not be repeated here to avoid repetition.

[0067] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by hardware related to program instructions, and the program can be stored in a readable medium.

[0068] This application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium stores a computer program, which, when executed by a processor, can perform the above-described functions. Figure 1 To avoid repetition, any steps in the corresponding method embodiments will not be described again here.

[0069] The storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0070] The above description represents the preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for removing adhesion, characterized in that, include: The terminal sends a detach request message to the network-side device and starts a waiting timer; Before the waiting timer expires, if the terminal determines that the detachment has failed, the terminal sends a request message to the network-side device to establish a communication link. Then, the terminal sends the detachment request message to the network-side device again and restarts the waiting timer. The terminal determines that de-attachment has failed, including at least one of the following: The terminal receives a release link message sent by the network-side device; The terminal disconnects the communication link between itself and the network-side device. The terminal sends the detach request message to the network-side device again, including: The terminal sends the detach request message to the network-side device again through the communication link established by the request message to establish the communication link.

2. The method as described in claim 1, characterized in that, Before the waiting timer expires, if the terminal determines that the detachment has failed, the terminal sends the detachment request message to the network-side device again and restarts the waiting timer, including: If the terminal determines that the detachment has failed before the waiting timer expires, the terminal closes the waiting timer, sends the detachment request message to the network-side device again, and restarts the waiting timer.

3. A de-adhesion device, characterized in that, include: The first sending module is used to send a detach request message to the network-side device and to start a waiting timer; The second sending module is used to send a request message to the network-side device to establish a communication link before the waiting timer expires, in the case where the terminal determines that the detachment has failed. Then, the terminal sends the detachment request message to the network-side device again and restarts the waiting timer. The terminal determines that de-attachment has failed, including at least one of the following: The terminal receives a release link message sent by the network-side device; The terminal disconnects the communication link between itself and the network-side device. The second sending module is also used for: The terminal sends the detach request message to the network-side device again through the communication link established by the request message to establish the communication link.

4. The apparatus as described in claim 3, characterized in that, The second sending module includes: The shutdown unit is used to close the waiting timer if the terminal determines that the detachment has failed before the waiting timer expires, and then send the detachment request message to the network-side device again, and restart the waiting timer.

5. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps in the de-attachment method as described in claim 1 or 2.

6. A readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the steps in the de-attachment method as described in claim 1 or 2.

Images