Communication method, RLC entity, PDCP entity, apparatus, and storage medium

Abstract

The present disclosure relates to a communication method, an RLC entity, a PDCP entity, an apparatus, and a storage medium. The method comprises: when it is determined that a preset timer has expired, moving a receiving window of a first RLC entity and generating an RLC status report; and sending to a second RLC entity the RLC status report. In the embodiments of the present disclosure, after a timer expires, a first RLC entity adjusts a receiving window and triggers an RLC status report, such that on the basis of the RLC status report, a second RLC entity does not retransmit a data packet discarded by a PDCP entity any more, thereby avoiding the wastes of radio resources.

Description

Communication method, RLC entity, PDCP entity, device and storage medium Technical Field

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

[0002] In the related art, when a state variable RX_DELIV of a PDCP entity increases due to expiration of a reordering timer t-Reordering, the PDCP entity discards a received PDCP PDU whose count value COUNT is less than RX_DELIV.

[0003] If the RLC entity corresponding to the PDCP entity is an Acknowledged Mode Radio Link Control (AM RLC) entity, the AM RLC entity continues to retransmit the RLC SDU that the PDCP entity is not waiting for according to a lossless working mode, thereby causing a waste of radio resources.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a communication method, an RLC entity, a PDCP entity, a device, and a storage medium.

[0006] In a first aspect, an embodiment of the present disclosure provides a communication method, performed by a first RLC entity, the method including:

[0007] determining that a preset timer has expired, moving a receiving window of the first RLC entity, and generating an RLC status report;

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

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

[0010] receiving a third message sent by a first RLC entity, where the third message includes a lower limit of a receiving window of the first RLC entity after the move, where the lower limit of the receiving window after the move is related to a preset timer of the first RLC entity;

[0011] Using the moved lower limit as the lower limit of the receiving window of the PDCP entity;

[0012] The preset timer is a reassembly timer or a first timer. After the reassembly timer or the first timer times out, the lower limit of the receiving window of the first RLC entity is moved.

[0013] In a third aspect, an embodiment of the present disclosure provides a first RLC entity, including:

[0014] a processing module, configured to determine that a preset timer has expired, move a receiving window of the first RLC entity, and generate an RLC status report;

[0015] A sending module is used to send the RLC status report to the second RLC entity.

[0016] In a fourth aspect, an embodiment of the present disclosure provides a PDCP entity, including:

[0017] a receiving module, configured to receive a third message sent by a first RLC entity, where the third message includes a lower limit of a receiving window of the first RLC entity after movement, where the lower limit of the receiving window after movement is related to a preset timer of the first RLC entity;

[0018] a processing module, configured to use the moved lower limit as the lower limit of the receiving window of the PDCP entity;

[0019] The preset timer is a reassembly timer or a first timer. After the reassembly timer or the first timer times out, the lower limit of the receiving window of the first RLC entity is moved.

[0020] In a fifth aspect, an embodiment of the present disclosure provides a first RLC entity, including:

[0021] one or more processors;

[0022] The first RLC entity is used to execute the communication method described in any one of the first aspects of the embodiments of the present disclosure.

[0023] In a sixth aspect, an embodiment of the present disclosure provides a PDCP entity, including:

[0024] one or more processors;

[0025] The PDCP entity is used to execute the communication method described in any one of the second aspects of the embodiments of this disclosure.

[0026] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, including: a first RLC entity and a PDCP entity; wherein the first RLC entity is configured to implement the communication method of any one of the first aspect of the embodiment of the present disclosure; and the PDCP entity is configured to implement the communication method of any one of the second aspect of the embodiment of the present disclosure.

[0027] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, which, when an instruction is executed on a communication device, enables the communication device to execute any one of the communication methods of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0029] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

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

[0031] FIG2B is an exemplary schematic diagram showing a situation in which a gap exists in an RLC SDU data packet received by a first RLC entity according to an embodiment of the present disclosure;

[0032] FIG2C is an exemplary schematic diagram showing a situation in which a gap exists in an RLC SDU data packet received by a first RLC entity according to an embodiment of the present disclosure;

[0033] FIG2D is an exemplary schematic diagram showing that there is no gap in the RLC SDU data packet received by the first RLC entity according to an embodiment of the present disclosure;

[0034] FIG2E is an exemplary schematic diagram showing that there is no gap in the RLC SDU data packet received by the first RLC entity according to an embodiment of the present disclosure;

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

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

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

[0038] FIG6 is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure;

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

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

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

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

[0043] The embodiments of the present disclosure provide a communication method, an RLC entity, a PDCP entity, a device, and a storage medium.

[0044] In a first aspect, an embodiment of the present disclosure provides a communication method, which is performed by a first RLC entity. The method includes:

[0045] determining that a preset timer has expired, moving a receiving window of the first RLC entity, and generating an RLC status report;

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

[0047] In the above embodiment, after the preset timer expires, the receiving window of the first RLC entity is moved and an RLC status report is generated, and the first RLC entity status report is sent to the second RLC entity; in this way, after the second RLC entity receives the RLC status report, it will no longer retransmit the data packet that the PDCP entity will discard, thereby avoiding waste of wireless resources.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the first RLC entity is located in a terminal device, and the second RLC entity is located in a base station device;

[0049] The duration of the preset timer is determined by the following methods, including:

[0050] receiving a first message sent by the base station device, where the first message includes a first value, and the first value is used to indicate the duration of the preset timer;

[0051] Using the first value as the duration of the preset timer;

[0052] The first value is determined by the base station device according to the duration of the reordering timer t-Reordering.

[0053] In the above embodiment, a method is provided in which the terminal device uses the first value sent by the base station device as the duration of the preset timer.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, determining that a preset timer has timed out also includes:

[0055] receiving an RLC data packet sent by a second RLC entity;

[0056] updating a state variable according to the RLC data packet;

[0057] According to the updated state variable, it is determined that the condition for starting the preset timer is met, and the preset timer is started.

[0058] In the above embodiment, the state variable of the first RLC entity is updated according to the RLC data packet, and the updated state variable is used as the starting condition of the preset timer.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the RLC data packet includes first information or second information, the first information includes a sequence number of an RLC SDU, and the second information includes a sequence number of an RLC SDU segment;

[0060] The state variables include a receiving state variable RX_Next or a highest receiving state variable RX_Next_Highest;

[0061] The updating of the state variable according to the RLC data packet comprises:

[0062] Update RX_Next or RX_Next_Highest according to the sequence number of the RLC SDU or the sequence number of the RLC SDU segment.

[0063] In the above embodiment, a method for updating the state variable of the first RLC entity according to the sequence number of the RLC SDU or the sequence number of the RLC SDU segment is provided.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the preset timer is a first timer;

[0065] A starting condition of the first timer is that there is a gap in the received RLC data packet.

[0066] In the above embodiment, a method for starting a first timer is provided.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the presence of gaps in the received RLC data packets is determined by any one of the following methods:

[0068] The difference between the RX_Next_Highest and the RX_Next is greater than a first preset threshold;

[0069] The difference between the RX_Next_Highest and the RX_Next is greater than a second preset threshold, and there is at least one lost RLC SDU segment before the last RLC SDU segment of the received RLC SDU, wherein the sequence number of the RLC SDU is equal to RX_Next.

[0070] In the above embodiment, a method for determining whether gaps exist in received RLC data packets is provided.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the state variable further includes: RX_Highest_Status and RX_Next_Status_Trigger;

[0072] The moving the receiving window of the first RLC entity includes any one of the following:

[0073] Updating the lower limit of the receiving window to a sequence number of the first RLC SDU that is not completely received and is greater than RX_Next;

[0074] Updating the lower limit of the receive window to a sequence number of the first RLC SDU that is not completely received and is greater than or equal to RX_Next_Status_Trigger;

[0075] The lower limit of the receiving window is updated to RX_Highest_Status.

[0076] In the above embodiment, when the preset timer is the first timer, the operation of updating the lower limit of the receiving window of the first RLC entity is implemented.

[0077] In combination with some embodiments of the first aspect, in some embodiments, the preset timer is a reassembly timer.

[0078] In the above embodiment, a method is provided for moving the receiving window of the first RLC entity when the reassembly timer times out.

[0079] In conjunction with some embodiments of the first aspect, in some embodiments, the first RLC entity is located in a terminal device;

[0080] The step of determining that a preset timer has timed out also includes:

[0081] A second message sent by a base station device is received, where the second message is used to instruct to move the receiving window of the first RLC entity after the reassembly timer times out.

[0082] In the above embodiment, a method is provided for configuring the terminal device to move the receiving window of the first RLC entity after the reassembly timer times out.

[0083] In conjunction with some embodiments of the first aspect, in some embodiments, the state variable further includes a next receive state variable trigger RX_Next_Status_Trigger;

[0084] The moving the receiving window of the first RLC entity includes any one of the following:

[0085] Updating the lower limit of the receiving window to a sequence number of the first RLC SDU that is not completely received and is greater than RX_Next;

[0086] The lower limit of the receiving window is updated to a sequence number of the first RLC SDU that is not completely received and is greater than or equal to RX_Next_Status_Trigger.

[0087] In the above embodiment, when the preset timer is a reassembly timer, the operation of updating the lower limit of the receiving window of the first RLC entity is implemented.

[0088] In conjunction with some embodiments of the first aspect, in some embodiments, the moving the receiving window of the first RLC entity further includes:

[0089] Sending a third message to a Packet Data Convergence Protocol (PDCP) entity;

[0090] The third message includes the lower limit of the receiving window after it moves; the third message is used to instruct the PDCP entity to use the lower limit of the receiving window after it moves as the lower limit of the receiving window of the PDCP entity.

[0091] In the above embodiment, a method for determining the lower limit of the receiving window of the PDCP entity according to the lower limit of the mobile receiving window of the first RLC entity is provided.

[0092] In a second aspect, an embodiment of the present disclosure provides a communication method, performed by a PDCP entity, the method including:

[0093] receiving a third message sent by a first RLC entity, where the third message includes a lower limit of a receiving window of the first RLC entity after the move, where the lower limit of the receiving window after the move is related to a preset timer of the first RLC entity;

[0094] Using the moved lower limit as the lower limit of the receiving window of the PDCP entity;

[0095] The preset timer is a reassembly timer or a first timer. After the reassembly timer or the first timer times out, the lower limit of the receiving window of the first RLC entity is moved.

[0096] In the above embodiment, a method is provided for the PDCP entity to determine the lower limit of its own receiving window according to the lower limit of the mobile receiving window of the first RLC entity.

[0097] In conjunction with some embodiments of the second aspect, in some embodiments, the preset timer is a reassembly timer;

[0098] The lower limit of the receiving window of the first RLC entity after moving is any one of the following:

[0099] A sequence number greater than the first incompletely received RLC SDU of RX_Next of the first RLC entity;

[0100] The sequence number of the first incompletely received RLC SDU that is greater than or equal to the RX_Next_Status_Trigger of the first RLC entity.

[0101] In the above embodiment, a method for determining the lower limit of the receiving window of the first RLC entity is provided when the preset timer is a reassembly timer.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the preset timer is a first timer;

[0103] The lower limit of the receiving window of the first RLC entity after moving is any one of the following:

[0104] A sequence number greater than the first incompletely received RLC SDU of RX_Next of the first RLC entity;

[0105] a sequence number of the first incompletely received RLC SDU that is greater than or equal to the RX_Next_Status_Trigger of the first RLC entity;

[0106] RX_Highest_Status of the first RLC entity.

[0107] In the above embodiment, a method for determining the lower limit of the receiving window of the first RLC entity is provided when the preset timer is the first timer.

[0108] In a third aspect, an embodiment of the present disclosure provides a first RLC entity, including:

[0109] a processing module, configured to determine that a preset timer has expired, move a receiving window of the first RLC entity, and generate an RLC status report;

[0110] A sending module is used to send the RLC status report to the second RLC entity.

[0111] In a fourth aspect, an embodiment of the present disclosure provides a PDCP entity, including:

[0112] a receiving module, configured to receive a third message sent by a first RLC entity, where the third message includes a lower limit of a receiving window of the first RLC entity after movement, where the lower limit of the receiving window after movement is related to a preset timer of the first RLC entity;

[0113] a processing module, configured to use the moved lower limit as the lower limit of the receiving window of the PDCP entity;

[0114] The preset timer is a reassembly timer or a first timer. After the reassembly timer or the first timer times out, the lower limit of the receiving window of the first RLC entity is moved.

[0115] In a fifth aspect, an embodiment of the present disclosure provides a first RLC entity, including:

[0116] one or more processors;

[0117] The first RLC entity is used to execute the communication method described in any one of the first aspects of the embodiments of the present disclosure.

[0118] In a sixth aspect, an embodiment of the present disclosure provides a PDCP entity, including:

[0119] one or more processors;

[0120] The PDCP entity is used to execute the communication method described in any one of the second aspects of the embodiments of this disclosure.

[0121] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, including a first RLC entity and a PDCP entity; wherein the first RLC entity is configured to implement the communication method of any one of the first aspect of the embodiment of the present disclosure; and the PDCP entity is configured to implement the communication method of any one of the second aspect of the embodiment of the present disclosure.

[0122] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, which, when an instruction is executed on a communication device, enables the communication device to execute any one of the communication methods of the embodiments of the present disclosure.

[0123] 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 described in the optional implementation of the first and second aspects.

[0124] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0125] 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 the method described in the optional implementation of the first and second aspects above.

[0126] It is understandable that the first RLC entity, PDCP entity, communication system, storage medium, program product, computer program, chip, or chip system described above are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0127] The embodiments of the present disclosure provide a communication method, a first RLC entity, a PDCP entity, an apparatus, and a storage medium. In some embodiments, the terms communication method, signal transmission method, and radio frame transmission method are interchangeable, and the terms information processing system, communication system, and the like are interchangeable.

[0128] 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.

[0129] 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.

[0130] 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.

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

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

[0133] 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.

[0134] 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.

[0135] 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.

[0136] 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.

[0137] 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.

[0138] In some embodiments, terms such as "greater than", "less 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.

[0139] 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", "device", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0140] In some embodiments, “access network device (AN device)”, “radio access network device (radio

[0141] The terms access network device (RAN device),” “base station (BS)”, “radio base station”, “fixed station”, “node”, “access point”, “transmission point (TP)”, “reception point (RP)”, “transmission / reception point (TRP)”, “panel”, “antenna panel”, “antenna array”, “cell”, “macro cell”, “small cell”, “femto cell”, “pico cell”, “sector”, “cell group”, “carrier”, “component carrier”, and “bandwidth part (BWP)” are used interchangeably.

[0142] In some embodiments, the device may refer to a device on the ground, such as an access network device and / or a core network device on the ground; it may also refer to a device on a satellite, such as an access network device and / or a core network device on a satellite; the embodiments of the present disclosure do not limit whether the device is a device on the ground or a device on a satellite, nor do they limit whether the device refers to an access network device or a core network device.

[0143] In some embodiments, the terms "terminal", "terminal device", "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. can be used interchangeably.

[0144] In some embodiments, the device may refer to a device on the ground, such as an access network device and / or a core network device on the ground; it may also refer to a device on a satellite, such as an access network device and / or a core network device on a satellite; the embodiments of the present disclosure do not limit whether the device is a device on the ground or a device on a satellite, nor do they limit whether the device refers to an access network device or a core network device.

[0145] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, it can also be called device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, language such as "uplink" and "downlink" can also be replaced by language corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0146] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0147] 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.

[0148] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0149] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

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

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

[0152] In some embodiments, "predetermined" and "preset" can be interpreted as pre-specified in a protocol, etc., or can be interpreted as a pre-set action performed by a device, etc.

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

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

[0155] 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.

[0156] FIG1 is an exemplary schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a first RLC entity 101 , a second RLC entity 102 , and a PDCP entity 103 .

[0157] In some embodiments, the terminal includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, 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 a wireless terminal device in a smart home, but is not limited thereto. It is 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. It is known to those skilled in the art that with the evolution of 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. The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or a portion of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and configuration of the entities may be arbitrary. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected. The connection may be in any manner, whether direct or indirect, and wired or wireless.

[0158] The embodiments of the present disclosure may 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), 5th generation mobile communication system-Advanced (5G-Advanced), 6th generation mobile communication system (6G), 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 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 communication methods, and next-generation systems based on and extending these methods. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be employed.

[0159] In some embodiments, the 3GPP Radio Link Control (RLC) entity includes three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM); accordingly, an RLC entity can be classified as a TM RLC entity, a UM RLC entity, and an AM RLC entity. An AM RLC entity consists of a transmitting side and a receiving side. For an RLC entity configured on the network side, a peer RLC entity is configured on the user equipment (UE) side, and vice versa. An RLC entity receives an RLC SDU from an upper layer (e.g., a PDCP layer) and sends an RLC PDU to a peer RLC entity through a lower layer (e.g., a MAC layer); or, receives an RLC PDU from a peer RLC entity through a lower layer and passes the RLC SDU to an upper layer. When the space provided by the MAC layer is insufficient to transmit a complete RLC SDU, the RLC SDU is transmitted in segments, which are accordingly called RLC SDU segments.

[0160] In some embodiments, RLC PDUs are classified 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 to send RLC status reports to the peer RLC entity when used for automatic repeat reQuest (ARQ).

[0161] In some embodiments, when the reassembly timer t-Reassembly expires, the receiving side of the AM RLC entity triggers an RLC status report; the automatic repeat request function of the peer RLC entity retransmits the RLC SDU or RLC SDU segment according to the RLC status report.

[0162] In some embodiments, the AM RLC entity maintains a window on both the sending side and the receiving side. The sending side of the AM RLC entity maintains a transmitting window according to the status variable TX_Next_Ack. When the sequence number (SN) of the AMD PDU is within the following range: TX_Next_Ack <= SN < TX_Next_Ack + AM_Window_Size, the sequence number of the AMD PDU is considered to be within the transmitting window; where AM_Window_Size is the size of the window. For 12-bit and 18-bit sequence numbers, AM_Window_Size is 2048 and 131072 respectively. The AM RLC entity does not send the AMD PDU with a sequence number outside the transmitting window to the lower layer. The status variable TX_Next_Ack is the lower edge of the transmitting window. When it receives an RLC status report indicating that the RLC SDU with a sequence number equal to TX_Next_Ack has been completely received, the AM RLC entity updates TX_Next_Ack.

[0163] In some embodiments, the receiving side of the AM RLC entity maintains a receiving window according to the status variable RX_Next, that is, when the sequence number of the AMD PDU is within the following range: RX_Next <= SN < RX_Next + AM_Window_Size, the sequence number of the AMD PDU is considered to be within the receiving window; where the definition of AM_Window_Size is as described above. The AM RLC entity discards the AMD PDU outside the receiving window. The status variable RX_Next is the lower edge of the receiving window. When the RLC SDU with a sequence number equal to RX_Next has been completely received, the AM RLC entity updates RX_Next.

[0164] In some embodiments, when the AM RLC entity constructs an RLC status report, it reports the information of the incompletely received RLC SDUs starting from the sequence number RX_Next.

[0165] In some embodiments, the information of the missing segments includes: SOstart and SOend; where the value of SOstart indicates from which byte of the original SDU the missing SDU segment starts; the value of SOend indicates at which byte of the original SDU the missing SDU segment ends.

[0166] It should be noted that the ACK_SN field in the RLC status report is used to indicate the sequence number of the next unreceived RLC SDU that was not lost. Upon receiving the status report, the transmitting side of the AM RLC entity will assume that all RLC SDUs with sequence numbers less than ACK_SN have been correctly received, except for the RLC SDU indicated by NACK_SN in the status report and the RLC SDU segments indicated by NACK_range, SOstart, and SOend.

[0167] It should be noted that the current NR RLC AM operating mode is lossless. This means that when an RLC SDU with a sequence number equal to RX_Next is not completely received, the AM RLC entity notifies the peer RLC entity of the incomplete reception of the RLC SDU through a status report. The transmitting side of the peer AM RLC entity performs ARQ retransmissions until the RLC SDU with a sequence number equal to RX_Next is completely received, at which point the state variable RX_Next is updated.

[0168] It should also be noted that the PDCP entity's state variable RX_DELIV indicates the COUNT value of the first PDCP SDU that has not yet been submitted to upper layers but is awaiting delivery. A received PDCP PDU with a COUNT value less than RX_DELIV is discarded. The PDCP entity maintains a reordering timer (t-Reordering). When this timer expires, the RX_DELIV value increases.

[0169] In the above embodiment, when the PDCP entity's state variable RX_DELIV increases due to the expiration of the t-Reordering timer, the PDCP entity discards received PDCP PDUs whose COUNT value is less than RX_DELIV. If the RLC entity corresponding to the PDCP entity is an AM RLC entity, the AM RLC entity will continue to retransmit RLC SDUs that the PDCP entity is not waiting for in a lossless mode until they are completely received. Therefore, retransmitting data packets that the PDCP entity discarded will result in a waste of radio resources.

[0170] FIG2A is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a communication method for use in a communication system 100, the method comprising:

[0171] Step S2101: The second RLC entity sends an RLC data packet.

[0172] In some embodiments, the RLC data packet includes the first information or the second information.

[0173] In some embodiments, the first information may include an RLC SDU and a sequence number of the RLC SDU. In some embodiments, the number of RLC SDUs in the first information is one.

[0174] In some embodiments, the second information may include an RLC SDU segment and a sequence number of the RLC SDU segment. In some embodiments, the number of RLC SDUs in the first information is 1.

[0175] In the embodiment of the present disclosure, the first RLC entity and the second RLC entity may be AM RLC entities, and the second RLC entity is a peer RLC entity of the first RLC entity.

[0176] In some embodiments, one AM RLC entity has both a receiving side and a transmitting side.

[0177] In some embodiments, the receiving side and the transmitting side of the RCL entity exist simultaneously in a base station device or a terminal device.

[0178] It should be noted that when the first RLC entity is located in the base station device, the second RLC entity is located in the terminal device; conversely, when the first RLC entity is located in the terminal device, the second RLC entity is located in the base station device. The embodiments of this disclosure do not limit whether the first RLC entity is located in the base station device or the terminal device.

[0179] Optionally, the RLC entity also has a corresponding PDCP entity; it can be understood that the base station device has a corresponding PDCP entity, and the terminal device also has a corresponding PDCP entity.

[0180] In the embodiments of the present disclosure, the base station device may adopt a centralized unit and a distributed unit separated architecture, or may not adopt a centralized unit and a distributed unit separated architecture. The embodiments of the present disclosure do not limit whether the base station device adopts a centralized unit and a distributed unit separated architecture.

[0181] Step S2102: When a preset timer times out, the receiving window of the first RLC entity is moved and an RLC status report is generated.

[0182] In some embodiments, the first RLC entity updates its own state variable according to the sequence number of the received RLC SDU or the sequence number of the RLC SDU segment.

[0183] In some embodiments, the state variables of the first RLC entity include, but are not limited to: RX_Next, RX_Next_Highest, RX_Highest_Status, and RX_Next_Status_Trigger.

[0184] For example, if the current RX_Next value of the first RLC entity is 2 and the sequence number of the received RLC SDU is 2, the RX_Next value is updated to 3; otherwise, if the sequence number of the received RLC SDU is not 2, the RX_Next value is not updated.

[0185] For example: before receiving the RLC data packet, the maximum value of the RLC SDU sequence number received by the first RLC entity is 2. At this time, the value of RX_Next_Highest is 3; when receiving the RLC data packet, when the sequence number of the RLC SDU carried in the RLC data packet is 3, the value of RX_Next_Highest is updated to 4.

[0186] For example, before receiving an RLC data packet, the maximum RLC SDU sequence number received by the first RLC entity is 1. In this case, the value of RX_Next_Status_Trigger is 2. When receiving an RLC data packet, if the sequence number of the RLC SDU carried in the RLC data packet is 3, it means that the RLC SDU with sequence number 2 has not been received. After the timer expires, the reassembly timer is started again, and the value of RX_Next_Status_Trigger is updated to 4.

[0187] For example: before receiving the RLC data packet, the maximum value of the RLC SDU sequence number received by the first RLC entity is 1. At this time, RX_Highest_Status is 2; when receiving the RLC data packet, when the sequence number of the RLC SDU carried by the RLC data packet is 2, the value of RX_Highest_Status is updated to 3.

[0188] It should be noted that the above examples are only examples for those skilled in the art to understand the relationship between each state variable and the RLC SDU sequence number. The definition and value of each state variable can refer to the description of the relevant chapters in the 3GPP protocol. The embodiments of the present disclosure do not limit the actual values ​​of each state variable.

[0189] In some embodiments, the first RLC entity determines, based on the updated state variable, that a condition for starting a timer is met, and starts the timer.

[0190] In an embodiment of the present disclosure, the preset timer may be a reassembly timer or a first timer; wherein, the start condition of the reassembly timer may refer to the contents of the relevant sections of the 3GPP protocol; the start condition of the first timer is that there is a gap in the received RLC SDU data packet.

[0191] In some embodiments, when the difference between RX_Next_Highest and RX_Next is greater than a first preset threshold, it is determined that there is a gap in the received RLC SDU data packets.

[0192] In some embodiments, when the difference between RX_Next_Highest and RX_Next is greater than a second preset threshold and there is at least one lost RLC SDU segment before the last RLC SDU segment of the received RLC SDU, it is determined that there is a gap in the received RLC SDU data packet; wherein the sequence number of the RLC SDU is equal to RX_Next.

[0193] Optionally, the first preset threshold and the second preset threshold may be 1. The embodiment of the present disclosure does not limit specific values ​​of the first preset threshold and the second preset threshold.

[0194] In some embodiments, after the first timer is started, if there is no gap in the subsequently received RLC SDU data packets, the first timer is stopped.

[0195] Optionally, when the first timer is used, if RX_Next or RX_Next_Highest is updated, it is detected whether the start condition and / or stop condition of the first timer is met.

[0196] Optionally, when the first timer is used, only when RX_Next is updated is it detected whether the start condition and / or stop condition of the first timer is met.

[0197] FIG2B is an exemplary schematic diagram illustrating a gap in an RLC SDU data packet received by a first RLC entity according to an embodiment of the present disclosure. As shown in the figure, gray rectangles represent sequence numbers of RLC SDUs received by the first RLC entity, and white rectangles represent sequence numbers of RLC SDUs not received. The first RLC entity has received an RLC SDU with sequence number 2. Therefore, the current value of RX_Next is 3, and the value of RX_Next_Highest is also 3. When the RLC data packet includes an RLC SDU with sequence number 4, it indicates that the RLC SDU with sequence number 3 has not been received. In this case, the value of RX_Next_Highest is updated to 5, and the difference between RX_Next_Highest and RX_Next is 2, which is greater than a first preset threshold (assuming that the first preset threshold is 1 at this time), satisfying the condition for a gap in the RLC SDU data packet. Therefore, it can be determined that a gap exists in the received RLC SDU data packet.

[0198] Figure 2C is an exemplary schematic diagram showing the existence of gaps in the RLC SDU data packets received by the first RLC entity according to an embodiment of the present disclosure. As shown in the figure, the gray rectangles represent the sequence numbers of the RLC SDUs or RLC SDU segments that have been received by the first RLC entity, and the white rectangles represent the sequence numbers of the RLC SDUs or RLC SDU segments that have not been received. The first RLC entity has received the RLC SDU with sequence number 2. Therefore, the current RX_Next value is 3, and the RX_Next_Highest value is also 3. When the RLC data packet includes the RLC SDU segment with sequence number 3, the RX_Next_Highest value is updated to 4. However, only a partial segment of the SDU with sequence number 3 has been received, namely, the gray portion of the rectangle where SN=3 is located in FIG2D . Therefore, the RX_Next value is still 3. The difference between RX_Next_Highest and RX_Next is 1, which is greater than the first preset threshold (assuming that the first preset threshold is 1 at this time). In addition, there is a missing RLC SDU segment before the last RLC SDU segment received for the RLC SDU with sequence number 3, namely, the white portion of the rectangle where SN=3 is located in FIG2D . This satisfies the condition that there is a gap in the RLC SDU data packet. Therefore, it can be determined that there is a gap in the received RLC SDU data packet.

[0199] Figure 2D is an exemplary schematic diagram illustrating the absence of gaps in an RLC SDU data packet received by a first RLC entity according to an embodiment of the present disclosure. As shown in the figure, gray rectangles represent sequence numbers of RLC SDUs received by the first RLC entity, and white rectangles represent sequence numbers of RLC SDUs not received. The first RLC entity has received an RLC SDU with sequence number 2. Therefore, the current value of RX_Next is 3, and the value of RX_Next_Highest is also 3. When the RLC data packet includes an RLC SDU with sequence number 3, the values ​​of RX_Next and RX_Next_Highest are updated to 4, and the difference between RX_Next_Highest and RX_Next is 0, which is less than a first preset threshold (assuming that the first preset threshold is 1 at this time), and the condition for the presence of gaps in the RLC SDU data packet is not met. Therefore, it can be determined that there are no gaps in the received RLC SDU data packet.

[0200] Figure 2E is an exemplary schematic diagram showing that there are no gaps in the RLC SDU data packets received by the first RLC entity according to an embodiment of the present disclosure. As shown in the figure, the gray rectangles represent the sequence numbers of the RLC SDUs or RLC SDU segments that have been received by the first RLC entity, and the white rectangles represent the sequence numbers of the RLC SDUs or RLC SDU segments that have not been received. The first RLC entity has received the RLC SDU with sequence number 2. Therefore, the current RX_Next value is 3, and the RX_Next_Highest value is also 3. When the RLC data packet includes the RLC SDU segment with sequence number 3, the RX_Next_Highest value is updated to 4. However, only a partial segment of the SDU with sequence number 3 has been received, namely, the gray portion of the rectangle where SN=3 is located in FIG2D . Therefore, the RX_Next value is still 3, and the difference between RX_Next_Highest and RX_Next is 1, which is greater than the first preset threshold (assuming that the first preset threshold is 1 at this time). However, there is no lost RLC SDU segment before the last RLC SDU segment received for the RLC SDU with sequence number 3. That is, the gray portion of the rectangle where SN=3 and the gray portion of the rectangle where SN=2 are located in FIG2E are continuous, which does not meet the condition for a gap in the RLC SDU data packet. Therefore, it can be determined that there is no gap in the received RLC SDU data packet.

[0201] In some embodiments, when the first RLC entity is located in a terminal device and the second RLC entity is located in a base station device, the base station device sends a first message to the terminal device, the first message includes a first value, and the first value is used to indicate the duration of the timer.

[0202] In some embodiments, the terminal uses the first value as the duration of the reassembly timer or the first timer.

[0203] In some optional examples, if the base station device adopts a separate architecture of a centralized unit and a distributed unit, the centralized unit sends the duration of the reordering timer to the distributed unit; the distributed unit determines a first value based on the duration of the reordering timer and sends a first message to the terminal device. It should be noted that the centralized unit can send the duration of the reordering timer to the distributed unit through signaling between network entities, for example, the centralized unit can send the duration of the reordering timer to the distributed unit through F1 signaling.

[0204] It should be noted that, in the embodiment of the present disclosure, the first RLC entity needs to be configured accordingly so that the receiving side window of the first RLC entity can be moved after the reassembly timer or the first timer times out.

[0205] In some embodiments, if the timer is a reassembly timer, the AM RLC receiving side can be configured via RRC signaling to determine whether to move the receiving window when the reassembly timer expires. This configuration can be configured for each first RLC entity, each MAC entity, or each terminal device.

[0206] Optionally, when this configuration is configured separately for each first RLC entity by RRC signaling, it can be configured in the IE RLCBearerConfig or RLC-Config. When this configuration is configured separately for each MAC entity by RRC signaling, it can be configured in the IE CellGroupConfig. When configured separately for each MAC entity, the first RLC entity associated with the MAC entity is configured accordingly.

[0207] Optionally, when configured for each terminal device, a second message sent by the base station device can be received, where the second message is used to indicate that the receiving window of the first RLC entity should be moved after the reassembly timer times out.

[0208] In some embodiments, configuration may be added to the RLC BearerConfig IE of 3GPP TS 38.331 so that the AM RLC receiving side adjusts the receiving window after the reassembly timer expires.

[0209] For example: RLC-Config-v1900IE can be added to RLCBearerConfig IE; wherein, the suffix v1900 of 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, then the suffix will change accordingly, for example: when introduced in Rel-20, the suffix will be v2000. The introduced field moveWindow is used to instruct the first RLC entity to adjust the receiving window of the first RLC entity after the reassembly timer t-Reassembly times out. It can be understood that when moveWindow is configured, that is, when moveWindow takes the value of true (true), the first RLC entity moves the receiving window after the reassembly timer times out.

[0210] The ASN.1 example in 3GPP TS 38.331 is as follows:

[0211] In some embodiments, section 5.2.3.2.4 of 3GPP TS 38.322 includes the following standard description:

[0212] Update RX_Highest_Status to the sequence number of the first RLC SDU; wherein the sequence number of the RLC SDU is the sequence number of the first RLC SDU that is not completely received and is greater than or equal to RX_Next_Status_Trigger;

[0213] If moveRLC-Window is configured, set the value of RX_Next to the value of RX_Highest_Status;

[0214] If RX_Next_Highest>RX_Highest_Status+1, or if RX_Next_Highest=RX_Highest_Status+1, and there is at least one lost RLC SDU segment before the last RLC SDU segment received by the RLC SDU, and the sequence number of the RLC SDU is equal to RX_Highest_Status; then start the reassembly timer and update the value of RX_Next_Status_Trigger to the value of RX_Next_Highest.

[0215] In the above embodiment, “if moveRLC-Window is configured, then the value of RX_Next is set to the value of RX_Highest_Status” is a newly added content in Section 5.2.3.2.4 of 3GPP TS 38.322 in the embodiment of the present disclosure.

[0216] In the above embodiment, RX_Next is updated to the sequence number of the first incompletely received RLC SDU greater than or equal to RX_Next_Status_Trigger, that is, the updated RX_Highest_Status; or, RX_Next is updated to the sequence number of the first incompletely received RLC SDU greater than the current RX_Next.

[0217] Correspondingly, the English description of the above standards is as follows:

[0218] When t-Reassembly expires, the receiving side of an AM RLC entity shall:

[0219] -update RX_Highest_Status to the SN of the first RLC SDU with SN>=RX_Next_Status_Trigger for which not all bytes have been received;

[0220] -if moveRLC-Window is configured:

[0221] -set RX_Next to RX_Highest_Status;

[0222] -if RX_Next_Highest>RX_Highest_Status+1:or

[0223] -if RX_Next_Highest=RX_Highest_Status+1 and there is at least one missing byte segment of the SDU associated with SN=RX_Highest_Status before the last byte of all received segments of this SDU:

[0224] -start t-Reassembly;

[0225] -set RX_Next_Status_Trigger to RX_Next_Highest.

[0226] It should be noted that the newly added content in the above English description is as follows, including:

[0227] -if moveRLC-Window is configured:

[0228] -set RX_Next to RX_Highest_Status;

[0229] In some embodiments, after the reassembly timer expires, moving the receiving window of the first RLC entity includes any one of the following:

[0230] Updating the lower limit of the receiving window to a sequence number of the first RLC SDU that is not completely received and is greater than RX_Next;

[0231] The lower limit of the receiving window is updated to a sequence number of the first RLC SDU that is not completely received and is greater than or equal to RX_Next_Status_Trigger.

[0232] If the timer is the first timer, a timer may be configured in a related communication protocol, such as RLC BearerConfig IE in 3GPP TS 38.331, to move the receiving window of the first RLC entity.

[0233] For example, the RLC-Config-v1900 IE can be added to the RLC BearerConfig IE. The suffix v1900 in the RLC-Config IE indicates its introduction in 3GPP Rel-19. This IE may also be introduced in other 3GPP releases or versions, in which case the suffix will change accordingly. For example, in Rel-20, the suffix will be v2000. The introduced field t-Window is used to indicate the duration of the receive window timer of the mobile first RLC entity.

[0234] The ASN.1 example in 3GPP TS 38.331 is as follows:

[0235] In some embodiments, the relevant communication protocol, for example, Section 5.2.3.2.3 of 3GPP TS 38.322, includes the following description:

[0236] When an AMD PDU with sequence number equal to x is placed in the receive buffer, the receiving side of the AM RLC entity shall perform the following operations:

[0237] If x>=RX_Next_Highest:

[0238] Update RX_Next_Highest to x+1.

[0239] If all bytes of the RLC SDU with sequence number equal to x are received:

[0240] reassembling the RLC SDU from the AMD PDU with sequence number equal to x, removing the RLC header when doing so, and delivering the reassembled RLC SDU to upper layers;

[0241] If x = RX_Highest_Status:

[0242] Update RX_Highest_Status to the sequence number of the first RLC SDU greater than RX_Highest_Status for which not all bytes have been received.

[0243] If x = RX_Next:

[0244] Update RX_Next to the sequence number of the first RLC SDU greater than the current RX_Next for which all bytes have not yet been received.

[0245] If RX_Next_Highest>RX_Next+1; or, if RX_Next_Highest=RX_Next+1, and there is at least one missing RLC SDU segment before the last RLC SDU segment of the received RLC SDU, where the sequence number of the RLC SDU is equal to RX_Next:

[0246] If the timer t-Window is not running at this time, start t-Window;

[0247] If the timer t-Window is running at this time, stop and reset t-Window.

[0248] It should be noted that, in the above embodiments, the following contents are newly added to Section 5.2.3.2.3 of 3GPP TS 38.322 in the embodiments of the present disclosure, including:

[0249] If RX_Next_Highest>RX_Next+1; or, if RX_Next_Highest=RX_Next+1, and there is at least one missing RLC SDU segment before the last RLC SDU segment of the received RLC SDU, where the sequence number of the RLC SDU is equal to RX_Next:

[0250] If the timer t-Window is not running at this time, start t-Window;

[0251] If the timer t-Window is running at this time, stop and reset t-Window.

[0252] Correspondingly, the English description of the above standards is as follows:

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

[0254] shall:

[0255] -if x>=RX_Next_Highest:

[0256] -update RX_Next_Highest to x+1.

[0257] -if all bytes of the RLC SDU with SN=x are received:

[0258] -reassemble the RLC SDU from AMD PDU(s)with SN=x,remove RLC headers when doing so and deliver the reassembled RLC SDU to upper layer;

[0259] -if x=RX_Highest_Status:

[0260] -update RX_Highest_Status to the SN of the first RLC SDU with SN>current RX_Highest_Status for which not all bytes have been received.

[0261] -if x=RX_Next:

[0262] -update RX_Next to the SN of the first RLC SDU with SN>current RX_Next for which not all bytes have been received.

[0263] -if RX_Next_Highest>RX_Next+1;or

[0264] -if RX_Next_Highest=RX_Next+1 and there is at least one missing byte segment of the SDU associated with SN=RX_Next before the last byte of all received segments of this SDU:

[0265] -if t-Window is not running:

[0266] -start t-Window;

[0267] -else if t-Window is running:

[0268] -stop and reset t-Window.

[0269] […omitted…]

[0270] It should be noted that the newly added content in the above English description is as follows, including:

[0271] -if RX_Next_Highest>RX_Next+1; or

[0272] -if RX_Next_Highest=RX_Next+1 and there is at least one missing byte segment of the SDU associated with SN=RX_Next before the last byte of all received segments of this SDU:

[0273] -if t-Window is not running:

[0274] -start t-Window;

[0275] -else if t-Window is running:

[0276] -stop and reset t-Window.

[0277] In some embodiments, the following description is added to a relevant communication protocol, such as a 3GPP protocol:

[0278] When the timer t-Window expires, the receiving side of the AM RLC entity shall perform the following operations:

[0279] Update RX_Next to the sequence number of the first RLC SDU that is not completely received and is greater than RX_Next;

[0280] If RX_Next_Highest > RX_Next + 1; or,

[0281] If RX_Next_Highest = RX_Next + 1, there is at least one lost RLC SDU segment before the last RLC SDU segment of the received RLC SDU, where the sequence number of the RLC SDU is equal to RX_Next:

[0282] Start timer t-Window.

[0283] Correspondingly, the English description of the above standards is as follows:

[0284] When t-Window expires, the receiving side of an AM RLC entity shall:

[0285] -update RX_Next to the SN of the first RLC SDU with SN>RX_Next for which not all bytes have been received;

[0286] -if RX_Next_Highest>RX_Next+1; or

[0287] -if RX_Next_Highest=RX_Next+1 and there is at least one missing byte segment of the SDU associated with SN=RX_Next before the last byte of all received segments of this SDU:

[0288] -start t-Window;

[0289] In some embodiments, the relevant communication protocol, for example, Section 5.3.4 of 3GPP TS 38.322, includes the following description:

[0290] The AM RLC entity sends an RLC status report to the peer AM RLC entity to provide positive and / or negative acknowledgement of the RLC SDU (or part thereof).

[0291] The triggers for starting RLC status reporting include:

[0292] Polling of the peer AM RLC entity:

[0293] When receiving an AMD PDU with a sequence number equal to x and the P field set to "1" from a lower layer, the receiving side of the AM RLC entity shall perform the following operations:

[0294] If the AMD PDU is discarded as specified in Subclause 5.2.3.2.2; or

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

[0296] Trigger an RLC status report.

[0297] Otherwise:

[0298] Delay triggering the RLC status report until x < RX_Highest_Status or x >= RX_Next + AM_Window_Size.

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

[0300] Detection of AMD PDU reception failure.

[0301] When the re-assembly timer expires, the receiving side of the AM RLC entity shall trigger an RLC status report.

[0302] Note 2: The expiration of the re-assembly timer will trigger an update of RX_Highest_Status and trigger an RLC status report, but the RLC status report shall be triggered after the update of RX_Highest_Status.

[0303] Move the lower limit of the receive window due to timer timeout;

[0304] The receiving side of the AM RLC entity shall trigger a status report when the t-Window expires.

[0305] It should be noted that in the above embodiments, the following content is newly added in Section 5.3.4 of 3GPP TS 38.322 in this disclosure, including:

[0306] Move the lower limit of the receive window due to timer timeout;

[0307] The receiving side of the AM RLC entity shall trigger a status report when the t-Window expires.

[0308] Correspondingly, the English description of the above standard is as follows:

[0309] 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).

[0310] Triggers to initiate STATUS reporting include:

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

[0312] -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:

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

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

[0315] -trigger a STATUS report.

[0316] -else:

[0317] -delay triggering the STATUS report until x<RX_Highest_Status or

[0318] x>=RX_Next+AM_Window_Size.

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

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

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

[0322] NOTE 2: The expiry of t-Reassembly triggers both RX_Highest_Status to be updated and a STATUS report to be triggered, but the STATUS report shall be triggered after RX_Highest_Status is updated.

[0323] -Movement of lower edge of the receiving window due to timer expiry

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

[0325] […omitted…]

[0326] It should be noted that the new content in the above English description is as follows, including:

[0327] -Movement of lower edge of the receiving window due to timer expiry

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

[0329] In some embodiments, the following description is included in the relevant communication protocol, for example, Section 7.3 of 3GPP TS 38.322:

[0330] TS 38.331[5] configures the following timers:

[0331] a)t-PollRetransmit

[0332] The transmitting side of the AM RLC entity uses this timer to resend polls (see clause 5.3.3).

[0333] b)t-Reassembly

[0334] This timer is used by the receiving side of the AM RLC entity and the receiving UM RLC entity to detect loss of lower layer RLC PDUs (see clauses 5.2.2.2 and 5.2.3.2). If the reassembly timer is running, the reassembly timer shall not be started additionally, i.e. the reassembly timer shall run only once per RLC entity at a given time.

[0335] c)t-StatusProhibit

[0336] The receiving side of the AM RLC entity uses this timer to prohibit the transmission of STATUS PDUs (see clause 5.3.4).

[0337] d)t-Window

[0338] This timer is used by the receiving side of the AM RLC entity to move the lower limit of the receiving window after the timer expires.

[0339] It should be noted that, in the above embodiment, the following content is newly added to Section 7.3 of 3GPP TS 38.322, including:

[0340] d)t-Window

[0341] This timer is used by the receiving side of the AM RLC entity to move the lower limit of the receiving window after the timer expires.

[0342] Correspondingly, the English description of the above standards is as follows:

[0343] The following timers are configured by TS 38.331[5]:

[0344] a)t-PollRetransmit

[0345] This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll (see clause 5.3.3).

[0346] b) t-Reassembly

[0347] 此定时器由AM RLC实体的接收方和接收UM RLC实体用于检测较低层的RLC PDU丢失情况(见5.2.2.2和5.2.3.2条款)。如果t-Reassembly正在运行,则不应额外启动t-Reassembly,即,在给定时间每个RLC实体仅运行一个t-Reassembly。

[0348] c) t-StatusProhibit

[0349] 此定时器由AM RLC实体的接收方用于禁止发送状态PDU(见5.3.4条款)。

[0350] d) t-Window

[0351] 此定时器由AM RLC实体的接收方用于移动接收窗口的下边缘。

[0352] It should be noted that the newly added content in the above English description is as follows, including:

[0353] d) t-Window

[0354] 此定时器由AM RLC实体的接收方用于移动接收窗口的下边缘。

[0355] In the above embodiment, the timer t-Window is an example of the first timer in the embodiment of the present disclosure. The first timer may also be called by other names in a specific implementation.

[0356] In combination with the content of the above embodiment, in some embodiments, after the first timer expires, moving the receiving window of the first RLC entity includes any one of the following:

[0357] Updating the lower limit of the receiving window to a sequence number of the first RLC SDU that is not completely received and is greater than RX_Next;

[0358] Updating the lower limit of the receive window to a sequence number of the first RLC SDU that is not completely received and is greater than or equal to RX_Next_Status_Trigger;

[0359] The lower limit of the receiving window is updated to RX_Highest_Status.

[0360] In the embodiment of the present disclosure, the RLC SDU that is not completely received includes: the sequence number of the RLC SDU that is not received; the partially received RLC SDU, which can be understood as the RLC SDU segmented transmission, but only part of the segment of the RLC SDU is received.

[0361] In some optional embodiments, the receiving window of the first RLC entity is moved, and then the method further includes: sending a third message to the PDCP entity corresponding to the first RLC entity; wherein the third message includes the lower limit of the receiving window after the move; and the third message is used to instruct the PDCP entity to use the lower limit of the receiving window after the move as the lower limit of the receiving window of the PDCP entity. It can be understood that after the reassembly timer or the first timer expires, the first RLC entity sends the lower limit of the receiving window after the move to the corresponding PDCP entity, so that the PDCP entity uses the lower limit of the receiving window after the move of the first RLC entity as the lower limit of its own receiving window.

[0362] Optionally, when the first RLC entity is located in the terminal device, the third message may be delivered through inter-layer communication between the first RLC entity and the PDCP entity.

[0363] Optionally, when the first RLC entity is located in the base station device and the base station device uses a centralized unit-distributed unit separation architecture, the third message can be transmitted through signaling between network entities, for example: it can be transmitted through F1 signaling between the centralized unit and the distributed unit.

[0364] Step S2103: Send an RLC status report to the second RLC entity.

[0365] In some embodiments, after the reassembly timer or the first timer expires, the first RLC entity may generate an RLC status report in addition to moving the receiving window of the first RLC entity.

[0366] In some optional embodiments, after receiving the RLC status report, the second RLC entity sends the RLC SDU indicated by NACK_SN and the RLC SDU segments indicated by NACK_range, SOstart and SOend to the first RLC entity.

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

[0368] FIG3 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3 , the embodiment of the present disclosure relates to a second RLC entity, and the method includes:

[0369] Step S3101: Send an RLC data packet to a first RLC entity.

[0370] For optional implementations of step S3101, reference may be made to the optional implementations of step 2101 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0371] In some embodiments, the second RLC entity sends an RLC data packet to the first RLC entity, where the RLC data packet includes the first information or the second information.

[0372] In some embodiments, the first information may include an RLC SDU and a sequence number of the RLC SDU. In some embodiments, the number of RLC SDUs in the first information is one.

[0373] In some embodiments, the second information may include an RLC SDU segment and a sequence number of the RLC SDU segment. In some embodiments, the number of RLC SDUs in the first information is 1.

[0374] Step S3102: Receive an RLC status report sent by the first RLC entity.

[0375] The optional implementation of step S3102 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0376] In some embodiments, an RLC status report sent by a first RLC entity is received.

[0377] In some embodiments, the RLC status report includes information of the incompletely received RLC SDU starting with a sequence number equal to RX_Next, including: the sequence number of the unreceived RLC SDU; the sequence number of the partially received RLC SDU and the unreceived segment information in the partially received RLC SDU.

[0378] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure relates to a first RLC entity, and the method includes:

[0379] Step S4101: Receive an RLC data packet sent by a second RLC entity.

[0380] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0381] In some embodiments, the RLC data packet includes the first information or the second information.

[0382] In some embodiments, the first information may include an RLC SDU and a sequence number of the RLC SDU. In some embodiments, the number of RLC SDUs in the first information is one.

[0383] In some embodiments, the second information may include an RLC SDU segment and a sequence number of the RLC SDU segment. In some embodiments, the number of RLC SDUs in the first information is 1.

[0384] Step S4102: Update the state variables of the first RLC entity.

[0385] The optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0386] In some embodiments, the first RLC entity updates its own state variable according to the sequence number of the received RLC SDU or the sequence number of the RLC SDU segment.

[0387] In some embodiments, the state variables of the first RLC entity include, but are not limited to: RX_Next, RX_Next_Highest, RX_Highest_Status, and RX_Next_Status_Trigger.

[0388] Step S4103: The preset timer meets the start condition, and the preset timer is started.

[0389] The optional implementation of step S4103 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0390] In some embodiments, the preset timer may be a reassembly timer or a first timer.

[0391] In some embodiments, the starting conditions of the reassembly timer may refer to the contents of the relevant sections of the 3GPP protocol.

[0392] In some embodiments, a starting condition of the first timer is that there is a gap in the received RLC SDU data packet.

[0393] Step S4104: When the preset timer times out, the receiving window of the first RLC entity is moved and an RLC status report is generated.

[0394] The optional implementation of step S4104 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0395] In some embodiments, after the reassembly timer expires, the first RLC entity may perform the following operations:

[0396] Updating the lower limit of the receiving window of the first RLC entity to a sequence number greater than RX_Next of the first RLC SDU that has not been completely received;

[0397] The lower limit of the receiving window of the first RLC entity is updated to a sequence number of the first incompletely received RLC SDU that is greater than or equal to RX_Next_Status_Trigger.

[0398] In some embodiments, after the first timer expires, the first RLC entity performs the following operations:

[0399] Updating the lower limit of the receiving window of the first RLC entity to a sequence number greater than RX_Next of the first RLC SDU that has not been completely received;

[0400] Update the lower limit of the receiving window of the first RLC entity to a sequence number of the first incompletely received RLC SDU that is greater than or equal to RX_Next_Status_Trigger;

[0401] The lower limit of the receiving window of the first RLC entity is updated to RX_Highest_Status.

[0402] In some embodiments, after the reassembly timer or the first timer expires, an RLC status report is further generated.

[0403] Step S4105: Send the lower limit of the moved receiving window to the PDCP entity.

[0404] The optional implementation of step S4105 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0405] In some embodiments, the first RLC entity sends a third message to the PDCP entity after moving the lower limit of the receiving window; wherein the third message includes the lower limit of the receiving window after moving, and the third message is used to instruct the PDCP entity to use the lower limit of the receiving window after moving as the lower limit of the receiving window of the PDCP entity.

[0406] It should be noted that step S4105 may be executed before step S4106, after step S4106, or simultaneously with step S4106. The embodiment of the present disclosure does not limit the order of step S4105 and step S4106.

[0407] Step S4106: Send an RLC status report to the second RLC entity.

[0408] The optional implementation of step S4106 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0409] In some embodiments, the second RLC entity sends an RLC status report to the first RLC entity.

[0410] In some embodiments, the RLC status report includes information of the incompletely received RLC SDU starting with a sequence number equal to RX_Next, including: the sequence number of the unreceived RLC SDU; the sequence number of the partially received RLC SDU and the unreceived segment information in the partially received RLC SDU.

[0411] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure involves a PDCP entity 103, and the method includes:

[0412] Step S5101: Receive the lower limit of the receiving window after the first RLC entity moves.

[0413] The optional implementation of step S5101 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0414] In some embodiments, a third message sent by a second RLC entity is received; wherein the third message includes the lower limit of the receiving window after moving, and the third message is used to instruct the PDCP entity to use the lower limit of the receiving window after moving as the lower limit of the receiving window of the PDCP entity.

[0415] Step S5102: Move the lower limit of the receiving window of the PDCP entity.

[0416] The optional implementation of step S5102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0417] In some embodiments, the PDCP entity uses the lower limit of the moved receiving window of the first RLC entity as the lower limit of its own receiving window.

[0418] FIG6 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG6 , the embodiment of the present disclosure relates to a communication method for a communication system 100, the method comprising:

[0419] Step S6101: The second RLC entity sends an RLC data packet to the first RLC entity.

[0420] The optional implementation of step S6101 can refer to the optional implementation of step S2101 in Figure 2A, step S3101 in Figure 3, step S4101 in Figure 4, and other related parts in the embodiments involved in Figures 2A, 3, and 4, which will not be repeated here.

[0421] In some embodiments, the second RLC entity sends an RLC data packet to the first RLC entity, where the RLC data packet includes the first information or the second information.

[0422] In some embodiments, the first information may include an RLC SDU and a sequence number of the RLC SDU. In some embodiments, the number of RLC SDUs in the first information is one.

[0423] In some embodiments, the second information may include an RLC SDU segment and a sequence number of the RLC SDU segment. In some embodiments, the number of RLC SDUs in the first information is 1.

[0424] Step S6102: The first RLC entity updates the state variables.

[0425] Optional implementations of step S6102 may refer to step S2102 in FIG. 2A , step S4102 in FIG. 4 , and other related parts in the embodiments involved in FIG. 2A and FIG. 4 , which will not be described in detail here.

[0426] In some embodiments, the first RLC entity updates its own state variable according to the sequence number of the received RLC SDU or the sequence number of the RLC SDU segment.

[0427] In some embodiments, the state variables of the first RLC entity include, but are not limited to: RX_Next, RX_Next_Highest, RX_Highest_Status, and RX_Next_Status_Trigger.

[0428] Step S6103: The preset timer meets the start condition, and the preset timer is started.

[0429] The optional implementation of step S6103 can refer to the optional implementation of step S2102 in Figure 2A, step S4103 in Figure 4, and other related parts in the embodiments involved in Figures 2A and 4, which will not be repeated here.

[0430] In some embodiments, the preset timer may be a reassembly timer or a first timer.

[0431] In some embodiments, the starting conditions of the reassembly timer may refer to the contents of the relevant sections of the 3GPP protocol.

[0432] In some embodiments, a starting condition of the first timer is that there is a gap in the received RLC SDU data packet.

[0433] Step S6104: When the preset timer times out, the receiving window of the first RLC entity is moved and an RLC status report is generated.

[0434] The optional implementation of step S6104 can refer to the optional implementation of step S2102 in Figure 2A, step S4104 in Figure 4, and other related parts in the embodiments involved in Figures 2A and 4, which will not be repeated here.

[0435] In some embodiments, after the reassembly timer expires, the first RLC entity performs the following operations:

[0436] Updating the lower limit of the receiving window of the first RLC entity to a sequence number greater than RX_Next of the first RLC SDU that has not been completely received;

[0437] The lower limit of the receiving window of the first RLC entity is updated to a sequence number of the first incompletely received RLC SDU that is greater than or equal to RX_Next_Status_Trigger.

[0438] In some embodiments, after the first timer expires, the first RLC entity performs the following operations:

[0439] Updating the lower limit of the receiving window of the first RLC entity to a sequence number greater than RX_Next of the first RLC SDU that has not been completely received;

[0440] Update the lower limit of the receiving window of the first RLC entity to a sequence number of the first incompletely received RLC SDU that is greater than or equal to RX_Next_Status_Trigger;

[0441] The lower limit of the receiving window of the first RLC entity is updated to RX_Highest_Status.

[0442] In some embodiments, after the reassembly timer or the first timer expires, an RLC status report is further generated.

[0443] Step S6105: The first RLC entity sends the lower limit of the moved receiving window to the PDCP entity.

[0444] The optional implementation of step S6105 can refer to the optional implementation of step S2102 in Figure 2A, step S5101 in Figure 5, and other related parts in the embodiments involved in Figures 2A and 5, which will not be repeated here.

[0445] In some embodiments, the first RLC entity sends a third message to the PDCP entity after moving the lower limit of the receiving window; wherein the third message includes the lower limit of the receiving window after moving, and the third message is used to instruct the PDCP entity to use the lower limit of the receiving window after moving as the lower limit of the receiving window of the PDCP entity.

[0446] Step S6106: Move the lower limit of the receiving window of the PDCP entity.

[0447] The optional implementation of step S6106 can refer to the optional implementation of step S2102 in Figure 2A, step S4105 in Figure 4, step S5102 in Figure 5, and other related parts in the embodiments involved in Figures 2A, 4, and 5, which will not be repeated here.

[0448] In some embodiments, the PDCP entity uses the lower limit of the moved receiving window of the first RLC entity as the lower limit of its own receiving window.

[0449] Step S6107: The first RLC entity sends an RLC status report to the second RLC entity.

[0450] The optional implementation of step S6107 can refer to the optional implementation of step S2103 in Figure 2A, step S3102 in Figure 3, step S4106 in Figure 4, and other related parts in the embodiments involved in Figures 2A, 3, and 4, which will not be repeated here.

[0451] In some embodiments, the second RLC entity sends an RLC status report to the first RLC entity.

[0452] In some embodiments, the RLC status report includes information of the incompletely received RLC SDU starting with a sequence number equal to RX_Next, including: the sequence number of the unreceived RLC SDU; the sequence number of the partially received RLC SDU and the unreceived segment information in the partially received RLC SDU.

[0453] The present disclosure also provides 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 the first RLC entity in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by the PDCP entity in any of the above methods.

[0454] 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.

[0455] In the embodiments of the present disclosure, a 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 relationships of hardware circuits. The logical relationships of the above-mentioned hardware circuits are 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 file to implement 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 ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0456] FIG7A is a schematic diagram of the structure of a first RLC entity proposed in an embodiment of the present disclosure. As shown in FIG7A , the first RLC entity may include: a processing module 7101 and a sending module 7102 .

[0457] In some embodiments, the processing module is configured to determine that a preset timer has expired, move a receiving window of the first RLC entity, and generate an RLC status report.

[0458] In some embodiments, the sending module is configured to send the RLC status report to the second RLC entity.

[0459] Optionally, the above-mentioned receiving module is used to execute the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, such as step S3101, which will not be repeated here.

[0460] FIG7B is a schematic diagram of the structure of a PDCP entity proposed in an embodiment of the present disclosure. As shown in FIG7B , the PDCP entity may include: a receiving module 7201 and a processing module 7202 .

[0461] In some embodiments, the receiving module is used to receive a third message sent by the first RLC entity, wherein the third message includes the lower limit of the receiving window of the first RLC entity after movement, and the lower limit of the receiving window after movement is related to a preset timer of the first RLC entity.

[0462] In some embodiments, the processing module is configured to use the moved lower limit as the lower limit of the receiving window of the PDCP entity;

[0463] The preset timer is a reassembly timer or a first timer. After the reassembly timer or the first timer times out, the lower limit of the receiving window of the first RLC entity is moved.

[0464] Optionally, the above-mentioned receiving module is used to execute the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, such as step S4101, which will not be repeated here.

[0465] 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 device (e.g., an access network device, a core network device, etc.), or an IoT device, or a chip, chip system, or processor that supports the device 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.

[0466] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0467] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step S2102, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0468] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Alternatively, all or part of the memories 8103 may be located outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memories 8103 and may be configured to receive data from the memories 8103 or other devices, or to send data to the memories 8103 or other devices. For example, the interface circuits 8104 may read data stored in the memories 8103 and send the data to the processor 8101.

[0469] The communication device 8100 described in the above embodiments may be a 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 device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0470] 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.

[0471] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

[0472] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Alternatively, all or part of memory 8203 may be located external to chip 8200. Optionally, interface circuit 8202 is connected to memory 8203 and may be used to receive data from memory 8203 or other devices, or may be used to send data to memory 8203 or other devices. For example, interface circuit 8202 may read data stored in memory 8203 and send the data to processor 8201.

[0473] In some embodiments, the interface circuit 8202 performs at least one of the communication steps (e.g., step S2101, but not limited thereto) in the above method, such as sending and / or receiving. The interface circuit 8202 performing the communication steps (e.g., sending and / or receiving) in the above method, for example, means that the interface circuit 8202 performs data exchange between the processor 8201, chip 8200, memory 8203, or a transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps (e.g., step S2102, but not limited thereto).

[0474] 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.

[0475] 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.

[0476] 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 communication method, characterized in that: The method is performed by a first RLC entity, comprising: determining that a preset timer has expired, moving a receiving window of the first RLC entity, and generating an RLC status report; The RLC status report is sent to the second RLC entity.

2. The method according to claim 1, characterized in that The first RLC entity is located in a terminal device, and the second RLC entity is located in a base station device; The duration of the preset timer is determined by the following methods, including: receiving a first message sent by the base station device, where the first message includes a first value, and the first value is used to indicate the duration of the preset timer; Using the first value as the duration of the preset timer; The first value is determined by the base station device according to the duration of the reordering timer t-Reordering.

3. The method according to claim 1 or 2, characterized in that The step of determining that a preset timer has timed out also includes: receiving an RLC data packet sent by a second RLC entity; updating a state variable according to the RLC data packet; According to the updated state variable, it is determined that the condition for starting the preset timer is met, and the preset timer is started.

4. The method according to claim 3, characterized in that The RLC data packet includes first information or second information, the first information includes a sequence number of a radio link control service data unit RLC SDU, and the second information includes a sequence number of an RLC SDU segment; The state variables include a receiving state variable RX_Next or a highest receiving state variable RX_Next_Highest; The updating of the state variable according to the RLC data packet comprises: Update RX_Next or RX_Next_Highest according to the sequence number of the RLC SDU or the sequence number of the RLC SDU segment.

5. The method according to claim 4, characterized in that The preset timer is a first timer; A starting condition of the first timer is that there is a gap in the received RLC data packet.

6. The method according to claim 5, characterized in that The first information includes an RLC SDU, and the second information includes an RLC SDU segment; The existence of gaps in the received RLC data packets is determined by any one of the following methods: The difference between the RX_Next_Highest and the RX_Next is greater than a first preset threshold; The difference between the RX_Next_Highest and the RX_Next is greater than a second preset threshold, and there is at least one lost RLC SDU segment before the last RLC SDU segment of the received RLC SDU, wherein the sequence number of the RLC SDU is equal to RX_Next.

7. The method according to any one of claims 5-6, characterized in that The state variables also include: RX_Highest_Status and RX_Next_Status_Trigger; The moving the receiving window of the first RLC entity includes any one of the following: Updating the lower limit of the receiving window to a sequence number of the first RLC SDU that is not completely received and is greater than RX_Next; Updating the lower limit of the receive window to a sequence number of the first RLC SDU that is not completely received and is greater than or equal to RX_Next_Status_Trigger; The lower limit of the receiving window is updated to RX_Highest_Status.

8. The method according to any one of claims 1 to 4, characterized in that The preset timer is a reassembly timer.

9. The method according to claim 8, characterized in that The first RLC entity is located in the terminal equipment; The step of determining that a preset timer has timed out also includes: A second message sent by a base station device is received, where the second message is used to instruct to move the receiving window of the first RLC entity after the reassembly timer times out.

10. The method according to claim 8 or 9, characterized in that The state variable also includes a next receive state variable trigger RX_Next_Status_Trigger; The moving the receiving window of the first RLC entity includes any one of the following: Updating the lower limit of the receiving window to a sequence number of the first RLC SDU that is not completely received and is greater than RX_Next; Update the lower limit of the receive window to the first unreceived value that is greater than or equal to RX_Next_Status_Trigger. Sequence number of the RLC SDU.

11. The method according to any one of claims 1 to 10, characterized in that: The step of moving the receiving window of the first RLC entity further comprises: Sending a third message to a Packet Data Convergence Protocol (PDCP) entity; The third message includes the lower limit of the receiving window after it moves; the third message is used to instruct the PDCP entity to use the lower limit of the receiving window after it moves as the lower limit of the receiving window of the PDCP entity.

12. A communication method, characterized in that: The method is performed by a PDCP entity and includes: receiving a third message sent by a first RLC entity, where the third message includes a lower limit of a receiving window of the first RLC entity after the move, where the lower limit of the receiving window after the move is related to a preset timer of the first RLC entity; Using the moved lower limit as the lower limit of the receiving window of the PDCP entity; The preset timer is a reassembly timer or a first timer. After the reassembly timer or the first timer times out, the lower limit of the receiving window of the first RLC entity is moved.

13. The method according to claim 12, characterized in that The preset timer is a reassembly timer; The lower limit of the receiving window of the first RLC entity after moving is any one of the following: A sequence number greater than the first incompletely received RLC SDU of RX_Next of the first RLC entity; The sequence number of the first incompletely received RLC SDU that is greater than or equal to the RX_Next_Status_Trigger of the first RLC entity.

14. The method according to claim 12, characterized in that The preset timer is a first timer; The lower limit of the receiving window of the first RLC entity after moving is any one of the following: A sequence number greater than the first incompletely received RLC SDU of RX_Next of the first RLC entity; a sequence number of the first incompletely received RLC SDU that is greater than or equal to the RX_Next_Status_Trigger of the first RLC entity; RX_Highest_Status of the first RLC entity.

15. A first RLC entity, characterized in that: include: a processing module, configured to determine that a preset timer has expired, move a receiving window of the first RLC entity, and generate an RLC status report; A sending module is used to send the RLC status report to the second RLC entity.

16. A PDCP entity, characterized in that: include: a receiving module, configured to receive a third message sent by a first RLC entity, where the third message includes a lower limit of a receiving window of the first RLC entity after movement, where the lower limit of the receiving window after movement is related to a preset timer of the first RLC entity; a processing module, configured to use the moved lower limit as the lower limit of the receiving window of the PDCP entity; The preset timer is a reassembly timer or a first timer. After the reassembly timer or the first timer times out, the lower limit of the receiving window of the first RLC entity is moved.

17. A first RLC entity, characterized in that: include: one or more processors; The processor is configured to execute the communication method according to any one of claims 1 to 11.

18. A PDCP entity, characterized in that: include: one or more processors; The processor is configured to execute the communication method according to any one of claims 12 to 14.

19. A communication system, characterized in that: include: A first RLC entity, configured to implement the communication method according to any one of claims 1 to 11; A PDCP entity, configured to implement the communication method according to any one of claims 12 to 14.

20. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1 to 11 and 12 to 14.

Images