Data sending and receiving method and apparatus, and communication system

Abstract

The present application provides a data sending and receiving method and apparatus, and a communication system. The data sending and receiving method comprises: sending an RLC service data unit (RLC SDU) or an RLC SDU segment in an acknowledged mode (AM) to a peer device; and before an RLC status protocol data unit (RLC STATUS PDU) of the peer device is received, performing at least one retransmission of the RLC SDU or the RLC SDU segment.

Description

Data sending and receiving method, device and communication system Technical Field

[0001] The embodiments of the present application relate to the field of wireless communication technology. Background Art

[0002] Extended Reality (XR) services were introduced during the standardization process of the 5th Generation Mobile Communication Technology (5G) within the 3rd Generation Partnership Project (3GPP). XR services refer to human-computer interactions that combine real and virtual environments, computing technologies, and wearable devices. XR services can include virtual reality (VR), augmented reality (AR), and mixed reality (MR). Research on enhancements to XR services began in Release 18.

[0003] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0004] Summary of the Invention

[0005] The inventors have discovered that in order to simultaneously meet the requirements of low delay and high reliability, XR services with a relatively small packet delay budget (PDB) can be sent using the RLC Acknowledged Mode (AM).

[0006] If the RLC acknowledgement mode is used, the RLC layer retransmission is triggered by receiving a status report from the peer device. However, the status report may not be received by the RLC transmitter quickly, which may result in failure to complete the transmission of the XR service within the packet delay budget.

[0007] Furthermore, the retransmission at the RLC layer will occupy radio resources, hinder the sending of new transmissions, and further affect the sending of other service data.

[0008] In order to solve at least one of the above problems or other similar problems, embodiments of the present application provide a data sending and receiving method, device, and communication system.

[0009] According to one aspect of an embodiment of the present application, a data receiving and sending apparatus is provided, which is applied to / configured in a terminal device, and includes:

[0010] a first sending unit, configured to send an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in an Acknowledged Mode (AM) to a peer device;

[0011] The second sending unit is configured to retransmit the RLC service data unit or the RLC service data unit segment N times before receiving the RLC status protocol data unit (RLC STATUS PDU) from the opposite device.

[0012] According to another aspect of an embodiment of the present application, a data receiving and sending device is provided, which is applied to / configured on a peer device of a terminal device, and the device includes:

[0013] a third receiving unit, configured to receive an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in an acknowledged mode (AM) sent by the terminal device;

[0014] A fourth receiving unit is configured to receive N retransmissions of the RLC service data unit or RLC service data unit segment by the terminal device before sending an RLC status protocol data unit (RLC STATUS PDU) to the terminal device.

[0015] According to another aspect of an embodiment of the present application, a data receiving and sending device is provided, which is applied to / configured in a network device, and includes:

[0016] The fifth sending unit is used to send configuration information for configuring RLC retransmission enhancement to the terminal device.

[0017] According to another aspect of an embodiment of the present application, a method for receiving and sending data is provided, which is applied to a terminal device, and the method includes:

[0018] Sending an Acknowledged Mode (AM) RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) to the peer device;

[0019] Before receiving the RLC status protocol data unit (RLC STATUS PDU) of the opposite device, the RLC service data unit or the RLC service data unit segment is retransmitted N times.

[0020] According to another aspect of an embodiment of the present application, a method for receiving and sending data is provided, which is applied to a peer device of a terminal device, the method comprising:

[0021] receiving an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in acknowledged mode (AM) sent by the terminal device;

[0022] Before sending an RLC status protocol data unit (RLC STATUS PDU) to the terminal device, N retransmissions of the RLC service data unit or the RLC service data unit segment by the terminal device are received.

[0023] According to another aspect of an embodiment of the present application, a data receiving and sending method is provided, which is applied to a network device, and the method includes:

[0024] Send configuration information for configuring RLC retransmission enhancement to the terminal device.

[0025] According to another aspect of an embodiment of the present application, a terminal device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the data sending and receiving method on the terminal device side.

[0026] According to another aspect of an embodiment of the present application, a terminal device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the data sending and receiving method on the opposite device side of the above-mentioned terminal device.

[0027] According to another aspect of an embodiment of the present application, a network device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the data sending and receiving method on the opposite device side of the above-mentioned terminal device.

[0028] According to another aspect of an embodiment of the present application, a network device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the data sending and receiving method on the above-mentioned network device side.

[0029] According to another aspect of an embodiment of the present application, a communication system is provided, including:

[0030] A first terminal device, wherein the first terminal device is configured to execute the above-mentioned terminal device side data sending and receiving method;

[0031] a second terminal device, the second terminal device being configured to execute the data sending and receiving method of the terminal device on the opposite-end device side;

[0032] A network device is configured to execute the data sending and receiving method on the opposite device side of the above-mentioned terminal device, or the data sending and receiving method on the network device side.

[0033] The beneficial effects of the embodiments of the present application include:

[0034] After the terminal device sends an RLC service data unit or an RLC service data unit segment to the opposite device, it first retransmits the RLC service data unit or the RLC service data unit segment N times while waiting to receive the RLC status protocol data unit from the opposite device. In this way, the number of RLC retransmissions can be increased within the packet delay budget, thereby improving the transmission reliability of the RLC layer and avoiding affecting the sending of new transmissions.

[0035] With reference to the following description and drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope thereby. Within the scope of the terms of the appended claims, the embodiments of the present application include many variations, modifications, and equivalents.

[0036] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0037] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0039] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0040] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0041] FIG2 is a schematic diagram of a method for sending and receiving data according to an embodiment of the present application;

[0042] FIG3 is a schematic diagram of an embodiment of the present application in which N retransmissions are located in consecutive time slots or symbols;

[0043] FIG4 is a schematic diagram of an embodiment of the present application in which N retransmissions are located in discontinuous time slots or symbols;

[0044] FIG5 is a schematic diagram of an embodiment of the present application in which M retransmissions are located in consecutive time slots or symbols;

[0045] FIG6 is a schematic diagram of an embodiment of the present application in which M retransmissions are located in discontinuous time slots or symbols;

[0046] FIG7 is another schematic diagram of the data sending and receiving method according to an embodiment of the present application;

[0047] FIG8 is another schematic diagram of the data sending and receiving method according to an embodiment of the present application;

[0048] FIG9 is another schematic diagram of the data sending and receiving method according to an embodiment of the present application;

[0049] FIG10 is a schematic diagram of a data receiving and transmitting device according to an embodiment of the present application;

[0050] FIG11 is another schematic diagram of the data receiving and sending device according to an embodiment of the present application;

[0051] FIG12 is another schematic diagram of the data receiving and sending device according to an embodiment of the present application;

[0052] FIG13 is another schematic diagram of the data receiving and sending device according to an embodiment of the present application;

[0053] FIG14 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application;

[0054] FIG15 is a schematic diagram of the structure of the network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0055] The foregoing and other features of the present application will become apparent from the following description with reference to the accompanying drawings. In the description and drawings, specific embodiments of the present application are disclosed, which illustrate some embodiments in which the principles of the present application can be employed. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations, and equivalents falling within the scope of the appended claims. Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application.

[0056] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0057] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0058] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0059] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

[0060] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0061] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0062] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A user equipment may be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0063] Among them, user devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0064] For another example, in scenarios such as the Internet of Things (IoT), the user equipment may also be a machine or device for monitoring or measurement, such as but not limited to: machine type communication (MTC) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, terminals that support sidelink communication, and the like.

[0065] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0066] In the present application, the RLC layer can also be expressed as an RLC entity or a transmitting end of an RLC entity or a receiving end of an RLC entity, and the RLC bearer can also be replaced by an RLC entity or an RLC channel.

[0067] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0068] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101, the first terminal device 102, and the second terminal 103. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low-latency communication (URLLC), and related communications of terminal devices with reduced capabilities, etc.

[0069] It is worth noting that FIG1 shows that the first terminal device 102 and the second terminal device 103 are both within the coverage range of the network device 101, but the present application is not limited thereto. The first terminal device 102 and the second terminal device 103 may both be outside the coverage range of the network device 101, or one of the first terminal device 102 and the second terminal device 103 may be within the coverage range of the network device 101 while the other is outside the coverage range of the network device 101.

[0070] In an embodiment of the present application, a terminal device can send services to and from an opposite-end device. Taking the terminal device as the first terminal device 102 in FIG. 1 as an example, the opposite-end device of the present application can be the network device 101 and / or the second terminal device 103 in FIG. 1 . In actual applications, the opposite-end device can also be other network devices or terminal devices, and the embodiments of the present application are not limited thereto.

[0071] 3GPP agreed to specify enhancements to the user plane in Release 19, including enhancements related to RLC retransmission for RLC Acknowledged Mode (AM) operation with a small packet delay budget (PDB). One of the work objectives is shown in Table 1 below:

[0072] Table 1

[0073] However, there is no clear solution for the details of RLC retransmission enhancements, such as the number of retransmissions, retransmission timing, actions after receiving the RLC status PDU, and configuration of the RLC retransmission enhancements. This may lead to the following problems for XR services with a small packet delay budget (PDB) and using RLC Acknowledged Mode (AM):

[0074] 1) The retransmission at the RLC layer is triggered by a status report received from the peer device. However, this status report may not be received quickly by the RLC transmitter, which may result in the XR service being unable to be sent within the packet delay budget.

[0075] 2) The RLC transmitter will not give up retransmissions. When the maximum number of RLC retransmissions is reached, the RLC layer will notify the upper layer, which will trigger a radio link failure (RLF). If the maximum number of RLC retransmissions is set to a small value due to a small PDB, the RLF can easily be triggered by reaching the maximum number of RLC retransmissions, leading to XR service transmission failure caused by non-radio link quality degradation;

[0076] 3) Retransmission at the RLC layer will occupy radio resources, hinder the sending of new transmissions, and thus affect the sending of other service data.

[0077] Therefore, the details of the RLC retransmission-related enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements, need further discussion.

[0078] In response to at least one of the above problems, embodiments of the present application provide a data receiving and sending method, device, and communication system.

[0079] Embodiments of the first aspect

[0080] An embodiment of the present application provides a method for sending and receiving data, which is described from the perspective of a terminal device.

[0081] FIG2 is a schematic diagram of a method for sending and receiving data according to an embodiment of the present application. The method is applied to a terminal device. As shown in FIG2 , the method includes:

[0082] 201, the terminal device sends an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in Acknowledged Mode (AM) to the peer device;

[0083] 202. Before receiving the RLC status protocol data unit (RLC STATUS PDU) from the opposite device, the terminal device retransmits the RLC service data unit or the RLC service data unit segment at least once.

[0084] According to the above embodiment, after the terminal device sends an RLC service data unit or an RLC service data unit segment to the opposite device, it first retransmits the RLC service data unit or the RLC service data unit segment at least once (for example, N times) while waiting to receive the RLC status protocol data unit of the opposite device. In this way, the number of RLC retransmissions can be increased within the packet delay budget, thereby improving the transmission reliability of the RLC layer and avoiding affecting the sending of new transmissions.

[0085] It is worth noting that FIG2 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG2 above.

[0086] In some embodiments, the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment) sent by the terminal device to the peer device in 201 may be sent by the terminal device through an RLC entity. The functions of the RLC layer are performed by the RLC entity. For each RLC entity configured on the network device (gNB) side, there is a peer RLC entity configured on the UE side, and vice versa. An RLC entity receives RLC SDUs from an upper layer (PDCP layer), or passes RLC SDUs to an upper layer (PDCP layer), sends RLC PDUs to its peer RLC entity via a lower layer (MAC layer), or receives RLC PDUs from its peer RLC entity. If an RLC entity receives RLC SDUs from an upper layer, it receives these RLC SDUs through a single RLC channel between the RLC and upper layers. After forming an RLC data PDU based on the received RLC SDUs, the RLC entity submits the RLC PDUs to the lower layer through a single logical channel. If an RLC entity receives RLC data PDUs from lower layers, it receives these RLC data PDUs through a single logical channel. After forming RLC SDUs from the received RLC data PDUs, the RLC entity delivers these RLC SDUs to the upper layers through a single RLC channel between the RLC and upper layers. An RLC entity can be configured to perform data transfer in one of three modes: Transparent Mode (TM), Unacknowledged Mode (UM), or Acknowledged Mode (AM). An AM RLC entity consists of a transmitter and a receiver.

[0087] In some embodiments, for XR services, the network device configures a PDCP discard timer (discardTimer) value for the terminal device based on the packet delay budget (PDB) of the XR service. In the PDCP layer of the terminal device, when the PDCP discardTimer associated with a PDCP SDU times out, the PDCP layer will discard the PDCP SDU and instruct the RLC layer to discard the RLC SDU associated with the PDCP SDU. In the RLC layer of the terminal device, upon receiving an indication from the PDCP layer to discard an RLC SDU, if the RLC SDU or its segments have not yet been submitted to the lower layer, the transmitting end of the AM RLC entity shall discard the indicated RLC SDU.

[0088] In some embodiments, the opposite-end device includes other terminal devices different from the terminal device that sends the RLC service data unit, or is a network device.

[0089] In some embodiments, when using the RLC acknowledgement mode, after the terminal device sends an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) to the peer device, the peer device will feedback an RLC status protocol data unit (RLC STATUS PDU) to the terminal device. The RLC STATUS PDU includes relevant information for feedback on the RLC SDU or RLC SDU segment, and the relevant information is acknowledgment (ACK) or negative acknowledgment (NACK) information. The ACK indicates that the opposite device has successfully received the RLC SDU or RLC SDU segment; the NACK indicates that the opposite device has not received or has not completely received the RLC SDU or RLC SDU segment. At this time, the terminal device can perform RLC retransmission on the RLC SDU or RLC SDU segment if the retransmission requirements are met. The situation where the retransmission requirements are met is, for example, that the RLC maximum number of retransmissions is not reached and / or the delay exceeds the packet delay budget (PDB) corresponding to the RLC SDU or RLC SDU segment.

[0090] In some embodiments, in 202, before receiving the RLC status protocol data unit (RLC STATUS PDU) of the opposite device, the terminal device performs at least one (e.g., N) RLC retransmissions or repetitions of the RLC service data unit or RLC service data unit segment. Thus, while waiting for the RLC status protocol data unit (RLC STATUS PDU) of the opposite device, the terminal device first spontaneously performs N retransmissions, which can fully utilize the time between sending the RLC SDU or RLC SDU segment and receiving the RLC STATUS PDU, increase the number of RLC retransmissions, and improve the transmission reliability of the RLC layer.

[0091] In some embodiments, the value of N is a positive integer configured by the network or predefined by the terminal device. For example, the network configures the value of N through an RRC message and / or downlink control information (DCI) and / or a medium access control element (MAC Control Element, MAC CE).

[0092] In some embodiments, the N retransmissions are recorded in a retransmission timer (e.g., RETX_COUNT) associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment). The retransmission counter is set by the RLC layer. If an RLC SDU or RLC SDU segment is considered to be retransmitted for the first time, the retransmission counter associated with the RLC SDU is set to 0. For example, if the RLC SDU or RLC SDU segment considered to be retransmitted is not waiting for retransmission and the retransmission counter associated with the RLC SDU has not been increased due to another NACK in the same RLC STATUS PDU, the retransmission counter is increased. When the value of the retransmission counter reaches the RLC maximum number of retransmissions, the RLC layer indicates to the upper layer (RRC layer) that the maximum number of retransmissions has been reached, and the RRC layer will consider that a radio link failure (RLF) has been detected.

[0093] In some embodiments, the N retransmissions are recorded as 1 in the retransmission counter. That is, after the terminal device sends an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in confirmation mode to the peer device, before receiving the RLC status protocol data unit (RLC STATUS PDU) of the peer device, N RLC retransmissions are performed, but in the retransmission counter, these N retransmissions are regarded as 1 retransmission, that is, the retransmission counter is increased by 1, so as to avoid the recorded number of RLC retransmissions reaching the RLC maximum retransmission number too early and triggering a radio link failure, thereby affecting the reliable transmission of XR data of the XR service.

[0094] In some embodiments, the N retransmissions are recorded as N times in the retransmission counter. That is, after the terminal device sends an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in confirmation mode to the opposite device, before receiving the RLC status protocol data unit (RLC STATUS PDU) of the opposite device, N RLC retransmissions are performed, and all these N retransmissions are recorded in the retransmission counter, that is, the retransmission counter increases by N. Accordingly, it is necessary to set the RLC maximum retransmission number to a larger value to avoid the recorded RLC retransmission number reaching the RLC maximum retransmission number too early and triggering a wireless link failure, which affects the reliable transmission of XR data of the XR service.

[0095] In some embodiments, when N retransmissions are recorded in a retransmission counter associated with the RLC service data unit or RLC service data unit segment, the maximum number of RLC retransmissions is greater than the number of RLC retransmissions recorded in the retransmission counter for the N retransmissions. For example, when N retransmissions are recorded as 1 in the retransmission counter, the maximum number of RLC retransmissions should be greater than 1; for another example, when N retransmissions are recorded as N in the retransmission counter, the maximum number of RLC retransmissions should be greater than N. This prevents a radio link failure from being triggered due to reaching the maximum number of RLC retransmissions after N retransmissions.

[0096] In some embodiments, the maximum number of RLC retransmissions is greater than the maximum number of RLC retransmissions in the prior art, for example, when the N retransmissions are recorded in a retransmission counter associated with the RLC service data unit or RLC service data unit segment. The maximum number of RLC retransmissions in the prior art is at most 32, while the maximum number of RLC retransmissions in the present solution may be 64 or more, thereby preventing a radio link failure from being triggered due to the number of retransmissions reaching the maximum number of RLC retransmissions when the N retransmissions are recorded in the retransmission counter.

[0097] In some embodiments, the N retransmissions are not recorded in a retransmission timer associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment). Thus, the N retransmissions performed before receiving the RLC status protocol data unit (RLC STATUS PDU) from the peer device will not cause a change in the value of the retransmission counter, thereby not occupying the opportunity for RLC retransmission and not requiring the RLC maximum number of retransmissions to be set to a larger value. This can prevent the RLC retransmission number from reaching the RLC maximum number of retransmissions too early and triggering a radio link failure, thereby improving the reliability of XR data transmission for the XR service.

[0098] In some embodiments, the N retransmissions are located in consecutive time slots or symbols. For example, FIG3 is a schematic diagram of an embodiment of the present application in which N retransmissions are located in consecutive time slots or symbols. As shown in FIG3 , the terminal device sends at least one RLC SDU or RLC SDU segment in confirmation mode to the opposite device, i.e., RLC TX in FIG3 ; assuming that the value of N is 3, before receiving the RLC STATUS PDU from the opposite device, the terminal device performs three RLC retransmissions on the RLC SDU or RLC SDU segment in three consecutive time slots or symbols after RLC TX, i.e., consecutive RLC ReTX1, RLC ReTX2, and RLC ReTX3 in FIG3 .

[0099] In some embodiments, the N retransmissions are located in discontinuous time slots or symbols. For example, FIG4 is a schematic diagram of an embodiment of the present application in which N retransmissions are located in discontinuous time slots or symbols. As shown in FIG4 , the terminal device sends an RLC SDU or RLC SDU segment in confirmation mode to the opposite device, i.e., RLC TX in FIG4 ; assuming that the value of N is 3, before receiving the RLC STATUS PDU from the opposite device, the terminal device performs three RLC retransmissions on the RLC SDU or RLC SDU segment in three discontinuous time slots or symbols after RLC TX, i.e., the discontinuous RLC ReTX1, RLC ReTX2, and RLC ReTX3 in FIG4 .

[0100] In some embodiments, the N retransmissions are in discontinuous time slots or symbols, including all N retransmissions being in discontinuous time slots or symbols, or some of the N retransmissions being continuous. For example, in FIG3 , RLC ReTX1 and RLC ReTX2 are continuous, while RLC ReTX2 and RLC ReTX3 are discontinuous.

[0101] In some embodiments, whether the N retransmissions are located in continuous time slots or symbols and when the N retransmissions are located in discontinuous time slots or symbols, the intervals of the discontinuous time slots or symbols can be determined in a variety of ways, for example, by a network device configuration, that is, the network device configures the N retransmissions to be located in continuous time slots or symbols, or the network device configures the N retransmissions to be located in discontinuous time slots or symbols and configures the intervals of the discontinuous time slots or symbols; for another example, by a terminal device pre-definition, that is, the terminal device pre-defines the N retransmissions to be located in continuous time slots or symbols, or the terminal device pre-defines the N retransmissions to be located in discontinuous time slots or symbols and the intervals of the discontinuous time slots or symbols; for another example, according to the position of an uplink grant (UL grant) configured or scheduled by the network device, such as a configured uplink grant or an uplink scheduled by DCI. grant, for example, when the position of the uplink grant configured or scheduled by the network device is continuous, the N retransmissions are located in continuous time slots or symbols; when the position of the uplink grant configured or scheduled by the network device is discontinuous, the N retransmissions are located in discontinuous time slots or symbols, and the intervals of the discontinuous time slots or symbols are determined according to the intervals of the positions of the discontinuous uplink grant configured or scheduled by the network device.

[0102] In some embodiments, the interval of the discontinuous time slots or symbols includes the number of time slots or the number of symbols.

[0103] In some embodiments, the intervals between the time slots or symbols of two adjacent retransmissions in N retransmissions may be the same or different. For example, as shown in FIG3 and FIG4 , the interval between RLC ReTX1 and RLC ReTX2 may be the same as or different from the interval between RLC ReTX2 and RLC ReTX3.

[0104] In some embodiments, the time slots or symbols of two adjacent retransmissions in the N retransmissions may be partially consecutive. For example, as shown in FIG3 and FIG4 , RLC ReTX1 and RLC ReTX2 may be located in consecutive time slots or symbols, while RLC ReTX2 and RLC ReTX3 may be separated by one time slot or symbol.

[0105] In some embodiments, the method further comprises:

[0106] The terminal device receives the RLC status protocol data unit sent by the opposite device; and

[0107] Perform RLC retransmission-related operations based on the received RLC status protocol data unit.

[0108] In some embodiments, the RLC status protocol data unit received by the terminal device includes a NACK for the RLC SDU or the RLC SDU segment. In this case, performing operations related to RLC retransmission based on the received RLC status protocol data unit includes:

[0109] The RLC service data unit or the RLC service data unit segment is retransmitted M times.

[0110] In some embodiments, the value of M is a positive integer configured by the network or predefined by the terminal device. For example, the network configures or notifies the value of M through an RRC message and / or downlink control information (DCI) and / or a medium access control element (MAC Control Element, MAC CE).

[0111] In some embodiments, the M retransmissions are recorded in a retransmission timer associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment). The retransmission timer can be found in the above embodiment and will not be repeated here.

[0112] In some embodiments, the M retransmissions are recorded as 1 in the retransmission counter. That is, when the terminal device receives a NACK for the RLC SDU or the RLC SDU segment from the peer device, it performs M RLC retransmissions on the RLC SDU or the RLC SDU segment, but records these M retransmissions as 1 retransmission in the retransmission counter, so as to avoid the recorded number of RLC retransmissions reaching the maximum number of RLC retransmissions too early and triggering a radio link failure, thereby affecting the reliable transmission of XR data of the XR service.

[0113] In some embodiments, the M retransmissions are recorded as M times in the retransmission counter. That is, when the terminal device receives a NACK for the RLC SDU or the RLC SDU segment from the opposite device, it performs M RLC retransmissions on the RLC SDU or the RLC SDU segment, and records all of the M retransmissions in the retransmission counter. Accordingly, the maximum number of RLC retransmissions can be set to a larger value to avoid the recorded number of RLC retransmissions reaching the maximum number of RLC retransmissions too early and triggering a wireless link failure, thereby affecting the reliable transmission of XR data of the XR service.

[0114] In some embodiments, when M retransmissions are recorded in a retransmission counter associated with the RLC service data unit or RLC service data unit segment, the maximum number of RLC retransmissions is greater than or equal to the sum of the number of RLC retransmissions recorded in the retransmission counter for the M retransmissions and the number of RLC retransmissions recorded in the retransmission counter for the N retransmissions. For example, when the M retransmissions are recorded as 1 in the retransmission counter and the N retransmissions are recorded as 1 in the retransmission counter, the maximum number of RLC retransmissions should be greater than or equal to 2. For another example, when the M retransmissions are recorded as M in the retransmission counter and the N retransmissions are recorded as 1 in the retransmission counter, the maximum number of RLC retransmissions should be greater than or equal to M+1. When the N retransmissions are recorded as N in the retransmission counter, the value of the maximum number of RLC retransmissions is similar. This prevents the maximum number of RLC retransmissions from being reached prematurely, thereby triggering a radio link failure.

[0115] In some embodiments, the M retransmissions are located in consecutive time slots or symbols. For example, FIG5 is a schematic diagram of an embodiment of the present application in which M retransmissions are located in consecutive time slots or symbols. As shown in FIG5 , the terminal device sends an RLC SDU or an RLC SDU segment in confirmation mode to the opposite device, i.e., RLC TX in FIG5 , and before receiving the RLC status protocol data unit of the opposite device including NACK for the RLC SDU or the RLC SDU segment, i.e., “RLC STATUS PDU including NACK” in FIG5 , the terminal device performs N=3 RLC retransmissions on the RLC SDU or the RLC SDU segment. After receiving the “RLC STATUS PDU including NACK”, the terminal device performs M=2 RLC retransmissions on the RLC SDU or the RLC SDU segment in two consecutive time slots or symbols, i.e., consecutive RLC ReTX4 and RLC ReTX5 in FIG5 .

[0116] In some embodiments, the M retransmissions are located in discontinuous time slots or symbols. For example, FIG6 is a schematic diagram of an embodiment of the present application in which the M retransmissions are located in discontinuous time slots or symbols. As shown in FIG6 , the terminal device sends an RLC SDU or an RLC SDU segment in confirmation mode to the opposite device, i.e., RLC TX in FIG6 ; and before receiving the RLC status protocol data unit including NACK for the RLC SDU or the RLC SDU segment from the opposite device, i.e., “RLC STATUS PDU including NACK” in FIG6 , the terminal device performs N=3 RLC retransmissions on the RLC SDU or the RLC SDU segment. After receiving the “RLC STATUS PDU including NACK”, the terminal device performs M=2 RLC retransmissions on the RLC SDU or the RLC SDU segment in 2 discontinuous time slots or symbols, i.e., discontinuous RLC ReTX4 and RLC ReTX5 in FIG6 .

[0117] In some embodiments, whether the M retransmissions are located in continuous time slots or symbols and when the M retransmissions are located in discontinuous time slots or symbols, the intervals of the discontinuous time slots or symbols can be determined in a variety of ways, for example, by a network device configuration, that is, the network device configures the M retransmissions to be located in continuous time slots or symbols, or the network device configures the M retransmissions to be located in discontinuous time slots or symbols and configures the intervals of the discontinuous time slots or symbols; for another example, by a terminal device pre-definition, that is, the terminal device pre-defines the M retransmissions to be located in continuous time slots or symbols, or the terminal device pre-defines the M retransmissions to be located in discontinuous time slots or symbols and the intervals of the discontinuous time slots or symbols; for another example, according to an uplink grant (UL) configured or scheduled by the network device. For example, when the position of the uplink grant configured or scheduled by the network device is continuous, the M retransmissions are located in continuous time slots or symbols; when the position of the uplink grant configured or scheduled by the network device is discontinuous, the M retransmissions are located in discontinuous time slots or symbols, and the intervals of the discontinuous time slots or symbols are determined according to the intervals of the positions of the discontinuous uplink grant configured or scheduled by the network device.

[0118] In some embodiments, the interval of the discontinuous time slots or symbols includes the number of time slots or the number of symbols.

[0119] In some embodiments, when the value of M is greater than 2, the intervals between the time slots or symbols of two adjacent retransmissions in the M retransmissions may be the same or different. For example, taking M=3 as an example, assuming that the M retransmissions are represented as RLC ReTX4, RLC ReTX5, and RLC ReTX6, respectively, the interval between RLC ReTX4 and RLC ReTX5 may be the same as or different from the interval between RLC ReTX5 and RLC ReTX6.

[0120] In some embodiments, when the value of M is greater than 2, the time slots or symbols of two adjacent retransmissions in the M retransmissions may be partially consecutive. For example, taking M=3 as an example, assuming that the M retransmissions are represented as RLC ReTX4, RLC ReTX5, and RLC ReTX6, then RLC ReTX4 and RLC ReTX5 may be located in consecutive time slots or symbols, and RLC ReTX5 and RLC ReTX6 are separated by one time slot or symbol.

[0121] In some embodiments, the value of M and the value of N may be the same or different.

[0122] In some embodiments, the N retransmissions and the M retransmissions are both located in consecutive time slots or symbols, or both are located in discontinuous time slots or symbols, or one of them is located in a continuous time slot or symbol and the other is located in a discontinuous time slot or symbol, and this application does not impose any restrictions on this.

[0123] In some embodiments, the method further comprises:

[0124] The terminal device receives an RLC status protocol data unit sent by the opposite device after M retransmissions, where the RLC status protocol data unit includes a NACK for the RLC SDU or the RLC SDU segment; and

[0125] The RLC service data unit or the RLC service data unit segment is retransmitted L times.

[0126] Therefore, when a NACK is received from the peer device after M retransmissions, L retransmissions can be performed autonomously. The value of L can be the same as M or N, or different from both.

[0127] In some embodiments, the RLC status protocol data unit received by the terminal device includes an ACK for the RLC SDU or the RLC SDU segment. In this case, performing operations related to RLC retransmission according to the received RLC status protocol data unit includes:

[0128] Stop RLC retransmission of the RLC SDU or the RLC SDU segment, and / or send an indication of successful delivery of the RLC SDU to an upper layer (eg, a PDCP layer).

[0129] When the ACK for the RLC SDU or the RLC SDU segment is received from the opposite device, it indicates that the opposite device has correctly received the RLC SDU or the RLC SDU segment, and therefore there is no need to retransmit the RLC SDU or the RLC SDU segment.

[0130] In some embodiments, the operation related to RLC retransmission is performed based on the received RLC status protocol data unit, regardless of whether N RLC retransmissions were completed before the terminal device received the RLC status protocol data unit sent by the peer device. For example, when the terminal device receives the RLC status protocol data unit sent by the peer device, it has already performed n RLC retransmissions, where n is a positive integer less than or equal to N. In this case, the terminal device can perform the operation related to RLC retransmission based on the received RLC status protocol data unit without considering whether all N retransmissions are completed.

[0131] In some embodiments, upon receiving an RLC status protocol data unit (RLC STATUS PDU) from the peer device, the terminal device performs n RLC retransmissions, where n is a positive integer less than N. If the RLC status protocol data unit includes acknowledgment (ACK) information for the RLC SDU or the RLC SDU segment, the RLC retransmission is stopped. That is, if an ACK is received from the peer device for the RLC SDU or the RLC SDU segment, even if the number of retransmissions has not reached N, RLC retransmission is discontinued.

[0132] In some embodiments, upon receiving the RLC status protocol data unit (RLC STATUS PDU) from the peer device, the terminal device performs n RLC retransmissions, where n is a positive integer less than N. If the RLC status protocol data unit includes negative acknowledgment (NACK) for the RLC SDU or the RLC SDU segment, operations related to RLC retransmission after receiving the NACK are performed, such as performing "retransmitting the RLC service data unit or the RLC service data unit segment M times" in the above embodiment. That is, if a NACK is received from the peer device for the RLC SDU or the RLC SDU segment, even if the number of retransmissions does not reach N, the remaining (Nn) RLC retransmissions will not be continued, but a new retransmission process will be entered.

[0133] In some embodiments, after performing N retransmissions, the terminal device does not receive the RLC status protocol data unit (RLC STATUS PDU) from the peer device. At this time, the terminal device can wait for the RLC STATUS PDU from the peer device, or autonomously send K RLC retransmissions. The value of K can be the same as M or N, or different from both M and N.

[0134] In some embodiments, after N retransmissions, when the terminal device does not receive the RLC status protocol data unit (RLC STATUS PDU) from the other device within a preset time, it autonomously sends K RLC retransmissions. The value of K can be the same as M or N, or different from both M and N.

[0135] In some embodiments, the preset time is configured by the network device or predefined by the terminal device.

[0136] Through the above embodiments, the data sending and receiving method of the present application describes the enhanced details related to RLC retransmission, such as the number of retransmissions, the timing of retransmissions, and the operations after receiving the RLC status PDU, which helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, and is simple to implement.

[0137] In some embodiments, the method further comprises:

[0138] The terminal device receives configuration information for configuring RLC retransmission enhancement sent by the network device.

[0139] The configuration information is used to configure the number of retransmissions related to RLC retransmission, retransmission timing, operations after receiving the RLC status PDU, etc.

[0140] In some embodiments, the configuration information may be related to or configured for at least one of the following:

[0141] the terminal device;

[0142] A data radio bearer (DRB) of the terminal device;

[0143] The terminal device is configured with a data radio bearer in RLC Acknowledged Mode (RLC AM);

[0144] RLC bearer of the terminal device;

[0145] The terminal device is configured with an RLC bearer in RLC Acknowledged Mode (RLC AM).

[0146] This embodiment describes the objects for configuring RLC retransmission enhancement on a network device, where the network device configures RLC retransmission enhancement for at least one of the terminal device itself, the wireless bearer of the terminal device, the data wireless bearer of the terminal device configured with RLC confirmation mode, the RLC bearer of the terminal device, and the RLC bearer of the terminal device configured with RLC confirmation mode (RLC AM).

[0147] In some embodiments, the configuration information includes at least one of the following information:

[0148] Whether to use RLC retransmission enhancement;

[0149] Using the initiation conditions and / or end conditions and / or duration of RLC retransmission enhancement;

[0150] Number of RLC retransmissions N and / or M;

[0151] Whether RLC retransmissions are in consecutive slots or symbols;

[0152] RLC retransmission related timers;

[0153] RLC retransmission interval.

[0154] This embodiment describes the specific information for configuring RLC retransmission enhancement on a network device.

[0155] In some embodiments, whether RLC retransmission enhancement is used in the configuration information may be indicated by one bit, with different values ​​of the one bit indicating whether RLC retransmission enhancement is used or not. For example, a value of 1 for the one bit indicates that RLC retransmission enhancement is used, a value of 0 for the one bit indicates that RLC retransmission enhancement is not used, and vice versa; or the presence of the one bit indicates that RLC retransmission enhancement is used, and the absence of the one bit indicates that RLC retransmission enhancement is not used, and vice versa.

[0156] In some embodiments, the initiation conditions for using RLC retransmission enhancement in the configuration information are, for example, the first moment t1 before the PDCP discard timer (discardTimer) times out, the time difference between the first moment t1 and the moment t3 when the PDCP discard timer times out is the first time difference T1, or the remaining time corresponding to the logical channel group (LCG) is less than T1, and the first time difference T1 is configured by the network or predefined by the terminal device.

[0157] In some embodiments, the termination condition for using RLC retransmission enhancement in the configuration information is, for example, a second time t2 before the PDCP discard timer (discardTimer) times out, or a time t3 when the PDCP discard timer (discardTimer) times out, or a remaining time corresponding to the logical channel group is 0. The time difference between the second time t2 and the time t3 when the PDCP discard timer times out is a second time difference T2, or the remaining time corresponding to the logical channel group is less than T2, and the second time difference T2 is configured by the network or predefined by the terminal device.

[0158] In some embodiments, the second time t2 is later than the first time t1.

[0159] In some embodiments, the duration of using RLC retransmission enhancement in the configuration information is, for example, the time difference T3 between the time when RLC retransmission enhancement is initiated and the time when RLC retransmission enhancement is terminated. After RLC retransmission enhancement is initiated, RLC retransmission enhancement is terminated after the duration T3 has elapsed.

[0160] In some embodiments, the number of RLC retransmissions N is the number of RLC retransmissions performed after the terminal device sends an Acknowledged Mode (AM) RLC service data unit (RLC SDU) or an RLC service data unit segment to the peer device and before receiving an RLC status protocol data unit (RLC STATUS PDU) from the peer device. The number of RLC retransmissions M is the number of RLC retransmissions performed after the terminal device receives an RLC STATUS PDU from the peer device including the RLC SDU or RLC SDU segment.

[0161] In some embodiments, whether the RLC retransmissions are in consecutive time slots or symbols includes whether the N RLC retransmissions are in consecutive time slots or symbols, and / or whether the M RLC retransmissions are in consecutive time slots or symbols.

[0162] In some embodiments, the interval of the RLC retransmission includes the number of time slots or symbols between two adjacent retransmissions when the N RLC retransmissions are in discontinuous time slots or symbols, and / or the number of time slots or symbols between two adjacent retransmissions when the M RLC retransmissions are in discontinuous time slots or symbols.

[0163] In some embodiments, the RLC retransmission-related timer includes a PDCP discard timer corresponding to an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment).

[0164] In some embodiments, the method further comprises:

[0165] According to the RRC message, the RRC layer of the terminal device configures RLC retransmission enhancement to the RLC layer, or instructs the RLC layer to use RLC retransmission enhancement.

[0166] Therefore, the RRC layer of the terminal device configures RLC retransmission enhancement to the RLC layer according to the configuration information in the RRC message, or instructs the RLC layer to use RLC retransmission enhancement.

[0167] In some embodiments, the configuration information further includes a configuration of an initial state or default state of RLC retransmission enhancement. For example, the initial state or default state of RLC retransmission enhancement includes activation and deactivation. When the initial state or default state of RLC retransmission enhancement is activation, the terminal device uses RLC retransmission enhancement; when the initial state or default state of RLC retransmission enhancement is deactivation, the terminal device does not use RLC retransmission enhancement and uses RLC retransmission enhancement after the RLC retransmission enhancement is activated.

[0168] In some embodiments, the initial state or default state of the RLC retransmission enhancement is associated with or indicated for at least one of the following:

[0169] Terminal device, radio bearer of terminal device, data radio bearer of terminal device configured with RLC acknowledgement mode, RLC bearer of terminal device, RLC bearer of terminal device configured with RLC acknowledgement mode (RLC AM).

[0170] In some embodiments, different values ​​of the initial state or default state indicate whether the initial state or default state of RLC retransmission enhancement is activated or deactivated. For example, the initial state or default state is represented by 1 bit, and different values ​​of the 1 bit indicate whether the initial state or default state of RLC retransmission enhancement is activated, or the initial state or default state of RLC retransmission enhancement is deactivated. For example, the value of the 1 bit is 1, indicating that the initial state or default state of RLC retransmission enhancement is activated, and the value of the 1 bit is 0, indicating that the initial state or default state of RLC retransmission enhancement is deactivated, and vice versa; or whether the initial state or default state appears indicates whether the initial state or default state of RLC retransmission enhancement is activated or deactivated. For example, the initial state or default state is represented by 1 bit, the appearance of the 1 bit indicates that the initial state or default state of RLC retransmission enhancement is activated, and the absence of the 1 bit indicates that the initial state or default state of RLC retransmission enhancement is deactivated, and vice versa.

[0171] In some embodiments, the initial state or default state is represented by a bitmap, and each bit in the bitmap corresponds to the initial state or default state of the RLC retransmission enhancement of a configured data radio bearer DRB of a terminal device or a data radio bearer of a terminal device configured with an RLC confirmation mode or an RLC bearer of a terminal device or an RLC bearer of a terminal device configured with an RLC confirmation mode (RLC AM). The relationship between the value of a bit in the bitmap and the initial state or default state of the RLC retransmission enhancement of a corresponding configured DRB or RLC confirmation mode DRB or RLC bearer or RLC confirmation mode RLC bearer is as described in the above-mentioned embodiment. For example, a value of a bit in the bitmap is 1, which indicates that the initial state or default state of the RLC retransmission enhancement of a corresponding configured DRB or RLC confirmation mode DRB or RLC bearer or RLC confirmation mode RLC bearer is activated, and a value of a bit in the bitmap is 0, which indicates that the initial state or default state of the RLC retransmission enhancement of a corresponding configured DRB or RLC confirmation mode DRB or RLC bearer or RLC confirmation mode RLC bearer is deactivated, and vice versa.

[0172] In some embodiments, the order of the bits in the bitmap corresponding to the initial state or default state of the RLC retransmission enhancement of each configured DRB or RLC confirmation mode or RLC bearer or RLC bearer of RLC confirmation mode is arranged in ascending or descending order according to the configured DRB identifier or DRB identifier of RLC confirmation mode or index or identifier of RLC bearer or index or identifier of RLC bearer of RLC confirmation mode or identifier of logical channel, or the order is configured by the network device.

[0173] In some embodiments, the identifier of the DRB or DRB in RLC confirmation mode is, for example, a data radio bearer identifier (DRB ID), the index or identifier of the RLC bearer or RLC bearer in RLC confirmation mode is, for example, an identifier of the logical channel corresponding to the RLC bearer or an RLC bearer identifier (RLC Bearer ID), and the identifier of the logical channel is a logical channel identifier (Logical Channel Identifier) ​​configured by the network.

[0174] In some embodiments, the configuration information is carried by RRC signaling, for example, the configuration information is included in an RRC message such as an RRC reconfiguration message, an RRC resume message, or an RRC re-establishment message.

[0175] In some embodiments, the method further comprises:

[0176] According to the RRC message, the RRC layer of the terminal device instructs the RLC layer to activate or deactivate RLC retransmission enhancement.

[0177] Therefore, when the configuration information includes the configuration of the initial state or default state of RLC retransmission enhancement, the RRC layer of the terminal device instructs the RLC layer to activate or deactivate the RLC retransmission enhancement based on the configuration of the initial state or default state of the RLC retransmission enhancement in the configuration information in the RRC message, and the RLC layer can activate or deactivate the RLC retransmission enhancement (for the indicated RLC bearer or DRB-related RLC bearer).

[0178] In some embodiments, the method further comprises:

[0179] Receive indication information sent by the network device for indicating the state of RLC retransmission enhancement. For example, the state of RLC retransmission enhancement includes activation and deactivation, and the indication information indicates activation of RLC retransmission enhancement or deactivation of RLC retransmission enhancement.

[0180] In some embodiments, different states of RLC retransmission enhancement are indicated by different values ​​of the indication information, for example, the indication information is 1 bit, and different states of RLC retransmission enhancement are indicated by different values ​​of the 1 bit, for example, the 1 bit value is 1, indicating that the state of RLC retransmission enhancement is activated, the 1 bit value is 0, indicating that the state of RLC retransmission enhancement is deactivated, and vice versa; or different states of RLC retransmission enhancement are indicated by whether the indication information appears, for example, the indication information is 1 bit, the appearance of the 1 bit indicates that the state of RLC retransmission enhancement is activated, the absence of the 1 bit indicates that the state of RLC retransmission enhancement is deactivated, and vice versa.

[0181] In some embodiments, the indication information is a bitmap, and each bit in the bitmap indicates the state of RLC retransmission enhancement of a configured data radio bearer DRB of a terminal device or a data radio bearer configured in RLC confirmation mode of the terminal device or an RLC bearer of the terminal device or an RLC bearer configured in RLC confirmation mode (RLC AM) of the terminal device. The relationship between the value of a bit in the bitmap and the state of RLC retransmission enhancement of a configured DRB or DRB or RLC bearer of RLC confirmation mode or RLC bearer of RLC confirmation mode indicated by it is as described in the above embodiment. For example, a value of 1 in the bitmap indicates that the state of RLC retransmission enhancement of a corresponding configured DRB or DRB or RLC bearer of RLC confirmation mode or RLC bearer of RLC confirmation mode is activated, and a value of 0 in the bitmap indicates that the state of RLC retransmission enhancement of a corresponding configured DRB or DRB or RLC bearer of RLC confirmation mode or RLC bearer of RLC confirmation mode is deactivated, and vice versa.

[0182] In some embodiments, the order of the bits in the bitmap corresponding to the status of RLC retransmission enhancement of each configured DRB or RLC confirmation mode or RLC bearer or RLC bearer of RLC confirmation mode is arranged in ascending or descending order according to the configured DRB identifier or DRB identifier of RLC confirmation mode or index or identifier of RLC bearer or index or identifier of RLC bearer of RLC confirmation mode or identifier of logical channel, or the order is configured by the network device.

[0183] In some embodiments, the indication information is carried by downlink control information (DCI) or media access control element (MAC Control Element, MAC CE) or RLC control protocol data unit (RLC control PDU) or PDCP control protocol data unit (PDCP control PDU).

[0184] In this way, the status of RLC retransmission enhancement of the terminal device or the configured terminal device's radio bearer DRB or the terminal device's data radio bearer configured with RLC confirmation mode or the terminal device's RLC bearer or the terminal device's RLC bearer configured with RLC confirmation mode (RLC AM) can be dynamically indicated, thereby more flexibly applying the RLC retransmission enhancement function.

[0185] In some embodiments, the method further comprises:

[0186] According to the downlink control information or the medium access control element, the physical layer or MAC layer of the terminal device instructs the RLC layer to activate or deactivate RLC retransmission enhancement.

[0187] Therefore, when the indication information is carried by DCI or MAC CE, the physical layer or MAC layer of the terminal device instructs the RLC layer to activate or deactivate RLC retransmission enhancement based on the indication information in the DCI or MAC CE, and the RLC layer can activate or deactivate RLC retransmission enhancement (for the indicated RLC bearer or DRB-related RLC bearer).

[0188] In some embodiments, the method further comprises:

[0189] According to the RLC control protocol data unit, the RLC layer of the terminal device activates or deactivates RLC retransmission enhancement.

[0190] Therefore, when the indication information is carried by the RLC control PDU, the RLC layer of the terminal device activates or deactivates the RLC retransmission enhancement according to the indication information in the RLC control PDU (for the indicated RLC bearer or the DRB-related RLC bearer).

[0191] In some embodiments, the method further comprises:

[0192] According to the PDCP control protocol data unit, the PDCP layer of the terminal device instructs the RLC layer to activate or deactivate RLC retransmission enhancement.

[0193] Therefore, when the indication information is carried by the PDCP control PDU, the PDCP layer of the terminal device instructs the RLC layer to activate or deactivate the RLC retransmission enhancement based on the indication information in the PDCP control PDU, and the RLC layer can activate or deactivate the RLC retransmission enhancement (for the indicated RLC bearer or the DRB-related RLC bearer).

[0194] In some embodiments, the indication information is received when the terminal device receives configuration information for configuring RLC retransmission enhancement sent by the network device, or the indication information is received when the terminal device does not receive configuration information for configuring RLC retransmission enhancement sent by the network device.

[0195] In some embodiments, the method further comprises:

[0196] The terminal device determines to use RLC retransmission enhancement or stop using RLC retransmission enhancement.

[0197] In some embodiments, the terminal device determines to use RLC retransmission enhancement, including: the terminal device performs RLC retransmission enhancement at the first moment before the PDCP discard timer (discardTimer) times out or when the remaining time corresponding to at least one LCG is lower than the first threshold. For example, the moment when the PDCP discard timer times out is t3, and when the first moment t1 before moment t3 arrives, the terminal device uses RLC retransmission enhancement; or when the remaining time corresponding to at least one LCG is lower than the first threshold Th1, the terminal device uses RLC retransmission enhancement. As a result, the terminal device can determine to use RLC retransmission enhancement by itself without relying on the configuration or dynamic indication of the network device. In some embodiments, the terminal device determines to stop using RLC retransmission enhancement, including: the terminal device stops RLC retransmission enhancement when the PDCP discard timer times out or at the second moment before the PDCP discard timer times out or when the remaining time corresponding to at least one LCG is lower than the second threshold or when the remaining time corresponding to at least one LCG is zero. For example, the PDCP discard timer times out at t3. At t3 or a second time t2 before t3, the terminal device stops using RLC retransmission enhancement. Alternatively, when the remaining time corresponding to at least one LCG is less than a second threshold Th2, the terminal device uses RLC retransmission enhancement. Thus, the terminal device can independently determine to stop using RLC retransmission enhancement without relying on the configuration or dynamic indication of the network device. In some embodiments, the second time t2 is later than the first time t1.

[0198] In some embodiments, the first time difference T1 between the first moment t1 and the moment t3 when the PDCP discard timer times out, and / or the second time difference T2 between the second moment t2 and the moment t3 when the PDCP discard timer times out, and / or the first threshold Th1, and / or the second threshold Th2 are configured by the network device or customized by the terminal device.

[0199] In some embodiments, the above-mentioned PDCP discardTimer can be a PDCP discardTimer associated with at least one PDCP SDU, for example, the shortest PDCP discardTimer among the PDCP discardTimers associated with the cached PDCP SDU or the shortest PDCP discardTimer among the PDCP discardTimers associated with the PDCP SDU cached in an LCG; the remaining time corresponding to an LCG can be the shortest remaining value of the PDCP discardTimer associated with the PDCP SDU cached in an LCG.

[0200] In some embodiments, at least one LCG includes a logical channel group in which a logical channel for transmitting an RLC SDU or an RLC SDU segment (or its corresponding RLC PDU) is located, and the LCG includes an LCG configured by a network device, or an LCG configured by a network device that uses (or supports) RLC retransmission enhancement, or an LCG predefined by a terminal device.

[0201] In some embodiments, the PDCP layer of the terminal device instructs the RLC layer to perform RLC retransmission enhancement, or the PDCP layer instructs the RLC layer to stop RLC retransmission enhancement.

[0202] In some embodiments, the PDCP layer of the terminal device determines in the above embodiment to instruct the RLC layer to perform RLC retransmission enhancement or stop RLC retransmission enhancement.

[0203] In some embodiments, the PDCP layer of the terminal device instructs the RLC layer to perform RLC retransmission enhancement on at least one PDCP service data unit (PDCP SDU) and / or PDCP protocol data unit (PDCP PDU) and / or RLC service data unit (RLC SDU) and / or RLC service data unit segment (RLC SDU segment); or, the PDCP layer instructs the RLC layer to stop RLC retransmission enhancement on at least one PDCP service data unit (PDCP SDU) and / or PDCP protocol data unit (PDCP PDU) and / or RLC service data unit (RLC SDU) and / or RLC service data unit segment (RLC SDU segment).

[0204] In some embodiments, RLC retransmission enhancement is performed, including: performing RLC retransmission enhancement on the RLC entity (or DRB) corresponding to at least one configured DRB, or performing RLC retransmission enhancement on the RLC entity (or DRB) corresponding to at least one DRB (or RLC bearer) configured with RLC retransmission enhancement, or performing RLC retransmission enhancement on the RLC entity (or DRB) corresponding to the PDCP SDU associated with the PDCP discardTimer, or performing RLC retransmission enhancement on the RLC entity (or DRB) corresponding to at least one logical channel (Logical channel, LCH) included in the LCG.

[0205] In some embodiments, RLC retransmission enhancement is performed, including: performing RLC retransmission enhancement on at least one RLC SDU or RLC SDU segment in the RLC entity, for example, performing RLC retransmission enhancement on all RLC SDUs or RLC SDU segments in the RLC entity, or performing RLC retransmission enhancement on a portion of the RLC SDUs or RLC SDU segments in the RLC entity, or performing RLC retransmission enhancement on the RLC SDUs or RLC SDU segments indicated by the PDCP layer in the RLC entity.

[0206] In the above embodiment, executing RLC retransmission enhancement may also be expressed as starting RLC retransmission enhancement, or beginning RLC retransmission enhancement, or using RLC retransmission enhancement, or activating RLC retransmission enhancement, etc.

[0207] In some embodiments, stopping RLC retransmission enhancement includes: stopping RLC retransmission enhancement for all RLC entities (or DRBs) corresponding to the configured DRBs, or stopping RLC retransmission enhancement for the RLC entity (or DRB) corresponding to the DRB (or RLC bearer) configured with RLC retransmission enhancement, or stopping RLC retransmission enhancement for the RLC entity (or DRB) corresponding to the PDCP SDU associated with the PDCP discardTimer, or stopping RLC retransmission enhancement for the RLC entity (or DRB) corresponding to at least one LCH included in the LCG.

[0208] In some embodiments, stopping RLC retransmission enhancement includes: stopping RLC retransmission enhancement for at least one RLC SDU or RLC SDU segment in the RLC entity, for example, stopping RLC retransmission enhancement for all RLC SDUs or RLC SDU segments in the RLC entity, or stopping RLC retransmission enhancement for a part of the RLC SDUs or RLC SDU segments in the RLC entity, or stopping RLC retransmission enhancement for the RLC SDUs or RLC SDU segments indicated by the PDCP layer in the RLC entity.

[0209] In the above embodiment, stopping RLC retransmission enhancement may also be expressed as turning off RLC retransmission enhancement, or ending RLC retransmission enhancement, or not using RLC retransmission enhancement, or deactivating RLC retransmission enhancement, etc.

[0210] Through the above embodiments, the data sending and receiving method of the present application illustrates the configuration method of RLC retransmission enhancement, which helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, and is simple to implement.

[0211] It can be seen from the above embodiments that in the data sending and receiving method of the embodiments of the present application, after the terminal device sends an RLC service data unit or an RLC service data unit segment to the opposite device, while waiting to receive the RLC status protocol data unit of the opposite device, the RLC service data unit or the RLC service data unit segment is first retransmitted N times. In this way, the time of waiting for the RLC status protocol data unit of the opposite device can be fully utilized, the number of RLC retransmissions can be increased within the packet delay budget, the transmission reliability of the RLC layer is improved, and the sending of new transmissions is avoided.

[0212] In addition, the details of the RLC retransmission-related enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0213] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0214] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0215] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0216] Embodiments of the second aspect

[0217] An embodiment of the present application provides a method for sending and receiving data, which is described from the perspective of a terminal device.

[0218] FIG7 is another schematic diagram of a method for sending and receiving data according to an embodiment of the present application. The method is applied to a terminal device. As shown in FIG7 , the method includes:

[0219] 701. The terminal device sends information to the network device to indicate whether RLC retransmission enhancement is supported.

[0220] In this way, the network device can know the capabilities of the terminal device related to RLC retransmission enhancement, and thus configure the terminal device with RLC retransmission enhancement consistent with the capabilities of the terminal device, avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0221] In some embodiments, the information is carried by a UE capability information message, an RRC connection establishment complete message, an RRC reconfiguration complete message, or a UE assistance information message.

[0222] In some embodiments, whether the terminal device supports RLC retransmission enhancement is indicated by different values ​​of the information, for example, the information is 1 bit, and the value of the 1 bit is 1, indicating that the terminal device supports RLC retransmission enhancement, and the value of the 1 bit is 0, indicating that the terminal device does not support RLC retransmission enhancement, and vice versa; or whether the terminal device supports RLC retransmission enhancement is indicated by whether the information appears, for example, the information is 1 bit, the appearance of the 1 bit indicates that the terminal device supports RLC retransmission enhancement, and the absence of the 1 bit indicates that the terminal device does not support RLC retransmission enhancement, and vice versa.

[0223] In some embodiments, the information indicates each DRB configured by the terminal device or DRB configured with RLC AM or RLC bearer or RLC AM bearer. For example, for each DRB configured by the terminal device or DRB configured with RLC AM or RLC bearer or RLC AM bearer, the information is 1 bit, and the different values ​​of this 1 bit indicate whether a configured data radio bearer DRB of the terminal device or a data radio bearer configured with RLC confirmation mode of the terminal device or an RLC bearer of the terminal device or an RLC bearer configured with RLC confirmation mode (RLC AM) of the terminal device supports RLC retransmission enhancement. For example, the value of this bit is 1, indicating that a configured data radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device configured with RLC confirmation mode (RLC AM) supports RLC retransmission enhancement; the value of this bit is 0, indicating that a configured data radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device configured with RLC confirmation mode (RLC AM) does not support RLC retransmission enhancement, and vice versa; or the presence of this bit indicates that a configured data radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device supports RLC retransmission enhancement; the absence of this bit indicates that a configured data radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device configured with RLC confirmation mode (RLC AM) RLC bearers that are not connected to AM do not support RLC retransmission enhancement, and vice versa.

[0224] In some embodiments, the information is a bitmap, and each bit in the bitmap indicates whether a data radio bearer DRB of a configured terminal device or a data radio bearer of a terminal device configured with an RLC confirmation mode or an RLC bearer of a terminal device or an RLC bearer of a terminal device configured with an RLC confirmation mode (RLC AM) supports RLC retransmission enhancement. The relationship between the value of a bit in the bitmap and whether a configured DRB or a DRB or RLC bearer of an RLC confirmation mode or an RLC bearer of an RLC confirmation mode indicated by it supports RLC retransmission enhancement is as described in the aforementioned embodiment. For example, a value of 1 in a bit in the bitmap indicates that a corresponding configured DRB or a DRB or RLC bearer of an RLC confirmation mode or an RLC bearer of an RLC confirmation mode supports RLC retransmission enhancement, and a value of 0 in the bitmap indicates that a corresponding configured DRB or a DRB or RLC bearer of an RLC confirmation mode or an RLC bearer of an RLC confirmation mode does not support RLC retransmission enhancement, and vice versa.

[0225] In some embodiments, the order of the bits in the bitmap indicating whether each configured DRB or DRB or RLC bearer of RLC confirmation mode or RLC bearer of RLC confirmation mode supports RLC retransmission enhancement is arranged in ascending or descending order according to the configured DRB identifier or DRB identifier of RLC confirmation mode or index or identifier of RLC bearer or index or identifier of RLC bearer of RLC confirmation mode or identifier of logical channel, or the order is configured by the network device.

[0226] In some embodiments, the method further comprises:

[0227] The terminal device receives configuration information for configuring RLC retransmission enhancement sent by the network device.

[0228] For content related to the configuration information, please refer to the embodiment of the first aspect of this application. The above content is incorporated herein and will not be repeated here.

[0229] Therefore, the details of the RLC retransmission enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0230] Through the above embodiments, the network device can know the capabilities of the terminal device related to RLC retransmission enhancement, so as to configure the terminal device with RLC retransmission enhancement consistent with the capabilities of the terminal device, thereby avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0231] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments or the embodiments of the first aspect of the present application may be combined.

[0232] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0233] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0234] Embodiments of the third aspect

[0235] The present invention provides a method for sending and receiving data, which is described from the perspective of a peer device of a terminal device. The peer device may be a network device or other terminal device, and the following description takes the peer device as an example.

[0236] FIG8 is another schematic diagram of a method for sending and receiving data according to an embodiment of the present application. The method is applied to a network device. As shown in FIG8 , the method includes:

[0237] 801, a network device receives an Acknowledged Mode (AM) RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) sent by a terminal device;

[0238] 802. Before sending an RLC status protocol data unit (RLC STATUS PDU) to the terminal device, the network device receives at least one retransmission of the RLC service data unit or RLC service data unit segment by the terminal device.

[0239] According to the above embodiment, after the network device receives the RLC service data unit or RLC service data unit segment sent by the terminal device, before sending the RLC status protocol data unit to the terminal device, the terminal device first retransmits the RLC service data unit or RLC service data unit segment at least once (for example, N times). In this way, the number of RLC retransmissions can be increased within the packet delay budget, the transmission reliability of the RLC layer can be improved, and the sending of new transmissions can be avoided.

[0240] It is worth noting that FIG8 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG8 above.

[0241] In some embodiments, the implementation and glossary of 801 of this embodiment are similar to the content of 301 of the embodiment of the first aspect of this application. The above related contents are merged here and will not be repeated here.

[0242] In some embodiments, when the RLC confirmation mode is used, after the terminal device sends an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) to the peer device, the peer device will feedback an RLC status protocol data unit (RLC STATUS PDU) to the terminal device. The RLC STATUS PDU includes relevant information for feedback on the RLC SDU or RLC SDU segment, and the relevant information is confirmation information (Acknowledgement, ACK) or negative confirmation (Negative Acknowledgement, NACK) information. The ACK indicates that the peer device has successfully received the RLC SDU or RLC SDU segment; the NACK indicates that the peer device has not received the RLC SDU or RLC SDU segment. At this time, the terminal device can perform RLC retransmission if the retransmission requirements are met. The situation where the retransmission requirements are met is, for example, not reaching the RLC maximum retransmission number and / or the delay exceeds the packet delay budget (PDB) corresponding to the RLC SDU or RLC SDU segment.

[0243] In some embodiments, in 802, before the network device sends an RLC status protocol data unit (RLC STATUS PDU) to the terminal device, it receives at least one (e.g., N) RLC retransmissions or repetitions of the RLC service data unit or RLC service data unit segment. As a result, while waiting for the RLC status protocol data unit (RLC STATUS PDU) from the other device, the terminal device first spontaneously performs N retransmissions, which can fully utilize the time between sending the RLC SDU or RLC SDU segment and receiving the RLC STATUS PDU, increase the number of RLC retransmissions, and improve the transmission reliability of the RLC layer.

[0244] In some embodiments, the value of N is a positive integer configured by the network or predefined by the terminal device. For example, the network configures the value of N through an RRC message and / or downlink control information (DCI) and / or a medium access control element (MAC Control Element, MAC CE).

[0245] In some embodiments, the N retransmissions are recorded in a retransmission timer (e.g., RETX_COUNT) associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment). For details regarding the retransmission timer, see the embodiments of the first aspect of the present application. The above-mentioned relevant contents are incorporated herein and are not repeated here.

[0246] In some embodiments, the N retransmissions are recorded as 1 in the retransmission counter. That is, after the terminal device sends an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in confirmation mode to the peer device, before receiving the RLC status protocol data unit (RLC STATUS PDU) of the peer device, N RLC retransmissions are performed, but in the retransmission counter, these N retransmissions are regarded as 1 retransmission, that is, the retransmission counter is increased by 1, so as to avoid the recorded number of RLC retransmissions reaching the RLC maximum retransmission number too early and triggering a radio link failure, thereby affecting the reliable transmission of XR data of the XR service.

[0247] In some embodiments, the N retransmissions are recorded as N times in the retransmission counter. That is, after the terminal device sends an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in confirmation mode to the opposite device, before receiving the RLC status protocol data unit (RLC STATUS PDU) of the opposite device, N RLC retransmissions are performed, and all these N retransmissions are recorded in the retransmission counter, that is, the retransmission counter increases by N. Accordingly, it is necessary to set the RLC maximum retransmission number to a larger value to avoid the recorded RLC retransmission number reaching the RLC maximum retransmission number too early and triggering a wireless link failure, which affects the reliable transmission of XR data of the XR service.

[0248] In some embodiments, when N retransmissions are recorded in a retransmission counter associated with the RLC service data unit or RLC service data unit segment, the maximum number of RLC retransmissions is greater than the number of RLC retransmissions recorded in the retransmission counter for the N retransmissions. For example, when N retransmissions are recorded as 1 in the retransmission counter, the maximum number of RLC retransmissions should be greater than 1; for another example, when N retransmissions are recorded as N in the retransmission counter, the maximum number of RLC retransmissions should be greater than N. This prevents a radio link failure from being triggered due to reaching the maximum number of RLC retransmissions after N retransmissions.

[0249] In some embodiments, the N retransmissions are not recorded in a retransmission timer associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment). Thus, the N retransmissions performed before receiving the RLC status protocol data unit (RLC STATUS PDU) from the peer device will not cause a change in the value of the retransmission counter, thereby not occupying the opportunity for RLC retransmission and not requiring the RLC maximum number of retransmissions to be set to a larger value. This can prevent the RLC retransmission number from reaching the RLC maximum number of retransmissions too early and triggering a radio link failure, thereby improving the reliability of XR data transmission for the XR service.

[0250] In some embodiments, the N retransmissions are located in consecutive time slots or symbols. For related content, please refer to the embodiment of the first aspect of the present application. The above related content is incorporated herein and will not be repeated here.

[0251] In some embodiments, the N retransmissions are located in discontinuous time slots or symbols. For related content, please refer to the embodiment of the first aspect of the present application. The above related content is incorporated herein and will not be repeated here.

[0252] In some embodiments, the N retransmissions are located in discontinuous time slots or symbols, including all the N retransmissions being located in discontinuous time slots or symbols, or some of the N retransmissions being continuous.

[0253] In some embodiments, whether the N retransmissions are located in continuous time slots or symbols and when the N retransmissions are located in discontinuous time slots or symbols, the intervals of the discontinuous time slots or symbols can be determined in a variety of ways, such as by the network device configuration, and / or predefined by the terminal device, and / or determined according to the position of the uplink grant (UL grant) configured or scheduled by the network device. For related content, please refer to the embodiment of the first aspect of the present application. The above related content is merged here and will not be repeated here.

[0254] In some embodiments, the interval of the discontinuous time slots or symbols includes the number of time slots or the number of symbols.

[0255] In some embodiments, the intervals between the time slots or symbols of two adjacent retransmissions in the N retransmissions may be the same or different.

[0256] In some embodiments, the time slots or symbols in which two adjacent retransmissions in the N retransmissions are located may be partially continuous.

[0257] In some embodiments, the method further comprises:

[0258] The network device sends an RLC status protocol data unit to the terminal device, so that the terminal device performs operations related to RLC retransmission according to the received RLC status protocol data unit.

[0259] In some embodiments, the terminal device performs operations related to RLC retransmission based on the received RLC status protocol data unit. Please refer to the embodiments of the first aspect of the present application. The above related content is incorporated herein and will not be repeated here.

[0260] In some embodiments, the RLC status protocol data unit sent by the network device includes a NACK for the RLC SDU or the RLC SDU segment, or an ACK for the RLC SDU or the RLC SDU segment.

[0261] In some embodiments, when the RLC status protocol data unit sent by the network device includes a NACK for the RLC SDU or the RLC SDU segment, the method further includes:

[0262] The RLC service data unit or the RLC service data unit segment is retransmitted M times.

[0263] In some embodiments, the value of M is a positive integer configured by the network or predefined by the terminal device. For example, the network configures the value of M through an RRC message and / or downlink control information (DCI) and / or a medium access control element (MAC Control Element, MAC CE).

[0264] In some embodiments, the M retransmissions are recorded in a retransmission timer associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment). The retransmission timer can be found in the above embodiment and will not be repeated here.

[0265] In some embodiments, the M retransmissions are recorded as 1 in the retransmission counter. That is, when the terminal device receives a NACK for the RLC SDU or the RLC SDU segment from the peer device, it performs M RLC retransmissions on the RLC SDU or the RLC SDU segment, but records these M retransmissions as 1 retransmission in the retransmission counter, so as to avoid the recorded number of RLC retransmissions reaching the maximum number of RLC retransmissions too early and triggering a radio link failure, thereby affecting the reliable transmission of XR data of the XR service.

[0266] In some embodiments, the M retransmissions are recorded as M times in the retransmission counter. That is, when the terminal device receives a NACK for the RLC SDU or the RLC SDU segment from the opposite device, it performs M RLC retransmissions on the RLC SDU or the RLC SDU segment, and records all of the M retransmissions in the retransmission counter. Accordingly, the maximum number of RLC retransmissions can be set to a larger value to avoid the recorded number of RLC retransmissions reaching the maximum number of RLC retransmissions too early and triggering a wireless link failure, thereby affecting the reliable transmission of XR data of the XR service.

[0267] In some embodiments, when M retransmissions are recorded in a retransmission counter associated with the RLC service data unit or RLC service data unit segment, the maximum number of RLC retransmissions is greater than or equal to the sum of the number of RLC retransmissions recorded in the retransmission counter for the M retransmissions and the number of RLC retransmissions recorded in the retransmission counter for the N retransmissions. For example, when the M retransmissions are recorded as 1 in the retransmission counter and the N retransmissions are recorded as 1 in the retransmission counter, the maximum number of RLC retransmissions should be greater than or equal to 2. For another example, when the M retransmissions are recorded as M in the retransmission counter and the N retransmissions are recorded as 1 in the retransmission counter, the maximum number of RLC retransmissions should be greater than or equal to M+1. When the N retransmissions are recorded as N in the retransmission counter, the value of the maximum number of RLC retransmissions is similar. This prevents the maximum number of RLC retransmissions from being reached prematurely, thereby triggering a radio link failure.

[0268] In some embodiments, the M retransmissions are located in consecutive time slots or symbols, or the M retransmissions are located in discontinuous time slots or symbols. For related content, please refer to the embodiment of the first aspect of the present application. The above related content is merged here and will not be repeated here.

[0269] In some embodiments, whether the M retransmissions are located in continuous time slots or symbols and when the M retransmissions are located in discontinuous time slots or symbols, the intervals of the discontinuous time slots or symbols can be determined in a variety of ways, such as by the network device configuration, and / or predefined by the terminal device, and / or determined according to the position of the uplink grant (UL grant) configured or scheduled by the network device. For related content, please refer to the embodiment of the first aspect of the present application. The above related content is merged here and will not be repeated here.

[0270] In some embodiments, the interval of the discontinuous time slots or symbols includes the number of time slots or the number of symbols.

[0271] In some embodiments, when the value of M is greater than 2, the intervals between the time slots or symbols of two adjacent retransmissions in the M retransmissions may be the same or different.

[0272] In some embodiments, when the value of M is greater than 2, the time slots or symbols in which two adjacent retransmissions in the M retransmissions are located may be partially continuous.

[0273] In some embodiments, the value of M and the value of N may be the same or different.

[0274] In some embodiments, the N retransmissions and the M retransmissions are both located in consecutive time slots or symbols, or both are located in discontinuous time slots or symbols, or one of them is located in a continuous time slot or symbol and the other is located in a discontinuous time slot or symbol, and this application does not impose any restrictions on this.

[0275] In some embodiments, the method further comprises:

[0276] After receiving M retransmissions from the terminal device, the network device sends an RLC status protocol data unit to the terminal device, where the RLC status protocol data unit includes a NACK for the RLC SDU or the RLC SDU segment; and

[0277] Receive L retransmissions of the RLC service data unit or the RLC service data unit segment sent by the terminal device.

[0278] Therefore, when a NACK is received from the peer device after M retransmissions, L retransmissions can be performed autonomously. The value of L can be the same as M or N, or different from both.

[0279] In some embodiments, the method further comprises:

[0280] Configuration information sent by a network device to a terminal device for configuring RLC retransmission enhancement.

[0281] The configuration information is used to configure the number of retransmissions related to RLC retransmission, retransmission timing, operations after receiving the RLC status PDU, etc.

[0282] In some embodiments, the configuration information may be related to or configured for at least one of the following:

[0283] the terminal device;

[0284] A data radio bearer (DRB) of the terminal device;

[0285] The terminal device is configured with a data radio bearer in RLC Acknowledged Mode (RLC AM);

[0286] RLC bearer of the terminal device;

[0287] The terminal device is configured with an RLC bearer in RLC Acknowledged Mode (RLC AM).

[0288] In some embodiments, the configuration information includes at least one of the following information:

[0289] Whether to use RLC retransmission enhancement;

[0290] Using the initiation conditions and / or end conditions and / or duration of RLC retransmission enhancement;

[0291] Number of RLC retransmissions N and / or M;

[0292] Whether RLC retransmissions are in consecutive slots or symbols;

[0293] RLC retransmission related timers;

[0294] RLC retransmission interval.

[0295] In some embodiments, the configuration information further includes configuration of an initial state or a default state of RLC retransmission enhancement. For example, the initial state or the default state of RLC retransmission enhancement includes activation and deactivation.

[0296] In some embodiments, the initial state or default state is represented by 1 bit, and different values ​​of this 1 bit indicate that the initial state or default state of RLC retransmission enhancement is activated, or the initial state or default state of RLC retransmission enhancement is deactivated.

[0297] In some embodiments, the initial state or default state is represented by a bitmap, and each bit in the bitmap corresponds to the initial state or default state of the RLC retransmission enhancement of a configured radio bearer DRB of a terminal device or a data radio bearer of a terminal device configured with an RLC confirmation mode or an RLC bearer of a terminal device or an RLC bearer of a terminal device configured with an RLC confirmation mode (RLC AM).

[0298] In some embodiments, the configuration information is carried by RRC signaling, for example, the configuration information is included in an RRC message such as an RRC connection request message and an RRC connection establishment complete message.

[0299] In some embodiments, the content related to the configuration information can be found in the embodiments of the first aspect of this application. The above content is incorporated herein and will not be repeated here.

[0300] In some embodiments, the method further comprises:

[0301] The network device sends indication information for indicating the state of RLC retransmission enhancement to the terminal device. For example, the state of RLC retransmission enhancement includes activation and deactivation, and the indication information indicates activation of RLC retransmission enhancement or deactivation of RLC retransmission enhancement.

[0302] In some embodiments, the indication information is 1 bit, and different states of RLC retransmission enhancement are indicated by different values ​​of the 1 bit.

[0303] In some embodiments, the indication information is a bitmap, and each bit in the bitmap indicates the status of RLC retransmission enhancement of a configured radio bearer DRB of a terminal device or a data radio bearer of a terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of a terminal device configured with RLC confirmation mode (RLC AM).

[0304] In some embodiments, the indication information is carried by downlink control information (DCI) or media access control element (MAC Control Element, MAC CE) or RLC control protocol data unit (RLC control PDU) or PDCP control protocol data unit (PDCP control PDU).

[0305] In this way, the status of RLC retransmission enhancement of the terminal device or the configured terminal device's radio bearer DRB or the terminal device's data radio bearer configured with RLC confirmation mode or the terminal device's RLC bearer or the terminal device's RLC bearer configured with RLC confirmation mode (RLC AM) can be dynamically indicated, thereby more flexibly applying the RLC retransmission enhancement function.

[0306] In some embodiments, the content related to the indication information can be found in the embodiments of the first aspect of this application. The above content is incorporated herein and will not be repeated here.

[0307] In some embodiments, the method further includes: the network device receiving information from the terminal device indicating whether RLC retransmission enhancement is supported. Thus, the network device can know the terminal device's capabilities related to RLC retransmission enhancement, and thus configure RLC retransmission enhancement for the terminal device consistent with the terminal device's capabilities, thereby avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0308] In some embodiments, the information is carried by a UE capability information message, an RRC connection establishment complete message, or an RRC reconfiguration complete message.

[0309] In some embodiments, the information is 1 bit, and different values ​​of the 1 bit indicate whether the terminal device supports RLC retransmission enhancement.

[0310] In some embodiments, the information is a bitmap, and each bit in the bitmap indicates whether a configured radio bearer DRB of a terminal device or a data radio bearer of a terminal device configured with RLC confirmation mode or an RLC bearer of a terminal device or an RLC bearer of a terminal device configured with RLC confirmation mode (RLC AM) supports RLC retransmission enhancement.

[0311] In some embodiments, the content related to this information can be found in the embodiments of the first aspect of this application. The above content is incorporated herein and will not be repeated here.

[0312] It can be seen from the above embodiments that in the data sending and receiving method of the embodiments of the present application, after the terminal device sends an RLC service data unit or an RLC service data unit segment to the opposite device, while waiting to receive the RLC status protocol data unit of the opposite device, the RLC service data unit or the RLC service data unit segment is first retransmitted N times. In this way, the time of waiting for the RLC status protocol data unit of the opposite device can be fully utilized, the number of RLC retransmissions can be increased within the packet delay budget, the transmission reliability of the RLC layer is improved, and the sending of new transmissions is avoided.

[0313] In addition, the details of the RLC retransmission-related enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0314] The implementation and glossary of this embodiment are similar to those of the embodiment of the first aspect of this application. The above related contents are incorporated herein and will not be repeated here.

[0315] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0316] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0317] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0318] Embodiments of the fourth aspect

[0319] An embodiment of the present application provides a method for sending and receiving data, which is described from the perspective of a network device.

[0320] FIG9 is another schematic diagram of a method for sending and receiving data according to an embodiment of the present application. The method is applied to a network device. As shown in FIG9 , the method includes:

[0321] 901. A network device receives information sent by a terminal device to indicate whether RLC retransmission enhancement is supported.

[0322] In this way, the network device can know the capabilities of the terminal device related to RLC retransmission enhancement, and thus configure the terminal device with RLC retransmission enhancement consistent with the capabilities of the terminal device, avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0323] In some embodiments, the information is carried by a UE capability information message, an RRC connection establishment complete message, an RRC reconfiguration complete message, or a UE assistance information message.

[0324] In some embodiments, different values ​​of this information are used to indicate whether the terminal device supports RLC retransmission enhancement. For example, the information is 1 bit, and a value of 1 for this bit indicates that the terminal device supports RLC retransmission enhancement, and a value of 0 for this bit indicates that the terminal device does not support RLC retransmission enhancement, and vice versa.

[0325] In some embodiments, whether the terminal device supports RLC retransmission enhancement is indicated by whether the information appears. For example, the information is 1 bit, and the presence of the 1 bit indicates that the terminal device supports RLC retransmission enhancement, and the absence of the 1 bit indicates that the terminal device does not support RLC retransmission enhancement, and vice versa.

[0326] In some embodiments, the information indicates each DRB configured by the terminal device or DRB configured with RLC AM or RLC bearer or RLC AM bearer. For example, for each DRB configured by the terminal device or DRB configured with RLC AM or RLC bearer or RLC AM bearer, the information is 1 bit, and the different values ​​of this 1 bit indicate whether a configured data radio bearer DRB of the terminal device or a data radio bearer configured with RLC confirmation mode of the terminal device or an RLC bearer of the terminal device or an RLC bearer configured with RLC confirmation mode (RLC AM) of the terminal device supports RLC retransmission enhancement. For example, the value of this bit is 1, indicating that a configured data radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device configured with RLC confirmation mode (RLC AM) supports RLC retransmission enhancement; the value of this bit is 0, indicating that a configured data radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device configured with RLC confirmation mode (RLC AM) does not support RLC retransmission enhancement, and vice versa; or the presence of this bit indicates that a configured data radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device supports RLC retransmission enhancement; the absence of this bit indicates that a configured radio bearer DRB of the terminal device or a data radio bearer of the terminal device configured with RLC confirmation mode or an RLC bearer of the terminal device or an RLC bearer of the terminal device configured with RLC confirmation mode (RLC AM) RLC bearers that are not connected to AM do not support RLC retransmission enhancement, and vice versa.

[0327] In some embodiments, the information is a bitmap, and each bit in the bitmap indicates whether a configured data radio bearer DRB of a terminal device or a data radio bearer configured with an RLC confirmation mode of the terminal device or an RLC bearer of the terminal device or an RLC bearer configured with an RLC confirmation mode (RLC AM) of the terminal device supports RLC retransmission enhancement. The relationship between the value of a bit in the bitmap and whether a configured DRB or a DRB or RLC bearer of an RLC confirmation mode or an RLC bearer of an RLC confirmation mode indicated by it supports RLC retransmission enhancement is as described in the aforementioned embodiment. For example, a value of 1 in the bitmap indicates that a corresponding configured DRB or a DRB or RLC bearer of an RLC confirmation mode or an RLC bearer of an RLC confirmation mode supports RLC retransmission enhancement, and a value of 0 in the bitmap indicates that a corresponding configured DRB or a DRB or RLC bearer of an RLC confirmation mode or an RLC bearer of an RLC confirmation mode does not support RLC retransmission enhancement, and vice versa.

[0328] In some embodiments, the order of the bits in the bitmap indicating whether each configured DRB or DRB or RLC bearer of RLC confirmation mode or RLC bearer of RLC confirmation mode supports RLC retransmission enhancement is arranged in ascending or descending order according to the configured DRB identifier or DRB identifier of RLC confirmation mode or index or identifier of RLC bearer or index or identifier of RLC bearer of RLC confirmation mode or identifier of logical channel, or the order is configured by the network device.

[0329] In some embodiments, the method further comprises:

[0330] The network device sends configuration information for configuring RLC retransmission enhancement to the terminal device.

[0331] For content related to this configuration information, please refer to the embodiment of the third aspect of this application. The above content is incorporated herein and will not be repeated here.

[0332] Therefore, the details of the RLC retransmission enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0333] Through the above embodiments, the network device can know the capabilities of the terminal device related to RLC retransmission enhancement, and thus configure the terminal device with RLC retransmission enhancement consistent with the capabilities of the terminal device, avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0334] The implementation and glossary of this embodiment are similar to the contents of the embodiment of the second aspect of this application. The above related contents are merged here and will not be repeated here.

[0335] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments or the embodiments of the third aspect of the present application may be combined.

[0336] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0337] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0338] Embodiments of the fifth aspect

[0339] The embodiment of the present application provides a data receiving and sending device, which is applied / configured to a terminal device. The data receiving and sending device and the data receiving and sending method in the embodiment of the first aspect provided by the present application are produced based on the same inventive concept, and the principles of solving the problem are similar. Therefore, the implementation of the data receiving and sending device refers to the implementation of the data receiving and sending method in the embodiment of the first aspect provided by the present application, and the repeated parts are not repeated here. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0340] FIG10 is a schematic diagram of a data sending device according to an embodiment of the present application. As shown in FIG10 , the device includes:

[0341] A first sending unit 1001 is configured to send an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in an Acknowledged Mode (AM) to a peer device;

[0342] The second sending unit 1002 is configured to retransmit the RLC service data unit or the RLC service data unit segment at least once before receiving the RLC status protocol data unit (RLC STATUS PDU) from the opposite device.

[0343] According to the above embodiment, after the terminal device sends an RLC service data unit or an RLC service data unit segment to the opposite device, it first retransmits the RLC service data unit or the RLC service data unit segment at least once (for example, N times) while waiting to receive the RLC status protocol data unit of the opposite device. In this way, the number of RLC retransmissions can be increased within the packet delay budget, thereby improving the transmission reliability of the RLC layer and avoiding affecting the sending of new transmissions.

[0344] In some embodiments, the opposite-end device includes other terminal devices different from the terminal device that sends the RLC service data unit, or is a network device.

[0345] In some embodiments, the RLC STATUS PDU includes relevant information of feedback on the RLC SDU or RLC SDU segment, where the relevant information is Acknowledgement (ACK) information or Negative Acknowledgement (NACK) information.

[0346] In some embodiments, the value of N is a positive integer configured by the network or predefined by the terminal device.

[0347] In some embodiments, the N retransmissions are recorded in a retransmission timer associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment).

[0348] In some embodiments, the N retransmissions are counted as 1 in the retransmission counter; or

[0349] The N retransmissions are recorded as N times in the retransmission counter.

[0350] In some embodiments, the N retransmissions are not recorded in a retransmission timer associated with the RLC service data unit (RLC SDU) or RLC service data unit segment (RLC SDU segment).

[0351] In some embodiments, the N retransmissions are in consecutive time slots or symbols; or

[0352] The N retransmissions are located in discontinuous time slots or symbols.

[0353] In some embodiments, the intervals of the discontinuous time slots or symbols are:

[0354] Network device configuration; and / or

[0355] predefined; and / or

[0356] It is determined according to the location of the uplink grant (UL grant) configured or scheduled by the network device.

[0357] In some embodiments, the apparatus further comprises:

[0358] a fifth receiving unit 1005 (not shown), configured to receive an RLC status protocol data unit sent by the opposite device, wherein the RLC status protocol data unit includes a NACK for the RLC SDU or the RLC SDU segment;

[0359] The seventh sending unit 1006 (not shown) is configured to retransmit the RLC service data unit or the RLC service data unit segment M times.

[0360] In some embodiments, the M retransmissions are recorded in a retransmission counter associated with the RLC service data unit.

[0361] In some embodiments, the M retransmissions are counted as 1 in the retransmission counter; or

[0362] The M retransmissions are recorded as M times in the retransmission counter.

[0363] In some embodiments, the apparatus further comprises:

[0364] The first receiving unit 1003 (not shown) is configured to receive configuration information for configuring RLC retransmission enhancement sent by a network device.

[0365] In some embodiments, the configuration information may be related to or configured for at least one of the following:

[0366] the terminal device;

[0367] a data radio bearer (DRB) of the terminal device;

[0368] a data radio bearer (DRB) configured with RLC acknowledged mode (RLC AM) of the terminal device;

[0369] RLC bearer of the terminal device;

[0370] The terminal device is configured with an RLC bearer in RLC Acknowledged Mode (RLC AM).

[0371] In some embodiments, the configuration information includes at least one of the following:

[0372] Whether to use RLC retransmission enhancement;

[0373] Using the initiation conditions and / or end conditions and / or duration of RLC retransmission enhancement;

[0374] Number of RLC retransmissions N and / or M;

[0375] Whether RLC retransmissions are in consecutive slots or symbols;

[0376] RLC retransmission related timers;

[0377] RLC retransmission interval.

[0378] In some embodiments, the configuration information further includes:

[0379] Configuration of the initial state or default state of RLC retransmission enhancement.

[0380] In some embodiments, the initial state or default state includes activation or deactivation.

[0381] In some embodiments, the initial state or default state is represented by 1 bit; and / or

[0382] The initial state or default state is represented by a bitmap, and each bit in the bitmap corresponds to the initial state or default state of a configured DRB or RLC confirmation mode DRB or RLC bearer or RLC confirmation mode RLC bearer.

[0383] In some embodiments, the configuration information is carried by an RRC message.

[0384] In some embodiments, the apparatus further comprises:

[0385] A first processing unit 1007 (not shown) is configured to configure, by the RRC layer of the terminal device, RLC retransmission enhancement to the RLC layer, or instruct the RLC layer to use RLC retransmission enhancement according to the RRC message; and / or

[0386] According to the RRC message, the RRC layer of the terminal device instructs the RLC layer to activate or deactivate RLC retransmission enhancement.

[0387] In some embodiments, the apparatus further comprises:

[0388] The second receiving unit 1004 (not shown) is configured to receive indication information sent by the network device to indicate a state of RLC retransmission enhancement.

[0389] In some embodiments, the state of the RLC retransmission enhancement includes activation or deactivation.

[0390] In some embodiments, the status of the RLC retransmission enhancement is represented by a bitmap, and each bit in the bitmap corresponds to the status of a configured DRB or DRB in RLC confirmation mode or RLC bearer or RLC bearer in RLC confirmation mode or DRB configured with RLC retransmission enhancement or RLC bearer configured with RLC retransmission enhancement.

[0391] In some embodiments, the indication information is carried by downlink control information (DCI) or medium access control element (MAC CE) or RLC control protocol data unit (RLC control PDU) or PDCP control protocol data unit (PDCP control PDU).

[0392] In some embodiments, the apparatus further comprises:

[0393] A second processing unit 1008 (not shown) is configured to, according to the downlink control information or the medium access control element, instruct the MAC layer of the terminal device to activate or deactivate RLC retransmission enhancement to the RLC layer; or

[0394] According to the RLC control protocol data unit, the RLC layer of the terminal device activates or deactivates RLC retransmission enhancement; or

[0395] According to the PDCP control protocol data unit, the PDCP layer of the terminal device instructs the RLC layer to activate or deactivate RLC retransmission enhancement.

[0396] In some embodiments, the apparatus further comprises:

[0397] a third processing unit 1009 (not shown), configured to perform RLC retransmission enhancement at a first moment before a PDCP discard timer (discardTimer) times out or when a remaining time corresponding to at least one LCG is less than a first threshold; and / or

[0398] When the PDCP discard timer times out or at a second moment before the PDCP discard timer times out or the remaining time corresponding to at least one LCG is lower than a second threshold or the remaining time corresponding to at least one LCG is zero, the RLC retransmission enhancement is stopped.

[0399] In some embodiments, the first time difference between the first moment and the expiration of the PDCP discard timer, and / or the second time difference between the second moment and the expiration of the PDCP discard timer, and / or the first threshold, and / or the second threshold are configured or predefined by the network device.

[0400] In some embodiments, the apparatus further comprises:

[0401] The fourth processing unit 1010 (not shown) is used to enable the PDCP layer of the terminal device to indicate to the RLC layer that the PDCP service data unit (PDCP SDU) and / or PDCP protocol data unit (PDCP PDU) and / or RLC service data unit (RLC SDU) and / or RLC service data unit segment (RLC SDU segment) uses or activates or deactivates RLC retransmission enhancement.

[0402] It can be seen from the above embodiments that in the data sending and receiving method of the embodiments of the present application, after the terminal device sends an RLC service data unit or an RLC service data unit segment to the opposite device, while waiting to receive the RLC status protocol data unit of the opposite device, the RLC service data unit or the RLC service data unit segment is first retransmitted N times. In this way, the time of waiting for the RLC status protocol data unit of the opposite device can be fully utilized, the number of RLC retransmissions can be increased within the packet delay budget, the transmission reliability of the RLC layer is improved, and the sending of new transmissions is avoided.

[0403] In addition, the details of the RLC retransmission-related enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0404] The implementation and glossary of this embodiment are similar to those of the embodiment of the first aspect of this application. The above related contents are incorporated herein and will not be repeated here.

[0405] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0406] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0407] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0408] Embodiments of the sixth aspect

[0409] The embodiment of the present application provides a data receiving and sending device, which is applied / configured to a terminal device. The data receiving and sending device and the data receiving and sending method in the embodiment of the second aspect provided by the present application are produced based on the same inventive concept, and the principles of solving the problem are similar. Therefore, the implementation of the data receiving and sending device refers to the implementation of the data receiving and sending method in the embodiment of the second aspect provided by the present application, and the repeated parts are not repeated here. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0410] FIG11 is a schematic diagram of a data sending device according to an embodiment of the present application. As shown in FIG11 , the device includes:

[0411] The third sending unit 1101 is configured to send information indicating whether RLC retransmission enhancement is supported to the network device.

[0412] In this way, the network device can know the capabilities of the terminal device related to RLC retransmission enhancement, and thus configure the terminal device with RLC retransmission enhancement consistent with the capabilities of the terminal device, avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0413] In some embodiments, the information is carried by a UE capability information message, an RRC connection establishment complete message, an RRC reconfiguration complete message, or a UE assistance information message.

[0414] In some embodiments, the information uses 1 bit to indicate support for RLC retransmission enhancement; and / or

[0415] The information is represented by 1 bit, indicating that RLC retransmission enhancement is supported for a configured DRB or RLC acknowledgement mode DRB or RLC bearer or RLC acknowledgement mode RLC bearer; and / or

[0416] The information is represented by a bitmap, and each bit in the bitmap represents support for RLC retransmission enhancement for a configured DRB or RLC confirmation mode DRB or RLC bearer or RLC confirmation mode RLC bearer.

[0417] In some embodiments, the apparatus further comprises:

[0418] The seventh receiving unit 1102 (not shown) is configured to receive configuration information for configuring RLC retransmission enhancement sent by the network device.

[0419] For content related to the configuration information, please refer to the embodiment of the first aspect of this application. The above content is incorporated herein and will not be repeated here.

[0420] Therefore, the details of the RLC retransmission enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0421] Through the above embodiments, the network device can know the capabilities of the terminal device related to RLC retransmission enhancement, so as to configure the terminal device with RLC retransmission enhancement consistent with the capabilities of the terminal device, thereby avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0422] The implementation and glossary of this embodiment are similar to the contents of the embodiment of the second aspect of this application. The above related contents are merged here and will not be repeated here.

[0423] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments or the embodiments of the first aspect of the present application may be combined.

[0424] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0425] Embodiments of the seventh aspect

[0426] An embodiment of the present application provides a data receiving and sending device, which is applied / configured to a peer device of a terminal device. The peer device may be a network device or other terminal device, and the following description will be made by taking the peer device as an example of a network device. The data receiving and sending device and the data receiving and sending method in the embodiment of the third aspect provided by the present application are based on the same inventive concept and have similar principles for solving problems. Therefore, the implementation of the data receiving and sending device refers to the implementation of the data receiving and sending method in the embodiment of the first aspect provided by the present application, and repeated parts will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements predetermined functions. Although the system described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceived.

[0427] FIG12 is a schematic diagram of a data sending device according to an embodiment of the present application. As shown in FIG12 , the device includes:

[0428] a third receiving unit 1201, configured to receive an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in an acknowledged mode (AM) sent by a terminal device;

[0429] The fourth receiving unit 1202 is configured to receive at least one retransmission of the RLC service data unit or the RLC service data unit segment by the terminal device before sending the RLC status protocol data unit (RLC STATUS PDU) to the terminal device.

[0430] According to the above embodiment, the network device receives the RLC service data unit or RLC service data unit segment sent by the terminal device, and before sending the RLC status protocol data unit to the terminal device, the network device retransmits the RLC service data unit or RLC service data unit segment sent by the terminal device at least once (for example, N times). As a result, the number of RLC retransmissions can be increased within the packet delay budget, the transmission reliability of the RLC layer can be improved, and the sending of new transmissions can be avoided from being affected.

[0431] In some embodiments, the network device includes other terminal devices different from the terminal device that sends the RLC service data unit, or is a network device.

[0432] In some embodiments, for content related to the RLC STATUS PDU, the value of N, whether the N retransmissions are recorded in the Retransmission Timer associated with the RLC SDU or RLC SDU segment, and whether the N retransmissions are located in consecutive time slots or symbols, please refer to the embodiments of the third aspect. The above related content is merged here and will not be repeated here.

[0433] In some embodiments, the apparatus further comprises:

[0434] a fourth sending unit 1203 (not shown), configured to send an RLC status protocol data unit to the terminal device, where the RLC status protocol data unit includes a NACK for the RLC SDU or the RLC SDU segment;

[0435] The sixth receiving unit 1204 (not shown) is configured to receive the RLC service data unit or the RLC service data unit segment and retransmit it M times.

[0436] In some embodiments, for the content related to the value of M, whether M retransmissions are recorded in the Retransmission Timer associated with the RLC SDU or RLC SDU segment, and whether the M retransmissions are located in consecutive time slots or symbols, please refer to the embodiment of the third aspect. The above related content is merged here and will not be repeated here.

[0437] In some embodiments, the apparatus further comprises:

[0438] The fifth sending unit 1205 (not shown) is used to send configuration information for configuring RLC retransmission enhancement to the terminal device.

[0439] In some embodiments, for content related to the configuration information, please refer to the embodiments of the third aspect. The above related content is merged here and will not be repeated here.

[0440] In some embodiments, the apparatus further comprises:

[0441] The sixth sending unit 1206 (not shown) is used to send indication information indicating the state of RLC retransmission enhancement to the terminal device.

[0442] In some embodiments, for content related to the indication information, please refer to the embodiment of the third aspect. The above related content is merged here and will not be repeated here.

[0443] It can be seen from the above embodiments that in the data sending and receiving method of the embodiments of the present application, after the terminal device sends an RLC service data unit or an RLC service data unit segment to the opposite device, while waiting to receive the RLC status protocol data unit of the opposite device, the RLC service data unit or the RLC service data unit segment is first retransmitted at least once (for example, N times). In this way, the time of waiting for the RLC status protocol data unit of the opposite device can be fully utilized, the number of RLC retransmissions can be increased within the packet delay budget, the transmission reliability of the RLC layer is improved, and the sending of new transmissions is avoided.

[0444] In addition, the details of the RLC retransmission-related enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0445] The implementation and glossary of this embodiment are similar to the contents of the embodiment of the third aspect of this application. The above related contents are merged here and will not be repeated here.

[0446] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0447] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0448] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0449] Embodiments of the eighth aspect

[0450] The embodiment of the present application provides a data receiving and sending device, which is applied / configured on the network device side. The data receiving and sending device and the data receiving and sending method in the embodiment of the fourth aspect provided by the present application are produced based on the same inventive concept, and the principles of solving the problem are similar. Therefore, the implementation of the data receiving and sending device refers to the implementation of the data receiving and sending method in the embodiment of the second aspect provided by the present application, and the repeated parts are not repeated here. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0451] FIG13 is a schematic diagram of a data sending device according to an embodiment of the present application. As shown in FIG13 , the device includes:

[0452] The eighth receiving unit 1301 is configured to receive information sent by a terminal device indicating whether RLC retransmission enhancement is supported.

[0453] In this way, the network device can know the capabilities of the terminal device related to RLC retransmission enhancement, and thus configure the terminal device with RLC retransmission enhancement consistent with the capabilities of the terminal device, avoiding incorrect or invalid configuration of RLC retransmission enhancement.

[0454] In some embodiments, for content related to the information, please refer to the embodiments of the fourth aspect. The above related content is merged here and will not be repeated here.

[0455] In some embodiments, the apparatus further comprises:

[0456] The eighth sending unit 1302 (not shown) is used to send configuration information for configuring RLC retransmission enhancement to the terminal device.

[0457] For content related to this configuration information, please refer to the embodiment of the fourth aspect of this application. The above content is incorporated here and will not be repeated here.

[0458] Therefore, the details of the RLC retransmission enhancements, such as the number of retransmissions, the timing of retransmissions, the operations after receiving the RLC status PDU, and the configuration method of the RLC retransmission enhancements are explained. This helps to reliably send XR data to the peer device within the packet delay budget (PDB) of the XR service, simplifies the implementation, and fills the gap in the details related to the RLC retransmission enhancements.

[0459] The implementation and glossary of this embodiment are similar to the contents of the embodiment of the fourth aspect of this application. The above related contents are merged here and will not be repeated here.

[0460] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments or the embodiments of the fourth aspect of the present application may be combined.

[0461] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0462] Embodiments of the ninth aspect

[0463] An embodiment of the present application provides a communication system, which can be referred to in FIG1 . The communication system includes a network device 101 , a first terminal device 102 , and a second terminal device 103 .

[0464] In an embodiment of the present application, the first terminal device 102 is configured to execute the data sending and receiving method in the first aspect and / or second aspect of the present application, the contents of which are incorporated herein and will not be repeated here.

[0465] In an embodiment of the present application, the second terminal device 103 is configured to execute the data sending and receiving method in the third aspect of the present application, the content of which is incorporated herein and will not be repeated here.

[0466] In an embodiment of the present application, the network device 101 is configured to execute the data sending and receiving method in the third aspect and / or fourth aspect of the present application, the contents of which are incorporated herein and will not be repeated here.

[0467] Embodiments of the tenth aspect

[0468] An embodiment of the present application provides a terminal device.

[0469] Figure 14 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application, which may be a remote terminal device. As shown in Figure 14 , terminal device 1400 may include a processor 1401 and a memory 1402. Memory 1402 stores data and programs and is coupled to processor 1401. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0470] For example, the processor 1401 may be configured to execute a program to implement the data sending and receiving method as described in the embodiment of the first aspect. For example, the processor 1401 may be configured to perform the following operations: sending an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in Acknowledged Mode (AM) to a peer device; and retransmitting the RLC service data unit or RLC service data unit segment at least once before receiving an RLC status protocol data unit (RLC STATUS PDU) from the peer device.

[0471] For another example, the processor 1401 may be configured to execute a program to implement the data sending and receiving method as described in the embodiment of the second aspect. For example, the processor 1401 may be configured to perform the following operations: sending information indicating whether RLC retransmission enhancement is supported to the network device.

[0472] For another example, the processor 1401 may be configured to execute a program to implement the data sending and receiving method as described in the embodiment of the third aspect. For example, the processor 1401 may be configured to perform the following operations: receiving an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in acknowledged mode (AM) sent by the terminal device; and before sending an RLC status protocol data unit (RLC STATUS PDU) to the terminal device, receiving at least one retransmission of the RLC service data unit or the RLC service data unit segment by the terminal device.

[0473] As shown in Figure 14 , the terminal device 1400 may further include: a communication module 1403, an input unit 1404, a display 1405, and a power supply 1406. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1400 does not necessarily include all of the components shown in Figure 14 , and these components are not essential. Furthermore, the terminal device 1400 may also include components not shown in Figure 14 , for which reference may be made to related art.

[0474] An embodiment of the present application provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0475] Figure 15 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 15 , network device 1500 may include a processor 1510 (e.g., a central processing unit (CPU)) and a memory 1520; memory 1520 is coupled to processor 1510. Memory 1520 may store various data and may also store an information processing program 1530, which is executed under the control of processor 1510.

[0476] For example, the processor 1510 may be configured to execute a program to implement the data sending and receiving method as described in the embodiment of the third aspect. For example, the processor 1510 may be configured to perform the following control: receiving an RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) in acknowledged mode (AM) sent by the terminal device; and before sending an RLC status protocol data unit (RLC STATUS PDU) to the terminal device, receiving at least one retransmission of the RLC service data unit or the RLC service data unit segment by the terminal device.

[0477] For example, the processor 1510 may be configured to execute a program to implement the data sending and receiving method as described in the embodiment of the fourth aspect. For example, the processor 1510 may be configured to perform the following control: receiving information sent by the terminal device to indicate whether RLC retransmission enhancement is supported.

[0478] In addition, as shown in FIG15 , network device 1500 may further include: a transceiver 1540 and an antenna 1550, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1500 does not necessarily include all the components shown in FIG15 ; in addition, network device 1500 may also include components not shown in FIG15 , and reference may be made to the prior art for details.

[0479] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program enables the computer to execute the data sending and receiving method described in the first aspect and / or second aspect and / or third aspect of the embodiment of the present application in the terminal device.

[0480] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the data sending and receiving method described in the first aspect and / or second aspect and / or third aspect of the present application in a terminal device.

[0481] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a network device, the program enables the computer to execute the data sending and receiving method described in the third aspect and / or fourth aspect of the present application in the network device.

[0482] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the data sending and receiving method described in the third aspect and / or fourth aspect of the present application in a network device.

[0483] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0484] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0485] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0486] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0487] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0488] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0489] 1. A data sending and receiving method, applied to a terminal device, comprising:

[0490] Sending an Acknowledged Mode (AM) RLC service data unit (RLC SDU) or an RLC service data unit segment (RLC SDU segment) to the peer device;

[0491] Before receiving the RLC status protocol data unit (RLC STATUS PDU) of the opposite device, the RLC service data unit or the RLC service data unit segment is retransmitted at least once.

[0492] 2. The method according to Note 1, wherein the value of N is a network-configured or predefined positive integer.

[0493] 3. The method according to Supplementary Note 1, wherein the method further comprises:

[0494] receiving an RLC status protocol data unit sent by the opposite device, where the RLC status protocol data unit includes a NACK for the RLC SDU or the RLC SDU segment;

[0495] The RLC service data unit or the RLC service data unit segment is retransmitted M times.

[0496] 4. The method according to Supplementary Note 1, further comprising:

[0497] receiving configuration information for configuring RLC retransmission enhancement sent by a network device;

[0498] Furthermore, the configuration information includes:

[0499] Configuration of the initial state or default state of RLC retransmission enhancement.

[0500] 5. The method according to Note 4, wherein the initial state or default state includes activation or deactivation.

[0501] 6. The method according to Note 4, wherein the initial state or default state is represented by 1 bit; and / or

[0502] The initial state or default state is represented by a bitmap, and each bit in the bitmap corresponds to the initial state or default state of a configured DRB or RLC confirmation mode DRB or RLC bearer or RLC confirmation mode RLC bearer.

[0503] 7. The method according to Note 4, wherein the configuration information is carried by an RRC message.

[0504] 8. The method according to Supplementary Note 7, wherein the method further comprises:

[0505] According to the RRC message, the RRC layer of the terminal device configures RLC retransmission enhancement to the RLC layer, or instructs the RLC layer to use RLC retransmission enhancement; and / or

[0506] According to the RRC message, the RRC layer of the terminal device instructs the RLC layer to activate or deactivate RLC retransmission enhancement.

[0507] 9. The method according to Supplementary Note 1, wherein the method further comprises:

[0508] Perform RLC retransmission enhancement at the first moment before the PDCP discard timer (discardTimer) times out or when the remaining time corresponding to at least one logical channel group is lower than a first threshold; and / or

[0509] The RLC retransmission enhancement is stopped when the PDCP discard timer times out or at a second moment before the PDCP discard timer times out or the remaining time corresponding to at least one logical channel group is lower than the second threshold or the remaining time corresponding to at least one logical channel group is zero.

[0510] 10. The method according to Supplementary Note 9, wherein:

[0511] The first time difference between the first moment and the expiration of the PDCP discard timer, and / or the second time difference between the second moment and the expiration of the PDCP discard timer and / or the first threshold and / or the second threshold are configured or predefined by the network device.

Claims

1. A data sending and receiving device, applied to a terminal device, the device comprising: A first sending unit, which is used to send a Radio Link Control (RLC) Service Data Unit (SDU) or an RLC SDU segment in Acknowledged Mode (AM) to a peer device; A second sending unit, which is used to retransmit the RLC SDU or the RLC SDU segment N times before receiving the RLC Status Protocol Data Unit (RLC STATUS PDU) of the peer device.

2. The device according to claim 1, wherein, The RLC STATUS PDU includes relevant information on the feedback of the RLC SDU or the RLC SDU segment, and the relevant information is Acknowledgement (ACK) or Negative Acknowledgement (NACK) information.

3. The device according to claim 1, wherein The N retransmissions are recorded in a retransmission counter associated with the RLC SDU or the RLC SDU segment.

4. The device according to claim 3, wherein The N retransmissions are recorded as 1 time in the retransmission counter; or The N retransmissions are recorded as N times in the retransmission counter.

5. The device according to claim 1, wherein The N retransmissions are not recorded in a retransmission counter associated with the RLC SDU or the RLC SDU segment.

6. The device according to claim 1, wherein The N retransmissions are located in consecutive time slots or symbols; or The N retransmissions are located in non - consecutive time slots or symbols.

7. The apparatus according to claim 6, wherein, The interval of the non - consecutive time slots or symbols is: Configured by a network device; and / or Pre - defined; and / or Determined according to the position of an uplink grant configured or scheduled by the network device.

8. The apparatus according to claim 1, wherein, The device further comprises: A first receiving unit, which is used to receive configuration information sent by a network device for configuring RLC retransmission enhancement.

9. The device according to claim 8, wherein, The configuration information is related to or configured for at least one of the following: The terminal device; The data radio bearer (DRB) of the terminal device; The DRB of the terminal device configured with RLC Acknowledged Mode (RLC AM); The RLC bearer of the terminal device; The RLC bearer of the terminal device configured with RLC AM.

10. The apparatus according to claim 8, wherein, The configuration information includes at least one of the following: Whether to use RLC retransmission enhancement; The initiation condition and / or end condition and / or duration of using RLC retransmission enhancement; The number of RLC retransmissions N and / or M; Whether RLC retransmissions are in consecutive time slots or symbols; Timers related to RLC retransmissions; The interval of RLC retransmissions.

11. The device according to claim 1, wherein, The device further comprises: A second receiving unit, which is configured to receive indication information sent by the network device for indicating the status of RLC retransmission enhancement.

12. The apparatus according to claim 11, wherein, The status of the RLC retransmission enhancement includes activation or deactivation.

13. The device according to claim 12, wherein, The status of the RLC retransmission enhancement is represented by a bitmap, and each bit in the bitmap correspondingly represents the status of RLC retransmission enhancement of a configured DRB or a DRB in RLC acknowledged mode or an RLC bearer or an RLC bearer in RLC acknowledged mode or a DRB configured with RLC retransmission enhancement or an RLC bearer configured with RLC retransmission enhancement.

14. The apparatus according to claim 11, wherein, The indication information is carried by a downlink control information (DCI) or a media access control control element (MAC CE) or an RLC control protocol data unit (RLC control PDU) or a PDCP control protocol data unit (PDCP control PDU).

15. The device according to claim 1, wherein, The apparatus further includes: A third processing unit, which is configured to perform RLC retransmission enhancement at a first moment before the PDCP discard timer (discardTimer) expires or when the remaining time corresponding to at least one logical channel group is lower than a first threshold; and / or Stop RLC retransmission enhancement when the PDCP discard timer expires or at a second moment before the PDCP discard timer expires or when the remaining time corresponding to at least one logical channel group is lower than a second threshold or when the remaining time corresponding to at least one logical channel group is zero.

16. The device according to claim 1, wherein, The apparatus further includes: A third sending unit, which is configured to send information to the network device for indicating whether RLC retransmission enhancement is supported.

17. The apparatus according to claim 16, wherein, The information is carried by a UE capability information message or an RRC connection establishment complete message or an RRC reconfiguration complete message or a UE assistance information message.

18. The apparatus according to claim 16, wherein, The information uses 1 bit to indicate support for RLC retransmission enhancement; and / or The information uses 1 bit to indicate support for RLC retransmission enhancement for a configured DRB or a DRB in RLC acknowledged mode or an RLC bearer or an RLC bearer in RLC acknowledged mode; and / or The information is represented by a bitmap, and each bit in the bitmap represents support for RLC retransmission enhancement for a configured DRB or a DRB in RLC acknowledged mode or an RLC bearer or an RLC bearer in RLC acknowledged mode.

19. A data sending and receiving apparatus, applied to the peer device of a terminal device, the apparatus includes: A third receiving unit, which is configured to receive an RLC service data unit (RLC SDU) or an RLC service data unit segment in acknowledged mode (AM) sent by the terminal device; A fourth receiving unit, which is configured to receive N retransmissions of the RLC service data unit or the RLC service data unit segment by the terminal device before sending an RLC status protocol data unit (RLC STATUS PDU) to the terminal device.

20. A data sending and receiving device is applied to a network device. The device includes: An eighth receiving unit, configured to receive information sent by a terminal device for indicating whether RLC retransmission enhancement is supported.

Images