Processing methods and apparatuses, and storage medium

Abstract

The present disclosure relates to processing methods and apparatuses, and a storage medium. A processing method comprises: on the basis of the first amount of received data, determining whether to trigger a status report, the status report being used for indicating the status of reception of the data by a first entity. In the embodiment, the problem of excessive delay is solved, and whether to trigger a status report is determined on the basis of the amount of data received by a first entity, thereby ensuring the accuracy in status report triggering and further ensuring the accuracy in performing retransmission on the basis of the status report, and thus ensuring the communication reliability.

Description

Processing method, device and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a processing method, device, and storage medium. Background Art

[0002] With the rapid development of mobile communication technology, a method for transmitting RLC reports through RLC entity polling has been provided, so that whether to trigger retransmission can be determined based on the RLC report. However, operations performed in a polling manner will cause delays.

[0003] Summary of the Invention

[0004] The solution provided by the present disclosure solves the problem of excessive latency, determines whether to trigger a status report based on the amount of data received by the first entity, ensures the accuracy of the triggered status report, further ensures the accuracy of retransmission based on the status report, and ensures communication reliability.

[0005] The embodiments of the present disclosure provide a processing method, an apparatus, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a processing method is proposed, the method comprising:

[0007] The first entity determines whether to trigger a status report based on a first amount of received data, where the status report is used to indicate a situation in which the first entity receives the data.

[0008] According to a second aspect of the embodiments of the present disclosure, a processing method is proposed, the method comprising:

[0009] The second entity receives a status report, where the status report is used to indicate a situation in which the first entity receives data.

[0010] According to a third aspect of the embodiments of the present disclosure, a processing method is proposed, the method comprising:

[0011] The first entity determines, based on a first amount of received data, whether to trigger a status report, where the status report is used to indicate a situation in which the first entity receives the data;

[0012] The second entity receives the status report.

[0013] According to a fourth aspect of an embodiment of the present disclosure, a processing device is provided, including:

[0014] The processing module is configured to determine, by the first entity, whether to trigger a status report based on a first amount of received data, where the status report is used to indicate a situation in which the first entity receives the data.

[0015] According to a fifth aspect of an embodiment of the present disclosure, a processing device is provided, including:

[0016] The transceiver module is used for the second entity to receive a status report, where the status report is used to indicate a situation in which the first entity receives data.

[0017] According to a sixth aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0018] one or more first entities;

[0019] The first entity is used to execute any method described in the first aspect.

[0020] According to a seventh aspect of an embodiment of the present disclosure, a network device is provided, including:

[0021] one or more second entities;

[0022] The second entity is used to execute any method described in the second aspect.

[0023] According to an eighth aspect of an embodiment of the present disclosure, a communication system is provided, including:

[0024] A terminal and a network device, wherein the terminal is configured to implement the processing method described in the first aspect, and the network device is configured to implement the processing method described in the second aspect.

[0025] According to a ninth aspect of an embodiment of the present disclosure, a storage medium is proposed, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes a method as described in any one of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings described herein are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the present disclosure. The illustrative embodiments of the embodiments of the present disclosure and their descriptions are used to explain the embodiments of the present disclosure and do not constitute an improper limitation on the embodiments of the present disclosure. In the drawings:

[0027] FIG1A is a schematic diagram illustrating an architecture of a communication system according to an embodiment of the present disclosure;

[0028] FIG1B is a structural diagram of data according to an embodiment of the present disclosure;

[0029] FIG2A is an interactive schematic diagram illustrating a processing method according to an embodiment of the present disclosure;

[0030] FIG2B is a structural diagram of a status report according to an embodiment of the present disclosure;

[0031] FIG3A is a schematic flow chart of a processing method according to an embodiment of the present disclosure;

[0032] FIG3B is a flow chart of a processing method according to an embodiment of the present disclosure;

[0033] FIG4A is a schematic flow chart of a processing method according to an embodiment of the present disclosure;

[0034] FIG4B is a flow chart of a processing method according to an embodiment of the present disclosure;

[0035] FIG5 is a flow chart of a processing method according to an embodiment of the present disclosure;

[0036] FIG6 is a flow chart of a processing method according to an embodiment of the present disclosure;

[0037] FIG7A is a schematic structural diagram of a first entity proposed in an embodiment of the present disclosure;

[0038] FIG7B is a schematic structural diagram of a second entity proposed in an embodiment of the present disclosure;

[0039] FIG8A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0040] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] The present disclosure provides a processing method, an apparatus, and a storage medium.

[0042] According to a first aspect of an embodiment of the present disclosure, a processing method is provided. The method is performed by a first entity and includes:

[0043] The first entity determines whether to trigger a status report based on a first amount of received data, where the status report is used to indicate a situation in which the first entity receives the data.

[0044] In the above embodiment, the problem of excessive latency is solved. Whether to trigger a status report is determined based on the amount of data received by the first entity, thereby ensuring the accuracy of the triggered status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first quantity refers to the data volume of the data, and the first entity determines whether to trigger a status report based on the first quantity of received data, including:

[0046] The first entity determines whether to trigger the status report based on the data volume of the received data.

[0047] In the above embodiment, whether to trigger the status report is determined by the amount of received data, thereby ensuring the accuracy of determining whether to trigger the status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the first entity determines whether to trigger the status report based on the amount of the received data, including:

[0049] If the amount of the data received by the first entity is greater than a first threshold, triggering the status report; or,

[0050] If the amount of the data received by the first entity is not greater than the first threshold, the status report is not triggered.

[0051] In the above embodiment, whether to trigger the status report is determined based on the relationship between the data volume and the threshold, thereby ensuring the accuracy of determining whether to trigger the status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the data includes an RLC SDU (Service Data Unit) and / or an RLC SDU segment, and the data amount includes the data amount of the RLC SDU and / or the RLC SDU segment; or,

[0053] The data includes an RLC data PDU (Protocol Data Unit), and the data amount includes the data amount of the RLC data PDU; or

[0054] The data includes an RLC PDU, and the data amount includes the data amount of the RLC PDU.

[0055] For AM (Acknowledged Mode) RLC entities, the RLC data PDU is called AMD PDU. In the following description of this patent, RLC data PDU is mainly used.

[0056] In the above embodiment, the definition of the data volume is expanded, thereby expanding the diversity of determining whether to trigger the status report, ensuring the accuracy of determining whether to trigger the status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0058] The terminal receives first information, where the first information is used to configure the first threshold; or,

[0059] The first threshold is defined by a communication protocol; or,

[0060] The first threshold is one of candidate thresholds preconfigured by the terminal.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the first number refers to the number of data packets carrying the data, and the first entity determines whether to trigger a status report based on the first number of received data, including:

[0062] The first entity determines whether to trigger the status report based on the number of received data packets carrying the data.

[0063] In the above embodiment, whether to trigger the status report is determined based on the number of data packets, thereby ensuring the accuracy of determining whether to trigger the status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the first entity determines whether to trigger the status report based on the number of received data packets carrying the data, including:

[0065] If the number of data packets carrying the data received by the first entity is greater than a second threshold, triggering the status report; or,

[0066] If the number of data packets carrying the data received by the first entity is not greater than the second threshold, the status report is not triggered.

[0067] In the above embodiment, whether to trigger the status report is determined based on the relationship between the number of data packets and the threshold, thereby ensuring the accuracy of determining whether to trigger the status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the number of data packets is based on RLC SDU counting; or,

[0069] The number of data packets is counted based on the number of RLC data PDUs; or

[0070] The number of data packets is counted based on the number of RLC PDUs.

[0071] In the above embodiment, the definition of the number of data packets is expanded, thereby expanding the diversity of determining whether to trigger a status report, ensuring the accuracy of determining whether to trigger a status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0073] The terminal receives second information sent by the network device, where the second information is used to configure the second threshold; or,

[0074] The second threshold is defined by a communication protocol; or,

[0075] The second threshold is one of candidate thresholds preconfigured by the terminal.

[0076] In combination with some embodiments of the first aspect, in some embodiments, the first entity includes a counter, and the counter is used to count the received data.

[0077] In the above embodiment, data is counted by a counter to ensure the accuracy of the counting, thereby ensuring the accuracy of the subsequent determination of whether to trigger a status report based on the counting result.

[0078] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0079] The first entity determines to trigger the status report and resets the counter to 0.

[0080] In combination with some embodiments of the first aspect, in some embodiments, the first entity is an RLC entity.

[0081] In combination with some embodiments of the first aspect, in some embodiments, the status report is an RLC status report.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0083] Determining to trigger the status report;

[0084] The status report is sent to the second entity.

[0085] In conjunction with some embodiments of the first aspect, in some embodiments, the situation in which the first entity receives the data includes:

[0086] Among the data received by the first entity, first data is received correctly; and / or second data is not received correctly; and / or whether the first entity receives the data correctly.

[0087] In a second aspect, an embodiment of the present disclosure provides a processing method, which is performed by a second entity and includes:

[0088] The second entity receives a status report sent by the first entity, where the status report is used to indicate a situation in which the first entity receives data.

[0089] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0090] The network device sends first information, where the first information is used to configure a first threshold; or,

[0091] The first threshold is defined by a communication protocol; or,

[0092] The first threshold is one of candidate thresholds preconfigured by the terminal;

[0093] The first threshold is used by the first entity to determine whether to send the status report.

[0094] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0095] The network device sends second information, where the second information is used to configure a second threshold; or,

[0096] The second threshold is defined by a communication protocol; or,

[0097] The second threshold is one of candidate thresholds preconfigured by the terminal;

[0098] The second threshold is used by the first entity to determine whether to send the status report.

[0099] In combination with some embodiments of the second aspect, in some embodiments, the second entity is an RLC entity.

[0100] In combination with some embodiments of the second aspect, in some embodiments, the status report is an RLC status report.

[0101] In conjunction with some embodiments of the second aspect, in some embodiments, the situation in which the first entity receives the data includes:

[0102] Among the data received by the first entity, first data is received correctly; and / or second data is not received correctly; and / or whether the first entity receives the data correctly.

[0103] In a third aspect, an embodiment of the present disclosure provides a processing method, the method comprising:

[0104] The first entity determines, based on a first amount of received data, whether to trigger a status report, where the status report is used to indicate a situation in which the first entity receives the data;

[0105] The second entity receives the status report.

[0106] In a fourth aspect, an embodiment of the present disclosure provides a first entity, which includes at least one of a transceiver module and a processing module; wherein the first entity is used to execute the optional implementation method of the first aspect.

[0107] In a fifth aspect, an embodiment of the present disclosure provides a second entity, which includes at least one of a transceiver module and a processing module; wherein the second entity is used to execute the optional implementation method of the second aspect.

[0108] In a sixth aspect, an embodiment of the present disclosure provides a terminal, including:

[0109] one or more first entities;

[0110] The first entity is configured to execute any one of the methods described in the first aspect.

[0111] In a seventh aspect, an embodiment of the present disclosure provides a network device, including:

[0112] one or more second entities;

[0113] The second entity is used to execute any one of the methods in the second aspect.

[0114] In an eighth aspect, an embodiment of the present disclosure provides a storage medium storing first information. When the first information is run on a communication device, the communication device executes a method as described in any one of the first aspect or the second aspect.

[0115] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method as described in any one of the first aspect or the second aspect.

[0116] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a communication device, enables the communication device to execute the method described in any one of the first aspect or the second aspect.

[0117] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute any one of the methods described in the first aspect or the second aspect.

[0118] It is understandable that the above-mentioned terminals, storage media, program products, computer programs, chips or chip systems are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0119] The present disclosure provides processing methods, devices, and storage media. In some embodiments, the terms "processing method," "information processing method," and "processing method" are interchangeable; the terms "processing device," "information processing device," and "processing device" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

[0120] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0121] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0122] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0123] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0124] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0125] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0126] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0127] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0128] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0129] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0130] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

[0131] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0132] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0133] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0134] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0135] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0136] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (terminal)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0137] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0138] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0139] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0140] FIG1A is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , the method provided in the embodiment of the present disclosure can be applied to a communication system 100, which may include a terminal 101 and a network device 102. It should be noted that the communication system 100 may also include other devices, and the present disclosure does not limit the devices included in the communication system 100.

[0141] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0142] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0143] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0144] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0145] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0146] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0147] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0148] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0149] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other processing methods, and next-generation systems based on and extending these systems. Furthermore, a combination of multiple systems (e.g., a combination of LTE or LTE-A with 5G) may also be employed.

[0150] In some embodiments, both the terminal 101 and the network device 102 are provided with an RLC entity that can perform data transmission. Optionally, the RLC entity can be configured in three modes, including transparent mode (TM), unacknowledged mode (UM), or acknowledged mode (AM). Correspondingly, the RLC entity can be classified as a TM RLC entity, a UM RLC entity, or an AM RLC entity. It should be noted that the present disclosure relates to an AM RLC entity.

[0151] In some embodiments, an AM RLC entity consists of a transmitting side and a receiving side. That is, the RLC entity of the terminal 101 includes a transmitting side and a receiving side, and the RLC entity of the network device 102 also includes a transmitting side and a receiving side.

[0152] In some embodiments, RLC AM supports ARQ (Automatic Repeat Request) functionality. RLC status reports can be triggered by: 1) polling by the peer AM RLC entity; 2) detection of an AMD PDU reception failure: When a timer expires, the receiving side of the AM RLC entity triggers an RLC status report. ARQ retransmits the RLC SDU or RLC SDU segment based on the RLC status report.

[0153] In some embodiments, RLC PDUs are divided into RLC data PDUs and RLC control PDUs. RLC data PDUs are used to transmit higher-layer PDUs (i.e., RLC SDUs). RLC data PDUs in AM mode are called AMD PDUs. RLC control PDUs are used for ARQ. The RLC status report described above is an RLC control PDU.

[0154] In some embodiments, referring to FIG. 1B , the format of the AMD PDU is as follows, wherein the data mapped to the Data field is the data sent from the PDCP layer to the RLC layer, ie, the RLC SDU or an RLC SDU segment.

[0155] In some embodiments, if the network device 102 is configured with an RLC entity, the terminal 101 will configure a peer RLC entity corresponding to the network device 102. Alternatively, if the terminal 101 is configured with an RLC entity, the network device 102 will configure a peer RLC entity corresponding to the terminal 101.

[0156] In some embodiments, if the RLC entity receives an RLC SDU from a higher layer, the RLC entity sends an RLC PDU to the peer RLC entity via a lower layer. In some embodiments, if the RLC entity sends an RLC SDU to a higher layer, the RLC entity needs to receive an RLC PDU from the peer RLC entity.

[0157] It should be noted that if the space provided by the MAC layer is unable to transmit a complete RLC SDU, the RLC SDU will be segmented, and the segmented RLC SDU segments will be transmitted.

[0158] In some embodiments, the ARQ function of RLC AM in the related art cannot support low-latency services. For example, there is a certain delay in the processing of polling, and the delay for detecting the reception failure of AMD PDU is also relatively large. Therefore, if the RLC SDU or RLC SDU segment is triggered to be retransmitted based on the RLC status report, the delay will also be relatively large. Therefore, the present disclosure proposes a solution for determining whether to trigger an RLC status report based on the amount of received data. When the amount of received data reaches a certain value, the status report can be triggered. There is no need to trigger the status report through polling or determining the reception failure of AMD PDU, thereby avoiding the delay of polling or reception failure of AMD PDU, thereby solving the problem of excessive delay, and indicating whether to retransmit data by triggering the status report, thereby ensuring the accuracy of retransmission based on the status report, thereby ensuring communication reliability.

[0159] FIG2A is an interactive diagram of a processing method according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a processing method, which includes:

[0160] Step S2101: The network device sends configuration information.

[0161] In some embodiments, the terminal receives the configuration information. In some embodiments, the above step S2101 may also be: the network device sends the configuration information to the terminal. Correspondingly, the terminal receives the configuration information sent by the network device.

[0162] In some embodiments, the configuration information is at least one of the first information or the second information. Optionally, the first information is used to configure a first threshold. In some embodiments, the first threshold is used by the first entity to determine whether to trigger a status report based on the amount of received data. Alternatively, it can be understood that the first threshold is a judgment condition for the first entity, and whether to trigger a status report can be determined based on the first threshold. Optionally, the second information is used to configure a second threshold. In some embodiments, the second threshold is used by the first entity to determine whether to trigger a status report based on the number of data packets of received data. Alternatively, it can be understood that the second threshold is a judgment condition for the first entity, and whether to trigger a status report can be determined based on the second threshold.

[0163] In some embodiments, the terminal includes one or more first entities. Optionally, the above configuration information is used to configure the first threshold and / or second threshold corresponding to the one or more first entities. Optionally, the above configuration information is used to configure the first threshold and / or second threshold for each first entity respectively. Alternatively, it can be understood that the configurations of different first entities in the terminal are different. Optionally, the above configuration information is used to configure the first threshold and / or second threshold for multiple first entities at the same time. Alternatively, it can be understood that the configurations of multiple first entities are the same. Alternatively, the configuration information can configure the first threshold and / or second threshold for all or part of the first entities of the terminal.

[0164] In some embodiments, if the terminal includes multiple first entities, each first entity in the terminal performs subsequent steps independently based on its own configuration.

[0165] In some embodiments, the first entity is an RLC entity. Optionally, the RLC entity is an AM RLC entity.

[0166] In some embodiments, the network device includes one or more second entities. Optionally, the configurations of the multiple second entities may be the same or different, which is not limited in the embodiments of the present disclosure.

[0167] In some embodiments, the second entity is an RLC entity. Optionally, the RLC entity is an AM RLC entity.

[0168] It should be noted that the first information and the second information in the embodiment of the present disclosure may be the same information, or two different pieces of information, and the embodiment of the present disclosure is not limited thereto.

[0169] It should be noted that the embodiments of this disclosure are described using an example in which a terminal includes one or more first entities and a network device includes one or more second entities. In another embodiment, the terminal includes one or more second entities and the network device includes one or more first entities. Alternatively, the embodiments of this disclosure are described using an example in which a terminal includes one or more first entities and a network device includes one or more second entities.

[0170] It should be noted that the embodiment of the present disclosure uses step S2101 as an example for illustration. In another embodiment, step S2101 is optional. In another embodiment, step S2101 may not be performed, and the first threshold and the second threshold may be determined in other ways.

[0171] In some embodiments, the first threshold is defined by a communication protocol. Alternatively, the second threshold is agreed upon by the communication protocol.

[0172] In some embodiments, the first threshold is one of the candidate thresholds preconfigured by the terminal. In some embodiments, the second threshold is one of the candidate thresholds preconfigured by the terminal. Optionally, the terminal is preconfigured with multiple candidate thresholds, and the terminal can select a candidate threshold as the first threshold or the second threshold.

[0173] In the embodiment of the present disclosure, a first threshold value and / or a second threshold value is configured for a terminal through a network device so that the first entity in a subsequent terminal can determine whether to trigger a status report, thereby achieving the effect of the network device instructing the terminal to trigger a status report through the configured threshold value, and providing a new way for the terminal to trigger a status report. Since the status report is triggered by the threshold value configured by the network device for the terminal, the delay of the terminal triggering the status report is reduced, and the efficiency of the terminal triggering the status report is improved, thereby ensuring the efficiency of data retransmission and ensuring communication reliability.

[0174] Step S2102: The second entity sends data.

[0175] In some embodiments, the first entity receives data. In some embodiments, the above step S2102 may also be: the second entity sends data to the first entity. Correspondingly, the first entity receives the data sent by the second entity.

[0176] In some embodiments, the network device includes one or more second entities. Accordingly, the above steps may be replaced by: the network device sends data. Alternatively, the second entity of the network device sends data. In some embodiments, the terminal includes one or more first entities, that is, the terminal receives data. Alternatively, the first entity of the terminal receives data.

[0177] In some embodiments, the second entity is an RLC entity. Optionally, the data received by the second entity at the upper layer can be referred to as an RLC SDU or an RLC SDU segment. It can also be understood that the data sent by the second entity is an RLC SDU or an RLC SDU segment. Optionally, the second entity encapsulates the RLC SDU or RLC SDU segment to obtain an RLC PDU, and then sends the RLC PDU to the lower layer.

[0178] In some embodiments, the first entity is an RLC entity. Optionally, the first entity receives an RLC PDU at a lower layer and then processes the RLC PDU to obtain an RLC SDU or an RLC SDU segment.

[0179] In some embodiments, the first entity is an AM RLC entity. Optionally, for an AM RLC entity, an RLC data PDU is referred to as an AMD PDU, and the following description mainly uses the RLC data PDU.

[0180] Step S2103: The first entity determines whether to trigger a status report based on a first amount of received data.

[0181] In the embodiment of the present disclosure, the amount of data received by the first entity is different, and whether to trigger a status report is determined according to the amount of data.

[0182] In some embodiments, the terminal includes one or more first entities, and different first entities can respectively perform the above step S2103.

[0183] In the embodiment of the present disclosure, whether to trigger a status report is determined based on the amount of data received by the first entity, thereby ensuring the accuracy of the triggered status report and further ensuring the accuracy of retransmission based on the status report, solving the problem of excessive latency and ensuring the timeliness of communication.

[0184] In some embodiments, the status report is an RLC status report. Optionally, the above step S2102 is replaced by the first entity determining whether to trigger the RLC status report based on the first amount of received data.

[0185] In some embodiments, the first quantity may be the amount of data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the amount of received data.

[0186] In some embodiments, the status report is used to indicate a situation in which the first entity receives data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received; and / or which data is not correctly received; and / or whether the first entity receives the data correctly. Among them, the first data refers to the data correctly received by the first entity; the second data refers to the data not correctly received. The first data and the second data in the embodiments of the present disclosure are examples, and the first data and the second data are both used to indicate a type of data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received; and / or which data is not correctly received; and / or whether the first entity receives the data correctly.

[0187] Optionally, the data is an RLC SDU or an RLC SDU segment. For example, if the data is an RLC SDU, the first entity receiving the data refers to which RLC SDUs the first entity has received and / or which RLC SDUs it has not received. For another example, if the data is an RLC SDU segment, the first entity receiving the data refers to which RLC SDU segments the first entity has received and / or which RLC SDU segments it has not received.

[0188] In some embodiments, the format of the status report is shown in FIG2B . The D / C in the status report is C, which can also be understood as a control message. The CPT field is used to identify different types of control messages. ACK_SN and subsequent messages are not received. E1 indicates whether a NACK_SN, E1, E2, and E3 fields follow. NACK_SN marks a lost message that has not been received. E2 identifies whether SoStart and SoEnd follow, and is mainly used to handle incomplete message reception scenarios. The E3 field indicates whether a message about a series of RLC SDUs not being received follows. The NACK range field indicates how many consecutive RLC SDUs are lost starting from the NACK_SN. SoStart and SoEnd indicate a portion of the SDU of the NACK_SN that is found to be lost by the RLC receiving end. The value of SoStart indicates which byte of the original SDU the lost SDU portion starts at, and SoEnd indicates which byte it ends at.

[0189] In some embodiments, the amount of data received by the first entity is greater than a first threshold, triggering a status report. In an embodiment of the present disclosure, the amount of data received by the first entity is greater than the first threshold, which indicates that the amount of data received by the first entity is large, and a status report is triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, the first threshold is 20,000 bytes, 50,000 bytes, or other values. In some embodiments, the first threshold is 50,000 bytes, and the amount of data received by the first entity is 80,000 bytes, which indicates that it is greater than the first threshold, triggering a status report.

[0190] In some embodiments, if the amount of data received by the first entity is not greater than the first threshold, a status report is not triggered. In an embodiment of the present disclosure, if the amount of data received by the first entity is not greater than the first threshold, it means that the amount of data received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, if the first threshold is 20,000 bytes, 50,000 bytes or other values. In some embodiments, if the first threshold is 50,000 bytes and the amount of data received by the first entity is 30,000 bytes, it means that it is not greater than the first threshold, and a status report is triggered.

[0191] In the embodiment of the present disclosure, whether to trigger a status report is determined based on the relationship between the data volume and the threshold, thereby ensuring the accuracy of determining whether to trigger a status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0192] In some embodiments, the data includes an RLC SDU and / or an RLC SDU segment, and the data amount includes the data amount of the RLC SDU and / or the RLC SDU segment. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU.

[0193] In some embodiments, the data includes an RLC data PDU, and the data amount includes the data amount of the RLC data PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU and the data amount of the RLC data PDU header.

[0194] In some embodiments, the data received by the first entity is RLC PDU, and the first entity processes the received RLC PDU to obtain RLC SDU. Therefore, the first entity can determine whether to trigger a status report based on the number of RLC PDUs, or determine whether to trigger a status report based on the number of RLC SDUs.

[0195] In some embodiments, the data includes an RLC PDU, and the data amount includes the data amount of the RLC PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU, the RLC data PDU header, and the data amount of the RLC control PDU.

[0196] In the embodiment of the present disclosure, the definition of the data volume is expanded, thereby expanding the diversity of determining whether to trigger the status report, ensuring the accuracy of determining whether to trigger the status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0197] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the amount of received data is counted by the counter. In some embodiments, the counter is used to count the amount of data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the amount of data of the received RLC PDU is counted by the counter, and when the amount of data counted by the counter is greater than a first threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0198] In some embodiments, the first number may be the number of data packets carrying data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the number of received data packets carrying data.

[0199] In some embodiments, the number of data packets carried by the first entity is greater than the second threshold, triggering a status report. In an embodiment of the present disclosure, if the number of data packets carried by the first entity is greater than the second threshold, it means that the first entity has received a large number of data packets, and a status report is triggered at this time. In some embodiments, the second threshold is agreed upon by a communication protocol, or the second threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 30, which means that it is greater than the second threshold, triggering a status report.

[0200] In some embodiments, the number of data packets carried by the first entity is not greater than the second threshold, and a status report is not triggered. In the embodiment of the present disclosure, the number of data packets carried by the first entity is not greater than the second threshold, which indicates that the number of data packets received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the second threshold is agreed upon by the communication protocol, or the second threshold is configured by the network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 5, which indicates that it is greater than the second threshold, and a status report is triggered.

[0201] In the embodiment of the present disclosure, whether to trigger a status report is determined based on the relationship between the number of data packets and the threshold, thereby ensuring the accuracy of determining whether to trigger a status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0202] In some embodiments, the number of data packets is based on the RLC SDU count. In some embodiments, if the RLC SDU is segmented, different RLC SDU segments corresponding to the same RLC SDU are counted once.

[0203] In some embodiments, the number of data packets is counted based on the number of RLC data PDUs. In some embodiments, the number of data packets is counted based on the number of received RLC SDUs and RLC SDU segments.

[0204] In some embodiments, the number of data packets is counted based on the number of RLC PDUs. In some embodiments, the number of data packets is counted based on the number of RLC data PDUs and RLC control PDUs.

[0205] In the disclosed embodiment, the definition of the number of data packets is expanded, thereby expanding the diversity of determining whether to trigger a status report, ensuring the accuracy of determining whether to trigger a status report, further ensuring the accuracy of retransmission based on the status report, and ensuring communication reliability.

[0206] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the number of received data packets carrying data is counted by the counter. In some embodiments, the counter is used to count the number of data packets carrying data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the data packets of the received RLC PDU are counted by the counter, and when the number of data packets counted by the counter is greater than a second threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0207] It should be noted that, in the embodiment of the present disclosure, the first entity will count the data. When counting, the time point when the first entity counts the amount of data received and / or the number of data packets can be when the PDU is placed in the RLC receive buffer, or when the PDU is received from the bottom layer (MAC layer). The embodiment of the present disclosure does not limit this.

[0208] It should be noted that the disclosed embodiment is described by taking the example of a first entity determining whether to trigger a status report based on the relationship between the data volume or number of data packets and a threshold. In another embodiment, the first entity determines whether to trigger a status report based on the data volume and number of data packets.

[0209] In some embodiments, if the amount of data received by the first entity is greater than a first threshold and the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0210] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0211] In some embodiments, if the amount of data received by the first entity is greater than a first threshold but the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0212] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold but the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined not to trigger a status report.

[0213] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold and the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0214] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined that the status report is not triggered.

[0215] Step S2104: If the first entity determines to trigger a status report, a status report is generated.

[0216] In an embodiment of the present disclosure, if the first entity determines through the above steps that a status report needs to be triggered, a status report is generated and subsequently sent.

[0217] In some embodiments, the status report is used to indicate a situation in which the first entity receives data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received and / or which data is not correctly received; and / or whether the first entity receives the data correctly. The first data refers to data correctly received by the first entity. The second data refers to data that is not correctly received. The first data and the second data in the embodiments of the present disclosure are examples, and the first data and the second data are both used to indicate a type of data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received; and / or which data is not correctly received; and / or whether the first entity receives the data correctly.

[0218] Optionally, the data is an RLC SDU or an RLC SDU segment. For example, if the data is an RLC SDU, the first entity receiving the data refers to which RLC SDUs the first entity has received and / or which RLC SDUs it has not received. For another example, if the data is an RLC SDU segment, the first entity receiving the data refers to which RLC SDU segments the first entity has received and / or which RLC SDU segments it has not received.

[0219] In some embodiments, the format of the status report is shown in FIG2B . The D / C in the status report is C, which can also be understood as a control message. The CPT field is used to identify different types of control messages. ACK_SN and subsequent messages are not received. E1 indicates whether a NACK_SN, E1, E2, and E3 fields follow. NACK_SN marks a lost message that has not been received. E2 identifies whether SoStart and SoEnd follow, and is mainly used to handle incomplete message reception scenarios. The E3 field indicates whether a message about a series of RLC SDUs not being received follows. The NACK range field indicates how many consecutive RLC SDUs are lost starting from the NACK_SN. SoStart and SoEnd indicate a portion of the SDU of the NACK_SN that is found to be lost by the RLC receiving end. The value of SoStart indicates which byte of the original SDU the lost SDU portion starts at, and SoEnd indicates which byte it ends at.

[0220] Step S2105: The terminal sends a status report.

[0221] In some embodiments, the network device receives the status report. In some embodiments, the above step S2105 may be: the terminal sends the status report to the network device. Correspondingly, the network device receives the status report sent by the terminal.

[0222] In some embodiments, the terminal includes one or more first entities. If any of the first entities determines that a status report needs to be triggered, the terminal determines to send a status report based on the determination of the first entity.

[0223] Step S2106: The network device receives a status report.

[0224] In some embodiments, the network device receives a status report sent by the terminal.

[0225] Step S2107: The second entity determines whether to resend the data based on the status report.

[0226] In some embodiments, the step in which the second entity determines whether to resend data based on the status report may also be referred to as RLC retransmission.

[0227] In some embodiments, if the second entity receives the status report, it determines to resend the data. Optionally, the network device includes one or more second entities. Accordingly, the second entity resends the RLC SDU or RLC SDU segment. Alternatively, it can be understood that the network device resends the RLC SDU or RLC SDU segment.

[0228] In some embodiments, the status report is used to indicate the reception status of the data sent by the second entity by the first entity. Therefore, after receiving the status report, the second entity can determine which data the first entity has not successfully received, and then the second entity resends the data that the first entity has not successfully received.

[0229] In some embodiments, the status report indicates whether the first entity successfully receives each data when the amount of data received by the first entity reaches a first threshold or a second threshold. If the first entity fails to successfully receive the corresponding data, the second entity determines to resend the data that the first entity fails to receive successfully.

[0230] In some embodiments, the status report indicates whether the first entity successfully receives data within a period of time. If the first entity fails to successfully receive the corresponding data, the second entity determines to resend the data that the first entity fails to receive.

[0231] It should be noted that the embodiments of the present disclosure illustrate the role of the status report by taking examples, and the above examples do not limit the role of the status report in the embodiments of the present disclosure.

[0232] In the embodiment of the present disclosure, whether to resend data is determined by status reporting to ensure the accuracy of the retransmitted data, and whether to trigger the RLC status report is determined based on the amount of received data to ensure the accuracy of the triggered status report, further ensuring the accuracy of retransmission based on the status report, solving the problem of excessive delay and ensuring communication reliability.

[0233] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0234] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0235] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0236] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0237] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0238] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0239] The processing method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, step S2105 can be implemented as an independent embodiment, step S2106 can be implemented as an independent embodiment, step S2107 can be implemented as an independent embodiment, step S2101 and step S2102 can be implemented as independent embodiments, and step S2101 and step S2103 can be implemented as independent embodiments. The present invention may be implemented as an independent embodiment, step S2101 and step S2104 may be implemented as an independent embodiment, step S2102 and step S2103 may be implemented as an independent embodiment, step S2102 and step S2104 may be implemented as an independent embodiment, step S2103 and step S2104 may be implemented as an independent embodiment, step S2105 and step S2106 may be implemented as an independent embodiment, step S2105, step S2106 and step S2107 may be implemented as independent embodiments, but are not limited thereto.

[0240] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0241] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0242] In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0243] In some embodiments, step S2104 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0244] In some embodiments, step S2105 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0245] In some embodiments, step S2106 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0246] In some embodiments, step S2107 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0247] In some embodiments, step S2101 and step S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0248] In some embodiments, step S2101 and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0249] In some embodiments, step S2101 and step S2104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0250] In some embodiments, step S2102 and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0251] In some embodiments, step S2102 and step S2104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0252] In some embodiments, step S2103 and step S2104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0253] In some embodiments, step S2105 and step S2106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0254] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0255] FIG3A is a flow chart of a processing method according to an embodiment of the present disclosure, which is applied to a terminal. As shown in FIG3A , the embodiment of the present disclosure relates to a processing method, which includes:

[0256] Step S3101: The first entity determines whether to trigger a status report based on a first amount of received data.

[0257] In the embodiment of the present disclosure, the amount of data received by the first entity is different, and whether to trigger a status report is determined according to the amount of data.

[0258] In some embodiments, the terminal includes one or more first entities, and each first entity may perform the above step S2103.

[0259] In some embodiments, the status report is an RLC status report. Optionally, the above step S2102 is replaced by the first entity determining whether to trigger the RLC status report based on the first amount of received data.

[0260] In some embodiments, the first quantity may be the amount of data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the amount of received data.

[0261] In some embodiments, the status report is used to indicate a situation in which the first entity receives data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received and / or which data is not correctly received; and / or whether the first entity receives the data correctly. The first data refers to data correctly received by the first entity. The second data refers to data that is not correctly received. The first data and the second data in the embodiments of the present disclosure are examples, and the first data and the second data are both used to indicate a type of data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received; and / or which data is not correctly received; and / or whether the first entity receives the data correctly.

[0262] Optionally, the data is an RLC SDU or an RLC SDU segment. For example, if the data is an RLC SDU, the first entity receiving the data refers to which RLC SDUs the first entity has received and / or which RLC SDUs it has not received. For another example, if the data is an RLC SDU segment, the first entity receiving the data refers to which RLC SDU segments the first entity has received and / or which RLC SDU segments it has not received.

[0263] In some embodiments, the format of the status report is shown in FIG2B . The D / C in the status report is C, which can also be understood as a control message. The CPT field is used to identify different types of control messages. ACK_SN and subsequent messages are not received. E1 indicates whether a NACK_SN, E1, E2, and E3 fields follow. NACK_SN marks a lost message that has not been received. E2 identifies whether SoStart and SoEnd follow, and is mainly used to handle incomplete message reception scenarios. The E3 field indicates whether a message about a series of RLC SDUs not being received follows. The NACK range field indicates how many consecutive RLC SDUs are lost starting from the NACK_SN. SoStart and SoEnd indicate a portion of the SDU of the NACK_SN that is found to be lost by the RLC receiving end. The value of SoStart indicates which byte of the original SDU the lost SDU portion starts at, and SoEnd indicates which byte it ends at.

[0264] In some embodiments, the amount of data received by the first entity is greater than a first threshold, triggering a status report. In an embodiment of the present disclosure, the amount of data received by the first entity is greater than the first threshold, which indicates that the amount of data received by the first entity is large, and a status report is triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, the first threshold is 20,000 bytes, 50,000 bytes, or other values. In some embodiments, the first threshold is 50,000 bytes, and the amount of data received by the first entity is 80,000 bytes, which indicates that it is greater than the first threshold, triggering a status report.

[0265] In some embodiments, if the amount of data received by the first entity is not greater than the first threshold, a status report is not triggered. In an embodiment of the present disclosure, if the amount of data received by the first entity is not greater than the first threshold, it means that the amount of data received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, if the first threshold is 20,000 bytes, 50,000 bytes or other values. In some embodiments, if the first threshold is 50,000 bytes and the amount of data received by the first entity is 30,000 bytes, it means that it is not greater than the first threshold, and a status report is triggered.

[0266] In some embodiments, the data includes an RLC SDU and / or an RLC SDU segment, and the data amount includes the data amount of the RLC SDU and / or the RLC SDU segment. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU.

[0267] In some embodiments, the data includes an RLC data PDU, and the data amount includes the data amount of the RLC data PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU and the data amount of the RLC data PDU header.

[0268] In some embodiments, the data received by the first entity is RLC PDU, and the first entity processes the received RLC PDU to obtain RLC SDU. Therefore, the first entity can determine whether to trigger a status report based on the number of RLC PDUs, or determine whether to trigger a status report based on the number of RLC SDUs.

[0269] In some embodiments, the data includes an RLC PDU, and the data amount includes the data amount of the RLC PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU, the RLC data PDU header, and the data amount of the RLC control PDU.

[0270] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the amount of received data is counted by the counter. In some embodiments, the counter is used to count the amount of data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the amount of data of the received RLC PDU is counted by the counter, and when the amount of data counted by the counter is greater than a first threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0271] In some embodiments, the first number may be the number of data packets carrying data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the number of received data packets carrying data.

[0272] In some embodiments, the number of data packets carried by the first entity is greater than the second threshold, triggering a status report. In an embodiment of the present disclosure, if the number of data packets carried by the first entity is greater than the second threshold, it means that the first entity has received a large number of data packets, and a status report is triggered at this time. In some embodiments, the second threshold is agreed upon by a communication protocol, or the second threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 30, which means that it is greater than the second threshold, triggering a status report.

[0273] In some embodiments, the number of data packets carried by the first entity is not greater than the second threshold, and a status report is not triggered. In the embodiment of the present disclosure, the number of data packets carried by the first entity is not greater than the second threshold, which indicates that the number of data packets received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the second threshold is agreed upon by the communication protocol, or the second threshold is configured by the network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 5, which indicates that it is greater than the second threshold, and a status report is triggered.

[0274] In some embodiments, the number of data packets is based on the RLC SDU count. In some embodiments, if the RLC SDU is segmented, the RLC SDU segments corresponding to the same RLC SDU are counted once.

[0275] In some embodiments, the number of data packets is counted based on the number of RLC data PDUs. In some embodiments, the number of data packets is counted based on the number of received RLC SDUs and RLC SDU segments.

[0276] In some embodiments, the number of data packets is counted based on the number of RLC PDUs. In some embodiments, the number of data packets is counted based on the number of RLC data PDUs and RLC control PDUs.

[0277] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the number of received data packets carrying data is counted by the counter. In some embodiments, the counter is used to count the number of data packets carrying data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the data packets of the received RLC PDU are counted by the counter, and when the number of data packets counted by the counter is greater than a second threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0278] It should be noted that, in the embodiment of the present disclosure, the first entity will count the data. When counting, the time point when the first entity counts the amount of data received and / or the number of data packets can be when the PDU is placed in the RLC receive buffer, or when the PDU is received from the bottom layer (MAC layer). The embodiment of the present disclosure does not limit this.

[0279] It should be noted that the disclosed embodiment is described by taking the example of a first entity determining whether to trigger a status report based on the relationship between the data volume or number of data packets and a threshold. In another embodiment, the first entity determines whether to trigger a status report based on the data volume and number of data packets.

[0280] In some embodiments, if the amount of data received by the first entity is greater than a first threshold and the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0281] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0282] In some embodiments, if the amount of data received by the first entity is greater than a first threshold but the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0283] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold but the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined not to trigger a status report.

[0284] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold and the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0285] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined that the status report is not triggered.

[0286] Step S3102: If the first entity determines to trigger a status report, it sends a status report.

[0287] In an embodiment of the present disclosure, if the first entity determines through the above steps that a status report needs to be triggered, a status report is generated and subsequently sent. In some embodiments, the terminal includes one or more first entities, and if any of the first entities determines that a status report needs to be triggered, the terminal determines to send a status report based on the determination of the first entity.

[0288] The processing method involved in the embodiment of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, and step S3102 may be implemented as an independent embodiment.

[0289] FIG3B is a flow chart of a processing method according to an embodiment of the present disclosure, which is applied to a terminal. As shown in FIG3B , the embodiment of the present disclosure relates to a processing method, which includes:

[0290] Step S3201: The first entity determines whether to trigger a status report based on a first amount of received data.

[0291] In the embodiment of the present disclosure, the amount of data received by the first entity is different, and whether to trigger a status report is determined according to the amount of data.

[0292] In some embodiments, the terminal includes one or more first entities, and each first entity can perform the above step s2103.

[0293] In some embodiments, the status report is an RLC status report. Optionally, the above step S2102 is replaced by the first entity determining whether to trigger the RLC status report based on the first amount of received data.

[0294] In some embodiments, the first quantity may be the amount of data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the amount of received data.

[0295] In some embodiments, the status report is used to indicate a situation in which the first entity receives data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received and / or which data is not correctly received; and / or whether the first entity receives the data correctly. The first data refers to data correctly received by the first entity. The second data refers to data that is not correctly received. The first data and the second data in the embodiments of the present disclosure are examples, and the first data and the second data are both used to indicate a type of data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received; and / or which data is not correctly received; and / or whether the first entity receives the data correctly.

[0296] Optionally, the data is an RLC SDU or an RLC SDU segment. For example, if the data is an RLC SDU, the first entity receiving the data refers to which RLC SDUs the first entity has received and / or which RLC SDUs it has not received. For another example, if the data is an RLC SDU segment, the first entity receiving the data refers to which RLC SDU segments the first entity has received and / or which RLC SDU segments it has not received.

[0297] In some embodiments, the format of the status report is shown in FIG2B . The D / C in the status report is C, which can also be understood as a control message. The CPT field is used to identify different types of control messages. ACK_SN and subsequent messages are not received. E1 indicates whether a NACK_SN, E1, E2, and E3 fields follow. NACK_SN marks a lost message that has not been received. E2 identifies whether SoStart and SoEnd follow, and is mainly used to handle incomplete message reception scenarios. The E3 field indicates whether a message about a series of RLC SDUs not being received follows. The NACK range field indicates how many consecutive RLC SDUs are lost starting from the NACK_SN. SoStart and SoEnd indicate a portion of the SDU of the NACK_SN that is found to be lost by the RLC receiving end. The value of SoStart indicates which byte of the original SDU the lost SDU portion starts at, and SoEnd indicates which byte it ends at.

[0298] In some embodiments, the amount of data received by the first entity is greater than a first threshold, triggering a status report. In an embodiment of the present disclosure, the amount of data received by the first entity is greater than the first threshold, which indicates that the amount of data received by the first entity is large, and a status report is triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, the first threshold is 20,000 bytes, 50,000 bytes, or other values. In some embodiments, the first threshold is 50,000 bytes, and the amount of data received by the first entity is 80,000 bytes, which indicates that it is greater than the first threshold, triggering a status report.

[0299] In some embodiments, if the amount of data received by the first entity is not greater than the first threshold, a status report is not triggered. In an embodiment of the present disclosure, if the amount of data received by the first entity is not greater than the first threshold, it means that the amount of data received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, if the first threshold is 20,000 bytes, 50,000 bytes or other values. In some embodiments, if the first threshold is 50,000 bytes and the amount of data received by the first entity is 30,000 bytes, it means that it is not greater than the first threshold, and a status report is triggered.

[0300] In some embodiments, the data includes an RLC SDU and / or an RLC SDU segment, and the data amount includes the data amount of the RLC SDU and / or the RLC SDU segment. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU.

[0301] In some embodiments, the data includes an RLC data PDU, and the data amount includes the data amount of the RLC data PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU and the data amount of the RLC data PDU header.

[0302] In some embodiments, the data received by the first entity is RLC PDU, and the first entity processes the received RLC PDU to obtain RLC SDU. Therefore, the first entity can determine whether to trigger a status report based on the number of RLC PDUs, or determine whether to trigger a status report based on the number of RLC SDUs.

[0303] In some embodiments, the data includes an RLC PDU, and the data amount includes the data amount of the RLC PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU, the RLC data PDU header, and the data amount of the RLC control PDU.

[0304] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the amount of received data is counted by the counter. In some embodiments, the counter is used to count the amount of data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the amount of data of the received RLC PDU is counted by the counter, and when the amount of data counted by the counter is greater than a first threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0305] In some embodiments, the first number may be the number of data packets carrying data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the number of received data packets carrying data.

[0306] In some embodiments, the number of data packets carried by the first entity is greater than the second threshold, triggering a status report. In an embodiment of the present disclosure, if the number of data packets carried by the first entity is greater than the second threshold, it means that the first entity has received a large number of data packets, and a status report is triggered at this time. In some embodiments, the second threshold is agreed upon by a communication protocol, or the second threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 30, which means that it is greater than the second threshold, triggering a status report.

[0307] In some embodiments, the number of data packets carried by the first entity is not greater than the second threshold, and a status report is not triggered. In the embodiment of the present disclosure, the number of data packets carried by the first entity is not greater than the second threshold, which indicates that the number of data packets received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the second threshold is agreed upon by the communication protocol, or the second threshold is configured by the network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 5, which indicates that it is greater than the second threshold, and a status report is triggered.

[0308] In some embodiments, the number of data packets is based on the RLC SDU count. In some embodiments, if the RLC SDU is segmented, the RLC SDU segments corresponding to the same RLC SDU are counted once.

[0309] In some embodiments, the number of data packets is counted based on the number of RLC data PDUs. In some embodiments, the number of data packets is counted based on the number of received RLC SDUs and RLC SDU segments.

[0310] In some embodiments, the number of data packets is counted based on the number of RLC PDUs. In some embodiments, the number of data packets is counted based on the number of RLC data PDUs and RLC control PDUs.

[0311] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the number of received data packets carrying data is counted by the counter. In some embodiments, the counter is used to count the number of data packets carrying data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the data packets of the received RLC PDU are counted by the counter, and when the number of data packets counted by the counter is greater than a second threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0312] It should be noted that, in the embodiment of the present disclosure, the first entity will count the data. When counting, the time point when the first entity counts the amount of data received and / or the number of data packets can be when the PDU is placed in the RLC receive buffer, or when the PDU is received from the bottom layer (MAC layer). The embodiment of the present disclosure does not limit this.

[0313] It should be noted that the disclosed embodiment is described by taking the example of a first entity determining whether to trigger a status report based on the relationship between the data volume or number of data packets and a threshold. In another embodiment, the first entity determines whether to trigger a status report based on the data volume and number of data packets.

[0314] In some embodiments, if the amount of data received by the first entity is greater than a first threshold and the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0315] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0316] In some embodiments, if the amount of data received by the first entity is greater than a first threshold but the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0317] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold but the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined not to trigger a status report.

[0318] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold and the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0319] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined that the status report is not triggered.

[0320] FIG4A is a flow chart of a processing method according to an embodiment of the present disclosure, which is applied to a network device. As shown in FIG4A , the embodiment of the present disclosure relates to a processing method, which includes:

[0321] Step S4101: The network device sends configuration information.

[0322] In some embodiments, the terminal receives the configuration information. In some embodiments, the above step S2101 can also be replaced by: the network device sends the configuration information to the terminal. Correspondingly, the terminal receives the configuration information sent by the network device.

[0323] In some embodiments, the configuration information is at least one of the first information or the second information. Optionally, the first information is used to configure a first threshold. In some embodiments, the first threshold is used by the first entity to determine whether to trigger a status report based on the amount of received data. Alternatively, it can be understood that the first threshold is a judgment condition for the first entity, and whether to trigger a status report can be determined based on the first threshold. Optionally, the second information is used to configure a second threshold. In some embodiments, the second threshold is used by the first entity to determine whether to trigger a status report based on the number of data packets of received data. Alternatively, it can be understood that the second threshold is a judgment condition for the first entity, and whether to trigger a status report can be determined based on the second threshold.

[0324] In some embodiments, the terminal includes one or more first entities. Optionally, the configuration information is used to configure the first threshold and / or second threshold corresponding to the one or more first entities. Optionally, the configuration information is used to configure the first threshold and / or second threshold for each first entity separately. Alternatively, it can be understood that different first entities in the terminal have different configurations. Optionally, the configuration information is used to simultaneously configure the first threshold and / or second threshold for multiple first entities. Alternatively, it can be understood that the configurations of multiple first entities are the same.

[0325] In some embodiments, if the terminal includes multiple first entities, each first entity in the terminal performs subsequent steps independently based on its own configuration.

[0326] In some embodiments, the first entity is an RLC entity. Optionally, the RLC entity is an AM RLC entity.

[0327] In some embodiments, the network device includes one or more second entities. Optionally, the configurations of the multiple second entities may be the same or different, which is not limited in the embodiments of the present disclosure.

[0328] In some embodiments, the second entity is an RLC entity. Optionally, the RLC entity is an AM RLC entity.

[0329] It should be noted that the first information and the second information in the embodiment of the present disclosure may be the same information, or two different pieces of information, and the embodiment of the present disclosure is not limited thereto.

[0330] It should be noted that the embodiments of this disclosure are described using an example in which a terminal includes one or more first entities and a network device includes one or more second entities. In another embodiment, the terminal includes one or more second entities and the network device includes one or more first entities. Alternatively, the embodiments of this disclosure are described using an example in which a terminal includes one or more first entities and a network device includes one or more second entities.

[0331] It should be noted that the embodiment of the present disclosure uses step S4101 as an example for illustration. In another embodiment, step S4101 is optional. In another embodiment, step S4101 may not be performed, and the first threshold and the second threshold may be determined in other ways.

[0332] In the embodiment of the present disclosure, a first threshold value and / or a second threshold value is configured for a terminal through a network device so that the first entity in a subsequent terminal can determine whether to trigger a status report, thereby achieving the effect of the network device instructing the terminal to trigger a status report through the configured threshold value, and providing a new way for the terminal to trigger a status report. Since the status report is triggered by the threshold value configured by the network device for the terminal, the delay of the terminal triggering the status report is reduced, and the efficiency of the terminal triggering the status report is improved, thereby ensuring the efficiency of data retransmission and ensuring communication reliability.

[0333] Step S4102: The second entity sends data.

[0334] In some embodiments, the first entity receives data. In some embodiments, the above step S4102 may also be replaced by: the second entity sends data to the first entity. Correspondingly, the first entity receives the data sent by the second entity.

[0335] In some embodiments, the network device includes one or more second entities. Accordingly, the above steps may be replaced by: the network device sends data. Alternatively, the second entity of the network device sends data. In some embodiments, the terminal includes one or more first entities, that is, the terminal receives data. Alternatively, the first entity of the terminal receives data.

[0336] In some embodiments, the second entity is an RLC entity. Optionally, the data received by the second entity at the upper layer can be referred to as an RLC SDU or an RLC SDU segment. It can also be understood that the data sent by the second entity is an RLC SDU or an RLC SDU segment. Optionally, the second entity encapsulates the RLC SDU or RLC SDU segment to obtain an RLC PDU, and then sends the RLC PDU to the lower layer.

[0337] In some embodiments, the first entity is an RLC entity. Optionally, the first entity receives an RLC PDU at a lower layer and then processes the RLC PDU to obtain an RLC SDU or an RLC SDU segment.

[0338] In some embodiments, the first entity is an AM RLC entity. Optionally, for an AM RLC entity, an RLC data PDU is referred to as an AMD PDU, and the following description mainly uses the RLC data PDU.

[0339] Step S4103: The second entity determines whether to resend the data based on the status report.

[0340] In some embodiments, the step in which the second entity determines whether to resend data based on the status report may also be referred to as RLC retransmission.

[0341] In some embodiments, if the second entity receives the status report, it determines to resend the data. Optionally, the network device includes one or more second entities. Accordingly, the second entity resends the RLC SDU or RLC SDU segment. Alternatively, it can be understood that the network device resends the RLC SDU or RLC SDU segment.

[0342] In some embodiments, the status report is used to indicate the reception status of the data sent by the second entity by the first entity. Therefore, after receiving the status report, the second entity can determine which data the first entity has not successfully received, and then the second entity resends the data that the first entity has not successfully received.

[0343] In some embodiments, the status report indicates whether the first entity successfully receives data within a period of time. If the first entity fails to successfully receive the corresponding data, the second entity determines to resend the data that the first entity fails to receive.

[0344] The processing method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4103. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, and step S4103 may be implemented as an independent embodiment.

[0345] FIG4B is a flow chart of a processing method according to an embodiment of the present disclosure, which is applied to a network device. As shown in FIG4B , the embodiment of the present disclosure relates to a processing method, which includes:

[0346] Step S4201: The second entity receives a status report.

[0347] In some embodiments, the network device receives a status report sent by the terminal.

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

[0349] The network device sends first information, where the first information is used to configure a first threshold; or,

[0350] The first threshold is defined by a communication protocol; or,

[0351] The first threshold is one of candidate thresholds preconfigured by the terminal;

[0352] The first threshold is used by the first entity to determine whether to send the status report.

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

[0354] The network device sends second information, where the second information is used to configure a second threshold; or,

[0355] The second threshold is defined by a communication protocol; or,

[0356] The second threshold is one of candidate thresholds preconfigured by the terminal;

[0357] The second threshold is used by the first entity to determine whether to send the status report.

[0358] In some embodiments, the second entity is an RLC entity.

[0359] In some embodiments, the status report is an RLC status report.

[0360] In some embodiments, the situation in which the first entity receives the data includes:

[0361] Among the data received by the first entity, first data is received correctly; and / or second data is not received correctly; and / or whether the first entity receives the data correctly.

[0362] FIG5 is a flow chart of a processing method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to a processing method, which includes:

[0363] Step S5101: The first entity determines whether to trigger a status report based on a first amount of received data.

[0364] In the embodiment of the present disclosure, the amount of data received by the first entity is different, and whether to trigger a status report is determined according to the amount of data.

[0365] In some embodiments, the terminal includes one or more first entities, and each first entity can perform the above step s2103.

[0366] In some embodiments, the status report is an RLC status report. Optionally, the above step S2102 is replaced by the first entity determining whether to trigger the RLC status report based on the first amount of received data.

[0367] In some embodiments, the first quantity may be the amount of data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the amount of received data.

[0368] In some embodiments, the status report is used to indicate a situation in which the first entity receives data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received and / or which data is not correctly received; and / or whether the first entity receives the data correctly. The first data refers to data correctly received by the first entity. The second data refers to data that is not correctly received. The first data and the second data in the embodiments of the present disclosure are examples, and the first data and the second data are both used to indicate a type of data. Optionally, the situation in which the first entity receives the data includes: which data in the data received by the first entity is correctly received; and / or which data is not correctly received; and / or whether the first entity receives the data correctly.

[0369] Optionally, the data is an RLC SDU or an RLC SDU segment. For example, if the data is an RLC SDU, the first entity receiving the data refers to which RLC SDUs the first entity has received and / or which RLC SDUs it has not received. For another example, if the data is an RLC SDU segment, the first entity receiving the data refers to which RLC SDU segments the first entity has received and / or which RLC SDU segments it has not received.

[0370] In some embodiments, the format of the status report is shown in FIG2B . The D / C in the status report is C, which can also be understood as a control message. The CPT field is used to identify different types of control messages. ACK_SN and subsequent messages are not received. E1 indicates whether a NACK_SN, E1, E2, and E3 fields follow. NACK_SN marks a lost message that has not been received. E2 identifies whether SoStart and SoEnd follow, and is mainly used to handle incomplete message reception scenarios. The E3 field indicates whether a message about a series of RLC SDUs not being received follows. The NACK range field indicates how many consecutive RLC SDUs are lost starting from the NACK_SN. SoStart and SoEnd indicate a portion of the SDU of the NACK_SN that is found to be lost by the RLC receiving end. The value of SoStart indicates which byte of the original SDU the lost SDU portion starts at, and SoEnd indicates which byte it ends at.

[0371] In some embodiments, the amount of data received by the first entity is greater than a first threshold, triggering a status report. In an embodiment of the present disclosure, the amount of data received by the first entity is greater than the first threshold, which indicates that the amount of data received by the first entity is large, and a status report is triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, the first threshold is 20,000 bytes, 50,000 bytes, or other values. In some embodiments, the first threshold is 50,000 bytes, and the amount of data received by the first entity is 80,000 bytes, which indicates that it is greater than the first threshold, triggering a status report.

[0372] In some embodiments, if the amount of data received by the first entity is not greater than the first threshold, a status report is not triggered. In an embodiment of the present disclosure, if the amount of data received by the first entity is not greater than the first threshold, it means that the amount of data received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the first threshold is agreed upon by a communication protocol, or the first threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives a first message sent by a network device, and the first message is used to configure the first threshold. For example, if the first threshold is 20,000 bytes, 50,000 bytes or other values. In some embodiments, if the first threshold is 50,000 bytes and the amount of data received by the first entity is 30,000 bytes, it means that it is not greater than the first threshold, and a status report is triggered.

[0373] In some embodiments, the data includes an RLC SDU and / or an RLC SDU segment, and the data amount includes the data amount of the RLC SDU and / or the RLC SDU segment. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU.

[0374] In some embodiments, the data includes an RLC data PDU, and the data amount includes the data amount of the RLC data PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU and the data amount of the RLC data PDU header.

[0375] In some embodiments, the data received by the first entity is RLC PDU, and the first entity processes the received RLC PDU to obtain RLC SDU. Therefore, the first entity can determine whether to trigger a status report based on the number of RLC PDUs, or determine whether to trigger a status report based on the number of RLC SDUs.

[0376] In some embodiments, the data includes an RLC PDU, and the data amount includes the data amount of the RLC PDU. In some embodiments, the data amount is counted according to the data amount of the Data field in the received RLC data PDU, the RLC data PDU header, and the data amount of the RLC control PDU.

[0377] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the amount of received data is counted by the counter. In some embodiments, the counter is used to count the amount of data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the amount of data of the received RLC PDU is counted by the counter, and when the amount of data counted by the counter is greater than a first threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0378] In some embodiments, the first number may be the number of data packets carrying data, and the above step S2102 is replaced by the first entity determining whether to trigger a status report based on the number of received data packets carrying data.

[0379] In some embodiments, the number of data packets carried by the first entity is greater than the second threshold, triggering a status report. In an embodiment of the present disclosure, if the number of data packets carried by the first entity is greater than the second threshold, it means that the first entity has received a large number of data packets, and a status report is triggered at this time. In some embodiments, the second threshold is agreed upon by a communication protocol, or the second threshold is configured by a network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 30, which means that it is greater than the second threshold, triggering a status report.

[0380] In some embodiments, the number of data packets carried by the first entity is not greater than the second threshold, and a status report is not triggered. In the embodiment of the present disclosure, the number of data packets carried by the first entity is not greater than the second threshold, which indicates that the number of data packets received by the first entity is small, and a status report is not triggered at this time. In some embodiments, the second threshold is agreed upon by the communication protocol, or the second threshold is configured by the network device. In some embodiments, the first entity is set at a terminal, and the terminal receives second information sent by the network device, and the second information is used to configure the second threshold. For example, the second threshold is 10, 20, 30 or other values. In some embodiments, the second threshold is 20, and the number of data packets carried by the first entity is 5, which indicates that it is greater than the second threshold, and a status report is triggered.

[0381] In some embodiments, the number of data packets is based on the RLC SDU count. In some embodiments, if the RLC SDU is segmented, the RLC SDU segments corresponding to the same RLC SDU are counted once.

[0382] In some embodiments, the number of data packets is counted based on the number of RLC data PDUs. In some embodiments, the number of data packets is counted based on the number of received RLC SDUs and RLC SDU segments.

[0383] In some embodiments, the number of data packets is counted based on the number of RLC PDUs. In some embodiments, the number of data packets is counted based on the number of RLC data PDUs and RLC control PDUs.

[0384] It should be noted that in the embodiment of the present disclosure, the first entity includes a counter, and the counter is used to count the received data. Alternatively, it can also be understood that the first entity maintains a counter, and the number of received data packets carrying data is counted by the counter. In some embodiments, the counter is used to count the number of data packets carrying data received since the last triggering of the status report. In some embodiments, if the first entity receives an RLC PDU, the data packets of the received RLC PDU are counted by the counter, and when the number of data packets counted by the counter is greater than a second threshold, a status report is triggered. In some embodiments, the first entity includes a counter, and if the first entity determines to trigger a status report, the counter is reset to 0.

[0385] It should be noted that, in the embodiment of the present disclosure, the first entity will count the data. When counting, the time point when the first entity counts the amount of data received and / or the number of data packets can be when the PDU is placed in the RLC receive buffer, or when the PDU is received from the bottom layer (MAC layer). The embodiment of the present disclosure does not limit this.

[0386] It should be noted that the disclosed embodiment is described by taking the example of a first entity determining whether to trigger a status report based on the relationship between the data volume or number of data packets and a threshold. In another embodiment, the first entity determines whether to trigger a status report based on the data volume and number of data packets.

[0387] In some embodiments, if the amount of data received by the first entity is greater than a first threshold and the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0388] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined that a status report is triggered.

[0389] In some embodiments, if the amount of data received by the first entity is greater than a first threshold but the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0390] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold but the number of data packets carrying data received by the first entity is greater than a second threshold, it is determined not to trigger a status report.

[0391] In some embodiments, if the amount of data received by the first entity is not greater than a first threshold and the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined not to trigger a status report.

[0392] In some embodiments, if either the amount of data received by the first entity is greater than a first threshold or the number of data packets carrying data received by the first entity is not greater than a second threshold, it is determined that the status report is not triggered.

[0393] Step S5102: The second entity receives a status report.

[0394] In some embodiments, the above method may include the methods of the above embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0395] FIG6 is a flow chart of a processing method according to an embodiment of the present disclosure. As shown in FIG6 , the embodiment of the present disclosure relates to a processing method, which includes:

[0396] Step S6101: triggering an RLC status report based on the amount of data received by the AM RLC entity.

[0397] In some embodiments, the amount of data can be counted in the following three ways:

[0398] a) The data volume is counted according to the amount of data in the received RLC SDU and RLC SDU segment (i.e., the amount of data in the Data field of the received RLC data PDU);

[0399] b) The data volume is counted according to the amount of data in the received RLC data PDU (in this case, the RLC data PDU header is also counted);

[0400] c) The data volume is counted according to the data volume of the received RLC PDU (in this case, the RLC data PDU header and RLC control PDU are also counted).

[0401] In some embodiments, the network may configure a threshold so that an RLC status report is triggered when the amount of data received by the AM RLC entity is greater than or equal to (or greater than) the threshold. The threshold may be configured through RRC signaling.

[0402] In some embodiments, the receiving side of the AM RLC entity may maintain a counter, such as BYTE_WITHOUT_STATUS_REPORT. This counter is used to count the amount of data (e.g., in bytes) received since the last RLC status report was sent. The counter is initialized to 0. When the UE receives an RLC PDU, the UE counts according to the method described above, i.e., increments BYTE_WITHOUT_STATUS_REPORT by the amount of data received. When the BYTE_WITHOUT_STATUS_REPORT counter is greater than or equal to (or greater than) a threshold, the UE triggers an RLC status report. When the UE transmits an RLC status report, the BYTE_WITHOUT_STATUS_REPORT counter is reset to 0.

[0403] Step S6102: triggering an RLC status report according to the number of data packets received by the AM RLC entity.

[0404] In some embodiments, the number of data packets can be counted in the following three ways:

[0405] a) The number of data packets is counted only based on the received RLC SDU. In this method, RLC SDU segments are not ignored, but the RLC SDU segments corresponding to the same RLC SDU (i.e., with the same RLC SN) are only counted once.

[0406] b) The number of data packets is counted according to the number of received RLC data PDUs (ie, AMD PDUs) (ie, the number of RLC SDUs and RLC SDU segments).

[0407] c) The number of data packets is counted according to the number of received RLC PDUs (ie both RLC data PDUs and RLC control PDUs are counted).

[0408] In some embodiments, the network may configure a threshold so that an RLC status report is triggered when the number of data packets received by the AM RLC entity is greater than or equal to (or greater than) the threshold. The threshold may be configured through RRC signaling.

[0409] In some embodiments, the receiving side of the AM RLC entity may maintain a counter, such as SDU_WITHOUT_STATUS_REPORT (corresponding to method a). This counter is used to count the number of data packets received since the last RLC status report was sent. The counter is initialized to 0. When the UE receives an RLC PDU, the UE counts according to the method described above, i.e., increments SDU_WITHOUT_STATUS_REPORT by the number of received data packets. When the counter SDU_WITHOUT_STATUS_REPORT is greater than or equal to (or greater than) a threshold, the UE triggers an RLC status report. When the UE transmits an RLC status report, the counter SDU_WITHOUT_STATUS_REPORT is reset to 0.

[0410] It should be noted that in Method 1 and Method 2, the time node when the AM RLC entity counts the amount of data received and / or the number of data packets can be when the AMD PDU is placed in the receive buffer (i.e., Section 5.2.3.2.3 of 3GPP TS 38.322), or when the AMD PDU is received from the bottom layer (MAC layer) (i.e., Section 5.2.3.2.2 of 3GPP TS 38.322). This patent does not limit this.

[0411] In the following examples, the underlined parts are the contents added to the standard according to the method of this patent.

[0412] In some embodiments, the following is an example of adding thresholds for the amount of data and the number of data packets received by the AM RLC entity in the RLC BearerConfig IE in 3GPP TS 38.331. Newly added RLC-Config-v1900IE. In this example, the suffix v1900 of the RLC-Config IE indicates that it was introduced in 3GPP Rel-19. This IE may also be introduced in other Releases or versions of 3GPP, and the suffix will change accordingly. For example, when introduced in Rel-20, the suffix will be v2000. The two introduced fields statusSDU and statusByte are the thresholds for the amount of data (method 1) and the number of data packets (method 2), respectively. The data type of statusSDU adopts the existing IE PollPDU, and the data type or value range can also be independently defined for statusSDU. Similarly, the data type of statusByte adopts the existing IE PollByte, and the data type or value range can also be independently defined for statusByte.

[0413] in,

[0414] In some embodiments, when placing an AMD PDU with SN=x in the receive buffer, the receiving side of the AM RLC entity shall:

[0415] - If statusSDU is configured and any byte of the RLC SDU with SN=x has not been received before:

[0416] -Increase SDU_WITHOUT_STATUS_REPORT by 1;

[0417] -If statusByte is configured:

[0418] -For each additional byte in the Data field of the AMD PDU, the BYTE_WITHOUT_STATUS_REPORT value will be increased by 1.

[0419] - If x >= RX_Next_Highest:

[0420] -Update RX_Next_Highest to x+1.

[0421] Correspondingly, the standard description is as follows:

[0422] When an AMD PDU with SN=x is placed in the reception buffer, the receiving side of an AM RLC entity shall:

[0423] -if statusSDU is configured and any bytes of the RLC SDU with SN=x have not been received before:

[0424] -increment SDU_WITHOUT_STATUS_REPORT by one;

[0425] -if statusByte is configured:

[0426] -increment BYTE_WITHOUT_STATUS_REPORT by every byte of the Data field of the AMD PDU;

[0427] -if x>=RX_Next_Highest:

[0428] - Update RX_Next_Highest to x+1.

[0429] In some embodiments, the AM RLC entity sends a STATUS PDU to its peer AM RLC entity to provide positive and / or negative acknowledgments for RLC SDUs (or portions thereof).

[0430] The triggers for initiating status reporting include:

[0431] - Peer AM RLC entity polling:

[0432] - When receiving an AMD PDU with SN = x and the P field set to "1" from the lower layer, the receiving side of the AM RLC entity shall:

[0433] - If the AMD PDU is discarded as specified in Clause 5.2.3.2.2; or

[0434] - If x < RX_Highest_Status or x >= RX_Next + AM_Window_Size:

[0435] - Trigger a status report.

[0436] - Otherwise:

[0437] - Delay triggering the STATUS report until x < RX_Highest_Status or x >= RX_Next + AM_Window_Size.

[0438] Note 1: This ensures that the RLC status report is sent after HARQ reordering.

[0439] - Detecting failure of AMD PDU reception

[0440] - The receiving side of the AM RLC entity shall trigger a STATUS report at t-Reassembly timeout.

[0441] - The number of received SDUs or amount of data exceeds the set threshold:

[0442] - When SDU_WITHOUT_STATUS_REPORT >= statusSDU or BYTE_WITHOUT_STATUS_REPORT >= statusByte, the AM RLC receiving side triggers a STATUS report.

[0443] Correspondingly, the standard description is as follows:

[0444] An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and / or negative acknowledgements of RLC SDUs(or portions of them).

[0445] Triggers to initiate STATUS reporting include:

[0446] -Polling from its peer AM RLC entity:

[0447] -When an AMD PDU with SN=x and the P field set to"1"is received from lower layer,the receiving side of an AM RLC entity shall:

[0448] -if the AMD PDU is to be discarded as specified in clause 5.2.3.2.2;or

[0449] -if x<RX_Highest_Status or x>=RX_Next+AM_Window_Size:

[0450] -trigger a STATUS report.

[0451] -else:

[0452] -delay triggering the STATUS report until x<RX_Highest_Status or x>=RX_Next+AM_Window_Size.

[0453] NOTE 1:This ensures that the RLC Status report is transmitted after HARQ reordering.

[0454] -Detection of reception failure of an AMD PDU

[0455] -The receiving side of an AM RLC entity shall trigger a STATUS report when t-Reassembly expires.

[0456] -The number of received SDUs or data exceeds the configured thresholds:

[0457] -The receiving side of an AM RLC entity shall trigger a STATUS report when SDU_WITHOUT_STATUS_REPORT>=statusSDU or BYTE_WITHOUT_STATUS_REPORT>=statusByte.

[0458] In some embodiments, when a STATUS PDU has been delivered to lower layers, the receiving end of the AM RLC entity shall:

[0459] -If statusSDU is configured:

[0460] - Set SDU_WITHOUT_STATUS_REPORT to 0;

[0461] -If statusByte is configured:

[0462] - Set BYTE_WITHOUT_STATUS_REPORT to 0;

[0463] -start t-StatusProhibit.

[0464] Correspondingly, the standard description is as follows:

[0465] When a STATUS PDU has been submitted to lower layer, the receiving side of an AM RLC entity shall:

[0466] -if statusSDU is configured:

[0467] -set SDU_WITHOUT_STATUS_REPORT to 0;

[0468] -if statusByte is configured:

[0469] -set BYTE_WITHOUT_STATUS_REPORT to 0;

[0470] -start t-StatusProhibit.

[0471] In some embodiments, the receiver of each AM RLC entity shall maintain the following counters:

[0472] a) SDU_WITHOUT_STATUS_REPORT - counter

[0473] This counter is initially set to 0. It counts the number of RLC SDUs received since the most recent status report was sent.

[0474] b)BYTE_WITHOUT_STATUS_REPORT-Counter

[0475] This counter is initially set to 0. It counts the number of data bytes received since the most recent status report was transmitted.

[0476] Correspondingly, the standard description is as follows:

[0477] The receiving side of each AM RLC entity shall maintain the following counters:

[0478] a)SDU_WITHOUT_STATUS_REPORT–Counter

[0479] This counter is initially set to 0.It counts the number of RLC SDUs received since the most recent status report was transmitted.

[0480] b)BYTE_WITHOUT_STATUS_REPORT–Counter

[0481] This counter is initially set to 0.It counts the number of data bytes received since the most recent status report was transmitted.

[0482] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0483] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0484] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0485] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0486] Figure 7A is a schematic diagram of the structure of the first entity proposed in an embodiment of the present disclosure. As shown in Figure 7A, the first entity 7100 may include: at least one of a transceiver module 7101, a processing module 7102, etc. In some embodiments, the processing module 7102 is used for the first entity to determine whether to trigger a status report based on the first amount of received data, and the status report is used to indicate the situation in which the first entity receives the data. Optionally, the above-mentioned transceiver module 7101 is used to execute at least one of the communication steps such as sending and / or receiving executed by the terminal in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps executed by the terminal in any of the above methods, which will not be repeated here.

[0487] Optionally, the processing module 7102 is used to execute at least one of the communication steps such as processing performed by the first entity in any of the above methods, which will not be repeated here.

[0488] In some embodiments, the first quantity refers to the data volume of the data, and the processing module 7102 is configured for the first entity to determine whether to trigger the status report based on the data volume of the received data.

[0489] In some embodiments, the processing module 7102 is configured to:

[0490] If the amount of the data received by the first entity is greater than a first threshold, triggering the status report; or,

[0491] If the amount of the data received by the first entity is not greater than the first threshold, the status report is not triggered.

[0492] In some embodiments, the data includes an RLC SDU and / or an RLC SDU segment, and the data amount includes the data amount of the RLC SDU and / or the RLC SDU segment; or,

[0493] The data includes an RLC data PDU, and the data amount includes the data amount of the RLC data PDU; or

[0494] The data includes an RLC PDU, and the data amount includes the data amount of the RLC PDU.

[0495] In some embodiments, the transceiver module 7101 is configured for the terminal to receive first information, where the first information is used to configure the first threshold; or

[0496] The first threshold is defined by a communication protocol; or,

[0497] The first threshold is one of candidate thresholds preconfigured by the terminal.

[0498] In some embodiments, the first quantity refers to the number of data packets carrying the data, and the first entity determines whether to trigger a status report based on the first quantity of received data, including:

[0499] The first entity determines whether to trigger the status report based on the number of received data packets carrying the data.

[0500] In some embodiments, the processing module 7102 is configured to:

[0501] If the number of data packets carrying the data received by the first entity is greater than a second threshold, triggering the status report; or,

[0502] If the number of data packets carrying the data received by the first entity is not greater than the second threshold, the status report is not triggered.

[0503] In some embodiments, the number of packets is based on an RLC SDU count; or,

[0504] The number of data packets is counted based on the number of RLC data PDUs; or

[0505] The number of data packets is counted based on the number of RLC PDUs.

[0506] In some embodiments, the transceiver module 7101 is configured for the terminal to receive second information sent by a network device, where the second information is used to configure the second threshold; or

[0507] The second threshold is defined by a communication protocol; or,

[0508] The second threshold is one of candidate thresholds preconfigured by the terminal.

[0509] In some embodiments, the first entity comprises a counter configured to count the received data.

[0510] In some embodiments, the processing module 7102 is configured to reset the counter to 0 when the first entity determines to trigger the status report.

[0511] In some embodiments, the first entity is a RLC entity.

[0512] In some embodiments, the status report is an RLC status report.

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

[0514] The first entity determines to trigger the status report;

[0515] The first entity sends the status report.

[0516] It should be noted that the terminal includes one or more first entities, and each first entity in the terminal includes at least one of the above-mentioned transceiver module 7101 or processing module 7102, and can all perform the above steps, which is not limited in the embodiments of the present disclosure.

[0517] Figure 7B is a schematic diagram of the structure of the second entity proposed in an embodiment of the present disclosure. As shown in Figure 7B, the second entity 7200 may include at least one of a transceiver module 7201 and a processing module 7202. In some embodiments, the transceiver module 7201 is configured to receive a status report sent by the first entity, wherein the status report indicates the status of the first entity receiving data. Optionally, the transceiver module is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by the network device in any of the above methods, and will not be further described here.

[0518] Optionally, the processing module 7202 is used to execute at least one of the communication steps such as processing performed by the second entity in any of the above methods, which will not be repeated here.

[0519] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0520] In some embodiments, the transceiver module 7201 is configured to send first information to the network device, where the first information is used to configure a first threshold; or

[0521] The first threshold is defined by a communication protocol; or,

[0522] The first threshold is one of candidate thresholds preconfigured by the terminal;

[0523] The first threshold is used by the first entity to determine whether to send the status report.

[0524] In some embodiments, the transceiver module 7201 is used for the network device to send second information, where the second information is used to configure a second threshold; or

[0525] The second threshold is defined by a communication protocol; or,

[0526] The second threshold is one of candidate thresholds preconfigured by the terminal;

[0527] The second threshold is used by the first entity to determine whether to send the status report.

[0528] In some embodiments, the second entity is an RLC entity.

[0529] In some embodiments, the status report is an RLC status report.

[0530] It should be noted that the network device includes one or more second entities, and each second entity in the network device includes at least one of the above-mentioned transceiver module 7201 or processing module 7202, and can all perform the above steps, which is not limited in the embodiments of the present disclosure.

[0531] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0532] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal, a chip, a chip system, or a processor that supports a network device in implementing any of the above methods, or a chip, a chip system, or an entity that supports a terminal in implementing any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0533] As shown in Figure 8A, a communication device 8100 includes one or more entities 8101. The communication device 8100 is configured to execute any of the above methods.

[0534] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0535] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2102, step S2103, step S2104, but not limited thereto).

[0536] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0537] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the entity 8101.

[0538] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal, an intelligent terminal, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0539] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0540] The chip 8200 includes one or more entities 8201 , and the chip 8200 is configured to execute any of the above methods.

[0541] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the entity 8201.

[0542] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the entity 8201 performs at least one of the other steps.

[0543] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0544] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0545] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0546] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0547] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A processing method, characterized in that: The method comprises: The first entity determines whether to trigger a status report based on a first amount of received data, where the status report is used to indicate a situation in which the first entity receives the data.

2. The method according to claim 1, characterized in that The first quantity refers to the amount of the data, and the first entity determines whether to trigger a status report based on the first quantity of the received data, including: The first entity determines whether to trigger the status report based on the data volume of the received data.

3. The method according to claim 2, characterized in that The first entity determines whether to trigger the status report based on the amount of the received data, including: If the amount of the data received by the first entity is greater than a first threshold, triggering the status report; or, If the amount of the data received by the first entity is not greater than the first threshold, the status report is not triggered.

4. The method according to claim 2 or 3, characterized in that The data includes an RLC SDU and / or an RLC SDU segment, and the data amount includes the data amount of the RLC SDU and / or the RLC SDU segment; or, The data includes an RLC data PDU, and the data amount includes the data amount of the RLC data PDU; or The data includes an RLC PDU, and the data amount includes the data amount of the RLC PDU.

5. The method according to claim 3 or 4, characterized in that The method further comprises: The terminal receives first information, where the first information is used to configure the first threshold; or, The first threshold is defined by a communication protocol; or, The first threshold is one of candidate thresholds preconfigured by the terminal.

6. The method according to claim 1, characterized in that The first quantity refers to the number of data packets carrying the data, and the first entity determines whether to trigger a status report based on the first quantity of received data, including: The first entity determines whether to trigger the status report based on the number of received data packets carrying the data.

7. The method according to claim 6, characterized in that The first entity determines whether to trigger the status report based on the number of received data packets carrying the data, including: If the number of data packets carrying the data received by the first entity is greater than a second threshold, triggering the status report; or, If the number of data packets carrying the data received by the first entity is not greater than the second threshold, the status report is not triggered.

8. The method according to claim 6 or 7, characterized in that The number of data packets is based on the RLC SDU count; or, The number of data packets is counted based on the number of RLC data PDUs; or The number of data packets is counted based on the number of RLC PDUs.

9. The method according to claim 7 or 8, characterized in that The method further comprises: The terminal receives second information sent by the network device, where the second information is used to configure the second threshold; or, The second threshold is defined by a communication protocol; or, The second threshold is one of candidate thresholds preconfigured by the terminal.

10. The method according to any one of claims 1 to 9, characterized in that: The first entity includes a counter, and the counter is used to count the received data.

11. The method according to claim 10, characterized in that The method further comprises: The first entity determines to trigger the status report and resets the counter to 0.

12. The method according to any one of claims 1 to 11, characterized in that: The first entity is an RLC entity.

13. The method according to any one of claims 1 to 12, characterized in that: The status report is an RLC status report.

14. The method according to any one of claims 1 to 13, characterized in that: The method further comprises: The first entity determines to trigger the status report; The first entity sends the status report.

15. The method according to any one of claims 1 to 14, characterized in that: The situation in which the first entity receives the data includes: Among the data received by the first entity, first data is received correctly; and / or second data is not received correctly; and / or whether the first entity receives the data correctly.

16. A processing method, characterized in that: The method comprises: The second entity receives a status report, where the status report is used to indicate a situation in which the first entity receives data.

17. The method according to claim 16, characterized in that The method further comprises: The network device sends first information, where the first information is used to configure a first threshold; or, The first threshold is defined by a communication protocol; or, The first threshold is one of candidate thresholds preconfigured by the terminal; The first threshold is used by the first entity to determine whether to send the status report.

18. The method according to claim 16, characterized in that The method further comprises: The network device sends second information, where the second information is used to configure a second threshold; or, The second threshold is defined by a communication protocol; or, The second threshold is one of candidate thresholds preconfigured by the terminal; The second threshold is used by the first entity to determine whether to send the status report.

19. The method according to any one of claims 16 to 18, characterized in that: The second entity is an RLC entity.

20. The method according to any one of claims 16 to 19, characterized in that The status report is an RLC status report.

21. The method according to any one of claims 16 to 20, characterized in that The situation in which the first entity receives the data includes: Among the data received by the first entity, first data is received correctly; and / or second data is not received correctly; and / or whether the first entity receives the data correctly.

22. A processing method, characterized in that: The method comprises: The first entity determines, based on a first amount of received data, whether to trigger a status report, where the status report is used to indicate a situation in which the first entity receives the data; The second entity receives the status report sent by the first entity.

23. A first entity, characterized in that: The first entity includes: The processing module is configured to determine, by the first entity, whether to trigger a status report based on a first amount of received data, where the status report is used to indicate a situation in which the first entity receives the data.

24. A second entity, characterized in that: The second entity includes: The transceiver module is used for the second entity to receive a status report sent by the first entity, where the status report is used to indicate a situation in which the first entity receives data.

25. A terminal, characterized in that: The terminal includes: one or more first entities; The first entity is configured to execute the processing method according to any one of claims 1 to 15.

26. A network device, characterized in that: The network equipment includes: one or more second entities; The second entity is configured to execute the processing method according to any one of claims 16 to 21.

27. A communication system, characterized in that: The invention comprises a terminal and a network device, wherein the terminal is configured to implement the processing method according to any one of claims 1 to 15, and the network device is configured to implement the processing method according to any one of claims 16 to 21.

28. A storage medium, characterized in that The storage medium stores instructions, and when the instructions are executed on the communication device, the communication device executes the processing method according to any one of claims 1 to 21.

29. A program product, characterized in that The program product is executed by a communication device, so that the communication device executes the processing method according to any one of claims 1 to 21.

Images