A user entity release method and base station

Abstract

The embodiment of the present application provides a user entity release method and a base station. In the scheme, the base station sends a user release message to the terminal and starts a HARQ process. The user release message is used to indicate the release of the user entity on the terminal. When a first confirmation success message sent by the terminal is received through the HARQ process, the user entity is released. The first confirmation success message is used to indicate that the terminal has successfully received the user release message. Applying the technical solution provided by the embodiment of the present application can shorten the time of the user entity release process and save network resources.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a user entity release method and a base station. Background Art

[0002] At present, in the process of user entity release initiated by the base station, after the base station sends the user release message to the terminal, the RLC (Radio Link Control) module of the terminal immediately passes the user release message to the RRC (Radio Resource Control) module of the terminal after receiving the user release message. After the RRC module of the terminal receives the user release message, it immediately releases the user entity. After the RLC module of the terminal receives the user release message, it needs a certain processing time to send a status report for the user entity to the base station. During a period of processing time, the RRC module of the terminal is likely to have released the user entity. In the case where the user entity has been released, the RLC module of the terminal will not send a status report to the base station.

[0003] In this case, the base station cannot receive the status report and can only release the user entity after the user release timer times out, which prolongs the time of the user entity release process. In addition, during the period of waiting for the user release timer to time out, the base station will repeatedly send user release messages to the terminal, which greatly wastes network resources. Summary of the invention

[0004] The purpose of the embodiment of the present application is to provide a user entity release method and a base station to shorten the time of the user entity release process and save network resources. The specific technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a user entity release method, which is applied to a base station, and the method includes:

[0006] Sending a user release message to the terminal and starting a HARQ (Hybrid Automatic Repeat Request) process, wherein the user release message is used to indicate a message for releasing a user entity on the terminal;

[0007] When a first confirmation success message sent by the terminal is received through the HARQ process, the user entity is released, where the first confirmation success message is used to indicate that the terminal has successfully received the user release message.

[0008] Optionally, the method further includes:

[0009] When a first confirmation failure message sent by the terminal is received through the HARQ process, a user release message is resent to the terminal until the first confirmation success message sent by the terminal is received through the HARQ process.

[0010] Optionally, the method further includes:

[0011] Start the ARQ (Automatic Repeat Request) process;

[0012] When the status report for the user entity sent by the terminal is successfully received through the ARQ process, the user entity is released, and a second confirmation success message is sent to the terminal, where the second confirmation success message indicates that the base station has successfully received the status report.

[0013] Optionally, the method further includes:

[0014] When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, a second confirmation failure message is sent to the terminal, and the second confirmation failure message indicates that the base station has not successfully received the status report, so that the terminal re-sends the status report to the base station.

[0015] Optionally, the method further includes:

[0016] When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, if it is determined that the user entity has been released, the second confirmation success message is sent to the terminal.

[0017] In a second aspect, an embodiment of the present application provides a base station, including a memory, a transceiver, and a processor; the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0018] Sending a user release message to the terminal and starting a HARQ process, wherein the user release message is used to indicate a message for releasing a user entity on the terminal;

[0019] When a first confirmation success message sent by the terminal is received through the HARQ process, the user entity is released, where the first confirmation success message is used to indicate that the terminal has successfully received the user release message.

[0020] Optionally, the processor is further configured to read the computer program in the memory and perform the following operations:

[0021] When a first confirmation failure message sent by the terminal is received through the HARQ process, a user release message is resent to the terminal until the first confirmation success message sent by the terminal is received through the HARQ process.

[0022] Optionally, the processor is further configured to read the computer program in the memory and perform the following operations:

[0023] Start the ARQ process;

[0024] When the status report for the user entity sent by the terminal is successfully received through the ARQ process, the user entity is released, and a second confirmation success message is sent to the terminal, where the second confirmation success message indicates that the base station has successfully received the status report.

[0025] Optionally, the processor is further configured to read the computer program in the memory and perform the following operations:

[0026] When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, a second confirmation failure message is sent to the terminal, and the second confirmation failure message indicates that the base station has not successfully received the status report, so that the terminal re-sends the status report to the base station.

[0027] Optionally, the processor is further configured to read the computer program in the memory and perform the following operations:

[0028] When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, if it is determined that the user entity has been released, the second confirmation success message is sent to the terminal.

[0029] In a third aspect, an embodiment of the present application provides a base station, the base station comprising:

[0030] A sending module, used to send a user release message to the terminal to start the HARQ process, wherein the user release message is used to indicate a message for releasing a user entity on the terminal;

[0031] A release module is used to release the user entity when a first confirmation success message sent by the terminal is received through the HARQ process, wherein the first confirmation success message is used to indicate that the terminal has successfully received the user release message.

[0032] In a fourth aspect, an embodiment of the present application provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute any of the user entity release methods described above.

[0033] In a fifth aspect, an embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute any of the user entity release methods described above.

[0034] In the technical solution provided by the embodiment of the present application, when the base station receives the first confirmation success message sent by the terminal through the HARQ process, the user entity is released. Among them, the terminal will not fail to send the first confirmation success message because the user entity has been released, and the time when the terminal sends the first confirmation success message is earlier than the time when the terminal sends the status report. Therefore, the embodiment of the present application greatly shortens the time of the user entity release process. In addition, in the embodiment of the present application, the base station releases the user entity based on the first confirmation success message. Therefore, the user release message will not be repeatedly sent to the terminal due to the delay in receiving the status report, which saves network resources.

[0035] Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other embodiments can be obtained based on these drawings without paying any creative work.

[0037] Figure 1 A flow chart of a user entity release method in the prior art;

[0038] Figure 2 A schematic diagram of a first flow chart of a user entity release method provided in an embodiment of the present application;

[0039] Figure 3 A second flow chart of the user entity release method provided in an embodiment of the present application;

[0040] Figure 4 A schematic diagram of the structure of an ARQ / HARQ system provided in an embodiment of the present application;

[0041] Figure 5 An interactive schematic diagram of detecting and resolving residual errors in an ARQ / HARQ system provided in an embodiment of the present application;

[0042] Figure 6 Another interactive schematic diagram of detecting and resolving residual errors in an ARQ / HARQ system provided in an embodiment of the present application;

[0043] Figure 7A schematic diagram of another interaction for detecting and resolving residual errors in an ARQ / HARQ system provided in an embodiment of the present application;

[0044] Figure 8 A third flow chart of the user entity release method provided in an embodiment of the present application;

[0045] Fig. 9 A fourth flow chart of the user entity release method provided in an embodiment of the present application;

[0046] Fig.10 A fifth flow chart of the user entity release method provided in an embodiment of the present application;

[0047] Fig.11 A sixth flow chart of the user entity release method provided in an embodiment of the present application;

[0048] Fig.12 An interactive schematic diagram of user entity release provided in an embodiment of the present application;

[0049] Fig.13 A schematic diagram of a structure of a user entity release device provided in an embodiment of the present application;

[0050] Fig.14 A schematic diagram of the structure of a base station provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0052] At present, the process of user entity release initiated by the base station is as follows: Figure 1 As shown, the following steps are included:

[0053] Step S11, the RRC module of the base station sends a user release message to the PDCP (Packet Data Convergence Protocol) module of the base station.

[0054] Among them, the user release message can also be called a Release message.

[0055] Step S12: The PDCP module of the base station processes the user release message according to the packet data convergence protocol, and sends the processed user release message to the RLC module of the base station.

[0056] Step S13: The RLC module of the base station processes the user release message according to the radio link layer control protocol, and sends the processed user release message to the MAC (Media Access Control) module of the base station.

[0057] After the RLC module of the base station sends the processed user release message to the MAC module of the base station, it waits for a status report returned by the RLC module of the terminal.

[0058] In step S14, the MAC module of the base station sends the user release message to the bottom layer, that is, sends the user release message to the MAC module of the terminal through the air interface. In addition, the MAC module of the base station starts the hybrid automatic repeat request HARQ process to wait for the ACK (Acknowledge) message returned by the MAC module of the terminal.

[0059] The ACK message is used to indicate that the terminal has successfully received the user release message.

[0060] Step S15, after successfully receiving the user release message, the MAC module of the terminal returns an ACK message to the MAC module of the base station, and sends the user release message to the RLC module of the terminal.

[0061] Step S16, the RLC module of the terminal processes the user release message according to the radio link layer control protocol, sends the processed user release message to the PDCP module of the terminal, and sends a status report to the RLC module of the base station.

[0062] Step S17, the PDCP module of the terminal processes the user release message according to the packet data convergence protocol, and sends the processed user release message to the RRC module of the terminal.

[0063] Step S18: The RRC module of the terminal releases the user entity according to the user release message.

[0064] Step S19: The RLC module of the base station sends a release notification to the RRC of the base station according to the status report.

[0065] Step S110: The RRC of the base station releases the user entity according to the release notification.

[0066] In the related art, after receiving the user release message, the RLC module of the terminal immediately transmits the user release message to the RRC module of the terminal. After receiving the user release message, the RRC module of the terminal immediately releases the user entity. However, after receiving the user release message, the RLC module of the terminal needs a certain processing time before sending a status report to the base station. During the processing time, the RRC module of the terminal is likely to have released the user entity. In the case where the user entity has been released, the RLC module of the terminal will not send a status report to the base station.

[0067] In this case, the base station cannot receive the status report and can only release the user entity after the user release timer times out, which prolongs the time of the user entity release process. In addition, during the period of waiting for the user release timer to time out, the base station will repeatedly send user release messages to the terminal, which greatly wastes network resources.

[0068] To solve the above problems, an embodiment of the present application provides a method for releasing a user entity. In the method, when the base station receives a first confirmation success message sent by a terminal through a HARQ process, the user entity is released. The terminal will not fail to send the first confirmation success message because the user entity has been released, and the time when the terminal sends the first confirmation success message is earlier than the time when the terminal sends a status report. Therefore, the embodiment of the present application greatly shortens the time of the user entity release process. In addition, in the embodiment of the present application, the base station releases the user entity based on the first confirmation success message. Therefore, the user release message will not be repeatedly sent to the terminal due to the delay in receiving the status report, thereby saving network resources.

[0069] The user entity release method provided in the embodiment of the present application is described in detail below through a specific embodiment.

[0070] See also Figure 2 , Figure 2 A first flow chart of a user entity release method provided in an embodiment of the present application is applied to a base station. The base station may be a 4G base station (ie, eNB (evolved Node Base Station)) or a 5G base station (ie, gNB (next Generation Node Base Station)), without limitation. The method comprises the following steps:

[0071] Step S21, sending a user release message to the terminal and starting a HARQ process. The user release message is used to indicate a message for releasing a user entity on the terminal.

[0072] After the base station initiates the process of releasing the user entity, it sends a user release message to the terminal and starts the HARQ process to ensure that the terminal successfully receives the user release message.

[0073] In one embodiment, if the base station does not receive access data from the user entity after a preset period of time, it can be determined that the user entity has gone offline, and the base station initiates the process of releasing the user entity. In another embodiment, after the base station receives a user release message input by a manager, it initiates the process of releasing the user entity.

[0074] In the embodiment of the present application, the manner in which the base station initiates the user entity release process is not limited.

[0075] Step S22: When a first confirmation success message sent by the terminal is received through the HARQ process, the user entity is released. The first confirmation success message is used to indicate that the terminal has successfully received the user release message.

[0076] When the terminal successfully receives the user release message, the terminal returns an ACK message, such as a first confirmation success message, to the base station through the HARQ process. When the base station receives the first confirmation success message sent by the terminal through the HARQ process, the base station releases the user entity.

[0077] In the technical solution provided by the embodiment of the present application, when the base station receives the first confirmation success message sent by the terminal through the HARQ process, the user entity is released. Among them, the terminal will not fail to send the first confirmation success message because the user entity has been released, and the time when the terminal sends the first confirmation success message is earlier than the time when the terminal sends the status report. Therefore, the embodiment of the present application greatly shortens the time of the user entity release process. In addition, in the embodiment of the present application, the base station releases the user entity based on the first confirmation success message. Therefore, the user release message will not be repeatedly sent to the terminal due to the delay in receiving the status report, which saves network resources.

[0078] In an optional embodiment, if the terminal fails to successfully receive the user release message, the terminal returns a NACK (N-Acknowledge) message, such as a first confirmation failure message, to the base station through the HARQ process. When the base station receives the first confirmation failure message sent by the terminal through the HARQ process, the base station resends the user release message to the terminal.

[0079] If the base station receives the first confirmation failure message sent by the terminal again through the HARQ process, the base station resends the user release message to the terminal again, and repeats this process until the base station receives the first confirmation success message sent by the terminal through the HARQ process.

[0080] In the embodiment of the present application, the base station continuously resends the user release message through the above-mentioned HARQ process until the terminal successfully receives the user release message, thereby ensuring that the terminal can receive the user release message, and further ensuring that the terminal and the base station successfully release the user entity.

[0081] In an optional embodiment, after the base station sends a user release message to the terminal, the ARQ process is started. After receiving the user release message, the terminal sends a status report to the base station based on the user release message. When the base station successfully receives the status report for the user entity sent by the terminal through the ARQ process, the base station releases the user entity. In addition, the base station sends an ACK message to the terminal, such as a second confirmation success message, and the second confirmation success message indicates that the base station has successfully received the status report. After receiving the second confirmation success message, the terminal will no longer send a status report to the base station, saving network resources.

[0082] In the embodiment of the present application, the base station will release the user entity upon receiving the first confirmation success message and the status report, which provides double protection for the base station to release the user entity and ensures the integrity of the base station's process of releasing the user entity.

[0083] In an optional embodiment, when the base station fails to successfully receive the status report for the user entity sent by the terminal through the ARQ process, the base station sends a second confirmation failure message to the terminal, and the second confirmation failure message indicates that the base station has not successfully received the status report, so that the terminal re-sends the status report to the base station.

[0084] In the embodiment of the present application, the base station receives a status report for a user entity sent by the terminal through an ARQ process, and there is an error in the status report, then it is determined that the status report has not been successfully received, and the base station sends a NACK message to the terminal, such as a second confirmation failure message. After the terminal receives the second confirmation failure message through the ARQ process, it resends the status report to the base station to ensure that the base station successfully receives the status report, thereby achieving double protection for the base station to release the user entity.

[0085] In an optional embodiment, when the base station fails to successfully receive the status report for the user entity sent by the terminal through the ARQ process, if it is determined that the user entity has been released, the base station sends a second confirmation success message to the terminal.

[0086] In the embodiment of the present application, when the base station fails to successfully receive the status report for the user entity sent by the terminal through the ARQ process, the base station determines whether the user entity has been released. If it is determined that the user entity has been released, the base station sends a second confirmation success message to the terminal. In this way, the terminal no longer retransmits the status report to the base station to save network resources.

[0087] If it is determined that the user entity is not released, the base station sends a second confirmation failure message to the terminal. After receiving the second confirmation failure message through the ARQ process, the terminal resends the status report to the base station to ensure that the base station successfully receives the status report, thereby achieving double guarantee for the base station to release the user entity.

[0088] Based on the above embodiments, the following embodiments provide a possible implementation in an actual application scenario, taking the example that a base station may include a MAC module, an RRC module, an RLC module and a PDCP module. For ease of distinction, the MAC module of the base station is referred to as the first MAC module, the RRC module of the base station is referred to as the first RRC module, the RLC module of the base station is referred to as the first RLC module, and the PDCP module of the base station is referred to as the first PDCP module. In actual implementation, the first MAC module of the base station can send a user release message to the second MAC module of the terminal, and start the HARQ process. The ARQ process is started through the first RLC module of the base station. Figure 3 As shown, the user entity release method may include the following steps:

[0089] Step S31: The first RRC module sends a user release message to the first RLC module through the first PDCP module. The user release message is a message for indicating the release of a user entity on the terminal.

[0090] After the base station initiates the process of releasing the user entity, the first RRC module sends a user release message to the first PDCP module. After receiving the user release message sent by the first RRC module, the first PDCP module processes the user release message according to the packet data convergence protocol and sends the processed user release message to the first RLC module.

[0091] Step S32: The first RLC module sends a user release message to the first MAC module.

[0092] In an embodiment of the present application, after the first RLC module receives the user release message sent by the first PDCP module, it processes the user release message according to the wireless link layer control protocol and sends the processed user release message to the first MAC module.

[0093] Step S33: The first MAC module sends a user release message to the second MAC module of the terminal and starts a HARQ process.

[0094] The second MAC module of the terminal actually refers to the MAC module of the terminal. The first MAC module and the second MAC module are used here only to distinguish the MAC modules of the base station and the terminal. The first and second writings of the RLC module, PDCP module and RRC module are also to distinguish the corresponding modules on the base station side and the terminal side. No further details will be given here.

[0095] In the embodiment of the present application, after the first MAC module receives the user release message sent by the first RLC module, it sends the user release message to the MAC module of the terminal (i.e., the second MAC module) through the air interface. While sending the user release message to the second MAC module, the first MAC module starts the HARQ process to wait for the ACK message returned by the MAC module of the terminal.

[0096] Step S34, when the first MAC module receives the first confirmation success message sent by the second MAC module through the HARQ process, the first MAC module sends a release notification to the first RRC module, and the first confirmation success message is used to indicate that the terminal has successfully received the user release message.

[0097] When the second MAC module of the terminal successfully receives the user release message, it returns an ACK message, such as a first confirmation success message, to the first MAC module through the HARQ process. When the first MAC module receives the first confirmation success message sent by the second MAC module through the HARQ process, the first MAC module sends a release notification to the first RRC module. The release notification is used to notify the first RRC module to release the user entity.

[0098] Step S35: The first RRC module releases the user entity according to the release notification.

[0099] The first RRC receives a release notification sent by the first MAC module, and releases the user entity based on the release notification.

[0100] In the technical solution provided by the embodiment of the present application, when the MAC module of the base station receives the first confirmation success message sent by the MAC module of the terminal through the HARQ process, it sends a release notification to the RRC module of the base station, and then the RRC module of the base station releases the user entity. Among them, the MAC module of the terminal will not fail to send the first confirmation success message because the user entity has been released, and the time when the MAC module of the terminal sends the first confirmation success message is earlier than the time when the RLC module of the terminal sends the status report. Therefore, the embodiment of the present application greatly shortens the time of the user entity release process. In addition, in the embodiment of the present application, the RRC module of the base station releases the user entity based on the first confirmation success message. Therefore, it will not repeatedly send user release messages to the terminal due to the delay in receiving the status report, saving network resources.

[0101] In the embodiment of the present application, the HARQ system consists of an ARQ (Automatic Repeat reQuest) system and an FEC (Forward Error Correction) system. The FEC system is used to correct errors that often occur in the channel to reduce the number of retransmissions, thereby improving the communication efficiency of the HARQ system. The role of the ARQ system is to correct those errors that do not occur frequently and cannot be corrected by the FEC system to improve the reliability of the HARQ system. Therefore, the HARQ system can achieve much higher reliability than the FEC system and higher transmission efficiency than the ARQ system.

[0102] In the HARQ system, a code capable of detecting and correcting errors, such as an (n, k) linear code, can be used. When an error code is found in the received code group, the receiving end first determines the error and performs error correction. If the number of error codes is within the preset error correction range, the error code will be corrected, and the receiving end will transmit the decoded message to the user. If the number of error codes exceeds the preset error correction range, that is, the error code cannot be corrected, the receiving end prohibits the transmission of the code group to the user, and feeds back a NACK message to the sending end through the channel to request the retransmission of the code group.

[0103] When the receiving end receives the retransmitted code group, it will try to correct its error code again. If the decoding is unsuccessful, the receiving end will reject the code group again and request another retransmission. The error correction and retransmission process continues until the code group is successfully received or correctly decoded.

[0104] In the NR (New Radio) network, in order to provide sufficient transmission reliability for upper layer applications, a dual ARQ protocol structure is adopted in the L2 layer (i.e., data link layer), and the ARQ system is located above the HARQ system. The ARQ / HARQ system is located in the eNB. The ARQ system is completed by the RLC module, the HARQ system is completed by the physical layer, and the control of the HARQ system is completed by the MAC module. The structure of the ARQ / HARQ system of the base station is as follows: Figure 4 In the RLC module, each UE (User Equipment) occupies two segmented ARQ protocols respectively, and in the MAC module, each UE occupies one HARQ protocol.

[0105] In the embodiment of the present application, the base station can detect and resolve the remaining errors through ARQ / HARQ system interaction. Figure 5-7, as follows: There is a control ARQ (C-ARQ) entity in each of the MAC module of the receiving end and the MAC module of the transmitting end. After receiving the data, the receiving end performs HARQ error detection. When the receiving end detects an error, it sends a local NACK to the local C-ARQ entity through the HARQ process. The C-ARQ entity of the receiving end sends an error indication message (which can be called HARQ error indication) to the C-ARQ entity of the transmitting end through the C-PDU (control Protocol Data Unit) of the MAC module. The error indication message carries the HARQ process ID (HARQ process ID) and frame number (Frame number) of the PDU where the error occurs. The C-ARQ entity of the transmitting end analyzes the ARQ PDU involved in this error according to the information carried by the error indication message, and triggers the local ARQ to perform related operations, such as retransmitting data. The above errors include CRC (Cyclic Redundancy Check) errors, NACK / ACK errors, etc. The specific contents are as follows.

[0106] (1) NACK / ACK residual error detection and recovery.

[0107] In uplink HARQ transmission, if CRC (Cyclic Redundancy Check) is introduced in the downlink feedback channel of ACK / NACK, it can be assumed that NACK / ACK errors will not occur, so downlink HARQ transmission is mainly considered. The process of ARQ / HARQ detecting and correcting errors generated when continuously sending transport blocks (i.e. data) is as follows Figure 5 shown.

[0108] For error correction when sending isolated transmission blocks, if the receiving end knows the maximum number of transmission times of the sending end, a retransmission timer mechanism can be introduced, using Figure 6 The error correction process shown in FIG. 1 is related to the specific mechanism of the HARQ system. If the receiving end adopts a synchronous HARQ system, the time of the retransmission timer can be strictly set; if the receiving end adopts an asynchronous HARQ system, the time of the retransmission timer needs to be accurately adjusted to obtain the best detection performance.

[0109] When the transmitting end receives a NACK message and the number of data retransmissions does not reach the maximum number of retransmissions, but the data transmitted by the HARQ system is discarded, an ARQ polling mechanism can be used to perform error recovery.

[0110] (2) DTX (Discontinuous Transmission) / ACK Residual Error and Recovery

[0111] In the uplink HARQ transmission process, the eNB performs scheduling and feedbacks ACK or NACK, so that DTX / ACK residual errors will not occur. For downlink HARQ transmission, after a DTX / ACK error occurs and the ARQ system of the receiving end detects segment loss, the error can be resolved through status reporting; if it is an isolated transmitting end, the transmitting end can resolve possible message errors through ARQ polling.

[0112] (3) HARQ failure detection and recovery

[0113] HARQ failures are caused by the transmitter giving up transmission, so HARQ failures can be caused by the transmitter's HARQ system sending a local NACK to the transmitter's ARQ system, triggering the corresponding ARQ retransmission, such as Figure 7 shown.

[0114] In the present application embodiment, based on the above Figure 4-7 The ARQ system and HARQ system shown in the figure realize the release of the user entity. Figure 4-7 The data N and data M are only used to distinguish different data and do not play a limiting role.

[0115] In one embodiment of the present application, based on Figure 3 The user entity release method shown in the embodiment of the present application also provides a user entity release method, such as Figure 8 As shown, the following steps may also be included:

[0116] Step S36, when the first MAC module receives the first confirmation failure message sent by the second MAC module through the HARQ process, the first MAC module re-sends the user release message to the second MAC module of the terminal.

[0117] When the second MAC module of the terminal fails to successfully receive the user release message, such as an error in the received message and the user release message is not successfully decoded, a NACK message, such as a first confirmation failure message, is returned to the first MAC module through the HARQ process. When the first MAC module receives the first confirmation failure message sent by the second MAC module through the HARQ process, the first MAC module resends the user release message to the second MAC module of the terminal.

[0118] If the first MAC module receives the first confirmation failure message sent by the second MAC module again through the HARQ process, the first MAC module will resend the user release message to the second MAC module of the terminal until the first MAC module receives the first confirmation success message sent by the second MAC module through the HARQ process.

[0119] In an embodiment of the present application, the first MAC module continuously resends the user release message through the above-mentioned HARQ process until the terminal successfully receives the user release message, thereby ensuring that the terminal can receive the user release message, and further ensuring that the terminal and the base station successfully release the user entity.

[0120] In one embodiment of the present application, based on Figure 2 The user entity release method shown in the embodiment of the present application also provides a user entity release method, such as Fig. 9 As shown, the following steps may also be included:

[0121] Step S37: The first RLC module starts the ARQ process.

[0122] In an embodiment of the present application, the first RLC module may start an ARQ process while sending a user release message to the first MAC module to wait for a status report for the user entity sent by the second RLC module of the receiving terminal.

[0123] Step S38, when the first RLC module successfully receives the status report for the user entity sent by the second RLC module of the terminal through the ARQ process, the first RLC module sends a release notification to the first RRC module and sends a second confirmation success message to the second RLC module, and the second confirmation success message indicates that the base station has successfully received the status report.

[0124] In an embodiment of the present application, after the second RLC module of the terminal receives the user release message, it sends a status report to the first RLC module based on the user release message. When the first RLC module successfully receives the status report for the user entity sent by the second RLC module of the terminal through the ARQ process, the first RLC module sends a release notification to the first RRC module, and the first RRC module releases the user entity according to the release notification sent by the first RLC module. In addition, while the first RLC module sends the release notification to the first RRC module, it can also send an ACK message to the second RLC module, such as a second confirmation success message, to inform the second RLC module that the base station has successfully received the status report, so that the second RLC module stops sending the status report and saves network resources.

[0125] In the embodiment of the present application, the first MAC module receives the first confirmation success message and sends a release notification to the first RRC module. The first RLC module receives the status report and also sends a release notification to the first RRC module. This provides double protection for the first RRC module to release the user entity, ensuring the integrity of the base station's process of releasing the user entity.

[0126] In one embodiment of the present application, based on Fig. 9 The user entity release method shown in the embodiment of the present application also provides a user entity release method, such as Fig.10 As shown, the following steps may also be included:

[0127] Step S39, when the first RLC module fails to successfully receive the status report for the user entity sent by the second RLC module through the ARQ process, the first RLC module sends a second confirmation failure message to the second RLC module, and the second confirmation failure message indicates that the base station has not successfully received the status report, so that the second RLC module re-sends the status report to the first RLC module.

[0128] In an embodiment of the present application, the first RLC module receives a status report for a user entity sent by the second RLC module through an ARQ process, and there is an error in the status report, then it is determined that the status report has not been successfully received, and the first RLC module sends a NACK message to the second RLC module, such as a second confirmation failure message.

[0129] After receiving the second confirmation failure message through the ARQ process, the second RLC module resends the status report to the first RLC module to ensure that the first RLC module successfully receives the status report, thereby achieving double protection for the first RRC module to release the user entity.

[0130] In one embodiment of the present application, based on Fig. 9 The user entity release method shown in the embodiment of the present application also provides a user entity release method, such as Fig.11 As shown, the following steps may also be included:

[0131] Step S310: When the first RLC module fails to successfully receive the status report for the user entity sent by the second RLC module through the ARQ process, if the first RLC module determines that the user entity has been released, it sends a second confirmation success message to the second RLC module.

[0132] In the embodiment of the present application, when the first RLC module fails to successfully receive the status report for the user entity sent by the second RLC module through the ARQ process, the first RLC module determines whether the user entity has been released. If it is determined that the user entity has been released, the first RLC module sends a second confirmation success message to the second RLC module. In this way, the second RLC module no longer retransmits the status report to the first RLC module to save network resources.

[0133] If it is determined that the user entity has not been released, the first RLC module sends a second confirmation failure message to the second RLC module. After receiving the second confirmation failure message through the ARQ process, the second RLC module resends the status report to the first RLC module to ensure that the first RLC module successfully receives the status report, thereby achieving double protection for the first RRC module to release the user entity.

[0134] Below through Fig.12 The interaction diagram shown provides a detailed description of the user entity release method provided in an embodiment of the present application.

[0135] Step S121, the RRC module of the base station sends a user release message to the PDCP module of the base station.

[0136] Step S122: The PDCP module of the base station processes the user release message according to the packet data convergence protocol, and sends the processed user release message to the RLC module of the base station.

[0137] Step S123, the RLC module of the base station processes the user release message according to the radio link layer control protocol, and sends the processed user release message to the MAC module of the base station.

[0138] In step S124, the MAC module of the base station sends a user release message to the MAC module of the terminal through the air interface, and starts a HARQ process to wait for an ACK message returned by the MAC module of the terminal.

[0139] Step S125: After successfully receiving the user release message, the MAC module of the terminal returns an ACK message to the MAC module of the base station and sends the user release message to the RLC module of the terminal. Then, step S126 and step S129 are executed.

[0140] Step S126: The RLC module of the terminal processes the user release message according to the radio link layer control protocol, sends the processed user release message to the PDCP module of the terminal, and sends a status report to the RLC module of the base station. Then, step S127 and step S129 are executed.

[0141] Step S127, the PDCP module of the terminal processes the user release message according to the packet data convergence protocol, and sends the processed user release message to the RRC module of the terminal.

[0142] Step S128: The RRC module of the terminal releases the user entity according to the user release message.

[0143] Step S129: After receiving the ACK message / status report, the MAC module of the base station sends a release notification to the RRC module of the base station. Then, step S1210 is executed.

[0144] Step S1210: The RRC module of the base station releases the user entity according to the release notification.

[0145] The description of the above steps S121-S1210 is relatively simple, please refer to the above Figure 2-11 The description of part is not repeated here.

[0146] Corresponding to the above-mentioned user entity release method, the embodiment of the present application also provides a user entity release device, see Fig.13 As shown, the device comprises:

[0147] The sending unit 131 is used to send a user release message to the terminal and start the HARQ process. The user release message is used to indicate the release of the user entity on the terminal;

[0148] The releasing unit 132 is configured to release the user entity when a first confirmation success message sent by the terminal is received through the HARQ process, where the first confirmation success message is used to indicate that the terminal has successfully received the user release message.

[0149] Optionally, the sending unit 131 may also be configured to, when a first confirmation failure message sent by the terminal is received through the HARQ process, resend a user release message to the terminal until a first confirmation success message sent by the terminal is received through the HARQ process.

[0150] Optionally, the sending unit 131 can also be used to start the ARQ process; when the status report for the user entity sent by the terminal is successfully received through the ARQ process, the user entity is released and a second confirmation success message is sent to the terminal, and the second confirmation success message indicates that the base station has successfully received the status report.

[0151] Optionally, the sending unit 131 can also be used to send a second confirmation failure message to the terminal when the status report for the user entity sent by the terminal is not successfully received through the ARQ process. The second confirmation failure message indicates that the base station has not successfully received the status report, so that the terminal re-sends the status report to the base station.

[0152] Optionally, the sending unit 131 may be further configured to send a second confirmation success message to the terminal if it is determined that the user entity has been released, when a status report for the user entity sent by the terminal is not successfully received through the ARQ process.

[0153] In the technical solution provided by the embodiment of the present application, when the base station receives the first confirmation success message sent by the terminal through the HARQ process, the user entity is released. Among them, the terminal will not fail to send the first confirmation success message because the user entity has been released, and the time when the terminal sends the first confirmation success message is earlier than the time when the terminal sends the status report. Therefore, the embodiment of the present application greatly shortens the time of the user entity release process. In addition, in the embodiment of the present application, the base station releases the user entity based on the first confirmation success message. Therefore, the user release message will not be repeatedly sent to the terminal due to the delay in receiving the status report, which saves network resources.

[0154] Corresponding to the above-mentioned user entity release method, the embodiment of the present application also provides a base station, such as Fig.14 As shown, it includes a memory 141, a transceiver 142 and a processor 143; the memory 141 is used to store computer programs; the transceiver 142 is used to send and receive data under the control of the processor 143; the processor 143 is used to read the computer program in the memory 141 and perform the following operations:

[0155] Send a user release message to the terminal and start the HARQ process. The user release message is used to indicate the release of the user entity on the terminal;

[0156] When a first confirmation success message sent by the terminal is received through the HARQ process, the user entity is released, and the first confirmation success message is used to indicate that the terminal has successfully received the user release message.

[0157] Optionally, the processor 143 may also be configured to read a computer program in the memory and perform the following operations:

[0158] When a first confirmation failure message sent by the terminal is received through the HARQ process, a user release message is resent to the terminal until a first confirmation success message sent by the terminal is received through the HARQ process.

[0159] Optionally, the processor 143 may also be configured to read a computer program in the memory and perform the following operations:

[0160] Start the ARQ process; when the status report for the user entity sent by the terminal is successfully received through the ARQ process, release the user entity and send a second confirmation success message to the terminal, the second confirmation success message indicates that the base station has successfully received the status report.

[0161] Optionally, the processor 143 may also be configured to read a computer program in the memory and perform the following operations:

[0162] When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, a second confirmation failure message is sent to the terminal, indicating that the base station has not successfully received the status report, so that the terminal resends the status report to the base station.

[0163] Optionally, the processor 143 may also be configured to read a computer program in the memory and perform the following operations:

[0164] When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, if it is determined that the user entity has been released, a second confirmation success message is sent to the terminal.

[0165] In the technical solution provided by the embodiment of the present application, when the base station receives the first confirmation success message sent by the terminal through the HARQ process, the user entity is released. Among them, the terminal will not fail to send the first confirmation success message because the user entity has been released, and the time when the terminal sends the first confirmation success message is earlier than the time when the terminal sends the status report. Therefore, the embodiment of the present application greatly shortens the time of the user entity release process. In addition, in the embodiment of the present application, the base station releases the user entity based on the first confirmation success message. Therefore, the user release message will not be repeatedly sent to the terminal due to the delay in receiving the status report, which saves network resources.

[0166] exist Fig.14 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 143 and various circuits of memory represented by memory 141 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 142 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the bus interface may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to keypads, displays, speakers, microphones, joysticks, and the like.

[0167] The memory 141 may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory 141 may also be at least one storage device located away from the aforementioned processor.

[0168] The processor 143 is responsible for managing the bus architecture and general processing, and the memory 141 can store data used by the processor 143 when performing operations.

[0169] Optionally, the processor 143 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0170] In another embodiment provided in the present application, a processor-readable storage medium is further provided, and the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute any of the user entity release methods described above.

[0171] In another embodiment provided by the present application, a computer program is also provided, which, when executed on a processor, enables the processor to execute any of the user entity release methods described above.

[0172] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0173] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0174] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the user entity release device, base station, processor-readable storage medium and computer program embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0175] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A user entity release method, characterized in that: Applied to a base station, the method comprises: Sending a user release message to the terminal and starting a hybrid automatic repeat request HARQ process, wherein the user release message is used to indicate a message for releasing a user entity on the terminal; When a first confirmation success message sent by the terminal is received through the HARQ process, releasing the user entity, wherein the first confirmation success message is used to indicate that the terminal has successfully received the user release message; The method further comprises: Start the automatic repeat request ARQ process; When the status report for the user entity sent by the terminal is successfully received through the ARQ process, the user entity is released, and a second confirmation success message is sent to the terminal, where the second confirmation success message indicates that the base station has successfully received the status report.

2. The method according to claim 1, characterized in that The method further comprises: When a first confirmation failure message sent by the terminal is received through the HARQ process, a user release message is resent to the terminal until the first confirmation success message sent by the terminal is received through the HARQ process.

3. The method according to claim 1, characterized in that: The method further comprises: When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, a second confirmation failure message is sent to the terminal, and the second confirmation failure message indicates that the base station has not successfully received the status report, so that the terminal re-sends the status report to the base station.

4. The method according to claim 1, characterized in that: The method further comprises: When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, if it is determined that the user entity has been released, the second confirmation success message is sent to the terminal.

5. A base station, characterized in that: The invention comprises a memory, a transceiver and a processor; the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Sending a user release message to the terminal and starting a hybrid automatic repeat request HARQ process, wherein the user release message is used to indicate a message for releasing a user entity on the terminal; When a first confirmation success message sent by the terminal is received through the HARQ process, releasing the user entity, wherein the first confirmation success message is used to indicate that the terminal has successfully received the user release message; The processor is further configured to read the computer program in the memory and perform the following operations: Start the automatic repeat request ARQ process; When the status report for the user entity sent by the terminal is successfully received through the ARQ process, the user entity is released, and a second confirmation success message is sent to the terminal, where the second confirmation success message indicates that the base station has successfully received the status report.

6. The base station according to claim 5, characterized in that The processor is further configured to read the computer program in the memory and perform the following operations: When a first confirmation failure message sent by the terminal is received through the HARQ process, a user release message is resent to the terminal until the first confirmation success message sent by the terminal is received through the HARQ process.

7. The base station according to claim 5, characterized in that The processor is further configured to read the computer program in the memory and perform the following operations: When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, a second confirmation failure message is sent to the terminal, and the second confirmation failure message indicates that the base station has not successfully received the status report, so that the terminal re-sends the status report to the base station.

8. The base station according to claim 5, characterized in that The processor is further configured to read the computer program in the memory and perform the following operations: When the status report for the user entity sent by the terminal is not successfully received through the ARQ process, if it is determined that the user entity has been released, the second confirmation success message is sent to the terminal.

9. A base station, characterized in that: The base station comprises: A sending module, used for sending a user release message to the terminal to start a hybrid automatic repeat request HARQ process, wherein the user release message is used to indicate a message for releasing a user entity on the terminal; A release module, configured to release the user entity when a first confirmation success message sent by the terminal is received through the HARQ process, wherein the first confirmation success message is used to indicate that the terminal has successfully received the user release message; The sending module is also used to start an automatic repeat request ARQ process; when the status report for the user entity sent by the terminal is successfully received through the ARQ process, the user entity is released and a second confirmation success message is sent to the terminal, and the second confirmation success message indicates that the base station has successfully received the status report.

10. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method according to any one of claims 1 to 4.

Images