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: receiving a difference value between receiving state variables RX_DELIV before and after an update that are sent by a PDCP entity; and on the basis of the difference value, updating a receiving state variable RX_Next, wherein the receiving state variable RX_Next is used for indicating the lower edge of a receiving window of a first RLC entity. In the embodiments of the present disclosure, a PDCP entity sends to a first RLC entity a difference value in respect of changes in RX_DELIV, such that the first RLC entity updates RX_Next on the basis of the difference value and triggers an RLC status report, thereby making a second RLC entity no longer retransmitting data packets to be discarded by the PDCP entity, and thus avoiding the waste 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 related technologies, 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 lossless mode, resulting in a waste of radio resources.

[0003] Furthermore, in 5G NR systems, because the PDCP Control PDU lacks a PDCP COUNT, while the corresponding RLC SDU at the RLC layer does have an RLC SN, the PDCP COUNT and RLC SN do not correspond one-to-one. Consequently, the method by which the PDCP entity notifies the RLC entity based on the PDCP COUNT to adjust the receive window and notify the peer RLC entity of the corresponding adjustment has some drawbacks. Therefore, further research is needed to address the issue of the AM RLC entity retransmitting packets that the PDCP entity would otherwise discard.

[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] Receive the difference between the receive state variable RX_DELIV before and after the update sent by the packet data convergence protocol PDCP entity;

[0008] A receiving state variable RX_Next is updated according to the difference, where the receiving state variable RX_Next is used to indicate a lower edge of a receiving window of the first 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] The difference between the receive state variable RX_DELIV before and after the update is sent to the first RLC entity, so that the first RLC entity updates the receive state variable RX_Next according to the difference, and the receive state variable RX_Next is used to indicate the lower edge of the receive window of the first RLC entity.

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

[0012] A receiving module, configured to receive a difference between a receive state variable RX_DELIV before and after an update, sent by a packet data convergence protocol PDCP entity;

[0013] A processing module is configured to update a receiving state variable RX_Next according to the difference, where the receiving state variable RX_Next is used to indicate a lower edge of a receiving window of the first RLC entity.

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

[0015] The sending module is used to send the difference between the receiving state variable RX_DELIV before and after the update to the first RLC entity, so that the first RLC entity updates the receiving state variable RX_Next according to the difference, and the receiving state variable RX_Next is used to indicate the lower edge of the receiving window of the first RLC entity.

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

[0017] one or more processors;

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

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

[0020] one or more processors;

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

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

[0023] 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

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

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

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

[0027] FIG2B is an exemplary schematic diagram showing that a first RLC entity updates a receive state variable RX_Next according to an embodiment of the present disclosure;

[0028] FIG2C is an exemplary schematic diagram showing that a first RLC entity updates a receive state variable RX_Next according to an embodiment of the present disclosure;

[0029] FIG2D is an exemplary schematic diagram showing that a first RLC entity updates a receive state variable RX_Next according to an embodiment of the present disclosure;

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

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

[0032] FIG5 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

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

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

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

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

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

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

[0039] Receive the difference between the receive state variable RX_DELIV before and after the update sent by the packet data convergence protocol PDCP entity;

[0040] A receiving state variable RX_Next is updated according to the difference, where the receiving state variable RX_Next is used to indicate a lower edge of a receiving window of the first RLC entity.

[0041] In the above embodiment, the first RLC entity receives the difference between the receive state variable RX_DELIV before and after the update, and updates RX_Next according to the difference, thereby solving the problem in the related art that the PDCP COUNT and the RLC SN are not one-to-one corresponding. In this way, the RLC status report generated according to RX_Next does not include the sequence number of the PDCP PDU that the PDCP entity is about to discard, thereby avoiding the second RLC entity from retransmitting the data packet that the PDCP entity is about to discard according to the RLC status report, thereby saving wireless resources.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, updating the receiving state variable RX_Next according to the difference further includes:

[0043] Determine the sum of the difference between the current value of RX_Next and the change of RX_DELIV as the first value; or,

[0044] Determine the number of first PDCP Control PDUs received by the first RLC entity and use the number as a second value; determine the sum of the first value and the second value as a third value;

[0045] The RLC sequence number corresponding to the first PDCP Control PDU is greater than the current value of RX_Next and not greater than the first value.

[0046] In the above embodiment, a method for determining the first value, the second value, and the third value is provided, so that the first RLC entity updates the value of RX_Next according to one of the first value, the second value, and the third value.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, updating the receive state variable RX_Next according to the difference includes:

[0048] Determining a first radio link control service data unit RLC SDU, where the first RLC SDU is a first incompletely received RLC SDU whose sequence number is not less than the first value;

[0049] Update the RX_Next to the sequence number of the first RLC SDU.

[0050] In the above embodiment, a method is provided in which the first RLC entity determines the first RLC SDU according to the first value and updates RX_Next according to the sequence number of the first RLC SDU.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, updating the receive state variable RX_Next according to the difference includes:

[0052] Determining a second RLC SDU, where the second RLC SDU is a first RLC SDU that is not completely received and has a sequence number that is not less than the third value;

[0053] Update the RX_Next to the sequence number of the second RLC SDU.

[0054] In the above embodiment, a method is provided in which the first RLC entity determines the second RLC SDU according to the first value and updates RX_Next according to the sequence number of the second RLC SDU.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, updating the receive state variable RX_Next according to the difference includes:

[0056] Determine a number of second PDCP Control PDUs received by the first RLC entity and use the number as a fourth value, where an RLC sequence number corresponding to the second PDCP Control PDU is greater than the first value and not greater than the third value;

[0057] determining a sum of the first value, the second value, and the fourth value as a fifth value;

[0058] Determining a third RLC SDU, where the third RLC SDU is a first RLC SDU that is not completely received and has a sequence number that is not less than the fifth value;

[0059] Update the RX_Next to the sequence number of the third RLC SDU.

[0060] In the above embodiment, a method is provided in which the first RLC entity determines the third RLC SDU according to the first value and updates RX_Next according to the sequence number of the third RLC SDU.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the first RLC entity and the PDCP entity are located in a terminal;

[0062] The difference in the change of the receiving state variable RX_DELIV sent by the receiving Packet Data Convergence Protocol PDCP entity also includes:

[0063] receiving first information configured by a network device, where the first information is used to instruct the first RLC entity to enable a first function and the PDCP entity to enable a second function;

[0064] The first function is to receive a difference between a reception state variable RX_DELIV sent by the PDCP entity before and after the update, and to update a reception state variable RX_Next according to the difference;

[0065] The second function is to send the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0066] In the above embodiment, a method is provided in which a network device instructs a first RLC entity to enable a first function and a PDCP entity to enable a second function by configuring first information.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the network device indicates the first information by any one of the following:

[0068] Radio Resource Control (RRC) signaling;

[0069] third PDCP Control PDU;

[0070] Fields in the PDCP PDU header;

[0071] RLC Control PDU;

[0072] fields in the RLC PDU header; or,

[0073] Media Access Control Element MAC CE.

[0074] In the above embodiment, a way for the network device to indicate the first information is provided.

[0075] In conjunction with some embodiments of the first aspect, in some embodiments, the radio resource control RRC signaling is any one of the following:

[0076] Radio Link Control Bearer Signaling RLCBearerConfig;

[0077] Radio link control configuration signaling RLC-Config;

[0078] Packet Data Convergence Protocol Configuration Signaling PDCP-Config;

[0079] Cell group configuration signaling CellGroupConfig.

[0080] In the above embodiments, several situations of radio resource control RRC signaling are provided.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments, updating the receiving state variable RX_Next according to the difference further includes:

[0082] Moving the receiving window of the first RLC entity according to the updated RX_Next and generating an RLC status report;

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

[0084] In the above embodiment, after receiving the RLC status report, the second RLC entity no longer retransmits the data packet that is about to be discarded by the PDCP entity, thereby avoiding waste of radio resources.

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

[0086] The difference between the receive state variable RX_DELIV before and after the update is sent to the first RLC entity, so that the first RLC entity updates the receive state variable RX_Next according to the difference, and the receive state variable RX_Next is used to indicate the lower edge of the receive window of the first RLC entity.

[0087] In the above embodiment, the PDCP entity sends the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity, so that the first RLC entity updates RX_Next according to the difference and generates an RLC status report. The second RLC entity receives the RLC status report, which solves the problem in the related art that the PDCP COUNT and RLC SN are not one-to-one corresponding, so that the second RLC entity no longer retransmits the data packet that the PDCP entity will discard, avoiding the waste of wireless resources.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the sending the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity further includes:

[0089] The reordering timer t-Reordering times out, triggering the PDCP entity to update the receiving state variable RX_DELIV.

[0090] In the above embodiment, a method for triggering the PDCP entity to update the reception state variable RX_DELIV is provided.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the PDCP entity is located in a network device, and the network device adopts a centralized unit and a distributed unit separation architecture;

[0092] The sending the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity includes:

[0093] The centralized unit sends a new radio interface user plane protocol NR User Plane Protocol signaling to the distributed unit, where the new radio interface user plane protocol signaling is used to indicate a difference between the receive state variable RX_DELIV before and after the update and an identifier of the corresponding first RLC entity;

[0094] The new air interface user plane protocol is associated with a data radio bearer DRB, and when the new air interface user plane protocol is used to indicate the difference before and after RX_DELIV update, the user plane protocol signaling is the new air interface user plane protocol instance corresponding to the first RLC entity.

[0095] In the above embodiment, a method is provided in which the centralized unit of the network device sends the difference between the reception state variable RX_DELIV before and after the update to the distributed unit when the PDCP entity is located in the network device and the network device adopts a centralized unit and distributed unit separation architecture.

[0096] In conjunction with some embodiments of the second aspect, in some embodiments, the first RLC entity and the PDCP entity are located in a terminal;

[0097] The step of sending the updated difference value of the receive state variable RX_DELIV to the first RLC entity further includes:

[0098] receiving first information configured by a network device, where the first information is used to instruct the first RLC entity to enable a first function and the PDCP entity to enable a second function;

[0099] The first function is to receive a difference between a reception state variable RX_DELIV sent by the PDCP entity before and after the update, and to update a reception state variable RX_Next according to the difference;

[0100] The second function is to send the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0101] In the above embodiment, a method is provided in which a network device configures first information so that a first RLC entity enables a first function and a PDCP entity enables a second function.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the network device indicates the first information by any one of the following:

[0103] Radio Resource Control (RRC) signaling;

[0104] third PDCP Control PDU;

[0105] Fields in the PDCP PDU header;

[0106] RLC Control PDU;

[0107] fields in the RLC PDU header; or,

[0108] Media Access Control Element MAC CE.

[0109] In the above embodiment, a method is provided for the network device to send the first information to the terminal.

[0110] In conjunction with some embodiments of the second aspect, in some embodiments, the radio resource control RRC signaling is any one of the following:

[0111] Radio Link Control Bearer Signaling RLCBearerConfig;

[0112] Radio link control configuration signaling RLC-Config;

[0113] Packet Data Convergence Protocol Configuration Signaling PDCP-Config;

[0114] Cell group configuration signaling CellGroupConfig.

[0115] In the above embodiments, several situations of radio resource control RRC signaling are provided.

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

[0117] A receiving module, configured to receive a difference between a receive state variable RX_DELIV before and after an update, sent by a packet data convergence protocol PDCP entity;

[0118] A processing module is configured to update a receiving state variable RX_Next according to the difference, where the receiving state variable RX_Next is used to indicate a lower edge of a receiving window of the first RLC entity.

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

[0120] The sending module is used to send the difference between the receiving state variable RX_DELIV before and after the update to the first RLC entity, so that the first RLC entity updates the receiving state variable RX_Next according to the difference, and the receiving state variable RX_Next is used to indicate the lower edge of the receiving window of the first RLC entity.

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

[0122] one or more processors;

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

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

[0125] one or more processors;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0162] 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 entity 101 and a PDCP entity 102 .

[0163] 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 part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

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

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

[0166] 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 for automatic repeat request (ARQ).

[0167] In some embodiments, an RLC status report can be triggered by: 1) polling by the peer AM RLC entity; or 2) detection of an AM PDU reception failure. 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 based on the RLC status report.

[0168] In some embodiments, the AM RLC entity maintains a window at each of the transmitting side and the receiving side. The transmitting 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 down to the lower layer an AMD PDU whose sequence number is outside the transmitting window. 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 fully received, the AM RLC entity updates TX_Next_Ack.

[0169] 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 an AMD PDU that is 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 fully received, the AM RLC entity updates RX_Next.

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

[0171] In some embodiments, the information about 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.

[0172] 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. After 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.

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

[0174] In some embodiments, a radio bearer (RB) has a corresponding PDCP entity. A PDCP entity consists of a transmitting PDCP entity and a receiving PDCP entity. The PDCP entity's state variable RX_DELIV indicates the COUNT value of the first PDCP SDU that has not yet been submitted to the upper layer but is waiting to be submitted. When the COUNT value of a received PDCP PDU is less than RX_DELIV, it will be discarded. The PDCP entity maintains a reordering timer (t-Reordering) to detect the loss of PDCP Data PDUs. The PDCP entity's state variable RX_REORD indicates the COUNT value after the COUNT value of the PDCP Data PDU that triggered t-Reordering (i.e., COUNT+1). When the reordering timer t-Reordering times out, the PDCP entity updates RX_DELIV to the first COUNT value that has not been submitted upward that is greater than or equal to RX_REORD.

[0175] In some embodiments, the gNB-CU-User Plane (gNB-CU-UP) is a logical node that carries the user plane functions for the PDCP and SDAP protocols in the gNB-CU. The gNB-CU-UP terminates the E1 interface with the gNB-CU-Control Plane (gNB-CU-CP) and the F1 User Plane (F1-U) interface with the gNB-DU.

[0176] 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, the retransmission of data packets that the PDCP entity would otherwise discard by the peer RLC entity results in a waste of radio resources.

[0177] In some embodiments, when the reordering timer t-Reordering times out, the PDCP entity notifies the RLC entity of the status of the receive window update, so that the RLC entity adjusts the receive window accordingly and notifies the RLC entity at the other end. In this embodiment, it is assumed that the COUNT of the PDCP PDU and the sequence number of the RLC PDU are one-to-one corresponding. Since the COUNT of the PDCP PDU is 32 bits and the sequence number of the RLC PDU is 12 or 18 bits, the one-to-one correspondence between the COUNT of the PDCP PDU and the sequence number of the RLC PDU means that the difference between the sequence numbers of the two RLC PDUs is equal to the difference between the COUNTs of the PDCP PDUs corresponding to the two RLC PDUs. However, in the 5G NR system, since the PDCP Control PDU does not have a PDCP COUNT, but the RLC PDU corresponding to the PDCP Control PDU has a corresponding sequence number, the COUNT of the PDCP PDU and the sequence number of the RLC PDU are not one-to-one corresponding. Furthermore, dual connectivity can use split bearers, meaning that PDCP PDUs within a PDCP entity are transmitted by different RLC entities. This can also result in a non-one-to-one correspondence between the PDCP PDU COUNT and the RLC SDU sequence number. Therefore, further research is needed to address the issue of wasting radio resources by retransmitting packets that would otherwise be discarded by the PDCP entity.

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

[0179] In step S2101, the PDCP entity sends the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

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

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

[0182] In some embodiments, the receiving side and the transmitting side of the RLC entity exist simultaneously in one base station device or terminal.

[0183] 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; conversely, when the first RLC entity is located in the terminal, 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.

[0184] 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 also has a corresponding PDCP entity.

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

[0186] In some optional embodiments, the network device may configure whether to adjust the AM RLC receive window based on the relationship between the COUNT of the PDCP PDU and the SN of the corresponding RLC PDU. This configuration may be configured for each PDCP entity, each AM RLC entity, each MAC entity, or each terminal.

[0187] When configured separately for each PDCP entity, it can be configured through RRC signaling (for example, in IE PDCP-Config), by defining a new PDCP Control PDU, or by indicating it using a field in the header of the PDCP PDU, or by using MAC CE (configured for one or more RBs).

[0188] When configured separately for each AM RLC entity, it can be configured through RRC signaling (for example, in IE RLCBearerConfig or RLC-Config), by defining a new RLC Control PDU, or by indicating it using a field in the header of the RLC PDU, or by using MAC CE (to configure for one or more AM RLC entities).

[0189] When each MAC entity is configured separately, it can be configured through RRC signaling (for example, in IE CellGroupConfig) or using MAC CE. When each MAC entity is configured separately, the AM RLC entity and the PDCP entity associated with the MAC entity are configured accordingly.

[0190] When configuring for each terminal, the configuration may be performed through RRC signaling, and all AM RLC entities of the terminal and the PDCP entities associated therewith adopt the configuration.

[0191] In some embodiments, the first RLC entity and the PDCP entity are located in the terminal; the network device sends first information to the terminal, and the first information is used to instruct the first RLC entity to enable the first function and the PDCP entity to enable the second function.

[0192] In some embodiments, the first function is that the first RLC entity receives the difference between the PDCP state variable RX_DELIV before and after the update sent by the PDCP entity, and updates the reception state variable RX_Next according to the difference.

[0193] In some embodiments, the second function is that the PDCP entity sends the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0194] In the above embodiment, when the first RLC entity and the PDCP entity are located in the terminal, the first RLC entity and the PDCP entity themselves have corresponding functions, but the corresponding functions are not turned on; the network device configures the first RLC entity and the PDCP entity by sending the first information to the terminal, and then the terminal turns on the corresponding functions of the first RLC entity and the PDCP entity.

[0195] Optionally, in the embodiment of the present disclosure, the network device indicates the first information by any one of the following:

[0196] Radio Resource Control (RRC) signaling;

[0197] third PDCP Control PDU;

[0198] Fields in the PDCP PDU header;

[0199] RLC Control PDU;

[0200] fields in the RLC PDU header; or,

[0201] Media Access Control Element MAC CE.

[0202] In some optional embodiments, the radio resource control (RRC) signaling includes any one of the following:

[0203] Radio Link Control Bearer Signaling RLCBearerConfig;

[0204] Radio link control configuration signaling RLC-Config;

[0205] Packet Data Convergence Protocol Configuration Signaling PDCP-Config;

[0206] Cell group configuration signaling CellGroupConfig.

[0207] It should be noted that, in the embodiment of the present disclosure, the network device sends first information to the terminal for configuring the first RLC entity and the PDCP entity to enable corresponding functions. The first RLC entity may enable the corresponding function first, and the PDCP entity may enable the corresponding function later. Alternatively, the PDCP entity may enable the corresponding function first, and the first RLC entity may enable the corresponding function later. Alternatively, the first RLC entity and the PDCP entity may enable the corresponding function simultaneously. The embodiment of the present disclosure does not limit the order in which the first RLC entity and the PDCP entity enable the corresponding functions.

[0208] In the above embodiment, the first RLC entity and the PDCP entity are located in the terminal, and after the first RLC entity and the PDCP entity enable corresponding functions, the terminal sends RRC signaling to the network device, and the RRC signaling is used to indicate that the first RLC entity and the PDCP entity on the terminal have enabled corresponding functions.

[0209] Optionally, the RRC signaling sent by the terminal to the network device includes but is not limited to: terminal capability information UECapabilityInformation.

[0210] In some embodiments, the first RLC entity and the PDCP entity are located in a network device, and the network device adopts a centralized unit and a distributed unit separation architecture, and the PDCP entity sends the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0211] In some embodiments, the PDCP entity sends a difference between a receive state variable RX_DELIV before and after the update to the first RLC entity, including: a centralized unit sends a new radio interface user plane protocol NR User Plane Protocol signaling to a distributed unit, wherein the new radio interface user plane protocol signaling is used to indicate the difference between the receive state variable RX_DELIV before and after the update and an identifier of the corresponding first RLC entity;

[0212] In the above embodiment, the new air interface user plane protocol is associated with a data radio bearer DRB. When the new air interface user plane protocol is used to indicate the difference before and after the RX_DELIV update, the user plane protocol signaling is the new air interface user plane protocol instance corresponding to the first RLC entity. It can be understood that the identifier of the first RLC entity has been implicitly indicated.

[0213] In some embodiments, due to the expiration of the reordering timer t-Reordering, the PDCP entity is triggered to update the value of the reception state variable RX_DELIV.

[0214] In some embodiments, the PDCP entity sends the difference between the reception state variable RX_DELIV before and after the update to the first RLC entity.

[0215] Step S2102: The first RLC entity updates the receiving state variable RX_Next according to the difference between the values ​​before and after the update of RX_DELIV.

[0216] In some embodiments, the first RLC entity adds the current value of RX_Next and the difference between the changes in RX_DELIV to obtain the first value.

[0217] In some embodiments, the first RLC entity determines a first incompletely received RLC SDU with a sequence number not less than a first value as the first RLC SDU, and updates RX_Next to the sequence number of the first RLC SDU.

[0218] Figure 2B is an exemplary schematic diagram of the first RLC entity updating the receiving state variable RX_Next according to an embodiment of the present disclosure. As shown in the figure, the numbers in the gray rectangles represent the COUNT of PDCP SDUs received by the PDCP entity or the serial number of the RLC SDUs received by the first RLC entity, the letter "C" represents the PDCP Control PDU, and the numbers in the white rectangles represent the COUNT of PDCP SDUs not received by the PDCP entity or the serial number of the RLC SDUs not received by the first RLC entity.

[0219] As shown in Figure 2B , the PDCP entity's receive state variable RX_DELIV has a value of RX_DELIV1 = 1 before adjustment and a value of RX_DELIV2 = 6 after adjustment. The current value of the first RLC entity's receive state variable RX_Next is 2, thus determining the first value. The formula for calculating the first value is: RX_Next + RX_DELIV2 - RX_DELIV1. Substituting the values ​​of the various parameters into the formula, we see that the first value is 7. As shown in Figure 2B , the sequence number of the first RLC SDU, whose sequence number is not less than 7 and has not been completely received, is 7. That is, the sequence number of the first RLC SDU is 7, and RX_Next is updated to 7.

[0220] In some embodiments, after determining the first value, the first RLC entity determines the number of first PDCP Control PDUs received by the first RLC entity and uses the number as the second value.

[0221] In some embodiments, the RLC sequence number corresponding to the first PDCP Control PDU is greater than the current value of RX_Next and not greater than the first value.

[0222] In some embodiments, the first RLC entity determines the second RLC SDU and updates RX_Next to the sequence number of the second RLC SDU.

[0223] In some embodiments, the second RLC SDU is a first incompletely received RLC SDU having a sequence number not less than a third value;

[0224] Figure 2C is an exemplary schematic diagram of the first RLC entity updating the receiving state variable RX_Next according to an embodiment of the present disclosure. As shown in the figure, the numbers in the gray rectangles represent the COUNT of PDCP SDUs received by the PDCP entity or the serial number of the RLC SDUs received by the first RLC entity, the letter "C" represents the PDCP Control PDU, and the numbers in the white rectangles represent the COUNT of PDCP SDUs not received by the PDCP entity or the serial number of the RLC SDUs not received by the first RLC entity.

[0225] As shown in Figure 2C , the PDCP entity's receive state variable RX_DELIV has a value of RX_DELIV1 = 1 before adjustment and a value of RX_DELIV2 = 6 after adjustment. The current value of the first RLC entity's receive state variable RX_Next is 2, and the first value can be determined. The first value is calculated using the formula: RX_Next + RX_DELIV2 - RX_DELIV1. Substituting the values ​​of the various parameters into the formula, the first value is 7.

[0226] As shown in Figure 2C , the number of PDCP Control PDUs received by the first RLC entity between the current value of RX_Next and the first value is 1, that is, the second value is equal to 1, and the third value is equal to the sum of the first value and the second value, that is, 8. From Figure 2C , it can be determined that the sequence number of the first incompletely received RLC SDU with a sequence number not less than 8 is 10, that is, the sequence number of the second RLC SDU is 10, and RX_Next is updated to 10.

[0227] In some embodiments, the number of second PDCP Control PDUs received by the first RLC entity is determined and used as the fourth value; wherein the RLC sequence number corresponding to the second PDCP Control PDU is greater than the first value and not greater than the third value.

[0228] In some embodiments, determining a sum of the first value, the second value, and the fourth value as the fifth value;

[0229] In some embodiments, a third RLC SDU is determined, the third RLC SDU being the first incompletely received RLC SDU with a sequence number not less than a fifth value, and RX_Next is updated to the sequence number of the third RLC SDU.

[0230] Figure 2D is an exemplary schematic diagram of the first RLC entity updating the receiving state variable RX_Next according to an embodiment of the present disclosure. As shown in the figure, the numbers in the gray rectangles represent the COUNT of PDCP SDUs received by the PDCP entity or the serial number of the RLC SDUs received by the first RLC entity, the letter "C" represents the PDCP Control PDU, and the numbers in the white rectangles represent the COUNT of PDCP SDUs not received by the PDCP entity or the serial number of the RLC SDUs not received by the first RLC entity.

[0231] In Figure 2D , the PDCP entity's receive state variable RX_DELIV has a value of RX_DELIV1 = 1 before adjustment and a value of RX_DELIV2 = 6 after adjustment. The current value of the first RLC entity's receive state variable RX_Next is 2. The sum of the current value of RX_Next and the difference between the change in RX_DELIV can be determined as the first value. The first value is calculated as: RX_Next + RX_DELIV2 - RX_DELIV1, which equals 7.

[0232] As can be seen from Figure 2D , the number of PDCP Control PDUs received by the first RLC entity between the current value of RX_Next and the first value is equal to 1, that is, the second value is equal to 1, and the third value is equal to the sum of the first and second values, that is, 8. From Figure 2D , it can be determined that the number of PDCP Control PDUs received by the first RLC entity within the interval greater than the first value but not greater than the third value is 1, recorded as the fourth value; therefore, the fifth value is equal to the sum of the first, second, and fourth values, that is, 9. From Figure 2D , it can be determined that the sequence number of the first incompletely received RLC SDU with a sequence number not less than 9 is 10, that is, the sequence number of the third RLC SDU is 10, and therefore, RX_Next is updated to 10.

[0233] Step S2103: The first RLC entity moves the receiving window according to the updated RX_Next and generates an RLC status report.

[0234] In some embodiments, the first RLC entity moves the receiving window according to the updated RX_Next and generates an RLC status report.

[0235] In some embodiments, the RLC status report includes information of RLC SDUs that have not been completely received starting from 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.

[0236] In some embodiments, after generating the RLC status report, the first RLC entity sends the RLC status report to the second RLC entity.

[0237] In the disclosed embodiment, the first RLC entity receives the difference between the receive state variable RX_DELIV before and after the update, and updates RX_Next based on the difference between the receive state variable RX_DELIV before and after the update, thereby solving the problem in the related art that the PDCP COUNT and the RLC SN are not one-to-one corresponding. In this way, the RLC status report generated by the first RLC entity based on RX_Next does not include the sequence number of the PDCP PDU that the PDCP entity is about to discard, thereby avoiding the second RLC entity from retransmitting the data packet that the PDCP entity is about to discard based on the RLC status report, thereby saving wireless resources.

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

[0239] 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 involves a first RLC entity 101, and the method includes:

[0240] Step S3101: Receive first information of network device configuration.

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

[0242] In some embodiments, the first RLC entity and the PDCP entity are located in the terminal, and the first RLC entity receives first information configured by the network device.

[0243] In some embodiments, the first information is used to instruct the first RLC entity to enable a first function, and the PDCP entity to enable a second function.

[0244] In some embodiments, the first function is to receive the difference between the reception state variable RX_DELIV before and after the update sent by the PDCP entity, and update the reception state variable RX_Next according to the difference.

[0245] In some embodiments, the second function is to send the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0246] In the above embodiment, after the first RLC entity and the PDCP entity enable corresponding functions, the terminal sends RRC signaling to the network device, and the RRC signaling is used to indicate that the first RLC entity has enabled the function of updating RX_Next according to the difference and adjusting the RLC receiving window accordingly according to the updated RX_Next.

[0247] It should be noted that if the first RLC entity and the PDCP entity are located in the network device, step S3101 is skipped.

[0248] Step S3102: Receive the difference between RX_DELIV before and after the update.

[0249] The optional implementation of step S3102 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.

[0250] In some embodiments, the first RLC entity receives the difference between the RX_DELIV before and after the update.

[0251] Step S3103: Update RX_Next according to the difference between the values ​​before and after the update of RX_DELIV.

[0252] The optional implementation of step S3103 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.

[0253] In some embodiments, the first RLC entity determines the sum of the current value of RX_Next and the difference between the changes in RX_DELIV as the first value.

[0254] In some embodiments, the first RLC entity determines a first incompletely received RLC SDU with a sequence number not less than a first value as the first RLC SDU, and updates RX_Next to the sequence number of the first RLC SDU.

[0255] In some embodiments, after determining the first value, the first RLC entity determines the number of first PDCP Control PDUs received by the first RLC entity and uses the number as the second value.

[0256] In some embodiments, the RLC sequence number corresponding to the first PDCP Control PDU is greater than the current value of RX_Next and not greater than the first value.

[0257] In some embodiments, the first RLC entity determines the second RLC SDU and updates RX_Next to the sequence number of the second RLC SDU.

[0258] In some embodiments, the number of second PDCP Control PDUs received by the first RLC entity is determined as a fourth value; wherein the RLC sequence number corresponding to the second PDCP Control PDU is greater than the first value and not greater than the third value.

[0259] In some embodiments, determining a sum of the first value, the second value, and the fourth value as the fifth value;

[0260] In some embodiments, a third RLC SDU is determined, the third RLC SDU being the first incompletely received RLC SDU with a sequence number not less than a fifth value, and RX_Next is updated to the sequence number of the third RLC SDU.

[0261] Step S3104: Move the receiving window according to the updated RX_Next and generate an RLC status report.

[0262] The optional implementation of step S3104 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.

[0263] In some embodiments, the first RLC entity moves the receiving window according to the updated RX_Next and generates an RLC status report.

[0264] In some embodiments, the RLC status report includes information of RLC SDUs that have not been completely received starting from 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.

[0265] Step S3105: Send an RLC status report to the second RLC entity.

[0266] The optional implementation of step S3105 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.

[0267] In some embodiments, after generating the RLC status report, the first RLC entity sends the RLC status report to the second RLC entity.

[0268] 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 involves a PDCP entity 102, and the method includes:

[0269] Step S4101: Receive first information of network device configuration.

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

[0271] In some embodiments, the first RLC entity and the PDCP entity are located in the terminal, and the PDCP entity receives first information configured by the network device.

[0272] In some embodiments, the first information is used to instruct the first RLC entity to enable a first function, and the PDCP entity to enable a second function.

[0273] In some embodiments, the first function is to receive the difference between the reception state variable RX_DELIV before and after the update sent by the PDCP entity, and update the reception state variable RX_Next according to the difference.

[0274] In some embodiments, the second function is to send the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0275] In the above embodiment, after the first RLC entity and the PDCP entity enable corresponding functions, the terminal sends RRC signaling to the network device, and the RRC signaling is used to indicate that the first RLC entity has enabled the function of updating RX_Next according to the difference and adjusting the RLC receiving window accordingly according to the updated RX_Next.

[0276] It should be noted that if the first RLC entity and the PDCP entity are located in the network device, step S4101 is skipped.

[0277] Step S4102: Send the difference between the RX_DELIV before and after the update to the first RLC entity.

[0278] The optional implementation of step S4102 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.

[0279] In some embodiments, due to the expiration of the reordering timer t-Reordering, the PDCP entity is triggered to update the value of the reception state variable RX_DELIV.

[0280] In some embodiments, the PDCP entity sends the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

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

[0282] Step S5101: A first RLC entity or a PDCP entity receives first information configured by a network device.

[0283] The optional implementation of step S5101 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.

[0284] In some embodiments, the first RLC entity and the PDCP entity are located in the terminal, and the first RLC entity or the PDCP entity receives first information configured by the network device.

[0285] In some embodiments, the first information is used to instruct the first RLC entity to enable a first function, and the PDCP entity to enable a second function.

[0286] In some embodiments, the first function is to receive the difference between the reception state variable RX_DELIV before and after the update sent by the PDCP entity, and update the reception state variable RX_Next according to the difference.

[0287] In some embodiments, the second function is to send the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0288] It should be noted that if the first RLC entity and the PDCP entity are located in the terminal, the embodiment of the present disclosure does not limit the order in which the first RLC entity and the PDCP entity enable corresponding functions; if the first RLC entity and the PDCP entity are located in the network device, step S5101 is skipped.

[0289] In step S5102, the PDCP entity sends the difference between the RX_DELIV before and after the update to the first RLC entity.

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

[0291] In some embodiments, due to the expiration of the reordering timer t-Reordering, the PDCP entity is triggered to update the value of the reception state variable RX_DELIV.

[0292] In some embodiments, the PDCP entity sends the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

[0293] Step S5103: The first RLC entity updates RX_Next according to the difference between the values ​​before and after the update of RX_DELIV.

[0294] The optional implementation of step S5103 can refer to the optional implementation of step S2102 in Figure 2A, step S3103 in Figure 3, and other related parts in the embodiments involved in Figures 2A and 3, which will not be repeated here.

[0295] In some embodiments, the first RLC entity determines the sum of the current value of RX_Next and the difference between the changes in RX_DELIV as the first value.

[0296] In some embodiments, the first RLC entity determines a first incompletely received RLC SDU with a sequence number not less than a first value as the first RLC SDU, and updates RX_Next to the sequence number of the first RLC SDU.

[0297] In some embodiments, after determining the first value, the first RLC entity determines the number of first PDCP Control PDUs received by the first RLC entity and uses the number as the second value.

[0298] In some embodiments, the RLC sequence number corresponding to the first PDCP Control PDU is greater than the current value of RX_Next and not greater than the first value.

[0299] In some embodiments, the first RLC entity determines the second RLC SDU and updates RX_Next to the sequence number of the second RLC SDU.

[0300] In some embodiments, the number of second PDCP Control PDUs received by the first RLC entity is determined and used as the fourth value; wherein the RLC sequence number corresponding to the second PDCP Control PDU is greater than the first value and not greater than the third value.

[0301] In some embodiments, determining a sum of the first value, the second value, and the fourth value as the fifth value;

[0302] In some embodiments, a third RLC SDU is determined, the third RLC SDU being the first incompletely received RLC SDU having a sequence number not less than the fifth value, and RX_Next is updated to the sequence number of the third RLC SDU.

[0303] Step S5104: The first RLC entity moves the receiving window according to the updated RX_Next and generates an RLC status report.

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

[0305] In some embodiments, the first RLC entity moves the receiving window according to the updated RX_Next and generates an RLC status report.

[0306] In some embodiments, the RLC status report includes information of RLC SDUs that have not been completely received starting from 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.

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

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

[0309] In some embodiments, after generating the RLC status report, the first RLC entity sends the RLC status report to the second RLC entity.

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

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

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

[0313] FIG6A is a schematic diagram of the structure of a first RLC entity proposed in an embodiment of the present disclosure. As shown in FIG6A , the first RLC entity may include: a receiving module 6101 and a processing module 6102 .

[0314] In some embodiments, the receiving module is configured to receive a difference between a receive state variable RX_DELIV before and after update, sent by a Packet Data Convergence Protocol (PDCP) entity.

[0315] In some embodiments, the processing module is configured to update a receiving state variable RX_Next according to the difference, where the receiving state variable RX_Next is configured to indicate a lower edge of a receiving window of the first RLC entity.

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

[0317] FIG6B is a schematic diagram of the structure of a PDCP entity proposed in an embodiment of the present disclosure. As shown in FIG6B , the PDCP entity may include: a sending module 6201 .

[0318] In some embodiments, the sending module is used to send the difference between the receiving state variable RX_DELIV before and after the update to the first RLC entity, so that the first RLC entity updates the receiving state variable RX_Next according to the difference, and the receiving state variable RX_Next is used to indicate the lower edge of the receiving window of the first RLC entity.

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

[0320] Figure 7A 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 to implement 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.

[0321] As shown in Figure 7A, 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.

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

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

[0324] 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 to FIG. 7A. 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.

[0325] 7B is a schematic diagram of the structure of the chip 8200 proposed in 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 FIG7B , but the present disclosure is not limited thereto.

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

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

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

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

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

[0331] 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: Receive the difference between the receive state variable RX_DELIV before and after the update sent by the packet data convergence protocol PDCP entity; A receiving state variable RX_Next is updated according to the difference, where the receiving state variable RX_Next is used to indicate a lower edge of a receiving window of the first RLC entity.

2. The method according to claim 1, characterized in that The updating of the receiving state variable RX_Next according to the difference further includes: Determine the sum of the difference between the current value of RX_Next and the change of RX_DELIV as the first value; or, Determine the number of first PDCP Control PDUs received by the first RLC entity and use the number as a second value; determine the sum of the first value and the second value as a third value; The RLC sequence number corresponding to the first PDCP Control PDU is greater than the current value of RX_Next and not greater than the first value.

3. The method according to claim 2, characterized in that The updating of the receiving state variable RX_Next according to the difference includes: Determining a first radio link control service data unit RLC SDU, where the first RLC SDU is a first incompletely received RLC SDU whose sequence number is not less than the first value; Update the RX_Next to the sequence number of the first RLC SDU.

4. The method according to claim 2, characterized in that The updating of the receiving state variable RX_Next according to the difference includes: Determining a second RLC SDU, where the second RLC SDU is a first RLC SDU that is not completely received and has a sequence number that is not less than the third value; Update the RX_Next to the sequence number of the second RLC SDU.

5. The method according to claim 2, characterized in that The updating of the receiving state variable RX_Next according to the difference includes: Determine a number of second PDCP Control PDUs received by the first RLC entity and use the number as a fourth value, where an RLC sequence number corresponding to the second PDCP Control PDU is greater than the first value and not greater than the third value; determining a sum of the first value, the second value, and the fourth value as a fifth value; Determining a third RLC SDU, where the third RLC SDU is a first RLC SDU that is not completely received and has a sequence number that is not less than the fifth value; Update the RX_Next to the sequence number of the third RLC SDU.

6. The method according to any one of claims 1 to 5, characterized in that The first RLC entity and the PDCP entity are located in a terminal; The difference in the change of the receiving state variable RX_DELIV sent by the receiving Packet Data Convergence Protocol PDCP entity also includes: receiving first information configured by a network device, where the first information is used to instruct the first RLC entity to enable a first function and the PDCP entity to enable a second function; The first function is to receive a difference between a reception state variable RX_DELIV sent by the PDCP entity before and after the update, and to update a reception state variable RX_Next according to the difference; The second function is to send the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

7. The method according to claim 6, characterized in that The network device indicates the first information by any one of the following: Radio Resource Control (RRC) signaling; third PDCP Control PDU; Fields in the PDCP PDU header; RLC Control PDU; fields in the RLC PDU header; or, Media Access Control Element MAC CE.

8. The method according to claim 7, characterized in that The radio resource control (RRC) signaling is any one of the following: Radio Link Control Bearer Signaling RLCBearerConfig; Radio link control configuration signaling RLC-Config; Packet Data Convergence Protocol Configuration Signaling PDCP-Config; Cell group configuration signaling CellGroupConfig.

9. The method according to any one of claims 1 to 8, characterized in that The method further includes updating the receiving state variable RX_Next according to the difference, and then further including: Moving the receiving window of the first RLC entity according to the updated RX_Next and generating an RLC status report; The RLC status report is sent to the second RLC entity.

10. A communication method, characterized in that: The method is performed by a PDCP entity and includes: The difference between the receive state variable RX_DELIV before and after the update is sent to the first RLC entity, so that the first RLC entity updates the receive state variable RX_Next according to the difference, and the receive state variable RX_Next is used to indicate the lower edge of the receive window of the first RLC entity.

11. The method according to claim 10, characterized in that The step of sending the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity further includes: The reordering timer t-Reordering times out, triggering the PDCP entity to update the receiving state variable RX_DELIV.

12. The method according to claim 10 or 11, characterized in that The PDCP entity is located in a network device, and the network device adopts a centralized unit and a distributed unit separation architecture; The sending the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity includes: The centralized unit sends a new radio interface user plane protocol NR User Plane Protocol signaling to the distributed unit, where the new radio interface user plane protocol signaling is used to indicate a difference between the receive state variable RX_DELIV before and after the update and an identifier of the corresponding first RLC entity; The new air interface user plane protocol is associated with a data radio bearer DRB, and when the new air interface user plane protocol is used to indicate the difference before and after RX_DELIV update, the user plane protocol signaling is the new air interface user plane protocol instance corresponding to the first RLC entity.

13. The method according to claim 10 or 11, characterized in that The first RLC entity and the PDCP entity are located in a terminal; The step of sending the updated difference value of the receive state variable RX_DELIV to the first RLC entity further includes: receiving first information configured by a network device, where the first information is used to instruct the first RLC entity to enable a first function and the PDCP entity to enable a second function; The first function is to receive a difference between a reception state variable RX_DELIV sent by the PDCP entity before and after the update, and to update a reception state variable RX_Next according to the difference; The second function is to send the difference between the receive state variable RX_DELIV before and after the update to the first RLC entity.

14. The method according to claim 13, characterized in that The network device indicates the first information by any one of the following: Radio Resource Control (RRC) signaling; Third PDCP Control PDU; Fields in the PDCP PDU header; RLC ControlPDU; fields in the RLC PDU header; or, Media Access Control Element MAC CE.

15. The method according to claim 14, characterized in that The radio resource control (RRC) signaling is any one of the following: Radio Link Control Bearer Signaling RLCBearerConfig; Radio link control configuration signaling RLC-Config; Packet Data Convergence Protocol Configuration Signaling PDCP-Config; Cell group configuration signaling CellGroupConfig.

16. A first RLC entity, characterized in that: include: A receiving module, configured to receive a difference between a receive state variable RX_DELIV before and after an update, sent by a packet data convergence protocol PDCP entity; A processing module is configured to update a receiving state variable RX_Next according to the difference, where the receiving state variable RX_Next is used to indicate a lower edge of a receiving window of the first RLC entity.

17. A PDCP entity, characterized in that: include: The sending module is used to send the difference between the receiving state variable RX_DELIV before and after the update to the first RLC entity, so that the first RLC entity updates the receiving state variable RX_Next according to the difference, and the receiving state variable RX_Next is used to indicate the lower edge of the receiving window of the first RLC entity.

18. 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 9.

19. 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 10 to 15.

20. 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 9; A PDCP entity, configured to implement the communication method according to any one of claims 10 to 15.

21. 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 9 and 10 to 15.

Images