CN-122028107-A - Connection release message processing method, electronic device, storage medium, and program product
Abstract
The application provides a connection release message processing method, electronic equipment, a storage medium and a program product, and relates to the technical field of communication. According to the method, scene judgment is carried out on the trigger scene of RRC RELEASE messages, whether the bottom layer confirmation feedback needs to be waited or not is dynamically determined, and the differentiated processing strategy is matched, so that the terminal processing efficiency is optimized, and the service processing time delay can be reduced on the premise of guaranteeing the connection release reliability.
Inventors
- SHI CHENHUI
Assignees
- 南京星思半导体有限公司
Dates
- Publication Date
- 20260512
- Application Date
- 20260213
Claims (13)
- 1. A connection release message processing method, applied to a terminal, the method comprising: receiving RRC RELEASE a message from a network device; Determining whether acknowledgement feedback from an underlying layer needs to be waited before processing the RRC RELEASE message according to a trigger scenario associated with the RRC RELEASE message; and selecting a corresponding connection release processing strategy to process the RRC RELEASE messages according to the determined result.
- 2. The method of claim 1, wherein the determining whether acknowledgement feedback from an underlying layer needs to be waited before processing the RRC RELEASE message based on a trigger scenario associated with the RRC RELEASE message comprises: If the trigger scenario associated with the RRC RELEASE message is a terminally released scenario, determining that it is not necessary to wait for acknowledgement feedback from the bottom layer before processing the RRC RELEASE message; if the trigger scenario associated with the RRC RELEASE message is a non-terminating release scenario, then the determination is that acknowledgement feedback from the underlying layer needs to be waited for before processing the RRC RELEASE message.
- 3. The method of claim 2, wherein the terminal release scenario comprises a non-access stratum detach procedure scenario triggered by the terminal shutdown, the trigger scenario identified by: And if the indication information from the non-access layer is received, determining that the trigger scene is a terminative release scene, wherein the indication information is used for representing that the terminal is currently in a shutdown trigger detach process.
- 4. The method of claim 1, wherein selecting a corresponding connection release processing policy to process the RRC RELEASE message according to the determination comprises: If the result of the determination is that the acknowledgement feedback from the bottom layer needs to be waited before the RRC RELEASE message is processed, state information related to the processing of the RRC RELEASE message is obtained, the RRC RELEASE message is processed based on the estimated maximum waiting time length, and the estimated maximum waiting time length is smaller than or equal to the maximum waiting time length, specified by a communication protocol, that the terminal needs to wait for the acknowledgement feedback from the bottom layer after receiving the RRC RELEASE message.
- 5. The method of claim 4, wherein the obtaining status information related to the processing of the RRC RELEASE message comprises: And acquiring acknowledgement state information of a radio link control layer, wherein the acknowledgement state information is used for indicating whether an RLC service data unit carrying the RRC RELEASE message needs to wait for state acknowledgement of a peer RLC entity or not, and the state information comprises the acknowledgement state information.
- 6. The method of claim 5, wherein processing the RRC RELEASE message based on the estimated maximum wait time comprises: if the confirmation status information indicates that the peer RLC entity does not need to wait for status confirmation, processing the RRC RELEASE message based on a first estimated maximum wait time; If the confirmation status information indicates that the status confirmation of the peer RLC entity needs to be waited, the RRC RELEASE message is processed based on a second estimated maximum waiting time, where the second estimated maximum waiting time is a maximum waiting time specified by the communication protocol and the terminal needs to wait for the feedback of the bottom layer confirmation after receiving the RRC RELEASE message, and the second estimated maximum waiting time is greater than the first estimated maximum waiting time.
- 7. The method of claim 4, wherein the obtaining status information related to the processing of the RRC RELEASE message comprises: And acquiring HARQ feedback state information of a physical layer, wherein the HARQ feedback state information is used for indicating the HARQ acknowledgement state of the PDSCH carrying the RRC RELEASE message, and the state information comprises the HARQ feedback state information.
- 8. The method of claim 7, wherein the processing the RRC RELEASE message based on the estimated maximum wait time comprises: if the HARQ feedback status information indicates an HARQ acknowledgement indication, processing the RRC RELEASE message based on a third estimated maximum waiting duration, where the third estimated maximum waiting duration is less than a maximum waiting duration specified by a communication protocol and for which the terminal needs to wait for bottom layer acknowledgement feedback after receiving the RRC RELEASE message.
- 9. The method of claim 6 or 8, wherein a first estimated maximum wait time period is equal to a third estimated maximum wait time period, the first estimated maximum wait time period and the third estimated maximum wait time period being determined according to a processing time period and a slot length of the PDSCH.
- 10. A connection release message processing method, applied to a terminal, the method comprising: receiving RRC RELEASE a message from a network device; Determining whether acknowledgement feedback from an underlying layer needs to be waited before processing the RRC RELEASE message according to a trigger scenario associated with the RRC RELEASE message; If not, processing the RRC RELEASE message; if yes, acquiring state information related to the processing of the RRC RELEASE message; If the state information indicates that the state confirmation of the peer RLC entity does not need to be waited, processing the RRC RELEASE message based on a first estimated maximum wait time, where the first estimated maximum wait time is determined based on an HARQ feedback timing parameter and a slot length; If the state information indicates that the state confirmation of the peer RLC entity needs to be waited, processing the RRC RELEASE message based on a second estimated maximum waiting time length, where the second estimated maximum waiting time length corresponds to a maximum waiting time length, which is specified by a communication protocol, of a terminal to wait for feedback of a bottom layer confirmation after receiving the RRC RELEASE message; wherein the processing of the RRC RELEASE message includes immediately executing when a corresponding acknowledgement feedback is received before a corresponding estimated maximum wait time expires, or executing when the estimated maximum wait time expires.
- 11. An electronic device comprising a processor and a memory storing computer readable instructions that, when executed by the processor, perform the method of any of claims 1-10.
- 12. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, performs the method according to any of claims 1-10.
- 13. A computer program product comprising computer program instructions which, when read and executed by a processor, perform the method of any of claims 1-10.
Description
Connection release message processing method, electronic device, storage medium, and program product Technical Field The present application relates to the field of communications technologies, and in particular, to a connection release message processing method, an electronic device, a storage medium, and a program product. Background In a 5G NR (New Radio) network scenario, an RRC (Radio Resource Control ) connection release procedure is one of core procedures for guaranteeing efficient Radio resource utilization and reasonable handover of a terminal state, and the core purpose of the RRC (Radio Resource Control) connection release procedure is to release an established SRB2 (SIGNALING RADIO BEARER, signaling Radio bearer 2) and a DRB (Data Radio Bearer ) when a terminal completes service transmission, network optimization adjustment or triggers a specific operation by the terminal, clear Radio resource configuration, or implement terminal redirection, and finally switch the terminal RRC state from rrc_connected to rrc_inactive or rrc_idle. According to the 3GP protocol, the process is actively triggered by the network device (e.g., the gNB) only on the premise that the terminal has successfully established SRB2 and at least one DRB, which is a key link for maintaining the network and the terminal to cooperatively work. In the prior art, to ensure the reliability of the underlying data transmission, the protocol explicitly requires that the terminal cannot immediately execute the connection release process after receiving RRC RELEASE messages from the air interface, and must wait for the underlying feedback acknowledgement information, and the upper limit of the waiting time period is fixed to be 60ms. The original purpose of this design is to cover all possible underlying feedback scenarios. However, this unified waiting mechanism increases the traffic delay for the terminal to process RRC RELEASE messages. Disclosure of Invention An objective of the embodiments of the present application is to provide a connection release message processing method, an electronic device, a storage medium, and a program product, so as to solve the problem that in the existing manner, a service delay is increased due to the fact that a message is processed RRC RELEASE only after waiting for a fixed duration. In a first aspect, an embodiment of the present application provides a method for processing a connection release message, which is applied to a terminal, where the method includes: receiving RRC RELEASE a message from a network device; Determining whether acknowledgement feedback from an underlying layer needs to be waited before processing the RRC RELEASE message according to a trigger scenario associated with the RRC RELEASE message; and selecting a corresponding connection release processing strategy to process the RRC RELEASE messages according to the determined result. In the implementation process, the trigger scene of RRC RELEASE messages is subjected to scene judgment, whether the bottom layer confirmation feedback needs to be waited or not is dynamically determined, and the differential processing strategy is matched, so that the terminal processing efficiency is optimized, and the service processing time delay can be reduced on the premise of ensuring the connection release reliability. Optionally, the determining whether to wait for acknowledgement feedback from the bottom layer before processing the RRC RELEASE message according to a trigger scenario associated with the RRC RELEASE message includes: If the trigger scenario associated with the RRC RELEASE message is a terminally released scenario, determining that it is not necessary to wait for acknowledgement feedback from the bottom layer before processing the RRC RELEASE message; if the trigger scenario associated with the RRC RELEASE message is a non-terminating release scenario, then the determination is that acknowledgement feedback from the underlying layer needs to be waited for before processing the RRC RELEASE message. In the implementation process, through accurately distinguishing the ending and non-ending release scenes of RRC RELEASE messages and formulating a differentiated confirmation feedback strategy, a bottom confirmation waiting link is omitted aiming at ending release scenes such as terminal shutdown and the like, the time delay of key operations such as shutdown and the like is greatly shortened, the user experience is improved, a bottom confirmation feedback waiting mechanism is reserved aiming at non-ending release scenes such as network redirection and data transmission completion and the like, the state consistency of a network and a terminal is ensured, and communication abnormity caused by advanced release connection is avoided. Optionally, the termination release scenario includes a non-access stratum detach procedure scenario triggered by the terminal shutdown, and the trigger scenario is identified by: And if the indication