Fast rlc configuration update

Abstract

Various embodiments described herein relate to devices and methods capable of fast RLC configuration updates. One such example embodiment relates to a communication system comprising configuring or reconfiguring a parameter related to radio link control, RLC, status report triggering at a receiver entity, the parameter comprising a threshold value to trigger a RLC status report of a maximum value of RLC protocol data units, PDUs, received by the receiver entity.

Description

Technical Field

[0001] The various example embodiments described herein relate to devices and methods for implementing rapid RLC configuration updates. abbreviation

[0002] NR New Radio

[0003] RAN (Radio Access Network)

[0004] L2 Floor 2

[0005] UP User Plane

[0006] SDAP Service Data Adaptation Protocol

[0007] PDCP (Packet Data Convergence Protocol)

[0008] RLC Radio Link Control

[0009] MAC Media Access Control

[0010] RRC Radio Resource Control

[0011] MAC CE MAC control element

[0012] PDU Protocol Data Unit

[0013] TM Transparent Mode

[0014] UM Unconfirmed Mode

[0015] AM Confirmation Mode

[0016] QoS (Quality of Service)

[0017] SN serial number

[0018] UE User Equipment

[0019] gNB Next Generation Node B

[0020] ACK_SN Confirmation Serial Number

[0021] LCID (Logical Channel Identifier)

[0022] NACK (Negative Acknowledgment)

[0023] DL downlink

[0024] UP uplink Background Technology

[0025] 5G NR L2 UP consists of different protocol layers: SDAP, PDCP, RLC, and MAC. RRC configuration is used to configure various parameters at different layers (such as PDCP and RLC layers). This process ensures efficient data transmission and management within the RAN.

[0026] Taking RLC as an example, the configured parameters may include, for example:

[0027] • RLC mode: Operates in TM, UM or AM mode based on service requirements.

[0028] • PDU size: Adjust the PDU size based on network conditions and QoS requirements.

[0029] • Buffering and retransmission: Manage data buffering and retransmission strategies to achieve reliable transmission.

[0030] • Window size: Maintains send and receive windows to manage data flow.

[0031] • Buffer size and reordering: Ensure packets are delivered in the correct order.

[0032] RRC messages can be used to update RLC parameters (such as changes in RLC mode, PDU size, and window size). Summary of the Invention

[0033] The various exemplary embodiments disclosed in this subject are intended to address at least some of the issues and / or problems and disadvantages that are explicitly described herein or otherwise apparent to those skilled in the art, in order to provide methods, apparatus, and computer program products for efficiently (re)configuring / updating RLC layer parameters to achieve optimal system behavior.

[0034] Various aspects of the various example embodiments will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of the various example embodiments, nor are they intended to be used to otherwise limit the scope of this subject matter disclosure. In view of the subject matter disclosure, other features, aspects, and elements of the various example embodiments will be apparent to those skilled in the art.

[0035] According to the first aspect, a communication method is provided, comprising:

[0036] Configure or reconfigure parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold that indicates the maximum value of RLC Protocol Data Units (PDUs) received by the receiver entity to trigger an RLC status report.

[0037] According to the second aspect, a communication method is provided, including:

[0038] Configure or reconfigure parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold that indicates the maximum time elapsed since the RLC PDU was received by the receiver entity to trigger an RLC status report.

[0039] According to a third aspect, a communication device is provided, comprising:

[0040] At least one processor; and

[0041] At least one memory stores instructions that, when executed by at least one processor, cause the communication device to configure or reconfigure parameters related to the triggering of a Radio Link Control (RLC) Status Report at a receiver entity, including a threshold indicating the maximum value of an RLC Protocol Data Unit (PDU) received by the receiver entity to trigger the RLC Status Report.

[0042] According to the fourth aspect, a communication device is provided, comprising:

[0043] At least one processor; and

[0044] At least one memory, storing instructions that, when executed by the at least one processor, cause the communication device to configure or reconfigure parameters related to the triggering of a radio link control (RLC) status report at the receiver entity, including a threshold indicating the maximum value of time elapsed since the RLC PDU was received by the receiver entity to trigger the RLC status report.

[0045] According to the fifth aspect, a communication device is provided, comprising:

[0046] A component for configuring or reconfiguring parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold indicating the maximum value of RLC Protocol Data Units (PDUs) received by the receiver entity to trigger an RLC status report.

[0047] According to a sixth aspect, a communication device is provided, comprising:

[0048] A component for configuring or reconfiguring parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold indicating the maximum time elapsed since the RLCPDU was received by the receiver entity to trigger an RLC status report.

[0049] According to a seventh aspect, a computer program and instruction set are provided, which, when executed on a device, are configured to cause the device to perform the method according to the first or second aspect.

[0050] According to some example embodiments, at least one of the following advantages can be achieved:

[0051] • Reduced signaling overhead;

[0052] • Improved resource efficiency;

[0053] • A robust mechanism for triggering RLC status reports by the receiver entity itself;

[0054] • Optimize protocol behavior. Attached Figure Description

[0055] Further details, features, objects, and advantages will be apparent from the following detailed description of preferred exemplary embodiments, taken in conjunction with the accompanying drawings, wherein:

[0056] Figure 1 This is a block diagram illustrating a communication device according to an example embodiment;

[0057] Figure 2 This is a schematic diagram of a communication method according to an example embodiment;

[0058] Figure 3 This is a block diagram illustrating a communication device according to an example embodiment;

[0059] Figure 4 This is a schematic diagram of a communication method according to an example embodiment;

[0060] Figure 5 This is a block diagram illustrating a communication device according to an example embodiment;

[0061] Figure 6 This is a schematic diagram of a communication method according to an example embodiment;

[0062] Figure 7 This is a block diagram illustrating a communication device according to an example embodiment;

[0063] Figure 8 This is a schematic diagram of a communication method according to an example embodiment;

[0064] Figure 9 This is a block diagram illustrating a communication device according to an example embodiment;

[0065] Figure 10 This is a schematic diagram of a communication method according to an example embodiment;

[0066] Figure 11 This is a block diagram illustrating a communication device according to an example embodiment;

[0067] Figure 12 This is a schematic diagram of a communication method according to an example embodiment;

[0068] Figure 13 This is a schematic diagram illustrating a MAC CE according to an example embodiment;

[0069] Figure 14 This is a schematic diagram illustrating a MAC CE according to an example embodiment;

[0070] Figure 15 This is a schematic diagram illustrating a MAC CE according to an example embodiment;

[0071] Figure 16 This is a schematic diagram illustrating a MAC CE according to an example embodiment;

[0072] Figure 17 This is a schematic diagram of a method according to an example embodiment;

[0073] Figure 18 This is a schematic diagram of a method according to an example embodiment;

[0074] Figure 19 This is a schematic diagram of a method according to an example embodiment;

[0075] Figure 20 This is a schematic diagram of a method according to an example embodiment;

[0076] Figure 21 This is a schematic diagram of a method according to an example embodiment;

[0077] Figure 22 This is a schematic diagram of a method according to an example embodiment;

[0078] Figure 23 This is a schematic diagram illustrating an RLC status report according to an example embodiment;

[0079] Figure 24 This is a schematic diagram illustrating an RLC status report according to an example embodiment;

[0080] Figure 25 This is an alternative block diagram illustrating a communication device according to an example embodiment; and

[0081] Figure 26 This is an alternative block diagram illustrating a communication device according to an example embodiment.

[0082] Figure 27 This is an alternative block diagram illustrating a communication device according to an example embodiment; and

[0083] Figure 28 This is an alternative block diagram illustrating a communication device according to an example embodiment.

[0084] Figure 29 This is an alternative block diagram illustrating a communication device according to an example embodiment; and

[0085] Figure 30 This is an alternative block diagram illustrating a communication device according to an example embodiment. Detailed Implementation

[0086] The 5G NR UP configuration process is characterized by its ability to configure and dynamically update parameters through the RRC reconfiguration procedure. Protocol behavior changes dynamically depending on several factors, such as explicit dynamic (de)activation based on protocol functions (PDCP replication, adaptive QoS, etc.) and dynamic signaling conditions. In all these dynamic scenarios, the same configuration at the protocol layer may not be optimal.

[0087] Given the dynamically activatable PDCP replication, up to four copies of the same PDCP PDU can be sent, depending on the configuration. Depending on the corresponding lower-layer behavior (e.g., flow control algorithms (buffer capacity, network congestion, authorization, etc.)), all transport copies do not need to be sent by PDCP to the lower layer (RLC) simultaneously.

[0088] When the first copy of the PDCP PDU is successfully received by the receiver entity before the transmitter sends other remaining duplicate copies, the transmitter does not need to continue sending other copies of the same PDCP PDU.

[0089] This unwanted replication of the PDCP PDU can only be avoided if feedback (e.g., via RLC status report) is received from the receiver entity before replication is triggered at the transmitter PDCP entity.

[0090] The following problems may occur:

[0091] • Problem 1: Excessively long status report intervals

[0092] After dynamically activating PDCP replication, the time interval between triggering RLC state PDUs and before PDCP replication activation may not be optimal, and vice versa. A longer period of time before triggering RLC state reports may cause the transmitter to perform unwanted replications on packets that have already been successfully received.

[0093] Therefore, it is necessary to dynamically reconfigure the parameters that trigger the RLC status report.

[0094] • Question 2: Insufficient state information

[0095] RLC status reports are constrained to only transmit PDU statuses (ACK_SN in the RLC status report is set with RX_HIGHEST_STATUS) until a SN with RX_HIGHEST_STATUS is held. That is, even if an RLC SN greater than RX_HIGHEST_STATUS is successfully received, the receiver RLC entity cannot update the status of these SNs. Therefore, even successful reception of such RLC status reports cannot prevent duplicate packets with SN >= ACK_SN, even if these packets are successfully received at the receiver entity.

[0096] • Question 3: Missing trigger / Trigger not initiated

[0097] Currently, there are two triggers for RLC status reporting. One trigger is when the polling bit is set in the RLCPDU by the transmitter, while the other trigger is when the t-recombination timer expires.

[0098] However, the t-reassembly timer only starts when a lost RLC packet is detected at the receiver RLC entity. If no lost RLC complete PDU or RLC PDU segment is found, or if all lost packets are received before the t-reassembly timer expires, the t-reassembly timer is not started / stopped at the receiver. This means that an RLC status report will not be triggered. Even if an RLC status report is triggered based on the timer's expiration, the frequency / wait time depends on the t-reassembly timer value.

[0099] Furthermore, in the event that an RLC PDU containing polling bits is lost in the air (not successfully received), the triggering of the RLC status PDU is delayed.

[0100] Therefore, a robust mechanism is needed to trigger RLC status reports by the receiver entity itself.

[0101] In summary, when a system does not function optimally, it is necessary to effectively and dynamically (re)configure / update the RLC layer parameters, including the status reporting mechanism. For example, the system may not function optimally when the PDCP replication mechanism is dynamically activated / deactivated.

[0102] Other scenarios exist, such as when RLC layer parameters need to be dynamically updated. Another example scenario is AI / ML-based operations, where the UE can predict and report the optimal t-recombination timer to improve latency while managing wasted channel resources.

[0103] In the following detailed description with reference to the accompanying drawings, certain exemplary embodiments are described, wherein features of the exemplary embodiments may be freely combined with each other unless otherwise described. However, it should be clearly understood that the description of certain exemplary embodiments is provided by way of non-limiting and illustrative example only, and is in no way intended to be construed as limiting.

[0104] The terminology used herein is generally provided for the purpose of describing certain exemplary embodiments only and is not intended to be limiting. In the following, unless otherwise defined, all technical and scientific terms used herein may have the same meaning as commonly understood by those skilled in the art to which this subject matter disclosure pertains.

[0105] References to "example embodiments," "some example embodiments," "certain example embodiments," "various example embodiments," etc., in this disclosure indicate that the described embodiments(s) may include(s) specific features, structures, or characteristics, but not every example embodiment described herein necessarily includes(s) specific features, structures, or characteristics. Furthermore, these phrases do not necessarily refer to the same example embodiment. Additionally, when(s) specific features, structures, or characteristics are described in conjunction with exemplary embodiments, it is considered that combining such features, structures, or characteristics in conjunction with any other exemplary embodiments described herein is within the knowledge of those skilled in the art, whether or not such combination is explicitly described.

[0106] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including”, when used herein, specify the presence of the stated features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0107] As used herein, the terms “at least one” and “one or more” mean “any one of at least one” and “any one of one or more”, respectively.

[0108] As used herein, the term "at least one of X or Y" may mean "at least one of X and Y".

[0109] Furthermore, it should be understood that the device is configured to execute the corresponding method, even though in some cases only the device or method is described.

[0110] In addition, a computer program including instructions may be provided, which, when executed by the device, causes the device to perform each method step. The instructions may also be stored on a non-transitory computer-readable medium. As used herein, the term "non-transitory" refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., random access memory (RAM) versus read-only memory (ROM)).

[0111] Figure 1 This is a block diagram illustrating a communication device according to an example embodiment. Figure 1 The communication device 100 can be a receiver entity or a transmitter entity. For example, the communication device 100 can be a UE or a gNB. Figure 2 This is a schematic diagram of a communication method according to an example embodiment. According to... Figure 1 The communication device 100 can perform Figure 2 The communication method is applicable, but not limited to this method. Figure 2 The communication method can be determined by Figure 1 The communication device 100 performs the operation, but it is not limited to the communication device 100 performing the operation.

[0112] like Figure 1 As indicated, according to some example embodiments, the communication device 100 includes a component 110 for configuration or reconfiguration.

[0113] In some example embodiments, the component 110 for configuration or reconfiguration is configured to configure or reconfigure parameters related to the triggering of RLC status reports at the receiver entity, including a threshold indicating the maximum value of the RLC PDU received by the receiver entity to trigger an RLC status report (S210).

[0114] In some example embodiments, the maximum value of the RLC PDU received by the receiver entity to trigger an RLC status report includes at least one of the maximum number of RLC PDUs received by the receiver entity or the maximum number of bytes received by the receiver entity. This means that the maximum value of the RLC PDU received by the receiver entity to trigger an RLC status report can be indicated by the maximum number of RLC PDUs received by the receiver entity, the maximum number of bytes received by the receiver entity, or both.

[0115] In some example embodiments, configuration or reconfiguration is performed by the receiver entity. This means that the communication device 100 can be the receiver entity.

[0116] In some example embodiments, configuration or reconfiguration is performed by the transmitter entity by generating an RRC message or MAC CE of configuration or reconfiguration parameters and sending the RRC message or MAC CE to the receiver entity. This means that the communication device 100 can be the transmitter entity.

[0117] In some example implementations, the MAC CE is specified using a configured LCID value.

[0118] In some example embodiments, configuration or reconfiguration is triggered by activating or deactivating PDCP replication.

[0119] Figure 3 This is a block diagram illustrating a communication device according to an example embodiment. Figure 3 The communication device 300 can be a receiver entity or a transmitter entity. For example, the communication device 300 can be a UE or a gNB. Figure 4 This is a schematic diagram of a communication method according to an example embodiment. According to... Figure 3 The communication device 300 can perform Figure 4 The communication method is applicable, but not limited to. Figure 4 The communication method can be determined by Figure 3 The communication device 300 performs the operation, but it is not limited to the communication device 300 performing the operation.

[0120] like Figure 3 As indicated in the document, according to some example embodiments, the communication device 300 includes a component 310 for configuration or reconfiguration.

[0121] In some example embodiments, the component 310 for configuration or reconfiguration is configured to configure or reconfigure parameters related to the triggering of RLC status reports at the receiver entity, including a threshold indicating the maximum value of time elapsed since the RLC PDU was received by the receiver entity to trigger an RLC status report (S410).

[0122] In some example embodiments, configuration or reconfiguration is performed by the receiver entity. This means that the communication device 300 can be the receiver entity.

[0123] In some example embodiments, configuration or reconfiguration is performed by the transmitter entity by generating an RRC message or MAC CE of configuration or reconfiguration parameters and sending the RRC message or MAC CE to the receiver entity. This means that the communication device 300 can be the transmitter entity.

[0124] In some example implementations, the MAC CE is specified using a configured LCID value.

[0125] In some example embodiments, configuration or reconfiguration is triggered by activating or deactivating PDCP replication.

[0126] Figure 5 This is a block diagram illustrating a communication device according to an example embodiment. Figure 5 The communication device 500 can be a receiver entity or a transmitter entity. For example, the communication device 500 can be a UE or a gNB. Figure 6 This is a schematic diagram of a communication method according to an example embodiment. According to... Figure 5 The communication device 500 can perform Figure 6 The communication method is applicable, but not limited to. Figure 6 The communication method can be determined by Figure 5 The communication device 500 performs the execution, but it is not limited to the communication device 500 performing the execution.

[0127] like Figure 5 As indicated in the document, according to some example embodiments, the communication device 500 includes a component 510 for configuration or reconfiguration.

[0128] In some example embodiments, the component 510 for configuration or reconfiguration is configured to configure or reconfigure rules relating to the content of the RLC status report, which activates or deactivates at least one of the following in the RLC status report: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, or the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report (S610).

[0129] In some example embodiments, activating or deactivating the RLC status report, including the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, corresponds to the first rule. This means that the first rule can activate or deactivate the RLC status report, including the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0130] In some example embodiments, activating or deactivating the RLC status report includes the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report, corresponding to the second rule. This means that the second rule can activate or deactivate the RLC status report including the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0131] In some example embodiments, configuration or reconfiguration is performed by the receiver entity. This means that the communication device 500 can be the receiver entity.

[0132] In some example embodiments, configuration or reconfiguration is performed by the sender entity by generating an RRC message or MAC CE for the configuration or reconfiguration rules and sending the RRC message or MAC CE to the receiver entity. This means that the communication device 500 can be the sender entity. The configuration or reconfiguration rules can be at least one of a first rule or a second rule. The MAC CE can be specified using the configured LCID value.

[0133] In some example embodiments, configuration or reconfiguration is triggered by activating or deactivating PDCP replication.

[0134] Figure 7 This is a block diagram illustrating a communication device according to an example embodiment. Figure 7 The communication device 700 can be a receiver entity or a transmitter entity. For example, the communication device 700 can be a UE or a gNB. Figure 8 This is a schematic diagram of a communication method according to an example embodiment. According to... Figure 7 The communication device 700 can perform Figure 8 The communication method is applicable, but not limited to. Figure 8 The communication method can be determined by Figure 7 The communication device 700 performs the execution, but is not limited to execution by the communication device 700. Figure 7 and Figure 8 In the diagram, optional features are indicated by dashed lines.

[0135] like Figure 7As indicated herein, according to some example embodiments, the communication device 700 includes a component 720 for application. The communication device 700 may also include a component 710 for receiving.

[0136] In some example embodiments, the receiving component 710 is configured to receive an RRC message or MAC CE from a transmitter entity, which configures or reconfigures rules related to the content of an RLC status report (S810). The configured or reconfigured rules can be at least one of a first rule or a second rule. The MAC CE can be specified using a configured LCID value.

[0137] In some example embodiments, the application component 720 is configured to apply rules relating to the content of the RLC status report, which activate or deactivate at least one of the following in the RLC status report: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report (S820). The application component 720 can be executed by generating an RLC status report that includes at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, when the rule activates the RLC status report to include at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0138] In some example embodiments, activating or deactivating the RLC status report, including the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, may correspond to a first rule. This means that the first rule can activate or deactivate the RLC status report, including the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0139] In some example embodiments, the component 720 for application may be configured to apply the first rule by generating an RLC status report that includes the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device 700, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report. This case is where the first rule activates the RLC status report to include the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0140] In some example embodiments, activating or deactivating the RLC status report, including the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report, can correspond to the second rule. This means that the second rule can activate or deactivate the RLC status report, including the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0141] In some example embodiments, the component 720 for application may be configured to apply the second rule by generating an RLC status report that includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device 700, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report. In this case, the second rule activates the RLC status report to include the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0142] Figure 9This is a block diagram illustrating a communication device according to an example embodiment. Figure 9 The communication device 900 can be a receiver entity. For example, the communication device 900 can be a UE or a gNB. Figure 10 This is a schematic diagram of a communication method according to an example embodiment. According to... Figure 9 The communication device 900 can perform Figure 10 The communication method is applicable, but not limited to. Figure 10 The communication method can be determined by Figure 9 The communication device 900 performs the operation, but it is not limited to the operation performed by the communication device 900. Figure 9 and Figure 10 In the diagram, optional features are indicated by dashed lines.

[0143] like Figure 9 As indicated herein, according to some example embodiments, the communication device 900 includes a first component 920 for receiving and a component 930 for adding. The communication device 900 may also include a second component 910 for receiving, a component 940 for transmitting, and a component 950 for performing.

[0144] In some example embodiments, the second component 910 for receiving is configured to receive an RRC message or MAC CE from a transmitter entity, which configures or reconfigures at least one of a first threshold or a second threshold (S1010). The MAC CE may be specified using a configured LCID value.

[0145] In some example embodiments, the first component 920 for receiving is configured to receive at least one RLC PDU from the transmitter entity (S1020), and the component 930 for incrementing is configured to increment a counter for each received RLC PDU (S1030). The counter may include at least one of a first counter that increments by 1 for each received RLC PDU or a second counter that increments the size of each received RLC PDU.

[0146] In some example embodiments, the component 940 for sending is configured to send an RLC status report to the transmitter entity if at least one of the following threshold criteria for triggering an RLC status report is met: a first counter is greater than a configured first threshold or a second counter is greater than a configured second threshold (S1040).

[0147] In some example embodiments, the component 950 for execution is configured to perform at least one of the following when the RLC status report is triggered: resetting a first counter to 0 or resetting a second counter to 0 (S1050). The RLC status report may be triggered based on at least one of the following: a polling bit set in the received RLC PDU; the expiration of a reassembly timer, which is started at the communication device when at least a portion of the RLC PDU is detected as lost; a first counter greater than a configured first threshold; a second counter greater than a configured second threshold; or a timer value greater than a configured timer threshold, which is started at the communication device after receiving at least one RLC PDU if the timer is not running.

[0148] Figure 11 This is a block diagram illustrating a communication device according to an example embodiment. Figure 11 The communication device 1100 can be a receiver entity. For example, the communication device 1100 can be a UE or a gNB. Figure 12 This is a schematic diagram of a communication method according to an example embodiment. According to... Figure 11 The communication device 1100 can perform Figure 12 The communication method is applicable, but not limited to. Figure 12 The communication method can be determined by Figure 11 The communication device 1100 performs the execution, but it is not limited to the execution by the communication device 1100. Figure 11 and Figure 12 In the diagram, optional features are indicated by dashed lines.

[0149] like Figure 11 As indicated herein, according to some example embodiments, the communication device 1100 includes a first component 1120 for receiving and a component 1130 for initiating. The communication device 1100 may also include a second component 1110 for receiving, a component 1140 for transmitting, and a component 1150 for executing.

[0150] In some example embodiments, the second component 1110 for receiving is configured to receive an RRC message or a MAC CE from a transmitter entity that configures or reconfigures a timer threshold (S1210). The MAC CE may be specified using a configured LCID value.

[0151] In some example embodiments, the receiving component 1120 is configured to receive at least one RLC PDU from the transmitter entity (S1220), and the starting module 1130 is configured to start a timer if the timer is not running after receiving at least one RLC PDU (S1230).

[0152] In some example embodiments, the component 1240 for sending is configured to send an RLC status report to the transmitter entity if the following threshold criterion for triggering the RLC status report is met: the timer value is greater than the configured timer threshold (S1240).

[0153] In some example embodiments, the component 1150 for execution is configured to perform the following operation upon triggering an RLC status report: stop the timer and reset the timer to 0. The RLC status report may be triggered based on at least one of the following: a polling bit set in a received RLC PDU; the expiration of a reassembly timer, which is started at the communication device when at least a portion of the RLC PDU is detected as lost; a first counter greater than a configured first threshold, which is incremented by 1 for each received RLC PDU; a second counter greater than a configured second threshold, which is incremented by the size of each received RLC PDU; or a timer value greater than a configured timer threshold.

[0154] Note that communication devices 100, 300, 500, 700, 900, and 1100 can be configured as a single device that includes more than one of the functions of one of the communication devices 100, 300, 500, 700, 900, and 1100, and can include all the functions of communication devices 100, 300, 500, 700, 900, and 1100.

[0155] Figure 13 This is a schematic diagram illustrating a MAC CE according to an example embodiment. Figure 13 The diagram illustrates a MAC CE, according to an example embodiment, for configuring the content of the RLC status report (related to the state of the data packet) and / or the ACK_SN parameter in the RLC status report by activating or deactivating a first rule and / or a second rule (re-activation). Figure 13 The MAC CE can be generated by communication devices 100, 300, and 500.

[0156] according to Figure 13 The MAC CE includes the ACK_SN field and the LCID field. The LCID field indicates whether the MAC CE is used to configure or reconfigure the RLC parameter ACK_SN. The ACK_SN field indicates whether an RLC status report should be reported by setting ACK_SN to RX_NEXT_HIGHEST using number 1, and whether an RLC status report should be reported by setting ACK_SN to RX_HIGHEST_STATUS using number 0. Furthermore, when ACK_SN is set to RX_NEXT_HIGHEST, Figure 13The reserved bit R in the MAC CE shown can indicate whether the first rule is applied by using number 1 or the second rule is applied by using number 0.

[0157] An RLC status report showing complete details of successfully received packets can overcome situations where RLC status reports contain insufficient information. This complete status report can be advantageous during periods when HARQ retransmission expectations are low and PDCP replication is active, in order to avoid unwanted replication (i.e., the increased overhead caused by additional replication).

[0158] In addition to the RLC status report, which includes the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, and the indication of RX_NEXT_HIGHEST in the first ACK_SN field (corresponding to the first rule), RX_HIGHEST_STATUS can be indicated in the second ACK_SN field of the RLC status report (corresponding to the second rule). Based on this additional detail, the transmitter can choose to wait for the retransmission of packets that are NACKed between RX_HIGHEST_STATUS and RX_NEXT_HIGHEST (if any, until such NACKed packets fall below RX_HIGHEST_STATUS to complete HARQ retransmission), while packets indicated as ACK during this range (between RX_HIGHEST_STATUS and RX_NEXT_HIGHEST) will be deleted (in the case of PDCP replication, such packets can avoid replication).

[0159] The first rule and / or the second rule can be configured via RRC messages and RLC entity configuration, or can be dynamically (re)configured via RRC messages or MAC CE.

[0160] Figure 14 This is a schematic diagram illustrating a MAC CE according to an example embodiment. Figure 14 The diagram illustrates a MAC CE for (re)configuring timer value parameters according to an example embodiment. Figure 13 The MAC CE can be generated by communication devices 100, 300, and 500.

[0161] according to Figure 14 The MAC CE includes an LCID field and a timer value field. The LCID field indicates the timer value that the MAC CE is used to configure or reconfigure. The timer value field indicates the threshold for a periodic timer used to trigger an RLC status report. The timer value can be configured via RRC messages and RLC entity configuration, or it can be dynamically (re)configured via RRC messages or the MAC CE.

[0162] If the timer used to trigger the RLC status report is not running, a periodic timer can be started upon receiving an RLCPDU. When the periodic timer expires (i.e., its value is greater than the configured timer value), the RLC status report is triggered, and the timer is stopped and reset to 0. If any packets exist that do not send an RLC status report, the timer can be restarted.

[0163] If an RLC status report is triggered for any reason while the timer is running, the periodic timer is stopped and reset to 0. The reason for triggering the RLC status report can be any of the reasons described in this disclosure (PDU_WITHOUT_STATUS, BYTE_WITHOUT_STATUS, periodic timer), and may include a polling bit set by the transmitter entity in the received RLC PDU, and a t-reassembly timer that is started at the communication device when at least a portion of the RLC PDU is detected as lost.

[0164] Figure 15 This is a schematic diagram illustrating a MAC CE according to an example embodiment. Figure 15 The diagram illustrates a MAC CE for (re)configuring newPDU value parameters according to an example embodiment. Figure 15 The MAC CE can be generated by communication devices 100, 300, and 500.

[0165] according to Figure 15 The MAC CE includes an LCID field and a newPDU value field. The LCID field indicates the MAC CE used to configure or reconfigure the newPDU value. The newPDU value field indicates the threshold of the counter PDU_WITHOUT_STATUS used to trigger RLC status reporting. The newPDU value can be configured via RRC messages and RLC entity configuration, or it can be dynamically (re)configured / activated / deactivated via RRC messages or the MAC CE.

[0166] The counter PDU_WITHOUT_STATUS (corresponding to the first counter) can be initially set to 0 and can be incremented by 1 at the receiver entity for each received RLC PDU (non-replicated RLC PDU). If PDU_WITHOUT_STATUS is greater than the newPDU value (PDU_WITHOUT_STATUS > newPDU), an RLC status report can be triggered, and PDU_WITHOUT_STATUS can be reset to 0.

[0167] In a case where an RLC status report is triggered for any reason when PDU_WITHOUT_STATUS < newPDU, PDU_WITHOUT_STATUS is reset to 0. The reason for triggering the RLC status report may be any of the reasons described in the present disclosure (PDU_WITHOUT_STATUS, BYTE_WITHOUT_STATUS, periodic timer), and may include a poll bit set by a transmitter entity in a received RLC PDU, and a t-reordering timer, which is started at a communication device when at least partial loss of an RLC PDU is detected.

[0168] As is apparent from the foregoing, the counter PDU_WITHOUT_STATUS counts the number of RLC PDUs received at the receiver since the most recent RLC status report was transmitted.

[0169] Figure 16 is a schematic diagram illustrating a MAC CE according to an example embodiment. Figure 16 the figure illustrates a MAC CE for (re)configuring a newByte value parameter according to an example embodiment. According to Figure 16 the MAC CE may be generated by communication devices 100, 300, 500.

[0170] According to Figure 16 the MAC CE includes an LCID field and a newByte value field. The LCID may indicate that the MAC CE is used to configure or reconfigure the newByte value. The newByte value field may indicate a threshold for the counter BYTE_WITHOUT_STATUS for triggering an RLC status report. The newByte value may be configured via an RRC message and RLC entity configuration, or may be dynamically (re)configured / activated / deactivated via an RRC message or a MAC CE.

[0171] The counter BYTE_WITHOUT_STATUS (corresponding to a second counter) may be initially set to 0, and may be incremented at a receiver entity by the size of each received RLC PDU (non-duplicate RLC PDU). If BYTE_WITHOUT_STATUS is greater than the newByte value (BYTE_WITHOUT_STATUS>newByte), an RLC status report may be triggered, and BYTE_WITHOUT_STATUS may be reset to 0.

[0172] In the case where an RLC status report is triggered for any reason when BYTE_WITHOUT_STATUS < newByte, BYTE_WITHOUT_STATUS is reset to 0. The reasons for triggering an RLC status report may be any of the reasons described in the present disclosure (PDU_WITHOUT_STATUS, BYTE_WITHOUT_STATUS, periodic timer), and may include a polling bit set by a transmitting entity in a received RLC PDU, and a t-reassembly timer, which is started at a communication device when at least partial loss of an RLC PDU is detected.

[0173] As is apparent from the above, the counter BYTE_WITHOUT_STATUS counts the number of data bytes received at the receiver since the most recent RLC status report was transmitted.

[0174] Figure 17 is a schematic diagram of a method according to an example embodiment. Figure 17 the method illustrates optimization of system behavior according to an example embodiment. In accordance with Figure 17 the method may be performed by communication apparatuses 100, 300, 500.

[0175] In step S1710, a PDCP / RLC bearer is configured with an initial configuration. In step S1715, it is determined whether the system behavior is optimal. The system behavior may not be optimal in case of dynamic functional changes, for example, due to activation of features similar to PDCP duplication, changes in signaling conditions, etc. Taking PDCP duplication as an example, for example, when PDCP duplication is activated, for optimal system behavior, faster and more detailed information about the status of complete packets may be expected from the receiving RLC entity. For example, it may be determined that the system behavior is not optimal by the transmitting entity determining that the overhead caused by not waiting for HARQ reordering to transmit the RLC status report is less than the additional L2 duplication of packets, by the receiving entity detecting a delay in triggering an RLC status report for UL data, or by the transmitting entity detecting a delay in receiving an RLC status report for DL data.

[0176] In the case where the system behavior is optimal ("Yes" in S1715), step S1720 is performed. In step S1720, the current configuration is continued.

[0177] If the system behavior is not optimal ("No" in S1715), proceed to step S1725. In step S1725, the (re)configuration of the RLC status report triggering / content mechanism is performed. This means that at least one of the new(multiple) triggers used to trigger the RLC status report is added to the receiver entity (PDU_WITHOUT_STATUS, BYTE_WITHOUT_STATUS, timer-based trigger), or the content of the RLC status report—the status of data packets and / or (multiple) ACK_SN fields (RX_NEXT_HIGHEST, RX_HIGHEST_STATUS)—is adjusted using the first rule and / or the second rule.

[0178] Figure 18 This is a schematic diagram of a method according to an example embodiment. Figure 18 The method illustrates the dynamic (re)configuration of the RLC status report ACK_SN rule according to the example embodiment. Performed by the gNB. Figure 18 The method steps can be executed by the communication device 500.

[0179] In step S1810, DL data is sent from the gNB to the UE, which triggers an RLC status report at the UE (S1815), for example, by using the set polling bit. In step S1820, the UE sends an RLC status report to the gNB including the status of all packets up to RX_HIGHEST_STATUS and ACK_SN = RX_HIGHEST_STATUS. In step S1825, L2 packet replication is enabled by the gNB. In step S1810, DL data is sent from the gNB to the UE. In step S1835, the gNB determines that the overhead of not waiting for HARQ reordering for sending the RLC status report is less than the additional L2 replication of packets, i.e., the system behavior is not optimal. Due to the determination in step S1835, the gNB requests an RLC status report in step S1840, which includes the status of all packets up to RX_NEXT_HIGHEST and an indication of RX_NEXT_HIGHEST via MAC CE in the first ACK_SN field (e.g., according to...). Figure 13In step S1850, the gNB (reconfigures) the activation of the first rule to include the status of all RLC PDUs received at the UE up to RX_NEXT_HIGHEST, as well as the indication of RX_NEXT_HIGHEST in the first ACK_SN field via MAC CE, and triggers an RLC status report (S1845), for example by using the set polling bit. In step S1850, the UE sends an RLC status report to the gNB, which includes the status of all RLC PDUs received at the UE up to RX_NEXT_HIGHEST, and has ACK_SN (first ACK_SN field) = RX_NEXT_HIGHEST.

[0180] In step S1840, the gNB can (re)configure the activation of the second rule to include, via the MAC CE, the status of all RLC PDUs received at the UE up to RX_NEXT_HIGHEST, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report. In this case, in step S1850, the UE sends an RLC status report to the gNB, which includes the status of all RLC PDUs received at the UE up to RX_NEXT_HIGHEST, ACK_SN (first ACK_SN field) = RX_NEXT_HIGHEST, and ACK_SN (second ACK_SN field) = RX_HIGHEST_STATUS.

[0181] Figure 19 This is a schematic diagram of a method according to an example embodiment. Figure 19 The method illustrates a (re)configuration of a new RLC status report triggering mechanism at the receiver RLC entity used for UL data. Performed by the gNB. Figure 19 The method steps can be executed by communication devices 100, 300, and 500.

[0182] In step S1910, the UE determines that the RLC status report triggering criteria PDU_WITHOUT_POLL>polllPDU or BYTE_WITHOUT_POLL>polllByte are met. Therefore, in step S1915, the UE sends an RLC PDU including the set polling bits to the gNB. In step S1920, the gNB sends an RLC status report to the UE.

[0183] In step S1925, the UE determines that the RLC status report triggering criteria PDU_WITHOUT_POLL>polllPDU or BYTE_WITHOUT_POLL>polllByte are satisfied again (due to the RLC PDU (not shown) sent from the UE to the gNB). Therefore, in step S1930, the UE sends an RLC PDU including the set polling bit to the gNB. However, in this example, the RLC PDU with the set polling bit is lost in the air, so the gNB cannot successfully receive the RLC PDU with the set polling bit. In this scenario, RLC triggering will not be triggered on the gNB (step S1935). Therefore, even if the UE requests an RLC status report, the RLC status report will not be sent from the gNB to the UE.

[0184] Therefore, in step S1940, the UE sends the RLC PDU with the set polling bit to the gNB again, and then in step S1945, after successfully receiving the RLC PDU with the set polling bit, the gNB sends an RLC status report to the UE.

[0185] As is evident from this scenario, the time taken to trigger an RLC status report at the gNB is long due to the loss of the RLC PDU with the polling bit set in step S1930. Therefore, in step S1950, the gNB detects the delay in triggering the RLC status report for UL data, and thus (re)configures at least one of the new mechanisms to trigger the RLC status report (PDU_WITHOUT_STATUS, BYTE_WITHOUT_STATUS, timer-based triggering). The gNB can detect the delay in triggering the status report for UL data due to an increase in RLC lost packet detection or an increase in the time period pattern of receiving RLC PDUs with the polling bit set.

[0186] Figure 20 This is a schematic diagram of a method according to an example embodiment. Figure 20 The method illustrates a (re)configuration of a new RLC status report triggering mechanism at the receiver RLC entity for DL ​​data according to an example embodiment. Performed by the gNB. Figure 20 The method steps can be executed by communication devices 100, 300, and 500.

[0187] In step S2010, the gNB determines that the RLC status report triggering criteria PDU_WITHOUT_POLL>polllPDU or BYTE_WITHOUT_POLL>polllByte are met (due to the RLC PDU (not shown) sent from the gNB to the UE). Therefore, in step S2015, the gNB sends an RLC PDU including the set polling bits to the UE. In step S2020, the UE sends an RLC status report to the gNB.

[0188] In step S2025, the gNB determines that the RLC status report triggering criteria PDU_WITHOUT_POLL>polllPDU or BYTE_WITHOUT_POLL>polllByte are satisfied again (due to the RLC PDU (not shown) sent from the gNB to the UE). Therefore, in step S2025, the gNB sends an RLC PDU including the set polling bit to the UE. However, in this example, the RLC PDU with the set polling bit is lost in the air, causing the UE to fail to receive the RLC PDU with the set polling bit. In this scenario, RLC triggering is not triggered by the gNB (step S2035). Therefore, even if the gNB requests an RLC status report, the RLC status report will not be sent from the UE to the gNB.

[0189] Therefore, in step S2040, the gNB sends the RLC PDU with the set polling bit to the UE again, and then in step S2045, after successfully receiving the RLC PDU with the set polling bit, the UE sends an RLC status report to the gNB.

[0190] As is evident from this scenario, due to the loss of the RLC PDU with the polling bit set in step S2030, the time spent by the gNB receiving the RLC status report after requesting a report by setting the polling bit is long. Therefore, in step S2050, after sending the RLC PDU with the polling bit set, the gNB detects a delay in receiving the RLC status report for DL ​​data, and therefore, (re)configures at least one of the new mechanisms to use MAC CE (e.g., according to...). Figures 14 to 16 The gnB can detect delays in receiving status reports for DL ​​data after sending an RLC PDU with the polling bit set, due to an increase in RLC NACK.

[0191] Figure 21 This is a schematic diagram of a method according to an example embodiment. Figure 21The method exemplifies how the receiver RLC entity applies a new RLC status report triggering mechanism. This is performed by the receiver entity. Figure 21 The method steps can be executed by the communication device 900.

[0192] exist Figure 21 In the method, it is assumed that at least one of the first counter (PDU_WITHOUT_STATUS) or the second counter (BYTE_WITHOUT_STATUS) is activated at the receiver entity.

[0193] In step S2110, new data is sent from the transmitter entity to the receiver entity. In step S2115, the receiver entity increments at least one of a first counter or a second counter. This means that for each received RLC PDU, the receiver entity increments PDU_WITHOUT_STATUS by 1, and / or BYTE_WITHOUT_STATUS by the size of each received RLCPDU. Also in step S2115, the transmitter entity determines that the RLC status report triggering criteria PDU_WITHOUT_POLL > pollPDU or BYTE_WITHOUT_POLL > pollByte are met. Therefore, in step S2120, the UE requests an RLC status report by sending an RLC PDU including the set polling bit. In step S2125, the receiver entity sends the RLC status report to the transmitter entity.

[0194] Since the RLC status report is triggered by the polling bit, in step S2130, PDU_WITHOUT_STATUS and / or BYTE_WITHOUT_STATUS are reset to 0.

[0195] In step S2135, the transmitter entity determines that the RLC status report triggering criteria PDU_WITHOUT_POLL>polllPDU or BYTE_WITHOUT_POLL>polllByte are met (due to the transmission of an RLC PDU from the transmitter entity to the receiver entity (not shown)). Therefore, in step S2140, the transmitter entity transmits an RLCPDU including the set polling bit to the receiver entity. However, in this example, the RLC PDU with the set polling bit is lost in the air, causing the receiver entity to fail to receive the RLC PDU with the set polling bit. In this scenario, RLC triggering is not triggered by the polling bit at the receiver entity.

[0196] However, in step S2145, the receiver entity determines that at least one of the RLC status report trigger criteria PDU_WITHOUT_STATUS>newPDU or BYTE_WITHOUT_STATUS>newByte is met (this increases the counter value accordingly due to the RLC PDU sent from the transmitter entity to the receiver entity (not shown)).

[0197] In step S2150, due to the triggering mechanism at the receiver entity, the receiver entity sends an RLC status report to the transmitter entity. In step S2155, the receiver entity resets PDU_WITHOUT_STATUS and / or BYTE_WITHOUT_STATUS to zero.

[0198] As is evident from the above, the time spent triggering an RLC status report is reduced due to the receiver entity's triggering mechanism.

[0199] Figure 22 This is a schematic diagram of a method according to an example embodiment. Figure 22 The method illustrates a mechanism triggered by the application of a new RLC status report by the receiver RLC entity. Figure 22 The method steps can be executed by the communication device 1100.

[0200] In step S2210, a timer-based RLC status report is configured at the receiver entity. This can be implemented by the receiver entity configuring the receiver entity itself when the receiver entity is a gNB, or by the transmitter entity configuring the receiver entity itself when the receiver entity is a UE (e.g., via an RRC message or MAC CE (e.g., according to...)). Figure 14 )).

[0201] In step S2215, new data is sent from the transmitter entity to the receiver entity. Therefore, in step S2220, a periodic timer configured at the receiver entity is started due to the newly received data (RLC PDU).

[0202] In step S2225, new data is sent from the transmitter entity to the receiver entity. In step S2230, it is determined that the periodic timer is already running, so that the periodic timer will not be restarted.

[0203] In step S2235, new data is sent from the transmitter entity to the receiver entity. In step S2240, the receiver entity determines that the periodic timer has expired and triggers an RLC status report. Therefore, in step S2245, an RLC status report is sent from the receiver entity to the transmitter entity.

[0204] In step S2250, new data is sent from the transmitter entity to the receiver entity. Therefore, in step S2255, a periodic timer configured at the receiver entity is started due to the newly received data (RLC PDU).

[0205] In step S2260, new data, including the set polling bit, is sent from the transmitter entity to the receiver entity. Therefore, in step S2265, an RLC status report is triggered at the receiver entity. Due to the RLC status report triggered by the polling bit, the periodic timer is stopped and reset to 0 at the receiver entity.

[0206] In step S2270, the RLC status report is sent from the receiver entity to the transmitter entity.

[0207] Figure 23 This is a schematic diagram illustrating an RLC status report according to an example embodiment. Figure 23 The diagram illustrates the RLC status report, including the ACK_SN field, according to the first rule. Figure 23 The RLC status report can be generated by the communication device 500.

[0208] Figure 23 The RLC status report shown includes the status of all RLC PDUs up to RX_NEXT_HIGHEST received at the receiver entity.

[0209] Figure 24 This is a schematic diagram illustrating an RLC status report according to an example embodiment. Figure 24 The diagram illustrates a status report that includes two ACK_SN fields according to the second rule. Figure 23 The RLC status report can be generated by the communication device 500.

[0210] Figure 24 The RLC status report shown includes the status of all RLC PDUs up to RX_NEXT_HIGHEST received at the receiver entity.

[0211] Figure 25 This is an alternative block diagram illustrating a communication device according to an example embodiment. For example... Figure 25 As indicated in the example embodiment, the communication device 100' (corresponding to the communication device 100) includes a processor 2510, a memory 2520, and an I / O unit 2530 capable of sending to and / or receiving from other network elements.

[0212] Figure 26 This is an alternative block diagram illustrating a communication device according to an example embodiment. For example... Figure 26As indicated in the example embodiment, the communication device 300' (corresponding to the communication device 300) includes a processor 2610, a memory 2620, and an I / O unit 2630 capable of sending to and / or receiving from other network elements.

[0213] Figure 27 This is an alternative block diagram illustrating a communication device according to an example embodiment. For example... Figure 27 As indicated in the example embodiment, the communication device 500' (corresponding to the communication device 500) includes a processor 2710, a memory 2720, and an I / O unit 2730 capable of sending to and / or receiving from other network elements.

[0214] Figure 28 This is an alternative block diagram illustrating a communication device according to an example embodiment. For example... Figure 28 As indicated in the example embodiment, the communication device 700' (corresponding to the communication device 700) includes a processor 2810, a memory 2820, and an I / O unit 2830 capable of sending to and / or receiving from other network elements.

[0215] Figure 29 This is an alternative block diagram illustrating a communication device according to an example embodiment. For example... Figure 29 As indicated in the example embodiment, the communication device 900' (corresponding to the communication device 900) includes a processor 2910, a memory 2920, and an I / O unit 2930 capable of sending to and / or receiving from other network elements.

[0216] Figure 30 This is an alternative block diagram illustrating a communication device according to an example embodiment. For example... Figure 27 As shown, according to an example embodiment, device 1100' (corresponding to communication device 1100) includes a processor 3010, a memory 3020, and an I / O unit 3030 capable of sending to and / or receiving from other network elements.

[0217] The memories 2520, 2620, 2720, 2820, 2920, and 3020 can store corresponding programs, which are assumed to include program instructions or computer program code, and when executed by the corresponding processors 2510, 2610, 2710, 2810, 2910, and 3010, enable the corresponding electronic devices 100', 300', 500', 700', 900', and 1100' to operate according to the example embodiments.

[0218] In general, the corresponding device (and / or part thereof) may represent a component for performing the corresponding operation and / or displaying the corresponding functionality, and / or the corresponding device (and / or part thereof) may have a function for performing the corresponding operation and / or displaying the corresponding functionality.

[0219] When a description states that a processor (or some other component) is configured to perform certain functions, this will be interpreted as equivalent to stating that at least one processor, potentially cooperating with computer program code stored in the memory of the respective device, is configured to cause the device to perform at least the functions mentioned therein, and vice versa. Furthermore, such functions should be interpreted as being equivalently implementable by components specifically configured to perform the corresponding functions (i.e., the statement "a processor configured to [cause the device] to perform xxx" is interpreted as equivalent to statements such as "components for xxx"), and vice versa.

[0220] For further detailed information regarding the operability / functionality of each device, please refer to the above. Figures 1 to 24 Description of any one of them.

[0221] Generally, the example embodiments can be implemented by computer software stored in memory (memory resources, memory circuits) 2520, 2620, 2720, 2820, 2920, 3020, and can be executed by processor (processing resources, processing circuits) 2510, 2610, 2710, 2810, 2910, 3010 or hardware or a combination of software and / or firmware and hardware.

[0222] The memory (memory resources, memory circuitry) 2520, 2620, 2720, 2820, 2920, and 3020 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed and removable memory, and non-transitory computer-readable media. As a non-limiting example, the processor (processing resources, processing circuitry) 2510, 2610, 2710, 2810, 2910, and 3010 can be of any type suitable for the local technical environment and can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0223] Furthermore, as used in this application, the term "circuit" may refer to one or more or all of the following:

[0224] (a) Pure hardware circuit implementation (such as implementation in analog, digital and / or quantum circuits) and

[0225] (b) A combination of (multiple) hardware circuits and software, such as (if applicable):

[0226] (i) A combination of (multiple) analog, digital, and / or quantum hardware circuits and software / firmware, and

[0227] (ii) Any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors) having software and (multiple) memories, which work together to enable a device (such as a mobile device, computing device, or server) to perform various functions and

[0228] (c) Any or all parts of (multiple) hardware circuits (such as (multiple) microprocessors, (multiple) processors and / or (multiple) quantum processors) require software (e.g., firmware) to operate, but the software may be absent when it is not required to operate.

[0229] This definition of "circuit" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit" also covers only hardware circuitry or a processor (or multiple processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware implementation. For example, and if applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0230] For the purposes of this disclosure as described above, attention should be paid to

[0231] - The method steps, which may be implemented as part of software code and run on a processor at a network server or network entity (as an example of a device, apparatus and / or its modules, or as an example of an entity including an apparatus and / or its modules), are software code independent and can be specified using any known or future-developed programming language, as long as the functionality defined by the method steps is preserved;

[0232] - Generally, any method steps are suitable for implementation as software or by hardware without changing the idea of ​​the embodiment and its modifications in terms of the functionality achieved;

[0233] - The method steps and / or devices, units, or components that may be implemented as the apparatus or any (or more) modules thereof as defined above (e.g., devices performing the functions of the apparatus according to the embodiments described above) are hardware-independent and may be implemented using any known or future-developed hardware technology or any combination of such technologies, such as MOS (Metal-Oxide-Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter-Coupled Logic), TTL (Transistor-Transistor Logic), etc., using, for example, ASIC (Application-Specific IC (Integrated Circuit)) components, FPGA (Field-Programmable Gate Array) components, CPLD (Complex Programmable Logic Device) components, or DSP (Digital Signal Processor) components;

[0234] Devices, units, or components (such as any of the devices or their corresponding units / components as defined above) may be implemented as individual devices, units, or components, but this does not preclude them from being implemented in a distributed manner throughout the system, provided that the functionality of the devices, units, or components is preserved.

[0235] - A device (such as the device defined above) may be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this does not preclude the possibility that the functionality of the module is implemented as software in a (software) module rather than by hardware, such as a computer program or computer program product including executable software code portions for execution / running on a processor.

[0236] - A device can be considered as an apparatus or a component of one or more apparatuses, for example, whether they cooperate or are independent of each other in function, but are located in the same device housing.

[0237] Generally, it should be noted that the corresponding functional blocks or elements according to the aspects described above can be implemented by any known means, or in hardware and / or software respectively, provided that they are only suitable for performing the functions described in the corresponding parts. The mentioned method steps can be implemented in a single functional block or by a single device, or one or more of the method steps can be implemented in a single functional block or by a single device.

[0238] Generally, any method or step is suitable to be implemented in software or hardware without altering the ideas of this disclosure. Devices and components may be implemented as individual devices, but this does not preclude them from being implemented in a distributed manner throughout the system, provided that the functionality of the devices is preserved. These and similar principles are considered to be known to those skilled in the art.

[0239] Software in the sense of this specification includes software code that includes code components or portions for performing corresponding functions, or computer programs or computer program products, as well as software (or computer programs or computer program products) embodied on a tangible medium, such as a computer-readable (storage) medium on which corresponding data structures or code components / portions are stored, or which may be embodied as signals or chips during its processing.

[0240] This disclosure also covers any conceivable combination of the methods, steps, and operations described above, as well as any conceivable combination of the nodes, devices, apparatuses, modules, or elements described above, provided that the concepts of the methods and structural arrangements described above are applicable.

[0241] It should be understood that the various exemplary embodiments disclosed in this subject matter are illustrative and not restrictive, and are not intended to be construed as limiting. Various modifications and applications will be apparent to those skilled in the art without departing from the spirit and scope of the various exemplary embodiments disclosed in this subject matter.

[0242] The following items are covered by the above disclosure:

[0243] Project 1. A communication method, comprising:

[0244] Configure or reconfigure parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold that indicates the maximum value of RLC Protocol Data Units (PDUs) received by the receiver entity to trigger an RLC status report.

[0245] Project 2. According to the communication method described in Project 1, wherein...

[0246] The maximum value of the RLC PDU received by the receiver entity to trigger an RLC status report includes at least one of the following:

[0247] The maximum number of RLC PDUs received by the receiver entity, or

[0248] The maximum number of bytes received by the receiver entity.

[0249] Project 3. The communication method according to Project 1 or 2, wherein

[0250] Configuration or reconfiguration is performed by the receiver entity.

[0251] Project 4. The communication method according to Project 1 or 2, wherein...

[0252] Configuration or reconfiguration is performed by the transmitter entity by generating a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE) for configuration or reconfiguration parameters, and sending an RRC message or MAC CE to the receiver entity.

[0253] Project 5. The communication method described in Project 4, wherein...

[0254] MAC CE is specified using the configured LCID value.

[0255] Item 6. A communication method according to any one of Items 1 to 5, wherein

[0256] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0257] Project 7. A communication method, comprising:

[0258] Configure or reconfigure parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold that indicates the maximum time elapsed since the RLC PDU was received by the receiver entity to trigger an RLC status report.

[0259] Project 8. The communication method described in Project 7, wherein...

[0260] Configuration or reconfiguration is performed by the receiver entity.

[0261] Item 9. The communication method according to Item 7 or 8, wherein

[0262] Configuration or reconfiguration is performed by the transmitter entity by generating a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE) for configuration or reconfiguration parameters, and sending an RRC message or MAC CE to the receiver entity.

[0263] Project 10. The communication method according to Project 9, wherein

[0264] MAC CE is specified using the configured LCID value.

[0265] Item 11. A communication method according to any one of Items 7 to 10, wherein

[0266] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0267] Item 12. A communication device, comprising:

[0268] At least one processor; and

[0269] At least one memory stores instructions that, when executed by at least one processor, cause the communication device to configure or reconfigure parameters related to the triggering of a Radio Link Control (RLC) Status Report at a receiver entity, including a threshold indicating the maximum value of an RLC Protocol Data Unit (PDU) received by the receiver entity to trigger the RLC Status Report.

[0270] Item 13. The communication device according to Item 12, wherein

[0271] The maximum value of the RLC PDU received by the receiver entity to trigger an RLC status report includes at least one of the following:

[0272] The maximum number of RLC PDUs received by the receiver entity, or

[0273] The maximum number of bytes received by the receiver entity.

[0274] Item 14. The communication device according to Item 12 or 13, wherein

[0275] A communication device is a receiver entity.

[0276] Item 15. The communication device according to Item 12 or 13, wherein

[0277] The communication device is the transmitter entity, and

[0278] Configuration or reconfiguration is performed by generating a Radio Resource Control (RRC) message or a Media Access Control (MAC) Control Element (CE) that generates configuration or reconfiguration parameters, and sending the RRC message or MAC CE to the receiver entity.

[0279] Item 16. The communication device according to Item 15, wherein

[0280] MAC CE is specified using the configured LCID value.

[0281] Item 17. A communication device according to any one of Items 12 to 16, wherein

[0282] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0283] Item 18. A communication device, comprising:

[0284] At least one processor; and

[0285] At least one memory stores instructions that, when executed by at least one processor, cause the communication device to configure or reconfigure parameters related to the triggering of a radio link control (RLC) status report at a receiver entity, the parameters including a threshold indicating the maximum value of time elapsed since the RLCPDU was received by the receiver entity to trigger the RLC status report.

[0286] Item 19. The communication device according to Item 18, wherein

[0287] A communication device is a receiver entity.

[0288] Item 20. The communication device according to Item 18 or 19, wherein

[0289] The communication device is the transmitter entity, and

[0290] Configuration or reconfiguration is performed by generating a Radio Resource Control (RRC) message or a Media Access Control (MAC) Control Element (CE) that generates configuration or reconfiguration parameters, and sending the RRC message or MAC CE to the receiver entity.

[0291] Item 21. The communication device according to Item 20, wherein

[0292] MAC CE is specified using the configured LCID value.

[0293] Item 22. The communication device according to any one of Items 18 to 21, wherein

[0294] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0295] Item 23. A communication device, comprising:

[0296] Components for configuring or reconfiguring parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold indicating the maximum value of RLC Protocol Data Units (PDUs) received by the receiver entity to trigger an RLC status report.

[0297] Item 24. The communication device according to Item 23, wherein

[0298] The maximum value of the RLC PDU received by the receiver entity to trigger an RLC status report includes at least one of the following:

[0299] The maximum number of RLC PDUs received by the receiver entity, or

[0300] The maximum number of bytes received by the receiver entity.

[0301] Item 25. The communication device according to Item 23 or 24, wherein

[0302] A communication device is a receiver entity.

[0303] Item 26. The communication device according to Item 23 or 24, wherein

[0304] The communication device is the transmitter entity, and

[0305] The component used for configuration or reconfiguration performs configuration or reconfiguration by generating Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CE) for configuration or reconfiguration parameters, and sending RRC messages or MAC CEs to the receiver entity.

[0306] Item 27. The communication equipment according to item 26, wherein

[0307] MAC CE is specified using the configured LCID value.

[0308] Item 28. A communication device according to any one of Items 23 to 27, wherein...

[0309] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0310] Item 29. A communication device, comprising:

[0311] A component for configuring or reconfiguring parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold indicating the maximum time elapsed since the RLCPDU was received by the receiver entity to trigger an RLC status report.

[0312] Item 30. The communication device according to Item 29, wherein

[0313] A communication device is a receiver entity.

[0314] Item 31. The communication device according to Item 29 or 30, wherein

[0315] The communication device is the transmitter entity, and

[0316] The component used for configuration or reconfiguration performs configuration or reconfiguration by generating Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CE) for configuration or reconfiguration parameters, and sending RRC messages or MAC CEs to the receiver entity.

[0317] Item 32. The communication device according to Item 31, wherein

[0318] MAC CE is specified using the configured LCID value.

[0319] Item 33. The communication device according to any one of Items 29 to 32, wherein

[0320] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0321] Item 34. A computer program product comprising an instruction set, which, when executed on a device, is configured to cause the device to perform the method according to any one of items 1 to 6 or 7 to 11.

[0322] Item 35. The computer program product according to Item 34 is embodied in a computer-readable medium or can be directly loaded into a computer.

[0323] Item 36. A communication method, comprising:

[0324] Configure or reconfigure rules relating to the content of the Radio Link Control (RLC) Status Report, which activate or deactivate at least one of the following in the RLC Status Report: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or the indication of RX_NEXT_HIGHEST in the first acknowledgment sequence number (ACK_SN) field of the RLC Status Report.

[0325] Item 37. The communication method according to Item 36, wherein

[0326] The activation or deactivation of the following items in the RLC status report corresponds to the first rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0327] Item 38. The communication method according to Item 36, wherein

[0328] The activation or deactivation of the following items in the RLC status report corresponds to the second rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0329] Item 39. A communication method according to any one of Items 36 to 38, wherein

[0330] Configuration or reconfiguration is performed by the receiver entity.

[0331] Item 40. A communication method according to any one of Items 36 to 38, wherein

[0332] Configuration or reconfiguration is performed by the transmitter entity by generating a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE) to generate configuration or reconfiguration rules, and by sending an RRC message or MAC CE to the receiver entity.

[0333] Item 41. The communication method according to Item 40, wherein

[0334] MAC CE is specified using the configured LCID value.

[0335] Item 42. A communication method according to any one of items 36 to 41, wherein

[0336] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0337] Project 43. A communication method, comprising:

[0338] The application uses rules relating to the content of Radio Link Control (RLC) status reports, which activate or deactivate at least one of the following in the RLC status report: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or the indication of RX_NEXT_HIGHEST in the first acknowledgment sequence number (ACK_SN) field of the RLC status report.

[0339] Item 44. The communication method according to Item 43, wherein the rule is applied by generating an RLC status report that includes at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, wherein the rule activates the RLC status report to include at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0340] Item 45. The communication method according to Item 43 or 44, wherein

[0341] The activation or deactivation of the following items in the RLC status report corresponds to the first rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0342] Item 46. The communication method according to Item 45, wherein the application of the first rule is performed by generating an RLC status report that includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, wherein the first rule activates the RLC status report to include the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0343] Item 47. The communication method according to Item 43 or 44, wherein

[0344] The activation or deactivation of the following items in the RLC status report corresponds to the second rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0345] Item 48. The communication method according to Item 47, wherein the application of the second rule is performed by generating an RLC status report that includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report, wherein the second rule activates the RLC status report to include the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0346] Item 49. The communication method according to any one of items 43 to 48 further includes: receiving from a transmitter entity a Radio Resource Control (RRC) message or a Medium Access Control (MAC) control element (CE), wherein the RRC message or MAC CE configures or reconfigures rules relating to the content of an RLC status report.

[0347] Item 50. The communication method according to Item 49, wherein

[0348] The configuration or reconfiguration rule is at least one of the first rule or the second rule.

[0349] Item 51. The communication method according to Item 49 or 50, wherein the MAC CE is specified using a configured LCID value.

[0350] Item 52. A communication device, comprising:

[0351] At least one processor; and

[0352] At least one memory stores instructions that, when executed by at least one processor, cause the communication device to configure or reconfigure rules relating to the content of a Radio Link Control (RLC) status report, the rules activating or deactivating at least one of the following in the RLC status report: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or the indication of RX_NEXT_HIGHEST in the first acknowledgment sequence number (ACK_SN) field of the RLC status report.

[0353] Item 53. The communication device according to Item 52, wherein...

[0354] The activation or deactivation of the following items in the RLC status report corresponds to the first rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0355] Item 54. The communication device according to Item 52, wherein

[0356] The activation or deactivation of the following items in the RLC status report corresponds to the second rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0357] Item 55. A communication device according to any one of items 52 to 54, wherein

[0358] A communication device is a receiver entity.

[0359] Item 56. The communication device according to any one of Items 52 to 54, wherein

[0360] The communication device is a transmitter entity; and

[0361] Configuration or reconfiguration is performed by generating Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CEs) that generate configuration or reconfiguration rules, and sending RRC messages or MAC CEs to the receiver entity.

[0362] Item 57. The communication device according to Item 56, wherein

[0363] MAC CE is specified using the configured LCID value.

[0364] Item 58. A communication device according to any one of items 52 to 57, wherein...

[0365] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0366] Item 59. A communication device, comprising:

[0367] At least one processor; and

[0368] At least one memory stores instructions that, when executed by at least one processor, cause the communication device to apply at least a rule relating to the content of a Radio Link Control (RLC) Status Report, which activates or deactivates at least one of the following in the RLC Status Report: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or the indication of RX_NEXT_HIGHEST in the first acknowledgment sequence number (ACK_SN) field of the RLC Status Report.

[0369] Item 60. The communication device according to Item 59, wherein a rule is applied by generating an RLC status report that includes at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, wherein the rule activates the RLC status report to include at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0370] Item 61. The communication device according to Item 59 or 60, wherein

[0371] The activation or deactivation of the following items in the RLC status report corresponds to the first rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0372] Item 62. The communication device according to Item 61, wherein the communication device applies a first rule by generating an RLC status report that includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, wherein the first rule activates the RLC status report to include the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0373] Item 63. The communication device according to Item 59 or 60, wherein

[0374] The activation or deactivation of the following items in the RLC status report corresponds to the second rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0375] Item 64. The communication device according to Item 63, wherein the communication device applies the second rule by generating an RLC status report that includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report, wherein the second rule is activated when the RLC status report includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0376] Item 65. The communication device according to any one of Items 59 to 64, wherein

[0377] When the instruction is executed by at least one processor, it also enables the communication device to:

[0378] Receive Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CEs) from the transmitter entity. These RRC messages or MAC CEs configure or reconfigure rules related to the content of the RLC status report.

[0379] Item 66. The communication device according to Item 65, wherein

[0380] The configuration or reconfiguration rule is at least one of the first rule or the second rule.

[0381] Item 67. A communication device according to Item 65 or 66, wherein the MAC CE is specified using a configured LCID value.

[0382] Item 68. A communication device, comprising:

[0383] A component for configuring or reconfiguring rules relating to the content of Radio Link Control (RLC) status reports, which activate or deactivate at least one of the following in the RLC status report: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or the indication of RX_NEXT_HIGHEST in the first acknowledgment sequence number (ACK_SN) field of the RLC status report.

[0384] Item 69. The communication device according to Item 68, wherein

[0385] The activation or deactivation of the following items in the RLC status report corresponds to the first rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0386] Item 70. The communication device according to Item 68, wherein

[0387] The activation or deactivation of the following items in the RLC status report corresponds to the second rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0388] Item 71. The communication device according to any one of Items 68 to 70, wherein

[0389] A communication device is a receiver entity.

[0390] Item 72. The communication device according to any one of Items 68 to 70, wherein

[0391] The communication device is a transmitter entity; and

[0392] The component used for configuration or reconfiguration performs configuration or reconfiguration by generating Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CEs) that generate configuration or reconfiguration rules, and sending RRC messages or MAC CEs to the receiver entity.

[0393] Item 73. The communication device according to Item 72, wherein

[0394] MAC CE is specified using the configured LCID value.

[0395] Item 74. The communication device according to any one of Items 68 to 73, wherein

[0396] Configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (PDCP) replication.

[0397] Item 75. A communication device, comprising:

[0398] A component for applying rules relating to the content of Radio Link Control (RLC) status reports, which activate or deactivate at least one of the following in the RLC status report: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or the indication of RX_NEXT_HIGHEST in the first acknowledgment sequence number (ACK_SN) field of the RLC status report.

[0399] Item 76. The communication device according to Item 75, wherein the application component is subject to a rule by generating an RLC status report that includes at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, wherein the rule activates the RLC status report to include at least one of the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, or an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0400] Item 77. The communication device according to Item 75 or 76, wherein

[0401] The activation or deactivation of the following items in the RLC status report corresponds to the first rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, and the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0402] Item 78. The communication device according to Item 77, wherein the application component applies a first rule by generating an RLC status report that includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, wherein the first rule activates the RLC status report to include the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, and an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report.

[0403] Item 79. The communication device according to Item 75 or 76, wherein

[0404] The activation or deactivation of the following items in the RLC status report corresponds to the second rule: the status of all RLC PDUs received at the receiver entity up to RX_NEXT_HIGHEST, the indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and the indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0405] Item 80. A communication device according to Item 79, wherein the communication device applies a second rule by generating an RLC status report that includes the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the communication device, an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and an indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report, wherein the second rule activates the RLC status report to include the following: the status of all RLC PDUs received up to RX_NEXT_HIGHEST at the receiver entity, an indication of RX_NEXT_HIGHEST in the first ACK_SN field of the RLC status report, and an indication of RX_HIGHEST_STATUS in the second ACK_SN field of the RLC status report.

[0406] Item 81. The communication apparatus according to any one of Items 75 to 80 further includes a component for receiving Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CEs) from a transmitter entity, wherein the RRC messages or MAC CEs configure or reconfigure rules relating to the content of an RLC status report.

[0407] Item 82. The communication device according to Item 81, wherein

[0408] The configuration or reconfiguration rule is at least one of the first rule or the second rule.

[0409] Item 83. The communication device according to Item 81 or 82, wherein the MAC CE is specified using a configured LCID value.

[0410] Item 84. A computer program product comprising an instruction set, which, when executed on a device, is configured to cause the device to perform any one of items 36 to 42 or 43 to 51.

[0411] Item 85. The computer program product according to Item 84 is embodied in a computer-readable medium or can be directly loaded into a computer.

[0412] Project 86. A communication method, comprising:

[0413] Receive at least one Radio Link Control (RLC) Protocol Data Unit (PDU) from the transmitter entity; and

[0414] A counter is incremented for each received RLC PDU.

[0415] Item 87. The communication method according to Item 86, wherein

[0416] The counter includes at least one of the following

[0417] The first counter is incremented by 1 for each received RLC PDU, or

[0418] A second counter is incremented by the size of each received RLC PDU.

[0419] Item 88. The communication method according to Item 87 further includes sending an RLC status report to the sender entity if at least one of the following threshold criteria for triggering an RLC status report is met:

[0420] The first counter is greater than the configured first threshold; or

[0421] The second counter is greater than the configured second threshold.

[0422] Item 89. The communication method according to Item 88 further includes: receiving from a transmitter entity a Radio Resource Control (RRC) message or a Medium Access Control (MAC) control element (CE), wherein the RRC message or MAC CE configures or reconfigures at least one of a first threshold or a second threshold.

[0423] Item 90. The communication method according to Item 89, wherein

[0424] MAC CE is specified using the configured LCID value.

[0425] Item 91. The communication method according to any one of Items 86 to 90 further includes performing at least one of the following when an RLC status report is triggered:

[0426] Reset the first counter to 0, or

[0427] Reset the second counter to 0.

[0428] Item 92. The communication method according to Item 91, wherein

[0429] The RLC status report is triggered based on at least one of the following:

[0430] The polling bit set in the received RLC PDU

[0431] The expiration of the reassembly timer, which is initiated at the communication device upon detection of at least partial loss of the RLC PDU.

[0432] The first counter is greater than the configured first threshold.

[0433] The second counter is greater than the configured second threshold, or

[0434] The timer value is greater than the configured timer threshold. This timer is started at the communication device after receiving at least one RLC PDU if the timer is not running.

[0435] Project 93. A communication method, comprising:

[0436] Receive at least one Radio Link Control (RLC) Protocol Data Unit (PDU) from the transmitter entity; and

[0437] If the timer is not running after receiving at least one RLC PDU, then start the timer.

[0438] Item 94. The communication method according to Item 93 further includes sending an RLC status report to the sender entity if the following threshold criteria for triggering an RLC status report are met:

[0439] The timer value is greater than the configured timer threshold.

[0440] Item 95. The communication method according to Item 94 further includes: receiving a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE) from a transmitter entity, the transmitter entity configuring or reconfiguring a timer threshold.

[0441] Item 96. The communication method according to Item 95, wherein

[0442] MAC CE is specified using the configured LCID value.

[0443] Item 97. The communication method according to any one of items 93 to 96 further includes performing the following operations when an RLC status report is triggered:

[0444] Stop the timer and reset it to 0.

[0445] Item 98. The communication method according to Item 97, wherein

[0446] The RLC status report is triggered based on at least one of the following:

[0447] The polling bit set in the received RLC PDU

[0448] The expiration of the reassembly timer, which is initiated at the communication device upon detection of at least partial loss of the RLC PDU.

[0449] When the first counter is greater than the configured first threshold, the first counter is incremented by 1 for each received RLC PDU.

[0450] When the second counter is greater than the configured second threshold, the second counter is incremented by the size of each received RLC PDU, or

[0451] The timer value is greater than the configured timer threshold.

[0452] Item 99. A communication device, comprising:

[0453] At least one processor; and

[0454] At least one memory storing instructions that, when executed by at least one processor, cause the communication device to at least:

[0455] Receive at least one Radio Link Control (RLC) Protocol Data Unit (PDU) from the transmitter entity; and

[0456] A counter is incremented for each received RLC PDU.

[0457] Item 100. The communication device according to Item 99, wherein

[0458] The counter includes at least one of the following

[0459] The first counter is incremented by 1 for each received RLC PDU, or

[0460] A second counter is incremented by the size of each received RLC PDU.

[0461] Item 101. The communication device according to Item 100, wherein when an instruction is executed by at least one processor, the communication device further causes to send an RLC status report to a transmitter entity if at least one of the following threshold criteria for triggering an RLC status report is met:

[0462] The first counter is greater than the configured first threshold; or

[0463] The second counter is greater than the configured second threshold.

[0464] Item 102. The communication device according to Item 101, wherein when the instruction is executed by the at least one processor, the communication device further causes:

[0465] The transmitter entity receives a Radio Resource Control (RRC) message or a Medium Access Control (MAC) control element (CE), which configures or reconfigures at least one of a first threshold or a second threshold.

[0466] Item 103. The communication device according to Item 102, wherein

[0467] MAC CE is specified using the configured LCID value.

[0468] Item 104. A communication device according to any one of items 99 to 103, wherein when the instruction is executed by at least one processor, the communication device further causes to perform at least one of the following when an RLC status report is triggered:

[0469] Reset the first counter to 0, or

[0470] Reset the second counter to 0.

[0471] Item 105. The communication device according to Item 104, wherein

[0472] The RLC status report is triggered based on at least one of the following:

[0473] The polling bit set in the received RLC PDU

[0474] The expiration of the reassembly timer, which is initiated at the communication device upon detection of at least partial loss of the RLC PDU.

[0475] The first counter is greater than the configured first threshold.

[0476] The second counter is greater than the configured second threshold, or

[0477] The timer value is greater than the configured timer threshold. This timer is started at the communication device after receiving at least one RLC PDU if the timer is not running.

[0478] Item 106. A communication device, comprising:

[0479] At least one processor; and

[0480] At least one memory storing instructions that, when executed by at least one processor, cause the communication device to at least:

[0481] Receive at least one Radio Link Control (RLC) Protocol Data Unit (PDU) from the transmitter entity; and

[0482] If the timer is not running after receiving at least one RLC PDU, then start the timer.

[0483] Item 107. The communication device according to Item 106, wherein when the instruction is executed by at least one processor, the communication device further causes to send an RLC status report to the transmitter entity if the following threshold criteria for triggering an RLC status report are met:

[0484] The timer value is greater than the configured timer threshold.

[0485] Item 108. The communication device according to Item 107, wherein when the instructions are executed by at least one processor, the communication device further causes:

[0486] The transmitter entity receives Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CE) from the transmitter entity, which configures or reconfigures timer thresholds.

[0487] Item 109. The communication device according to Item 108, wherein

[0488] MAC CE is specified using the configured LCID value.

[0489] Item 110. A communication device according to any one of items 106 to 109, wherein when the instruction is executed by at least one processor, the communication device further causes to perform the following operation when an RLC status report is triggered:

[0490] Stop the timer and reset it to 0.

[0491] Item 111. The communication device according to Item 110, wherein

[0492] The RLC status report is triggered based on at least one of the following:

[0493] The polling bit set in the received RLC PDU

[0494] The expiration of the reassembly timer, which is initiated at the communication device upon detection of at least partial loss of the RLC PDU.

[0495] When the first counter is greater than the configured first threshold, the first counter is incremented by 1 for each received RLC PDU.

[0496] When the second counter is greater than the configured second threshold, the second counter is incremented by the size of each received RLC PDU, or

[0497] The timer value is greater than the configured timer threshold.

[0498] Item 112. A communication device, comprising:

[0499] Components for receiving at least one Radio Link Control (RLC) Protocol Data Unit (PDU) from a transmitter entity; and

[0500] A component used to increment a counter for each received RLC PDU.

[0501] Item 113. The communication device according to Item 112, wherein

[0502] The counter includes at least one of the following

[0503] The first counter is incremented by 1 for each received RLC PDU, or

[0504] A second counter is incremented by the size of each received RLC PDU.

[0505] Item 114. The communication device according to Item 113 further includes a component for sending an RLC status report to a transmitter entity if at least one of the following threshold criteria for triggering an RLC status report is met:

[0506] The first counter is greater than the configured first threshold; or

[0507] The second counter is greater than the configured second threshold.

[0508] Item 115. The communication apparatus according to Item 114 further includes components for receiving a Radio Resource Control (RRC) message or a Medium Access Control (MAC) control element (CE) from a transmitter entity, wherein the RRC message or MAC CE configures or reconfigures at least one of a first threshold or a second threshold.

[0509] Item 116. The communication device according to Item 115, wherein

[0510] MAC CE is specified using the configured LCID value.

[0511] Item 117. The communication device according to any one of items 112 to 116 further includes a component for performing at least one of the following when an RLC status report is triggered:

[0512] Reset the first counter to 0, or

[0513] Reset the second counter to 0.

[0514] Item 118. The communication device according to Item 117, wherein

[0515] The RLC status report is triggered based on at least one of the following:

[0516] The polling bit set in the received RLC PDU

[0517] The expiration of the reassembly timer, which is initiated at the communication device upon detection of at least partial loss of the RLC PDU.

[0518] The first counter is greater than the configured first threshold.

[0519] The second counter is greater than the configured second threshold, or

[0520] The timer value is greater than the configured timer threshold. This timer is started at the communication device after receiving at least one RLC PDU if the timer is not running.

[0521] Item 119. A communication device, comprising:

[0522] Components for receiving at least one Radio Link Control (RLC) Protocol Data Unit (PDU) from a transmitter entity; and

[0523] A component for starting a timer if it is not running, after receiving at least one RLC PDU.

[0524] Item 120. The communication device according to Item 119 further includes a component for sending an RLC status report to a transmitter entity if the following threshold criteria for triggering an RLC status report are met:

[0525] The timer value is greater than the configured timer threshold.

[0526] Item 121. The communication device according to Item 120 further includes components for receiving Radio Resource Control (RRC) messages or Media Access Control (MAC) control elements (CEs) from a transmitter entity, which configures or reconfigures timer thresholds.

[0527] Item 122. The communication device according to Item 121, wherein

[0528] MAC CE is specified using the configured LCID value.

[0529] Item 123. The communication device according to any one of items 112 to 122 further includes a component for performing the following operations when an RLC status report is triggered:

[0530] Stop the timer and reset it to 0.

[0531] Item 124. The communication device according to Item 123, wherein

[0532] The RLC status report is triggered based on at least one of the following:

[0533] The polling bit set in the received RLC PDU

[0534] The expiration of the reassembly timer, which is initiated at the communication device upon detection of at least partial loss of the RLC PDU.

[0535] When the first counter is greater than the configured first threshold, the first counter is incremented by 1 for each received RLC PDU.

[0536] When the second counter is greater than the configured second threshold, the second counter is incremented by the size of each received RLC PDU, or

[0537] The timer value is greater than the configured timer threshold.

[0538] Item 125. A computer program product comprising an instruction set that, when executed on a device, is configured to cause the device to perform the method according to any one of items 86 to 92 or 93 to 98.

[0539] Item 126. The computer program product according to Item 125 is embodied in a computer-readable medium or can be directly loaded into a computer.

Claims

1. A communication method, comprising: Configure or reconfigure parameters related to the triggering of Radio Link Control (RLC) Status Reports at the receiver entity, including a threshold indicating the maximum value of RLC Protocol Data Units (PDUs) received by the receiver entity to trigger an RLC Status Report.

2. The communication method according to claim 1, wherein... The maximum value of the RLC PDU received by the receiver entity to trigger the RLC status report includes at least one of the following: The maximum number of RLC PDUs received by the receiver entity, or The maximum number of bytes received by the receiver entity.

3. The communication method according to claim 1 or 2, wherein... The configuration or reconfiguration is performed by the receiver entity; or The configuration or reconfiguration is performed by the transmitter entity by: generating a Radio Resource Control (RRC) message or a Medium Access Control (MAC) Control Element (CE) to configure or reconfigure the parameters, and sending the RRC message or the MAC CE to the receiver entity, wherein the MAC CE is specified using a configured LCID value.

4. The communication method according to any one of claims 1 to 2, wherein The configuration or reconfiguration is triggered by activating or deactivating the Packet Data Convergence Protocol (DPCP) replication.

5. A communication method, comprising: Configure or reconfigure parameters related to the triggering of Radio Link Control (RLC) status reports at the receiver entity, including a threshold indicating the maximum time elapsed since the RLC PDU was received by the receiver entity to trigger an RLC status report.

6. The communication method according to claim 5, wherein The configuration or reconfiguration is performed by the receiver entity.

7. The communication method according to claim 5 or 6, wherein The configuration or reconfiguration is performed by the transmitter entity by: generating a Radio Resource Control (RRC) message or a Medium Access Control (MAC) Control Element (CE) to configure or reconfigure the parameters, and sending the RRC message or the MAC CE to the receiver entity. The MAC CE mentioned above is specified using the configured LCID value.

8. The communication method according to any one of claims 5 to 6, wherein The configuration or reconfiguration is triggered by activating or deactivating Packet Data Convergence Protocol (DPCP) replication.

9. A communication device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the communication device to configure or reconfigure parameters related to the triggering of a Radio Link Control (RLC) Status Report at a receiver entity, the parameters including a threshold indicating the maximum value of an RLC Protocol Data Unit (PDU) received by the receiver entity to trigger the RLC Status Report.

10. A communication device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the communication device to configure or reconfigure parameters related to the triggering of a radio link control (RLC) status report at a receiver entity, the parameters including a threshold indicating a maximum value of time elapsed since the RLC PDU was received by the receiver entity to trigger the RLC status report.

Images