Communication method, device, and computer storage medium
By configuring groups, timers, and drop indication mechanisms, and combining the importance of SDUs and the number of retransmissions, the problem of not being able to trigger RLF in RLC AM mode was solved, realizing normal wireless link quality detection under unreliable transmission conditions, and improving the reliability and efficiency of the communication system.
Patent Information
- Application Number
- PCT/CN2026/079718
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-02-24
- Publication Date
- 2026-11-12
AI Technical Summary
When the existing RLC AM mode is configured with the function to avoid unnecessary retransmissions, the RLC entity may be unable to detect the radio link quality properly because the number of retransmissions will never reach the configured maximum number of retransmissions, thus failing to trigger Radio Link Failure (RLF).
By using configuration groups and timer mechanisms, combined with the importance of SDU and the number of retransmissions, the maximum retransmission threshold is updated to ensure that RLF can still be triggered when uplink transmission is unavailable/unreliable. Mechanisms such as the first configuration group, the second configuration group, timers, and drop indications are used to achieve normal radio link quality detection for RLC entities.
This ensures that RLF can still be triggered even when uplink transmission is unavailable or unreliable, thereby ensuring that the RLC entity can properly detect the quality of the wireless link and improving the reliability and efficiency of the communication system.
Smart Images

Figure CN2026079718_12112026_PF_FP_ABST
Abstract
Description
A communication method, device, and computer storage medium
[0001] This application claims priority to Chinese Patent Application No. 202510599819.2, filed on May 9, 2025, entitled "A Communication Method, Device and Computer Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communication technology, and in particular to a communication method, device and computer storage medium. Background Technology
[0003] Extended Reality (XR) is an innovative digital experience platform that integrates Virtual Reality (VR) and Augmented Reality (AR) technologies. To better support XR services, 3GPP Release 19's Radio Link Control (RLC) layer initiated enhancement research, primarily focusing on enhancing the RLC acknowledged mode (AM). Specifically, RLC AM mode requires the RLC transmitting entity to receive an acknowledgment report from the receiving end before ceasing to maintain the data packet.
[0004] According to the current RLC and Radio Resource Control (RRC) specifications, if an RLC service data unit (SDU) reaches the configured maximum number of retransmissions within a certain period of time, a radio link failure (RLF) is triggered, thereby initiating RRC reconstruction.
[0005] However, when the "avoid unnecessary retransmissions" function is configured on the transmitting RLC entity, the number of retransmissions may never reach the configured maximum. This is because the corresponding RLC SDU will stop being retransmitted before the maximum number of retransmissions is reached, based on the drop instruction from the Packet Data Convergence Protocol (PDCP) layer, which may cause the RLC entity to be unable to properly detect the radio link quality. Summary of the Invention
[0006] To address the aforementioned issues, this application provides a communication method, device, and computer storage medium that can trigger RLF normally even if the terminal device supports the "avoid unnecessary retransmission function," ensuring that the RLC entity can normally detect the wireless link quality.
[0007] In a first aspect, this application provides a communication method applied to a terminal device, comprising: receiving first information sent by a network device, the first information including configuration information, the configuration information including at least one of the following: a first configuration group, a second configuration group, first enable information, and update information of the maximum retransmission threshold for a Service Data Unit (SDU); and determining whether to trigger an Retransmission Request for Fire (RLF) based on the first information. The first configuration group indicates whether to trigger an RLF by summing the retransmission counts of SDUs transmitted based on a Radio Link Control (RLC) entity; the second configuration group indicates whether to trigger an RLF by determining the number of SDUs transmitted based on an RLC entity that meet the retransmission threshold; and the first enable information indicates whether to enable the cessation of retransmission after a high-importance SDU times out.
[0008] In the method provided in this application, the first configuration group and the second configuration group determine the retransmission count on an RLC entity basis. The first configuration group indicates whether to trigger an RLF (Recurrent Link Default) by summing the retransmission counts of SDUs transmitted based on the RLC entity, while the second configuration group indicates whether to trigger an RLF by determining the number of SDUs transmitted based on the RLC entity that meet the retransmission count threshold. The first enable information indicates whether to enable retransmission cessation after a high-importance SDU timeout, thus enabling the determination of whether to trigger an RLF based on a subset of SDUs, considering their importance. The update information for the maximum retransmission count threshold of the SDU updates the maximum retransmission count threshold of the SDU when a discard indication is received from the RLC SDU, facilitating timely triggering of an RLF. In summary, the terminal device in this application not only triggers an RLF based on whether the retransmission count of the SDU reaches the configured maximum retransmission count, but also ensures that an RLF can still be triggered even when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can normally detect the wireless link quality.
[0009] In one possible implementation, the first configuration group includes: a first threshold and the duration of a first timer; wherein, the first threshold represents the maximum number of retransmissions that the RLC entity can trigger an RLF; and the duration of the first timer is the maximum detection duration of the RLF.
[0010] In this implementation, the network device can configure the first threshold and the duration of the first timer of the RLC entity to the UE, so that the UE can determine whether to trigger RLF based on the sum of the number of retransmissions of SDU transmitted by the RLC entity. This ensures that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can detect the radio link quality normally.
[0011] In one possible implementation, the first timer is started when the RLC entity receives a discard instruction for the SDU and the SDU has been delivered to the lower layer; the first timer stops and the first variable is set to zero when the first variable is greater than or equal to the first threshold; the first variable is set to zero when the first timer times out and the first variable has not reached the first threshold; wherein, the first variable is used to record the sum of the number of retransmissions of the timed-out SDU transmitted by the RLC entity.
[0012] In one possible implementation, determining whether to trigger RLF is based on first information, specifically including: triggering RLF when the first variable is greater than or equal to the first threshold.
[0013] In one possible implementation, the second configuration group includes: a second threshold, a third threshold, and the duration of a second timer; wherein, the second threshold represents the maximum number of SDUs that the RLC entity can trigger an RLF; the duration of the second timer is the maximum detection duration of the RLF; and the third threshold is the minimum number of retransmissions reached by the timeout SDUs used to trigger the RLF.
[0014] In this implementation, the network device can configure the second threshold, the third threshold, and the duration of the second timer of the RLC entity to the UE, so that the UE can determine whether to trigger RLF based on the number of SDUs that meet the retransmission number threshold transmitted by the RLC entity. This ensures that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can detect the radio link quality normally.
[0015] In one possible implementation, the second timer is started when the SDU has been submitted to the lower layer and the number of SDU retransmissions is greater than or equal to the third threshold; when the second variable is greater than or equal to the second threshold, the second timer is stopped and the second variable is set to zero. The second variable is used to record the number of timeout SDUs that meet the third threshold in the RLC entity transmission; when the second timer times out and the second variable has not reached the second threshold, the second variable is set to zero.
[0016] In one possible implementation, determining whether to trigger RLF is based on the first information, specifically including: triggering RLF when the second variable is greater than or equal to the second threshold.
[0017] In one possible implementation, when the RLC entity receives a first discard instruction for an SDU and a first enable message indicates that retransmission is stopped after a high-importance SDU times out, the SDUs already submitted to the lower layer stop retransmission and no RLF is triggered. Otherwise, the SDUs already submitted to the lower layer do not stop retransmission, and whether to trigger an RLF is determined based on whether the number of retransmissions of the SDU reaches the maximum retransmission threshold of the SDU. When the RLC entity receives a second discard instruction for an SDU, the SDUs already submitted to the lower layer stop retransmission and no RLF is triggered. The first discard instruction is generated after the first discard timer times out, and the first discard timer is associated with a high-importance SDU. The second discard instruction is generated after the second discard timer times out, and the second discard timer is associated with a low-importance SDU.
[0018] In this implementation, the network device can configure first enable information to the UE so that the UE can determine whether to trigger RLF based on the enable status of "stop retransmission after high importance SDU timeout" and the importance of the timed-out SDU. This ensures that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can detect radio link quality normally.
[0019] In one possible implementation, the update information of the maximum retransmission threshold of the SDU includes an update value of the maximum retransmission threshold of at least one SDU; the update value of the maximum retransmission threshold of at least one SDU is less than or equal to the initial value of the maximum retransmission threshold of the SDU.
[0020] The UE determines whether to trigger RLF based on the updated value of the maximum retransmission threshold of the SDU, ensuring that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can normally detect the radio link quality.
[0021] In one possible implementation, the update information of the maximum retransmission threshold of the SDU indicates the mapping relationship between the updated value of the maximum retransmission threshold of the SDU and the initial value of the maximum retransmission threshold of the SDU, and the mapping relationship is used to determine the updated value of the maximum retransmission threshold of the SDU.
[0022] Network devices can send updated information about the maximum retransmission threshold of the SDU to the UE, so that the UE can determine the updated value of the maximum retransmission threshold of the SDU based on the updated information, and then determine whether to trigger RLF based on the updated value. This ensures that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can detect the radio link quality normally.
[0023] In one possible implementation, determining whether to trigger RLF based on the first information includes: triggering RLF when the RLC entity receives a discard instruction for the SDU and the number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU; when the RLC entity receives a discard instruction for the SDU and the number of retransmissions of the SDU is less than the updated value of the maximum retransmission threshold of the SDU, if a negative acknowledgment is received in the received status report SR, updating the number of retransmissions of the SDU; and triggering RLF when the updated number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU.
[0024] In one possible implementation, the method further includes: receiving second information, the second information including a first trigger threshold and / or a second trigger threshold, wherein the first trigger threshold is a threshold for triggering enhanced polling, and the second trigger threshold is a threshold for triggering autonomous retransmission.
[0025] Using this method, the PDCP layer can instruct the RLC to consider enhanced polling and autonomous retransmission of data packets, thus enabling the configuration of timely retransmission enhancement schemes.
[0026] In one possible implementation, the second information includes a first trigger threshold, and the method further includes: when the remaining time of the Packet Data Convergence Protocol (PDCP) SDU is less than or equal to the first trigger threshold, if the associated PDCP Data PDU has been submitted to the lower layer, then providing the lower layer with a first indication of the associated PDCP Data PDU; otherwise, when the associated PDCP Data PDU is submitted to the lower layer, providing the lower layer with a first indication of the associated PDCP Data PDU, the first indication being used to instruct the RLC entity to include Poll in the Acknowledgment Mode Data (AMD) PDU.
[0027] In one possible implementation, the second information includes a second trigger threshold, and the method further includes: when the remaining time of the Packet Data Convergence Protocol (PDCP) SDU is less than or equal to the second trigger threshold, if the associated PDCP Data PDU has been submitted to the lower layer, then providing a second indication of the associated PDCP Data PDU to the lower layer; otherwise, when the associated PDCP Data PDU is submitted to the lower layer, providing a second indication of the associated PDCP Data PDU to the lower layer, the second indication being used to trigger the RLC entity to perform autonomous retransmission.
[0028] In one possible implementation, the method further includes: when the sender of the acknowledgment mode AM RLC entity receives a negative acknowledgment of an RLC SDU or RLC SDU segment from a peer AM RLC entity via a STATUS PDU, or receives an autonomous retransmission instruction for the corresponding RLC SDU from the PDCP layer and the RLC SDU or RLC SDU segment is not waiting for retransmission, the sender of the AM RLC entity performs the following steps: if the corresponding RLC SDU has been delivered to the lower layer but no positive acknowledgment ACK has been received, retransmit the RLC SDU or RLC SDU segment.
[0029] In one possible implementation, the method further includes: when the sender of the acknowledgment mode AM RLC entity receives a negative acknowledgment of an RLC SDU or RLC SDU segment from the peer AM RLC entity via the STATUS PDU, or receives an autonomous retransmission instruction for the corresponding RLC SDU from the PDCP layer, the sender of the AM RLC entity performs the following steps: if the corresponding RLC SDU has been delivered to the lower layer but no positive acknowledgment ACK has been received, and the RLC SDU or RLC SDU segment is not waiting for retransmission, retransmit the RLC SDU or RLC SDU segment.
[0030] In one possible implementation, it is determined that an RLC SDU or RLC SDU segment is not waiting for retransmission based on the following method: when an auto-retransmission is triggered, the first buffer is traversed to determine whether an RLC SDU or RLC SDU segment is waiting for retransmission. The first buffer is used to cache the RLC SDU or RLC SDU segment corresponding to an automatic retransmission request (ARQ) retransmission. When an ARQ retransmission is triggered, the second buffer is traversed to determine whether an RLC SDU or RLC SDU segment is waiting for retransmission. The second buffer is used to cache the RLC SDU or RLC SDU segment corresponding to an auto-retransmission.
[0031] By using two buffers to cache RLC SDUs or RLC SDU segments corresponding to different types of retransmissions, the overall number of cached RLC SDUs or RLC SDU segments will not increase, but targeted traversal can be performed, reducing traversal overhead and improving efficiency.
[0032] Secondly, this application provides a communication method applied to a network device, comprising: sending first information, the first information including configuration information, the configuration information including at least one of the following: a first configuration group, a second configuration group, first enable information, and update information of the maximum retransmission number threshold of a Service Data Unit (SDU); the first information is used to enable a terminal device to determine whether to trigger an Retransmission Request for Fire (RLF); wherein the first configuration group indicates whether to trigger an RLF by summing the retransmission number of SDUs transmitted based on a Radio Link Control (RLC) entity; the second configuration group indicates whether to trigger an RLF by determining the number of SDUs transmitted based on an RLC entity that meet the retransmission number threshold; and the first enable information indicates whether to enable the cessation of retransmission after a high-importance SDU times out.
[0033] This method sends a first message to the terminal device, enabling the terminal device to trigger RLF not only based on whether the number of retransmissions of the SDU has reached the configured maximum number of retransmissions, but also to ensure that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can normally detect the quality of the wireless link.
[0034] In one possible implementation, the first configuration group includes: a first threshold and the duration of a first timer; wherein, the first threshold represents the maximum number of retransmissions that the RLC entity can trigger an RLF; and the duration of the first timer is the maximum detection duration of the RLF.
[0035] In one possible implementation, the first timer is started when the RLC entity receives a discard instruction for the SDU and the SDU has been delivered to the lower layer; the first timer stops and the first variable is set to zero when the first variable is greater than or equal to the first threshold; the first variable is set to zero when the first timer times out and the first variable has not reached the first threshold; wherein, the first variable is used to record the sum of the number of retransmissions of the timed-out SDU transmitted by the RLC entity.
[0036] In one possible implementation, an RLF is triggered when the first variable is greater than or equal to a first threshold.
[0037] In one possible implementation, the second configuration group includes: a second threshold, a third threshold, and the duration of a second timer; wherein, the second threshold represents the maximum number of SDUs that the RLC entity can trigger an RLF; the duration of the second timer is the maximum detection duration of the RLF; and the third threshold is the minimum number of retransmissions reached by the timeout SDUs used to trigger the RLF.
[0038] In one possible implementation, the second timer is started when the SDU has been submitted to the lower layer and the number of SDU retransmissions is greater than or equal to the third threshold; when the second variable is greater than or equal to the second threshold, the second timer is stopped and the second variable is set to zero. The second variable is used to record the number of timeout SDUs that meet the third threshold in the RLC entity transmission; when the second timer times out and the second variable has not reached the second threshold, the second variable is set to zero.
[0039] In one possible implementation, an RLF is triggered when the second variable is greater than or equal to the second threshold.
[0040] In one possible implementation, if the first enable message indicates that retransmission is stopped after a high-importance SDU timeout, then when the RLC entity receives the first discard instruction for the SDU, the SDUs already submitted to the lower layer stop retransmission, and RLF is not triggered; if the first enable message indicates that retransmission is stopped after a high-importance SDU timeout, then when the RLC entity receives the first discard instruction for the SDU, the SDUs already submitted to the lower layer do not stop retransmission, and whether to trigger RLF is determined based on whether the number of retransmissions of the SDU reaches the maximum retransmission threshold of the SDU; when the RLC entity receives the second discard instruction for the SDU, the SDUs already submitted to the lower layer stop retransmission, and RLF is not triggered; wherein, the first discard instruction is generated after the first discard timer times out, and the first discard timer is associated with a high-importance SDU; the second discard instruction is generated after the second discard timer times out, and the second discard timer is associated with a low-importance SDU.
[0041] In one possible implementation, the update information of the maximum retransmission threshold of the SDU includes an update value of the maximum retransmission threshold of at least one SDU; the update value of the maximum retransmission threshold of at least one SDU is less than or equal to the initial value of the maximum retransmission threshold of the SDU.
[0042] In one possible implementation, the update information of the SDU's maximum retransmission threshold indicates the mapping relationship between the updated value of the SDU's maximum retransmission threshold and the initial value of the SDU's maximum retransmission threshold. This mapping relationship is used to determine the updated value of the SDU's maximum retransmission threshold.
[0043] In one possible implementation, when the RLC entity receives a discard instruction for the SDU and the number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU, an RLF is triggered; when the RLC entity receives a discard instruction for the SDU and the number of retransmissions of the SDU is less than the updated value of the maximum retransmission threshold of the SDU, if a negative acknowledgment is received in the received status report SR, the number of retransmissions of the SDU is updated, and an RLF is triggered when the updated number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU.
[0044] In one possible implementation, the method further includes: sending second information, the second information including a first trigger threshold and / or a second trigger threshold, the first trigger threshold being a threshold for triggering enhanced polling, and the second trigger threshold being a threshold for triggering autonomous retransmission.
[0045] Thirdly, this application also provides a terminal device, which includes a processor and a memory. The processor is coupled to the memory; the memory is used to store instructions; the processor is used to execute the computer program or instructions stored in the memory to implement the methods described in the first aspect and any implementation thereof.
[0046] Fourthly, this application also provides a network device, which includes a processor and a memory. The processor is coupled to the memory; the memory is used to store instructions; the processor is used to execute the computer program or instructions stored in the memory to implement the methods described in the second aspect and any implementation thereof above.
[0047] Fifthly, this application also provides a computer storage medium for storing a computer program, which, when executed, implements the method described in the first aspect and any implementation thereof, or implements the method described in the second aspect and any implementation thereof.
[0048] Sixthly, this application also provides a communication system, which includes the terminal equipment provided in the third aspect above and the network equipment provided in the fourth aspect above. Optionally, the communication system may also include other equipment that communicates with the terminal equipment and / or the network equipment.
[0049] In a seventh aspect, this application also provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform a method in any of the possible implementations of any of the above aspects. Attached Figure Description
[0050] Figure 1 is a schematic diagram of a communication system applied in an embodiment of this application;
[0051] Figure 2 is a schematic diagram of an application scenario applicable to this application;
[0052] Figure 3 is a schematic diagram of another application scenario applicable to this application;
[0053] Figure 4 is a schematic diagram of the user plane protocol stack provided in this application;
[0054] Figure 5 is a schematic diagram of the control plane protocol stack provided in this application;
[0055] Figure 6 is a flowchart of a communication method provided in an embodiment of this application;
[0056] Figure 7 is a flowchart of another communication method provided in an embodiment of this application;
[0057] Figure 8 is a flowchart of another communication method provided in an embodiment of this application;
[0058] Figure 9 is a flowchart of another communication method provided in an embodiment of this application;
[0059] Figure 10 is a flowchart of another communication method provided in an embodiment of this application;
[0060] Figure 11 is a flowchart of another communication method provided in an embodiment of this application;
[0061] Figure 12 is a schematic diagram of a network device provided in an embodiment of this application;
[0062] Figure 13 is a schematic diagram of another network device provided in an embodiment of this application;
[0063] Figure 14 is a schematic diagram of a terminal device provided in an embodiment of this application. Detailed Implementation
[0064] The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, “one or more” means one, two, or more; “and / or” describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character “ / ” generally indicates that the preceding and following related objects are in an “or” relationship.
[0065] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0066] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.
[0067] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.
[0068] Referring to Figure 1, this figure is a schematic diagram of a communication system applied in an embodiment of this application.
[0069] The wireless communication system includes an access network 400 and a core network 200. Optionally, the communication system may also include an Internet 300.
[0070] The radio access network 100 can be a next-generation (e.g., 6G or higher) radio access network or a traditional (e.g., 5G, 4G, 3G or 2G) radio access network.
[0071] One or more terminal devices 420 (only one is shown in the figure) can be interconnected or connected to one or more network devices in the access network 400. In Figure 1, the access network 400 includes network devices 410a and 410b as an example.
[0072] The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units that can implement some of the functions of a base station. Access network equipment can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, access network equipment can also be a server, wearable device, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as a network device.
[0073] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.
[0074] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.
[0075] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.
[0076] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios; for example, both can be deployed on land; or the access network device can be deployed on land, and the terminal device on water, etc., and so on.
[0077] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing some of the functions of a base station. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).
[0078] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.
[0079] See Figure 2, which is a schematic diagram of an application scenario applicable to this application.
[0080] As shown in Figure 2, the embodiments of this application can be applied to the field of extended reality (XR) business.
[0081] XR is an innovative digital experience platform that integrates Virtual Reality (VR) and Augmented Reality (AR) technologies. By utilizing computer graphics, perception technology, and human-computer interaction technology, XR merges virtual information with real-world scenes, enabling users to interact with the virtual world in real time. XR service data packets mainly consist of video / images and interactive commands, and their network requirements include high throughput, low latency, and high reliability.
[0082] The business scenario includes AF network elements and multiple XR devices, such as XR device 1 and XR device 2.
[0083] In this example, the AF network element can be an XR server, and the XR device can be an XR head-mounted display (HMD) or XR glasses. The XR device can also include a controller, such as a gamepad. In this example, XR device 1 can be XR glasses, and XR device 2 can be a gamepad. Users can wear XR glasses and hold the gamepad to play cloud games.
[0084] The XR server can receive video frames, audio data, haptic data, or pose and control data from the XR device, such as video frames and audio data captured by the XR glasses, and haptic data and pose and control data captured by the controller. It then returns the processed video frames, audio data, haptic data, or pose and control data to the XR device. The XR server and XR device interact with each other through communication links in the network architecture, forming a global control loop. The video frames mentioned above can also be referred to as video data or video frame data.
[0085] In multimodal service application scenarios, multiple data streams are required, such as QoS streams, to transmit different data types, including video, audio, haptic feedback, or gesture and control data. These data streams are spatially and temporally correlated.
[0086] In the example of Figure 2, data collected by the XR device, such as video frames, audio data, haptic data, gesture and control data, can be transmitted from the terminal device to the access network, for example, to an access network device, such as a gNB. The access network device can transmit the above data to the 5GC through QoS flow, and then the 5GC transmits the above data to the XR server.
[0087] It should be noted that XR devices can also communicate directly with access network devices. For example, if an XR device integrates an eSIM or UE functionality, it can directly connect to the access network device. Consequently, the XR device can directly transmit collected data to the access network device, for example, via QoS flow, without going through the UE. Alternatively, the terminal can be located inside the XR device. For example, terminal 1 can be located inside XR device 1, and terminal 2 can be located inside XR device 2. XR devices 1 and 2 can then directly interact with the access network device.
[0088] Correspondingly, the XR server can return multimodal data streams to the XR device. Specifically, the XR server can first return multimodal data streams to the 5GC, which then transmits the multimodal data streams to the access network device via QoS flow. The access network device then transmits the multimodal data streams to the corresponding UEs, and the UEs then transmit the received data streams to the XR device. The multimodal data streams can be transmitted using PDU sets.
[0089] It should be noted that Figure 2 illustrates a multimodal scenario where multiple XR devices connect to the network through different terminals, such as an inter-UE multimodal scenario. In other possible implementations of this application, the application scenario may also include a multimodal scenario where multiple XR devices connect to the network through the same terminal, such as an intra-UE multimodal scenario.
[0090] As shown in Figure 3, multiple XR devices can connect to the network through the same terminal. This terminal can serve as a unified entry or exit point for the multiple XR devices, enabling interaction with the XR server. The multiple XR devices can include XR Device 1 and XR Device 2. In the example in Figure 3, XR Device 1 can be XR glasses, which can collect video and audio data. XR Device 2 can be a controller, which can collect tactile, posture, and control data. XR Device 1 and XR Device 2 are connected to the same terminal, and the data collected by XR Device 1 and XR Device 2 can be transmitted to the access network device through the terminal.
[0091] Figures 2 and 3 above illustrate only two XR devices. This application can be applied to multiple XR devices, and is not limited to two. Furthermore, the XR devices described above can also be replaced with other sensing devices, and this application does not impose any restrictions on this.
[0092] Besides the application scenarios involving the architecture between the application server and terminal devices described above, the application scenarios of this application can also be constructed using multiple terminal devices. In a scenario constructed using multiple terminal devices, one side of the terminal device may include an XR HMD and a controller, while the other side of the terminal device may include a remote robot. Users can control the remote robot through the controller, combining the content presented by the XR HMD. The construction of the application scenarios of this application is not limited to the above scenarios; all application scenarios applicable to the technical solutions of this application are within the protection scope of this application.
[0093] In addition to the above scenarios, this application solution can also be applied to scenarios with multimodal services such as healthcare, road traffic, and distance education, which will not be elaborated on again.
[0094] The data transmission methods in the above scenarios are explained below, along with a brief explanation of the relevant data. Optionally, explanations of some terms can also be found in the 3rd Generation Partnership Project (3GPP) standard protocol.
[0095] See Figure 4, which is a schematic diagram of the user plane protocol stack provided in this application.
[0096] The user plane protocol stack is used to transmit service data and includes the Physical Layer (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP).
[0097] Specifically, the physical layer provides a transmission channel for the MAC layer; the MAC layer provides a logical channel for the RLC layer; the RLC layer provides an RLC channel for the PDCP layer; the PDCP layer provides a radio bearer for the SDAP layer; and the SDAP layer provides a Quality of Service (QoS) flow for the 5GC.
[0098] The technical solution of this application mainly involves the PDCP layer and RLC layer of the user plane protocol stack.
[0099] Service Data Unit (SDU):
[0100] An SDU is a data packet received by this layer from the upper layer. For example, a data packet received by the RLC layer from the upper PDCP layer is called an RLC SDU.
[0101] Protocol Data Unit (PDU):
[0102] A PDU is a data packet processed by this layer after processing an SDU (adding header information, etc.). For example, the data packet that RLC processes an RLC SDU and delivers to the lower-layer MAC is an RLC PDU. The RLC layer has three transport modes: transport mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). Therefore, RLC PDUs can be referred to as TMD PDU, UMD PDU, and AMD PDU according to their mode.
[0103] See also Figure 5, which is a schematic diagram of the control plane protocol stack provided in this application.
[0104] The control plane protocol stack is used to transmit control data. This application mainly involves the Radio Resource Control (RRC) layer, the PDCP layer, and the RLC layer. The network side can configure the characteristics and related parameters of PDCP and RLC through RRC signaling, such as configuring timer durations and various threshold values.
[0105] PDU Set:
[0106] One or more PDUs are used to carry the payload of an information unit generated at the application layer (e.g., a frame or video clip of an XR service). PDUs belonging to the same set generally have the same QoS requirements, such as the same Packet Delay Budget (PDB), which can also be understood as the remaining time. PDUs in a PDU set correspond to PDCP SDUs.
[0107] pdu-SetDiscard:
[0108] The PDCP entity, PDU, has a drop parameter. If this parameter is configured, all packets in a PDU set will be processed in the same way.
[0109] discardTimer:
[0110] The PDCP entity discards a timer, which is configured only for the data radio bearer (DRB), and the duration of the timer is configured by the upper layer RRC TS 38.331[3]. In the transmitting end, a new timer is started when an SDU is received from the upper layer.
[0111] The following explains the behavior of enabling discardTimer.
[0112] When a PDCP SDU is received from the upper layer, the sending PDCP entity should:
[0113] If discardTimerForLowImportance is configured, and SDU discarding behavior based on PDU Set Importance (PSI) is activated, and the PDCP SDU belongs to a low-importance PDU set, then discardTimerForLowImportance associated with the PDCP SDU is enabled; otherwise, discardTimer associated with the PDCP SDU is enabled.
[0114] The PSI parameter indicates the relative importance of a PDU set compared to other PDU sets within the same QoS flow. Generally, a larger PSI value indicates a lower PDU set importance, and a smaller PSI value indicates a higher PDU set importance. For example, a PSI value of 0 indicates the highest importance PDU set, and a PSI value of 15 indicates the lowest importance PDU set. In the event of congestion, the PSI can be used to determine whether a PDU set should be dropped; for example, packets with lower importance indicated by the PSI value can be dropped during congestion.
[0115] The following explains the timeout behavior of discardTimer.
[0116] When the discardTimer or discardTimerForLowImportance of a PDCP SDU expires, the sending PDCP entity should: if pdu-SetDiscard is configured, discard all PDCP SDUs belonging to the PDU set to which the PDCP SDU belongs, as well as the corresponding PDCP data PDUs; if subsequent PDCP SDUs received from the upper layer belong to the same PDU set, they should also be discarded; otherwise, discard the PDCP SDU and the corresponding PDCP data PDUs.
[0117] If the corresponding PDCP data PDU has been submitted to the lower layer, PDCP provides a discard instruction to the lower layer.
[0118] Segmentation:
[0119] When the underlying MAC layer provides transmission opportunities (transmission resource size, etc.), it may not be sufficient to transmit the entire Found Mode Data (AMD) PDU. This can result in a situation where the final resource size is only enough to transmit a portion of the AMD PDU. In this case, it is necessary to segment the RLC SDU within the AMD PDU and then generate new, different AMD PDUs with the same serial number.
[0120] Polling mechanism:
[0121] An AM RLC entity (sender) can poll its peer AM RLC entity (receiver) to trigger a status report at the peer AM RLC entity (the status report contains information on the success / failure of receiving some SDUs).
[0122] The following explains the triggering conditions for Poll.
[0123] When a lower layer notifies of a transmission opportunity, for each AMD PDU submitted for transmission, if the AMD PDU contains an RLC SDU that has not been previously transmitted or an RLC SDU segment containing a previously untransmitted byte segment, the transmitter of the AM RLC entity should:
[0124] Increment PDU_WITHOUT_POLL by one;
[0125] Add BYTE_WITHOUT_POLL to each new data field element byte that it maps to in the AMD PDU data field;
[0126] If PDU_WITHOUT_POLL >= pollPDU, or if BYTE_WITHOUT_POLL >= pollByte: include polling in the AMD PDU.
[0127] When the lower layer notifies of a transmission opportunity, for each AMD PDU that submits a transmission, the transmission party of the AM RLC entity should:
[0128] If, after transmitting the AMD PDU, both the transfer buffer and the retransmission buffer become empty (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgment); or,
[0129] If a new RLC SDU cannot be transferred after the AMD PDU is transferred (e.g., due to window freeze);
[0130] Polling is included in AMD PDU.
[0131] When data is waiting at the upper layer, an empty RLC buffer (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgment) should not cause unnecessary polling.
[0132] All RLC SDUs received from the upper layer are placed in the transmission buffer, and the transmitted RLC SDUs are placed in the retransmission buffer.
[0133] Disposal instructions:
[0134] When an upper layer (e.g., PDCP) instructs the discard of a specific RLC SDU, if neither the RLC SDU nor its fragments have been committed to the lower layer, the sender of the AM RLC entity or the sending UM RLC entity should discard the instructing RLC SDU. The sender of the AM RLC entity should not introduce an RLC SN gap when discarding the RLC SDU.
[0135] If the RLC AM entity supports "avoid unnecessary retransmissions," then all SDUs transmitted by that TX RLC entity must adhere to this feature. When the TX RLC entity receives a discard instruction for an SDU (an SDU that has been submitted to the MAC layer) from the PDCP, the TX RLC entity will treat that SDU as an obsolete SDU. The TX RLC entity will not perform any transmission or retransmission of that SDU / SDU segment.
[0136] To better support XR services, 3GPP Release 19's RLC layer initiated enhancement technology research, primarily focusing on enhancing RLC AM mode. RLC AM refers to a mechanism where the RLC transmitting entity only ceases to maintain the data packet after receiving an acknowledgment report from the receiving end following data transmission.
[0137] For RLC AM, a large amount of data may become outdated during transmission, and there is currently no way to avoid retransmitting this data. The transmission of a large number of outdated SDUs consumes transmission resources, and due to the short latency of XR data packets, even more subsequent data packets may become outdated before successful transmission. To avoid retransmitting outdated data, the existing joint scheme between the sender (TX) and receiver (RX) sides is as follows:
[0138] When the TX RLC entity receives an SDU discard instruction from the PDCP, the TX RLC entity will treat the SDU as an expired SDU and will not perform any transmission or retransmission of the SDU / SDU segment.
[0139] The RX RLC entity introduces a new RLC timer to identify obsolete RLC SDUs; the timer is activated when a gap is detected in the RLC layer.
[0140] The RX RLC entity notifies the TX RLC entity of outdated SDUs. The outdated RLC SDUs determined by the new RLC timer are affirmed in the Status Report (SR).
[0141] Currently, "avoiding unnecessary retransmissions" is a feature of RLC AM entities, and whether this feature is supported is determined by the network configuration when the RLC AM entity is established.
[0142] On the RLC AM entity sender (TX), the radio link quality needs to be detected by the number of SDU retransmissions. When the number of retransmission failures of an SDU / SDU segment reaches maxRetxThreshold (maximum number of retransmissions, configured by the network side), a radio link failure (RLF) is triggered, thus initiating RRC reconstruction.
[0143] If the RLC AM entity supports "avoid unnecessary retransmissions," then all SDUs transmitted by that TX RLC entity must adhere to this feature. When the TX RLC entity receives a discard instruction for an SDU (an SDU that has been submitted to the MAC layer) from the PDCP, the TX RLC entity will treat that SDU as an obsolete SDU. The TX RLC entity will not perform any transmission or retransmission of that SDU / SDU segment. In this case, if the number of retransmissions for that SDU / SDU segment is less than the maximum number of retransmissions, RLF will not be triggered.
[0144] In summary, if the RLC AM entity supports "avoiding unnecessary retransmissions," an SDU must reach the maximum retransmission count within a certain period (based on a PDCP timer) in order to trigger RLF correctly. In existing protocols, the time it takes for an SDU / SDU segment to reach the maximum retransmission count cannot be guaranteed, which may cause the RLC entity to fail to properly detect the radio link quality.
[0145] To address the above technical problems, this application provides a communication method, device, and computer storage medium. Using this method, a network device can configure configuration information for determining whether to trigger a Radio Link Failure (RLF) by sending first information to a terminal device. This ensures that the terminal device triggers the RLF not only based on whether the number of retransmissions of the SDU has reached the configured maximum number of retransmissions, but also ensures that the RLF can still be triggered when the uplink transmission is unavailable or unreliable, thereby ensuring that the RLC entity can normally detect the radio link quality.
[0146] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.
[0147] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.
[0148] Referring to Figure 6, this figure is a flowchart of a communication method provided in an embodiment of this application.
[0149] The following description uses the UE as an example of a terminal device, and the method includes the following steps:
[0150] S11: The network device sends first information to the UE, which includes configuration information.
[0151] The configuration information included in the first information in this application embodiment may include one or more of the following: first configuration group, second configuration group, first enable information, and update information of the maximum retransmission number threshold of SDU, which will be described below.
[0152] The first and second configuration groups determine the number of retransmissions based on RLC entities.
[0153] Specifically, the first configuration group instructs the terminal device to determine whether to trigger an RLF (Recursive Read Default) based on the sum of the retransmission counts of the SDUs transmitted by the RLC entity. For example, an RLF can be triggered when the sum of the retransmission counts of the SDUs transmitted by the RLC entity is greater than or equal to the maximum retransmission count threshold.
[0154] The second configuration group instructs the terminal device to determine whether to trigger an RLF (Retransmission Response Function) based on the number of SDUs that meet the retransmission threshold in RLC entity transmission. For example, an RLF can be triggered when the number of SDUs that meet the retransmission threshold is greater than or equal to the maximum number of SDUs threshold.
[0155] The first enable information indicates whether to enable the stop retransmission after a high-importance SDU timeout. The stop retransmission after a high-importance SDU timeout is a feature configured in network devices, allowing the UE to determine whether to trigger an RLF (Restricted Retransmission Function) based on the importance of the SDU.
[0156] For example, when the retransmission stop is enabled after a high-importance SDU times out, if the RLC receives a discard instruction for a high-importance RLC SDU, the RLC SDU that has been submitted to the lower layer will stop retransmitting, and no further RLF will be triggered. This is because after enabling this feature, the number of retransmissions of subsequent SDUs cannot reach the configured maximum number of retransmissions.
[0157] The UE can determine the updated value of the maximum retransmission threshold of the SDU based on the update information of the maximum retransmission threshold of the SDU. Based on the analysis of the shortcomings of existing technologies, it is known that when the "avoid unnecessary retransmissions" function is configured on the transmitting end RLC entity, the retransmission count may never reach the configured maximum retransmission count. Therefore, in this embodiment, the updated value of the maximum retransmission threshold of the SDU is generally less than the initial value of the maximum retransmission threshold of the SDU, thus reducing the maximum retransmission threshold of the SDU after the update. This ensures that the retransmission count of the SDU is greater than or equal to the updated maximum retransmission threshold of the SDU before the LCR entity receives the discard indication from the PDCP layer, thereby triggering the RLF.
[0158] S12: The UE determines whether to trigger RLF based on the first information.
[0159] After the UE obtains the first information, it determines whether to trigger RLF based on the configuration information in the first information. When the RLC entity supports "avoiding unnecessary retransmission", the UE has an additional method to judge the quality of the radio link.
[0160] In summary, the network device in this application embodiment can configure the UE based on the first information, so that the UE can trigger RLF not only based on whether the number of retransmissions of SDU reaches the configured maximum number of retransmissions, but also based on a more flexible and reliable method to trigger RLF, thereby ensuring that the RLC entity can normally detect the wireless link quality.
[0161] The following section will explain the specific implementation method.
[0162] First, we will introduce the implementation method when the configuration information includes the first configuration group.
[0163] Referring to Figure 7, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0164] The method includes the following steps:
[0165] S21: The network device sends first information to the UE. The first information includes a first configuration group, which includes a first threshold and the duration of a first timer.
[0166] In this embodiment of the application, the first information includes a first configuration group, which is used to configure a first threshold and the duration of a first timer when the RLC entity is established.
[0167] The first threshold represents the maximum number of retransmissions that an RLC entity can trigger an RLF, and is denoted as maxRetxThresholdPerRLC in this embodiment. The first timer in this embodiment is denoted as RLFtimer.
[0168] The duration of the first timer is the maximum detection duration of the RLF. In this embodiment, the first timer is started when the RLC entity receives the SDU discard instruction and the SDU has been submitted to the lower layer, and stops when the first variable is greater than or equal to the first threshold.
[0169] The first variable is used to record the sum of the number of retransmissions of the timeout SDU in the RLC entity transmission. When the first variable is greater than or equal to the first threshold, the first variable is set to zero. When the first timer times out and the first variable has not reached the first threshold, the first variable is set to zero.
[0170] The network device configures the UE based on the first information, so that the UE does not only trigger RLF based on whether the SDU retransmission count has reached the configured maximum retransmission count.
[0171] S22: The UE uses the first variable to record the sum of the number of retransmissions of all timeout SDUs transmitted by the RLC entity.
[0172] In this embodiment, the first variable is represented by RLF_RETX_COUNT. When the RLC entity is established, the UE uses the first variable to record the sum of the number of retransmissions of all timeout SDUs transmitted by the RLC entity during the first timer period. The initial value of the first variable is zero.
[0173] In this embodiment, it is no longer necessary to determine whether the number of retransmissions of the SDU has reached the configured maximum number of retransmissions. Instead, a comparison is made between the first variable and the first threshold to determine whether to trigger RLF. Since the first variable records the sum of the number of retransmissions of all timed-out SDUs, it can provide another method to trigger RLF when the number of retransmissions of a single SDU cannot trigger RLF.
[0174] S23: The UE triggers an RLF when the first variable is greater than or equal to the first threshold.
[0175] During data transmission, when the PDCP layer receives a PDCP SDU from the upper layer, it starts a discard timer. This discard timer can be either discardTimer or discardTimerForLowImportance; this embodiment does not specify a particular timer. The discard timer is associated with the PDCP SDU.
[0176] The PDCP layer assembles the PDCP SDU into a PDCP PDU and delivers it to the RLC layer. During this process, the timer associated with the PDCP PDU runs continuously.
[0177] When the PDCP layer timer expires, if the associated PDCP SDU has already been submitted to the lower layer, the RLC layer is provided with a discard instruction for the PDCP SDU associated with that timer.
[0178] During data transmission, when the RLC receives a discard instruction for a certain RLC SDU (PDCP PDU), if the RLC SDU has not been delivered to the lower layer, the RLC discards the SDU; if the RLC SDU has been delivered to the lower layer and the first timer RLFtimer is not running, the RLFtimer is started.
[0179] At this point, the first variable RLF_RETX_COUNT = RLF_RETX_COUNT + RETX_COUNT of the SDU.
[0180] RETX_COUNT is the retransmission counter value, recording the number of retransmissions for the associated RLC SDU or RLC SDU segment. The first variable is updated as the number of retransmissions accumulates.
[0181] If RLF_RETX_COUNT ≥ maxRetxThresholdPerRLC, it indicates that the cumulative number of retransmissions triggered by the RLC entity has reached the maximum retransmission threshold for triggering RLF. At this time, it can indicate to the upper layer that the maximum number of retransmissions has been reached to trigger RLF, and reset RLF_RETX_COUNT to zero and stop the first timer RLFtimer.
[0182] When the first timer RLFtimer times out and RLF_RETX_COUNT is less than maxRetxThresholdPerRLC, RLF_RETX_COUNT is reset to 0 and RLF is not triggered.
[0183] In summary, by using the method provided in the embodiments of this application, the network device can configure a first threshold and a first timer duration for the RLC entity to the UE, so that the UE can determine whether to trigger RLF based on the sum of the number of retransmissions of the SDU transmitted by the RLC entity. This ensures that RLF can still be triggered even when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can normally detect the quality of the radio link.
[0184] The following explains how to implement configuration information that includes a second configuration group.
[0185] Referring to Figure 8, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0186] The method includes the following steps:
[0187] S31: The network device sends first information to the UE. The first information includes a second configuration group, which includes a second threshold, a third threshold, and the duration of a second timer.
[0188] In this embodiment of the application, the first information includes a first configuration group, which is used to configure the second threshold, the third threshold, and the duration of the second timer when the RLC entity is established.
[0189] The second threshold represents the maximum number of SDUs that an RLC entity can trigger an RLF, and is represented by maxnumSDU in this embodiment.
[0190] The third threshold is the minimum number of retransmissions required for a timeout SDU to trigger an RLF. That is, the third threshold is used to filter SDUs; only when the number of retransmissions for a timeout SDU reaches at least the third threshold will that SDU be recorded for triggering an RLF. In this embodiment, the third threshold is represented by obsolete-minRetxThreshold.
[0191] The duration of the second timer is the maximum detection duration of the RLF. In this embodiment, the second timer is denoted as RLFtimer. The second timer starts when the SDU has been submitted to the lower layer and the number of SDU retransmissions is greater than or equal to the third threshold. The second timer RLFtimer stops when the second variable is greater than or equal to the second threshold.
[0192] In this embodiment, the second variable is used to record the number of timeout SDUs that satisfy the third threshold in RLC entity transmission, denoted as RLF_SDU_COUNT. When the second variable is greater than or equal to the second threshold, it is set to zero; when the second timer times out and the second variable has not reached the second threshold, it is also set to zero. The network device configures the UE based on the first information, ensuring that the UE triggers RLF not only based on whether the number of SDU retransmissions has reached the configured maximum number of retransmissions.
[0193] S32: The UE uses the second variable to record the number of timeout SDUs that satisfy the third threshold in the RLC entity transmission.
[0194] In this embodiment of the application, the initial value of the second variable RLF_SDU_COUNT is zero, and the value of the second variable is incremented by 1 whenever the number of retransmissions of a timed-out SDU reaches obsolete-minRetxThreshold.
[0195] In this embodiment, it is no longer necessary to determine whether the number of retransmissions of the SDU has reached the configured maximum number of retransmissions. Instead, the second variable and the second threshold are compared to determine whether to trigger RLF. Since the second variable records the number of timeout SDUs transmitted by the RLC entity that meet the third threshold, the second variable will not fail to trigger RLF because the RLC AM entity supports "avoiding unnecessary retransmissions". Therefore, the reliability of triggering RLF is high.
[0196] S33: The UE triggers an RLF when the second variable is greater than or equal to the second threshold.
[0197] During data transmission, when the PDCP layer receives a PDCP SDU from the upper layer, it starts a discard timer. This discard timer can be either discardTimer or discardTimerForLowImportance; this embodiment does not specify a particular timer. The discard timer is associated with the PDCP SDU.
[0198] The PDCP layer assembles the PDCP SDU into a PDCP PDU and delivers it to the RLC layer. During this process, the timer associated with the PDCP PDU runs continuously.
[0199] When the PDCP layer timer expires, if the associated PDCP SDU has already been submitted to the lower layer, the RLC layer is provided with a discard instruction for the PDCP SDU associated with that timer.
[0200] During data transmission, when the RLC receives a discard instruction for an RLC SDU (PDCP PDU), if the RLC SDU has not been submitted to the lower layer, the RLC discards the SDU; if the RLC SDU has been submitted to the lower layer, and the RETX_COUNT associated with the RLC SDU is greater than or equal to obsolete-minRetxThreshold, the RLFtimer is started if it is not running.
[0201] RETX_COUNT is the count value of the retransmission counter, which records the number of retransmissions of the associated RLC SDU or RLC SDU segment.
[0202] Since a new timeout SDU that satisfies the third threshold has been added, the second variable is updated by incrementing it by 1, i.e., RLF_SDU_COUNT = RLF_SDU_COUNT + 1.
[0203] When the updated RLF_SDU_COUNT is greater than or equal to maxnumSDU, it indicates that the total number of timeout SDUs that meet the third threshold has reached the second threshold. At this time, the upper layer is instructed to trigger RLF, reset RLF_SDU_COUNT to zero, and stop the second timer RLFtimer.
[0204] When the second timer RLFtimer times out and RLF_SDU_COUNT is still less than maxnumSDU, RLF_SDU_COUNT is set to zero.
[0205] In summary, by using the method provided in the embodiments of this application, the network device can configure the second threshold, the third threshold, and the duration of the second timer of the RLC entity to the UE, so that the UE can determine whether to trigger RLF based on the number of SDUs that meet the retransmission number threshold transmitted by the RLC entity, ensuring that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can normally detect the radio link quality.
[0206] The following describes how the configuration information, including the first enabled information, is implemented.
[0207] Referring to Figure 9, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0208] The method includes the following steps:
[0209] S41: The network device sends first information to the UE, the first information including first enable information.
[0210] The first activation message indicates whether to enable retransmission after a high-importance SDU times out.
[0211] In this application embodiment, stopping retransmission after the high-importance SDU times out is a feature. The configuration parameter can be represented by HighImportanceSDUobsoleted. When this feature is enabled (i.e. supported), the state corresponds to enabled; when this feature is disabled (i.e. not supported), the state corresponds to disabled.
[0212] In one possible implementation, the first information may include an indicator field to indicate whether retransmission is enabled after a timeout for a high-importance SDU. For example, the indicator field may include a one-bit binary number; when the binary number is a first value, it indicates that retransmission is enabled; when the binary number is a second value, it indicates that retransmission is disabled. The first value can be 1 and the second value 0, or the first value can be 0 and the second value 1.
[0213] The network device configures the UE based on the first enable information, so that the UE triggers RLF based on whether the number of retransmissions of SDU reaches the configured maximum number of retransmissions. Therefore, it is not affected by the RLC AM entity's support for "avoiding unnecessary retransmissions". In addition, the amount of data transmitted by the first enable information is small and the technical implementation is simple.
[0214] S42: When the PDCP layer receives a PDCP SDU from the upper layer, it sends a PDCP entity based on the importance of the PDCP SDU and associates the corresponding discard timer with the PDCP SDU.
[0215] If the UE is configured with discardTimerForLowImportance and the "SDU discarding based on PDU Set Importance (PSI)" behavior is activated, then the discard timer associated with the PDCP SDU is based on the importance of the PDCP SDU.
[0216] In this embodiment, the existing discard timers discardTimer and discardTimerForLowImportance are associated with the importance of the SDU. Specifically, the first discard timer, discardTimer, is used to associate a corresponding high-importance SDU; the second discard timer, discardTimerForLowImportance, is used to associate a corresponding low-importance SDU.
[0217] If the PDCP SDU belongs to a low-importance PDU Set, then the second discard timer associated with that PDCP SDU is started; otherwise, the first discard timer associated with that PDCP SDU is started.
[0218] S43: When the discard timer associated with the PDCP SDU times out and the PDCP data PDU has been submitted to the lower layer, the PDCP provides the corresponding discard instruction to the lower layer.
[0219] When the first or second discard timer associated with a PDCP SDU expires, if the sending PDCP entity has pdu-SetDiscard configured, it discards all PDCP SDUs belonging to the PDU set to which that PDCP SDU belongs, along with their corresponding PDCP data PDUs. If subsequent PDCP SDUs received from the upper layer belong to that PDU set, they will also be discarded. If the sending PDCP entity has not configured pdu-SetDiscard, it discards both the PDCP SDU and its corresponding PDCP data PDU.
[0220] If the corresponding PDCP data PDU has been submitted to the lower layer, the PDCP instructs the lower layer to discard it. In this embodiment, the discard instruction is associated with the type of the discard timer, that is, with the importance of the SDU, which will be explained in detail below.
[0221] In order to clarify the importance of the SDU corresponding to the discard instruction, the discard instructions provided to the lower layer are different after the first discard timer discardTimer and the second discard timer discardTimerForLowImportance time out.
[0222] The discard indication generated after the first discard timer expires is the first discard indication, which can indicate that the associated SDU is a high-importance SDU; the discard indication generated after the second discard timer expires is the second discard indication, which is associated with a low-importance SDU.
[0223] S44: When the RLC receives the first discard indication of the RLC SDU, and the retransmission stop is not enabled after the high importance SDU times out, determine whether to trigger RLF based on the number of retransmissions of the high importance RLC SDU.
[0224] When an RLC receives a discard instruction for an RLC SDU (PDCP PDU), it first determines whether the discard instruction is the first discard instruction or the second discard instruction.
[0225] If the drop indication is the first drop indication, it indicates that the RLC SDU is a high-importance SDU. In this case, it is further determined whether the high-importance SDU timeout retransmission stop function is enabled. If enabled (i.e., HighImportanceSDUobsoleted enabled), the high-importance RLC SDU already submitted to the lower layer will stop retransmitting, and no further RLF will be triggered. If disabled (i.e., HighImportanceSDUobsoleted disabled), the high-importance RLC SDU already submitted to the lower layer will not stop retransmitting. In this case, it is determined whether the number of retransmissions of the RLC SDU has reached the maximum retransmission threshold of the SDU. If it has, an RLF is triggered. The maximum retransmission threshold of the SDU can be pre-configured by the network device.
[0226] If the drop instruction is the second drop instruction, it indicates that the RLC SDU is a low-importance SDU. At this time, the RLC SDU that has been submitted to the lower layer will stop retransmission and will not trigger RLF again.
[0227] In summary, by using the method provided in the embodiments of this application, the network device can configure first enable information to the UE, so that the UE can determine whether to trigger RLF based on the enable status of "stop retransmission after high importance SDU timeout" and the importance of the timed-out SDU, thereby ensuring that RLF can still be triggered when uplink transmission is unavailable / unreliable, and thus ensuring that the RLC entity can normally detect the radio link quality.
[0228] The following describes how to implement the configuration information, which includes the update information for the maximum retransmission threshold of the SDU.
[0229] Referring to Figure 10, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0230] The method includes the following steps:
[0231] S51: The network device sends the first information to the UE, which includes the update information of the maximum retransmission threshold of the SDU.
[0232] The update information for the maximum retransmission threshold of the SDU is used to determine the update value of the maximum retransmission threshold of the SDU.
[0233] Considering that when the sending end RLC entity is configured with the "avoid unnecessary retransmission function", the number of retransmissions of the timeout SDU may never reach the configured maximum retransmission threshold of the SDU. Therefore, in this embodiment, the updated value of the maximum retransmission threshold of the SDU is generally less than the initial value of the maximum retransmission threshold of the SDU, so that the maximum retransmission threshold of the SDU is reduced after the update, and the number of retransmissions of the SDU can be greater than or equal to the updated maximum retransmission threshold of the SDU, so as to trigger RLF.
[0234] The network device configures the UE based on the update information of the maximum retransmission threshold of the SDU. The impact of this implementation on the UE is that the UE only needs to update the maximum retransmission threshold of the SDU to trigger the RLF normally.
[0235] S52: The UE determines the updated value of the maximum retransmission threshold of the SDU based on the update information of the maximum retransmission threshold of the SDU.
[0236] In one possible implementation, the update information of the maximum retransmission threshold of the SDU includes an update value of the maximum retransmission threshold of at least one SDU, wherein the update value of the maximum retransmission threshold of at least one SDU is less than or equal to the initial value of the maximum retransmission threshold of the SDU.
[0237] For example, the update information for the maximum retransmission threshold of the SDU includes the updated value of the maximum retransmission threshold of the SDU, represented as obsolete-maxRetxThreshold. The initial value of the maximum retransmission threshold of the SDU is represented as maxRetxThreshold. When the RLC entity is established, obsolete-maxRetxThreshold is used as the maximum retransmission threshold of the timeout SDU.
[0238] In another possible implementation, the update information of the SDU's maximum retransmission threshold indicates the mapping relationship between the updated value of the SDU's maximum retransmission threshold and its initial value. This mapping relationship is used to determine the updated value of the SDU's maximum retransmission threshold. This application embodiment does not limit the specific mapping relationship. For example, obsolete-maxRetxThreshold = maxRetxThreshold - N, where N can be a positive integer configured by the network device; or, for another example, obsolete-maxRetxThreshold can be equal to maxRetxThreshold / M, where M can be an integer greater than or equal to 2, and the result of calculating maxRetxThreshold / M can be rounded up or down. The UE uses the determined obsolete-maxRetxThreshold as the maximum retransmission threshold for the timeout SDU.
[0239] S53: The UE determines whether to trigger RLF based on the updated values of the retransmission count of the RLC SDU and the maximum retransmission count threshold of the SDU.
[0240] During data transmission, when the PDCP layer receives a PDCP SDU from the upper layer, it starts a discard timer. This discard timer can be either discardTimer or discardTimerForLowImportance; this embodiment does not specify a particular timer. The discard timer is associated with the PDCP SDU.
[0241] When the RLC receives a discard indication for an RLC SDU (which may also be an RLC SDU segment), it determines the retransmission count RETX_COUNT for the RLC SDU. When RETX_COUNT is greater than or equal to obsolete-maxRetxThreshold, an RLF is triggered.
[0242] When RETX_COUNT is less than obsolete-maxRetxThreshold, it indicates that the RLC SDU (or possibly an RLC SDU segment) has not yet been retransmitted. If a negative acknowledgment is received in this case, and the RETX_COUNT associated with the RLC SDU has not been increased due to another negative acknowledgment in the same STATUS PDU, then RETX_COUNT is increased to complete the update of the retransmission count RETX_COUNT. If the updated retransmission count RETX_COUNT is greater than or equal to obsolete-maxRetxThreshold, it can indicate to the upper layer that the maximum retransmission count has been reached to trigger RLF.
[0243] In summary, by using the method provided in the embodiments of this application, the network device can send update information of the maximum retransmission threshold of the SDU to the UE, so that the UE can determine the updated value of the maximum retransmission threshold of the SDU based on the update information, and then determine whether to trigger RLF based on the updated value, thus ensuring that RLF can still be triggered when uplink transmission is unavailable / unreliable, thereby ensuring that the RLC entity can normally detect the radio link quality.
[0244] RLC-AM helps limit data loss, but its feedback or retransmission triggering mechanism is not well-suited for the short packet delay budgets of XR traffic. To ensure successful transmission of XR packets within a limited time, timely retransmission by the TX is necessary. Currently, there are two enhanced timely retransmission schemes: stateless autonomous retransmission and enhanced polling. Stateless autonomous retransmission means that retransmission is no longer triggered by a status report (SR), and the sender does not need to wait for a status report, thus reducing retransmission latency. Enhanced polling refers to the TX promptly notifying the RX to send a status report, enabling the TX to retransmit faster based on the status report. Therefore, this application provides a communication method that allows the PDCP to provide the RLC with enhanced Poll and / or autonomous retransmission indications for the SDU, which will be described in detail below with reference to the accompanying drawings.
[0245] Referring to Figure 11, this figure is a flowchart of another communication method provided in an embodiment of this application.
[0246] The method includes the following steps:
[0247] S61: The network device sends second information to the UE, the second information including a first trigger threshold and a second trigger threshold.
[0248] The second piece of information is used to configure the timely retransmission enhancement scheme.
[0249] The first trigger threshold is the threshold for triggering the enhanced Poll, which is the minimum remaining time for triggering the enhanced Poll. That is, when the remaining time of the SDU is less than or equal to the first trigger threshold, the enhanced Poll is triggered. In this embodiment, the first trigger threshold is represented by enhancedPollingThreshold.
[0250] The second trigger threshold is the threshold for triggering autonomous retransmission. This threshold is the minimum remaining time for triggering autonomous retransmission; that is, autonomous retransmission is triggered when the remaining time of the SDU is less than or equal to the second trigger threshold. In this embodiment, the second trigger threshold is represented by autonomousReTxThreshold.
[0251] The first trigger threshold and the second trigger threshold can be carried in the same signaling or in different signaling. S61 takes carrying them in the same signaling as an example, but this does not constitute a limitation on the technical solution of this application.
[0252] The first trigger threshold and the second trigger threshold may be the same or different, and this application embodiment does not make specific limitations.
[0253] S62: When the PDCP layer receives a PDCP SDU from the upper layer, it starts the discard timer associated with that PDCP SDU.
[0254] The discard timer can be either discardTimer or discardTimerForLowImportance; this embodiment does not impose a specific limitation. The remaining time of the discard timer is the remaining time of the PDCP SDU.
[0255] S63: When the remaining time of the PDCP SDU is less than or equal to the first trigger threshold, determine whether the associated PDCP Data PDU has been submitted to the lower layer.
[0256] If yes, execute S64; otherwise, execute S65.
[0257] S64: Provides the first indication of the associated PDCP Data PDU to the lower layer.
[0258] The first instruction is used to instruct the RLC entity to include Poll in the Authentication Mode Data AMD PDU.
[0259] S65: When the associated PDCP Data PDU is submitted to the lower layer, provide the lower layer with the first instruction of the associated PDCP Data PDU.
[0260] S66: When the remaining time of the PDCP SDU is less than or equal to the second trigger threshold, determine whether the associated PDCP Data PDU has been submitted to the lower layer.
[0261] If yes, execute S67; otherwise, execute S68.
[0262] S67: Provides a second indication of the associated PDCP Data PDU to the lower layer.
[0263] The second instruction is used to trigger the RLC entity to perform autonomous retransmission.
[0264] S68: When the associated PDCP Data PDU is submitted to the lower layer, provide a second instruction to the associated PDCP Data PDU to the lower layer.
[0265] It is understandable that the second information sent by the network device to the UE may be only one of the first trigger threshold or the second trigger threshold. The principle is similar and will not be elaborated here.
[0266] Using the scheme provided in the embodiments of this application, the RLC can receive the enhanced Poll indication (i.e., the first indication) of the associated RLC SDU provided by the PDCP, and then consider including Poll in a certain AMD PDU; the RLC also receives the autonomous retransmission indication (i.e., the second indication) of the associated RLC SDU provided by the PDCP, and then considers the retransmission of the RLC SDU. Therefore, using this method, the PDCP layer can instruct the RLC to consider the enhanced Poll and autonomous retransmission of data packets, and realize the configuration of the timely retransmission enhancement scheme.
[0267] Furthermore, currently, if an RLC SDU (or RLC SDU segment) is already waiting for retransmission (here, retransmission based on SR, corresponding to the ARQ retransmission mechanism), then autonomous retransmission will not be triggered. However, if an RLC SDU (or RLC SDU segment) is already waiting for retransmission (here, autonomous retransmission based on remaining time), and then TX receives a negative acknowledgment (NACK) for that RLC SDU (or RLC SDU segment), it may lead to duplicate retransmission. The following describes the specific implementation method of this application embodiment to solve the above technical problems.
[0268] In one possible implementation, the processing of autonomous retransmissions does not affect the consideration of SR-based retransmissions.
[0269] In this implementation, when the sender of the AM RLC entity receives a negative acknowledgment of an RLC SDU or RLC SDU segment from the peer AM RLC entity via a STATUS PDU, or receives an autonomous retransmission indication for the corresponding RLC SDU from the PDCP layer (as shown in the second indication in the corresponding description of Figure 11), the sender of the AM RLC entity performs the following steps:
[0270] If the corresponding RLC SDU has been submitted to the lower layer but no acknowledgment ACK has been received, and the RLC SDU or RLC SDU segment is not waiting for retransmission, retransmit the RLC SDU or RLC SDU segment.
[0271] In one possible implementation, the processing of autonomous retransmissions affects consideration of SR-based retransmissions.
[0272] In this implementation, when the sender of the AM RLC entity receives a negative acknowledgment of an RLC SDU or RLC SDU segment from the peer AM RLC entity via a STATUS PDU, or receives an autonomous retransmission indication for the corresponding RLC SDU from the PDCP layer, the sender of the AM RLC entity performs the following steps:
[0273] If the corresponding RLC SDU has been submitted to the lower layer but no acknowledgment ACK has been received, and the RLC SDU or RLC SDU segment is not waiting for retransmission, consider retransmitting the RLC SDU or RLC SDU segment.
[0274] To achieve this implementation, the solution in this application specifically adjusts the buffer of the RLC SDU or RLC SDU segment. In existing solutions, only one retransmission buffer is generally configured, and all RLC SDUs or RLC SDU segments considering retransmission wait for the lower layer to provide a transmission opportunity in the retransmission buffer. When an autonomous retransmission or ARQ retransmission is triggered, the retransmission buffer is traversed to check whether the relevant RLC SDU or RLC SDU segment is waiting for retransmission.
[0275] The solution in this application embodiment includes a first buffer and a second buffer. The first buffer is used to cache the RLC SDU or RLC SDU segment corresponding to ARQ retransmission, meaning that the retransmission buffer in the existing solution can be used to cache the RLC SDU or RLC SDU segment corresponding to ARQ retransmission. The added second buffer is used to cache the RLC SDU or RLC SDU segment corresponding to autonomous retransmission.
[0276] At this point, it can be determined that the RLC SDU or RLC SDU segment is not waiting for retransmission in the following ways:
[0277] When an autonomous retransmission is triggered, the first buffer is traversed to determine whether an RLC SDU or RLC SDU segment is waiting for retransmission.
[0278] When an ARQ retransmission is triggered, the second buffer is traversed to determine whether an RLC SDU or RLC SDU segment is waiting for retransmission.
[0279] It can be observed that by using two buffers to cache the RLC SDU or RLC SDU segments corresponding to different types of retransmissions, the overall number of cached RLC SDU or RLC SDU segments does not increase, but targeted traversal can be performed, reducing traversal overhead and improving efficiency.
[0280] Based on the communication methods provided in the above embodiments, this application also provides a network device, which will be described in detail below with reference to the accompanying drawings.
[0281] Referring to Figure 12, this figure is a schematic diagram of a network device provided in an embodiment of this application.
[0282] Network device 50 includes a processor 51, a communication interface 52, a memory 53, and a bus 54. The number of processor 51, communication interface 52, and memory 53 can be one or more. Processor 51 and memory 53 communicate with each other via bus 54, and network device 50 communicates via communication interface 52.
[0283] Processor 51 may include one or more processing units, such as a modem processor, a baseband processor, etc. Different processing units may be independent devices or integrated into one or more processors. Processor 51 may also include memory for storing instructions and data.
[0284] In one possible implementation, the network device can be a base station, in which case the processor 51 is used to call program instructions in the memory 53 to execute the method steps implemented by the base station side in the above embodiment.
[0285] See Figure 13, which is a schematic diagram of another network device provided in an embodiment of this application.
[0286] Taking a network device as an example, the network device includes a processor 1110, a memory 1120, and a transceiver 1130.
[0287] The processor 1110 is mainly used for baseband processing and controlling the base station; the processor 1110 is usually the control center of the base station, used to control the base station to execute the method steps implemented by the base station side in the above method embodiments.
[0288] The memory section 1120 is mainly used to store computer program code and data.
[0289] The transceiver 1130 section is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals; the transceiver 1130 section is also commonly referred to as a transceiver module, transceiver, transceiver circuit, etc.
[0290] The network device also includes an antenna 1133 and radio frequency (RF) circuitry (not shown in the figure), where the RF circuitry is mainly used for RF processing. Optionally, the device in the transceiver 1130 section used to implement the receiving function can be regarded as a receiver 1032, and the device used to implement the transmitting function can be regarded as a transmitter 1031; that is, the transceiver 1130 includes a receiver 1032 and a transmitter 1031. The receiver 1032 can also be called a receiving module, receiver, or receiving circuit, etc., and the transmitter 1031 can be called a transmitting module, transmitter, or transmitting circuit, etc.
[0291] The processor 1110 section and the memory 1120 section may include one or more circuit boards, each circuit board may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple circuit boards exist, they can be interconnected to enhance processing capabilities. As an optional implementation, multiple circuit boards may share one or more processors, multiple circuit boards may share one or more memories, or multiple circuit boards may simultaneously share one or more processors.
[0292] It should be understood that Figure 13 is merely an example and not a limitation, and the network device described above, including processor 1110, memory 1120 and transceiver 1130, may not depend on the structure shown in Figure 13.
[0293] Based on the communication methods provided in the above embodiments, this application also provides a terminal device.
[0294] Referring to Figure 14, this figure is a schematic diagram of a terminal device provided in an embodiment of this application.
[0295] The terminal device 60 includes a processor 61, a communication interface 62, a memory 63, and a bus 64. The number of processor 61, communication interface 62, and memory 63 can be one or more.
[0296] The processor 61 and memory 63 communicate with each other via bus 64, and the terminal device 60 communicates with the network device via communication interface 62.
[0297] Processor 61 may include one or more processing units, such as a modem processor, a baseband processor, etc. Different processing units may be independent devices or integrated into one or more processors. Processor 61 may also include memory for storing instructions and data.
[0298] The processor 61 is used to call program instructions in the memory 63 to execute the above-described communication method.
[0299] Terminal device 60 can be an XR device, or a mobile phone, tablet computer, computer with wireless transceiver function, VR terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle terminal device, wireless terminal in autonomous driving, wireless terminal in telemedicine, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc.
[0300] Furthermore, embodiments of this application also provide a computer-readable storage medium storing a program, which, when executed by a processor, implements the communication method executed on the network device side or the communication method executed on the terminal device side in the above embodiments.
[0301] This application also provides a communication system that may include the network devices and terminal devices described above.
[0302] Computer-readable storage media include permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically-erasable programmable read-only memory (EEPROM), flash memory, or other memory technologies.
[0303] Specifically, the computer-readable storage medium includes program instructions that instruct an electronic device to perform the above-described method, or instruct a network device to perform the above-described method.
[0304] This application also provides a computer program product containing instructions. The computer program product may be software or program products containing instructions, capable of running on a terminal device or network device, or stored on any usable medium. When the computer program product runs on a terminal device, it causes the terminal device to perform the above-described method; or, when the computer program product runs on a network device, it causes the network device to perform the above-described method.
[0305] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0306] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. A communication method, characterized in that, Applied to terminal devices, including: Receive first information, the first information including configuration information, the configuration information including at least one of the following: a first configuration group, a second configuration group, a first activation information, and update information of the maximum retransmission threshold of the Service Data Unit (SDU); Determine whether to trigger RLF based on the first information; The first configuration group indicates whether to trigger an RLF (Recurrent Link Default) by summing the retransmission counts of SDUs transmitted based on the Radio Link Control (RLC) entity; the second configuration group indicates whether to trigger an RLF by determining the number of SDUs that meet the retransmission count threshold based on the RLC entity transmission; and the first enable information indicates whether to enable the stop retransmission after a high-importance SDU times out.
2. The method according to claim 1, characterized in that, The first configuration group includes: a first threshold and the duration of a first timer; Wherein, the first threshold represents the maximum number of retransmissions that an RLC entity can trigger an RLF; The duration of the first timer is the maximum detection duration of the RLF.
3. The method according to claim 2, characterized in that, The first timer is started when the RLC entity receives a discard instruction for the SDU and the SDU has been delivered to the lower layer; When the first variable is greater than or equal to the first threshold, the first timer stops and the first variable is set to zero; When the first timer times out and the first variable has not reached the first threshold, the first variable is set to zero; The first variable is used to record the sum of the number of retransmissions of the timeout SDU transmitted by the RLC entity.
4. The method according to claim 3, characterized in that, The step of determining whether to trigger an RLF based on the first information specifically includes: RLF is triggered when the first variable is greater than or equal to the first threshold.
5. The method according to claim 1, characterized in that, The second configuration group includes: a second threshold, a third threshold, and the duration of a second timer; The second threshold represents the maximum number of SDUs that an RLC entity can trigger an RLF; The duration of the second timer is the maximum detection duration of the RLF; The third threshold is the minimum number of retransmissions reached by the timeout SDU used to trigger the RLF.
6. The method according to claim 5, characterized in that, The second timer is activated when the SDU has been submitted to the lower layer and the number of retransmissions of the SDU is greater than or equal to the third threshold. When the second variable is greater than or equal to the second threshold, the second timer stops and the second variable is set to zero. The second variable is used to record the number of timeout SDUs that satisfy the third threshold transmitted by the RLC entity. When the second timer times out and the second variable has not reached the second threshold, the second variable is set to zero.
7. The method according to claim 6, characterized in that, The step of determining whether to trigger an RLF based on the first information specifically includes: RLF is triggered when the second variable is greater than or equal to the second threshold.
8. The method according to claim 1, characterized in that, When the RLC entity receives the first discard indication of the SDU, and the first enable information indicates that the retransmission of the high-importance SDU is stopped after the timeout, the SDUs submitted to the lower layer stop retransmission and no RLF is triggered. Otherwise, the SDUs submitted to the lower layer do not stop retransmission, and whether to trigger RLF is determined based on whether the number of retransmissions of the SDU reaches the maximum number of retransmissions threshold of the SDU. When the RLC entity receives the second discard instruction of the SDU, the SDU that has been submitted to the lower layer stops retransmission and does not trigger RLF; The first discard indication is generated after the first discard timer expires, and the first discard timer is associated with a high-importance SDU; the second discard indication is generated after the second discard timer expires, and the second discard timer is associated with a low-importance SDU.
9. The method according to claim 1, characterized in that, The update information of the maximum retransmission threshold of the SDU includes an update value of the maximum retransmission threshold of at least one SDU. The updated value of the maximum retransmission threshold of at least one SDU is less than or equal to the initial value of the maximum retransmission threshold of the SDU.
10. The method according to claim 1, characterized in that, The update information of the maximum retransmission threshold of the SDU indicates the mapping relationship between the updated value of the maximum retransmission threshold of the SDU and the initial value of the maximum retransmission threshold of the SDU. The mapping relationship is used to determine the updated value of the maximum retransmission threshold of the SDU.
11. The method according to claim 9 or 10, characterized in that, The step of determining whether to trigger an RLF based on the first information includes: When the RLC entity receives a discard instruction for the SDU, and the number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU, an RLF is triggered; When the RLC entity receives a discard instruction for the SDU, and the number of retransmissions of the SDU is less than the updated value of the maximum retransmission threshold of the SDU, if a negative acknowledgment is received in the received status report SR, the retransmission count of the SDU is updated. When the updated number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU, an RLF is triggered.
12. The method according to any one of claims 1-11, characterized in that, The method further includes: Receive second information, the second information including a first trigger threshold and / or a second trigger threshold, the first trigger threshold being a threshold for triggering enhanced polling, and the second trigger threshold being a threshold for triggering autonomous retransmission.
13. The method according to claim 12, characterized in that, The second information includes the first trigger threshold, and the method further includes: When the remaining time of the Packet Data Convergence Protocol (PDCP) SDU is less than or equal to the first trigger threshold, if the associated PDCP Data PDU has been submitted to the lower layer, a first indication of the associated PDCP Data PDU is provided to the lower layer; otherwise, when the associated PDCP Data PDU is submitted to the lower layer, a first indication of the associated PDCP Data PDU is provided to the lower layer. The first indication is used to instruct the RLC entity to include Poll in the Acknowledgment Mode Data (AMD) PDU.
14. The method according to claim 12 or 13, characterized in that, The second information includes the second trigger threshold, and the method further includes: When the remaining time of the Packet Data Convergence Protocol (PDCP) SDU is less than or equal to the second trigger threshold, if the associated PDCP Data PDU has been submitted to the lower layer, a second indication of the associated PDCP Data PDU is provided to the lower layer; otherwise, when the associated PDCP Data PDU is submitted to the lower layer, a second indication of the associated PDCP Data PDU is provided to the lower layer. The second indication is used to trigger the RLC entity to perform autonomous retransmission.
15. The method according to any one of claims 1-11, characterized in that, The method further includes: When the sender of an AM RLC entity in acknowledgment mode receives a negative acknowledgment of an RLC SDU or RLC SDU segment from a peer AM RLC entity via a STATUS PDU, or receives an autonomous retransmission indication for a corresponding RLC SDU from the PDCP layer and the RLC SDU or RLC SDU segment is not waiting for retransmission, the sender of the AM RLC entity performs the following steps: If the corresponding RLC SDU has been submitted to the lower layer but no positive ACK has been received, the RLC SDU or RLC SDU segment is retransmitted.
16. The method according to any one of claims 1-11, characterized in that, The method further includes: When the sender of an AM RLC entity in acknowledgment mode receives a negative acknowledgment of an RLC SDU or RLC SDU segment from a peer AM RLC entity via a STATUS PDU, or receives an autonomous retransmission indication for the corresponding RLC SDU from the PDCP layer, the sender of the AM RLC entity performs the following steps: If the corresponding RLC SDU has been submitted to the lower layer but no positive ACK has been received, and the RLC SDU or RLC SDU segment is not waiting for retransmission, the RLC SDU or RLC SDU segment will be retransmitted.
17. The method according to claim 16, characterized in that, The following methods are used to determine that the RLC SDU or RLC SDU segment is not waiting for retransmission: When an automatic retransmission is triggered, the first buffer is traversed to determine whether the RLC SDU or RLC SDU segment is waiting for retransmission. The first buffer is used to cache the RLC SDU or RLC SDU segment corresponding to the automatic retransmission request (ARQ) retransmission. When an ARQ retransmission is triggered, the second buffer is traversed to determine whether the RLC SDU or RLC SDU segment is waiting for retransmission. The second buffer is used to cache the RLC SDU or RLC SDU segment corresponding to the autonomous retransmission.
18. A communication method, characterized in that, Applied to network devices, including: Send first information, the first information including configuration information, the configuration information including at least one of the following: a first configuration group, a second configuration group, a first enable information, and update information of the maximum retransmission threshold of the Service Data Unit (SDU); the first information is used to enable the terminal device to determine whether to trigger RLF; The first configuration group indicates whether to trigger an RLF (Recurrent Link Default) by summing the retransmission counts of SDUs transmitted based on the Radio Link Control (RLC) entity; the second configuration group indicates whether to trigger an RLF by determining the number of SDUs that meet the retransmission count threshold based on the RLC entity transmission; and the first enable information indicates whether to enable the stop retransmission after a high-importance SDU times out.
19. The method according to claim 18, characterized in that, The first configuration group includes: a first threshold and the duration of a first timer; Wherein, the first threshold represents the maximum number of retransmissions that an RLC entity can trigger an RLF; The duration of the first timer is the maximum detection duration of the RLF.
20. The method according to claim 19, characterized in that, The first timer is started when the RLC entity receives a discard instruction for the SDU and the SDU has been delivered to the lower layer; When the first variable is greater than or equal to the first threshold, the first timer stops and the first variable is set to zero; When the first timer times out and the first variable has not reached the first threshold, the first variable is set to zero; The first variable is used to record the sum of the number of retransmissions of the timeout SDU transmitted by the RLC entity.
21. The method according to claim 20, characterized in that, RLF is triggered when the first variable is greater than or equal to the first threshold.
22. The method according to claim 18, characterized in that, The second configuration group includes: a second threshold, a third threshold, and the duration of a second timer; The second threshold represents the maximum number of SDUs that an RLC entity can trigger an RLF; The duration of the second timer is the maximum detection duration of the RLF; The third threshold is the minimum number of retransmissions reached by the timeout SDU used to trigger the RLF.
23. The method according to claim 22, characterized in that, The second timer is activated when the SDU has been submitted to the lower layer and the number of retransmissions of the SDU is greater than or equal to the third threshold. When the second variable is greater than or equal to the second threshold, the second timer stops and the second variable is set to zero. The second variable is used to record the number of timeout SDUs that satisfy the third threshold transmitted by the RLC entity. When the second timer times out and the second variable has not reached the second threshold, the second variable is set to zero.
24. The method according to claim 23, characterized in that, RLF is triggered when the second variable is greater than or equal to the second threshold.
25. The method according to claim 18, characterized in that, If the first activation information indicates that retransmission will stop after the high-importance SDU times out, then when the RLC entity receives the first discard indication of the SDU, the SDU that has been submitted to the lower layer will stop retransmission and will not trigger RLF; If the first enable information indicates that the high-importance SDU will stop retransmission after timeout and will not be enabled, then when the RLC entity receives the first discard indication of the SDU, the SDU that has been submitted to the lower layer will not stop retransmission, and whether to trigger RLF is determined based on whether the number of retransmissions of the SDU reaches the maximum number of retransmissions threshold of the SDU; When the RLC entity receives the second discard instruction of the SDU, the SDU that has been submitted to the lower layer stops retransmission and does not trigger RLF; The first discard indication is generated after the first discard timer expires, and the first discard timer is associated with a high-importance SDU; the second discard indication is generated after the second discard timer expires, and the second discard timer is associated with a low-importance SDU.
26. The method according to claim 18, characterized in that, The update information of the maximum retransmission threshold of the SDU includes an update value of the maximum retransmission threshold of at least one SDU. The updated value of the maximum retransmission threshold of at least one SDU is less than or equal to the initial value of the maximum retransmission threshold of the SDU.
27. The method according to claim 18, characterized in that, The update information of the maximum retransmission threshold of the SDU indicates the mapping relationship between the updated value of the maximum retransmission threshold of the SDU and the initial value of the maximum retransmission threshold of the SDU. The mapping relationship is used to determine the updated value of the maximum retransmission threshold of the SDU.
28. The method according to claim 26 or 27, characterized in that, When the RLC entity receives a discard instruction for the SDU, and the number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU, an RLF is triggered; When the RLC entity receives a discard instruction for the SDU, and the number of retransmissions of the SDU is less than the updated value of the maximum retransmission threshold of the SDU, if a negative acknowledgment is received in the received status report SR, the retransmission count of the SDU is updated. When the updated number of retransmissions of the SDU is greater than or equal to the updated value of the maximum retransmission threshold of the SDU, an RLF is triggered.
29. The method according to any one of claims 18-28, characterized in that, The method further includes: Send a second message, the second message including a first trigger threshold and / or a second trigger threshold, the first trigger threshold being a threshold for triggering enhanced polling, and the second trigger threshold being a threshold for triggering autonomous retransmission.
30. A terminal device, characterized in that, The terminal device includes a processor and a memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is used to execute computer programs or instructions stored in the memory to implement the method as described in any one of claims 1-17.
31. A network device, characterized in that, The network device includes a processor and a memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is configured to execute computer programs or instructions stored in the memory to implement the method as described in any one of claims 18-29.
32. A computer storage medium, characterized in that, The computer storage medium is used to store a computer program, which, when executed, implements the method as described in any one of claims 1-17, or the method as described in any one of claims 18-29.
