CN108282292B

CN108282292B - Method, sending end and receiving end for processing data

Info

Publication number: CN108282292B
Application number: CN201710010455.5A
Authority: CN
Inventors: 酉春华; 刘星; 黄曲芳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-01-06
Filing date: 2017-01-06
Publication date: 2020-10-23
Anticipated expiration: 2037-01-06
Also published as: CN108282292A

Abstract

The embodiment of the invention provides a method for processing data, a sending end and a receiving end. The method comprises the following steps: a first entity in a sending end acquires reconfiguration information, wherein the reconfiguration information comprises information for configuring the SN length of a first sequence number to a second SN length; the first entity configures the first SN length to a second SN length according to the reconfiguration information. The method, the sending end and the receiving end for processing data of the embodiment of the invention can flexibly configure the SN length and realize the lossless transmission of the data packet.

Description

Method, sending end and receiving end for processing data

Technical Field

The present invention relates to the field of communications, and in particular, to a method, a transmitting end, and a receiving end for processing data.

Background

In a Long Term Evolution (LTE) system, a radio interface protocol stack may be divided into three protocol layers, which are sequentially from bottom to top: physical layer (L1), data link layer (L2), and network layer (L3). Wherein, the data link layer (L2) is, from bottom to top: a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer. The PDCP layer processes Radio Resource Control (RRC) messages on a Control plane and Internet Protocol (IP) packets on a user plane, etc., the PDCP sublayer, after obtaining IP Data packets from an upper layer, may perform header compression and Ciphering on an IP Data packet PDCP Service Data Unit (SDU), and add a PDCP header to the processed Data packets to form PDCP Protocol Data Unit (PDU), and then deliver the PDCP PDUs to the sublayer, which also provides in-Sequence delivery and duplicate packet detection functions to the upper layer, for which there is a Sequence Number (SN) in the PDCP header in each PDCP PDU, and the PDCP also applies PDCP SNs, which are components of COUNT, when Ciphering and Deciphering, wherein COUNT is an input parameter of a Ciphering and Deciphering algorithm, in the full configuration of the L2 layer, only one fixed SN length can be used, and the SN cannot be reconfigured. Based on this, it is necessary to propose a new scheme.

Disclosure of Invention

Embodiments of the present invention provide a method, a sending end, and a receiving end for processing data, which can flexibly configure an SN length and implement lossless transmission of a data packet.

In a first aspect, a method for processing data is provided, including:

a first entity in a sending end acquires reconfiguration information, wherein the reconfiguration information comprises information for configuring the SN length of a first sequence number to a second SN length;

the first entity configures the first SN length to a second SN length according to the reconfiguration information.

In some possible implementations, after the first entity obtains the reconfiguration information, the method may further include:

the first entity suspends or stops data processing operation in the first entity, wherein the data processing operation comprises at least one operation of data encryption operation, header compression operation, integrity protection operation, data operation in the first entity transmitted to a second entity in the transmitting end, and operation of the first entity increasing SN number to data according to the used SN length.

Wherein the data encryption operation is used for preventing data from being intercepted, the header compression operation is used for saving overhead, and the integrity protection operation is used for preventing data from being tampered. It is to be understood that the explanations herein are merely intended to schematically describe the functions of the data operations and are not intended to limit the present invention.

In the embodiment of the present invention, the first entity at the sending end can flexibly configure the SN length by acquiring the reconfiguration information and configuring the first SN length as the second SN length according to the reconfiguration information, thereby implementing lossless transmission of the data packet.

In some possible implementations, the first SN length may be greater than the second SN length, or may be less than the second SN length. In other words, the sending end may change the SN length from long to short or from short to long according to the current service situation when reconfiguring the SN length, which is not limited herein. For example, the first SN length may be 18 bits (bits) and the second SN length may be 12 bits.

In some possible implementations, the first entity in the transmitting end may be any one of a plurality of entities of the transmitting end, which is not limited herein. In other words, the first entity may be any one of a packet data convergence protocol PDCP entity, a radio link layer control protocol RLC entity, a medium access control MAC entity, and a physical PHY entity in the transmitting end.

In some possible implementations, for after the SN length changes: how to let the receiving end know whether the received data packet uses the first SN length or the second SN length provides a solution.

Optionally, the sending end and the receiving end perform "handshake interaction" so that the receiving end knows whether the received data packet uses the first SN length or the second SN length.

In some possible implementation manners, the first entity sends first information to a third entity in a receiving end, where the first information is used to notify the third entity of a first parameter of the first SN length, and the first parameter is used to identify a protocol data unit PDU corresponding to the first SN length.

In an embodiment of the present invention, the first entity and the third entity belong to corresponding or peer entities of the same layer. For example, the first entity at the transmitting end is a PDCP entity, and correspondingly, the third entity at the receiving end is also a PDCP entity. Or, for example, the first entity of the sending end is an RLC entity, and correspondingly, the third entity of the receiving end is also an RLC entity.

It should be noted that the PDU corresponding to the first SN length may include various situations. For example, if the first parameter indicates an end bit when a first SN length is used, the PDU corresponding to the first SN length may be understood as: using the PDU of the first SN length before the end bit; alternatively, if the first parameter indicates a plurality of SN numbers in the first SN length (for example, numbering by using a bitmap method), the PDU corresponding to the first SN length may be understood as the PDU corresponding to the plurality of SN numbers, which is not limited in this embodiment of the present invention.

Here, the first entity may send the first information to a third entity in the receiving end, so that the third entity knows the first parameter of the first SN length. Wherein the first parameter comprises at least one of a COUNT value, an SN number of a first SN length. Wherein, the COUNT value can be uniquely allocated to a certain PDU, and the COUNT value can be used for identifying the PDU.

In some possible implementations, the first information may be sent through a PDCP message, or may also be sent through an RRC message, which is not limited thereto.

In some possible implementations, the method may further include:

the first entity receives second information sent by the third entity;

and enabling the second SN length by the first entity according to the second information and the reconfiguration information.

In some possible implementations, the first entity may resume or start data processing operations in the first entity after receiving the second information. For example, the first entity starts to enable the second SN length for numbering, and delivers data to an entity at a lower layer of a protocol stack.

In some possible implementations, the first entity may further reset at least one of the first entity and the second entity after receiving the second information. For example, the PDCP entity may Reset (Reset) the PDCP entity and/or the RLC entity after receiving the second information.

In some possible implementations, the method may further include:

the first entity determines the first information.

In particular, the first entity may determine the first information. Alternatively, the first information may include status information of SNs, number information (including a number of a certain specific SN), and the like. Alternatively, the status information may be understood as an SN set, such as a bitmap file, etc.

In some possible implementation manners, the second information is sent to the first entity by the third entity after a first timer expires, where the first timer is used for the third entity to obtain the PDU with the first SN length during the running period of the first timer, and the first timer is started when the third entity obtains the first information.

In some possible implementations, after the first entity receives the second information sent by the third entity, the method further includes:

the first entity resumes or starts the data processing operation in the first entity.

In some possible implementation manners, the method may also be applied to a handover scenario of a sending end, where the sending end is a target network device, and the reconfiguration information is carried in a handover confirmation message acquired by the target network device, and the method further includes:

the target network equipment receives an SN status report sent by source network equipment, wherein the SN status includes a first PDU and a first Service Data Unit (SDU), the first SDU is generated by the source network equipment according to the PDU which receives an acknowledgement message, the first PDU includes at least one of the PDU which exceeds a corresponding window of the second SN length when the first SN length is used for transmitting data and the PDU which does not receive the acknowledgement message when the second SN length is used, and the second SN length is smaller than the first SN length;

the target network equipment numbers and transmits the PDU and the first SDU which exceed the corresponding window of the second SN length when transmitting data by using the first SN length by using the SN of the first SN length; or,

and the target network equipment numbers and transmits the PDU which does not receive the confirmation message when the second SN length is used by the target network equipment by using the SN with the second SN length.

In some possible implementations, the method may further include:

a second entity in the sending end sends first data to the first entity, wherein the first data is cached data in the second entity;

the first entity adds the serial number of the second SN length to the first data to obtain second data, and the second data is sent to the second entity;

and the first entity sends first indication information to the second entity, wherein the first indication information is used for informing the SN length corresponding to the second data.

In some possible implementations, the method may further include:

the second entity adds second indication information to a Protocol Data Unit (PDU) in the second entity, wherein the second indication information is used for indicating the SN length corresponding to the PDU of the first entity in the PDU, and the second indication information is carried in a reserved field in a frame structure corresponding to the PDU;

and the second entity sends the PDU to a fourth entity in the receiving end, and the second indication information is used for informing the fourth entity of the SN length corresponding to the PDU.

Here, the first data may include: at least one of an RLC SDU unprocessed by the RLC entity, an RLC PDU not transmitted outside a transmission window of the RLC entity, and a PDU which is ACK-ready and not ACK-ready in the transmission window of the RLC entity.

In some possible implementations, before the first entity receives the second information sent by the third entity, the method may further include:

after the first entity suspends or stops the data processing operation in the first entity, the first entity determines the service data unit SDU of the first entity as unavailable data, and the unavailable data indicates that the first entity does not process a scheduling request SR triggered by a third entity aiming at the SDU of the first entity.

In a second aspect, a method for processing data is provided, comprising:

a first entity in a sending end generates or acquires identification information, wherein the identification information is used for indicating the SN length used by a Protocol Data Unit (PDU), and the identification information is carried in a reserved field in a frame format corresponding to the PDU;

and the first entity sends the PDU to a third entity in a receiving end.

In the embodiment of the present invention, for example, the PDCP Head may carry identification information indicating different SN lengths. Therefore, the first entity in the sending end can send the PDU to the third entity in the receiving end, the SN length can be flexibly configured, and the lossless transmission of the data packet is realized.

In some possible implementation manners, there is a corresponding relationship between the identification information and the SN length, where the corresponding relationship is predefined in a protocol, or the corresponding relationship is carried in reconfiguration information.

In a third aspect, a method for processing data is provided, including:

a third entity in a receiving end receives first information sent by a first entity in a sending end;

and the third entity acquires a data packet corresponding to a first SN length according to the first information, wherein the first SN length is the SN length of the first entity before the SN length reconfiguration is carried out.

In the embodiment of the present invention, a third entity in a receiving end receives first information sent by a first entity in a sending end, and obtains a data packet corresponding to a first SN length according to the first information, where the first SN length is an SN length before SN length reconfiguration is performed by the first entity, so as to interact with the sending end, notify the sending end to enable a second SN length, and flexibly configure the SN length, thereby implementing lossless transmission of the data packet.

In some possible implementation manners, the third entity obtains a first parameter of the first SN length according to the first information;

and the third entity receives the protocol data unit PDU corresponding to the first SN length according to the first parameter.

In some possible implementation manners, optionally, after the third entity receives the PDU corresponding to the first SN length according to the first parameter, the third entity may Reset the PDCP entity and/or the RLC entity

In some possible implementations, the method may further include:

and after the third entity acquires the data packet corresponding to the first SN length, the third entity sends second information to the first entity, wherein the second information is used for informing the first entity of starting a second SN length.

In some possible implementations, the method may further include:

when the third entity acquires the first information, the third entity starts a first timer;

the third entity obtains a protocol data unit PDU corresponding to the first SN length during the running period of the first timer;

wherein the third entity sends second information to the first entity, including:

and the third entity sends second information to the first entity after the first timer is overtime.

That is, when transmitting data in the RLC UM mode, the third entity at the receiving end may start a timer (e.g., a first timer) when receiving the first information, and then wait for or receive a PDU corresponding to the first SN length (specifically, a PDU corresponding to the first parameter) during the running of the timer. Then, after the first timer expires, the third entity may send second information to the first entity so as to notify the first entity of enabling a second SN length.

In some possible implementations, the duration of the first timer may be pre-configured by the network device, or may be specified in a protocol, which is not limited herein.

In a fourth aspect, a method for processing data is provided, comprising:

a third entity in a receiving end receives a protocol data unit PDU sent by a first entity in a sending end;

the third entity obtains identification information according to the PDU, wherein the identification information is used for indicating the SN length used by a Protocol Data Unit (PDU), and the identification information is carried in a reserved field in a frame format corresponding to the PDU;

and the third entity determines at least one item of SN length and SN number used by the PDU according to the identification information.

In the method for processing data according to the embodiment of the present invention, the third entity in the receiving end may obtain the identification information, and determine at least one of the SN length and the SN number used by the PDU according to the identification information, so that the SN length can be flexibly configured, and lossless transmission of a data packet is achieved.

That is, the receiving end (for example, a third entity in the receiving end) may also obtain the indication information, specifically, the reserved field, from the PDCP Head, so as to know which PDUs adopt the old SN length and which PDUs adopt the new SN length, so as to implement accurate decryption.

In the embodiment of the present invention, there is a mapping relationship (mapping) between the identification information and the SN length, and the mapping relationship may be predefined in a protocol.

In a fifth aspect, a method for processing data is provided, comprising:

if the SN length of the sequence number of at least one Protocol Data Unit (PDU) in a sending end is about to change, the sending end generates or acquires first information, and the first information is used for determining at least one PDU which is not changed;

and the sending end sends the first information to a receiving end.

In the embodiment of the present invention, if the SN length of at least one PDU in the sending end is to be changed, the sending end may generate or obtain first information, where the first information is used to determine at least one PDU that is not changed, and send the first information to the receiving end, so that when the SN length is changed, lossless transmission of a data packet can be ensured.

With reference to the fifth aspect, in a first possible implementation manner, the first information indicates a last PDU that is not changed.

Here, the first information may indicate: and in the at least one PDU, the last PDU when the SN length is not changed enables the receiving end to know the last PDU.

Or, optionally, the first information may also indicate: and some PDUs with unchanged SN length in the at least one PDU are ensured, so that a receiving end can know some PDUs with unchanged SN length.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner, the method may further include:

the sending end receives second information sent by the receiving end, the second information is used for the receiving end to indicate that the sending end is allowed to send the at least one PDU, and the SN length of the at least one PDU is about to change;

after the SN length of the at least one PDU is changed, the transmitting end transmits the at least one PDU to the receiving end.

In this embodiment of the present invention, the sending end may receive the second information, and learn that it may start sending at least one PDU with a changed SN length. Further, after the SN length of the at least one PDU is changed, the transmitting end may transmit the one PDU (i.e., the PDU with the changed SN length) to the receiving end. In other words, the transmitting end needs to obtain the second information to be allowed to transmit the at least one PDU using the changed SN length. The "first information" and the "second information" may be understood as related information when the sending end and the receiving end perform "handshake interaction".

Optionally, after the SN length of the at least one PDU is changed, the transmitting end does not generate the PDU of the SN length before the SN length is changed.

With reference to the fifth aspect, any one of the first possible implementation manner of the fifth aspect and the second possible implementation manner of the fifth aspect, in a third possible implementation manner, the method may further include:

the PDCP entity of the sending end sends at least one PDU with unchanged SN length to an RLC entity of the sending end; optionally, the RLC entity of the transmitting end transmits at least one PDU with unchanged SN length.

With reference to the second possible implementation manner of the fifth aspect or the third possible implementation manner of the fifth aspect, in a fourth possible implementation manner, the second information is that the receiving end receives the at least one unchanged PDU or that the first timer is sent to the transmitting end after the first timer expires, where the first timer is used for the receiving end to obtain the at least one unchanged PDU during the running period of the first timer.

Optionally, the duration of the first timer may be preconfigured by the network device, or may be specified in the protocol, which is not limited herein.

With reference to the fifth aspect, or any one of the first possible implementation manner of the fifth aspect, the second possible implementation manner of the fifth aspect, the third possible implementation manner of the fifth aspect, and the fourth possible implementation manner of the fifth aspect, in a fifth possible implementation manner, before a PDU is sent to a receiving end, the PDU carries indication information, where the indication information indicates that an SN length of the PDU is changed or an SN length of an unchanged PDU occurs in the PDU.

In a sixth aspect, there is provided a method for processing data, comprising:

a receiving end receives first information sent by a sending end;

the receiving end determines at least one unchanged PDU according to the first information;

wherein the first information is generated or obtained by the sending end when the SN length of at least one PDU in the sending end is about to change.

In the embodiment of the present invention, the receiving end may receive the first information sent by the sending end, and then the sending end may generate or obtain the first information and determine at least one unchanged PDU according to the first information, which may ensure lossless transmission of a data packet when the SN length changes.

Optionally, the determining, by the receiving end, at least one unchanged PDU according to the first information includes: and the receiving end determines the SN number or the COUNT value of at least one unchanged PDU according to the first information.

With reference to the sixth aspect, in a first possible implementation manner, the first information indicates a last PDU that is not changed.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner, the method may further include:

the receiving end sends second information to the sending end, and the second information indicates that the sending end is allowed to send the at least one PDU;

and after the SN length of the at least one PDU is changed, the receiving end receives the at least one PDU sent by the sending end.

Optionally, after the PDCP entity of the sending end sends at least one PDU that is not changed to the RLC of the sending end, the PDCP entity of the receiving end stops generating PDUs whose SN lengths are not changed.

With reference to the sixth aspect, the first possible implementation manner of the sixth aspect, and any one of the second possible implementation manner of the sixth aspect, in a third possible implementation manner, the method may further include:

after the receiving end acquires the first information, starting a first timer;

the receiving end acquires the at least one unchanged PDU during the running period of the first timer;

and after the receiving end receives the at least one unchanged PDU or the first timer is overtime, the receiving end sends the second information to the sending end, wherein the second information is used for indicating that the sending end is allowed to send the at least one PDU, and the SN length of the at least one PDU is about to change.

In this embodiment of the present invention, after acquiring the first information, the receiving end may start a first timer, then acquire the at least one unchanged PDU during the operation of the first timer, and after receiving the at least one unchanged PDU or the first timer times out, the receiving end sends the second information to the sending end, so as to notify the sending end that the at least one PDU may be continuously sent after the SN length is changed.

With reference to the sixth aspect, the first possible implementation manner of the sixth aspect, the second possible implementation manner of the sixth aspect, and any one of the third possible implementation manner of the sixth aspect, in a fourth possible implementation manner, the method may further include:

the receiving end receives the PDU sent by the sending end, the PDU carries indication information, and the indication information indicates that the SN length of the PDU is changed or the SN length of the unchanged PDU is generated;

and the receiving end determines the SN length of the PDU according to the indication information.

Here, the receiving end may read the SN length of the PDU from the indication information carried in the PDU sent by the sending end. It should be understood that the identification information may be understood as the aforementioned reserved field carried in the frame format corresponding to the PDU, which is only expressed in another way and is not a limitation to the present invention.

A seventh aspect provides a transmitting end, configured to perform the method in the first aspect or any possible implementation manner of the first aspect. In particular, the apparatus comprises means for performing the method of the first aspect described above or any possible implementation manner of the first aspect.

In an eighth aspect, a transmitting end is provided, configured to perform the method in the second aspect or any possible implementation manner of the second aspect. In particular, the apparatus comprises means for performing the method of the second aspect described above or any possible implementation of the second aspect.

In a ninth aspect, there is provided a receiving end configured to perform the method in the third aspect or any possible implementation manner of the third aspect. In particular, the apparatus comprises means for performing the method of the third aspect or any possible implementation manner of the third aspect.

A tenth aspect provides a receiving end configured to perform the method of the fourth aspect or any possible implementation manner of the fourth aspect. In particular, the apparatus comprises means for performing the method of the fourth aspect described above or any possible implementation manner of the fourth aspect.

In an eleventh aspect, a transmitting end is provided, configured to perform the method in the fifth aspect or any possible implementation manner of the fifth aspect. In particular, the apparatus comprises means for performing the method of the fifth aspect or any possible implementation of the fifth aspect.

In a twelfth aspect, a receiving end is provided, configured to perform the method in the sixth aspect or any possible implementation manner of the sixth aspect. In particular, the apparatus comprises means for performing the method of the sixth aspect or any possible implementation manner of the sixth aspect.

In a thirteenth aspect, a transmitting end is provided. The transmitting end includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the first aspect or any possible implementation of the first aspect.

In a fourteenth aspect, a transmitting end is provided. The transmitting end includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the second aspect or the method of any possible implementation of the second aspect.

In a fifteenth aspect, a receiving end is provided. The receiving end includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the third aspect or the method of any possible implementation of the third aspect.

In a sixteenth aspect, a receiving end is provided. The receiving end includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the fourth aspect or any possible implementation of the fourth aspect.

In a seventeenth aspect, a transmitting end is provided. The transmitting end includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the fifth aspect or any possible implementation of the fifth aspect.

In an eighteenth aspect, a receiving end is provided. The receiving end includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the sixth aspect or any possible implementation of the sixth aspect.

In a nineteenth aspect, there is provided a computer-readable storage medium storing a program for causing a transmitting end to execute the method for processing data of the first aspect described above, and any one of its various implementations.

In a twentieth aspect, there is provided a computer-readable storage medium storing a program for causing a transmitting end to execute the method for processing data of the second aspect described above, and any one of its various implementations.

In a twenty-first aspect, there is provided a computer-readable storage medium storing a program for causing a receiving end to execute the method for processing data of the third aspect and any one of its various implementations.

In a twenty-second aspect, there is provided a computer-readable storage medium storing a program for causing a receiving end to execute the fourth aspect described above and any one of its various implementations of the method for processing data.

In a twenty-third aspect, there is provided a computer-readable storage medium storing a program for causing a transmitting end to execute the fifth aspect described above, and any one of its various implementations, of a method for processing data.

A twenty-fourth aspect provides a computer-readable storage medium storing a program for causing a receiving end to execute the method for processing data of the sixth aspect described above, and any of its various implementations.

Drawings

Fig. 1 is a schematic view of a scene.

FIG. 2 is a schematic flow chart diagram of a method for processing data in accordance with an embodiment of the present invention.

FIG. 3 is a schematic interaction diagram of a method in a handover scenario according to an embodiment of the invention.

Fig. 4 is a schematic diagram of an example according to an embodiment of the present invention.

Fig. 5 is a schematic flow chart diagram of a method for processing data according to another embodiment of the present invention.

Fig. 6 is a schematic block diagram of a transmitting end according to an embodiment of the present invention.

Fig. 7 is a schematic block diagram of a receiving end according to an embodiment of the present invention.

Fig. 8 is a block diagram of a transmitting end according to an embodiment of the present invention.

Fig. 9 is a block diagram of a receiving end according to an embodiment of the present invention.

Detailed Description

The technical solution in the embodiments of the present invention will be described below with reference to the accompanying drawings.

It should be understood that the technical solutions of the embodiments of the present invention can be applied to various communication systems, for example: global System for Mobile communications (GSM) systems, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (Long Term Evolution, LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), and other current communication systems, and are particularly applicable to future New Radio (New Radio, NR) NR systems or 5G systems.

It should also be understood that, in the embodiment of the present invention, the network-side device may also be referred to as a network device or a Base Station, and the Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, or a Base Station device gNB in a future 5G network, and the present invention is not limited thereto.

It should also be understood that, in the embodiments of the present invention, a terminal device may communicate with one or more Core networks (Core networks) through a Radio Access Network (RAN), and the terminal device may be referred to as an access terminal, a User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment. The terminal device may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a future 5G network, and so on.

The following description is provided for the concepts and terms related to the embodiments of the present invention.

In LTE, the radio interface can be divided into three protocol layers, which are in turn from bottom to top: physical layer (L1), data link layer (L2), and network layer (L3). L1 is mainly used to provide wireless physical channels for transmission of higher layer services. L2 is, from bottom to top: packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC). L3 includes Radio Resource Control (RRC) sub-layer in the access stratum and Mobility Management (MM) and Call Control (CC) of the non-access stratum.

During data transmission, each sub-layer in the L2 layer may correspond to an entity. For example, the PDCP layer corresponds to a PDCP entity responsible for managing the PDCP layer, and the RLC layer corresponds to an RLC entity responsible for managing the RLC layer. For example, Data in a Radio Bearer (RB) may be processed by the PDCP entity to generate a PDCP Protocol Data Unit (PDU), the PDCP entity delivers the PDCP PDU to the corresponding RLC entity, the RLC entity generates and delivers the RLC PDU to the MAC entity for processing after the processing is completed, and the MAC entity generates and delivers the MAC PDU to the L1 layer, so as to successfully send the Data in the RB.

Wherein the RLC entity may be configured in one of the following modes:

(1) transparent Mode (TM): corresponding to TM RLC entity, TM entity for short. This mode may be considered as a null RLC since it provides only pass through (pass) functionality for data.

(2) Unacknowledged Mode (UM): corresponding to UM RLC entity, abbreviated as UM entity. This mode provides RLC functions in addition to retransmission and re-segmentation, thus providing an unreliable transport service.

(3) Acknowledged Mode (AM): corresponding AM RLC entity, AM entity for short. AM mode provides a reliable transmission service through error detection and retransmission.

The functions supported by each of the above-mentioned modes are similar to those defined in the existing protocol and will not be described in detail here.

The PDCP layer is configured to process RRC messages on a control plane, Internet Protocol (IP) packets on a user plane, non-IP packets, and the like. On the user plane, after the PDCP layer obtains a data packet from an upper layer, header compression and ciphering may be performed on the data packet, for example, a Service Data Unit (SDU), and a PDCP head may be added to the processed data packet to form a PDCP PDU, which is then delivered to the RLC layer. The PDCP layer also has the function of providing in-order delivery and duplicate packet detection to the upper layers. For this purpose, there is a Sequence Number (SN) in the PDCP head in each PDCP PDU. The PDCP also uses PDCP SNs, which are components of COUNT, which are input parameters to ciphering and deciphering algorithms, in ciphering and deciphering. For example, the COUNT value used for packet encryption may uniquely identify a packet. In the control plane, the PDCP layer provides signaling transport services for the upper RRC layer, and implements ciphering and consistency protection of the RRC signaling, and implements deciphering and consistency checking of the RRC signaling in the reverse direction.

It should be understood that, in the embodiment of the present invention, data obtained after data is processed by related functions of the protocol layer (for example, various data processing operations mentioned below) may be referred to as PDU, or may also be a term newly defined in 5G, and the embodiment of the present invention does not limit this.

In addition, the flow control mode of the PDCP mainly adopts a window mechanism, and the larger the window is, the faster the data transmission is, and the smaller the window is, the slower the data transmission is. Specifically, in the data transmission process, the sending end maintains a sending window, and the receiving end maintains a receiving window. The lengths of the transmit window and the receive window are matched. Wherein the Length of the transmission window and the reception window is equal to half of the PDCPSN Length (Length).

Currently, in the prior art, the change of SN length can only be achieved by Full configuration (Full configuration), requiring the resetting (reset) of the entire L2 layer. Embodiments of the present invention propose a method for processing data, which attempts to reconfigure the SN length, for example, in the PDCP layer or the RLC layer of the L2 layer. Furthermore, the embodiment of the invention also provides a solution for how the receiving end or the sending end knows the new and old SN lengths after the SN length reconfiguration.

In the embodiment of the present invention, a sending end may be a network device, and a corresponding receiving end may be a terminal device; alternatively, the sending end may be a terminal device, and the corresponding receiving end may be a network device, which is not limited in this invention.

Fig. 1 is a schematic view of a scene. It should be understood that the scenario in fig. 1 is introduced here as an example for the convenience of understanding, but the present invention is not limited thereto. Terminal device 11, terminal device 12, terminal device 13 and base station 21 are shown in fig. 1. For example, the base station 21 is a transmitting end, and the terminal device 11 is a receiving end.

As shown in fig. 1, terminal device 11 may communicate with base station 21, terminal device 12 may communicate with base station 21, and terminal device 13 may communicate with base station 21. Alternatively, the terminal device 12 may communicate with the terminal device 11. Or, as another case, the terminal device 13 communicates with the base station 12.

FIG. 2 shows a schematic flow chart of a method 200 for processing data according to an embodiment of the invention. The method 200 may be performed by a transmitting end. For example, the transmitting end may be base station 21 in fig. 1, and the corresponding receiving end is terminal device 11, terminal device 12, or terminal device 13 in fig. 1. For another example, the transmitting end may be terminal device 11, terminal device 12, or terminal device 13 in fig. 1, and the corresponding receiving end may be base station 21 in fig. 1. As shown in fig. 2, the method 200 includes:

s210, a first entity in a sending end acquires reconfiguration information, wherein the reconfiguration information comprises information for configuring the SN length of a first sequence number to a second SN length;

s220, the first entity configures the first SN length into a second SN length according to the reconfiguration information.

For example, when the sending end is a network device, the network device may reconfigure the SN length according to the service condition. Specifically, when the amount of service data is reduced, the network device may shorten the SN length from a long length to a short length, so as to save air interface resources; when the service data volume is increased, the network device can change the SN length from short to long, so as to improve the efficiency of data transmission, reduce the data transmission delay, and avoid packet loss. In other words, the SN length can be reconfigured according to the service data condition, and the whole L2 layer does not need to be reset, so that the lossless transmission of data can be ensured.

For example, in 5G, multiple types of flows data can be mapped simultaneously into one data bearer. For a certain data bearer, if the transmission of a certain flow data is finished or deleted, the network device may shorten the SN length to save the overhead; on the contrary, if a large amount of flow data arrives or is added to the data bearer, the network device may extend (extended) SN length to ensure data transmission efficiency.

Optionally, in the embodiment of the present invention, the first SN length may be greater than the second SN length, or may be smaller than the second SN length. In other words, the sending end may change the SN length from long to short or from short to long according to the current service situation when reconfiguring the SN length, which is not limited herein. For example, the first SN length may be 18 bits (bits) and the second SN length may be 12 bits.

Optionally, in this embodiment of the present invention, the "reconfiguration information" may be generated by the sending end or sent by the receiving end, which is not limited in this embodiment of the present invention.

For example, the "reconfiguration information" may be generated by the RRC entity at the transmitting end, or may be generated by the RRC entity at the receiving end and transmitted to the transmitting end during handover or RRC reconfiguration.

It should be noted that, in the embodiment of the present invention, the first entity in the sending end may be any entity of multiple entities of the sending end, which is not limited herein. In other words, the first entity may be any one of a packet data convergence protocol PDCP entity, a radio link layer control protocol RLC entity, a medium access control MAC entity, and a physical PHY entity in the transmitting end.

Optionally, in this embodiment of the present invention, after the first entity acquires the reconfiguration information, the method 200 may further include:

The first entity suspends or stops the data processing operation in the first entity, which may also be understood as the first entity suspending the data processing operation in the first entity.

Specifically, after acquiring the reconfiguration information, the first entity may suspend or stop data processing operations in the first entity, including encryption processing on data, header compression processing, data transmission to an entity in a lower layer of a protocol stack, and the like. For example, if the first entity is a PDCP entity, the PDCP entity may suspend or stop transmitting data to the RLC entity after acquiring the reconfiguration information.

Therefore, in the embodiment of the present invention, the first entity at the sending end can flexibly configure the SN length by acquiring the reconfiguration information and configuring the first SN length as the second SN length according to the reconfiguration information, thereby implementing lossless transmission of the data packet.

In the embodiment of the present invention, after the SN length is changed: how to let the receiving end know whether the received data packet uses the first SN length or the second SN length provides a solution.

Optionally, the sending end and the receiving end perform "handshake interaction" so that the receiving end knows whether the received data packet uses the first SN length or the second SN length. As will be described in detail below.

Optionally, as an embodiment, the method 200 may further include:

the first entity sends first information to a third entity in a receiving end, wherein the first information is used for notifying the third entity of a first parameter of the first SN length, and the first parameter is used for identifying a Protocol Data Unit (PDU) corresponding to the first SN length. In an embodiment of the present invention, the first entity and the third entity belong to corresponding or peer entities of the same layer. For example, the first entity at the transmitting end is a PDCP entity, and correspondingly, the third entity at the receiving end is also a PDCP entity. Or, for example, the first entity of the sending end is an RLC entity, and correspondingly, the third entity of the receiving end is also an RLC entity.

Specifically, the first entity may send the first information to a third entity in the receiving end, so that the third entity knows the first parameter of the first SN length. Wherein the first parameter comprises at least one of a COUNT value, an SN number of a first SN length. Wherein, the COUNT value can be uniquely allocated to a certain PDU, and the COUNT value can be used for identifying the PDU.

It should be understood that in the embodiment of the present invention, the COUNT value may be one or more; similarly, the SN number may be one or more, which is not limited.

It should also be understood that the first parameter is introduced only for describing the SN number, or the COUNT value, of the first information, and is not limiting on the present invention.

It should be noted that the PDU corresponding to the first SN length may include various situations. For example, if the first parameter indicates an end bit when a first SN length is used, the PDU corresponding to the first SN length may be understood as: the end bit and the end bit are preceded by at least one PDU or all PDUs of the first SN length; alternatively, if the first parameter indicates a plurality of SN numbers in the first SN length (for example, numbering by using a bitmap method), the PDU corresponding to the first SN length may be understood as the PDU corresponding to the plurality of SN numbers, which is not limited in this embodiment of the present invention.

For example, specifically, assuming that the end SN number determined by the PDCP entity of the sending end is 16, if the SN number at the bottom of the current sending window is 8, the PDCP entity of the sending end suspends all PDCP PDUs with SN numbers of 8 to 16 after being delivered to the RLC entity, for example, no more PDCP PDUs are delivered to the RLC entity. Alternatively, if the first parameter indicates a COUNT value, the PDCP entity at the transmitting end may deliver PDCP PDUs less than or equal to the COUNT value to the bottom layer and then suspend, for example, no more PDCP PDUs are delivered to the RLC entity. Or, for example, if the first parameter indicates a SN number with a first SN length (e.g., a SN number corresponding to the end bit), the PDCP entity at the transmitting end may submit at least one PDCP PDU corresponding to a COUNT value less than or equal to the SN number to the underlay and suspend the PDCP PDU.

For example, the first information may be understood as information, such as location information, data information, number information, etc., of the last PDU in the first SN length that the first entity notifies the third entity.

Optionally, the first information may be transmitted in the last PDU in the first SN length, or may also be transmitted in any PDU in the first SN length, which is not limited herein.

Optionally, the first information may be sent through a PDCP message, or may also be sent through an RRC message, which is not limited herein. For example, the first information may be Control information Control PDU or data information data PDU of the PDCP layer, or may be Control information located in the RRC layer.

Optionally, after the first entity submits the PDU corresponding to the first SN length (as in the foregoing cases, which are not described herein) to the second entity, the first entity may suspend or stop submitting the PDU to the second entity, that is, the PDCP of the first entity is suspended. In addition, after the PDCP of the first entity is suspended, a second SN length is enabled to perform the data processing operation in the first entity unless a second message sent by a receiving end (a corresponding third entity) is received.

Accordingly, a third entity (e.g., a PDCP entity) in the receiving end may receive the first information.

Thus, the third entity may receive the PDU corresponding to the first SN length according to the first information (as in the foregoing cases, details are not described here), so that the PDU with the first SN length may be received. Optionally, after the third entity in the receiving end receives the PDU corresponding to the first parameter, the third entity in the receiving end may reset the third entity and/or the fourth entity in the receiving end, and send second information to the first entity in the transmitting end, where the second information is used to notify that the first entity may enable the second SN length, and may also be understood as being used to notify that the first entity may recover or start the data processing operation of the first entity. For example, if the first information includes a SN end number using the first SN length, the PDCP entity of the receiving end may Reset the PDCP entity and/or the RLC entity after receiving the PDU corresponding to the SN end number.

Wherein, the receiving end Reset PDCP entity comprises at least one of the following:

(1) a Reset PDCP timer, such as the PDCP Reordering timer T-Reordering. The T-Reordering timer is used for PDCP to detect packet loss.

(2) The PDCP timer, such as the PDCP Reordering timer T-Reordering, is stopped.

(3) And setting a new Reordering _ Window according to the second SN length by the Reset PDCP Reordering Window Reordering _ Window. Optionally, the new Reordering _ Window is not greater than the second SN length. Such as the new Reordering Window being equal to half the length of the second SN.

(4) The Reset encryption and decryption algorithms encryption and decryption function. E.g., resetCOUNT, COUNT starts at 0. Including the Frame Number (HFN) and SN corresponding to the second SN length of the Reset. Wherein, HFN and SN jointly form COUNT.

(5) Reset HFN, HFN for the second SN length starts from 0.

(6) Reset the starting SN corresponding to the second SN length, starting from 0.

(7) The Reset header compression protocol.

(8) And clearing the PDCP PDU buffer of the PDCP entity.

It should be understood that (1) and (2) above are only described by taking the reordering timer as an example, and other timers may be used for specific implementation, which is not limited in the embodiment of the present invention.

Wherein, the receiving end Reset RLC entity comprises at least one of the following:

(1) a Reset RLC timer, such as the RLC Reordering timer T-Reordering. The T-Reordering timer is used for RLC to detect packet loss. Alternatively, the T-Reordering timer duration may be configured by the base station.

(2) The RLC timer, such as RLC T-Reordering, is stopped.

(3) A Reset RLC timer, such as the RLC Status Prohibit timer t-Status Prohibit. the t-statuppriohibit timer is used to prohibit transmission of RLC status reports to the transmitting end. During the running period of the t-Status Prohibit timer, the RLC Status report is not triggered. Optionally, the time length of the t-Status Prohibit timer may be configured by the base station.

(4) The RLC timer, such as RLC t-Status Prohibit, is stopped.

(5) Reset RLC AM _ Window _ Size, Window of RLC AM mode (receive Window).

(6) Reset RLC UM _ Window _ Size, Window of RLC UM mode (receive Window).

(7) And clearing the buffer of the RLC PDU of the RLC entity.

It should also be understood that (3) above is only described by taking the status prohibit timer as an example, and other timers may be used for specific implementation, which is not limited in the embodiment of the present invention.

It should also be understood that the above list is only exemplary of some possible implementations of the receiver-side Reset PDCP entity and/or RLC entity, and does not limit the present invention.

Optionally, the method 200 may further include:

the first entity receives second information sent by the third entity;

Here, the third entity sends second information to the first entity, for informing that the first entity (e.g., PDCP entity) may start enabling the second SN length, and delivers PDUs to a second entity (e.g., RLC entity) in the transmitting end, which may also be understood as informing that the first entity may resume or start data processing operations of the first entity. Wherein the PDU is a PDU of a second SN length.

Optionally, the first entity may resume or start the data processing operation in the first entity after receiving the second information. For example, the first entity starts to enable the second SN length for numbering, and delivers data to an entity at a lower layer of a protocol stack.

Optionally, the first entity may further reset at least one of the first entity and the second entity after receiving the second information.

For example, the PDCP entity may Reset (Reset) the PDCP entity and/or the RLC entity after receiving the second information.

Wherein, the sending end Reset PDCP entity comprises at least one of the following:

(1) the PDCP Timer, such as the PDCP discard Timer, is stopped. The discard Timer is used to control the transmission time of the PDCP SDU on the air interface, that is, if the discard Timer expires and is not successfully transmitted, the PDCP SDU is discarded. Alternatively, the discard Timer duration may be configured by the base station.

(2) A Reset PDCP timer. Such as PDCP discard Timer.

(3) Reset encrypts and decrypts the encryption and decryption function. E.g., resetCOUNT, COUNT starts at 0. Including the HFN and SN corresponding to the Reset second SN length.

(4) Reset HFN, HFN for the second SN length starts from 0.

(5) Reset the starting SN corresponding to the second SN length, starting from 0.

(6) The Reset header compression protocol.

(7) And clearing the PDCP PDU buffer of the PDCP entity.

It should be understood that (1) and (2) above are only described by taking the discard timer as an example, and other timers may be used in specific implementation, which is not limited in the embodiment of the present invention.

Wherein, the sending end Reset RLC entity includes at least one of the following:

(1) the RLC timer, such as the RLC forwarding timer t-Poll transmit, is stopped. the t-PollRecransmit timer is used for informing the receiving end of triggering the RLC state report, and after the t-PollRecransmit timer is overtime, the receiving end is informed of triggering the RLC state report. The RLC status report is used to inform the transmitting end which RLC PDUs are successfully received and which RLC PDUs are not successfully received. Alternatively, the t-Poll transmit timer duration may be configured by the base station.

(2) A Reset RLC timer, such as t-Poll Retransmit of RLC.

(3) Reset RLC AM _ Window _ Size, Window of RLC AM mode (transmission Window).

Reset RLC UM _ Window _ Size. Window (transmission window) of RLC UM mode.

(4) And clearing the buffer of the RLC PDU of the RLC entity.

It should be understood that (1) and (2) above are only described by taking the forwarding timer as an example, and other timers may be used in specific implementation, which is not limited in the embodiment of the present invention.

It should also be understood that the above list is only exemplary of some possible implementations of the PDCP entity and/or the RLC entity of the transmitting side, and does not limit the present invention.

Optionally, in this embodiment of the present invention, the ciphered COUNT1 corresponding to the last PDU in the first SN length has a relationship with the ciphered COUNT2 corresponding to the first PDU in the second SN length: COUNT2 ═ COUNT1+ k, where k is an integer greater than or equal to 1.

Alternatively, assuming that COUNT is Nbits and the first SN length is N1bits, the length of HFN1 corresponding to the first SN length may be inferred to be N-N1 bits; the length of the reconfigured second SN is N2bits, and the length of HFN2 corresponding to the length of the second SN is naturally N-N2bits, where N1, N2, and N are integers. That is, the SN length is changed from N1bits to N2 bits. Assuming that the SN of the last PDCP PDU of the first SN length is: SN ═ x (binary), and HFN1 ═ y (binary). The ciphering COUNT used for the PDCP PDU of the first SN length is: x y (binary). Then, with the starting SN of the second SN length enabled, there may be three cases:

(1) HFN and SN for the second SN length start from 0: SN is 0 (binary), and HFN2 is 0 (binary) in this case.

(2) The starting SN of the second SN length starts at the low N2bit of COUNT +1 HFN2 takes the high N-N2bit of COUNT.

(3) The starting SN for the second SN length starts at 0. HFN2 has a high absolute value of N1-N2 equal to HFN1+1 and a low absolute value of N-N1 complementary 00.

For example, the COUNT is 8bits, the first SN length is 6bits, and the HFN1 length corresponding to the first SN length can be inferred to be 2 bits; the length of the reconfigured second SN is 4bits, and the length of the HFN2 corresponding to the length of the second SN is naturally 4 bits. That is, the SN length is changed from 6bits to 4 bits. Assuming that the SN of the last PDCP PDU of the first SN length is: SN 100101 (binary), and HFN1 00. The ciphering COUNT used for the PDCP PDU is: 00100101. then the starting SN of the second SN length is enabled, there may be three cases:

(1) HFN and SN for the second SN length start from 0: SN is 0000, and HFN2 is 0000.

(2) The starting SN of the second SN length starts with the lower 4bits of COUNT +1, i.e., 0110. HFN2 takes the upper 4bits 0010 of COUNT.

(3) The starting SN for the second SN length starts at 0. HFN2 has 2 high bits equal to HFN1+1 and 2 low bits of 00, HFN2 being 0100.

Accordingly, the receiving end can perform data processing procedures, such as encryption and decryption, according to the above rules.

It should be understood that the above description is only exemplary in describing the relationship between the first SN length and the second SN length, and the start bit of the second SN length, and there may be more reasonable forms in practice, and the embodiments of the present invention do not limit this.

Optionally, the method 200 may further include:

the first entity determines the first information.

For example, if the bitmap method is adopted to represent: 01110001, wherein the 0 th bit to the 8 th bit are from right to left, wherein the 0 th, 4 th, 5 th, 6 th bits indicate using the second SN length for numbering, and the rest using the first SN length for numbering.

In the embodiment of the present invention, for the data transmission process of the RLC layer, an AM mode may be adopted, and an UM mode may also be adopted. Alternatively, when the UM mode is adopted, the receiving end side may introduce a timer to acquire the PDU of the first SN length.

Optionally, as an embodiment, the second information is sent to the first entity by the third entity after a first timer expires, where the first timer is used for the third entity to obtain the PDU with the first SN length during a running period of the first timer, and the first timer is started when the third entity obtains the first information.

Specifically, for the third entity at the receiving end, after receiving the first information (i.e., knowing the first parameter) sent by the first entity at the sending end, a timer (e.g., a first timer) may be started. During the operation of the first timer, the third entity may acquire or wait for the PDU corresponding to the first SN length. In other words, the first timer may be understood as being used for the receiving end to wait for the PDU corresponding to the first parameter. In addition, the third entity may send the second information to the first entity after the first timer is overtime or receives the PDU corresponding to the first parameter, so that the first entity enables a second SN length.

In this way, for a radio bearer RB in RLC UM mode, the third entity in the receiving end may start a timer, receive PDUs using the first SN length during the running of the timer, and notify the first entity in the transmitting end to enable the second SN length after the timer expires.

Therefore, in the method for processing data according to the embodiment of the present invention, the first entity at the sending end can flexibly configure the SN length by acquiring the reconfiguration information and configuring the first SN length as the second SN length according to the reconfiguration information, thereby implementing lossless transmission of the data packet.

The above describes embodiments where the sender interacts with the receiver to know when to enable a new SN length. Another embodiment provided by the present invention will be described below. In the embodiment of the present invention, the PDCP Head may carry identification information indicating different SN lengths.

Optionally, the method for processing data according to another embodiment of the present invention may further include:

the first entity sends the PDU to a third entity in a receiving end;

Optionally, there is a corresponding relationship between the identifier information and the SN length, where the corresponding relationship is predefined in a protocol, or the corresponding relationship is carried in reconfiguration information.

For example, a reserved field in the PDCP data PDU may be used to indicate the first SN length and the second SN length. For example, when the reserved field is 0, it indicates that the PDU corresponds to the first SN length (old SN length); when the reserved field is 1, it indicates that the PDU corresponds to the second SN length (new SN length).

In this way, the third entity in the receiving end can learn whether the PDU adopts the first SN length or the second SN length and the SN number under the corresponding SN length by reading the content indicated in the reserved field.

Similarly, the receiving end (or an entity in the receiving end) may also obtain the identification information, i.e. obtain the indication in the reserved field, so as to determine whether the PDU uses the first SN length or the second SN length, so as to achieve accurate decryption of the PDU.

Optionally, the method for processing data according to the embodiment of the present invention may also be applied to a handover scenario, such as a handover between base stations under one Mobility Management Entity (MME), or a handover between base stations between different MMEs. As will be described in detail below.

Optionally, the sending end is a target network device, and the reconfiguration information is carried in a handover confirmation message acquired by the target network device, where the method further includes:

the target network equipment receives an SN status report sent by source network equipment, wherein the SN status report comprises a first PDU and a first Service Data Unit (SDU), the first SDU is generated by the source network equipment according to a PDU which receives an acknowledgement message (ACK), the first PDU comprises at least one of a PDU which exceeds a corresponding window of a second SN length when the source network equipment transmits data by using the first SN length and a PDU which does not receive the acknowledgement message (ACK) by using the second SN length, and the second SN length is smaller than the first SN length;

and the target network equipment numbers and transmits the PDU which does not receive an acknowledgement message (ACK) when the second SN length is used by the target network equipment.

FIG. 3 shows a schematic interaction diagram of a method 300 in a handover scenario, according to an embodiment of the invention. It should be understood that for brevity, similar parts to those in the prior art handover scenario are not described in detail herein. Here, the sending end is a target network device in a handover scenario. As shown in fig. 3, the method 300 may include:

s301, the source network device 30 sends a handover request to the target network device 31. Optionally, the switching request may carry SN length configuration information of the terminal device (for example, the old SN length is X bits), or may not carry the SN length configuration information, which is not limited to this.

S302, the target network device 31 sends a handover confirmation message to the source network device 30, where the handover confirmation message carries reconfiguration information (for example, the reconfiguration information includes a new SN length Y bits, and it is assumed that Y is smaller than X). Correspondingly, the source network equipment sends the reconfiguration information to the terminal equipment to inform the terminal equipment of the change of the SN length. The reconfiguration information source network device may read.

S303, the source network device 30 may generate an SN status report.

S304, the source network device 30 sends an SN status report to the target network device 31.

The specific steps of the source network device generating the SN status report are as follows:

the RLC entity of the source network equipment processes the RLC PDU of the ACK buffered by the current RLC into RLC SDU and delivers the RLC SDU to the PDCP entity. And the PDCP entity generates an SN state report according to the state of the current sending window, and adopts a bitmap method to represent ACK/NACK, wherein 0 is used for representing ACK PDCP, and 1 is used for representing NACK PDCP.

S305, the source network device 30 performs Data Forwarding (Data Forwarding).

Here, since Y is smaller than X, the transmission window of the PDCP entity is made shorter by a long length. Thus, when performing data forwarding, the source network device 30 needs to process PDCP PDUs (including ACK or unacknowledged PDUs) outside the short window to obtain SDUs, and then forward the SDUs to the target network device 31.

Optionally, the source network device 30 also needs to forward PDCP PDUs (PDUs that are not ACK) in the short window to the target network device 31 during data forwarding. For example, if the first SN length is 12bits, the size of the sending window corresponding to the first SN length is 6; and if the second SN length is 6bits, the size of the sending window corresponding to the second SN length is 3. As will be illustrated in connection with fig. 4. Fig. 4 shows a schematic diagram of an example according to an embodiment of the invention. As shown in fig. 4, the transmission window of the first SN length is larger than the transmission window of the second SN length. Suppose SN of the first SN length is 1, 3 is a NACK PDCP PDU, SN is 2, 4, 5 is an ACK PDCP PDU (i.e., successfully received). As the window shrinks (becomes the second SN length), the terminal device discards PDCP PDUs with

SN

4, 5. In order to avoid packet loss, the source network device needs to forward the PDCP SDU corresponding to

SN

4 and 5 to the target network device as well. Of course, the source network device also needs to forward the NACK pdcp sdu of the second SN length to the target network device.

That is to say, in the switching scenario of the network device, the method of the embodiment of the present invention is still applicable, and can implement the reconfiguration of the SN length in the switching scenario and ensure the lossless transmission of the data packet.

Optionally, as an embodiment, the method 200 may further include:

Optionally, the method 200 may further include:

and the second entity sends the PDU to a fourth entity in the receiving end, and the second indication information is used for informing the SN length corresponding to the PDU.

Here, the first entity is a PDCP entity, and the second entity is an RLC entity. Specifically, the RLC entity may deliver data (e.g., the first data) buffered (buffer) by the RLC entity to the PDCP entity for reprocessing. The PDCP entity removes the header of the first data, including the SN number with the first SN length, adds a new header again, including the SN number with the second SN length, obtains second data, and delivers the second data to the RLC entity. Optionally, the PDCP entity may further send first indication information to the RLC entity, where the first indication information is used to notify the RLC entity of the SN length corresponding to the second data, so that an upper layer of a protocol stack knows the SN length used by the second data. In this way, the RLC entity in the sending end can obtain the SN length corresponding to the second data according to the first indication information.

In an embodiment of the present invention, the first data may include: at least one of an RLC SDU unprocessed by the RLC entity, an RLC PDU not transmitted outside a transmission window of the RLC entity, and a PDU which is ACK-ready and not ACK-ready in the transmission window of the RLC entity.

In the embodiment of the present invention, "ACK PDU" refers to a PDU that is acknowledged by a peer entity (e.g., RLC entity) at the receiving end to be successfully received.

Optionally, the RLC entity may add or add indication information (such as second indication information) to the RLC PDU in the RLC entity, where the second indication information is carried in a reserved field in a frame structure corresponding to the PDU. Optionally, the RLC entity may send the PDU carrying the second indication information to the RLC entity in the receiving end. The RLC entity in the receiving end can determine whether the current RLC PDU is a PDU with a first SN length or a PDU with a second SN length according to the second indication information, process the RLC PDU into RLC SDU, and notify the PDCP entity of the RLC SDU and the corresponding SN length, so that the PDCP entity can accurately receive or decrypt the PDCP PDU data packet, thereby implementing in-sequence delivery and lossless transmission of the data packet.

Optionally, as an embodiment, before the first entity receives the second information sent by the third entity, the method 200 may further include:

after the first entity suspends or stops the data processing operation in the first entity, the first entity determines the service data unit SDU of the first entity as unavailable data, and the unavailable data is not used for informing a MAC entity to trigger a Scheduling Request (SR).

Specifically, for example, after the PDCP entity in the transmitting end suspends or stops the data processing operation in the PDCP entity, the PDCP entity regards the service data unit SDU of the PDCP entity as unavailable data, and the unavailable data indicates that the PDCP entity in the transmitting end is not used for a Scheduling Request (SR) triggered by the MAC entity.

That is, after the PDCP entity at the transmitting end has delivered the PDCP PDU corresponding to the first SN length, the data processing operation at the PDCP entity may be suspended or stopped (as described above), for example, the PDCP entity may be suspended and no more PDCP PDUs are delivered to the RLC entity, and the stored PDCP SDUs no longer become available data. At this time, the PDCP SDU will no longer be used for responding to the scheduling request SR triggered by the MAC entity.

It should be noted that, in the embodiment of the present invention, if the SN length is shortened from long to short, or the sending/receiving window is shortened from long to short, before reconfiguring the SN, the network device needs to schedule to ensure that the SN numbers corresponding to the data packet with the long SN length are all within the short window, so as to implement lossless transmission of the data packet.

It should be understood that some of the embodiments of the present invention may be combined in some possible reasonable implementations, and the present invention is not limited thereto.

The foregoing describes a method for processing data according to an embodiment of the present invention from the perspective of a transmitting end, and the following describes a method for processing data according to an embodiment of the present invention from a receiving end. For brevity, no further description will be provided for terms or concepts related to the same or similar terms or concepts as the transmitting end.

Fig. 5 shows a schematic flow chart of a method 500 for processing data according to another embodiment of the invention. The method 500 may be performed by a receiving end, for example, the receiving end is the terminal device 11, the terminal device 12, or the terminal device 13 in fig. 1, and a corresponding transmitting end may be the base station 21 in fig. 1. For another example, the receiving end may be base station 21 in fig. 1, and the corresponding transmitting end may be terminal device 11, terminal device 12, or terminal device 13 in fig. 1. As shown in fig. 5, the method 500 includes:

s510, a third entity in a receiving end receives first information sent by a first entity in a sending end;

s520, the third entity obtains a data packet corresponding to a first SN length according to the first information, wherein the first SN length is the SN length of the first entity before the SN length reconfiguration is carried out.

Specifically, corresponding to the aforementioned "handshake interaction", a third entity (e.g., a PDCP entity) in the receiving end may receive first information sent by the sending end, and obtain a data packet corresponding to the first SN length according to the first information, so as to interact with the sending end, and notify the sending end to enable the second SN length.

Therefore, in the method for processing data according to the embodiment of the present invention, the third entity in the receiving end receives the first information sent by the first entity in the sending end, and obtains the data packet corresponding to the first SN length according to the first information, where the first SN length is the SN length of the first entity before SN length reconfiguration is performed, so as to interact with the sending end, and notify the sending end to enable the second SN length, so that the SN length can be flexibly configured, and lossless transmission of the data packet is achieved.

Optionally, S520 may include:

the third entity acquires a first parameter of the first SN length according to the first information;

Here, the related meaning of the "first parameter" is already introduced at the sending end, and is the same as that indicated at the receiving end, and for brevity, is not described herein again.

In this embodiment of the present invention, the third entity at the receiving end may obtain the first parameter of the first SN length according to the first information. The third entity may receive the data packet with the first SN length according to the first parameter, for example, if the first parameter indicates an end SN number with the first SN length, the third entity may receive a PDU corresponding to the SN number before (including) the SN number. For another example, if the first parameter indicates a plurality of SN numbers (e.g., discontinuous SN numbers in bitmap) or a plurality of COUNT values, the third entity may receive PDUs corresponding to the plurality of SN numbers or the plurality of COUNT values. For example, if the first parameter indicates a COUNT value, the PDCP entity at the receiving end may receive PDCP PDUs less than or equal to the COUNT value. Or, specifically, for example, if the first parameter indicates an SN number with the first SN length (e.g., an SN number corresponding to the end bit), the PDCP entity at the receiving end may receive a PDCP PDU corresponding to a COUNT value smaller than or equal to the SN number.

Optionally, after receiving the PDU corresponding to the first SN length according to the first parameter, the third entity may use a Reset PDCP entity and/or an RLC entity (which has been described in detail above and is not described herein again).

Optionally, the method 500 may further include:

and after the third entity acquires the PDU corresponding to the first SN length, the third entity sends second information to the first entity, wherein the second information is used for informing the first entity to start a second SN length.

Here, after receiving the data packet corresponding to the first SN length, the third entity (PDCP entity) may send second information to the first entity (PDCP entity) in the sending end, where the second information is used for a receiving end to notify the sending end to start enabling the second SN length.

Optionally, the method 500 may further include:

The foregoing describes a corresponding embodiment of the receiver side in "handshake interaction". Optionally, the receiving end may also obtain identification information indicating different SN lengths from the PDCPHead.

That is, the receiving end (e.g., a third entity in the receiving end) may also receive the PDU sent by the sending end, and then obtain the identification information according to the PDCP Head of the PDU, specifically, read the content indicated in the reserved field, so that the PDU adopts the first SN length or the second SN length, and the SN number under the corresponding SN length.

In the method for processing data according to the embodiment of the present invention, the third entity in the receiving end may obtain the identification information, and determine at least one of the SN length and the SN number used by the PDU according to the identification information, and may flexibly configure the SN length without interacting with the transmitting end, thereby implementing lossless transmission of the data packet.

Optionally, the following provides a method for processing data according to still another embodiment of the present invention, which may be performed by a transmitting end, the method including:

if the SN length of the sequence number of at least one PDU in a sending end is about to change, the sending end generates or acquires first information, and the first information is used for determining at least one PDU which is not changed;

and the sending end sends the first information to a receiving end.

Optionally, the first information indicates a last PDU that has not changed.

Optionally, the method may further include:

Here, the transmitting end may receive the second information to know that it can start transmitting at least one PDU of which SN length is changed. Further, after the SN length of the at least one PDU is changed, the transmitting end may transmit the one PDU (i.e., the PDU with the changed SN length) to the receiving end. In other words, the transmitting end needs to obtain the second information to be allowed to transmit the at least one PDU using the changed SN length. The "first information" and the "second information" may be understood as related information when the sending end and the receiving end perform "handshake interaction".

Optionally, the method may further include:

the PDCP entity of the sending end sends at least one PDU with unchanged SN length to an RLC entity of the sending end; optionally, the RLC entity of the transmitting end transmits at least one PDU with unchanged SN length;

optionally, the second information is sent to the sending end after the receiving end receives the at least one unchanged PDU or a first timer expires, where the first timer is used for the receiving end to obtain the at least one unchanged PDU during the running period of the first timer.

Optionally, the duration of the first timer may be, for example, preconfigured by the network device, or specified in the protocol, which is not limited herein.

Optionally, before sending the PDU, the PDU carries indication information indicating that the PDU has changed its SN length or has not changed its SN length.

Here, the transmitting end may read the SN length of the PDU from the indication information carried by the PDU. It should be understood that the identification information may be understood as the aforementioned reserved field carried in the frame format corresponding to the PDU, which is only expressed in another way and is not a limitation to the present invention.

Optionally, the following provides a method for processing data according to still another embodiment of the present invention, which may be performed by a receiving end, the method including:

a receiving end receives first information sent by a sending end;

Optionally, the first information indicates a last PDU that has not changed.

Optionally, the method may further include:

Optionally, in some possible implementations, after the PDCP entity of the transmitting end sends at least one PDU that is not changed to the RLC of the transmitting end, the PDCP entity of the receiving end stops generating PDUs whose SN lengths are not changed.

Optionally, the method may further include:

after the receiving end acquires the first information, starting a first timer;

Optionally, the receiving end receives a PDU sent by a sending end, where the PDU carries indication information indicating that the PDU changes the SN length of the PDU or does not change the SN length of the PDU;

Therefore, the receiving end can receive the first information sent by the sending end, and the sending end can generate or obtain the first information and determine at least one unchanged PDU according to the first information, so that when the SN length changes, the lossless transmission of the data packet can be ensured.

The foregoing describes a method for processing data according to an embodiment of the present invention, and the following describes a transmitting end and a receiving end according to an embodiment of the present invention.

Fig. 6 shows a schematic block diagram of a transmitting end 600 according to an embodiment of the present invention. As shown in fig. 6, the transmitting end 600 includes:

a first entity 610, configured to obtain reconfiguration information, where the reconfiguration information includes information for configuring a first sequence number SN length as a second SN length;

the first entity 610 is further configured to configure the first SN length to a second SN length according to the reconfiguration information.

Optionally, as an embodiment, the first entity 610 is further configured to: after the reconfiguration information is acquired, suspending or stopping data processing operation in the first entity, where the data processing operation includes at least one of data encryption operation, header compression operation, integrity protection operation, data operation in the first entity transmitted to a second entity in the transmitting end, and operation in which the first entity adds an SN number to data according to the used SN length.

Optionally, as an embodiment, the first entity 610 is further configured to: and sending first information to a third entity in a receiving end, wherein the first information is used for notifying the third entity of a first parameter of the first SN length, and the first parameter is used for identifying a Protocol Data Unit (PDU) corresponding to the first SN length.

Optionally, as an embodiment, the first entity 610 is further configured to:

receiving second information sent by the third entity;

and enabling the second SN length according to the second information and the reconfiguration information.

Optionally, as an embodiment, the first entity 610 is further configured to:

determining the first information;

and after the first entity finishes processing the PDU corresponding to the first information according to the first information, suspending or stopping the data processing operation in the first entity.

Optionally, as an embodiment, the first entity 610 is further configured to:

and after the first entity receives the second information sent by the third entity, recovering or starting the data processing operation in the first entity.

Optionally, as an embodiment, the sending end 600 may further include:

the second entity is used for sending first data to the first entity, wherein the first data is cached data in the second entity;

the first entity is further configured to add the number of the second SN length to the first data to obtain second data, and send the second data to the second entity;

the first entity is further configured to send first indication information to the second entity, where the first indication information is used to notify the SN length corresponding to the second data.

Optionally, as an embodiment, the second entity is further configured to add second indication information to a protocol data unit PDU in the second entity, where the second indication information is carried in a reserved field in a frame structure corresponding to the PDU;

and the second indication information is used for notifying the SN length corresponding to the PDU.

The sending end 600 according to the embodiment of the present invention may execute the method 200 for processing data according to the embodiment of the present invention, and the above and other operations and/or functions of each module in the sending end 600 are respectively for implementing corresponding flows of the foregoing methods, and are not described herein again for brevity.

Therefore, at the transmitting end 600 in the embodiment of the present invention, the first entity at the transmitting end can flexibly configure the SN length by acquiring the reconfiguration information and configuring the first SN length as the second SN length according to the reconfiguration information, thereby implementing lossless transmission of the data packet.

Optionally, as an embodiment, the present invention further provides a sending end, including:

a first entity (which may be the first entity 610 described above) configured to generate or obtain identification information, where the identification information is used to indicate an SN length used by a protocol data unit PDU, and the identification information is carried in a reserved field in a frame format corresponding to the PDU;

the first entity is further configured to send the PDU to a third entity in a receiving end.

Fig. 7 illustrates a receiving end 700 according to an embodiment of the present invention. As shown in fig. 7, the receiving end 700 includes:

a third entity 710, configured to receive first information sent by a first entity in a sending end;

the third entity 710 is further configured to obtain, according to the first information, a data packet corresponding to a first SN length, where the first SN length is an SN length before SN length reconfiguration of the first entity.

Optionally, as an embodiment, the third entity 710 is specifically configured to:

acquiring a first parameter of the first SN length according to the first information;

and receiving the protocol data unit PDU corresponding to the first SN length according to the first parameter.

Optionally, as an embodiment, the third entity 710 is further configured to:

and after the data packet corresponding to the first SN length is obtained, sending second information to the first entity, wherein the second information is used for informing the first entity to start a second SN length.

Optionally, as an embodiment, the third entity 710 is further configured to:

starting a first timer when the first information is acquired;

acquiring a Protocol Data Unit (PDU) corresponding to the first SN length during the running period of the first timer;

and after the first timer is overtime, sending second information to the first entity.

Optionally, as an embodiment, the present invention further provides a receiving end, including:

a third entity (which may be the third entity 710 described above) configured to receive the protocol data unit PDU sent by the first entity in the sending end;

the third entity 710 is further configured to obtain identification information according to the PDU, where the identification information is used to indicate an SN length used by a protocol data unit PDU, and the identification information is carried in a reserved field in a frame format corresponding to the PDU;

the third entity 710 is further configured to determine at least one of an SN length and an SN number used by the PDU according to the identification information.

Optionally, as an embodiment, there is a corresponding relationship between the identification information and the SN length, where the corresponding relationship is predefined in a protocol, or the corresponding relationship is carried in reconfiguration information.

The receiving end 700 according to the embodiment of the present invention may execute the method 500 for processing data according to the embodiment of the present invention, and the above and other operations and/or functions of each module in the receiving end 700 are respectively for implementing corresponding flows of the foregoing methods, and are not described herein again for brevity.

Therefore, the third entity 710 in the receiving end 700 in the embodiment of the present invention receives the first information sent by the first entity in the sending end, and obtains the data packet corresponding to the first SN length according to the first information, where the first SN length is the SN length before the SN length reconfiguration is performed by the first entity, so as to interact with the sending end, notify the sending end to start the second SN length, and can flexibly configure the SN length, thereby implementing lossless transmission of the data packet.

Fig. 8 shows a structure of a transmitting end according to an embodiment of the present invention, which includes at least one processor 802 (e.g., a CPU), at least one network interface 803 or other communication interface, and a memory 804. Optionally, a receiver 805 and a transmitter 806 are also provided. The processor 802 is configured to execute executable modules, such as computer programs, stored in the memory 804. The Memory 804 may include a Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection with at least one other network element is realized through at least one network interface 803 (which may be wired or wireless). The receiver 805 and the transmitter 806 are used to transmit various signals or information. The sender may be a first entity in the sender.

In some embodiments, the memory 804 stores a program 8041, which program 8041 may be executed by the processor 802 to perform the methods of the transmitting end of the embodiments of the present invention described above.

Fig. 9 shows a structure of a receiving end according to an embodiment of the present invention, which includes at least one processor 902 (e.g., a CPU), at least one network interface 903 or other communication interface, and a memory 904. Optionally, a receiver 905 and a transmitter 906 are also possible. The processor 902 is configured to execute executable modules, such as computer programs, stored in the memory 904. The Memory 904 may comprise a high-speed Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection with at least one other network element is realized through at least one network interface 903 (which may be wired or wireless). The receiver 905 and the transmitter 906 are used to transmit various signals or information. The receiving end may be a third entity in the receiving end.

In some embodiments, memory 904 stores a program 9041, and program 9041 is executable by processor 902 to perform the method of the receiving end of the embodiments of the present invention as described above.

It should be understood that, in the embodiment of the present invention, the transmitting end and the receiving end may perform some or all of the steps in the above embodiments, and these steps or operations are merely examples, and the embodiment of the present invention may also perform other operations or variations of various operations. Further, the various steps may be performed in a different order presented in the above-described embodiments, and it is possible that not all of the operations in the above-described embodiments are performed.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or make a contribution to the prior art, or may be implemented in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only a specific implementation of the embodiments of the present invention, but the scope of the embodiments of the present invention is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the embodiments of the present invention, and all such changes or substitutions should be covered by the scope of the embodiments of the present invention. Therefore, the protection scope of the embodiments of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for processing data, comprising:

the first entity configures the first SN length into a second SN length according to the reconfiguration information;

after the first entity acquires the reconfiguration information, the method further includes:

the first entity suspends or stops data processing operation in the first entity, wherein the data processing operation comprises at least one operation of data encryption operation, header compression operation, integrity protection operation, data operation in the first entity transmitted to a second entity in the transmitting end, and operation of the first entity increasing SN number to data according to the used SN length;

the sending end is a target network device, the reconfiguration information is carried in a handover confirmation message acquired by the target network device, and the method further includes:

the target network equipment receives an SN status report sent by source network equipment, wherein the SN status includes a first Protocol Data Unit (PDU) and a first Service Data Unit (SDU), the first SDU is generated by the source network equipment according to the PDU receiving an acknowledgement message, the first PDU includes at least one of the PDU of a corresponding window exceeding the second SN length when the first SN length is used for transmitting data and the PDU without receiving the acknowledgement message when the second SN length is used, and the second SN length is smaller than the first SN length;

2. The method of claim 1, further comprising:

the first entity sends first information to a third entity in a receiving end, wherein the first information is used for notifying the third entity of a first parameter of the first SN length, and the first parameter is used for identifying a Protocol Data Unit (PDU) corresponding to the first SN length.

3. The method of claim 2, further comprising:

the first entity receives second information sent by the third entity;

4. A method according to claim 2 or 3, characterized in that the method further comprises:

the first entity determining the first information;

wherein the first entity suspending or stopping data processing operations in the first entity comprises:

and after the first entity processes the PDU corresponding to the first information according to the first information, the first entity suspends or stops the data processing operation in the first entity.

5. The method according to claim 2 or 3, wherein the first information is sent via a packet data Convergence PDCP message or a radio resource control RRC message.

6. The method according to claim 3, wherein the second information is sent to the first entity by the third entity after a first timer expires, wherein the first timer is used for the third entity to obtain the PDU corresponding to the first SN length during a running period of the first timer, and the first timer is started when the third entity obtains the first information.

7. The method according to claim 3 or 6, wherein after the first entity receives the second information sent by the third entity, the method further comprises:

8. The method of claim 7, further comprising:

the first entity resets at least one of the first entity and the second entity.

9. The method of claim 1, further comprising:

the first entity generates or acquires identification information, wherein the identification information is used for indicating the SN length used by a Protocol Data Unit (PDU), the identification information is carried in a reserved field in a frame format corresponding to the PDU, and the reconfiguration information comprises the identification information;

and the first entity determines at least one item of SN length and SN number used by the PDU according to the identification information.

10. The method of claim 9, wherein the identification information has a correspondence with an SN length, wherein the correspondence is predefined in a protocol, or wherein the correspondence is carried in the reconfiguration message.

11. The method of claim 1, further comprising:

12. The method of claim 11, further comprising:

the second entity adds second indication information to a Protocol Data Unit (PDU) in the second entity, wherein the second indication information is carried in a reserved field in a frame structure corresponding to the PDU;

and the second entity sends the PDU to a fourth entity in a receiving end, and the second indication information is used for informing the fourth entity of the SN length corresponding to the PDU.

13. The method according to claim 3 or 6, wherein before the first entity receives the second information sent by the third entity, the method further comprises:

14. A transmitting end, comprising:

a first entity, configured to acquire reconfiguration information, where the reconfiguration information includes information that configures a first sequence number SN length as a second SN length;

the first entity is further configured to configure the first SN length to a second SN length according to the reconfiguration information;

the first entity is further to:

after the reconfiguration information is acquired, suspending or stopping data processing operation in the first entity, where the data processing operation includes at least one of data encryption operation, header compression operation, integrity protection operation, data operation in the first entity transmitted to a second entity in the transmitting end, and operation of the first entity increasing an SN number to data according to the used SN length;

the sending end is a target network device, the reconfiguration information is carried in a handover confirmation message acquired by the target network device, and the sending end is configured to:

receiving an SN status report sent by source network equipment, wherein the SN status includes a first Protocol Data Unit (PDU) and a first Service Data Unit (SDU), the first SDU is generated by the source network equipment according to the PDU receiving an acknowledgement message, the first PDU includes at least one of the PDU which exceeds a corresponding window of the second SN length when the first SN length is used for transmitting data and the PDU which does not receive the acknowledgement message when the second SN length is used, and the second SN length is smaller than the first SN length;

using the SN with the first SN length to number and transmit the PDU and the first SDU which exceed the corresponding window with the second SN length when the first SN length is used for transmitting data; or,

and numbering and transmitting the PDU which does not receive the confirmation message when the second SN length is used by using the SN of the second SN length.

15. The transmitting end of claim 14, wherein the first entity is further configured to:

and sending first information to a third entity in a receiving end, wherein the first information is used for notifying the third entity of a first parameter of the first SN length, and the first parameter is used for identifying a Protocol Data Unit (PDU) corresponding to the first SN length.

16. The transmitting end of claim 15, wherein the first entity is further configured to:

receiving second information sent by the third entity;

17. A transmitting end according to claim 15 or 16, characterized in that the first entity is further configured to:

determining the first information;

18. The transmitting end of claim 16, wherein the first entity is further configured to:

19. The transmitter according to claim 14, wherein the transmitter further comprises:

20. The sender according to claim 19, wherein the second entity is further configured to add second indication information to a protocol data unit PDU in the second entity, where the second indication information is carried in a reserved field in a frame structure corresponding to the PDU;

and the second indication information is used for notifying the fourth entity of the SN length corresponding to the PDU.