Reception window processing methods, entities, communication system and storage medium

Abstract

The present disclosure relates to reception window processing methods, entities, a communication system and a storage medium. A method comprises: sending a first RLC SDU to a PDCP entity, wherein the first RLC SDU is at least one RLC SDU completely received by an AM RLC entity; receiving a first sequence number (SN) sent by the PDCP entity; and processing a state variable RX_Next on the basis of the first SN, the state variable RX_Next being used for indicating the lower edge of a reception window, wherein the first SN is an RLC SN of an RLC SDU, which corresponds to a PDCP PDU having a first count, among first RLC SDUs, or the first SN is a PDCP SN in the first count; the first count is the maximum count, within a count range, among counts of PDCP PDUs corresponding to the first RLC SDUs; and the count range is related to a state variable RX_DELIV before and after the PDCP entity is updated. In the embodiments of the present disclosure, the reception window can be accurately adjusted when PDCP counts do not correspond to SNs of RLC SDUs on a one-to-one basis, thereby avoiding the waste of wireless resources.

Description

Receive window processing method, entity, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method, entity, communication system, and storage medium for processing a receiving window. Background Art

[0002] 3GPP Radio Link Control (RLC) entities can be configured in three modes: Transparent Mode (TM), Unacknowledged Mode (UM), or Acknowledged Mode (AM). Accordingly, an RLC entity is classified as a TM RLC entity, a UM RLC entity, or an AM RLC entity.

[0003] When the state variable RX_DELIV of the Packet Data Convergence Protocol (PDCP) entity increases due to the expiration of the t-Reordering timer, the PDCP entity will discard the received Packet Data Convergence Protocol Protocol Data Unit (PDCP PDU) whose COUNT (ie, count) is less than RX_DELIV.

[0004] If the RLC entity corresponding to the PDCP entity is an AM RLC entity, the AM RLC entity will continue to retransmit the RLC SDUs that the PDCP entity is not waiting for in the lossless working mode until they are completely received. In this way, the ARQ retransmission of the data packets that the PDCP entity will discard will cause a waste of radio resources.

[0005] Summary of the Invention

[0006] The embodiments of the present disclosure provide a receiving window processing method, entity, communication system, and storage medium.

[0007] In a first aspect, an embodiment of the present disclosure provides a method for processing a receive window, which is performed by an AM RLC entity. The method includes:

[0008] Sending a first RLC SDU to a PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity;

[0009] receiving a first SN sent by the PDCP entity;

[0010] Processing a state variable RX_Next according to the first SN, where the state variable RX_Next is used to indicate a lower edge of a receiving window;

[0011] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0012] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

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

[0014] receiving a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity;

[0015] Sending a first SN to the AM RLC entity;

[0016] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0017] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

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

[0019] a transceiver module configured to send a first RLC SDU to a PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and receive a first SN sent by the PDCP entity;

[0020] a processing module, configured to process a state variable RX_Next according to the first SN, wherein the state variable RX_Next is used to indicate a lower edge of the receiving window;

[0021] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0022] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

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

[0024] a transceiver module configured to receive a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and send a first SN to the AM RLC entity;

[0025] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0026] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

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

[0028] one or more processors;

[0029] The processor is used to execute the method described in the first aspect.

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

[0031] one or more processors;

[0032] The processor is used to execute the method described in the second aspect.

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

[0034] 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 methods in the embodiments of the present disclosure.

[0035] In a ninth aspect, an embodiment of the present disclosure proposes a program product, which is used by a communication device to execute any one of the methods in the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0039] FIG2B is an exemplary schematic diagram showing an AM RLC entity updating a receive state variable RX_Next according to an embodiment of the present disclosure;

[0040] FIG2C is an exemplary schematic diagram showing an AM RLC entity updating a receive state variable RX_Next according to an embodiment of the present disclosure;

[0041] FIG3 is a flow chart of a method for processing a receiving window according to an embodiment of the present disclosure;

[0042] FIG4 is a flow chart of a method for processing a receiving window according to an embodiment of the present disclosure;

[0043] FIG5 is a flow chart of a method for processing a receiving window according to an embodiment of the present disclosure;

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

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

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

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

[0048] The embodiments of the present disclosure provide a communication method, a terminal, a network element, a device, and a storage medium.

[0049] In a first aspect, an embodiment of the present disclosure provides a method for processing a receive window, which is performed by an AM RLC entity. The method includes:

[0050] Sending a first radio link control layer service data unit RLC SDU to a packet data convergence protocol PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity;

[0051] receiving a first SN sent by the PDCP entity;

[0052] Processing a state variable RX_Next according to the first SN, where the state variable RX_Next is used to indicate a lower edge of a receiving window;

[0053] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0054] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

[0055] The embodiments of the present disclosure provide two methods for describing the correspondence between the PDCP COUNT and the SN of the RLC SDU. According to different methods, the first SN sent by the PDCP entity can be the RLC SN of the RLC SDU corresponding to the PDCP PDU with the first COUNT in the first RLC SDU, or the PDCPSN in the first COUNT, so that the AM RLC entity updates the state variable RX_Next according to the first SN. The embodiments of the present disclosure can accurately adjust the receiving window and avoid waste of wireless resources when there is no one-to-one correspondence between the PDCP COUNT and the RLC SN of the RLC SDU.

[0056] As an optional implementation manner, the first SN is an RLC SN of an RLC SDU corresponding to the PDCP PDU having the first COUNT in the first RLC SDU;

[0057] Sending a first RLC SDU to a PDCP entity, comprising:

[0058] Send the first RLC SDU and the RLC SN of the first RLC SDU to the PDCP entity.

[0059] As an optional implementation manner, processing the state variable RX_Next according to the first SN includes:

[0060] Determining a second RLC SDU, where the second RLC SDU is a first RLC SDU that is not completely received and has an RLC SN that is not less than the first SN;

[0061] The state variable RX_Next is updated to the SN of the second RLC SDU.

[0062] As an optional implementation manner, the first SN is a PDCP SN in the first COUNT;

[0063] The processing of the state variable RX_Next according to the first SN also includes:

[0064] A one-to-one correspondence is established between the RLC SN of the completely received RLC SDU and the PDCP SN in the completely received RLC SDU.

[0065] As an optional implementation manner, processing the state variable RX_Next according to the first SN includes:

[0066] Using the RLC SN of the RLC SDU corresponding to the first SN as the second SN;

[0067] Determining a third RLC SDU, where the third RLC SDU is a first RLC SDU that is not completely received and has an RLC SN that is not less than the second SN;

[0068] The state variable RX_Next is updated to the RLC SN of the third RLC SDU.

[0069] As an optional implementation manner, the first SN is empty and the state variable RX_Next is not updated; or

[0070] The first SN is the RLC SN of the RLC SDU corresponding to the PDCP PDU with the first COUNT in the first RLC SDU, and the first SN is not in the receiving window of the AM RLC entity, and the state variable RX_Next is not updated.

[0071] As an optional implementation manner, the AM 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;

[0072] The RLC SN of the first RLC SDU is sent in the following manner:

[0073] The distributed unit where the AM RLC entity is located sends a GTP-U message to the centralized unit where the PDCP entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

[0074] As an optional implementation manner, the AM 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;

[0075] The receiving a first SN sent by the PDCP entity includes:

[0076] The distributed unit where the AM RLC entity is located receives new air interface user plane protocol signaling NR User Plane Protocol corresponding to the AM RLC entity and sent by the centralized unit where the PDCP entity is located, where the new air interface user plane protocol signaling is used to indicate the first SN.

[0077] As an optional implementation manner, the AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture;

[0078] The RLC SN of the first RLC SDU is sent in the following manner:

[0079] The base station node where the AM RLC entity is located sends a GTP-U message to the base station node where the PDCP entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

[0080] As an optional implementation manner, the AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture;

[0081] The receiving a first SN sent by the PDCP entity includes:

[0082] The base station node where the AM RLC entity is located receives NR User Plane Protocol signaling corresponding to the AM RLC entity and sent by the base station node where the PDCP entity is located, where the NR User Plane Protocol signaling is used to indicate the first SN.

[0083] As an optional implementation manner, the AM RLC entity and the PDCP entity are located in a terminal;

[0084] Sending a first RLC SDU to a PDCP entity, prior to which:

[0085] receiving first information configured by a network device, where the first information is used to instruct an AM RLC entity to enable a first function for a receive window and a PDCP entity to enable a second function for the receive window;

[0086] The first function includes: sending a first RLC SDU to a PDCP entity, receiving a first SN sent by the PDCP entity, and processing a state vector RX_Next according to the first SN;

[0087] The second function includes: receiving a first RLC SDU sent by an AM RLC entity, and sending a first SN to the AM RLC entity.

[0088] As an optional implementation manner, the network device indicates the first information in any of the following ways:

[0089] Indicating the first information in radio resource control RRC signaling;

[0090] indicating the first information in a PDCP Control PDU;

[0091] indicating the first information in an RLC Control PDU;

[0092] Indicating the first information in a PDCP PDU header;

[0093] Indicating the first information in an RLC PDU header; or,

[0094] The first information is indicated in a medium access control element MAC CE.

[0095] As an optional implementation, the COUNT range is [RX_DELIV1+1,RX_DELIV2-1];

[0096] Among them, RX_DELIV1 represents the state variable RX_DELIV before updating; RX_DELIV2 represents the state variable RX_DELIV after updating.

[0097] As an optional implementation manner, the state variable RX_DELIV before and after the PDCP entity is updated refers to: the state variable RX_DELIV before and after the PDCP entity is updated due to the expiration of the t-Reordering timer.

[0098] As an optional implementation, the first SN is sent when the PDCP entity determines that the COUNT of at least one PDCP PDU corresponding to the first RLC SDU is within the COUNT range, that is, if the COUNT of at least one PDCP PDU corresponding to the first RLC SDU is not within the technical COUNT range, the PDCP entity does not send the first SN.

[0099] As an optional implementation manner, processing the state variable RX_Next according to the first SN includes:

[0100] Moving the receiving window of the AM RLC entity according to the updated state variable RX_Next and generating an RLC status report;

[0101] Sending the RLC status report to an entity on the opposite side of the AM RLC entity.

[0102] In a second aspect, an embodiment of the present disclosure provides a method for processing a receive window, which is performed by a PDCP entity. The method includes:

[0103] receiving a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity;

[0104] Sending a first SN to the AM RLC entity;

[0105] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0106] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

[0107] As an optional implementation manner, the first SN is an RLC SN of an RLC SDU corresponding to the PDCP PDU having the first COUNT in the first RLC SDU;

[0108] The receiving a first RLC SDU sent by the AM RLC entity includes:

[0109] Receive the first RLC SDU and the RLC SN of the first RLC SDU sent by the AM RLC entity.

[0110] As an optional implementation manner, the first SN is determined by:

[0111] Establishing a one-to-one correspondence between the RLC SN of the first RLC SDU and the COUNT of the PDCP PDU corresponding to the RLC SN of the RLC SDU;

[0112] According to the corresponding relationship and the first COUNT, an RLC SN of an RLC SDU corresponding to the PDCP PDU having the first COUNT in the first RLC SDU is determined and used as the first SN.

[0113] As an optional implementation manner, the AM 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;

[0114] The RLC SN of the first RLC SDU is received in the following manner, including:

[0115] The centralized unit where the PDCP entity is located receives a GTP-U message sent by the distributed unit where the AM RLC entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

[0116] As an optional implementation manner, the AM 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;

[0117] The sending the first SN to the AM RLC entity includes:

[0118] The centralized unit where the PDCP entity is located sends a new air interface user plane protocol signaling NR User Plane Protocol corresponding to the AM RLC entity to the distributed unit where the AM RLC entity is located, where the new air interface user plane protocol signaling is used to indicate the first SN.

[0119] As an optional implementation manner, the AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture;

[0120] The RLC SN of the first RLC SDU is received in the following manner:

[0121] The base station node where the PDCP entity is located receives a GTP-U message sent by the base station node where the AM RLC entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

[0122] As an optional implementation manner, the AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture;

[0123] The sending the first SN to the AM RLC entity includes:

[0124] The base station node where the PDCP is located sends NR User Plane Protocol signaling corresponding to the AM RLC entity to the base station node where the AM RLC entity is located, where the NR User Plane Protocol signaling is used to indicate the first SN.

[0125] As an optional implementation manner, the AM RLC entity and the PDCP entity are located in a terminal;

[0126] The receiving of the first RLC SDU sent by the AM RLC entity also includes:

[0127] receiving first information sent by a network device, where the first information is used to instruct an AM RLC entity to enable a first function for a receive window and a PDCP entity to enable a second function for the receive window;

[0128] The first function includes: sending a first RLC SDU to a PDCP entity, receiving a first SN sent by the PDCP entity, and processing a state vector RX_Next according to the first SN;

[0129] The second function includes: receiving a first RLC SDU sent by an AM RLC entity, and sending a first SN to the AM RLC entity.

[0130] As an optional implementation manner, the network device indicates the first information in any of the following ways:

[0131] indicating the first information in RRC signaling;

[0132] indicating the first information in a PDCP Control PDU;

[0133] indicating the first information in an RLC Control PDU;

[0134] Indicating the first information in a PDCP PDU header;

[0135] Indicating the first information in an RLC PDU header; or,

[0136] The first information is indicated in a MAC CE.

[0137] As an optional implementation, the COUNT range is [RX_DELIV1+1,RX_DELIV2-1];

[0138] Among them, RX_DELIV1 represents the state variable RX_DELIV before updating; RX_DELIV2 represents the state variable RX_DELIV after updating.

[0139] As an optional implementation manner, the state variable RX_DELIV before and after the PDCP entity is updated refers to: the state variable RX_DELIV before and after the PDCP entity is updated due to the expiration of the t-Reordering timer.

[0140] As an optional implementation manner, sending the first SN to the AM RLC entity includes:

[0141] Determine that there is a COUNT of at least one PDCP PDU corresponding to the first RLC SDU and is within a COUNT range, and send a first SN to the AM RLC entity.

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

[0143] a transceiver module configured to send a first RLC SDU to a PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and receive a first SN sent by the PDCP entity;

[0144] a processing module, configured to process a state variable RX_Next according to the first SN, wherein the state variable RX_Next is used to indicate a lower edge of the receiving window;

[0145] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0146] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

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

[0148] a transceiver module configured to receive a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and send a first SN to the AM RLC entity;

[0149] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0150] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

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

[0152] one or more processors;

[0153] The processor is used to execute the method described in the first aspect.

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

[0155] one or more processors;

[0156] The processor is used to execute the method described in the second aspect.

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

[0158] 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 methods in the embodiments of the present disclosure.

[0159] In a ninth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect or the second aspect.

[0160] In a tenth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0161] It is understandable that the aforementioned entities, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure, and when there is no one-to-one correspondence between PDCP COUNTs and RLC SDU SNs, waste of radio resources can be avoided. Therefore, the beneficial effects achieved can be referenced to the beneficial effects of the corresponding methods and will not be further elaborated here.

[0162] The present disclosure provides a method, entity, communication system, and storage medium for processing a receive window. In some embodiments, the terms "receive window processing method" and "communication method," "signal transmission method," and "wireless frame transmission method" are interchangeable, and the terms "information processing system" and "communication system" are interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0178] In some embodiments, the access 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 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.

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

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

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

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

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

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

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

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

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

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

[0189] FIG1 is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 and an access network device 102 .

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

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

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

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

[0194] In some embodiments, the access network device may be a single device including a first network element 1021, a second network element 1022, etc., or may be multiple devices or a device group including all or part of an AM RLC network element, a PDCP network element, etc. The network element may be virtual or physical. In some embodiments, the first network element may be an AM RLC network element, and the second network element may be a PDCP network element.

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

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

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

[0198] An AM RLC entity consists of a transmitting side and a receiving side. For an RLC entity configured on the network side, there is an RLC peer entity configured on the UE side, and vice versa. An RLC entity receives RLC SDUs from upper layers and passes them to upper layers. An RLC entity sends RLC PDUs to or receives RLC PDUs from an RLC peer entity through lower layers. 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.

[0199] RLC AM supports ARQ functionality. RLC status reporting can be triggered by:

[0200] 1) Polling of the peer AM RLC entity;

[0201] 2) Detection of AMD PDU reception failure: When the timer t-Reassembly expires, the receiving side of the AM RLC entity triggers an RLC status report. ARQ retransmits the RLC SDU or RLC SDU segment based on the RLC status report.

[0202] RLC PDUs are categorized as RLC data PDUs and RLC control PDUs. RLC data PDUs are used to transmit higher-layer PDUs (i.e., RLC SDUs). RLC data PDUs in AM mode are called AMD PDUs. RLC control PDUs are used for ARQ. The RLC status report mentioned above is an RLC control PDU.

[0203] When performing arithmetic comparisons (e.g., <, <=) on a status variable or a Sequence Number (SN), the modulus base is used. On the AM RLC receiving side, RX_Next is the modulus base. All relevant values are subtracted by the modulus base and then compared. For example, for RX_Next <= SN < RX_Next + AM_Window_Size, the comparison is performed as follows: [RX_Next – RX_Next] modulo 2[sn-FieldLength] <= [SN – RX_Next] modulo 2[sn-FieldLength] < [RX_Next + AM_Window_Size –

[0204] RX_Next] modulo 2[sn-FieldLength]), where sn-FieldLength is the length of SN, which is 12 or 18 in NR. In the embodiments of the present disclosure, unless otherwise specified, all arithmetic comparisons on the status 03 variables or SNs of the AM RLC entity use the modulus base.

[0205] The AM RLC entity maintains a window on both the transmitting side and the receiving side.

[0206] On the transmitting side of the AM RLC entity, the transmitting window is maintained according to the status variable TX_Next_Ack, that is, when the SN of the AMD PDU is within the following range, it is considered that the SN is within the transmitting window: TX_Next_Ack <= SN < TX_Next_Ack + AM_Window_Size, where AM_Window_Size is the size of the window. For 12-bit and 18-bit SNs, AM_Window_Size is 2048 and 131072 respectively. The AM RLC entity does not send down to the lower layer the AMD PDU whose SN is outside the transmitting window. The status variable TX_Next_Ack is the lower edge of the transmitting window. When it receives the RLC status report indicating that the RLC SDU with SN = TX_Next_Ack has been completely received, the AM RLC entity updates TX_Next_Ack.

[0207] On the receiving side, the AM RLC entity maintains a receiving window according to the status variable RX_Next. That is, when the SN of an AMD PDU is within the following range, it is considered to be within the receiving window: RX_Next <= SN < RX_Next + AM_Window_Size, where the definition of AM_Window_Size is as described above. The AM RLC entity discards AMD PDUs outside the receiving window. The status variable RX_Next is the lower edge of the receiving window. When the RLC SDU with RLC SN = RX_Next has been completely received, the AM RLC entity updates RX_Next.

[0208] When the AM RLC entity constructs an RLC status report, it starts from SN = RX_Next and reports information about RLC SDUs that have not been completely received: the RLC SN of the RLC SDUs not received, and the RLC SN of the partially received RLC SDUs and the un-received segmentation information (SOstart, SOend). The field ACK_SN in the RLC status report indicates the SN of the next un-received RLC SDU that has not been reported as lost in the status report. When the sending side of the AM RLC entity receives the status report, it will consider that all RLC SDUs up to ACK_SN (but not including ACK_SN) have been correctly received, except for those indicated by NACK_SN, NACK_range, SOstart, and SOend and the parts of the RLC SDUs.

[0209] The current working mode of the NR RLC AM is lossless. That is, if the RLC SDU with RLC SN = RX_Next has not been completely received, the receiving side of the AM RLC entity will notify the peer RLC entity through a status report that the RLC SDU has not been completely received. The sending side of the peer AM RLC entity will perform ARQ retransmission until the RLC SDU with RLC SN = RX_Next has been completely received, at which time the status variable RX_Next will be updated.

[0210] The gNB-CU-User Plane (gNB-CU-UP) is a logical node that carries the user plane functions for the PDCP and SDAP protocols within the gNB-CU. The gNB-CU-UP terminates the E1 interface with the gNB-CU-CP and the F1-U interface with the gNB-DU. In a DC configuration, MgNB-CU-UP refers to the gNB-CU-UP of the gNB serving as the master node, while SgNB-CU-UP refers to the gNB-CU-UP of the gNB serving as the secondary node. MgNB-DU refers to the gNB-DU of the gNB serving as the master node, while SgNB-DU refers to the gNB-DU of the gNB serving as the secondary node.

[0211] When the state variable RX_DELIV of the PDCP entity increases due to the expiration of the timer t-Reordering, the PDCP entity will discard the received PDCP PDUs whose COUNT value is less than RX_DELIV.

[0212] If the RLC entity corresponding to the PDCP entity is an AM RLC entity, the AM RLC entity will continue to retransmit the RLC SDUs that the PDCP entity is not waiting for in the lossless working mode until they are completely received. In this way, the ARQ retransmission of the data packets that the PDCP entity will discard will cause a waste of radio resources.

[0213] In some embodiments, when t-Reordering times out, the PDCP entity notifies the RLC entity of the receive window update status, causing the RLC entity to make corresponding receive window adjustments and notify the peer RLC entity. This paper assumes a one-to-one correspondence between the PDCP COUNT and the RLC SN. Since the PDCP COUNT is 32 bits and the RLC SN is 12 or 18 bits, this one-to-one correspondence primarily refers to the difference in the PDCP COUNT between two RLC PDUs being equal to the difference in the corresponding RLC SN. In the NR system, the PDCP COUNT and RLC SN do not correspond one-to-one. This is because the PDCP Control PDU does not have a PDCP COUNT, but is an RLC SDU at the RLC layer and has a corresponding RLC SN. Furthermore, split bearers can be used in dual connectivity, meaning that PDCP PDUs within a PDCP entity are transmitted by different RLC entities, resulting in a non-one-to-one correspondence between the PDCP COUNT and the RLC SN.

[0214] The disclosed embodiments provide a method for adjusting the AM RLC receive window based on the relationship between the PDCP PDU COUNT and the corresponding RLC PDU SN. After adjusting the RLC receive window, the AM RLC entity receiving side can trigger an RLC status report. This allows the peer RLC entity to avoid retransmitting packets that may have been discarded by the PDCP entity based on the RLC status report. This avoids wasting radio resources even when there is no one-to-one correspondence between the PDCP COUNT and the RLC SN.

[0215] The embodiment of the present disclosure provides a method for adjusting the AM RLC receiving window based on the relationship between the COUNT of the PDCP PDU and the SN of the corresponding RLC PDU. The AM RLC entity receiving side can trigger an RLC status report after adjusting the RLC receiving window.

[0216] When the PDCP entity adjusts the receive state variable RX_DELIV (this variable 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, and is hereinafter referred to as RX_DELIV) due to the expiration of the t-Reordering timer, the lower edge of the AM RLC entity's receive window (i.e., indicating the next SN of the last RLC SDU completely received in sequence, and is hereinafter referred to as RX_Next) is adjusted based on the relationship between the COUNT value of the PDCP PDU and the SN of the corresponding RLC PDU. This patent is applicable to both non-separable bearers and separable bearers.

[0217] If the value of RX_DELIV before adjustment is RX_DELIV1 and after adjustment is RX_DELIV2, then for received PDCP PDUs (i.e., completely received RLC SDUs) whose COUNT satisfies RX_DELIV1+1<=COUNT<=RX_DELIV2–1, the largest COUNT value among the PDCP PDUs received by the corresponding AM RLC entity is selected. Let the RLC SN of the RLC SDU corresponding to the PDCP PDU be RLC_SN. The AM RLC entity then updates RX_Next to the RLC SN of the first RLC SDU whose RLC SN is greater than RLC_SN and that has not been completely received.

[0218] If the set of received PDCP PDUs (i.e., completely received RLC SDUs) for which the COUNT corresponding to the AM RLC entity satisfies RX_DELIV1+1<=COUNT<=RX_DELIV2–1 is an empty set, the AM RLC entity receiving side does not adjust the lower edge of the receive window (i.e., RX_Next). Alternatively, if the RLC_SN is not within the AM RLC entity's receive window, the AM RLC entity receiving side does not adjust the lower edge of the receive window (i.e., RX_Next).

[0219] FIG2A is an interactive diagram of a method for processing a receive window according to an embodiment of the present disclosure. As shown in FIG2A , an embodiment of the present disclosure relates to a method for processing a receive window, which is used in a communication system 100. The method includes:

[0220] S2101. The AM RLC entity sends a first RLC SDU to the PDCP entity.

[0221] In some embodiments, the PDCP entity receives a first RLC SDU.

[0222] In some embodiments, the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity. It should be understood that when split bearers are used, one PDCP entity can receive completely received RLC SDUs sent by multiple AM ​​RLC entities.

[0223] The embodiment of the present disclosure utilizes the relationship between the COUNT of the PDCP PDU and the SN of the corresponding RLC PDU in the following ways:

[0224] Mode 1: When the AM RLC entity receives the first RLC SDU, it also passes the SN of the first RLC SDU to the PDCP entity. It should be understood that since the first RLC SDU is at least one completely received RLC SDU, the RLC SN of the passed first RLC SDU is the RLC SN of each of the at least one completely received RLC SDUs. The PDCP entity derives the PDCP COUNT based on the PDCP SN and establishes a correspondence between the PDCP COUNT and the RLC SN.

[0225] Mode 2: Since the RLC SDU contains the PDCP SN, the AM RLC entity can establish a correspondence between the SN of the RLC SDU and the PDCP SN in the RLC SDU. Moreover, since the COUNT is composed of the HFN and the SN, the PDCP entity is configured with the length of the PCCP SN for downlink and uplink transmission. Therefore, the PDCP entity can indicate the PDCP SN corresponding to the COUNT value to the corresponding AM RLC entity, so that the AM RLC entity determines the RLC SN corresponding to the indicated PDCP SN based on the correspondence between the PDCP SN and the RLC SN.

[0226] In some embodiments, the RLC SN of the first RLC SDU may be sent simultaneously with the first RLC SDU, or may be sent at different times. For example, the RLC SN of the first RLC SDU may be sent after step S2101 and before step S2103. This embodiment of the present application does not limit the timing relationship between sending the first RLC SDU and the RLC SN of the first RLC SDU.

[0227] In some embodiments, the AM RLC entity establishes a correspondence between the RLC SN of the fully received RLC SDU and the PDCP SN in the fully received RLC SDU, which can be performed in step S2101 or between steps S2101 and S2103, and is not specifically limited in this embodiment of the present application.

[0228] When the PDCP entity and the AM RLC entity receiving side are on the UE, the network can configure whether to adjust the AM RLC receive window based on the relationship between the PDCP PDU COUNT and the corresponding RLC PDU SN. This configuration can be configured for each PDCP entity, each AM RLC entity, each MAC entity, or each UE.

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

[0230] 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 using a field in the header of the RLC PDU, or by using MAC CE (configured for one or more AM RLC entities).

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

[0232] When configuring for each UE, it can be configured through RRC signaling, and all AM RLC entities of the UE and the PDCP entities associated therewith adopt the configuration.

[0233] In some embodiments, the AM RLC entity and the PDCP entity are located in a terminal. The network device sends first information to the terminal, the first information being used to instruct the AM RLC entity to enable a first function for the receive window and the PDCP entity to enable a second function for the receive window; wherein the first function includes: sending a first RLC SDU to the PDCP entity, receiving a first SN sent by the PDCP entity, and processing a state vector RX_Next according to the first SN; the second function includes: receiving a first RLC SDU sent by the AM RLC entity and sending a first SN to the AM RLC entity. It can be understood that when the AM RLC entity and the PDCP entity are located in a terminal, the AM RLC entity and the PDCP entity themselves have the ability to perform the corresponding functions, but the corresponding functions are not enabled. The network device configures the AM RLC entity and the PDCP entity by sending the first information to the terminal, and then the terminal enables the corresponding functions of the AM RLC entity and the PDCP entity.

[0234] In some embodiments, the network device indicates the first information in any of the following ways:

[0235] indicating the first information in RRC signaling;

[0236] indicating the first information in a PDCP Control PDU;

[0237] indicating the first information in an RLC Control PDU;

[0238] Indicating the first information in a PDCP PDU header;

[0239] Indicating the first information in an RLC PDU header; or,

[0240] The first information is indicated in a MAC CE.

[0241] S2102. The PDCP entity sends a first SN to the AM RLC entity.

[0242] The first SN of the embodiment of the present disclosure is determined by the PDCP entity based on the first COUNT. The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU. The COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated.

[0243] In some embodiments, if the state variable RX_DELIV before updating is represented as RX_DELIV1 and the state variable RX_DELIV after updating is represented as RX_DELIV2, the COUNT range may be represented as [RX_DELIV1+1, RX_DELIV2-1].

[0244] In some embodiments, the state variable RX_DELIV before and after the PDCP entity is updated refers to: the state variable RX_DELIV before and after the PDCP entity is updated due to the expiration of the t-Reordering timer.

[0245] As can be seen from the above embodiments, the embodiments of the present application utilize the relationship between the COUNT of the PDCP PDU and the SN of the corresponding RLC PDU in two ways. Therefore, for different modes, the first SN sent by the PDCP entity is different:

[0246] For method 1, since the PDCP PDU obtains the RLC SN of each RLC SDU completely received by the AM RLC entity, after obtaining the first COUNT, the RLC SN of the RLC SDU corresponding to the first COUNT (referred to as RLC_SN in subsequent embodiments of this disclosure) is used as the first SN and sent to the AM RLC entity.

[0247] For mode 2, since the PDCP COUNT is composed of the HFN and the PDCP SN, after obtaining the maximum COUNT, the PDCU PDU can determine the PDCP SN from the maximum COUNT and send the PDCP SN as the first SN to the AM RLC entity.

[0248] In this embodiment, the PDCP entity transfers the PDCP SN (mode 2) or RLC_SN (mode 1) to the AM RLC entity, and the AM RLC entity transfers the RLC SN of the RLC SDU to the PDCP entity (mode 1) through inter-layer interaction.

[0249] 1) When the receiving side of the PDCP entity and the AM RLC entity is at the UE, this information transfer can be accomplished through the internal implementation of the UE.

[0250] 2) When the PDCP entity and the AM RLC entity receiving side are on the network side, and the base station adopts an integrated architecture (ie, does not adopt a CU-DU separation architecture), this information transmission can be achieved within the base station.

[0251] 3) When the PDCP entity and the AM RLC entity receiving side are on the network side, and the base station adopts the CU-DU separation architecture:

[0252] When the gNB-DU sends an RLC SDU (i.e., PDCP PDU) via the F1-U interface to the gNB-CU or gNB-CU-UP, the RLC SN of the RLC SDU must be sent to the gNB-CU or gNB-CU-UP according to method 1. The GTP-U protocol is used to transmit the RLC SDU, and the RLC SN can be indicated in the GTP-U Extension Header.

[0253] The gNB-CU or gNB-CU-UP needs to notify the corresponding gNB-DU of the RLC_SN (mode 1) or PDCP SN (mode 2) and the corresponding RLC entity identifier in the F1-U interface, for example by introducing new NR User Plane Protocol signaling so that the gNB-DU adjusts the lower edge of the receive window (i.e., RX_Next) after receiving the RLC_SN or PDCP SN. Since an NR User Plane Protocol instance is associated with only one DRB, when NR User Plane Protocol signaling is used to indicate the RLC_SN (mode 1) or PDCP SN (mode 2), only the NR User Plane Protocol instance corresponding to the AM RLC entity is used, meaning that the AM RLC entity identifier is implicitly indicated.

[0254] 4) When the receiving PDCP entity and the AM RLC entity are on the network side and split bearer in DC architecture is used:

[0255] When the PDCP entity is in the MgNB and the AM RLC entity is in the SgNB, and the SgNB sends the RLC SDU (i.e., PDCP PDU) via the Xn interface, the RLC SN of the RLC SDU needs to be sent to the MgNB according to method 1. Similarly, when the PDCP entity is in the SgNB and the AM RLC entity is in the MgNB, and the MgNB sends the RLC SDU (i.e., PDCP PDU) via the Xn interface, the RLC SN of the RLC SDU needs to be sent to the SgNB according to method 1. The GTP-U protocol is used when transmitting the RLC SDU, and the RLC SN can be indicated in the GTP-U Extension Header;

[0256] When the PDCP entity is in the MgNB and the AM RLC entity is in the SgNB, the MgNB needs to notify the corresponding SgNB of the RLC_SN (mode 1) or PDCP SN (mode 2) and the identifier of the corresponding RLC entity in the Xn interface. Similarly, when the PDCP entity is in the SgNB and the AM RLC entity is in the MgNB, the SgNB needs to notify the corresponding MgNB of the RLC_SN (mode 1) or PDCP SN (mode 2) and the identifier of the corresponding RLC entity in the Xn interface. For example, new NR User Plane Protocol signaling can be introduced to transmit RLC_SN (mode 1) or PDCP SN (mode 2). Since the NR User Plane Protocol instance is associated with only one DRB, when NR User Plane Protocol signaling is used to indicate RLC_SN (mode 1) or PDCP SN (mode 2), only the NR User Plane Protocol instance corresponding to the AM RLC entity is used, that is, the identifier of the AM RLC entity has been implicitly indicated.

[0257] In some embodiments, the PDCP entity determines that the COUNT of at least one PDCP PDU corresponding to the first RLC SDU is within the COUNT range, and sends a first SN to the AM RLC entity. That is, if the COUNT of at least one PDCP PDU corresponding to the first RLC SDU is not within the COUNT range, the PDCP entity will not send the first SN, and accordingly, the receiving side of the AM RLC entity does not adjust the lower edge of the receiving window (that is, the state variable RX_Next).

[0258] S2103. The AM RLC entity processes the state variable RX_Next according to the first SN.

[0259] For mode 1, the AM RLC entity determines a second RLC SDU based on the first SN, where the second RLC SDU is the first RLC SDU that is not completely received and whose RLC SN is not less than the first SN; and updates the state variable RX_Next to the SN of the second RLC SDU.

[0260] For mode 2, the AM RLC entity uses the RLC SN of the RLC SDU corresponding to the first SN as the second SN; determines a third RLC SDU, where the third RLC SDU is the first RLC SDU that has not been completely received and whose RLC SN is not less than the second SN, and updates the state variable RX_Next to the RLC SN of the third RLC SDU.

[0261] In some embodiments, if RLC_SN is not within the receiving window of the AM RLC entity, the receiving side of the AM RLC entity does not adjust the lower edge of the receiving window (ie, the state variable RX_Next).

[0262] After updating the state variable RX_Next, the AM RLC entity of the embodiment of the present disclosure moves the receiving window of the AM RLC entity according to the updated state variable RX_Next, generates an RLC status report, and sends the RLC status report to the opposite entity of the AM RLC entity.

[0263] The receiving window processing method of the embodiment of the present disclosure provides two ways to describe the correspondence between the PDCP COUNT and the SN of the RLC SDU. According to different ways, the first SN sent by the PDCP entity can be the SN of the RLC SDU corresponding to the PDCP PDU with the first COUNT in the first RLC SDU, or it can be the PDCP SN in the first COUNT, so that the AM RLC entity updates the state variable RX_Next according to the first SN. The embodiment of the present disclosure can accurately adjust the receiving window when there is no one-to-one correspondence between the PDCP COUNT and the RLC SN, thereby avoiding waste of wireless resources.

[0264] Please refer to Figure 2B, which exemplarily shows an exemplary schematic diagram of the AM 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 RLC SN of the RLC SDUs received by the AM 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 RLC SN of the RLC SDUs not received by the AM RLC entity.

[0265] 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 set of COUNTs corresponding to received PDCP PDUs satisfying RX_DELIV1+1 <= COUNT <= RX_DELIV2–1 is {3, 4, 5}, with the maximum COUNT value being 5. The RLC_SN corresponding to this PDCP PDU is 9. The SN of the first RLC SDU with an SN greater than 9 and not completely received is 10, so the RX_Next value updated by the AM RLC entity is 10.

[0266] Please refer to Figure 2C, which exemplarily shows an exemplary schematic diagram of the 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 RLC SN of the RLC SDUs received by the 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 RLC SN of the RLC SDUs not received by the RLC entity.

[0267] As can be seen from FIG2B , one PDCP entity in the embodiment of the present disclosure corresponds to two RLC entities.

[0268] For AM RLC entity 1, the set of COUNTs corresponding to received PDCP PDUs satisfying RX_DELIV1+1<=COUNT<=RX_DELIV2–1 is {3, 4}, where the maximum COUNT value is 4. The SN of the RLC SDU corresponding to the PDCP PDU is RLC_SN=3, and the SN of the first RLC SDU with SN>3 and not completely received is 5. Therefore, the updated RX_Next is 5;

[0269] For AM RLC entity 2, the set of COUNTs corresponding to received PDCP PDUs satisfying RX_DELIV1+1<=COUNT<=RX_DELIV2–1 is {5}, then the maximum COUNT value is 5, the SN of the RLC SDU corresponding to the PDCP PDU is RLC_SN=3, and the SN of the first RLC SDU with SN>3 and not completely received is 5, so the updated RX_Next is 5.

[0270] FIG3 is a flow chart of a method for processing a receive window according to an embodiment of the present disclosure. As shown in FIG3 , the embodiment of the present disclosure is performed by an AM RLC entity. The method includes:

[0271] S3101: Send a first RLC SDU to a PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by an AM RLC entity.

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

[0273] S3102. Receive the first SN sent by the PDCP entity.

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

[0275] S3103. Process the state variable RX_Next according to the first SN.

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

[0277] The receive window processing method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3103. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and step S3103 may be implemented as an independent embodiment, but are not limited thereto.

[0278] It should be noted that, in the embodiment of the present disclosure, S3101, S3102 and S3103 can be arbitrarily swapped in order and freely combined for implementation without contradiction.

[0279] FIG4 is a flow chart of a method for processing a receive window according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure is performed by a PDCP entity. The method includes:

[0280] S4101. Receive a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity.

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

[0282] S4102. Send a first SN to the AM RLC entity.

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

[0284] The method for processing a receive window according to the embodiment of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment, and step S4102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0285] It should be noted that, in the embodiment of the present disclosure, S4101 and S4102 can be arbitrarily swapped in order and freely combined for implementation without contradiction.

[0286] FIG5 is a flow chart of a method for processing a receive window according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure is executed by a communication system. The method includes:

[0287] S5101. The AM RLC entity sends a first RLC SDU to the PDCP entity.

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

[0289] S5102. The PDCP entity sends a first SN to the AM RLC entity.

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

[0291] S5103. The AM RLC entity processes the state variable RX_Next according to the first SN.

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

[0293] The receive window processing method involved in the embodiment of the present disclosure may include at least one of steps S5101 to S5103. For example, step S5201 may be implemented as an independent embodiment, step S5102 may be implemented as an independent embodiment, and step S5103 may be implemented as an independent embodiment, but are not limited thereto.

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

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

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

[0297] It should be noted that, in the embodiment of the present disclosure, S5101, S5102 and S5103 can be arbitrarily swapped in order and freely combined for implementation without contradiction.

[0298] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by the first network element 1021 in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by the second network element 1022 in any of the above methods.

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

[0300] 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 a 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 to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0301] FIG6A is a schematic diagram of the structure of an AM RLC entity proposed in an embodiment of the present disclosure. As shown in FIG6A , the AM RLC entity may include: a transceiver module 6011 and a processing module 6012 .

[0302] In some embodiments, the transceiver module 6011 is configured to send a first RLC SDU to a PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and receive a first SN sent by the PDCP entity.

[0303] In some embodiments, the processing module 6012 is configured to process the state variable RX_Next according to the first SN.

[0304] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0305] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

[0306] 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 transceiver module 6021 .

[0307] In some embodiments, the transceiver module 6021 is configured to receive a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and send a first SN to the AM RLC entity.

[0308] The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT;

[0309] The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

[0310] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device), an IoT device, or a chip, chip system, or processor that supports a network device implementing any of the above methods. It can also be a chip, chip system, or processor that supports an IoT device implementing any of the above methods. Communication device 7100 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.

[0311] As shown in Figure 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 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 7100 is used to perform any of the above methods. Optionally, one or more processors 7101 are used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0312] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 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 7101 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.

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

[0314] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 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 network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0315] 7B is a schematic diagram of the structure of a chip 7200 according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG9B , but the present disclosure is not limited thereto.

[0316] The chip 7200 includes one or more processors 7201. The chip 7200 is configured to execute any of the above methods.

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

[0318] In some embodiments, the interface circuit 7202 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. For example, the interface circuit 7202 performing the communication steps (e.g., sending and / or receiving) in the above method means that the interface circuit 7202 performs data exchange between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps (e.g., step S2102, but not limited thereto).

[0319] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes 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.

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

[0321] 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 method for processing a receiving window, characterized in that: The method is performed by an AM RLC entity in an acknowledged mode, comprising: Sending a first radio link control layer service data unit RLC SDU to a packet data convergence protocol PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; receiving a first sequence number SN sent by the PDCP entity; Processing a state variable RX_Next according to the first SN, where the state variable RX_Next is used to indicate a lower edge of a receiving window; The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first count COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT; The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

2. The method according to claim 1, characterized in that The first SN is an RLC SN of an RLC SDU corresponding to the PDCP PDU having the first COUNT in the first RLC SDU; Sending a first RLC SDU to a PDCP entity, comprising: Send the first RLC SDU and the RLC SN of the first RLC SDU to the PDCP entity.

3. The method according to claim 2, characterized in that The processing of the state variable RX_Next according to the first SN includes: Determining a second RLC SDU, where the second RLC SDU is a first RLC SDU that is not completely received and has an RLC SN that is not less than the first SN; The state variable RX_Next is updated to the RLC SN of the second RLC SDU.

4. The method according to claim 1, wherein The first SN is a PDCP SN in the first COUNT; The processing of the state variable RX_Next according to the first SN also includes: A one-to-one correspondence is established between the RLC SN of the completely received RLC SDU and the PDCP SN in the completely received RLC SDU.

5. The method according to claim 4, characterized in that The processing of the state variable RX_Next according to the first SN includes: Using the RLC SN of the RLC SDU corresponding to the first SN as the second SN; Determining a third RLC SDU, where the third RLC SDU is a first RLC SDU that is not completely received and has an RLC SN that is not less than the second SN; The state variable RX_Next is updated to the RLC SN of the third RLC SDU.

6. The method according to any one of claims 2 to 5, characterized in that: Also includes: Moving the receiving window of the AM RLC entity according to the updated state variable RX_Next and generating an RLC status report; Sending the RLC status report to an entity on the opposite side of the AM RLC entity.

7. The method according to claim 1, characterized in that The processing of the state variable RX_Next according to the first SN includes: The first SN is the RLC SN of the RLC SDU corresponding to the PDCP PDU with the first COUNT in the first RLC SDU, and the first SN is not in the receiving window of the AM RLC entity, and the state variable RX_Next is not updated.

8. The method according to claim 2 or 3, characterized in that The AM 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; The RLC SN of the first RLC SDU is sent in the following manner: The distributed unit where the AM RLC entity is located sends a GTP-U message to the centralized unit where the PDCP entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

9. The method according to any one of claims 1 to 8, characterized in that The AM 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; The receiving a first SN sent by the PDCP entity includes: The distributed unit where the AM RLC entity is located receives new air interface user plane protocol signaling NR User Plane Protocol corresponding to the AM RLC entity and sent by the centralized unit where the PDCP entity is located, where the new air interface user plane protocol signaling is used to indicate the first SN.

10. The method according to claim 2 or 3, characterized in that The AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture; The RLC SN of the first RLC SDU is sent in the following manner: The base station node where the AM RLC entity is located sends a GTP-U message to the base station node where the PDCP entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

11. The method according to any one of claims 1 to 7 and 10, characterized in that: The AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture; The receiving a first SN sent by the PDCP entity includes: The base station node where the AM RLC entity is located receives NR User Plane Protocol signaling corresponding to the AM RLC entity and sent by the base station node where the PDCP entity is located, where the NR User Plane Protocol signaling is used to indicate the first SN.

12. The method according to any one of claims 1 to 7, characterized in that: The AM RLC entity and the PDCP entity are located in the terminal; Sending a first RLC SDU to a PDCP entity, prior to which: receiving first information configured by a network device, where the first information is used to instruct an AM RLC entity to enable a first function for a receive window and a PDCP entity to enable a second function for the receive window; The first function includes: sending a first RLC SDU to a PDCP entity, receiving a first SN sent by the PDCP entity, and processing a state vector RX_Next according to the first SN; The second function includes: receiving a first RLC SDU sent by an AM RLC entity, and sending a first SN to the AM RLC entity.

13. The method according to claim 12, characterized in that The network device indicates the first information in any of the following ways: Indicating the first information in radio resource control RRC signaling; indicating the first information in a PDCP Control PDU; indicating the first information in an RLC Control PDU; Indicating the first information in a PDCP PDU header; Indicating the first information in an RLC PDU header; or, The first information is indicated in a medium access control element MAC CE.

14. The method according to any one of claims 1 to 13, characterized in that The COUNT range is [RX_DELIV1+1,RX_DELIV2-1]; Among them, RX_DELIV1 represents the state variable RX_DELIV before updating; RX_DELIV2 represents the state variable RX_DELIV after updating.

15. The method according to any one of claims 1 to 14, characterized in that: The state variable RX_DELIV before and after the PDCP entity is updated refers to the state variable RX_DELIV before and after the PDCP entity is updated due to the expiration of the t-Reordering timer.

16. The method according to claims 1-15, characterized in that The first SN is sent when the PDCP entity determines that there is a COUNT of at least one PDCP PDU corresponding to the first RLC SDU and that the COUNT is within a COUNT range.

17. A method for processing a receiving window, characterized in that: The method is performed by a PDCP entity and includes: receiving a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; Sending a first SN to the AM RLC entity; The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT; The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

18. The method according to claim 17, characterized in that The first SN is an RLC SN of an RLC SDU corresponding to the PDCP PDU having the first COUNT in the first RLC SDU; The receiving a first RLC SDU sent by the AM RLC entity includes: Receive the first RLC SDU and the RLC SN of the first RLC SDU sent by the AM RLC entity.

19. The method according to claim 18, characterized in that The first SN is determined by: Establishing a one-to-one correspondence between the RLC SN of the first RLC SDU and the COUNT of the PDCP PDU corresponding to the SN of the RLC SDU; According to the corresponding relationship and the first COUNT, an RLC SN of an RLC SDU corresponding to the PDCP PDU having the first COUNT in the first RLC SDU is determined and used as the first SN.

20. The method according to any one of claims 17 to 19, characterized in that: The AM 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; The RLC SN of the first RLC SDU is received in the following manner: The centralized unit where the PDCP entity is located receives a GTP-U message sent by the distributed unit where the AM RLC entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

21. The method according to any one of claims 17 to 20, characterized in that: The AM 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; The sending the first SN to the AM RLC entity includes: The centralized unit where the PDCP entity is located sends a new air interface user plane protocol signaling NR User Plane Protocol corresponding to the AM RLC entity to the distributed unit where the AM RLC entity is located, where the new air interface user plane protocol signaling is used to indicate the first SN.

22. The method according to any one of claims 17 to 19, characterized in that The AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture; The RLC SN of the first RLC SDU is received in the following manner: The base station node where the PDCP entity is located receives a GTP-U message sent by the base station node where the AM RLC entity is located, where the extended header of the GTP-U message indicates the RLC SN of the first RLC SDU.

23. The method according to any one of claims 17 to 19 and 22, characterized in that: The AM RLC entity and the PDCP entity are located in a network device, and the network device adopts a separate bearer in a dual connectivity architecture; The sending the first SN to the AM RLC entity includes: The base station node where the PDCP is located sends NR User Plane Protocol signaling corresponding to the AM RLC entity to the base station node where the AM RLC entity is located, where the NR User Plane Protocol signaling is used to indicate the first SN.

24. The method according to any one of claims 17 to 19, characterized in that: The AM RLC entity and the PDCP entity are located in the terminal; The receiving of the first RLC SDU sent by the AM RLC entity also includes: receiving first information configured by a network device, where the first information is used to instruct an AM RLC entity to enable a first function for a receive window and a PDCP entity to enable a second function for the receive window; The first function includes: sending a first RLC SDU to a PDCP entity, receiving a first SN sent by the PDCP entity, and processing a state vector RX_Next according to the first SN; The second function includes: receiving a first RLC SDU sent by an AM RLC entity, and sending a first SN to the AM RLC entity.

25. The method according to claim 24, characterized in that The network device indicates the first information in any of the following ways: indicating the first information in RRC signaling; indicating the first information in a PDCP Control PDU; indicating the first information in an RLC Control PDU; Indicating the first information in a PDCP PDU header; Indicating the first information in an RLC PDU header; or, The first information is indicated in a MAC CE.

26. The method according to any one of claims 17 to 25, characterized in that The COUNT range is [RX_DELIV1+1,RX_DELIV2-1]; Among them, RX_DELIV1 represents the state variable RX_DELIV before updating; RX_DELIV2 represents the state variable RX_DELIV after updating.

27. The method according to any one of claims 17 to 26, wherein: The state variable RX_DELIV before and after the PDCP entity is updated refers to the state variable RX_DELIV before and after the PDCP entity is updated due to the expiration of the t-Reordering timer.

28. The method according to claims 17-27, characterized in that Sending a first SN to the AM RLC entity includes: Determine that there is a COUNT of at least one PDCP PDU corresponding to the first RLC SDU and is within a COUNT range, and send a first SN to the AM RLC entity.

29. An AM RLC entity, characterized in that: include: a transceiver module configured to send a first RLC SDU to a PDCP entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and receive a first SN sent by the PDCP entity; a processing module, configured to process a state variable RX_Next according to the first SN, wherein the state variable RX_Next is used to indicate a lower edge of the receiving window; The first SN is an RLC SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT; The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

30. A PDCP entity, characterized in that: include: a transceiver module configured to receive a first RLC SDU sent by an AM RLC entity, where the first RLC SDU is at least one RLC SDU completely received by the AM RLC entity; and send a first SN to the AM RLC entity; The first SN is an SN of an RLC SDU corresponding to a PDCP PDU having a first COUNT in the first RLC SDU, or the first SN is a PDCP SN in the first COUNT; The first COUNT is the maximum COUNT in the COUNT range of the PDCP PDU corresponding to the first RLC SDU; the COUNT range is related to the state variable RX_DELIV before and after the PDCP entity is updated, and the state variable RX_DELIV is used to indicate the COUNT of the first PDCP SDU that the PDCP entity is waiting to submit to the upper layer.

31. An AM RLC entity, characterized in that: include: one or more processors; The processor is configured to execute the method according to any one of claims 1 to 16.

32. A PDCP entity, characterized in that: include: one or more processors; The processor is configured to execute the method according to any one of claims 17 to 28.

33. A communication system, characterized in that: include: AM RLC entity, configured to implement the method according to any one of claims 1 to 16; A PDCP entity, configured to implement the method according to any one of claims 17 to 28.

34. 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 method according to any one of claims 1 to 28.

35. A program product, characterized in that When the program product is executed by a communication device, the method according to any one of claims 1 to 28 is implemented.

Images