Communication method and device, terminal, chip and storage medium

Abstract

The invention provides a communication method and device, a terminal, a chip and a storage medium, and relates to the field of communication, and the method comprises the steps: responding to each special message segment, received by the terminal, of a downlink special signaling sent by network equipment, and configuring the special configuration of the terminal according to each special message segment; and in response to each special message segment indicating that a message receiving state needs to be sent to the network device, sending a target state report to the network device based on the special configuration, the target state report being used for indicating the receiving state of each special message segment. Therefore, after the terminal receives all special message segments of the downlink special signaling and completes special configuration according to the special message segments, the RLC state report is reported to the network equipment, so that unnecessary RACH triggering can be effectively avoided, wireless resources are utilized more reasonably, resource waste is reduced, the success rate of initiating the RACH by the terminal is improved, and the user experience is improved. And the communication continuity is ensured.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus, terminal, chip, and storage medium. Background Technology

[0002] When the message content of downlink dedicated signaling is large, network devices can use the downlink dedicated message segmentation (DLDedicatedMessageSegment) transmission method to send downlink dedicated signaling to the terminal. Summary of the Invention

[0003] This application proposes a communication method, apparatus, terminal, chip, and storage medium to at least partially solve one of the technical problems in the related art.

[0004] One embodiment of this application proposes a communication method, including: in response to a terminal receiving downlink dedicated signaling segments sent by a network device, configuring a dedicated configuration of the terminal according to each dedicated message segment; in response to each dedicated message segment indicating that a message reception status needs to be sent to the network device, sending a target status report to the network device based on the dedicated configuration, wherein the target status report is used to indicate the reception status of each dedicated message segment.

[0005] Another embodiment of this application proposes a communication apparatus, including: a configuration module, configured to configure a dedicated configuration of the terminal according to each dedicated message segment in response to the terminal receiving downlink dedicated signaling sent by a network device; and a sending module, configured to send a target status report to the network device based on the dedicated configuration in response to each dedicated message segment indicating that a message reception status needs to be sent to the network device, wherein the target status report is used to indicate the reception status of each dedicated message segment.

[0006] In another aspect of this application, a terminal is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the communication method as described in the foregoing aspect.

[0007] Another aspect of this application provides a chip including an interface circuit and a processing circuit coupled to each other, the interface circuit being used to input or output signals, and the processing circuit being configured to perform the communication method as described in the preceding aspect.

[0008] In another aspect of this application, a non-transitory computer-readable storage medium is provided, on which computer program instructions are stored, which, when executed by a processor, implement the communication method as described in the foregoing aspect.

[0009] Another aspect of this application provides a computer program product having a computer program stored thereon, which, when executed by a processor, implements the communication method as described in the foregoing aspect.

[0010] The communication method, apparatus, terminal, chip, and storage medium proposed in this application delay the transmission of RLC status reports during the transmission of dedicated message segments. That is, the RLC status report is reported to the network device only after the terminal has received all dedicated message segments of downlink dedicated signaling and completed dedicated configuration accordingly. This not only effectively avoids unnecessary RACH triggering, enabling more rational use of radio resources and reducing resource waste, but also helps to improve the success rate of the terminal initiating RACH and ensures the continuity of communication.

[0011] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0012] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a schematic diagram illustrating the process of a terminal restoring its connection state from an inactive state in related technologies. Figure 2 A flowchart illustrating a communication method provided for an exemplary embodiment of this application; Figure 3 A flowchart illustrating another communication method provided for an exemplary embodiment of this application; Figure 4 A flowchart illustrating yet another communication method provided for an exemplary embodiment of this application; Figure 5 A flowchart illustrating another communication method provided for an exemplary embodiment of this application; Figure 6 A schematic diagram illustrating an application scenario provided for an exemplary embodiment of this application; Figures 7(a) and 7(b) are schematic diagrams of the terminal resume process provided by an exemplary embodiment of this application; Figure 8 A schematic diagram of the structure of a communication device provided for an exemplary embodiment of this application; Figure 9 A schematic diagram of the structure of a terminal provided for an exemplary embodiment of this application; Figure 10 This is a schematic diagram of the structure of a chip proposed in an exemplary embodiment of this application. Detailed Implementation

[0013] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0014] Taking the downlink dedicated signaling as Radio Resource Control Reconfiguration (RRCReconfiguration) signaling as an example, when a network device needs to reconfigure the radio resources of a terminal, it generates RRCReconfiguration signaling. Since RRCReconfiguration signaling may contain a large amount of configuration information, such as new measurement configurations, radio bearer configurations, and mobility management configurations, the signaling message is quite large. Under suboptimal radio channel conditions, transmitting such a large signaling message at once may face a high probability of errors, or even lead to transmission failure. To address this issue, network devices can use the DLDedicatedMessageSegment segmentation transmission method to divide the RRCReconfiguration signaling into multiple smaller segments. Each segment can be encoded and transmitted independently, and the transmission strategy can be flexibly adjusted according to channel conditions. After receiving these segments, the terminal can recombine them into a complete RRCReconfiguration signaling according to a certain order and rules, and perform the corresponding configuration update. This can effectively improve the transmission success rate of RRCReconfiguration signaling, reduce the number of retransmissions due to signaling transmission failures, thereby reducing the signaling overhead between the terminal and network equipment and improving the performance and efficiency of the entire wireless communication system.

[0015] Taking the downlink dedicated signaling as Radio Resource Control Recovery (RRCResume) signaling as an example, when a terminal initiates an RRCResume request to the network device in an inactive state to restore the context between the terminal and the network device, if the network device detects the context identified by the terminal, it uses the DLDedicatedMessageSegment fragmentation transmission method to send RRCResume signaling to the terminal, enabling the terminal to quickly return to the dedicated state and reducing unnecessary signaling processes between the terminal and the network device.

[0016] As an example, taking the downlink dedicated signaling as RRCresume signaling, the process of a terminal restoring the connection state from the inactive state can be as follows: Figure 1 As shown, it mainly includes the following steps: in, Figure 1In this context, NAS stands for Non-Access Stratum; RRC refers to Radio Resource Control; L2 refers to Layer 2, which includes sublayers such as Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP); L1 refers to Layer 1, i.e., the physical layer; RACH refers to Random Access Channel, used by terminals to initiate random access procedures; CRNTI refers to Cell-Radio Network Temporary Identifier, used to identify terminals within a cell; DCCH refers to Dedicated Control Channel, used to transmit terminal-specific control information; DCI refers to Downlink Control Information, used to transmit downlink control commands; STATUS PDU refers to Status Protocol Data Unit; and RLC... STATUSPDU is a control message generated by the RLC layer, used to provide network devices with feedback on the status of data reception, such as which data blocks have been successfully received and which data blocks have been lost and need to be retransmitted. By sending RLC STATUS PDU to the network device, the network device can notify the terminal to perform necessary data retransmissions to ensure the integrity and correctness of the data.

[0017] 1. MM_RRC_EST_REQ (resume_req): The NAS layer triggers an RRC establishment request, requiring the terminal to recover from the inactive state to the connected state. That is, when the terminal needs to restore its connection with the network device, the NAS layer sends a recovery request (resume_req) to the RRC layer.

[0018] 2. RRC_L1_COMMON_CONFIG_REQ: The RRC layer requests configuration of common radio parameters from the L1 layer. These parameters usually come from System Information Block 1 (SIB1) and the default configuration.

[0019] 3. RRC_L2_COMMON_CONFIG_REQ: The RRC layer requests configuration of common radio parameters from the L2 layer.

[0020] 4. L1_RRC_COMMON_CONFIG_CNF: After L1 layer completes the configuration of common radio parameters, it sends an acknowledgment message to RRC layer to confirm that the configuration of common radio parameters is complete.

[0021] 5. L2_RRC_COMMON_CONFIG_CNF: After the L2 layer completes the configuration of the common radio parameters, it sends an acknowledgment message to the RRC layer to confirm that the configuration of the common radio parameters is complete.

[0022] 6. RRC_L2_DATA_REQ (RRCResume REQ): The RRC layer prepares to send an RRCesume request to transmit data to the L2 layer.

[0023] 7. MAC_L1_RACH_REQ: The MAC layer requests the L1 layer to initiate a random access procedure.

[0024] 8. Rach Preamble: The terminal sends a rach preamble, which is used by network devices to detect the terminal's random access request.

[0025] 9. L1_L2_RACH_RSP (recv RAR): After receiving the random access response from the network device, the L1 layer sends a random access response (RAR) to the L2 layer.

[0026] 10. Message MSG3 (RRCResume req): The terminal sends MSG3 during the random access process, which contains an RRRCResume request.

[0027] 11. Contention Resolution MAC Control Element (CR MAC CE): The network device sends a contention resolution message to resolve conflicts caused by multiple terminals accessing the network simultaneously.

[0028] 12. L2_RRC_RACH_STATUS_IND (rach_succ): The L2 layer indicates to the RRC layer that random access was successful.

[0029] 13. L1_L2_DATA_IND(Poll=1): The L1 layer indicates to the L2 layer that data has arrived and sets the Poll bit to 1 to trigger an RLC status report; where Poll is used to indicate whether a message reception status needs to be sent to the network device.

[0030] 14. L2_RRC_DATA_IND(DLDedicatedMessageSegment1): The L2 layer indicates to the RRC layer that dedicated message segment 1 has been received.

[0031] 15. RLC_STATUS_PDU_REQ: RLC Status Report Request. Because the Poll bit is set to 1, the RLC layer triggers a status report request, demanding the sending of an RLC status report.

[0032] 16. MAC_L1_RACH_REQ: The MAC layer requests a random access procedure from the L1 layer again. That is, due to the lack of uplink grant resources, the MAC layer decides to initiate a random access procedure again to send an RLC status report.

[0033] 17. Rach Preamble: Send the random access preamble again to attempt to acquire uplink authorized resources.

[0034] 18. L1_L2_RACH_RSP (recv RAR): After receiving the random access response from the network device, the L1 layer sends it to the L2 layer.

[0035] 19. MSG3 (STATUS PDU, CRNTI): MSG3 carries the RLC status report and CRNTI.

[0036] The MSG3 sent by the terminal during random access includes an RLC status report and CRNTI. However, because the segments of the RRCresume signaling have not been fully received, the L1 layer cannot configure dedicated parameters to decode DCI Format 0-1 (referred to as DCI0-1), which ultimately leads to a timeout in random access contention resolution, RACH failure, connection release, and failure of the resume process.

[0037] That is, steps 1-6 are the process of NAS triggering a connection request when the terminal needs to restore the connection state in the inactive state, and the RRC configuring the L1 / L2 layer to use the common (SIB1+Default) radio parameters; steps 7-12 are the 4-step random access process, which completes the access contention resolution, at which point temp C-RNTI is converted to C-RNTI; Steps 13-14 are when the network device receives the terminal's RRC Resume request, queries the context associated with the terminal identifier (UEidentity), and uses C-RNTI-scrambled RRC Resume signaling. Here, because the RRC Resume signaling is large, the network device adopts a segmented transmission method. The terminal's L1 layer successfully decrypts DLDedicatedMessageSegment1 (the first segment of the RRC Resume signaling) on ​​the downlink DCCH using COMMON radio parameters + CRNTI, and reports segment1 to the RRC layer; Steps 15-19: Because the RLC data carries Poll=1 during the transmission of the DLDedicatedMessageSegment of the RRC Resume signaling, the RLC layer triggers the RLC status report according to the protocol. Since there is no uplink grant (ULgrant) resource at this time, and the scheduling request (SR) resource does not exist, the uplink transmission of the RLC status report can only be initiated through random access. In step 19, MSG3 (RLC STATUS) carrying CRNTI is sent. After PDU, according to the protocol, it is necessary to decode the uplink grant resources in Physical Downlink Control Channel (PDCCH) DCI0-1. At this time, L1 layer needs to use dedicated configuration to decode DCI0-1. However, at this time, the segmented RRC of RRC Resume signaling has not been fully collected, and L1 layer's dedicated configuration cannot be configured. This eventually leads to the random access contention resolution timeout. After trying the maximum number of times, RACH fails, reports to the RRC layer, and ultimately leads to the release of the link and the resume process failure.

[0038] Therefore, in view of at least one of the problems existing in the above-mentioned related technologies, this application proposes a communication method, device, terminal, chip and storage medium.

[0039] The communication method, apparatus, terminal, chip, and storage medium of this application are described below with reference to the accompanying drawings.

[0040] Figure 2 This is a flowchart illustrating a communication method provided for an exemplary embodiment of this application.

[0041] It should be noted that the communication method of this application embodiment can be applied to a communication device. In some possible embodiments, the communication device can be configured in a terminal or chip so that the terminal or chip can perform communication functions. Additionally, in some possible embodiments, the communication device can also be software within the terminal.

[0042] In any embodiment of this application, the chip can be integrated into a terminal. The chip includes a Central Processing Unit (CPU), an Image Signal Processing (ISP), an Application-Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Field-Programmable Gate Array (FPGA), a System-on-Chip (SOC), a Reduced Instruction Set Computer (RISC), etc., which will not be listed here.

[0043] In this context, a terminal is a user-side entity used to receive or transmit signals, such as a mobile phone. A terminal can also be called a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. Terminals can be communication-enabled vehicles, smart cars, mobile phones, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on. The embodiments in this application do not limit the specific technology or device form used in the terminal.

[0044] For ease of explanation, the following description will use the terminal as the executing entity of this communication method as an example.

[0045] like Figure 2 As shown, the communication method may include the following steps S201 to S202: Step S201: In response to the terminal receiving each dedicated message segment of downlink dedicated signaling sent by the network device, configure the terminal's dedicated configuration according to each dedicated message segment.

[0046] In this context, network equipment refers to an entity on the network side used for transmitting or receiving signals. Network equipment includes access network equipment and core network equipment. Access network equipment can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G new radio (NR) system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment. The access network equipment provided in the embodiments of this application can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0047] Downlink dedicated signaling refers to signaling messages sent by network devices to terminals to control terminal behavior and configure radio resources, including but not limited to: RRCReconfiguration signaling, RRCResume signaling, and other downlink signaling messages with relatively large message content.

[0048] In this embodiment, when the message content of the downlink dedicated signaling is relatively large, the network device can use the downlink dedicated message segmentation (DLDedicatedMessageSegment) transmission method to divide the downlink dedicated signaling into multiple smaller dedicated message segments and send these dedicated message segments to the terminal. After the terminal receives all the dedicated message segments of the downlink dedicated signaling sent by the network device, it can configure the terminal's dedicated configuration based on all the received dedicated message segments.

[0049] As an example, taking the downstream dedicated signaling as RRCReconfiguration signaling, when the terminal receives all dedicated message segments of the RRCReconfiguration signaling sent by the network device, it can combine all dedicated message segments of the RRCReconfiguration signaling to obtain the complete RRCReconfiguration signaling, and perform configuration updates based on the RRCReconfiguration signaling to obtain the terminal's new dedicated configuration.

[0050] As another example, taking the downlink dedicated signaling as RRCResume signaling, when the terminal receives all dedicated message segments of the RRCResume signaling sent by the network device, it can combine all dedicated message segments of the RRCResume signaling to obtain the complete RRCResume signaling, and configure the terminal's Layer 1 and Layer 2 dedicated configurations according to the RRCResume signaling, so that the terminal can recover from the inactive state to the connected state.

[0051] Step S202: In response to each dedicated message segment indicating that it needs to send a message reception status to the network device, a target status report is sent to the network device based on the dedicated configuration, wherein the target status report is used to indicate the reception status of each dedicated message segment.

[0052] For example, each dedicated message segment may carry a target flag, which indicates whether the terminal needs to send a message reception status to the network device. For example, taking downlink dedicated signaling including RRCresume signaling as an example, the target flag may be the Poll flag.

[0053] In this embodiment of the application, when each dedicated message segment of the downlink dedicated signaling indicates that a message reception status needs to be sent to the network device, the terminal can send a target status report to the network device based on the dedicated configuration. The target status report is used to indicate the reception status of each dedicated message segment.

[0054] As an example, taking the number of dedicated message segments as M, the target status report can include the RLC status reports (RLC STATUS PDUs) corresponding to the M dedicated message segments. The terminal can send the RLC status reports corresponding to the M dedicated message segments to the network device based on the dedicated configuration.

[0055] Among them, the M RLC status reports are status reports triggered by the terminal's RLC layer for the M dedicated message segments. Each RLC status report is used to indicate the reception status of the corresponding dedicated message segment.

[0056] As another example, taking M dedicated message segments as an example, the target status report can also include only one RLC status report. This single RLC status report can be obtained by merging the RLC status reports (RLC STATUS PDUs) corresponding to the M dedicated message segments. That is, in this application, the RLC status reports triggered by the terminal's RLC layer for each dedicated message segment can be merged to obtain the target status report. The terminal can then send an RLC status report (i.e., the final merged target status report) to the network device based on its dedicated configuration.

[0057] It should be understood that merging M RLC status reports into a single target status report for network devices can effectively reduce the number of unnecessary status reports and decrease the number of RACH triggers.

[0058] It should be noted that in related technologies, when a terminal receives any dedicated message segment of downlink dedicated signaling, if that dedicated message segment indicates the need to send a message reception status to the network device, the terminal will trigger an RLCSTATUS PDU. If the terminal has not yet completed the dedicated configuration of Layer 1 and Layer 2 at this time, it will blindly trigger the Random Access Channel (RACH) procedure. Due to the lack of dedicated configuration, RACH will most likely fail (unable to detect the DCI signaling in DCI0-1 format sent by the network device), which not only wastes valuable radio resources but also increases the signaling overhead of the network device and the terminal.

[0059] In this application, during the transmission of dedicated message segments, the RLC status report is sent with a delay. The RLC status report is only reported after the terminal has completed the dedicated configuration of Layer 1 and Layer 2. This can effectively avoid RACH triggering caused by triggering the RLC STATUS PDU when the terminal is not ready, so that radio resources can be used more rationally, unnecessary resource waste is reduced, and the resource utilization efficiency of the entire network is improved.

[0060] The communication method of this application embodiment delays the transmission of RLC status reports during the transmission of dedicated message segments. That is, the RLC status report is reported to the network device only after the terminal receives all dedicated message segments of downlink dedicated signaling and completes dedicated configuration accordingly. This not only effectively avoids unnecessary RACH triggering, enabling more rational use of radio resources and reducing resource waste, but also helps to improve the success rate of the terminal initiating RACH and ensures the continuity of communication.

[0061] As one possible implementation method, Figure 3 This is a flowchart illustrating another communication method provided for an exemplary embodiment of this application. It should be noted that this communication method can be executed alone, or it can be executed together with any embodiment or possible implementation thereof in this application, or it can be executed together with any technical solution in related technologies. This application does not impose any limitations on this.

[0062] like Figure 3 As shown, the communication method may include the following steps S301 to S306: Step S301: In response to the terminal receiving each dedicated message segment of downlink dedicated signaling sent by the network device, configure the terminal's dedicated configuration according to each dedicated message segment.

[0063] Step S302: Merge the RLC status reports triggered by the terminal's RLC layer for each dedicated message segment to obtain a target status report; wherein, the RLC status report is used to indicate the reception status of the corresponding dedicated message segment.

[0064] It should be noted that the explanations of steps S301 to S302 can be found in the relevant descriptions in any embodiment of this application, and will not be repeated here.

[0065] Step S303: Determine whether SR resources are configured in the downlink dedicated signaling. If yes, proceed to steps S305 to S306. If no, proceed to step S304.

[0066] In this embodiment, when the terminal receives all dedicated message segments of downlink dedicated signaling sent by the network device, all received dedicated message segments can be combined or assembled to obtain complete downlink dedicated signaling. It is then determined whether the downlink dedicated signaling contains SR resources. If so, steps S305 to S306 are executed; otherwise, step S304 is executed. It should be noted that step S304 and steps S305 to S306 are two parallel possible implementations, and either can be executed.

[0067] Step S304: Based on the dedicated configuration and the first random access procedure, obtain the first uplink authorization resource allocated by the network device to the terminal, and send the target status report through the first uplink authorization resource.

[0068] In this embodiment of the application, when no SR resources are configured in the downlink dedicated signaling, the terminal can obtain the first uplink authorized resources allocated to the terminal by the network device based on the dedicated configuration and the first random access procedure, and send a target status report through the first uplink authorized resources. The target status report is used to indicate the reception status of each dedicated message segment.

[0069] In any embodiment of this application, the acquisition of the first uplink grant resource is, for example, as follows: initiating a first random access request and sending a first random access preamble to the network device; wherein, the first random access preamble is used by the network device to detect the first random access request; in response to receiving the first random access response sent by the network device, sending a first MSG3 carrying a scrambled target state report and CRNTI to the network device, wherein, the scrambled target state report is obtained by scrambling the target state report using CRNTI; based on a dedicated configuration, detecting the DCI signaling sent by the network device in response to the first MSG3; wherein, the DCI signaling is used to indicate the first uplink grant resource. The DCI format of the DCI signaling can be DCI Format 0-1 (abbreviated as DCI0-1), used for uplink scheduling, that is, the DCI signaling indicates the uplink grant resource used for uplink transmission.

[0070] Accordingly, the target status report is sent in the following manner: in response to the terminal detecting DCI signaling, determining that the random access contention has been successfully resolved, and sending a target status report to the network device based on the first uplink authorized resource indicated by the DCI signaling.

[0071] As an example, if no SR resource is configured in the downlink dedicated signaling, the terminal cannot request uplink grant resources through SR, and therefore can only obtain uplink grant resources through random access. Specifically, the terminal's MAC layer sends a random access request to Layer 1 (i.e., L1 layer), initiating a four-step random access process; the terminal sends a random access preamble for the network device to detect the terminal's random access request; L1 layer receives the network device's random access response (RAR) and sends it to Layer 2 (L2 layer); the terminal sends a target state report carrying CRNTI in the random access message 3 (MSG3). At this point, because the target state report is scrambled using C-RNTI according to the protocol, this contention resolution process requires the use of a dedicated DEDICATED configuration to detect the network device's DCI0-1. Only after obtaining the uplink grant resources allocated by the network device is the contention considered resolved successfully; L1 layer indicates to L2 layer that it has received the uplink grant resources allocated by the network device, the RACH contention is resolved successfully, and the target state report is sent on the uplink grant resources.

[0072] In summary, by delaying the transmission of RLC status reports, the terminal is ensured to perform related operations only after completing the dedicated configurations for Layer 1 and Layer 2. In this way, the terminal already has the dedicated configuration to detect DCI0-1 when initiating RACH, which greatly improves the success rate of RACH, thereby ensuring that the terminal can successfully access the network, maintain the continuity of communication, and improve the user's communication experience.

[0073] Step S305: Send a scheduling request SR to the network device based on the SR resource; wherein, the SR is used to request the second uplink authorization resource from the network device.

[0074] In this embodiment of the application, when SR resources are configured in the downlink dedicated signaling, the terminal can directly send a scheduling request (SR) to the network device based on the SR resources to request the network device to allocate a second uplink authorized resource.

[0075] Step S306: In response to the network device having allocated a second uplink grant resource to the terminal, a target status report is sent to the network device through the second uplink grant resource.

[0076] In this embodiment of the application, when the network device has allocated a second uplink grant resource to the terminal, the terminal can send a target status report to the network device through the second uplink grant resource.

[0077] The communication method in this application embodiment flexibly selects different methods to send target status reports to network devices depending on whether SR resources are configured in the downlink dedicated signaling. Specifically, when SR resources are configured in the downlink dedicated signaling, requesting uplink authorized resources using SR resources is more efficient, enabling rapid acquisition of uplink authorized resources and timely feedback of RLC status reports. Conversely, when SR resources are not configured in the downlink dedicated signaling, requesting uplink authorized resources through a random access procedure is used as a backup solution. This ensures that even in the absence of SR resources, the terminal can still promptly report message reception status to the network device, providing a solid guarantee for communication reliability.

[0078] As one possible implementation method, Figure 4 This is a flowchart illustrating another communication method provided for an exemplary embodiment of this application. It should be noted that this communication method can be executed alone, or it can be executed together with any embodiment or possible implementation thereof in this application, or it can be executed together with any technical solution in related technologies. This application does not impose any limitations on this.

[0079] like Figure 4 As shown, the communication method may include the following steps S401 to S404: Step S401: In response to the terminal receiving each dedicated message segment of downlink dedicated signaling sent by the network device, configure the terminal's dedicated configuration according to each dedicated message segment.

[0080] It should be noted that the explanation of step S401 can be found in the relevant description in any embodiment of this application, and will not be repeated here.

[0081] In any embodiment of this application, before the terminal delays sending the target status report, the RLC status report triggered by the RLC layer for each dedicated message segment can be written into the delay queue.

[0082] As an example, when a terminal receives any dedicated message segment of downlink dedicated signaling based on common radio parameters, a target flag can be extracted from that dedicated message segment. This target flag indicates whether the terminal needs to send a message reception status report to the network device. If the target flag indicates that the terminal needs to send a message reception status report to the network device, the RLC status report corresponding to that dedicated message segment can be triggered through the terminal's RLC layer, and written to the delay queue. The RLC status report indicates the reception status of that dedicated message segment.

[0083] It is understandable that the terminal delays sending the target status report in order to avoid unnecessary RACH triggering and other issues. The delay queue can temporarily store the RLC status report and send it uniformly at the appropriate time, which is coordinated with the terminal's overall delay sending strategy and ensures the smoothness of the communication process.

[0084] Step S402: Retrieve the RLC status report corresponding to each dedicated message segment from the delay queue.

[0085] In this embodiment of the application, the terminal can retrieve the RLC status report triggered by the RLC layer for each dedicated message segment of downlink dedicated signaling from the delay queue; wherein, the RLC status report is used to indicate the reception status of the corresponding dedicated message segment.

[0086] Step S403: Merge the RLC status reports corresponding to each dedicated message segment to obtain the target status report.

[0087] For example, the RLC status reports corresponding to each dedicated message segment can be merged, and only the RLC status report corresponding to the last received dedicated message segment can be retained, while other RLC status reports are cleared locally.

[0088] Step S404: Send a target status report to the network device based on the dedicated configuration.

[0089] It should be noted that the explanations of steps S403 to S404 can be found in the relevant descriptions in any embodiment of this application, and will not be repeated here.

[0090] As an example, taking the downlink dedicated signaling including RRCresume signaling as an example, after the terminal receives each dedicated message segment of the RRCresume signaling sent by the network device, and configures the terminal's Layer 1 and Layer 2 dedicated configurations according to each dedicated message segment, it can recover from the inactive state to the connected state, and in the connected state, send a target status report to the network device based on the dedicated configuration; wherein, the target status report is used to indicate the reception status of each dedicated message segment.

[0091] The communication method in this application embodiment can effectively avoid unnecessary RACH triggering by delaying the transmission of RLC status reports corresponding to each dedicated message segment, thereby enabling more rational use of radio resources and reducing resource waste. Furthermore, merging multiple RLC status reports into a single target status report for reporting to the network device can effectively reduce the number of unnecessary status reports and the number of RACH triggers.

[0092] As one possible implementation method, Figure 5This is a flowchart illustrating another communication method provided as an exemplary embodiment of the present application. It should be noted that this communication method can be executed alone, or it can be executed together with any embodiment of the present application or any possible implementation thereof, or it can be executed together with any technical solution in related technologies. The embodiments of the present application do not impose any limitations on this.

[0093] like Figure 5 As shown, the communication method may include the following steps S501 to S503: Step S501: In response to the terminal being in an inactive state and the common radio parameters being configured at Layer 1 and Layer 2, an RRCResume request is sent to the network device based on the common radio parameters and the second random access procedure; wherein, the RRCResume request is used to request to recover from the inactive state to the connected state.

[0094] In this embodiment of the application, when the terminal is in an inactive state and the common radio parameters of the terminal are configured in Layer 1 and Layer 2, if the terminal needs to initiate a service, it can send an RRRCResume request to the network device based on the common radio parameters and the second random access procedure; wherein, the RRRCResume request is used to request to recover from the inactive state to the connected state.

[0095] In any embodiment of this application, the method of sending the RRCResume request is as follows: In response to Layer 2 of the terminal receiving the RRCResume request sent by the RRC layer, a second random access request is initiated to Layer 1; Layer 1 sends a second random access preamble to the network device based on the common radio parameters and the second random access request, wherein the second random access preamble is used by the network device to detect the second random access request; In response to Layer 2 receiving the second random access response sent by the network device, a second MSG3 carrying relevant information of the RRCResume request is sent to the network device; In response to Layer 2 receiving the random access contention resolution message sent by the network device based on the common radio parameters, the random access is indicated to the RRC layer as successful; wherein the random access contention resolution message carries a third uplink grant resource allocated for the RRCResume request; Based on the third uplink grant resource, the RRCResume request is sent to the network device.

[0096] For example, the terminal may employ Figure 1 Steps 1-12 in the process are used to send an RRRCResume request to the network device.

[0097] Step S502: In response to the terminal receiving each dedicated message segment of the RRRCResume signaling sent by the network device, configure the terminal's Layer 1 and Layer 2 dedicated configurations according to each dedicated message segment, so that the terminal recovers from the inactive state to the connected state.

[0098] In step S503, in response to each dedicated message segment indicating that it needs to send a message reception status to the network device, in the connected state, a target status report is sent to the network device based on the dedicated configuration; wherein, the target status report is used to indicate the reception status of each dedicated message segment.

[0099] It should be noted that the explanations of steps S502 to S503 can be found in the relevant descriptions in any embodiment of this application, and will not be repeated here.

[0100] In any embodiment of this application, when the terminal is in a connected state and the service process has been completed, the terminal can receive an RRC Release signaling sent by the network device and switch from the connected state to the inactive state; wherein, the RRC Release signaling is used to instruct the terminal to enter the inactive state.

[0101] Therefore, after a terminal completes its service and enters the inactive state, the network device no longer needs to continuously allocate dedicated resources, such as control channel resources and data channel resources. These resources can be released and redistributed to other terminals with service needs, thereby improving the overall utilization of network resources and allowing limited resources to serve more users. Furthermore, in the connected state, the terminal and network device need to frequently exchange signaling to maintain the connection. After entering the inactive state, this signaling interaction is significantly reduced, lowering the signaling overhead between the terminal and network device, alleviating the processing burden on the network device, and reducing the signaling processing pressure on the terminal, thus reducing terminal power consumption and extending terminal battery life.

[0102] As one application scenario, the communication method provided in this application can be applied to, for example... Figure 6 In the illustrated application scenario, when the terminal is in a connected state and the service has ended, the network device uses the RRCRelease signaling to put the terminal into an inactive state. If the terminal needs to initiate the service again later, it can send an RRCResume request to the network device. The network device uses a fragmented transmission method to transmit each dedicated message segment of the RRCResume signaling. Each dedicated message segment carries an RLC Header with Poll=1, meaning the terminal needs to trigger an RLC STATUS PDU to the network device. After receiving the dedicated message segment, the terminal can delay sending the corresponding RLC STATUS PDU.

[0103] The communication method of this application embodiment, after the terminal is in an inactive state and has completed the configuration of Layer 1 and Layer 2 common radio parameters, sends an RRRCResume request based on the common radio parameters and the second random access procedure to restore to the connected state. This can ensure that the terminal initiates state restoration in an orderly manner after having basic communication conditions, avoiding restoration failure due to incomplete configuration. At the same time, by utilizing common radio parameters and a specific random access procedure, access efficiency and success rate can be improved, unnecessary signaling interactions and resource waste can be reduced, and the terminal can be guaranteed to quickly and stably restore from the inactive state to the connected state, maintaining the continuity of communication.

[0104] In any embodiment of this application, the downstream dedicated signaling is used as an example of RRCResume signaling. In order to solve the problem in the related technology that during the transmission of RRCResume segment, Poll=1 triggers RLC STATUS PDU, which leads to RACH triggering. Ultimately, due to the lack of dedicated configuration, RACH fails and the terminal resume process fails, this application can delay the transmission (pending) of Poll on the network side when any dedicated message segment of RRCResume signaling is received. That is, for each poll, there will be an RLC PDU STATUS (ack=x, x=1,2,3,…n+1), where n+1 refers to the number of dedicated message segments contained in RRCResume signaling. When the terminal successfully receives all dedicated message segments of RRCResume signaling, the dedicated configuration of L1 & L2 layers is immediately configured. At this time, the pending RLC STATUS PDUs are merged into an RLC STAUTS PDU (ack=n+1) and reported to the network device. Because L1 & L2 layers are configured with dedicated settings, RLC STATUS PDUs can report to network devices via SR or random access. This avoids the failure of the aforementioned resume process, effectively reduces power consumption during RACH, shortens resume recovery time, reduces the number of unnecessary status reports, and decreases the number of RACH triggers.

[0105] As an example, taking the RRRCResume signaling as containing 3 dedicated message segments, the terminal resume process can be shown in Figures 7(a) and 7(b), mainly including the following steps: 1. MM_RRC_EST_REQ (resume_req): The NAS layer triggers an RRC establishment request, requiring the terminal to recover from the inactive state to the connected state. That is, when the terminal needs to restore its connection with the network device, the NAS layer sends a recovery request (resume_req) to the RRC layer.

[0106] 2. RRC_L1_COMMON_CONFIG_REQ: The RRC layer requests configuration of common radio parameters from the L1 layer. These parameters are usually derived from SIB1 and the default configuration.

[0107] 3. RRC_L2_COMMON_CONFIG_REQ: The RRC layer requests configuration of common radio parameters from the L2 layer.

[0108] 4. L1_RRC_COMMON_CONFIG_CNF: After L1 layer completes the configuration of common radio parameters, it sends an acknowledgment message to RRC layer to confirm that the configuration of common radio parameters is complete.

[0109] 5. L2_RRC_COMMON_CONFIG_CNF: After the L2 layer completes the configuration of the common radio parameters, it sends an acknowledgment message to the RRC layer to confirm that the configuration of the common radio parameters is complete.

[0110] 6. RRC_L2_DATA_REQ (RRCResume REQ): The RRC layer prepares to send an RRCesume request to transmit data to the L2 layer.

[0111] 7. MAC_L1_RACH_REQ: The MAC layer requests the L1 layer to initiate a random access procedure.

[0112] 8. Rach Preamble: The terminal sends a rach preamble, which is used by network devices to detect the terminal's random access request.

[0113] 9. L1_L2_RACH_RSP (recv RAR): After receiving the random access response from the network device, the L1 layer sends a random access response (RAR) to the L2 layer.

[0114] 10. Message MSG3 (RRCResume req): The terminal sends MSG3 during the random access process, which contains an RRRCResume request.

[0115] 11. Contention Resolution MAC Control Element (CR MAC CE): The network device sends a contention resolution message to resolve conflicts caused by multiple terminals accessing the network simultaneously.

[0116] 12. L2_RRC_RACH_STATUS_IND (rach_succ): The L2 layer indicates to the RRC layer that random access was successful.

[0117] 13. L1_L2_DATA_IND(Poll=1,SN=0): The L1 layer indicates to the L2 layer that the first dedicated message segment has arrived and sets the Poll bit to 1 to trigger an RLC status report; where Poll is used to indicate whether a message reception status needs to be sent to the network device.

[0118] 14. L2_RRC_DATA_IND(DLDedicatedMessageSegment1): The L2 layer indicates to the RRC layer that it has received dedicated message segment 1.

[0119] The RLC status report corresponding to dedicated message segment 1, i.e., RLC STATUS PDU (ack=1), is placed in the pending queue.

[0120] 15. L1_L2_DATA_IND(Poll=1,SN=1): The L1 layer indicates to the L2 layer that the second dedicated message segment has arrived and sets the Poll bit to 1 to trigger an RLC status report.

[0121] 16. L2_RRC_DATA_IND(DLDedicatedMessageSegment2): The L2 layer indicates to the RRC layer that dedicated message segment 2 has been received.

[0122] The RLC status report (ack=2) corresponding to dedicated message segment 2 is placed in the pending queue.

[0123] 17. L1_L2_DATA_IND(Poll=1,SN=2): The L1 layer indicates to the L2 layer that the third dedicated message segment has arrived and sets the Poll bit to 1 to trigger an RLC status report.

[0124] 18. L2_RRC_DATA_IND(DLDedicatedMessageSegment3, last segment): The L2 layer indicates to the RRC layer that the last dedicated message segment 3 has been received.

[0125] The RLC status report (ack=3) corresponding to dedicated message segment 3 is placed in the pending queue. DLDedicatedMessageSegment1, Segment2 and Segment3 are assembled and merged into RRCResume signaling to restore the dedicated configuration of the underlying L1 / L2.

[0126] 19. RRC_L1_DEDICATED_CONFIG_REQ: The RRC layer requests configuration-specific settings from the L1 layer.

[0127] 20. RRC_L2_DEDICATED_CONFIG_REQ: The RRC layer requests configuration-specific settings from the L2 layer.

[0128] 21. L1_RRC_DEDICATED_CONFIG_CNF: After completing the dedicated configuration, the L1 layer sends an acknowledgment message to the RRC layer to confirm that the dedicated configuration is complete.

[0129] 22. L2_RRC_DEDICATED_CONFIG_CNF: After completing the dedicated configuration, the L2 layer sends an acknowledgment message to the RRC layer to confirm that the dedicated configuration is complete.

[0130] Merge RLC status reports (ack=1), RLC status reports (ack=2), and RLC status reports (ack=3) in the pending queue, retain only RLC status report (ack=3), and clear the other RLC status reports locally.

[0131] 23. RLC_STATUS_PDU_REQ(ack=3): The RLC layer triggers an RLC STATUS PDU request. ack=3 indicates that this is a merged RLC STATUS PDU request.

[0132] If SR resources are configured in the RRRCResume signaling, then execute steps 24-26 (opt in Figure 7 indicates optional operations): 24. L2_L1_SR_REQ: The L2 layer sends an SR request to the L1 layer, that is, the terminal requests uplink authorized resources from the network device through the SR mechanism.

[0133] 25. L1_L2_SR_CNF: The L1 layer sends an SR confirmation message to the L2 layer, indicating that the SR request has been successfully sent or processed.

[0134] 26. L1_L2_UL_GRANT_IND: The L1 layer indicates to the L2 layer that it has received uplink grant resources from the network device. This indicates that the network device has responded to the terminal's SR request and allocated uplink grant resources.

[0135] SR successful, received uplink authorization resources from network device, and used the uplink authorization resources to send RLC STATUSPDU (ack=3) to report message reception status to network device.

[0136] If no SR resource is configured in the RRRCResume signaling, proceed to steps 27-31: 27. MAC_L1_RACH_REQ: The MAC layer sends a random access request to the L1 layer, initiating a 4-step random access procedure. Because the RRCResume signaling does not configure SR resources, the terminal cannot request uplink authorized resources through SR, and therefore can only obtain uplink authorized resources through random access.

[0137] 28. Rach Preamble: The terminal sends a random access preamble, which is used by network devices to detect the terminal's random access request.

[0138] 29. L1_L2_RACH_RSP(recv RAR): The L1 layer receives the random access response (RAR) from the network device and sends it to the L2 layer.

[0139] 30. MSG3 (STATUS PDU, CRNTI): The terminal sends an RLC STATUS PDU in the MSG3 of random access, carrying CRNTI.

[0140] At this point, since the RLC STATUS PDU uses C-RNTI scrambling according to the protocol, this contention resolution process requires a dedicated configuration to detect the network device's DCI0-1. Only when the network device's uplink grant resource is received is the contention resolution considered successful. This explains the conditions for contention resolution: the terminal needs to use a dedicated configuration to detect a specific DCI (DCI0-1) to confirm successful contention resolution.

[0141] 31. L1_L2_UL_GRANT_IND: The L1 layer indicates to the L2 layer that it has received uplink authorized resources from the network device.

[0142] The terminal receives the uplink grant resource allocated by the network device, the RACH contention is successfully resolved, and the RLC STATUS PDU is successfully sent on the uplink grant resource.

[0143] In MSG3, sending RLC STATUS PDU is for timely feedback, while sending related operations again based on uplink authorized resources is to ensure that RLC STATUS PDU can be reliably transmitted to network devices. The two perform different functions in the random access process, working together to ensure smooth communication.

[0144] In summary, steps 1-6 involve the NAS triggering a link establishment request when the terminal needs to restore the connection state in the inactive state, and the RRC configuring the L1 / L2 layers to use the common (SIB1+Default) radio parameters; steps 7-12 are the four-step random access process, completing the access contention resolution, at which point the temp C-RNTI is converted to C-RNTI; steps 13-14 involve the network device receiving the terminal's RRC Resume request, querying the context associated with the terminal identifier (UEidentity), and transmitting RRC Resume signaling to the terminal. Here, because the RRC Resume signaling is large, the network device adopts a segmented transmission method (taking the RRC Resume signaling divided into 3 segments as an example). The terminal's L1 layer successfully decodes the DLDedicatedMessageSegment (the first segment of the RRC recovery signaling) on ​​the downlink DCCH using the common radio parameters + CRNTI, and reports segment 1 to the RRC layer; because the RLC data carries Poll=1 during the segment transmission of the RRC Resume signaling, the RLC layer triggers RLC according to the protocol. In this application, the RLC STATU PDU (ack=0) can be placed in the pending queue and processed after the Resume successfully configures the dedicated L1 & L2 configurations. Steps 15-18: Since the network device sends RRC Resume signaling, the processing method of segment 2 and segment 3 is the same as in steps 13-14, poll=1, triggering RLC STATU PDU (ack=1) and RLC STATU PDU (ack=2). These RLC status reports are still placed in the pending queue and processed after the Resume successfully configures the dedicated L1 & L2 layer configurations.

[0145] In particular, the RLC STATUS PDU generated in steps 13-18 is delayed; otherwise, a random access procedure would be triggered, and the random access contention resolution would fail. This reduces the number of RACH processes triggered during the resume process, thereby preventing RACH failure from causing resume failure and improving the resume success rate.

[0146] Steps 19-22: Since all segments of the RRCResume signaling have been received, after the RRC layer decodes the RRCResume signaling stream, the dedicated configuration of the L1 & L2 layers is successful, and the terminal successfully resumes the connected state. Step 23: Take out all RLC STATUS PDUs in the pending queue (including status reports ack=1, ack=2, and ack=3), merge the status reports, and finally only keep the status report ack=3 to inform the network device that the segments SN=0,1,2 have been received. Steps 24-26: If SR resources are configured in the RRCResume signaling, request uplink authorization resources from the network through SR and send the RLC STATUS PDU to the network device. Steps 27-31: If SR resources are not configured in the RRCResume signaling, request uplink authorization resources from the network device through four-step random access and send the RLC STATUS PDU to the network device.

[0147] Steps 19-22 are the signs of successful RLC Resume recovery, which can be implemented according to the existing protocol; Step 23 is to merge the RLC STATUS PDUs in the delay queue and send them, thereby reducing the number of unnecessary RLC status reports and the number of RACH triggers.

[0148] In summary, the solution provided in this application has at least the following advantages: it optimizes the RLC status report sending mechanism, reduces resume time overhead, and allows the terminal to quickly recover from the inactive state to the connected state; it merges RLC status reports and reduces random access procedures, thereby reducing terminal power consumption during the resume process.

[0149] To implement the above embodiments, this application also proposes a communication device. Figure 8 This is a schematic diagram of the structure of a communication device provided for an exemplary embodiment of this application.

[0150] like Figure 8 As shown, the communication device 800 may include a configuration module 810 and a transmission module 820.

[0151] The configuration module 810 is used to configure the terminal's dedicated configuration according to each dedicated message segment in response to the terminal receiving downlink dedicated signaling sent by the network device; the sending module 820 is used to send a target status report to the network device based on the dedicated configuration in response to each dedicated message segment indicating that a message reception status needs to be sent to the network device. The target status report is used to indicate the reception status of each dedicated message segment.

[0152] In one implementation of this application, the sending module 820 is configured to: merge the RLC status reports triggered by the terminal's RLC layer for each dedicated message segment to obtain a target status report; wherein the RLC status report is used to indicate the reception status of the corresponding dedicated message segment; and send the target status report to the network device based on the dedicated configuration.

[0153] In one implementation of this application, the sending module 820 is configured to: in response to the absence of a scheduling request (SR) resource in the downlink dedicated signaling, obtain a first uplink authorized resource allocated to the terminal by the network device based on the dedicated configuration and the first random access procedure; and send a target status report through the first uplink authorized resource.

[0154] In one implementation of this application, the sending module 820 is configured to: initiate a first random access request and send a first random access preamble to the network device; wherein the first random access preamble is used by the network device to detect the first random access request; in response to receiving a first random access response sent by the network device, send a first message MSG3 to the network device carrying a scrambled target state report and a cell radio network temporary identifier (CRNTI); wherein the scrambled target state report is obtained by scrambling the target state report using CRNTI; based on a dedicated configuration, detect the DCI signaling sent by the network device in response to the first MSG3; wherein the DCI signaling is used to indicate a first uplink grant resource; in response to detecting the DCI signaling, determine that the random access contention has been successfully resolved, and send the target state report to the network device based on the first uplink grant resource indicated by the DCI signaling.

[0155] In one implementation of this application, the sending module 820 is further configured to: in response to the downlink dedicated signaling being configured with SR resources, send a scheduling request SR to the network device based on the SR resources; wherein the SR is used to request a second uplink grant resource from the network device; and in response to the network device having allocated a second uplink grant resource to the terminal, send a target status report to the network device through the second uplink grant resource.

[0156] In one implementation of this application, the sending module 820 is configured to: retrieve the RLC status report corresponding to each dedicated message segment from the delay queue; and merge the RLC status reports corresponding to each dedicated message segment to obtain the target status report.

[0157] In one implementation of this application, the communication device 800 may further include: an extraction module, configured to extract a target flag bit from the dedicated message segment in response to the terminal receiving any dedicated message segment of downlink dedicated signaling based on public radio parameters; wherein the target flag bit is used to indicate whether the terminal needs to send a message reception status to the network device; a triggering module, configured to trigger an RLC status report corresponding to the dedicated message segment through the RLC layer in response to the target flag bit indicating that the terminal needs to send a message reception status to the network device; and a writing module, configured to write the RLC status report corresponding to the dedicated message segment into a delay queue.

[0158] In one implementation of this application, in response to downlink dedicated signaling including RRC Resume signaling, configuration module 810 is configured to: in response to the terminal receiving each dedicated message segment of the RRC Resume signaling sent by the network device, configure the terminal's Layer 1 and Layer 2 dedicated configurations according to each dedicated message segment, so that the terminal recovers from the inactive state to the connected state; and sending module 820 is configured to: in response to each dedicated message segment indicating that a message receiving status needs to be sent to the network device, send a target status report to the network device based on the dedicated configuration in the connected state.

[0159] In one implementation of this application, the sending module 820 is further configured to: in response to the terminal being in an inactive state and the Layer 1 and Layer 2 having completed the configuration of common radio parameters, send an RRCResume request to the network device based on the common radio parameters and the second random access procedure; wherein the RRCResume request is used to request to recover from the inactive state to the connected state.

[0160] In one implementation of this application, the sending module 820 is configured to: initiate a second random access request to layer 1 in response to layer 2 receiving an RRCResume request sent by the RRC layer; send a second random access preamble to the network device through layer 1 based on common radio parameters and the second random access request; wherein the second random access preamble is used by the network device to detect the second random access request; send a second MSG3 carrying relevant information of the RRCResume request to the network device in response to layer 2 receiving a second random access response sent by the network device; indicate to the RRC layer that random access was successful in response to layer 2 receiving a random access contention resolution message sent by the network device based on common radio parameters; wherein the random access contention resolution message carries a third uplink grant resource allocated for the RRCResume request; and send the RRCResume request to the network device based on the third uplink grant resource.

[0161] In one implementation of this application, the communication device 800 may further include: a receiving module, configured to receive an RRC Release signaling sent by a network device in response to the terminal being in a connected state and the service process being completed; wherein the RRC Release signaling is used to instruct the terminal to enter an inactive state; and a control module, configured to control the terminal to switch from the connected state to the inactive state.

[0162] It should be noted that the explanation of the communication method embodiment executed by the terminal described above also applies to the communication device of this embodiment, and will not be repeated here.

[0163] In the communication device of this application embodiment, during the transmission of dedicated message segments, the RLC status report is sent with a delay. That is, the RLC status report is reported to the network device only after the terminal receives all dedicated message segments of downlink dedicated signaling and completes dedicated configuration accordingly. This not only effectively avoids unnecessary RACH triggering, enabling more rational use of radio resources and reducing resource waste, but also helps to improve the success rate of the terminal initiating RACH and ensures the continuity of communication.

[0164] To implement the above embodiments, this application also proposes a terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the communication method as described in any of the foregoing embodiments.

[0165] Figure 9 This is a schematic diagram of the structure of a terminal provided for an exemplary embodiment of this application. For example, the terminal 900 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.

[0166] Reference Figure 9 Terminal 900 may include one or more of the following components: processing component 902, memory 904, power component 906, multimedia component 908, audio component 910, input / output (I / O) interface 912, sensor component 914, and communication component 916.

[0167] Processing component 902 typically controls the overall operation of terminal 900, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 902 may include one or more processors 920 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 902 may include one or more modules to facilitate interaction between processing component 902 and other components. For example, processing component 902 may include a multimedia module to facilitate interaction between multimedia component 908 and processing component 902.

[0168] Memory 904 is configured to store various types of data to support operation on terminal 900. Examples of this data include instructions for any application or method operating on terminal 900, contact data, phonebook data, messages, pictures, videos, etc. Memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0169] Power component 906 provides power to various components of terminal 900. Power component 906 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to terminal 900.

[0170] Multimedia component 908 includes a screen that provides an output interface between the terminal 900 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a Touch Panel, the screen may be implemented as a touchscreen to receive input signals from the user. The Touch Panel includes one or more touch sensors to sense touches, swipes, and gestures on the Touch Panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 908 includes a front-facing camera and / or a rear-facing camera. When the terminal 900 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0171] Audio component 910 is configured to output and / or input audio signals. For example, audio component 910 includes a microphone (MIC) configured to receive external audio signals when terminal 900 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 904 or transmitted via communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.

[0172] I / O interface 912 provides an interface between processing component 902 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0173] Sensor assembly 914 includes one or more sensors for providing status assessments of various aspects of terminal 900. For example, sensor assembly 914 can detect the on / off state of terminal 900, the relative positioning of components such as the display and keypad of terminal 900, changes in the position of terminal 900 or a component of terminal 900, the presence or absence of user contact with terminal 900, the orientation or acceleration / deceleration of terminal 900, and temperature changes of terminal 900. Sensor assembly 914 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 914 may also include an optical sensor, such as a complementary metal-oxide-semiconductor (CMOS) or charge-coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, sensor assembly 914 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0174] Communication component 916 is configured to facilitate wired or wireless communication between terminal 900 and other devices. Terminal 900 can access wireless networks based on communication standards, such as WiFi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 916 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 916 also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be based on Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra-Wideband (UWB), Bluetooth, and other technologies.

[0175] In an exemplary embodiment, terminal 900 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0176] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including instructions, which can be executed by a processor 920 of a terminal 900 to complete the above method. For example, the non-transitory computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0177] To implement the above embodiments, this application also proposes a chip, wherein the chip includes an interface circuit and a processing circuit coupled to each other. The interface circuit is used to input or output signals, and the processing circuit is configured to perform the communication method provided in any of the foregoing embodiments.

[0178] Figure 10 This is a schematic diagram of the structure of a chip proposed in an exemplary embodiment of this application. See also... Figure 10 The diagram shown is a schematic representation of the structure of chip 1000, but it is not limited to this.

[0179] Chip 1000 includes processing circuit 1001, which is configured to perform any of the above communication methods.

[0180] In some embodiments, the chip 1000 further includes one or more interface circuits 1002. Optionally, the interface circuit 1002 is connected to the memory 1003, and the interface circuit 1002 can be used to receive signals from the memory 1003 or other devices, and the interface circuit 1002 can be used to send signals to the memory 1003 or other devices. For example, the interface circuit 1002 can read instructions stored in the memory 1003 and send the instructions to the processing circuit 1001.

[0181] In some embodiments, the interface circuit 1002 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processing circuit 1001 performs other steps.

[0182] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0183] In some embodiments, chip 1000 further includes one or more memories 1003 for storing instructions. Optionally, all or part of the memories 1003 may be located outside of chip 1000.

[0184] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the communication method as described in any of the foregoing method embodiments.

[0185] To implement the above embodiments, this application also proposes a computer program product having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the communication method as described in any of the foregoing method embodiments.

[0186] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0187] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0188] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0189] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and compact disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0190] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), FPGAs, etc.

[0191] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0192] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0193] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A communication method, characterized in that, include: In response to each dedicated message segment received by the terminal from the network device for downlink dedicated signaling, the dedicated configuration of the terminal is configured according to each dedicated message segment. In response to each of the dedicated message segments indicating that a message reception status needs to be sent to the network device, a target status report is sent to the network device based on the dedicated configuration, wherein the target status report is used to indicate the reception status of each of the dedicated message segments.

2. The method according to claim 1, characterized in that, Sending the target status report to the network device based on the dedicated configuration includes: The RLC status reports triggered by the RLC layer of the terminal for each dedicated message segment are merged to obtain the target status report; wherein, the RLC status report is used to indicate the reception status of the corresponding dedicated message segment; The target status report is sent to the network device based on the dedicated configuration.

3. The method according to claim 2, characterized in that, Sending the target status report to the network device based on the dedicated configuration includes: In response to the absence of a scheduling request (SR) resource in the downlink dedicated signaling, the first uplink authorized resource allocated by the network device to the terminal is obtained based on the dedicated configuration and the first random access procedure. The target status report is sent through the first uplink authorized resource.

4. The method according to claim 3, characterized in that, The step of obtaining the first uplink authorized resource allocated by the network device to the terminal based on the dedicated configuration and the first random access procedure includes: A first random access request is initiated, and a first random access preamble is sent to the network device; wherein, the first random access preamble is used by the network device to detect the first random access request; In response to receiving a first random access response from the network device, a first message MSG3 carrying a scrambled target state report and a cell radio network temporary identifier (CRNTI) is sent to the network device; wherein the scrambled target state report is obtained by scrambling the target state report using the CRNTI; Based on the dedicated configuration, the network device is detected responding to the DCI signaling sent by the first MSG3; wherein the DCI signaling is used to indicate the first uplink authorized resource; Sending the target status report through the first uplink authorized resource includes: In response to the detection of the DCI signaling, it is determined that the random access contention has been successfully resolved, and the target status report is sent to the network device based on the first uplink authorized resource indicated by the DCI signaling.

5. The method according to claim 3, characterized in that, Sending the target status report to the network device based on the dedicated configuration further includes: In response to the downlink dedicated signaling which is configured with the SR resource, a scheduling request SR is sent to the network device based on the SR resource; wherein the SR is used to request a second uplink authorized resource from the network device; In response to the network device having allocated the second uplink grant resource to the terminal, the target status report is sent to the network device through the second uplink grant resource.

6. The method according to claim 2, characterized in that, The step of merging the RLC status reports triggered by the RLC layer of the terminal for each dedicated message segment to obtain the target status report includes: Retrieve the RLC status report corresponding to each dedicated message segment from the delay queue; The RLC status reports corresponding to each dedicated message segment are merged to obtain the target status report.

7. The method according to claim 6, characterized in that, Before configuring the dedicated configuration according to each dedicated message segment in response to the terminal receiving downlink dedicated signaling sent by the network device, the method further includes: In response to the terminal receiving any of the dedicated message segments of the downlink dedicated signaling based on public radio parameters, a target flag bit is extracted from the dedicated message segment; wherein, the target flag bit is used to indicate whether the terminal needs to send a message reception status to the network device; In response to the target flag indicating that the terminal needs to send a message reception status to the network device, the RLC status report corresponding to the dedicated message segment is triggered through the RLC layer; Write the RLC status report corresponding to the dedicated message segment into the delay queue.

8. The method according to any one of claims 1-7, characterized in that, In response to the downlink dedicated signaling, including RRC recovery resume signaling, The method of responding to each dedicated message segment received by the terminal from the network device for downlink dedicated signaling, and configuring the dedicated configuration of the terminal according to each dedicated message segment, includes: In response to each dedicated message segment of the RRRCResume signaling sent by the network device, the terminal configures the dedicated configuration of Layer 1 and Layer 2 according to each dedicated message segment, so that the terminal recovers from the inactive state to the connected state; The response to each of the dedicated message segments indicating that a message reception status needs to be sent to the network device, and the sending of a target status report to the network device based on the dedicated configuration, includes: In response to each of the dedicated message segments indicating that a message reception status needs to be sent to the network device, in the connected state, the target status report is sent to the network device based on the dedicated configuration.

9. The method according to claim 8, characterized in that, Before configuring the terminal's Layer 1 and Layer 2 dedicated configurations according to each dedicated message segment in response to the terminal receiving the RRRCResume signaling sent by the network device, the method further includes: In response to the terminal being in an inactive state, and the Layer 1 and Layer 2 having completed the configuration of common radio parameters, the RRRCResume request is sent to the network device based on the common radio parameters and the second random access procedure. The RRCResume request is used to request a return from the inactive state to the connected state.

10. The method according to claim 9, characterized in that, The step of sending the RRRCResume request to the network device based on public radio parameters and the second random access procedure includes: In response to receiving the RRCResume request sent by the RRC layer, the layer 2 initiates a second random access request to the layer 1; Layer 1 sends a second random access preamble to the network device based on the public radio parameters and the second random access request; wherein the second random access preamble is used by the network device to detect the second random access request; In response to the Layer 2 receiving the second random access response sent by the network device, a second MSG3 carrying relevant information of the RRRCResume request is sent to the network device; In response to the Layer 2 receiving a random access contention resolution message sent by the network device based on the public radio parameters, the Layer 2 indicates to the RRC layer that random access was successful; wherein the random access contention resolution message carries a third uplink grant resource allocated for the RRC Resume request; Based on the third uplink grant resource, the RRCResume request is sent to the network device.

11. The method according to claim 8, characterized in that, The method further includes: In response to the terminal being in a connected state and the service process being completed, the terminal receives an RRC Release signaling sent by the network device; wherein the RRC Release signaling is used to instruct the terminal to enter an inactive state; Control the terminal to switch from the connected state to the inactive state.

12. A communication device, characterized in that, include: The configuration module is used to configure the terminal's dedicated configuration according to each dedicated message segment in response to the terminal receiving downlink dedicated signaling sent by the network device. The sending module is configured to send a target status report to the network device based on the dedicated configuration in response to each of the dedicated message segments indicating that a message reception status needs to be sent to the network device. The target status report is used to indicate the reception status of each of the dedicated message segments.

13. The apparatus according to claim 12, characterized in that, The sending module is used for: The RLC status reports triggered by the RLC layer of the terminal for each dedicated message segment are merged to obtain the target status report; wherein, the RLC status report is used to indicate the reception status of the corresponding dedicated message segment; The target status report is sent to the network device based on the dedicated configuration.

14. The apparatus according to claim 13, characterized in that, The sending module is used for: In response to the absence of a scheduling request (SR) resource in the downlink dedicated signaling, the first uplink authorized resource allocated by the network device to the terminal is obtained based on the dedicated configuration and the first random access procedure. The target status report is sent through the first uplink authorized resource.

15. The apparatus according to claim 14, characterized in that, The sending module is further configured to: In response to the downlink dedicated signaling which is configured with the SR resource, a scheduling request SR is sent to the network device based on the SR resource; wherein the SR is used to request a second uplink authorized resource from the network device; In response to the network device having allocated the second uplink grant resource to the terminal, the target status report is sent to the network device through the second uplink grant resource.

16. A terminal, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the steps of the method as described in any one of claims 1 to 11.

17. A non-transitory computer-readable storage medium having computer program instructions stored thereon, characterized in that, When executed by a processor, the program instructions implement the steps of the method described in any one of claims 1 to 11.

18. A chip, characterized in that, The chip includes an interface circuit and a processing circuit that are coupled to each other. The interface circuit is used to input or output signals, and the processing circuit is used to implement the method of any one of claims 1 to 11.

19. A computer program product, characterized in that, It includes a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 11.

Images